> 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-ims-en/operacion/primerospasos/administrador-de-onesait-editran/ficheros-de-aplicacion-de-emision.md). # Issuance application files ## **Administration** This screen is accessed with option 5 of the administrator menu, 1.5 of the general menu, and the execution or cancellation of the invoked function. This function can be considered complementary to the maintenance functions of presentation session profiles. ``` ------------------------------------------------------------------------------ | 21/06/26 ADMINISTRATOR EDITRAN | | 11:55:12 EMISSION APPLICATION FILES 5.3 | ------------------------------------------------------------------------------ | | | | | | | | | | | TO ADMINISTRATION | | | | C QUERY | | | | | | | | OPTION : A | | LOCAL CODE : 0 0009998 0 | | REMOTE CODE : 0 0009994 0 | | APPLICATION : TEST | | | | | | | | | ------------------------------------------------------------------------------ ``` Enter the desired option and the codes for the local entity, remote entity, and the presentation application for a specific session and a generic one for all of them, and the following screen will appear: ``` 21/06/26 11:56:47 EMISSION FILES ADMINISTRATION EDITRAN 5.3 ------------------------------------------------------------------------------ S PRESENTATION SESSION CRI VER.CRI FILE 1 - ------------------------ --- ------- ------------------------------------- 000099980000099940PRGIGA N KI.EIDA.F1GB 000099980000099940PRPSD2 N 3.0 KI.EGDI.RL.L0000999.L80.S0.R00 000099980000099940PRTCP0 S 3.0 KI.EIDA.A01 000099980000099940PRTCP1 N KI.EIDA.A01 000099980000099940PRTCP2 N KI.EIDA.A01 000099980000099940PRTCP3 N KI.EIDA.A01 000099980000099940PRTCP4 S 3.0 KI.EIDA.A01 000099980000099940PRTCP5 S 3.0 KI.EIDA.A01 000099980000099940PRTCP6 S 3.0 KI.EIDA.A01 000099980000099940PRTCP7 S 3.0 KI.EIDA.A01 000099980000099940PRTCP8 S 3.0 KI.EIDA.A01 000099980000099940PRTCP9 S 4.0 KI.EIDA.A01 000099980000099940PRTC10 N KI.EIDA.A01 000099980000099940PRTC14 S 4.0 000099980000099940PRUEBA S 4.0 KI.EIDA.F01 000099980000099940PRUEB1 N 4.0 KI.EIDA.FF14 000099980000099940PRUEFF N 3.0 ``` For a specific session, the following screen will appear: ``` ------------------------------------------------------------------------------ | 21/06/26 ADMINISTRATOR EDITRAN | | 11:57:56 EMISSION FILES ADMINISTRATION 5.3 | ------------------------------------------------------------------------------ | PRESENTATION SESSION: 0 0009998 0 - 0 0009994 0 - TEST | | REMOTE EDITRAN VERSION: 5.3 | | | | D ORDER PHYSICAL NAME EMISSION APPLICATION FILE FMT ALF TRA COM | | - ----- -------------------------------------------- --- --- --- --- | | 01 KI.EIDA.F01 B N N N | | 02 KI.EIDA.F02 B N N S | | 03 KI.EIDA.F03 R E S N | | 04 KI.EIDA.F04 R E S S | | | | | | | | | | | | | | | | | | | | FMT:R,B - ALF:A,E,N - TRA:S,N - COM:S,N | ------------------------------------------------------------------------------ ``` Up to 99 file lines are displayed. To navigate between the different possible screens, press PF7 and PF8 as usual. To remove a file line, enter D at the beginning of it or delete it completely. To add one, type the data on a free line; if the file characteristics are not provided, those appearing in the application profile will be used by default, assuming format “R”. To modify, type the data on an already filled line. Pressing ENTER performs the update and returns to the 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 entered automatically. * **PHYSICAL NAME OF THE EMISSION APPLICATION FILE**: MVS files can be included, in which case the rules regarding DSNAME must be met, as well as files belonging to HFS, which are those residing in the Unix partition of z/OS (USS). * **FMT**: Emission file format (R/B). The formats can be Record type (fixed, variable, and expanded variable) and Binary type for MVS files. For HFS files, B will preferably be used, although R can be used for those with delimiters ('15': line break in USS). * **ALF**: Original alphabet of the data. It can be ASCII (A), EBCDIC (E), and None (N). * **TRA**: Translate on output. It can take the values TRANSLATE (S), DO NOT TRANSLATE (N). Translation cannot be set for binary files (B) on HFS. * **COM**: File compression. It can be COMPRESSED (S) and NOT COMPRESSED (N). The user has 2 ways to operate regarding emission application files: * Specify a profile with emission files. * Do not specify emission files in the profile. In the pre-output step, include a DD ZTBGFCAR, a fixed file of length 80, whose content is the emission application files and their characteristics. The format of this file, which can have up to 999,999 records (emission application files), is as follows:
LevelNameLengthTypeDescription
1File format1Alph.

Application file format:

‘R’: Record, ‘M’: Modified

1Source data alphabet1Alph.

Original alphabet of the data:

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

1Translate on output1Alph.

Alphabet in which the data is output:

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

1Compression1Alph.

Compression:

‘F’ Compressed, ‘N’ No compression

1Filler1Alph.Separation
1Physical name74Alph.Physical name of the application file
The values that can be entered have the same requirements as if they were entered through the administrator. If the format, alphabet, translate, and compression fields are not specified, they will be taken from the presentation session profile. The DSNAME of ZTBGFCAR does not have to be the same for all sessions, even though the procedure is. For this purpose, it is suggested that the name of this file be obtained based on parameters known to the procedure. ## **Query** A screen similar to the previous one is displayed with all fields protected, and if the number of defined files makes it necessary to use several screens, you can navigate through them using PF7 and PF8. PF3 returns to the corresponding menu. --- # 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-ims-en/operacion/primerospasos/administrador-de-onesait-editran/ficheros-de-aplicacion-de-emision.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.