> 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/tcp/editran.-description-of-fields-and-formats-user.md). # Editran. Description of fields and formats (user) ## Flowcharts ``` ---------- ------------------------ ---------- ---------- ---------- ¦N COPIES¦ ¦ N COPIES ¦ ¦N COPIES¦ ¦N COPIES¦ ¦N COPIES¦ ¦¿TERMID?¦ ¦ NO TERMINAL ¦ ¦1 x PORT¦ ¦NO TERM¦ ¦¿TERMID?¦ ¦--------¦ ---------------------- ¦ ¦--------¦ ¦--------¦ ¦-------- ¦ ¦ ZTB0 ¦-- ¦ ZTBB ¦-NET ¦ ZTBA ¦-- ¦ ZTBB ¦-- ¦ ZTB0 ¦-- ¦ CORE ¦ ¦ CLIENT ¦ ¦LISTENER¦ ¦SERVER ¦ ¦ CORE ¦ ¦ZTBPO100¦ ¦ ZTBPOTCD ¦ ¦ZTBPOTCC¦ ¦ZTBPOTCD¦ ¦ZTBPO100¦ ¦ ¦ ¦ ¦ ¦PORT 7777 ¦ ¦ ¦ ¦ ---------- ------------------------ ---------- ---------- ---------- ¦CALL-REQ¦ ¦ ¦ ¦ ¦ ¦INITAPI ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦GETCLIENTID ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦SOCKET ¦ ¦ ¦ ¦ ¦ ¦ START ¦ ¦ ¦ ¦ ¦ ¦BIND ¦ ¦ ¦ ¦ ¦ ¦ZTBPQCLD-------->INITAPI ¦ ¦ ¦ ¦LISTEN ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦GETHOSTNAME ¦ ¦ ¦ ¦ ¦ ¦ ¦SOCKET(1) ¦ ¦ ¦SELECTEX¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦GETHOSTBYNAME¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦SETSOCKOPT ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦FCNTL ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦CONNECT ----------------------> ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ <---------------------ACCEPT ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦GIVESOCKET ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦START ZTBB--->RETRIEVE¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ <-----TAKESOCKET ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦SETSOCKOPT ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ FCNTL ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦SELECTEX¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE USER DATA----------------------------->READ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦CALL-IND--------->CALL-IND ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦CALL-ACPT ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE TS¦ ¦CALL ACCEPT<---------------------READ <---------------------WRITE <--------ZTBEXXXX¦ ¦-->SAP ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE TS¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ZTBEXXXX----------------------->WRITE ---------------------->READ -------->SAP -- ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦SAR <-| ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE TS¦ ¦ SAR <-----------------------READ <-------------- ¦ ¦WRITE <--------ZTBEXXXX¦ ¦ SFP ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE TS¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ZTBEXXXX---------------------->WRITE ---------------------->READ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE TS¦ ¦ ¦ ¦SEND ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ZTBRXXXX¦ ¦ ¦ ¦BURST + ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ SBP ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE TS¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ZTBEXXXX---------------------->WRITE ---------------------->READ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE TS¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ZTBRXXXX-------->SFP+SBP ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦SBR ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦WRITE TS¦ ¦ SBR <-----------------------READ <-------------- ¦ ¦WRITE <--------ZTBEXXXX¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦REL-REQ ----------------------->CLOSE(2)-------------------->CLOSE --------->REL-IND¦ ¦ ¦ ¦ ¦ ¦ RETURN ¦ ¦ CLOSE <-----RETURN ¦ ¦ ¦ ---------- ------------------------ ---------- ---------- ---------- ``` ## Trace query A network message protocol has been implemented that is easily interpretable because of its similarity to X25 (now obsolete), with call request X0B, accept X0F and release X13. The cvc is the CICS task number and the lu is the local or remote port (depending on whether it is an incoming or outgoing call). An x20 message is included to display errors (see the log with cause-diagnostic. Documentation on ERRNO, RETCODE and error messages in TCPCICS, provided by the macros used for EXTENDED SOCKETS, is available in appendix C of the IBM TCP/IP for MVS manual. CICS TCP/IP Socket Interface Guide and Reference. Document Number SC31-7131-03. Program number 5655 HAL. File Number S370/4300/30xx-50. See also Document Number: SC31-8518-00. If the corresponding errno does not appear, the error may be OS390 V2R5 OPEN EDITION, so it may be found in F1AF9000 IP Planning and Migration Guide ``` 14/03/2000 EDITRAN MANAGEMENT EDITRAN 14:00:52 TRACE QUERY VERSION 5.3 SESSION : DATE : 14/03/2000 S SESSION TIME S MSG NSM/LU T COMMENT = ============================= ====== = ==== ====== = =================== CICS01-CICS02 TCP PRUTCP 140026 S TCP 07777 0B 0002 CICS02-CICS01 TCP PRUTCP 140027 E TCP 01067 0B 0EF0 CICS02-CICS01 TCP PRUTCP 140027 S TCP 01067 0F 0EF0 CICS02-CICS01 TCP PRUTCP 140027 E TCP 01055 0B 0F85 CICS02-CICS01 TCP PRUTCP 140027 S TCP 01055 0F 0F85 CICS01-CICS02 TCP PRUTCP 140027 E TCP 07777 0F 0EEE 0002 CICS01-CICS02 TCP PRUTCP 140027 S SAP NOTIFICATION REQ. 00 CICS01-CICS02 TCP PRUTCP 140027 S STN NOTIFICATION T/O CICS02-CICS01 TCP PRUTCP 140029 E SAP NOTIFICATION IND. 00 CICS02-CICS01 TCP PRUTCP 140029 S SAR+ NOTIFICATION RESP. 00 CICS01-CICS02 TCP PRUTCP 140030 E SAR+ NOTIFICATION RESP. 00 CICS01-CICS02 TCP PRUTCP 140049 E E11 RELEASE REQUEST CICS01-CICS02 TCP PRUTCP 140049 S SAB RELEASE REQ. 02 CICS02-CICS01 TCP PRUTCP 140050 E SAB RELEASE REQ. 02 CICS02-CICS01 TCP PRUTCP 140050 S TCP 01055 13 0F85 0000 00 0F CICS01-CICS02 TCP PRUTCP 140051 E TCP 07777 13 0EEE 0000 00 0F 00000000000000000000000000000 172115 E TCP 07777 20 0000 15 09 ``` The meaning of the previous trace is as follows, for example, for the second message: * In the S and Comment columns, an incoming message (E) appears, and it is an x’0B’ message (call indication). * In the NSM/LU column, the remote port appears (in this case 1055 or x’41F’). * In the Comment column, a cvc appears, x’0F85’ or 3973 in decimal, which is actually the CICS task number (transid ZTBB) that processes the connection indication. It is important to note that if, in a very short time, that number jumps by very large amounts, we will find that CICS is very heavily loaded (it is executing many tasks simultaneously). If problems are detected in CICS, review the parameterization of the CICS-to-VTAM definition, specifically the EAS parameter (number of simultaneous active communications) and the relationship between the Tclass parameters of the transactions and the CMXT parameter of the SIT (transid can be assigned to a class, and the SIT limits the number of transid in each class. The SIT has the MXT parameter to indicate the number of CICS transid. In some cases, digits appear, which correspond to the CNID (application identifier, in the case of a call request, so that it returns the same thing in the accepted call. Other types of message are x’0F’ (accepted call), x’13’ (release) and x’20’ (error), in addition to x’0B’ itself, which if it is meaningful S means call request. If we select the second message (expanded trace), we see the complete content of the incoming call (among other things, the previously described fields x’0B’, x’041F’ and x’0F85’ appear. The session editran user data (x’C0...0A’) and the remote IP address (192.168.172.088), whose DNS is ampurdan.indra.es, also appear. In this case, they are all preceded by the ‘TCP ‘ header or x’E3C3D740’, which appears in the MSJE column. ``` 14/03/2000 EDITRAN MANAGEMENT EDITRAN 12:14:29 TRACE QUERY VERSION 5.3 TRACE SESSION...: CICS02-CICS01 TCP PRUTCP DATE SSAAMMDD.: 20000314 TIME HHMMSS....: 140027 INPUT/OUTPUT.: E E3C3D7400B0000041F0F8500000000000000000000000000000000000000000FC0A3310000 9994305052555443500A4040404040404040404040404040404040404040000000C9404040 40404040404040404040404040404040404040404040404040404040404040404040404040 404040404040404040F1F9F24BF1F6F84BF1F7F24BF0F8F800000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000011819497A499 8481954B89958499814B85A240404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 01B34040400000404040F1F4F0F0F2F7404040404040 PF2: SWITCH HEXADECIMAL - CHARACTER ``` If PF2 is pressed, it is displayed in character mode: ``` 14/03/2000 EDITRAN MANAGEMENT EDITRAN 12:14:29 TRACE QUERY VERSION 5.3 TRACE SESSION...: CICS02-CICS01 TCP PRUTCP DATE SSAAMMDD.: 20000314 TIME HHMMSS....: 140027 INPUT/OUTPUT.: E ....+....1....+....2....+....3....+....4....+....5....+....6....+....7.... TCP . ...> I .{t. rg........ 192.168.172.088 .ampurdan.indra.es .. 140027 MESSAGE PROCESS TIME : 140027 PROCESSED MESSAGE LENGTH: 000435 PF2: SWITCH HEXADECIMAL - CHARACTER ``` Next, a trace with errors is shown: ``` 16/06/2004 FILE QUERY editran 5.3 09:56:17 TRACE QUERY SESSION : DATE : 16/06/2004 SEL SESSION TIME S MSG NSM/LU T COMMENT = ============================= ====== = ==== ====== = =================== S01DI S02DI TCP001 095614 E E00 CONNECTION REQUEST S01DI S02DI TCP001 095614 S STC CONNECTION TIMEOUT S01DI S02DI TCP001 095614 S TCP 07777 0B 0002 S01DI S02DI TCP001 095615 E TCP 07777 20 027C 07 00 S01DI S02DI TCP001 095615 E TCP 07777 13 027C 0002 FF 0C ``` In this case, a call request packet has been sent to the remote side (x’0B’ in the comment column and S in the S column), and the client process has responded with 2 incoming messages (x’13’ and x‘20’ in the comment column and E in the S column). The first of them (x’13’) is a release indication and the second an error indication. Selecting the first one (x’0B’ outgoing call): ``` 16/06/2004 FILE QUERY editran 5.3 10:01:26 TRACE QUERY TRACE SESSION...: S01DI S02DI TCP001 DATE SSAAMMDD.: 20040616 TIME HHMMSS....: 095614 INPUT/OUTPUT.: S ....+....1....+....2....+....3....+....4....+....5....+....6....+....7.... E3C3D7400B00021E61000000000000000000F0F3F0C90000000000000000000FC0A3315000 9994305443503030310A000000000000000000000000000000000040404000000000404040 40404040404040404040404040404040404040404040404040404040404040404040404040 404040404040404040404040404040404040D6F4F3F9F0C200000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000 00000000404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 00E24040400000404040F0F9F5F6F1F4404040404040 ``` The packet that has been sent is the following: * Line 1, columns 9 (x’0B’), call request message type. * Line 1, columns 11-14 (x’0002’) identifier assigned by editran * Line 1, columns 15-18 (x’1E61’) remote port 7777. * Line 1, columns 37-42, timer specified in session 030 seconds. * Line 1, columns 66 onward, user data length and user data * Line 4, column 37 DNS to call (O4390B). If we press PF2, we see the representable characters: ``` ....+....1....+....2....+....3....+....4....+....5....+....6....+....7.... TCP . ../ 030I .{t.& rm...&.... O4390B S 095614 MESSAGE PROCESS TIME : 095614 PROCESSED MESSAGE LENGTH: 000226 ``` The next message is an error indication (x’20’). If we select it: ``` 16/06/2004 FILE QUERY editran 5.3 12:56:41 TRACE QUERY TRACE SESSION...: S01DI S02DI TCP001 DATE SSAAMMDD.: 20040616 TIME HHMMSS....: 095615 INPUT/OUTPUT.: E ....+....1....+....2....+....3....+....4....+....5....+....6....+....7.... E3C3D7402000021E61027C00000700000000F0F3F0C90000000100000000000FC0A3315000 9994305443503030310A000000000000000000000000000000000040404000000000404040 40404040404040404040404040404040404040404040404040404040404040404040404040 404040404040404040404040404040404040D6F4F3F9F0C200000000000000000000000000 ``` The meaning of the new fields is: * Line 1, columns 9 (x’20’), error indication message type. * Line 1, columns 19-22 (x’027C’) task identifier * Line 1, columns 27-30 (x’0700’) Cause 07, diagnostic 00 (see x20 errors in this manual; specifically, it means error in the gethostbyname macro). * Line 1, columns 45-60, errno and retcode of the macro, specifically 00000001 and 00000000, which indicates that the DNS has not been resolved. The next message is a release indication (x’13’). If we select it: ``` 16/06/2004 FILE QUERY editran 5.3 13:03:22 TRACE QUERY TRACE SESSION...: S01DI S02DI TCP001 DATE SSAAMMDD.: 20040616 TIME HHMMSS....: 095615 INPUT/OUTPUT.: E ....+....1....+....2....+....3....+....4....+....5....+....6....+....7.... E3C3D7401300021E61027C0000FF0C000000F0F3F0C90000000000000000000FC0A3315000 9994305443503030310A000000000000000000000000000000000040404000000000404040 40404040404040404040404040404040404040404040404040404040404040404040404040 404040404040404040404040404040404040D6F4F3F9F0C200000000000000000000000000 ``` The meaning of the new fields is: * Line 1, columns 9 (x’13’), release indication message type. * Line 1, columns 27-30 (x’FF0C’) Cause FF, diagnostic 0C (see x13 errors in this manual; specifically, it means that “an error occurs in the client process, before sending user data (up to and including the connect macro). This release is accompanied by a previous x20 message, which indicates the error that occurred (initial TCP macros before sending/receiving user data)”. In short, the error situation mentioned corresponds to the profile DNS not existing on the name server, so it was impossible to make the connect because the remote IP was unknown. For more detailed INDRA traces, set operating-system = EDIP, operating-system-version = spaces or MULT, and maximum-cvcs-number = 999. In this case, TS queues ZTBPEDIP are created (operating-system-version = spaces) or TS queues ZTBH+ (MMSS, minute and second) (operating-system-version = MULT), with data about network writes and reads, to be analyzed by INDRA. In the case of ZTBPEDIP, it is a single TS whose contents are all IP sessions. In the case of ZTBH\*\*\*, ALL MACROS are also recorded. ## Error messages (TYPE X20) x20 messages indicate errors in the process. As an example, the trace shows them as follows (in TCP they carry the TCP key and in PROXY they carry the ETT key), indicating cause x’0F’, diagnostic x’05’:
``` 000099940000099980AE9994 170338 E TCP 08888 20 3497 0F 05 ``` By selecting them, in some cases you can find information about errno – retcode TCP/IP, for example: ``` ....+....1....+....2....+....3....+....4....+....5....+....6....+....7.... E3C3D74020000222B8349700000F05000000000000000000003DFFFFFFFF00000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040404040404040404040404040404040404040404040 00B24040400000404040F1F7F0F3F3F8404040404040 ``` In the previous case, errno (x’0000003D’ = 61) and retcode (x’FFFFFFFF’ = -1) are shown. The meaning is: cause x’05’ (Error in read macro), diagnostic x’0F’ (Error in ZTBB or client-server child, when attempting to receive user data), read error 61 (ECONNREFUSED, the connection request has been refused) The meanings of those x20 messages are shown below:


