> 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/configuracion_local.md). # Appendix A. Transmission module messages to the operator and Log These messages appear on the OPERATOR TERMINAL, if specified in the Session profile, and are always recorded in the Log database, as a result of significant events in connections and transmissions, whether normal or exceptional. The following messages are detailed with their explanation, if it is not obvious, and the recommended action, if applicable, to resolve the possible incident: * **ZTP001: RELEASE BY THE OPERATOR** > A release C:00 D:08 has been received, possibly originating from the transmission module of a remote Editran, due to a request from the corresponding operator. * **ZTP002: REMOTE CALL REJECTED. CROSSOVER** > When a crossover of calls occurs between the local and the remote, the transmission module of the Editran with the lower local code releases with C:00 D:04. In this case it is the local one that has released. It is assumed that the remote call succeeds. * **ZTP003: REMOTE CALL REJECTED. UNKNOWN SESSION** > The remote call is rejected because the session is not registered locally. It may also be because the connection type does not match in the local and remote session profiles. The remote receives a release with C:00 (Cause) D:0D (Diagnosis). * **ZTP004: CIRCUIT RELEASE. INTERNAL ERROR IN GCV** > The most likely cause is receiving a remote release C:00 D:03, which indicates that the maximum number of sessions that Editran can manage has been reached. See MAXIMUM NRO. CVC in Administrator, Local Environment. * **ZTP005: CIRCUIT RELEASE. NETWORK RECOVERY** > Circuit release due to network outage/recovery > > Action: Check the status of the network. * **ZTP006: RELEASE DUE TO NETWORK RESTART** > Local or remote release C:00 D:09 due to network restart. The local one occurs for sessions that are not in data traffic, but are connected, with operator option 9. * **ZTP007: CALL REJECTED. INVALID TIME** > The remote call is rejected with C:00 D=0C because it was made outside the interval specified in the session profile START TIME - END TIME. * **ZTP008: REMOTE CALL REJECTED. CONNECTION TYPE NOT ALLOWED.** > The remote call is rejected because it uses a connection type that is not allowed. * **ZTP009: REMOTE CALL REJECTED. CALLING END** > The remote call is rejected with C:00 D:0E because CALLING END = L (Local) in the session profile. * **ZTP010: REMOTE CALL ACCEPTED** > The remote call has passed all checks for the existence of the session profile, calling and called direction, and the others seen in the previous messages. A confirmation is sent to the remote. * **ZTP011: CONNECTION ESTABLISHED** > The remote has confirmed the local call or the local has confirmed the remote call. * **ZTP012: TRANSMISSION RELEASE** > A connection release has occurred that is not translated into a specific message. > > The message must be accompanied by the Error Number or TCP 'errno'. The error numbers can be consulted in the IBM manual “z/OS Communications Server. IP IMS Sockets Guide” * **ZTP013: CONNECTION ALREADY EXISTS** > A session connection has been requested by the Editran operator and it is already connected. * **ZTP014: LOCAL CANNOT CALL. PROFILES** > An attempt is made to establish a session connection and its profile has CALLING END = R (Remote). * **ZTP015: MAKES THE CALL** > Local Editran makes a call to the remote as a result of an operator connection request (option 2) or an operator or interface send/receive request when there is no connection and AUTOMATIC CONNECTION in the session profile = S. * **ZTP016: REQUEST IN FLIGHT** > A connection, send, or receive request is requested that had already been processed previously and with *timeout* enabled. * **ZTP017: NO CONNECTION EXISTS** > With a session not connected, a release or transmission has been requested with AUTOMATIC CONNECTION = N in the session profile. * **ZTP018: TRANSMITTING** > A release has been requested when the session is transmitting, or a send/receive has been requested while already transmitting. > > Action: If you want to release a session that is transmitting, you must request interruption of send or receive display, as appropriate (options 5 and 9 of the Editran operator). * **ZTP019: REMOTE SENDER FILE QUERY** > The control record of the remote send buffer has been queried (file query option 1). It is required to be in session with the remote and to have a terminal set in TERM. OPER in the session profile. * **ZTP020: REMOTE RECEIVER FILE QUERY** > The same as the previous one for the remote receiver buffer. * **ZTP021: SENDER BUFFER FILE CLOSED** > This message does not appear in the log, but it can be received by the remote when querying the local sender buffer if it is not loaded. * **ZTP022: RECEIVER BUFFER FILE CLOSED** > Similar to the previous one for the receiver buffer. * **ZTP023: RELEASE DUE TO CALL CROSSOVER** > Similar to ZTP002 but releasing the remote. * **ZTP024: PENDING CONNECTION** > The transmission request is waiting for the circuit to be established. * **ZTP025: LOCAL CANNOT SEND. PROFILES** > Send has been requested and the TRAFFIC DIRECTION of the session profile does not allow it * **ZTP026: RECEIVING** > A receive or release request reaches Editran when reception is in progress. * **ZTP027: RECEIVE REQUEST** > The reception of a session is requested from Editran. * **ZTP028: LOCAL CANNOT RECEIVE. PROFILES** > Similar to ZTP041 for reception. * **ZTP029: BEGINNING OF SESSION. LOCAL TRANSMISSION** > Local Editran has sent the first burst of messages to the remote. * **ZTP030: EXCESS OF RETRIES TO RECEIVE** > Reception is requested from the remote (that the remote transmit) and there is no response. The request is repeated as many times as NUM. MAX. RETRIES in the session profile with the periodicity expressed in TIME-OUT, and no response is received either. * **ZTP031: EXCESS OF RETRIES TO SEND** > Similar to ZTBP030 for a request to send to the remote. * **ZTP032: CORRECT AND COMPLETED TRANSMISSION** > The transmission has been completed. The local has sent the end-of-transmission message to the remote and it has replied affirmatively. * **ZTP033: END OF LOCAL TRANSMISSION REQUESTED BY THE REMOTE** > The remote has requested the end of transmission without it having been completed. * **ZTP034: SCP RECEIVED IN INCORRECT STATE** > An SCP message (remote send request) enters and the SESSION has not been established. > > Action: A logically impossible situation, but one that could occur if there is some queued message from a previous connection of the same session. It would require an analysis of the trace at both ends for diagnosis. * **ZTP035: INCOMPATIBLE PROFILES (TRANSMISSION/PRESENTATION)** > The remote send request is rejected because the TRAFFIC DIRECTION of the session profile does not allow it. * **ZTP037: RECEPTION DATABASE NOT PREPARED** > Reception has been requested locally or transmission remotely and the local reception buffer is not prepared. If applicable, a later message will indicate the subsequent action taken by Editran depending on several circumstances, including whether or not PREVIOUS RECEPTION PROCESS has been set in the session profile. * **ZTP038: BEGINNING OF RECEPTION** > The beginning of transmission has been requested by remote Editran and the local has replied affirmatively. * **ZTP039: START OF TRANSMISSION** > Transmission to the remote begins. * **ZTP040: TRANSMISSION DATABASE NOT PREPARED** > Similar to ZTP037 for the local sender buffer. * **ZTP041: INCORRECT MESSAGE RECEIVED. RECEIVER PROCESS** > Similar to ZTP034. * **ZTP042: END OF RECEPTION REQUESTED BY OPERATOR** * **ZTP043: BUFFER FILES IN INCOMPATIBLE STATE** > An attempt is made to send a sender buffer with a total number of records lower than that recorded by the receiver buffer. Possibly there was an incomplete transmission and the sender loaded a smaller file again and the receiver did not initialize reception. > > Action: The receiver must initialize its reception buffer. * **ZTP044: SEQUENCE LOSS IN RECEIVER PROCESS** > Some record is missing in reception. Possible invalid CRC problem. * **ZTP045: TOTALS MISMATCH IN RECEIVER PROCESS** > Reception process: the totals sent do not match the received ones. * **ZTP046: EXCESS OF RETRIES IN THE RECEIVER PROCESS** > Similar to ZTBP046 for a receive request. * **ZTP047: IMPOSSIBILITY OF RECEPTION DUE TO PROFILES** > Reception is not allowed due to the TRAFFIC DIRECTION of the session profile. * **ZTP048: CORRECT AND COMPLETED RECEPTION** * **ZTP049: END OF TRANSMISSION FROM THE REMOTE** * **ZTP050: SEP RECEIVED IN INCORRECT STATE** > Similar to ZTP034. * **ZTP051: EXCESS OF BLOCK RETRIES** > Similar to ZTP053. * **ZTP052: SBR WITH TOTALS MISMATCH** > Similar to ZTP045. * **ZTP053: EXCESS OF RETRIES FOR SYNCHRONIZATION** > The sender, after sending the number of records specified in NUM. REG. SYNCHRONIZATION in the session profile, sends a synchronization message to the receiver and, if no response is received, retries as many times and with the periodicity specified in the session profile, likewise without receiving a response. > > Action: A possible cause would be that the sender has a very high number of synchronization records depending on the line speed, in which case coherent values should be set in NUM. REG. SYNCHRONIZATION, TIME-OUT, and NUM. MAX. RETRIES of the session profile. * **ZTP054: EXCESS OF RETRIES TO CLOSE** > An end-of-transmission SEP message has been sent and all possible retries have been exhausted and no response has been received from the remote. > > Action: See ZTP046. Check whether the message was really not received at the remote, since if it had been received, the transmission would be finished at the remote but not at the local. * **ZTP055: INCORRECT MESSAGE RECEIVED. SENDER PROCESS** > Similar to ZTP034. * **ZTP056: END OF TRANSMISSION REQUESTED BY OPERATOR** * **ZTP057: BUFFER FILES IN INCOMPATIBLE STATE** > Similar to ZTP043. * **ZTP058: SEQUENCE LOSS IN SENDER PROCESS** > Similar to ZTP044 but during transmission. * **ZTP059: TOTALS MISMATCH IN SENDER PROCESS** > Similar to ZTP045. * **ZTP060: EXCESS OF RETRIES IN THE SENDER PROCESS** > Similar to ZTP030 but during transmission. * **ZTP061: IMPOSSIBILITY OF TRANSMISSION DUE TO PROFILES** > Transmission is not allowed due to the TRAFFIC DIRECTION of the session profile. * **ZTP062: REMOTE SEND REQUEST (NOT USED)** * **ZTP063: USER REQUEST** > The user made an operator request from one of the following menus. > > * Editran Operator (option 2.1) > * State Modification (option 2.2) > > The *REQUEST* may be > > * for the Operator > > > * REQUESTED SEND LOAD > > * REQUESTED POST-SEND PROCESS > > * REQUESTED PRESENTATION SEND > > * REQUESTED END OF SEND > > * REQUESTED RECEPTION INITIALIZATION > > * REQUESTED RECEPTION DOWNLOAD > > * REQUESTED PRESENTATION RECEPTION > > * REQUESTED END OF RECEPTION > > * CONNECTION HAS BEEN REQUESTED > > * RELEASE HAS BEEN REQUESTED > > * RESTART HAS BEEN REQUESTED > * for State Modification > > > * RECEPTION STATE MODIFICATION REQUESTED > > * REQUESTED SEND STATE MODIFICATION > > The *USER* will indicate the user name, if /SIGN ON was performed, or the USERID assigned by default. * **ZTP064: BATCH NOTIFICATION PREPARED SEND BUFFER** > The interface notifies that it has loaded the send buffer, which is available for local or remote Editran. * **ZTP065: BATCH NOTIFICATION PREPARED RECEPTION BUFFER** > Similar to the previous one regarding reception buffer initialization. * **ZTP066: PRE-SEND PROCESS COMPLETED CORRECTLY** > The interface reports that the pre-send process requested from Editran has finished successfully and sending will proceed. * **ZTP067: PRE-RECEPTION PROCESS COMPLETED CORRECTLY** > Similar to the previous one regarding the pre-reception process. * **ZTP068: POST-SEND PROCESS COMPLETED CORRECTLY** > Similar to the previous one regarding the post-send process. * **ZTP069: POST-RECEPTION PROCESS COMPLETED CORRECTLY** > Similar to the previous one regarding the post-reception process. * **ZTP070: ERROR IN PRE-SEND PROCESS** > The interface reports that the pre-send process launched by Editran has ended with an error. > > Action: You should analyze the execution of the process. In Editran it is a *batch job.* * **ZTP071: ERROR IN PRE-RECEPTION PROCESS** * **ZTP072: ERROR IN POST-SEND PROCESS** * **ZTP073: ERROR IN POST-RECEPTION PROCESS** > Similar to ZTP116 for the corresponding process. * **ZTP074: PRE-SEND PROCESS REQUESTED** > The pre-send process has been launched by Editran, which indicates that there is a local or remote send request, that the local sender buffer is not prepared, and that PRE-SEND PROCESS exists in the session profile. * **ZTP075: PRE-RECEPTION PROCESS REQUESTED** > Similar to the previous one for reception. * **ZTP076: POST-SEND PROCESS REQUESTED** > The local has finished sending and launches the POST-SEND PROCESS of the session profile. * **ZTP077: POST-RECEPTION PROCESS REQUESTED** > Similar to the previous one for reception. * **ZTP078: ERROR ISSUING COMMAND.CMD/GCMD** > The transmission module of local Editran tries to start a procedure or check an IMS resource and receives an error code. > > Action: Check that the Editran core transaction is authorized to issue commands. * **ZTP079: INCORRECT APPLICATION REQUEST RECEIVED** > A message is received from an application with an incorrect session or function. It should not normally occur with Indra interfaces and utilities. * **ZTP080: CONNECTION EXISTS. APPLICATION REQUEST REJECTED.** > An A5P request is received for a session when a connection already exists. * **ZTP081: ERROR IN CRC CALCULATION** > An error has occurred in the cyclic redundancy check CRC calculation routine. * **ZTP082: MESSAGE RECEIVED WITH INVALID CRC** > A message has been received from the remote and, when calculating its CRC, it does not match the one included in the message itself. > > Action: Message integrity problem received. It should be very infrequent, because otherwise there may be a malfunction in one of the communications devices, line configurations inappropriate for their characteristics, etc. It may require line traces at both ends for diagnosis. * **ZTP083: REQUEST FOR PREPARATION AND START OF TRANSMISSION** * **ZTP084: REQUEST FOR PREPARATION AND START OF RECEPTION** * **ZTP085: REQUEST FOR TRANSMISSION DOWNLOAD** * **ZTP086: REQUEST FOR RECEPTION DOWNLOAD** > An A5P message has been received from an application with the corresponding request. * **ZTP087: SESSION STATUS QUERY BY APPLICATION** > An A6P message is received from an application. * **ZTP088: RESPONSE TO THE QUERY MADE BY APPLICATION** > The previous message is answered. * **ZTP089: PROCEDURE DOES NOT EXIST IN PROFILES** > An application has requested that Editran launch a pre/post send/receive process and the corresponding procedure does not exist in the session profile. * **ZTP090: EXCESS OF RETRIES TO ESTABLISH SESSION** > After a local call, a SAP session establishment message is sent and, after exhausting retransmission retries, no response is obtained from the remote. > > Action: Check that the local and remote communication resources are available and that there is no message queueing. Verify that there are no network errors and that routes and security rules are up to date. Make sure that unexpected application errors do not occur (abend, CRC error, incident messages, etc.) at either end. If the session uses cryptography, verify that the time-out intervals are adequate (TIME-OUT (MSS) and NUM. MAX. RETRIES). * **ZTP091: SESSION ESTABLISHED** > The remote has responded affirmatively to the local SAP or the local has done the same with the remote SAP. * **ZTP092: END OF SESSION** > The end of session is requested from the remote after a normal or abnormal termination of an operation. Normally, the remote responds by releasing the connection. * **ZTP093: CRYPTO LABELS NOT OBTAINED. IN SESSION REQ. (1)** * **ZTP094: ERROR GENERATING THE UNCERT. OR THE SIGNATURE (2)** * **ZTP095: ERROR GENERATING SESSION KEY (3)** * **ZTP096: CRYPTO LABELS NOT OBTAINED. IN SESSION RES. (4)** * **ZTP097: ERROR DECRYPTING THE UNCERTAINTY OR THE SIGNATURE (5)** * **ZTP098: ERROR DECRYPTING THE SESSION KEY (6)** * **ZTP099: ERROR ENCRYPTING DATA (7)** * **ZTP100: ERROR DECRYPTING DATA (8)** * **ZTP101: ERROR DIFFERENT KEYS AT BOTH ENDS (9)** > See Annex C for the reasons for the error as well as the codes returned by the corresponding encryption routine. * **ZTP102: EXCESS OF CONNECTION RETRIES** > The number of connection attempts for each local-remote IP address combination has been exhausted without achieving the connection. * **ZTP103: INCORRECT SESSION ESTABLISHMENT MESSAGE** > A SAP message has been received from the remote with invalid fields. It should not occur. * **ZTP104: SESSION REJECTED BY PROFILES.VERSION** * **ZTP105: SESSION REJECTED BY PROFILES.MESSAGE LENGTH** * **ZTP106: SESSION REJECTED BY PROFILES.COMPRESSION** * **ZTP107: SESSION REJECTED BY PROFILES.CRYPTOGRAPHY** * **ZTP108: SESSION REJECTED BY PROFILES.CONNECTION TYPE** * **ZTP109: SESSION REJECTED BY PROFILES.CRC** > The remote SAP is rejected because the corresponding parameter in the session profile does not match the equivalent remote parameter. > > Action: Agree with the remote on the parameters to use. See session maintenance in the Administrator in this manual. * **ZTP110: SESSION NOT ESTABLISHED** > A local or remote message has been received with a request that requires the session to be established. * **ZTP111: SESSION REQUEST** > After the connection, the local sends the remote the SAP session establishment message that informs it of the parameters that will be used in the transmission so that it can accept or reject them. **ZTP112: ERROR IN REMOTE BATCH PROCESS** > A release request is received from the remote because some of its pre/post send/receive processes ended in error and the session is connected (unusual). * **ZTP113: RELEASE BY REMOTE OPERATOR** > The remote Editran operator requests the release of the session. * **ZTP114: REMOTE RECEIVER FILE UNAVAILABLE** > A release request is received from the remote because its reception buffer is closed or inaccessible and its pre-reception process has not been launched. * **ZTP115: REMOTE SENDER FILE UNAVAILABLE** > Similar to the previous one regarding the remote send buffer. * **ZTP116: ERROR IN REMOTE COMPRESSION/DECOMPRESSION** > A release request is received from the remote due to an error in its compression/decompression process. * **ZTP117: EXCESS OF RETRIES TO ESTABLISH REMOTE SESSION** > A release request is received from the remote because it was not possible to establish the session. It would be unusual for the release request message to arrive and not the session establishment messages, but anything could happen. * **ZTP118: REMOTE OPERATOR NETWORK RESTART** > A release request is received from the remote due to a restart of its network. * **ZTP119: ERROR IN REMOTE CRYPTOGRAPHY** > A release request is received from the remote due to an error in its cryptographic process. The remote should have in its log a descriptive message of the error produced. * **ZTP120: LOCAL CRYPTOGRAPHY ERROR** > A cryptographic error has occurred locally. A release request with cryptographic ERR9 will be sent to the remote. See Annex C. * **ZTP122: COMPRESSION ERROR** > An error has occurred in the local string compression routine. A release request is sent to the remote. * **ZTP123: DECOMPRESSION ERROR** > An error has occurred when decompressing a message received from the remote. Possible message integrity problem. The process continues, although normally a sequence loss or a message resend from the remote will occur. > > Action: It is recommended to set CRC = S in the local and remote session profiles. * **ZTP124: SEND PREPARATION REQUEST** > A request has been received from an application for Editran to launch a pre-send process, but only with an indication that it should be prepared (load the send buffer). * **ZTP125: RECEPTION PREPARATION REQUEST** > Similar to the previous one for preparing the reception buffer. * **ZTP126: IMPOSSIBILITY OF TRANSMISSION. OUT OF HOURS** > A send request has been received from an application at a time outside the range specified in the session profile. * **ZTP127: NOT SENDING** > A request for end of transmission has been received from an application and no transmission is in progress. * **ZTP128: IMPOSSIBILITY OF RECEIVING. OUT OF HOURS** > Similar to ZTP187 for a receive request. * **ZTP129: IMPOSSIBILITY OF RECEIVING. LOCAL DB NOT AVAILABLE** > A receive request has been received from an application and the session reception buffer is marked as Not Available. > > Action: A "not available" reception buffer normally indicates that Editran launched a post-reception process and that it ended abnormally, or that the interface does not clear it (this is what happens in Editran if "Clear Buffer After Reception" = N is set in the presentation session profile. * **ZTP130: ERROR IN ASCII/EBCDIC TRANSLATION** > Editran does not translate the data, but it does so in some messages for session identification. An error has occurred in this translation process. * **ZTP131: APPLICATION REQUEST TO END TRANSMISSION** > A request for end of transmission has been received from an application. * **ZTP132: APPLICATION REQUEST TO END RECEPTION** > A request for end of reception has been received from an application. * **ZTP133: END OF RECEPTION REQUESTED BY REMOTE. PROFILE ERROR** > The remote requests an end of transmission (logically it is reception on the local side) because its session profile does not allow it to send. * **ZTP134: INCORRECT REMOTE SENDER FILE. LAUNCHES PREVIOUS** > The remote reports that it cannot send because the sender buffer is not prepared, but that it has launched the procedure to prepare it. > > Action: If the remote has it enabled in the session profile, its Editran will take the initiative once its sender buffer has been prepared; otherwise the local side must request reception again. * **ZTP135: INCORRECT REMOTE SENDER FILE. NO PREVIOUS EXISTS** > Situation similar to the previous one, but the remote has not specified the pre-send procedure in the session profile. * **ZTP136: INCORRECT REMOTE SENDER FILE. PREVIOUS IN PROGRESS** > Situation similar to the previous one, but it is possible that the remote is executing its pre-send procedure. Situation similar to ZTP191 regarding the remote sender buffer. * **ZTP137: LOCAL SEND DATABASE NOT AVAILABLE** > Similar to ZTP191 regarding the local sender buffer. * **ZTP138: END OF TRANSMISSION REQUESTED BY REMOTE. PROFILE ERROR** > Similar to ZTP197 for remote reception (local transmission). * **ZTP139: INCORRECT REMOTE RECEIVER FILE. LAUNCHES PREVIOUS** * **ZTP140: INCORRECT REMOTE RECEIVER FILE. DOES NOT LAUNCH PREVIOUS** * **ZTP141: INCORRECT REMOTE RECEIVER FILE. PREVIOUS IN PROGRESS** > Similar to ZTP134, 135 and 136 regarding the remote receiver buffer. * **ZTP143: INCORRECT REMOTE RECEIVER FILE. TOTALS/DATE** > The remote does not allow transmission to it because its reception buffer has a total number of records greater than the local sender buffer. See ZTP043. * **ZTP144: BUFFER LOADED WITH LENGTH DIFFERENT FROM PROFILES** > The local sender buffer was loaded with a different MESSAGE LENGTH than the one currently specified in the session profile. > > Action: Reload the sender buffer or correct the session profile. * **ZTP148: TRANSMISSION RELEASE DETECTED** > A session has been detected whose connection socket has been reused by another transmission, and the connection is considered lost. * **ZTP149: REMOTE CALL REJECTED. TCP/IP CS NOT ALLOWED** > A remote call is rejected because it comes through a TCP/IP client/server not defined for the session. > > Action: Check that the client/server transactions defined for the session match the local IP addresses and ports that the transmission must use. * **ZTP150: NOT RECEIVING** > A receive completion is received from an application and the session is not in the receiving state. * **ZTP151: ERROR IN CALL TO THE KEYS INTERFACE PROGRAM** > An error occurred when calling the external KEYS INTERFACE specified in the session profile. > > Action: Check the return code and reason for the error that accompany the message and consult the documentation for the external encryption interface. * **ZTP152: INCORRECT AUTHENTICATION. ID=XXXXXXXXXXX** > The exchange key whose *label* is XXXXXXXXX has been used as indicated by the External Key Management Interface specified in the session profile. However, this key does not match the one the remote side used in the endpoint authentication process. > > Action: Check the session profile and verify that the KEYS INTERFACE PARAMETERS are correct according to the documentation for that interface. * **ZTP153: SESSION REJECTED.XXXXXXXXXXXXXXXXX** > A rejection is received from the remote side to the local Session Request. The session profile parameter that is inconsistent at both ends is specified. > > Action: Agree with the remote side and modify the session profile accordingly. * **ZTP154: SESSION REJECTED BY PROFILES.** > Similar to the previous one. * **ZTP155: ERROR IN CALL TO SECURITY MODULE ZTBPOCR9** > An error was returned by the Editran cryptographic manager. The message shows C: 91 to 99, which corresponds to encryption ERR1 to 9. See Appendix C. * **ZTP156: SAR REJECTED BY MESSAGE IDENTIFIER** > A response, SAR, is received from the remote to a SAP session establishment message, with an identifier that does not match the SAP's. Possible queuing of messages from a previous connection. * **ZTP157: ERROR READING FROM THE IOPCB(GU).** * **ZTP158: ERROR IN ISRT/PURG AGAINST ALTVA PCB.** * **ZTP159: ERROR ACCESSING THE DB (GU/GHU).** * **ZTP160: ERROR INSERTING INTO THE DB \.** * **ZTP161: ERROR DELETING FROM THE DB (DLET).** * **ZTP162: ERROR UPDATING THE DB (REPL).** * ZTP163: ERROR READING THE DB (GN/GHN). > Errors returned by IMS. Analyze the codes that accompany the messages. The most frequent is ZTP230 for specifying an incorrect TRANSAC. associated with the procedures, TERM.OPER or LOCAL TERMINAL in the session profile. * **ZTP164: INCORRECT LOG MESSAGE CODE** > Only if the Editran/E module is installed. The manager of that module has received a log message it does not recognize. * **ZTP165: INCORRECT DATA IN THE DB** > Only if the Editran/E module is installed. One of the states of the transmissions or presentations in the corresponding databases is not correct. * **ZTP166: TRANSMISSION START WITHOUT END OF POST-PROCESS** > Only if the Editran/E module is installed. A transmission has been started without receiving the completion message for the post-process of the previous transmission. * **ZTP167: RELEASES CIRCUIT ESTABLISHED BY INCOMING CALL** > A call arrives from the remote side for a session that appears locally as connected. The previous connection is considered released and the new call is accepted. * **ZTP168: INCOMPATIBLE REMOTE FILE (APP.CONFIR.ID).** > An emission request has been made through Editran/MQ and the receiving buffer is not synchronized with the sending buffer (the identifier of the last exchanged message is not the same). * ZTP169: PROCESS INTERRUPTED BY USER EXIT. RESULT. > Shows the result code returned by the user exit if it is nonzero. * **ZTP170: ERROR IN CALL TO THE EZASOKET INTERFACE-.** > Generic error message in a call to the TCP/IP access interface, EZASOCKET. It will show in each case the function requested and the return code. * **ZTP171: ERROR IN CALL TO THE CONVERSION PROGRAM: ...** > Message shown when an error occurs calling IBM's EZACIC06 and EZACIC08 modules of the TCP/IP interface. * **ZTP172: UNKNOWN REMOTE TCP/IP ADDRESS OR NAME.** > The TCP/IP connection manager cannot find the remote address associated with the name specified in the profiles. > > Action: Verify the remote IP address. If the address is a name, check that your name server (DNS) is active and accessible from your TCP region (TCPIP:DATA file). * **ZTP173: ERROR SENDING TCP/IP CONNECTION DATA.** > The TCP/IP connection manager cannot send the connection data to the remote during the establishment of a local or remote call. > > Action: Check that the remote IP address and port specified in Profiles are correct and that the remote Editran is running on this port. If the problem persists, increase the WAIT INTERVAL (TCPIP) in the Profiles Environment. * **ZTP174: INCORRECT CONNECTION TYPE.** > The network management module has received an operator request for a session with a connection type that this module does not handle. * **ZTP175: TCP/IP CLIENT-SERVER RESTART.** > Indicates the moment when the client-server process was started. * **ZTP176: ERROR IN SOCKET HANDLING.** > An error occurred while handling a socket, indicating that it had been released (TCP/IP interface). * **ZTP177: ERROR RECEIVING TCP/IP CONNECTION DATA.** > The TCP/IP connection manager cannot receive the connection data during the establishment of a local or remote call. Similar to ZTP249. * **ZTP178: ERROR VALIDATING TCP/IP CONNECTION DATA.** > During the establishment of a local call, the TCP/IP connection manager receives the connection data from the remote side, but these do not match those sent to it. * **ZTP179: INCORRECT INPUT DATA:** > The client module ZTBPOCEF, associated with the external certificate server, receives an incorrect communication area. * **ZTP180: TIME EXCEEDED ON EXTERNAL SERVER** > The client module, ZTBPOCEF, cannot make a request within the time limit specified in Profiles. > > Action: Verify the server status and the TCP/IP connection status. If everything is correct, increase the PROXY WAIT TIME in the Profiles Environment. * **ZTP181: DEFERRED TRANSMISSION OUTSIDE SCHEDULE.** * **ZTP182: DEFERRED RECEPTION OUTSIDE SCHEDULE.** > A local send or receive request is received, from the operator or the application, outside the transmission time window (START TIME, END TIME) with AUTOMATIC SEND enabled, and it is stored in Profiles. When the start time is reached, the T/O module will automatically generate a send/receive request. The generated automatic request will be accompanied by message ZTP273-4. * **ZTP183: RETRY OF DEFERRED TRANSMISSION DUE TO SCHEDULE.** * **ZTP184: RETRY OF DEFERRED RECEPTION DUE TO SCHEDULE.** > An off-schedule transmission occurred (accompanied by message ZTP270-1) and the Time-out module requests send/receive automatically, once the transmission start time has been reached, through a transmission start message (A1R, A2R). * ZTP185: INCORRECT RECEIVER FILE. TOTAL RECORDS. > The remote sender offers us a transmission with a total number of records lower than those already received. It is understood to be a new transmission if the previous transmission was received in full, and if a pre-reception procedure is available, a reception preparation request will be executed to receive the new transmission. If the previous transmission did not finish completely, an exception procedure (A7I) will be generated and the transmission will be interrupted. > > Action: If the previous procedure is not executed, we must initialize reception. > > This message is similar to ZTP055. * **ZTP186: INCORRECT RECEIVER FILE. CREATION DATE.** > When our reception is restarted, it is detected that the remote sender file has been loaded again after we had already received part of the transmission. To avoid mixing the two transmissions, the exception procedure is generated and reception is interrupted. > > Action: The first transmission cannot be completed unless it is loaded again by the remote side and we exceptionally initialize reception. If we want to discard the first transmission and receive the second, it is enough to reinitialize reception. * **ZTP187: EDI VERSION IGNORED BY DATE CONTROL.** > An association request is received that was generated on a date much earlier than the current one. The request may belong to a previous session, or the remote clock may not match ours. The message is ignored > > Action: If the association does not occur, check the remote date and time. * **ZTP188: SESSION NOT ESTABLISHED. TRANSMISSION DEFERRED.** * **ZTP189: SESSION NOT ESTABLISHED. RECEPTION DEFERRED.** > A send or receive request is received as a consequence of the completion of a previous procedure (A1R/A2R), when the previous session is ending (abort was requested or SAB is being awaited). To prevent the request from being rejected by the remote side, it is stored in Profiles. The T/O module will automatically start the transmission after two time-out intervals and message ZTP283-4 will be displayed. * **ZTP190: RETRY OF TRANSMISSION DUE TO SESSION NOT ESTABLISHED** * **ZTP191: RETRY OF RECEPTION DUE TO SESSION NOT ESTABLISHED** > A previous send or receive request was received when the session was aborting (accompanied by message ZTP281-2) and the T/O module requests the send/receive, via A1R/A2R, after two T/O intervals have elapsed. * **ZTP192: TRANSMISSION INITIALIZATION** * **ZTP193: RECEPTION INITIALIZATION** > A request for application end of transmission or reception was received as a consequence of a state initialization. * **ZTP194: LOCAL OPERATOR TRANSMISSION REQUEST** * **ZTP195: REMOTE OPERATOR TRANSMISSION REQUEST** * **ZTP196: LOCAL OPERATOR RECEPTION REQUEST** > A send/receive request was received from our operator or from the remote side. * **ZTP197: SESSION NOT ESTABLISHED BY THE REMOTE ENTITY** > After a remote call, the time-out intervals and retries are exhausted without the remote session establishment message being received. Similar to message ZTB145, but the initiative belongs to the remote side. > > Action: Check that the local and remote communication resources are available and that there is no message queueing. Verify that there are no network errors and that routes and security rules are up to date. Make sure that unexpected application errors do not occur (abend, CRC error, incident messages, etc.) at either end. If the session uses cryptography, verify that the time-out intervals are adequate (TIME-OUT (MSS) and NUM. MAX. RETRIES). * **ZTP198: REMOTE CALL REJECTED. UNKNOWN IP ADDRESS** > The incoming connection request is closed because the remote IP address recorded in the session does not match the IP address used by the remote side. For this verification to occur, the session parameter 'VALIDATE IP ADDRESS' must be active. If IP addresses in dot format (127.22...) are recorded in the session, the check is performed against the address obtained in the macro for accepting the incoming connection (ACCEPT macro). If IP addresses with names ([www](http://www)...) are recorded, the address from the acceptance macro is transformed into a name with the macro (GETHOSTBYADDR) and the HOSTNAME obtained will be compared with the profile name. In this case, validation will use the shorter of the two lengths. > > Action: Check with the remote side the address it will use. Disable the session parameter 'VALIDATE IP ADDRESS' because IP addresses can be translated or spoofed. * **ZTP199: UNKNOWN Editran PROXY NAME.** > The TCP/IP connection manager cannot find the IP address associated with the Proxy name. Editran (Editran/PX) specified in profiles. Similar to ZTP248. > > Action: Check the Editran Proxy in the Local Environment. If the address is a name, check that your name server (DNS) is active and accessible from your TCP region (TCPIP.DATA file). * **ZTP200: PROXY RELEASE.** > The socket closure has occurred for a TCP/IP transmission using Editran Proxy, and the release is originated by the Proxy. It must be accompanied by the Cause and Diagnosis of the release and by the 'errno' and 'retcode'. Similar to ZTP014 for TCP connections. * **ZTP208: ATTEMPT TO CHANGE TO HIGHER VERSION IGNORED** > The remote Editran has a higher version than the local one. * **ZTP209: ERROR MODIFYING THE TRANSMISSION SESSION** > An error occurred while modifying the Editran session to update the version * **ZTP210: NO TRANSPORT SESSION EXISTS** > There is no session in the transport database. * **ZTP211: ERROR IN TRANSPARENCY CALCULATION** > An error occurred while calculating transparency. * **ZTP212: MONITORING** > This message is shown when an IP line is monitored. * **ZTP213: INACTIVE SESSION RELEASE** > A session that has been inactive for more than one hour is released. * **ZTP214: SENDING BUFFER CANNOT BE SET** > No buffer space available for sending. * **ZTP215: RECEIVING BUFFER CANNOT BE SET** > No buffer space available for reception. * **ZTP216: BUFFER FILE ALREADY SENT** > In the previous transmission we sent the buffer correctly, but the end-of-transmission message was lost and we have no record that the receiver downloaded the file. In this situation, the sender file has all records sent and confirmed, but it does not have the complete-transmitted mark, while the receiver file has already been prepared for the new transmission and has no received records. This mechanism prevents receiving the same file twice. > > Action: We must load a new file. * **ZTP217: BUFFER FILE ALREADY RECEIVED** > Similar to ZTP216 but referring to the receiving end. > > In the previous transmission we received the buffer correctly, but the sender did not receive our confirmation message and has no record that we processed the file. The remote sender file has all records sent and confirmed, but it does not have the complete-transmitted mark, while the receiver file has already been prepared for the new transmission and has no received records. * **ZTP218: REMOTE DOWNLOAD COMPLETED R:XX.** > The remote end reports the state of the download of the files it has just received. The Editran presentation session has the download confirmation facility enabled. > > The download result can be > > * 00 The download process completed successfully > * 01 The download process was not requested because the transmission has not yet finished or the transmission has finished but the process is waiting to be executed. > * 11 The process started, but has not yet finished. > * 91 An error occurred during the download, leaving the remote presentation in received state. > * 92 An error occurred during the download and the remote side unconditionally modified the presentation state. > * 93 An error occurred during the download and the remote presentation is interrupted. > * 99 An error occurred during the download, leaving the presentation in any other state. * **ZTP219: LOCAL DOWNLOAD COMPLETED R:XX** > Similar to ZTP317 for the local end. We communicate to the remote side the result of the download of the files we have just received. The Editran presentation session has the download confirmation facility enabled. > > The result XX will have the same meaning as in message ZTP316. * **ZTP220: EXCESS OF REMOTE CONFIRMATION RETRIES** > Similar to ZTP046 regarding a download confirmation request. > > The error occurs when requesting confirmation of the download on the remote side of the files we have sent. > > If confirmation is REMOTE, it occurs when trying to communicate to the remote side the result of the download of the files we have received. > > Action: In addition to checking the status of the communication resources, verify that the Editran Download Confirmation facility is enabled at both ends. * **ZTP221: DOWNLOAD CONFIRMATION PROCESS REQUESTED** > A download confirmation request has been received from the remote side, asking how the download of the files we have just received went, and a process is executed to verify it. This process is executed when our post-reception process did not communicate the result of the download, either because it did not finish or because it was not executed. If it had finished correctly, the result would have been stored and the process launch would not be necessary. The Editran presentation session has the download confirmation facility enabled. * **ZTP222: NO CLIENT-SERVER STARTED** > When a connection is required, the core transaction detects that there is no TCP/IP client/server that is operational. The connection is abandoned. > > Detection is performed by issuing a /DIS TRAN command for the transactions defined in the session as TCP/IP CLIENT SERVER. If it is detected that the number of regions in which the transaction is started is zero (RC field of the /DIS TRAN command), it is considered not operational. The core transaction will be authorized to issue the /DISPLAY TRAN command. If the transaction is not, it is considered that the client is started and this message will not be shown. > > Action: Check that the BMPs of the client servers defined for the session are started. If, even though the clients are started, the opposite is still detected incorrectly, disallow the core transaction of the session from issuing the /DISPLAY TRAN command and report it to Indra. * **ZTP223: CLIENT-SERVER NOT STARTED. DOES NOT SEND MSG.** > The core transaction detects that the TCP/IP client/server through which the transmission is taking place is not operational and cancels the sending of a datum. If the session is using tracing, the message is marked with the Direction field as Ignored. > > At the same time it will attempt to back up the transaction defined as TCP/IP CLIENT SERVER in the session. If it finds another operational client server, it will retry the connection through that one. If no operational client is found, it will abandon the connection. > > Detection is performed by issuing a /DIS TRAN command for the transaction defined in the session as TCP/IP CLIENT SERVER through which the transmission is being carried out. If it is detected that the number of regions in which the transaction is started is zero (RC field of the /DIS TRAN command), it is considered not operational. The core transaction will be authorized to issue the /DISPLAY TRAN command. If the transaction is not, it is considered that the client is started and this message will not be shown. > > Action: Check that the BMPs of the client servers defined for the session are started. If, even though the clients are started, the opposite is still detected incorrectly, disallow the core transaction of the session from issuing the /DISPLAY TRAN command and report it to Indra. * **ZTP226: EXCESS OF LOCAL CONFIRMATION RETRIES** > Similar to ZTP046 regarding a download confirmation request. > > The error occurs when trying to communicate to the remote side the result of the download of the files we have received. > > Action: In addition to checking the status of the communication resources, verify that the Editran Download Confirmation facility is enabled at both ends. * **ZTP227: LICENSE ERROR.XXXXXXXXXXXXXXXXXX ?** > License error. The text X..X describes the type of error. AA indicates a DL/I return code. NNN-NNN is the return code and reason of the license management module. > > It may indicate that a license for a local environment or an Editran facility has expired or will expire in the next few days. It may also indicate that an Editran product has not been contracted. > > Action: Review the license in option 2.6 of the operator menu. Verify the products you have contracted for that environment code. > > If the problem persists, contact Indra. *** --- # 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/configuracion_local.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.