> 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/migration-to-v5.3-phase-1/migration-from-editran-v5.3.0.md). # Migration from Editran v5.3.0 ## ZTBMJA53 The following JCL ZTBMJA53 is provided, which has the following content: ```cobol //KI63A23A JOB (EGDC,KIT,,99),'ZTBMJA53',MSGCLASS=H,CLASS=A, // MSGLEVEL=1,NOTIFY=&SYSUID //*-------------------------------------------------------------------- //* VERSION MIGRATION FROM 5.3.0 TO VERSION 5.3.1 //******************************************************************* //BORRADO EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE (KI.EIDC.ZTBG.ZTBGFPER.V531) PURGE //* //DEFPERF EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER - (NAME(KI.EIDC.ZTBG.ZTBGFPER.V531) - VOL(DES805) - LOG(NONE) - NOREUSE - REC (4000 50) - FREESPACE(25 25) - RECORDSIZE(3000 3000) - SHAREOPTIONS(2 3) - KEYS(27 0) - INDEXED ) - DATA - (NAME(KI.EIDC.ZTBG.ZTBGFPER.V531.DATA)) - INDEX - (NAME(KI.EIDC.ZTBG.ZTBGFPER.V531.INDEX)) //* //REPRO1 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=H //ENTRADA DD DSN=KI.EIDC.ZTBG.ZTBGFPER.V530,DISP=SHR //SALIDA DD DSN=KI.EIDC.ZTBG.ZTBGFPER.V531,DISP=SHR //SYSIN DD * REPRO INFILE(ENTRADA) OUTFILE(SALIDA) //******************************************************************* //BORRADO EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE (KI.EGDC.ZTBP.ZTBPFPE.V531) PURGE //* //DEFPERF EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER - (NAME(KI.EGDC.ZTBP.ZTBPFPE.V531) - VOL(DES805) - LOG(NONE) - NOREUSE - REC (3000 50) - FREESPACE(25 25) - RECORDSIZE(2500 2500) - SHAREOPTIONS(2 3) - KEYS(34 0) - INDEXED ) - DATA - (NAME(KI.EGDC.ZTBP.ZTBPFPE.V531.DATA)) - INDEX - (NAME(KI.EGDC.ZTBP.ZTBPFPE.V531.INDEX)) //* //REPRO2 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=H //ENTRADA DD DSN=KI.EGDC.ZTBP.ZTBPFPE.V530,DISP=SHR //SALIDA DD DSN=KI.EGDC.ZTBP.ZTBPFPE.V531,DISP=SHR //SYSIN DD * REPRO INFILE(ENTRADA) OUTFILE(SALIDA) //*--------------------------------------------------------------------- //* A C-CONSULTATION OR M-MODIFICATION OF //* A SPECIFIC SESSION CAN BE PERFORMED //* THE LOCAL-REMOTE SESSIONS //* THE LOCAL SESSIONS //* ALL SESSIONS //* THROUGH SYSIN //* //* SYSIN FORMAT //* 1.-LLLLLLLLLRRRRRRRRRAAAAAA //* 000099980000099940PRUEBA CONSULTATION/MODIFICATION OF A SESSION //* 000000000000099940PRUEBA CONSULTATION/MODIFICATION BY REMOTE/APPLI //* 000000000000000000PRUEBA CONSULTATION/MODIFICATION BY APPLICATION //* 000099980000099940000000 CONSULTATION/MODIFICATION BY LOCAL-REMOTE //* 000000000000099940000000 CONSULTATION/MODIFICATION BY REMOTE //* 000099980000000000000000 CONSULTATION/MODIFICATION BY LOCAL //* 000000000000000000000000 CONSULTATION/MODIFICATION ALL SESSIONS //* CONSULTATION/MODIFICATION ALL SESSIONS //* 2.-X //* C - CONSULTATION OF THE SESSIONS //* M - MODIFICATION OF THE SESSIONS //*--------------------------------------------------------------------- //PASO1 EXEC PGM=ZTBGBA53 //STEPLIB DD DSN=KI.EIDC.ZTBG.LOAD,DISP=SHR // DD DSN=KI.EGDC.ZTBP.LOAD31,DISP=SHR //ZTBGFPER DD DSN=KI.EIDC.ZTBG.ZTBGFPER.V531,DISP=SHR //ZTBPFPE DD DSN=KI.EGDC.ZTBP.ZTBPFPE.V531,DISP=SHR //EDILIST DD SYSOUT=* //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSDBOUT DD SYSOUT=* //ABENDAID DD SYSOUT=* //SYSCOUNT DD DUMMY //SYSUDUMP DD SYSOUT=* //SYSABOUT DD SYSOUT=* //SYSIN DD * 000000000000000000000000 M /* ``` By running the ZTBGBA53 program, a query or a modification can be performed on the session(s) we have defined. * The internal session value becomes LOCAL CODE + REMOTE CODE + APPLICATION * Editran/P sessions that are not associated with any Editran/G session are deleted. ## SYSIN The SYSIN format consists of two parameters: ### Presentation session With the following format LLLLLLLLLRRRRRRRRRAAAAAA. Here we will indicate the presentation session(s) to query or modify. This query/modification affects the presentation session and all associated transmission sessions (from now on we will refer to this set as the session). How to specify the fields LLLLLLLLLRRRRRRRRRAAAAAA. ### **Specify all fields.** The query/modification is performed on a specific session. Example: ``` 000099980000099940PRUEBA ``` It checks the following parameters for session 000099980000099940PRUEBA: ### **Specify the fields LLLLLLLLLRRRRRRRRR** The query/modification is performed by local code and remote code. Example: ``` 000099980000099940000000 ``` It checks the following parameters for all sessions with local 000099980 and remote 000099940. ### **Specify the fields LLLLLLLLLAAAAAA** The query/modification is performed by local code and application, for any remote code. Example: ``` 000099980000000000PRUEBA ``` the remote can also be left blank like this: ``` 000099980 PRUEBA ``` It checks the following parameters for all sessions with local code 000099980 and application PRUEBA. ### **Specify only the remote code RRRRRRRRR** The query/modification is performed by remote code and application, for any local code. Example: ``` 000099980000000000000000 ``` the remote code and the application can also be left blank like this: ``` 000099980 ``` It checks the following parameters for all sessions with local 000099980: ### **Specify only the local code LLLLLLLLL** The query/modification is performed by local code. Example: ``` 000099980000000000000000 ``` the remote code and the application can also be left blank like this: ``` 000099980 ``` It checks the following parameters for all sessions with local 000099980: ### **Specify only the remote code RRRRRRRRR** The query/modification is performed by remote code. Example: ``` 000000000000099940000000 ``` the local code and the application can also be left blank like this: ``` 000099940 ``` It checks the following parameters for all sessions with remote 000099940: ### **Specify only the application AAAAAA** The query/modification is performed by application. Example: ``` 000000000000000000PRUEBA ``` the local code and the remote code can also be left blank like this: ``` 000099940 ``` It checks the following parameters for all sessions with remote 000099940: ### Query/Modification. With a 'C' we indicate that it is a query and with an 'M' we indicate that it is a modification Example 1 ```cobol //SYSIN DD * 000099980000099940PRUEBA C ``` Query of presentation session 000099980000099940PRUEBA and all associated transmission sessions. Example 2 ```cobol //SYSIN DD * 000099980000099940PRUEBA M ``` Modification of presentation session 000099980000099940PRUEBA and all associated transmission sessions. ## ZTBGFLIS The output is the same for query or modification. This output has the following header: ``` 1 INDRA MIGRATION OF EDITRAN PROFILES FROM 5.3.0 TO 5.3.1 PAGE 1 EDI V5.3 =============================================== DATE 10/07/2026 SESSION IMPACT ON PROFILES ``` First come the presentation sessions, with their corresponding transmission sessions that have to be modified or are modified. Example: ``` INDRA MIGRATION OF EDITRAN PROFILES FROM 5.3.0 TO 5.3.1 PAGE 1 EDI V5.3 ============================================== DATE 10/07/2026 SESSION IMPACT ON PROFILES ------------------------ ------------------------------------------------------------------------------ A00099940000099940SWIFTC SESSION/P OF THE PRESENTATION SESSION A00099940000099940PRBSWC INT.SESSION:WINDOWS-PRUEBAS-SWIFT-A0C CHANGES TO:A00099940000099940SWIFTC A00099940000099940SWIFTA SESSION/P OF THE PRESENTATION SESSION A00099940000099940PRUEBA INT.SESSION:WINDOWS-PRUEBAS-SWIFT-B CHANGES TO:A00099940000099940SWIFTA ``` ### SYSOUT This output reports transmission sessions that do not exist for a specific presentation session. Example: ``` ZTBGBA53 PRESENTATION SESSION A0009994A000099990PRUJCB DELETED BECAUSE THE TRANSMISSION SESSION DOES NOT EXIST ZTBGBA53 PRESENTATION SESSION A00099940000099940CICLIN DELETED BECAUSE THE TRANSMISSION SESSION DOES NOT EXIST ``` --- # 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/migration-to-v5.3-phase-1/migration-from-editran-v5.3.0.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.