X’01’	X’xx’	INITAPI macro error
	X’00’	Error in ZTBB or client
	X‘05’	Error in ZTBA or parent server
X’02’	X’xx’	GETCLIENTIID macro error
	X‘05’	Error in ZTBA or parent server
X’03’	X’xx’	SOCKET macro error
	X’00’	Error in ZTBB or client
	X‘05’	Error in ZTBA or parent server
X’04’	X’xx’	SETSOCKOPT macro error
	X‘01’	Error in ZTBB or client. Error in SO-REUSEADDR option
	X’02’	Error in ZTBB or client. Error in SO-KEEPALIVE option
	X’05’	Error in ZTBB or server-child. Error in SO-REUSEADDR option
	X’06’	Error in ZTBB or server-child. Error in SO-KEEPALIVE option
X’05’	X’xx’	BIND macro error
	X‘05’	Error in ZTBA or parent server
X’06’	X’xx’	LISTEN macro error
	X‘05’	Error in ZTBA or parent server
X’07’	X’xx’	GETHOSTBYNAME macro error
	X’00’ and X’01’	Error in ZTBB or client. X00. Error resolving the connection IP. X01. editran/Proxy. Error resolving the destination IP.
X’08’	X’xx’	GETHOSTNAME macro error
	X‘05’	Error in ZTBA or parent server
