# Page Not Found

The URL `files/DV4gfEaElgI0rTMBhKVv` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [2.1 -Padrão, regras e "frescuras" do JCL](https://buga.gitbook.io/notas-de-mainframe-do-buga/capitulo-2-jcl/2.1-padrao-regras-e-frescuras-do-jcl.md)
- [Ambiente](https://buga.gitbook.io/notas-de-mainframe-do-buga/conceitos/ambiente.md)
- [Rascunhos e anotações prova certificação CICS](https://buga.gitbook.io/notas-de-mainframe-do-buga/capitulo-8-cics/rascunhos-e-anotacoes-prova-certificacao-cics.md)
- [Tópicos em PL/I do Buga](https://buga.gitbook.io/notas-de-mainframe-do-buga/capitulo-4-pl-1/topicos-em-pl-i-do-buga.md)
- [2.5 - Detalhamento adicional](https://buga.gitbook.io/notas-de-mainframe-do-buga/capitulo-2-jcl/2.5-detalhamento-adicional.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://buga.gitbook.io/notas-de-mainframe-do-buga/capitulo-2-jcl/2.1-padrao-regras-e-frescuras-do-jcl.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://buga.gitbook.io/notas-de-mainframe-do-buga/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://buga.gitbook.io/notas-de-mainframe-do-buga/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/notas-de-mainframe-do-buga/capitulo-2-jcl/2.1-padrao-regras-e-frescuras-do-jcl.md`).

You may also use `Accept: text/markdown` header for content negotiation.