> 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/operacion/onesait-editran-administrator/emission-application-files.md). # Emission application files The screen is displayed that allows managing application files for presentation sessions: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:27:37 OUTPUT FILES | ----------------------------------------------------------------------------- | | | | | | | | | | | | | | | | | A ---> ADMINISTRATION | | | | C ---> QUERY | | | | | | OPTION : C | | LOCAL CODE.: 0 0009994 0 | | REMOTE CODE: | | APPLICATION...: | | | | | ----------------------------------------------------------------------------- ``` If accessed without specifying a code: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:27:54 OUTPUT FILES | ----------------------------------------------------------------------------- | SELECTION CRITERIA: | | LOCAL CODE..: 0 0009994 0 REMOTE CODE.: * ******* * APPLICATION.: ****** | | S PRESENTATION SESSION CRI V.CRI FILE 1 | | - -------------------------- --- ----- ------------------------------------ | | 000099940 A00099940 EDTRF2 N /u/edixd/firmas/KI.EIDA.FFN43.OK2.EI | | 000099940 A00099940 EDTRF3 N | | 000099940 A00099940 EDTRF4 N | | 000099940 A00099940 EDTRF5 N | | 000099940 A00099940 ESTEFF N | | 000099940 A00099940 NORMA1 N | | 000099940 A00099940 NORMA2 N | | 000099940 A00099940 NORMA3 N | | 000099940 A00099940 NORMA4 N | | 000099940 A00099940 NORMA5 N | | 000099940 A00099940 NORM20 N | | 000099940 A00099940 NORM21 N | | 000099940 A00099940 NORM22 N | | | | EXIT, ADVANCE, SELECT | ----------------------------------------------------------------------------- ``` Once we have accessed: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:28:06 OUTPUT FILES | ----------------------------------------------------------------------------- | | | LOCAL CGO..: 0 0009994 0 REMOTE CGO.: A 0009994 0 APPLICATION.: EDTRF2 | | REMOTE VERSION: 5.3 | | WARNING. THIS SCREEN HANDLES UPPERCASE AND LOWERCASE. FILL IN APPROPRIATELY. | | D ORD PHYSICAL NAME FILE APPLICATION OUTPUT FR AL TR CO | | - --- -------------------------------------------- --------------- | | 01 /u/edixd/firmas/KI.EIDA.FFN43.OK2.EIDAS.xsig B E N S | | 02 KI.EIDA.F50 B N N S | | | | | | | | | | | | | | | | | | | | | | EXIT, BACK, FORWARD | ----------------------------------------------------------------------------- ``` * Up to 99 file lines are displayed. To navigate between the different possible screens, press PF7 and PF8 as usual. * Only the fields format, language, translation and compression may be modified, in the case of presentation sessions with remote Editran G version > 3.1 (it is allowed to issue files with different characteristics). If this is not the case, all its files will be issued with the same characteristics, those defined in the presentation session. In the first line of the file would appear the one defined in the presentation session profile. To delete a file line, enter D at the beginning of it or delete the corresponding file name. To add one, type the data on a free line. To modify, type the data on one already filled in. Pressing ENTER performs the update, but does not return to the previous menu and PF3 must be pressed to go back to that previous menu. The data for each line are: * **D**: Put D to delete the line. * **Order**: Sequential number of the file within the presentation. It is filled in automatically. * **Physical name of the output application file**n: MVS files (must comply with MVS rules for name segments separated by periods) and files belonging to HFS, which reside in the Unix partition of zOS. * **FR**: File format of the output file (R/B). The formats can be Record type (fixed, variable and expanded variable) and Binary type. For HFS files, B will preferably be used, although R may be used for those with delimiters ('15': line break in USS). * **AL**: Original alphabet of the data. It can be ASCII (A), EBCDIC (E) and None (N) * **TR**: Translate on output. It can take the values S (YES) or N (NO). * **CO**: File compression. It can be COMPRESSED (S) and NOT COMPRESSED (N). The user has 2 ways to operate regarding output application files: 1. Specify a profile with output files. 2. Do not specify output files in the profile. In the pre-output, include a DD ZTBGFCAR, a fixed file with length 80, whose content is the output application files and their characteristics. The format of this file, which can have up to 999,999 records (output application files), is as follows:
LevelNameLength.TypeDescription
1File format1Alfn.

Application file format:

‘R’: Record, ‘M’: Modified

1Source data language1Alfn.

Original language of the data:

‘A’: ASCII, ‘E’: EBCDIC, ‘B’: Binary

1Translate on output1Alfn.

Language in which the data are output:

‘A’: ASCII, ‘E’: EBCDIC, ‘N’: No translation

1Compression1Alfn.

Compression:

‘F’ Compressed, ‘N’ No compression

1Filler1Alfn.Separation space
1Physical name74Alfn.Physical name of the application file
1Filler1Alfn.Separation space
ℹ️ If the format, language, translation and compression fields are not specified, they will be taken from the presentation session profile. ⚠️ The dsname of the ZTBGFCAR does not have to be the same for all sessions, even though the procedure is; for this, it is suggested that the name of said file be obtained based on parameters known by the procedure. --- # 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/operacion/onesait-editran-administrator/emission-application-files.md?ask=&goal= ``` `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.