> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/definition-and-management-of-buffer-files/definition-in-the-vsam-catalog.md).

# Definition in the VSAM catalog

## Specific Buffer <a href="#toc149127358" id="toc149127358"></a>

It is defined and deleted by editran/G through calls to “IDCAMS”. It contains a single transmission session.

It only needs to be defined in CICS, since it is editran/G that defines and deletes it based on the profile data.

In any case, the ZTBPJITE jcl defines a specific buffer file with the following characteristics:&#x20;

```
DEFINE CLUSTER                          -                 
      (NAME(KI.EGDC.ZTBP.ZTBPFR1)         -                  
           VOL(DES801)                     -                 
           FREESPACE(25 25)                -                 
           REC (100 100)                   -                 
           RECORDSIZE(04074 04074)       -                   
           SHAREOPTIONS(2 3)               -                 
           KEYS(36 0)                      -                 
           INDEXED )                                    -    
         DATA                                           -    
           (NAME(KI.EGDC.ZTBP.ZTBPFR1.DATA))          -      
         INDEX                                          -    
           (NAME(KI.EGDC.ZTBP.ZTBPFR1.INDEX))                
 /*
```

## Matrix Buffer

It is advisable that it be defined by the user; this way, they have the opportunity to specify the number of records they consider appropriate.

To define it, there is a jcl (ZTBPJITM) that creates it with the following characteristics:&#x20;

```
DEFINE CLUSTER                          -                  
      (NAME(KI.EGDC.ZTBP.ZTBPFEL)         -                         
           VOL(DES502)                     -                        
           FREESPACE(25 25)                -                         
           REC (500 50)                  -                          
           RECORDSIZE(4074 4074)           -                        
           SHAREOPTIONS(3 3)               -                        
           KEYS(36 0)                      -                        
           INDEXED )                                    -           
         DATA                                           -           
           (NAME(KI.EGDC.ZTBP.ZTBPFEL.DATA))            -           
         INDEX                                          -           
           (NAME(KI.EGDC.ZTBP.ZTBPFEL.INDEX))                       
 /*
```

As can be seen, this type of buffer has SHAREOPTION (3,3).

If the file does not exist when the editran/G process starts, it will be defined by assigning to the number of records the sum of the records assigned to each of the transmission sessions associated with the presentation in progress.

## Unattended Buffer <a href="#toc149127360" id="toc149127360"></a>

It is mandatory that it be defined by the user.

To define it, there is a jcl (ZTBPJITD) that defines it with the same characteristics as the Specific Buffer, but also initializes it.

## EXCI Buffer <a href="#toc149127361" id="toc149127361"></a>

It is mandatory that it be defined by the user.

To define it, the same jcl is used as in the case of unattended buffers (ZTBPJITD).

## Public Buffer <a href="#toc149127362" id="toc149127362"></a>

It is mandatory that it be defined by the user.

It is defined in the same way as the Matrix Buffer (ZTBPJITM).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/definition-and-management-of-buffer-files/definition-in-the-vsam-catalog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
