> 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/control-de-actividad-de-onesait-editran/consulta-de-ficheros-de-control.md). # Control file query This screen is accessed with option 3 of the Activity Control menu or with option 2.3 of the general menu. ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 11:34:59 FILE QUERY 5.3 | ------------------------------------------------------------------------------ | | | | | | | | | 1 TRANSMISSION/RECEPTION RECORD QUERY | | 2 TRACE QUERY | | 3 EDITRAN/P LOG QUERY | | 4 GENERIC SESSION QUERY | | 5 DIAGNOSTIC AIDS | | 6 OPERATING LICENSE QUERY | | 7 EDITRAN/G LOG QUERY | | | | | | | | OPTION ---> | | | | | | | | | ------------------------------------------------------------------------------ ``` ℹ️Enter the desired option. PF3 returns to the previous menu ## **1-Transmission/reception record query** This screen is accessed with option 1 of the File Query menu and with option 2.3.1 of the general menu. ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 11:47:51 TRANSMISSION RECORD QUERY 5.3 | ------------------------------------------------------------------------------ | | | | | | | LOCAL - REMOTE (L/R) : L | | | | FILE TYPE (E/R) : E | | | | LOCAL CODE : 0 0009998 0 | | | | REMOTE CODE : 0 0009994 0 | | | | APPLICATION : PR* | | | | | | | | | | | | | | | ------------------------------------------------------------------------------ ``` The first 2 fields must be entered obligatorily with “L” for Local, “R” for Remote, “E” for Emission and “R” for reception. Regarding the other 3 fields that make up the session identifier, the same rules already mentioned for Session maintenance in the Administrator and for session query in the Operator apply, in relation to specific or generic query. In a specific query, the process is performed directly. In a generic query, a screen like the following example is displayed with all the sessions that match the selection criteria: ``` 21/06/26 TRANSMISSION RECORD QUERY EDITRAN 11:50:10 5.3 S L. CODE R. CODE APPLICATION PROCESS RESULT - --------- --------- ---------- ---------------------------------------------- 000099980000099940 PRGIGA 000099980000099940 PRPSD2 000099980000099940 PRTCP0 000099980000099940 PRTCP1 000099980000099940 PRTCP2 000099980000099940 PRTCP3 000099980000099940 PRTCP4 000099980000099940 PRTCP5 000099980000099940 PRTCP6 000099980000099940 PRTCP7 000099980000099940 PRTCP8 000099980000099940 PRTCP9 000099980000099940 PRTC11 000099980000099940 PRTC12 000099980000099940 PRTC13 000099980000099940 PRTC14 000099980000099940 PRUEBA ``` ℹ️By entering “S” in the selection field on the left in the line corresponding to the desired session, the same result is obtained as in the specific query. In any case, if the LOCAL query is selected, a screen is displayed with the control record data of the local transmission or reception buffer file for the specified Session. ``` ------------------------------------------------------------------------------ | 21/06/26 TRANSMISSION RECORD QUERY EDITRAN | | 11:51:33 LOCAL 5.3 | ------------------------------------------------------------------------------ | | | LOCAL CODE: 000099980 REMOTE CODE: 000099940 APPLICATION: PRUEBA | | | | FILE TYPE : EMISSION | | CREATION DATE ...: 15-06-2026 CREATION TIME .......: 15:21:01 | | LAST INSERT DATE .: 15-06-2026 LAST INSERT TIME .: 15:21:01 | | | | TRANSFER START DATE.: TRANSFER START TIME.....: | | LAST CONFIRM DATE.: LAST CONFIRM TIME....: | | | | TOTAL NO. OF RECORDS....: 840 | | CONFIRMED RECORDS .: 0 SENT RECORDS ....: 0 | | BUFFER STATUS ....: PREPARED | | RESULT CODE .: | | FULL TRANS. ..: NOT ISSUED IN FULL | | LAST SENT SYNC ..: 000000000000 LAST CONFIRM SYNC .: 000000000000 | | LAST INT. SYNC ..: 000000000000 INT. SESSION NO. : 1 | | | | | ------------------------------------------------------------------------------ ``` ## **2-Trace query** This screen is accessed with option 2 of the File Query menu and with option 2.3.2 of the general menu. ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 11:13:36 TRACE QUERY 5.3 | ------------------------------------------------------------------------------ | | | | | | | | | CONTROL MSGS ONLY: | | | | LOCAL CODE : | | | | REMOTE CODE : | | | | APPLICATION : | | | | DATE (DD/MM/YY): / / | | | | TIME (HH:MM:SS): : : | | | | | | | | | ------------------------------------------------------------------------------ ``` In the trace database, all messages processed by Editran are recorded, both incoming and outgoing, corresponding to the Sessions whose profile specifies Trace=S, or only the control messages if Trace=C is specified. Likewise, incoming calls whose Session does not exist are recorded. In the query, only control messages (all except data and synchronization messages) will be shown by entering ‘S’ in the first field of this screen. Due to its scope regarding the Sessions affected, the trace query can be divided into: * General. Obtained without typing any of the Codes. Messages from all Sessions are shown. * Specific. Obtained by entering the Local, Remote and Application Codes that make up the Session. Messages from that Session are shown. * Partial. Obtained by not entering or by putting “\*” in any of the three Codes, or by entering the beginning or the end of a Code with a “\*” after or before, respectively, the partial Code, or any combination that does not turn the query into either of the two above. All messages that meet all the selection criteria are shown. Due to the time at which the messages have been processed: * If neither the Date nor the time is entered, the latest messages that meet the Code selection criteria are shown. * If the Date is entered, but not the Time, the first messages of that Date are shown. * If the Date and the Time are entered, the messages from that Date starting at that Time are shown. * If only the Time is entered, the messages from today starting at that time are shown. * The year of the date can be entered with 4 or 2 digits. In the latter case, if it is 96 to 99 it is assumed to be 1996 to 1999; if it is less than 96 it is considered to be from 2000 to 2095. ℹ️Page forward with PF8 and backward with PF7 so that contiguous messages matching the selection criteria are displayed. The following image shows an example of a generic query. ``` 21/06/26 TRACE QUERY EDITRAN 13:26:17 5.3 s SESSION DATE TIME S CLA C NSM COMMENT -------------------------- ----- -------- - --- - ------ ---------------------- 000099980000099940PRTCP3 18-06 11:52:52 E SCP 0 0 RECEPTION REQUEST 000099980000099940PRTCP3 18-06 11:52:52 S SCR 0 0 START OF RECEPTION RESPONSE 000099980000099940PRTCP3 18-06 11:53:10 E SEP 0 261 END OF REMOTE TRANSMISSION 000099980000099940PRTCP3 18-06 11:53:10 S SER 9 261 CORRECT FINAL RECEPTION. 000099980000099940PRTCP3 18-06 11:53:10 S A4P REQUESTS POST-RECEPTION. 000099980000099940PRTCP3 18-06 11:53:11 E SAB CORRECT TRANSMISSION AND END. 000099980000099940PRTCP3 18-06 11:53:11 S E11 ZTCP52 TCP RELEASE REQUEST 000099980000099940PRTCP3 18-06 11:53:11 E E11 ZTCP52 TCP RELEASE REQUEST 000099980000099940PRTCP3 18-06 11:53:11 S X11 * ZTCP52 TCP RELEASE INDICATION 000099980000099940PRTCP3 18-06 11:53:11 S CLO 0 CLOSES TCP CONNECTION 000099980000099940PRTCP3 18-06 11:53:11 E X11 * ZTCP52 TCP RELEASE INDICATION 000099980000099940PRTCP3 18-06 11:53:20 E A4R END OF POST-RECEPTION.00 000099980000099940PRTCP3 18-06 11:58:58 E AAR RECEPTION BUFFER PREPARED00 000099980000099940PRUEBA 18-06 12:51:33 E EPE APPLICATION FILE QUERY. 000099980000099940PRTCP3 18-06 13:09:00 E EPE APPLICATION FILE QUERY. 000099980000099940PRUEBA 18-06 13:09:06 E EPE APPLICATION FILE QUERY. ``` On this screen we can select a specific message by typing an ‘s’ to its left, to view it in full. Once the message is displayed, the only option is to return to the query being performed by pressing \, as we can see on the next screen. ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 13:27:48 TRACE QUERY 5.3 | ------------------------------------------------------------------------------ | | | LOCAL CODE: 000099980 REMOTE CODE: 000099940 APPLICATION: PRTCP3 | | | | 18/06/2026 11:58:58.41 000099980000099940PRTCP3 E AAR | | AAR000099980000099940PRTCP3000 | | | | | | | | | | PRESS TO EXIT | | | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------------ ``` ## **3-EDITRAN/P log query** This screen is accessed with option 3 of the File Query menu and with option 2.3.3 of the general menu. ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 13:30:34 EDITRAN/P LOG QUERY 5.3 | ------------------------------------------------------------------------------ | | | | | | | LOCAL CODE : | | | | REMOTE CODE : | | | | APPLICATION : | | | | DATE (DD/MM/YY): / / | | | | TIME (HH:MM:SS): : : | | | | | | | | | | | | | | | ------------------------------------------------------------------------------ ``` All informational messages to the operator are recorded in the log database. These messages correspond to the most significant events of the connections and transmissions, as well as possible incidents that occurred. ## **4-Generic session query** This screen is accessed with option 4 of the File Query menu and with option 2.3.4 of the general menu. ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 15:36:56 GENERIC SESSION QUERY 5.3 | ------------------------------------------------------------------------------ | | | | | | | | | | | | | LOCAL CODE : 0 0009998 0 | | | | REMOTE CODE : 0 0009994 0 | | | | APPLICATION : | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------------ ``` The selection criteria, with regard to the Local, Remote and Application Codes, are those already explained for the trace and log queries. Once the selection is made, a screen like the following appears: ``` 21/06/26 15:38:59 GENERIC SESSION QUERY EDITRAN 5.3 ------------------------------------------------------------------------------ CODE CODE LOCAL REMOTE APPL. REMOTE DESC. APPLICATION DESC. CONNECTION DATA ------------------------ ---------------- ------------------ ------------------ 000099980000099940PRPSD2 NAME 9994 REMO IP:172.022.242.193 000099980000099940PRTCP0 NAME 9994 REMO TCP/IP TEST IP:172.022.242.193 000099980000099940PRTCP1 NAME 9994 REMO TCP/IP TEST IP:172.022.242.193 000099980000099940PRTCP2 NAME 9994 REMO TCP/IP TEST PX:172.022.242.193 000099980000099940PRTCP3 NAME 9994 REMO TCP/IP TEST PX:010.055.000.017 000099980000099940PRTCP4 NAME 9994 REMO TCP/IP TEST PX:172.022.242.193 000099980000099940PRTCP5 NAME 9994 REMO TCP/IP TEST IP:172.022.242.193 000099980000099940PRTCP6 NAME 9994 REMO TCP/IP TEST IP:172.022.242.193 000099980000099940PRTCP7 NAME 9994 REMO TCP/IP TEST PX:010.055.000.017 000099980000099940PRTCP8 NAME 9994 REMO TCP/IP TEST PX:172.022.242.193 000099980000099940PRTCP9 NAME 9994 REMO TCP/IP TEST PX:010.055.000.017 000099980000099940PRTC11 NAME 9994 REMO TEST 3 TRANSMISSIO PX:172.022.242.193 000099980000099940PRTC12 NAME 9994 REMO TEST 3 TRANSMISSIO PX:172.022.242.193 000099980000099940PRTC13 NAME 9994 REMO TEST 3 TRANSMISSIO PX:172.022.242.193 000099980000099940PRTC14 NAME 9994 REMO TCP/IP TEST PX:010.055.000.017 000099980000099940PRUEBA NAME 9994 REMO DATA IN APPLICATIO PX:172.022.242.193 ``` ℹ️ Page with PF8 to move forward and PF7 to move back. ## **5-Diagnostic help** This screen is accessed with option 5 of the File Query menu and with option 2.3.5 of the general menu. Here we find a summary of the error codes and types of messages generated by the application. ``` ------------------------------------------------------------------------------ | 21/06/25 ACTIVITY CONTROL EDITRAN | | 16:20:30 DIAGNOSTIC AIDS 5.3 | ------------------------------------------------------------------------------ | | | | | | | | | 1 DIAGNOSTICS AND REFERENCES A7I | | | | 2 EDITRAN NETWORK MESSAGES QUERY | | | | 3 OTHER EDITRAN MESSAGES QUERY | | | | 4 SAB REASONS | | | | 5 EDITRAN CRYPTOGRAPHY SYSTEM | | | | | | OPTION ---> | | | | | | | ------------------------------------------------------------------------------ ``` In the different options we can consult * codes and explanation of the interruption processes, * TCP/IP calls managed by Editran, * internal and external message keys managed by Editran, * causes of transmission abortion and * cryptography errors. ## **6-Operating license query** This screen is accessed with option 6 of the File Query menu and with option 2.3.6 of the general menu. n menus are displayed, corresponding to the *n* contracted environments-subenvironments. Within each contracted code, the following are described: * Editran identification of the contracted code. * Contracted version of said code. * Expiration date of said code. * Result of the license check. Different literals appear with a result code and reason, giving guidance on the problem that a license may have, سواء in terms of the entity code or some of the contracted products for it. If it indicates errors, consult INDRA. * License type, indicating whether the code is in test or production. * Indication of whether this is a general environment license or a subenvironment license. * Products developed by INDRA. Within each of the products, various fields also appear; if a field does not appear, it means it is not contracted: * Name of the product developed by INDRA. * Type of contract of the product for the indicated entity code, indicating whether it is in test or production. * Result of the product expiration date for the indicated entity code (if it is different from zero, check the license verification result literal and, if necessary, consult INDRA). ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 17:29:24 OPERATING LICENSE QUERY 5.3 | ------------------------------------------------------------------------------ | ENTITY CODE : A0009998S SUBENVIRONMENT IMSP VERSION: 0530 | | EXPIRATION DATE: 31-01-2099 ENTITY CODE AND PRODUCTS CORRECT. 0000-0000 | | LICENSE TYPE : E (P:TEST, E:PRODUCTION) MAINTENANCE: | | SUBENVIRONMENT LICENSE | | PRODUCT EXPIRATION TYPE RDO PRODUCT EXPIRATION TYPE RDO | | --------------- ---------- ---- --- --------------- ---------- ---- --- | | 31-01-2099 X 000 31-01-2099 X 000 | | TCP 31-01-2099 X 000 API-DES 31-01-2099 X 000 | | API-RSA 31-01-2099 E 000 31-01-2099 E 000 | | API-TRIPLE-DES 31-01-2099 E 000 LZW 31-01-2099 E 000 | | EDITRAN/E EDITRAN/TR 31-01-2099 E 000 | | 31-01-2099 E 000 EDITRAN/FF PKCS 31-01-2099 E 000 | | EDITRAN/FF XA-B | | EDITRAN/PROXY EDITR/XML SEPA | | API-AES | | | | EDITRAN LICENSE FOR CPUID : **-*-*-9D78-3932 | | CALCULATED CPUID : 00-0-2-9D78-3932 | | ENTITY CODE AND PRODUCTS CORRECT. TYPE X PARTIAL LIC. | ------------------------------------------------------------------------------ ``` ## **7-EDITRAN/G log query** This screen is accessed with option 7 of the File Query menu and with option 2.3.7 of the general menu. ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 14:06:41 EDITRAN/G LOG QUERY 5.3 | ------------------------------------------------------------------------------ | | | | | DIRECTION (E/S/I) : | | | | ORIGIN (O/A/E/I/U) : | | | | LOCAL CODE : | | | | REMOTE CODE : | | | | APPLICATION : | | | | DATE (DD/MM/YY) : / / | | | | TIME (HH:MM:SS) : : : | | | | | | | | | ------------------------------------------------------------------------------ ``` These data are used in the selection criteria for the Log query. If any of the first 5 are entered, the search will be performed on that one. If a date is entered, the messages generated from it are displayed; in this case, a start time for the query can also be provided. These data are: * **DIRECTION (E/S/I)**: * E: Incoming messages. * S: Outgoing messages. * I: Informational messages or incidents that occurred. * Blank: All. * **ORIGIN (O/A/E/I/U)**: * O: Editran presentation module operator * A: application JCL. * E: Editran transmission module. * I: The Editra presentation module. * U: Messages included in the Log by a user application, through the ZTBGB006 Interface. * Blank: All. * **LOCAL CODE**: A specific one or blank for all. * **REMOTE CODE**: A specific one or blank for all. * **APPLICATION**: Presentation application. A specific one, blank for all, and ‘\*’ at the beginning or end. * **DATE (DD/MM/YY)**: From a specific date or zeros from the beginning of the Log. * **TIME (HH:MM:SS)**: From a specific time within a date or zeros from the beginning of messages of a date. If no date or time is entered, the latest recorded messages are shown. ``` 21/06/26 14:10:15 EDITRAN/G LOG QUERY EDITRAN 5.3 TYPE CODE PRESENTATION SESSION TR. APL. DATE TIME JOB-ID E O ZTG0020 000099980 000099940 PRTCP2 21/06/2026 10:04:46 KICICD23 1246 PRESENTATION EMISSION REQUEST E O ZTG0020 000099980 000099940 PRTCP1 21/06/2026 10:04:46 KICICP13 1245 PRESENTATION EMISSION REQUEST E O ZTG0020 000099980 000099940 PRTCP3 21/06/2026 10:04:46 KICICD33 1248 PRESENTATION EMISSION REQUEST E O ZTG0020 000099980 000099940 PRTCP5 21/06/2026 10:04:49 KICICP53 1252 PRESENTATION EMISSION REQUEST E O ZTG0020 000099980 000099940 PRTCP4 21/06/2026 10:04:49 KICICP43 1251 PRESENTATION EMISSION REQUEST S ZTG0046 000099980 000099940 PRTCP2 21/06/2026 10:04:49 KICICD23 1246 APPLICATION FILE LOAD COMPLETED NF000001 S ZTG0046 000099980 000099940 PRTCP2 21/06/2026 10:04:50 KICICD23 1246 APPLICATION FILE LOAD COMPLETED NF000002 I I ZTG0232 000099980 000099940 PRTCP1 21/06/2026 10:04:50 KICICP13 1245 CORRECT FILE ADAPTATION AND COMPLETION I I ZTG0142 000099980 000099940 PRTCP3 21/06/2026 10:04:50 KICICD33 1248 CORRECT FILE COMPRESSION AND COMPLETION I I ZTG0142 000099980 000099940 PRTCP1 21/06/2026 10:04:51 KICICP13 1245 CORRECT FILE COMPRESSION AND COMPLETION ``` ℹ️Once inside the Log query, you can navigate forward or backward using PF8 and PF7 respectively. PF3 returns to the options screen for the query. Type (direction and origin), message code, presentation session (local, remote and presentation application codes), transmission application (only if Editran is origin or destination), date and time of the message, job name, job number and message text are shown. --- # 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/control-de-actividad-de-onesait-editran/consulta-de-ficheros-de-control.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.