> 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-editran-profiles.md).

# Definition in Editran profiles

In the session profile, the characteristics of the input and output buffers are specified, such as the type, the record length (transfer length), and the logical and physical name.  &#x20;

```
     TRANSFER LENGTH  :  4050     
     OUTPUT BUFFER FILE  :  ZTBPFE1   INPUT BUFFER FILE:  ZTBPFR1       
     T.OUTPUT.FILE.(E/M/P/C/D):  E         T.INPUT.FILE.(E/M/C/D)  :  E             
     NETNAME EXCI          :  BATCZTBG  CURRENT UPDATE BURST REC.:      (TYPE=M)  
                                                                               
                                                                                 
    OUTPUT BUFFER    : ZTBPFE1  KI.EGDC.ZTBP.ZTBPFE1                          
    INPUT BUFFER  : ZTBPFR1  KI.EGDC.ZTBP.ZTBPFR1                         
```

When specifying a Matrix Buffer, the parameter CURRENT UPDATE BURST REC.: 025 (TYPE=M) indicates the number of records that are received without yielding control of the file to another task; that is, every certain number of records a DEQ and an ENQ are performed before continuing to receive, to prevent a very high output burst from preventing the rest of the sessions from using the buffer file.

If the value zero is entered in the parameter CURRENT UPDATE BURST REC.:, editran/P assumes that it is a Matrix buffer with SHR (2,3), so it will not perform ENQ/DEQ on it, allowing several tasks to run concurrently on the file.

In the presentation profile, the volume in which you want to catalog and the number of records in the primary space of the buffer are specified (a secondary space of 25% of the primary is assigned). &#x20;

<pre><code><strong> |-----------------------------------------------------------------------------|
</strong> |  OUTPUT APPLICATION FILE:  KI.EIDC.IGA.FICHF132                          |
 |                                                                             |
 |                   BUFFER FILE DATA |                   BUFFER FILE DATA |
 | EDITRAN SESSION             PRIMARY SPACE | EDITRAN SESSION               PRIMARY SPACE |
 |    APPLICATION      VOLSER     (REC)  |    APPLICATION      VOLSER     (REC)  |
 | ----------------- --------- -------- | ----------------- --------- -------- |
 |     PV4001         DES807     00100  |     PV4002         DES807     00300  |
 |                                      |                                      |
 |  &#x3C;F8:CONTINUE>                                                            |
 ------------------------------------------------------------------------------- 
</code></pre>

The number of records is also used to size the work files used during data loading.


---

# 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-editran-profiles.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.