X’09’	X’xx’	CONNECT macro error
	X’00’	Error in ZTBB or client
X’0A’	X’xx’	ACCEPT macro error
	X‘05’	Error in ZTBA or parent server
X’0B’	X’xx’	GIVESOCKET macro error
	X‘05’	Error in ZTBA or parent server
X’0C’	X’xx’	TAKESOCKET macro error
	X’05’	Error in ZTBB or server child
X’0D’	X’xx’	FCNTL macro error
	X’00’	Error in ZTBB or client
	X‘05’	Error in ZTBB or server child
X’0E’	X’xx’	SELECTEX macro error
	X’00’	Error in ZTBB or client. User data was being sent
	X‘01’	Error in ZTBB or client. User data was sent and it was expected to receive it
	X’02’	Error in ZTBB or client. Select by write error in data traffic
	X’03’	Error in ZTBB or client. Select by read error in data traffic
	X‘05’	Error in ZTBB or server-child. User data was received and an attempt was made to resend it
	X’06’	Error in ZTBB or server-child. User data was received, not resent, and it was in select by read
	X’07’	Error in ZTBB or server-child. Select by write error in data traffic
	X’08’	Error in ZTBB or server-child. Select by read error in data traffic
	X’09’	Error in ZTBA or parent server, while waiting for connections
	X’0A’	Error in ZTBA or parent server, while waiting for socket handoff
