> 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-activity-control/file-query.md).
# File query
It is used to query the buffer, log, trace, license and help files of editran/P and editran/G.
```
-----------------------------------------------------------------------------
| 24/06/2026 EDITRAN MANAGER EDITRAN 5.3 |
| 12:51:27 FILE QUERY PHASE 01 |
-----------------------------------------------------------------------------
| |
| |
| |
| |
| 1 ---> QUERY OF SEND/RECEIVE RECORD |
| 2 ---> QUERY OF THE TRACE |
| 3 ---> QUERY OF EDITRAN/P LOG |
| 4 ---> DIAGNOSTIC HELPS |
| 5 ---> OPERATIONAL LICENSE QUERY |
| 6 ---> QUERY OF EDITRAN/G LOG |
| 7 ---> QUERY OF BUFFER ASSOCIATED WITH SESSION |
| |
| |
| |
| |
| |
| OPTION : |
| |
| |
-----------------------------------------------------------------------------
```
## Send/receive record query
It allows you to know the status of the Send or Receive Buffer Files of the different sessions.
```
-----------------------------------------------------------------------------
| 24/06/2026 FILE QUERY EDITRAN 5.3 |
| 12:51:36 SEND/RECEIVE RECORD QUERY |
-----------------------------------------------------------------------------
| |
| |
| |
| |
| LOCAL - REMOTE (L/R) : |
| |
| FILE TYPE (E/R) : |
| |
| SESSION : |
| |
| |
| |
| |
| |
| ('*' in generic request) |
| |
| |
| |
| |
-------------------------------------------------------------------------------
```
If the LOCAL query is selected, a screen is shown with the control record data of the local send or receive buffer file for the specified Session.
```
-----------------------------------------------------------------------------
| 24/06/2026 FILE QUERY EDITRAN 5.3 |
| 12:52:16 LOCAL SEND/RECEIVE RECORD QUERY |
-----------------------------------------------------------------------------
| FILE TYPE : E SESSION : A00099940000099980MINAYA |
| |
| CREATION DATE : 05/06/2026 CREATION TIME : 09:51:57 |
| LAST INSERT DATE : 05/06/2026 LAST INSERT TIME : 09:51:57 |
| |
| TRANS. START DATE: 00/00/0000 TRANS. START TIME : 00:00:00 |
| LAST CONFIRM DATE: 00/00/0000 LAST CONFIRM TIME : 00:00:00 |
| |
| TOTAL RECORDS : 000000000115 |
| CONFIRMED REGS : 000000000000 SENT RECORDS : 000000000000 |
| BUFFER STATE : PREPARED C-ONLY CAN BE USED IN EDITRAN/P |
| RESULT CODE : |
| COMPLETE TRANS. : NOT FULLY SENT |
| |
| LAST SYNC SENT : 000000000000 LAST CONFIRM SYNC : 000000000000 |
| LAST INTERCHG. SYNC: 000000000000 |
| |
| |
| |
-----------------------------------------------------------------------------
```
If the REMOTE query is selected, local editran sends the query message to the remote site, and the local site waits to receive the remote response, which is displayed at the OPERATOR TERMINAL of the Session with a screen format identical to that of the Local Query. An established connection between both sites is an essential requirement for the Remote Query, and an OPERATOR TERMINAL must have been declared for the Session.
## Trace file query
To perform a General query, no data needs to be typed in. If any of the SESSION and/or DATE and/or TIME fields are filled in, a specific query is performed for one or more Sessions only, with a specific date and time. The screen from which the Trace query is selected is as follows.
```
-----------------------------------------------------------------------------
| 24/06/2026 EDITRAN MANAGER EDITRAN 5.3 |
| 12:52:31 TRACE QUERY |
-----------------------------------------------------------------------------
| |
| |
| |
| |
| |
| |
| INTERNAL SESSION....: |
| |
| DATE (DD/MM/YYYY)...: / / |
| |
| TIME (HH:MM:SS)......: : : |
| |
| |
| |
| |
| |
| |
| |
| |
-------------------------------------------------------------------------------
```
If selected without date or time, the query begins by showing the latest recorded entries; otherwise, if the date and/or time are selected, the data will be shown starting from that date and/or time. To retrieve more records, the function keys \ are used to go back and \ to go forward. It is recommended to do a "delete-define" in VSAM for file ZTBPFTR before defining Sessions whose traffic you want to follow with the Trace (field TRACE='S'), since the detailed query by Session can be slow. Whether the query is General or Specific, it is shown on a screen like the following:
```
24/06/2026 12:52:42 TRACE QUERY EDITRAN 5.3
D-TIME SEL..: **/**/****-**:**:** SESSION:
D-TIME LESS: 2026/06/24-12:52:40 D-TIME GREATER: 2026/06/24-12:52:40
S TRANSMISSION SESSION TIME S MSG NSM/LU T COMMENT
= ============================= ====== = ==== ====== = ========================
000099940000099980000001 125240 S SFP 001937 DATA
000099940000099980000001 125240 S SFP 001938 DATA
000099940000099980000001 125240 S SFP 001939 DATA
000099940000099980000001 125240 S SFP 001940 DATA
000099940000099980000001 125240 S SFP 001941 DATA
000099940000099980000001 125240 S SFP 001942 DATA
000099940000099980000001 125240 S SFP 001943 DATA
000099940000099980000001 125240 S SFP 001944 DATA
000099940000099980000001 125240 S SFP 001945 DATA
000099940000099980000001 125240 S SFP 001946 DATA
000099940000099980000001 125240 S SFP 001947 DATA
000099940000099980000001 125240 S SFP 001948 DATA
000099940000099980000001 125240 S SFP 001949 DATA
000099940000099980000001 125240 S SFP 001950 DATA
000099940000099980000001 125240 S SBP 001950 SYNCHRONIZATION REQUEST.
000099940000099980000001 125240 S STR SEND TIME-OUT.
```
The data shown on this screen is divided into:
* **SELECTION**. Field to select a specific message and expand the record content in hexadecimal.
* **TRANSMISSION SESSION**: corresponds to the editran session that generates the message. If this field appears as zeros, it means that it is a generic message or a message whose editran session is unknown.
* **TIME**: refers to the time at which the message occurred.
* **S**: This field has two values: E (message entering the editran core) S (message leaving the editran core). Many messages are neither incoming from remote nor outgoing to remote. Normally (there is one exception), those that travel over the network are network messages and those that begin with S (see msg).
* **MSG**: is an internal message and is distinguished into two types:
* Network Message. These are communication messages that establish or release the connection. These messages depend on the communications interface available. In the case of a TCP/IP connection, TCP appears. In the case of an editran/PR connection, ETT appears.
* Editran Message. These are messages specific to the editran protocol and are very varied. Below, the most common ones are referenced:
* E00: Session establishment request.
* E11: Session release request.
* SAP: Session Start (session parameter notification).
* SAR: Session start response (session parameter notification response).
* ECP: Send request.
* ECR: Receive request.
* EDP: Send end request.
* EDR: Receive end request.
* EOP: Message for the remote operator.
* ECP8: Remote send request.
* SCP: Send start.
* SCR: Send start response.
* SBP: Synchronization request.
* SBR: Synchronization response.
* SFP: Buffer file record.
* **NSM/LU:** refers to the buffer data record number that goes out or comes in. Also to the port for TCP/IP messages.
* **T**: is an internal editran field with a specific code.
* **COMMENT**: refers to the specific comment of the incoming or outgoing message.
If any record is selected, a screen appears with the expanded content, which in turn can be viewed in hexadecimal or character mode by pressing PF2:
```
02/10/2023 FILE QUERY EDITRAN 5.3
15:03:30 TRACE QUERY
TRACE SESSION.: 000099940000099980ABEURA (000099940-000099980-ABEURA)
DATE YYMMDD.: 20230927 TIME HHMMSS....: 093840 IN/OUT.: S
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
E2E3D5F0F0F0F0F9F9F9F4F0F0F0F0F0F9F9F9F8F0C1C2C5E4D9C140404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
40404040404040404040404040404040404040404040404040404040404040404040404040
00204040400000404040F0F9F3F8F4F0404040404040
PF2: SWITCH HEXADECIMAL - CHARACTER
```
## Editran P log file query
All operator informational messages generated by editran are queried, regardless of whether they were shown on screen or not.
To query these records, the possible selection to be made is requested (Session, Date and Time), just as with the Trace. The screen is as follows.
```
-----------------------------------------------------------------------------
| 24/06/2026 EDITRAN MANAGER EDITRAN 5.3 |
| 12:53:37 TRANSMISSION LOG FILE QUERY |
-----------------------------------------------------------------------------
| |
| |
| |
| |
| |
| |
| TRANSMISSION SESSION...: |
| |
| DATE (DD/MM/YYYY)...: / / |
| |
| TIME (HH:MM:SS)......: : : |
| |
| |
| |
| |
| |
| |
| |
| |
-----------------------------------------------------------------------------
```
If selected without date or time, the query begins by showing the latest recorded entries; otherwise, if the date and/or time are selected, the data will be shown starting from that date and/or time. To retrieve more records, the function keys \ are used to go back and \ to go forward. The handling of the Log file is the same as that of the Trace file. The query is shown on the following screen.
```
24/06/2026 12:53:46 TRANSMISSION LOG QUERY EDITRAN 5.3
SESSION: D-TIME: **/**/****-**:**:**
TRANSMISSION SESSION EXTERNAL SESSION DATE TIME
================================ ========================== ========== ========
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:48:38
ZTP0055 : CONNECTION ESTABLISHED
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:48:41
ZTP0895 : SESSION ESTABLISHED
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:48:41
ZTP2320 : SEND REQUEST INITIATED BY CICSOPER
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:48:41
ZTP0040 : START OF TRANSMISSION
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:48:44
ZTP0755 : START OF SESSION. LOCAL SEND
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:53:35
ZTP0110 : SEND CORRECT AND COMPLETED
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:53:35
ZTP0850 : A BATCH HAS BEEN LAUNCHED AFTER SEND
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:53:36
ZTP0490 : TRANSMISSION RELEASE C:00 D:0F
000099940000099980000001 000099940-000099980-000001 24/06/2026 12:53:43
ZTP0735 : SUBSEQUENT SEND COMPLETED CORRECTLY
EXIT, BACK, FORWARD
```
## Diagnostic helps
A help menu is shown with explanations of how the product works, so that they can be useful to the operator:
```
-----------------------------------------------------------------------------
| 24/06/2026 FILE QUERY EDITRAN 5.3 |
| 12:57:45 DIAGNOSTIC HELPS |
-----------------------------------------------------------------------------
| 1 ---> CAUSES AND RELEASE DIAGNOSTICS |
| |
| 2 ---> DIAGNOSTICS AND A7I REFERENCES |
| |
| 3 ---> QUERY EDITRAN TCP/IP MESSAGES |
| |
| 4 ---> QUERY OTHER EDITRAN MESSAGES |
| |
| 5 ---> SAB REASONS |
| |
| 6 ---> TCP/IP ERROR CAUSES AND CODES |
| |
| 7 ---> EDITRAN CRYPTOGRAPHY SYSTEM |
| |
| 8 ---> EDITRAN TRANSLATION TABLES |
| |
| OPTION : |
| |
| |
-----------------------------------------------------------------------------
```
## Operational license query
n menus are shown, corresponding to the n contracted environments-subenvironments. Within each contracted code, the following are described:
1. editran identification of the contracted code.
2. Contracted version of that code.
3. Expiry date of that code.
4. Result of the license check. Different literals appear with a result code and reason, which provide guidance on the type of problem a specific license may have, سواء in terms of the entity code or in terms of any of the contracted products for it. If this literal indicates errors, consult INDRA.
5. License type, indicating whether the code is in test or in production.
6. Indication of whether it is a general-environment license or a subenvironment.
7. Products developed by INDRA. Within each of the products, different fields appear in turn:
> * Name of the product developed by INDRA.
> * Expiry date of the product for the indicated entity code (if it does not appear, it means it is not contracted).
> * Type of contract for the product for the indicated entity code, indicating whether it is in test (P), in test but only for some sessions (R), in production (E), in production but only for some sessions (X).
> * Result of the product expiry date for the indicated entity code (if it does not appear, it means it is not contracted) (if it is different from zeros, check the literal of the license check result and, if applicable, consult INDRA).
```
-----------------------------------------------------------------------------
| 24/06/2026 FILE QUERY EDITRAN 5.3 |
| 12:58:24 OPERATIONAL LICENSE QUERY |
-----------------------------------------------------------------------------
| ENTITY CODE : A0009994A SUBENV CICSD VERSION.: 0530 |
| EXPIRY DATE : 31-12-2099 ENTITY CODE AND PRODUCTS CORRECT. 0000-0000 |
| LICENSE TYPE.: * (P:TEST, E:PRODUCTION) MAINTENANCE.: 4 |
| SUBENV LICENSE |
| PRODUCT EXPIRY TYPE RSL PRODUCT EXPIRY TYPE RSL |
| --------------- ---------- ---- --- --------------- ---------- ---- --- |
| 24-06-2026 000 24-06-2026 000 |
| TCP 24-06-2026 000 API-DES 24-06-2026 000 |
| API-RSA 24-06-2026 000 24-06-2026 000 |
| API-TRIPLE-DES 24-06-2026 000 LZW 24-06-2026 000 |
| EDITRAN/E 24-06-2026 000 EDITRAN/TR 24-06-2026 000 |
| 24-06-2026 000 EDITRAN/FF PKCS 24-06-2026 000 |
| 24-06-2026 000 EDITRAN/FF XA-B 24-06-2026 000 |
| EDITRAN/PROXY 24-06-2026 000 EDITR/XML SEPA 24-06-2026 000 |
| EDITRAN/AES 24-06-2026 000 24-06-2026 000 |
| 24-06-2026 000 24-06-2026 000 |
| LICENSE FOR CPU ID **-**-9D78-3932 CALCULATED CPU ID 00-0-2-9D78-3932 |
| |
| EXIT, ADVANCE |
-----------------------------------------------------------------------------
```
## Editran G log query.
All operator informational messages generated by editran/G are queried, regardless of whether they were shown on screen or not.
To query these records, the possible selection to be made is requested (Session, Date and Time). The screen is as follows.
```
-----------------------------------------------------------------------------
| 24/06/2026 EDITRAN MANAGER EDITRAN 5.3 |
| 12:58:39 PRESENTATION LOG FILE QUERY |
-----------------------------------------------------------------------------
| |
| |
| |
| DIRECTION (E/S/I)......: |
| |
| ORIGIN (O/A/E/I/U)...: |
| |
| LOCAL CODE.........: |
| |
| REMOTE CODE........: |
| |
| APPLICATION...........: |
| |
| DATE (DD/MM/YYYY)...: / / |
| |
| TIME (HH:MM:SS)......: : : |
| |
| |
| |
-----------------------------------------------------------------------------
```
These data are used in the selection criteria for the Log query. If any of the first 5 is entered, the search will be carried out on that one. If a date is entered, the messages generated from it are displayed; in this case, a starting time can also be provided for the query. These data are:
* **DIRECTION**:
* E: Incoming messages.
* S: Outgoing messages.
* I: Informational messages or incidents that occurred.
* Blank: All.
* **ORIGIN**:
* O: Operator of editran/G
* A: Application JCL.
* E: editran/P.
* I: editran/G itself
* 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**: A specific one, blank for all, and '\*' at the beginning or end.
* **DATE:** From a specific one or zeros from the beginning of the Log.
* **TIME**: from a specific one within a date or zeros from the beginning of the messages of a date.
If no date or time is entered, the latest recorded messages are shown.
```
24/06/2026 12:58:53 PRESENTATION LOG QUERY EDITRAN 5.3
DIREC.: * ORIG.: * SESS.: ************************ D-TIME: **/**/****-**:**:**
TI CODE PRESENTATION SESSION APL.TR DATE TIME JOB-ID
-- ------- -------------------------- ------ ---------- -------- --------------
EA ZTG0021 000099940 000099980 000006 24/06/2026 12:57:01 KIIMS063 03681
CUMULATIVE PRESENTATION SEND REQUEST
II ZTG0046 000099940 000099980 000006 24/06/2026 12:57:02 KIIMS063 03681
END OF LOADING OF APPLICATION FILE NF000001
II ZTG0013 000099940 000099980 000006 24/06/2026 12:57:02 KIIMS063 03681
EMISSION LOAD OF CONVERTER ZTBGBG15 COMPLETED. R-C: 00000
II ZTG0087 000099940 000099980 000006 24/06/2026 12:57:02 KIIMS063 03681
NORMALIZED CSB FILE LOADING COMPLETED SUCCESSFULLY
II ZTG0083 000099940 000099980 000006 000006 24/06/2026 12:57:10 KIIMS063 03681
END OF TRANSMISSION SESSION LOAD: BUFFER ZTBPFEE
II ZTG0014 000099940 000099980 000006 24/06/2026 12:57:10 KIIMS063 03681
PRESENTATION LOAD COMPLETED SUCCESSFULLY
SI ZTG0015 000099940 000099980 000006 000006 24/06/2026 12:57:10 KIIMS063 03681
SEND REQUEST IS REQUESTED TO EDITRAN (A1R)
IA ZTG0109 000099940 000099980 000006 24/06/2026 12:57:10 KIIMS063 03681
THE USER APPLICATION PROGRAM ZTBGBUOP IS CALLED
IA ZTG0110 000099940 000099980 000006 24/06/2026 12:57:10 KIIMS063 03681
USER PROCESS COMPLETED SUCCESSFULLY
EXIT, BACK, FORWARD
```
Once inside the Log query, you navigate forward or backward using PF8 and PF7 respectively. PF3 returns to the options screen for the query.
Shown are: Type (direction and origin), message code, presentation session (codes of local, remote and presentation application), transmission application (only if editran/P is source or destination), message date and time, job name, job number and message text.
## Query of buffer associated with session
A menu is shown in which you can select the buffer name (generic as spaces, specific, with 1 asterisk on the left and right), the buffer type (send, receive or both), and the session (generic as spaces, specific, with 1 asterisk on the left and right), so that you can query the buffers of a session, those of n sessions, etc.
```
-----------------------------------------------------------------------------
| 24/06/2026 FILE QUERY EDITRAN 5.3 |
| 12:59:14 QUERY OF BUFFERS ASSOCIATED WITH SESSIONS |
-----------------------------------------------------------------------------
| |
| |
| |
| |
| BUFFER NAME .......: |
| |
| FILE TYPE (E/R/X).: |
| |
| SESSION............: |
| |
| |
| |
| |
| (WARNING. IN A GENERIC REQUEST THE QUERY MAY TAKE TIME) |
| |
| |
| |
| |
| |
-----------------------------------------------------------------------------
```
```
02/10/2023 FILE QUERY EDITRAN 5.3
15:33:56 QUERY OF BUFFERS ASSOCIATED WITH SESSIONS
BUFFER NAME...: FILE TYPE....: E
EXTERNAL SESSION..:
CALCULATED DSNAME:
S INTERNAL SESSION LOCAL CODE-REMOTE CODE-APPLIC. DDNAME E/R TYP
- -------------------------------- ------------------------ ------- --- ---
ACH-0001 ONLY SERVES TO VALIDATE 000099940000000010CEGSPV ZTBPFEL E M
ACH-0001-CHE EMITS END OF PRESENTATION 000099940000000010CECPRE ECP0000 E M
ACH-0001-CHE EMITS REJECTED END 000099940000000010CECREC ECR0000 E M
ACH-0001-CHE EMITS BILATERAL BALANCES 000099940000000010CECSAL ECS0000 E M
ACH-0001-CHE REC-PRESEN/EMI-CONF 000099940000000010ECCPRE ECC0000 E M
ACH-0001-CHE REC-RECHAZ/EMI-CONF 000099940000000010ECCREC ECC0000 E M
ACH-0001-DEB EMITS END OF PRESENTATION 000099940000000010CEDPRE EDP0000 E M
ACH-0001-DEB EMITS REJECTED END 000099940000000010CEDREC EDR0000 E M
ACH-0001-DEB EMITS BILATERAL BALANCES 000099940000000010CEDSAL EDS0000 E M
ACH-0001-DEB REC-PRESEN/EMI-CONF 000099940000000010ECDPRE EDC0000 E M
ACH-0001-DEB REC-RECHAZ/EMI-CONF 000099940000000010ECDREC EDC0000 E M
ACH-0001-TRA EMITS END OF PRESENTATION 000099940000000010CETPRE ETP0000 E M
ACH-0001-TRA EMITS REJECTED END 000099940000000010CETREC ETR0000 E M
ACH-0001-TRA EMITS BILATERAL BALANCES 000099940000000010CETSAL ETS0000 E M
FIRST SCREEN, ADVANCE
```
If we select one of the records, it shows us the details.
```
02/10/2023 FILE QUERY EDITRAN 5.3
15:35:14 QUERY OF BUFFERS ASSOCIATED WITH SESSIONS
-------------------------------------------------------------------------------
SELECTION CRITERIA
BUFFER NAME...: FILE TYPE....: E
SESSION..........:
DATA OF THE SELECTED SESSION
SESSION..........: ACH-0001 ONLY SERVES TO VALIDATE
LOCAL.....: 000099940 REMOTE....: 000000010 APPL.....: CEGSPV
TRANSM. LENGTH.: 4050 CURRENT RECEIPT BURST: 000
EXCI NETNAME....:
SENDER BUFFER DATA (IF SEARCH CRITERION IS MET)
BUFFER NAME...: ZTBPFEL BUFFER TYPE.....: M
PROFILE DSNAME.: KI.EGDC.ZTBP.ZTBPFEL
CALCULATED DSNAME: KI.EGDC.ZTBP.ZTBPFEL
RECEIVER BUFFER DATA (IF SEARCH CRITERION IS MET)
BUFFER NAME...: BUFFER TYPE.....:
PROFILE DSNAME.:
CALCULATED DSNAME:
```
---
# 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-activity-control/file-query.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.