> 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/utilidades-ims/listado-de-los-ficheros-de-perfiles.md). # List of profile files The need for applications to know the names of the files that are to be issued, stored in the Editran profiles file, has led to these names being extracted to a flat file with the characteristics they have with respect to sending by Editran. The program can be run as a JCL or as a step in the load processes. The session is passed via PARM. The result of the program is a sequential file of 80 bytes with one record for each output file contained in profiles. The record format is the same as that of the ZTBGFCAR load files file: FILE NAME –F-L-T-C Where FILE NAME has 44 bytes F is the record format and has values R for record format and M for binary format (modified), L is the original language of the data, with values A for ASCII, E for EBCDIC, and B for binary, T is the translation, with values A or E to translate to ASCII or EBCDIC and N for no translation, and C indicates compression, with F for compress by file and N for no compression. The program is a batch Cobol program that internally executes a BMP to access the ZTBGDPED profiles database. The ZTBGJLFP JCL runs the ZTBGBLFP module in isolation. A 24-byte presentation session is passed via PARM. ```cobol //KI88DC4F JOB (EGDC,KIT,,99),'ZTBGJLFP',MSGCLASS=H,CLASS=A, // NOTIFY=&SYSUID //*-------------------------------------------------------------------- //* JCL TO EXTRACT LIST OF PROFILE OUTPUT FILES /G //*-------------------------------------------------------------------- //* DATA: //* PRESENTATION SESSION 24 BYTES //* LOCAL --------------------------------------------> 9 BYTES //* REMOTE -------------------------------------------> 9 BYTES //* APPLICATION ---------------------------------------> 6 BYTES //*-------------------------------------------------------------------- //ZTBGLFP EXEC PGM=ZTBGBLFP, // PARM='000099980000099940PRUEBA/CBLQDA(ON)' //STEPLIB DD DSN=IMSP.SDFSRESL,DISP=SHR // DD DSN=KI.EGDI.LOAD,DISP=SHR //ZTBGF032 DD DSN=KI.EGDI.ZTBG.ZTBGF032,DISP=SHR //ZTBGFLFP DD SYSOUT=* //ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105) //SYSOUT DD SYSOUT=* //CEEDUMP DD SYSOUT=* // ``` If it is to be used within the load processes, an additional step will be added invoking the ZTBGBLFP program in the same way. In a standard procedure, the variables L1, L2, R1, R2 and PR (presentation) can be used to form the session. The ZTBGP1 load procedure, already modified, would look as follows. ```cobol // PROC ORIGEN=,FUNCION=,L0=, // L1=,L2=,R1=,R2=,AP=,PR=,LF= //*--------------------------------------------------------------- //ZTBGLFP EXEC PGM=ZTBGBLFP, // PARM='&L1&L2&R1&R2&PR/CBLQDA(ON)' //STEPLIB DD DSN=IMS710P.SDFSRESL,DISP=SHR // DD DSN=KI.EGDI.LOAD,DISP=SHR //ZTBGF032 DD DSN=KI.EGDI.ZTBG.ZTBGF032,DISP=SHR //*FILE LIST //ZTBGFLFP DD SYSOUT=* //ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105) //SYSOUT DD SYSOUT=* //CEEDUMP DD SYSOUT=* //* //A1P EXEC PGM=ZTBGB110,REGION=0M,TIME=1440, // PARM='&ORIGEN&FUNCION&L1&L2&R1&R2&PR&AP&LF/CBLQDA(ON)' //STEPLIB DD DSN=KI.EGDI.LOAD,DISP=SHR // DD DSN=CEE.SCEERUN,DISP=SHR // DD DSN=IMS710P.SDFSRESL,DISP=SHR ``` It is necessary to include the DD statements from the load step to access IMS and to return errors. It is not necessary to generate any PSB. The output file is ZTBGFLFP, which accepts an FB record of 80. The following run shows the KI.EIDA.F80 file, which is sent in binary and without compression. ``` SDSF OUTPUT DISPLAY KIIMST01 JOB06699 DSID 4 LINE 153 COLUMNS 02- 81 COMMAND INPUT ===> SCROLL ===> CSR IEF374I STEP/ZTBEBA00/STOP 2006271.0935 CPU 0MIN 00.00SEC SRB 0MIN 00.00S IEF375I JOB/KIIMST01/START 2006271.0919 IEF376I JOB/KIIMST01/STOP 2006271.0935 CPU 1MIN 51.61SEC SRB 0MIN 00.16S KI.EIDA.F80 M B N N +***** ZMA001H: DYNAMIC ALLOCATION -NORMAL- (RC=00,RS= 0000,I= 0000) DDN=NUMORD01 DSN=KI.EIDA.F80 DISP=(SHR, , ) +***** 09:19:57 ELAPSED TIME= 0.16 SEC. ``` --- # 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/utilidades-ims/listado-de-los-ficheros-de-perfiles.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.