X’0F’	X’xx’	READ macro error
	X‘05’	Error in ZTBB or client-server child, when attempting to read from the network.
X’10’	X’xx’	WRITE macro error
	X‘00’	Error in ZTBB or client. User data was being sent
	X‘01’	Error in ZTBB or client. Data was being sent in data traffic
	X‘05’	Error in ZTBB or server-child. User data came in and was being resent
	X‘06’	Error in ZTBB or server-child. Data was being sent in data traffic
X’11’	X’xx’	ERROR CALL EZACIC06 (SELECTEX MASKS)
	X‘00’	Error in ZTBB or client. User data was being sent
	X‘01’	Error in ZTBB or client. User data was sent and it was expected to receive it
	X‘02’	Error in ZTBB or client. Select by write error in data traffic
	X‘03’	Error in ZTBB or client. Select by read error in data traffic
	X‘05’	Error in ZTBB or server-child. User data was received and an attempt was made to resend it
	X‘06’	Error in ZTBB or server-child. User data was received, not resent, and it was in select by read
	X‘07’	Error in ZTBB or server-child. Select by write error in data traffic
	X‘08’	Error in ZTBB or server-child. Select by read error in data traffic
	X‘09’	Error in ZTBA or parent server, while waiting for connections
	X‘0A’	Error in ZTBA or parent server, while waiting for socket handoff
X’12’	X’xx’	ERROR CALL EZACIC08 (CACHE FILE)
	X‘00’	Error in ZTBB or client.
X’13’	X’xx’	ERROR RETRIEVE
	X‘00’	Error in ZTBB or client, with error receiving data from editran
	X‘0B’	Error in ZTBB or client-server child, with error receiving data
X’14’	X’xx’	ERROR START TRANSID – LINK
	X’’01’	Error in ZTBB or server child. Acting as client, a link to the editran/PR control program is attempted and it errors.
	X’02’	Error in ZTBB or server child. Acting as server child, a link to the editran/PR control program is attempted and it errors.
	X‘05’	Error in ZTBA or parent server, when trying to start server child (ZTBB)
X’15’		Other Errors in ZTBZ or server dispatcher
	X’01’	Error in ZTBZ or server dispatcher. EZACONFG file open error
	X‘02’	Error in ZTBZ or server dispatcher. EZACONFG file read error
	X‘03’	Error in ZTBZ or server dispatcher. Start transid error to parent server
	X’04’	Error in ZTBZ or server dispatcher. There is no parent server in EZACONFG or it does not have SECEXIT=editran
X’16’		Other Errors in ZTBA or parent server
	X’01’	Crash in ZTBA or parent server. The maximum number of simultaneous incoming connections to a tcp port has been reached. Check local environment parameter NRO.CONEX. SIMULT.LISTENER.
	X‘02’	Error in ZTBA or parent server. Error writing TS queue (ZTBPQTCC).
	X‘03’	Error in ZTBA or parent server. Error rewriting TS queue (ZTBPQTCC).
	X‘04’	Error in ZTBA or parent server. EZACONFG file open error
	X‘05’	Error in ZTBA or parent server. EZACONFG file read error
	X‘06’	Error in ZTBA or parent server. An active parent server already exists for the specified port (enqbusy)
	X‘07’	Error in ZTBA or parent server. No record exists in EZACONFG or it does not have SECEXIT = editran
	X’15’	Abend in ZTBA
X’17’		Other Errors in ZTBB (client or server child).
	X’01’	Error in ZTBB acting as server child. User data did not arrive within the time specified in the local environment, parameter TIME-OUT USER DATA MAX(MSS))
	X’03’	Error in ZTBB acting as client. User data has not been sent to the network, when it is about to read: -A message arrives from the network (it makes no sense, since the remote EDI does not take initiative) -A read error occurs (in this last case it is accompanied by another message with the errno for the read error, which may be zeros if the connection drops).
	X’04’	Error in ZTBB acting as server child in TCP/IP protocol (not in PR). User data has been received, passed to the core, and it is about to read from the network: -A message arrives from the network (it makes no sense, since the remote EDI does not take initiative) -A read error occurs (in this last case it is accompanied by another message with the errno for the read error, which may be zeros if the connection drops).
	X’05’	Error in ZTBB acting as client or server child. In the case of the client, user data has been sent to the network and it is waiting for a response. In the case of the server child, a connection has arrived and it is waiting for user data to arrive. A message > 36 bytes (maximum permitted user data) arrives (TCP/IP protocol only). Internal error.
	X’06’	Error in ZTBB acting as client. User data has been sent to the network and it is waiting for a response. A user data response message arrives with byte 2 x’A4’, and a user data format with length was sent from the source. (TCP/IP protocol only) Internal error.
	X’07’	Error in ZTBB acting as client or server child. In the case of the client, user data has been sent to the network and it is waiting for a response. In the case of the server child, a connection has arrived and it is waiting for user data to arrive. A message arrives > the length indicated at the start of the user data. Internal error.
	X’08’	Error in ZTBB acting as client. User data has been sent to the network and it is waiting for a response. A message has arrived that does not correspond to the original user data that was sent (TCP/IP-Proxy protocol only). Internal error.
	X’09’	Error in ZTBB acting as client. User data has been sent to the network and it is waiting for a response.
	X’0A’	Error in ZTBB acting as client or server child. In the case of the client, user data has been sent to the network and it is waiting for a response. In the case of the server child, a connection has arrived and it is waiting for user data to arrive. A message other than call-ind, accept-ind, release-ind arrives (PR protocol only). Internal error.
	X’0B’	Error in ZTBB acting as client or server child. In the case of the client, user data has been sent to the network and it is waiting for a response. In the case of the server child, a connection has arrived and it is waiting for user data to arrive. Message X0B arrives that does not have the proxy byte flagged (xff).
	X‘10’	Unknown error in ZTBB or CLIENT
	X‘11’	Unknown error in ZTBB or server child
	X’15’	Abend in ZTBB

## Release messages (TYPE X13) They are started from TCP-PR with destination to the editran core or vice versa. In the case of PR releases, they are collected in some cases, indicating the errno and retcode of the proxy. In the case of TCP releases, if they are as a result of normal transmission completion, cause x00, diagnostic x0F, is set. In the rest of cases, if it is the program that “simulates a release”, cause x’FF’ is set and the diagnostic described below. As an example, in the trace the message appears with cause (FF), diagnostic (01): ``` 000099940000099980AE9994 170338 E TCP 08888 13 3497 0002 FF 01 ``` | Diagnostic | Reason for the error with cause x’00’ | | ---------- | ---------------------------------------- | | X’0F’ | Orderly release (SAB) of editran TCP/IP. | --- # 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/tcp/editran.-description-of-fields-and-formats-user.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.