> 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/utilities-and-codes/appendix-a.-editran-messages-to-the-operator-and-log.md).
# Appendix A. Editran messages to the operator and LOG
These messages appear on the OPERATOR TERMINAL (and are always recorded in the log file) of each editran session, as a consequence of events in transmissions.
Below, these messages are detailed in numerical order, together with their explanation or the advised action to take.
* ZTP0005: PROCESS ERROR IN THE PROGRAM: XXXXXXXX
* ZTP0010: REJECTED CALL ACCEPTANCE
> The interface rejects the remote call acceptance packet.
* ZTP0020: STARTUP NOT CONTEMPLATED IN CORE
> Transaction startup outside protocol.
* ZTP0025: NETWORK FAILURE
> Network failure message received.
* ZTP0030: CHANNEL NOT FOUND. CALL NOT MADE
> An information report (NPSI-DATE) has been received with diagnosis to retry the call, but it cannot be made because no channel was found.
* ZTP0035: UNCONTROLLED INFORMATION REPORT CAUSE
> An information report (NPSI-DATE) has come in with unknown diagnostic code(s).
* ZTP0040: START OF TRANSMISSION
> Transmission to the remote side begins.
* ZTP0045: CONNECTION NOT MADE
> In NPSI-PCNE or point-to-point connections, the terminal cannot be activated.
* ZTP0047: INVALID CONNECTION TYPE
> Incoming call rejected because the session has a connection type in profiles that does not match the interface of the incoming call.
* ZTP0055: CONNECTION MADE
> A connection request, both local and remote, has been accepted.
* ZTP0080: STATUS QUERY
> Obsolete message.
* ZTP0085: QUERY OF REMOTE SENDER FILE
> The control record of the remote transmission buffer has been queried (File Query option 1). It is required to be in session with the remote side and to have a terminal set to TERM. OPER. in the Session Profile.
* ZTP0090: QUERY OF REMOTE RECEIVER FILE
> Same as the previous one for the remote receiver buffer.
* ZTP0092: TOTALS MISMATCH IN SENDER PROCESS
> Obsolete message.
* ZTP0095: TOTALS MISMATCH IN RECEIVER PROCESS
> Obsolete message.
* ZTP0097: CORRECT CTCP
> An error-information report (NPSI-DATE) message has come in. editran may fix the problem. Otherwise, refer to the message.
* ZTP0098: CORRECT CTCP OR X25 GENERATION
> An error-information report (NPSI-DATE) message has come in. editran may fix the problem. Otherwise, refer to the message.
* ZTP0100: REMOTE POINT-TO-POINT CONNECTION DETECTED
> In Point-to-Point or LU 6.2 connection types, as in NPSI/PCNE, a connection is detected upon an incoming message from the remote side.
* ZTP0103: PASSWORD EXISTS FOR DECRYPTION. TO DELETE IT, PRESS SPACES.
> The certificate included in profiles has a password and, if you want to remove it, you must leave the field blank.
* ZTP0105: TRANSMISSION RELEASE DETECTED
> The actual terminal has been deactivated in the middle of a transmission. Editran will try to connect to the affected session and restore the transmission.
* ZTP0110: CORRECT AND COMPLETED TRANSMISSION
> The transmission has been completed. The local side has sent the remote side the end-of-transmission message and it has replied affirmatively. The transmission is considered correctly finished.
* ZTP0115: CLEAR SENT BY INFORMATION REPORT
> An error-information report (NPSI-DATE) message has come in and, as a consequence, a release has been generated.
* ZTP0120: RESTART SENT BY INFORMATION REPORT
> An error-information report (NPSI-DATE) message has come in and a restart has been generated.
* ZTP0125: A5P ERROR WITH INCORRECT QUALIFIER
> Correct the A5P request type.
* ZTP0128: CERTIFICATE WITH PASSWORD FOR SIGNING. TO DELETE IT, PRESS SPACES.
> The certificate included in profiles has a password and, if you want to remove it, you must leave the field blank.
* ZTP0130: ERROR OPENING FILE XXXXXXXX
> The file cannot be opened in CICS. It may not have been defined to VSAM. Check the CICS log for the error being reported.
* ZTP0135: ERROR CLOSING FILE XXXXXXXX
> The file cannot be closed in CICS. Check the CICS log for the error being reported.
* ZTP0140: INCOMPATIBLE KEYS ERROR. (ERRX)
> Key authentication error. The local operational key does not match the remote one. See appendix D.
* ZTP0145: ERROR ALLOCATING FILE XXXXXXXX
> The file cannot be released to hand control over to CICS. Check that it is not assigned to another job, or that it has been correctly defined to VSAM.
* ZTP0150: CRC CALCULATION ERROR IN SENDER PROCESS
> Before sending a message to the remote side, there is a local error in calculating its CRC. The message is ignored.
* ZTP0153: DATA LENGTH TO BE SENT EXCEEDS 4096 BYTES.
* ZTP0155: CRC CALCULATION ERROR IN RECEIVED MESSAGE
> When receiving a message from the remote side, there is a local error in calculating its CRC.
* ZTP0160: RESID ERROR (ACCEPTED CALL) XXXX
> When a call is made (NPSI/DATE or GATE) and the call acceptance packet arrives, it is detected that the cvc through which it comes in is not within the range of cvcs in profiles.
* ZTP0161: RESID ERROR (REMOTE CALL) XXXX
> When a call arrives (NPSI/DATE or GATE), the circuit through which it comes in is not within the range of cvcs in profiles.
* ZTP0162: TERMID ERROR (ACCEPTED CALL) XXXX
> When a call is made (NPSI/DATE or GATE) and the call acceptance packet arrives, the terminal that is calculated is not defined.
* ZTP0163: TERMID ERROR (REMOTE CALL) XXXX
> When a call arrives (NPSI/DATE or GATE), the terminal that is calculated is not defined.
* ZTP0165: ERROR IN DEALLOCATION OF FILE XXXXXXXX
> The file cannot be released from CICS to hand control over to batch jobs. Check that it is not assigned to another job, or that it has been correctly defined to VSAM.
* ZTP0167: ERROR IN EXECUTION OF BATCH PROC. XXXXXXXX
> The procedure ended abnormally; check the execution output.
* ZTP0170: ERROR IN REMOTE BATCH PROCESS
> An error occurred in some automatic batch process on the remote side, with the consequent release.
* ZTP0180: ERROR IN TERMID RANGE XXXX
> Check the first terminal defined in the session, as well as the definition of the terminals (netnames) (NPSI-DATE or GATE).
* ZTP0185: ERROR IN TRANSPARENCY IN RECEIVED MESSAGE
> When receiving a message in Public or Private PAD connection type, a local error occurs in calculating its transparency.
* ZTP0190: INFORMATION REPORT ERROR C: XX D: XX
> An error information report message has been received (NPSI-DATE or GATE).
* ZTP0192: APPLICATION INTERFACE ERROR: RET CODE=??
> A return code is received from the communications interface with an untranslated code.
* ZTP0194: APP. DATA INCOMPATIBLE WITH STREAM COMPRESSION
> A batch compression (LZW compressor) has been performed and stream compression (online compression) is being attempted; this option is not compatible.
* ZTP0195: LOCAL ERROR IN COMPRESSION/DECOMPRESSION: X
> A local compression-decompression error occurs.
* ZTP0197: LOCAL CRYPTOGRAPHY ERROR: XXXX – XXXX (ERRX)
> An error occurred in the encryption process; check the result codes in Appendix D.
* ZTP0200: REMOTE CRYPTOGRAPHY ERROR (ERRx)
> A remote cryptography error has been detected. See ERRx in Appendix D.
* ZTP0205: REMOTE ERROR IN COMPRESSION/DECOMPRESSION
> The remote side had an error when compressing/decompressing data, with the consequent release of the circuit.
* ZTP0210: ERROR WITHOUT JOB OR FILE IN PROFILES
> Review the corresponding screen in the editran session profile.
* ZTP0215: EXCESS OF TRANSMISSION BLOCK RETRIES
> The sender, after sending the number of records specified in the Session Profile's NUM.REG. SINCRONISMO, sends a synchronization message to the receiver and, if no response is received, retries as many times and at the interval specified in the session profile, again without receiving a response. A possible cause would be that the sender has a very high number of synchronization records in relation to the line speed, in which case coherent values should be set in the Session Profile's NUM.REG. SINCRONISMO, TIME-OUT and MAX. REINTENTOS.
* ZTP0220: EXCESS OF CONNECTION RETRIES
> All connection retries have been exhausted, according to the number of retries in the editran session profiles, for each Local NRI – Remote NRI combination, without achieving the connection. Consult the possible releases produced in Appendix C.
* ZTP0225: EXCESS OF END-OF-BURST RETRIES
> All synchronization retries have been exhausted, according to the number of retries in the editran session profiles.
* ZTP0230: EXCESS OF RETRIES IN THE SENDER PROCESS
> All retries with duplicates in the sender process of messages that require a response have been exhausted.
* ZTP0235: EXCESS OF RETRIES IN THE RECEIVER PROCESS
> All retries with duplicates in the receiver process of messages that require a response have been exhausted.
* ZTP0245. EXCESS OF RETRIES TO ESTABLISH SESSION
> All retries of parameter notification for session establishment have been exhausted without receiving a response from the remote side.
* ZTP0246: EXCESS OF SAP WAIT RETRIES.
> All SAP wait retries have been exhausted without the remote side having sent that message and the session having been established. It is released to avoid leaving the cvc-socket connected.
* ZTP0250: EXCESS OF RETRIES FOR END OF TRANSMISSION
> When there is a request to end transmission, the retries waiting for a response are exhausted.
* ZTP0260: INVALID CALLING END PROFILE C: XX D: XX
> Incompatibility in the values of that field in the profiles record.
* ZTP0265: TRANSMISSION FILE NOT READY
> The control record information exchanged between the two ends, in the transmission start request/response message, does not allow data exchange to begin. The transmission/receipt file is not loaded, or is not available to editran (the batch process specified in profiles is triggered).
* ZTP0270: FILE CLOSED XXXXXXXX
> Obsolete message.
* ZTP0272: FILE WITHOUT SPACE XXXXXXXX
> While receiving data from the remote side, the buffer file has filled up. Define the VSAM file again with a larger number of records and make the request again.
* ZTP0275: FILE NOT CREATED XXXXXXXX
> Obsolete message.
* ZTP0280: RECEIPT FILE NOT READY
> The control record information exchanged between the two ends, in the transmission start request/response message, does not allow data exchange to begin. The transmission/receipt file is not loaded, or is not available to editran (the batch process specified in profiles is triggered).
* ZTP0282: RECEIPT FILE INCOMPATIBLE (TOTAL RECORDS-CREATION DATE)
> The total number of records in the local receipt buffer file differs from that in the remote transmission file. It can also happen with the same number of records. In all cases, it is because the receiver already had part of the file received, the transmission was released, and the sender reloaded it again (with the same or different content), so the receiver detects it through the creation date of its receipt buffer. Since the receiver does not know whether the content changed between one load and another, it rejects it. The way out is to initialize the receipt and start again from the beginning. The creation date of the receipt buffer is updated with that of the sender buffer only at the first start of the first transmission (when it still has no confirmed records).
* ZTP0283: RECEIPT FILE NOT READY (APP. CONFIR. ID)
> The application identifier of the receipt buffer file does not match that of the receipt start message and application synchronization 'Q' has been specified in profiles.
* ZTP0285: INCORRECT FILE XXXXXXXX
> Obsolete message.
* ZTP0290: REMOTE SENDER BUFFER IN INCOMPATIBLE STATE
> An attempt is made to receive a buffer with a total number of records less than the number registered in the buffer. There may have been an incomplete previous transmission and the sender reloaded a smaller file and the receiver did not initialize the receipt. The receiver must initialize its receipt buffer.
* ZTP0293: REMOTE RECEIVER BUFFER IN INCOMPATIBLE STATE
> Similar message to the previous one.
* ZTP0295: TRANSMISSION BUFFER FILE CLOSED
> This message does not appear in the Log, but the remote side can receive it when querying the local sender buffer if it is not loaded.
* ZTP0300: RECEIPT BUFFER FILE WITHOUT SPACE
> While receiving data from the remote side, the buffer file has filled up. Define the VSAM file again with a larger number of records and make the request again.
* ZTP0310: RECEIPT BUFFER FILE CLOSED
> Similar to message ZTP0295.
* ZTP0320: END OF TRANSMISSION REQUESTED BY REMOTE OPERATOR
> The remote side has requested the end of the transmission before it was completed.
* ZTP0325: END OF TRANSMISSION REQUESTED BY LOCAL APPLICATION INTERFACE
> When the Local interface requests forced end of transmission.
* ZTP0330: END OF TRANSMISSION REQUESTED BY LOCAL OPERATOR
> The local side has requested the end of the transmission before it was completed.
* ZTP0335: END OF RECEIPT REQUESTED BY REMOTE OPERATOR
> Similar to the previous one.
* ZTP0340: END OF RECEIPT REQUESTED BY LOCAL APP INTERFACE
> When the Local interface requests forced end of receipt.
* ZTP0345: END OF RECEIPT REQUESTED BY LOCAL OPERATOR
> Similar to message ZTP0330.
* ZTP0350: INTERRUPT CONFIRMATION INDICATION
> Response to an interruption request made by editran (NPSI-DATE or GATE).
* ZTP0355: RESET CONFIRMATION INDICATION
> Response to a Reset request made by editran (NPSI-DATE or GATE).
* ZTP0360: RESTART CONFIRMATION INDICATION
> Response to a Restart request made by editran (NPSI-DATE).
* ZTP0365: DIAGNOSIS INDICATION C: XX D: XX
> Incoming diagnostic message to editran (NPSI-DATE or GATE).
* ZTP0370: INTERRUPT INDICATION
> Incoming interruption message to editran (NPSI-DATE or GATE).
* ZTP0375: RESET INDICATION C: XX D: XX
> Incoming Reset message to editran (NPSI-DATE or GATE).
* ZTP0380: RELEASE INDICATION C: XX D: XX
> Release message for a circuit.
* ZTP0385: RESTART INDICATION C: XX D: XX
> Incoming Restart message to editran (NPSI-DATE).
* ZTP0390: START OF RECEIPT
> When receipt of the remote file begins.
* ZTP0392: APPLICATION INTERFACE DENIES BATCH REQUEST
> Editran/G rejects the request made because it is in a situation incompatible with the request.
* ZTP0395: COMMUNICATIONS INTERFACE NOT CONTEMPLATED
> A message is received that does not conform to the communications interface defined in the local environment.
* ZTP0400: INTERFACE DOES NOT REQUIRE RESTART
> A Restart request message is received from the operator, not necessary for environments with certain communications interfaces.
* ZTP0405: IMPOSSIBILITY OF TRANSMISSION: REMOTE PROFILE
> Transmission is not allowed due to the TRAFFIC DIRECTION of the session profile.
* ZTP0410: IMPOSSIBILITY OF RECEIPT: REMOTE PROFILE
> Similar to the previous one.
* ZTP0413: IMPOSSIBILITY OF TRANSMISSION: OUTSIDE SCHEDULE
> An attempt is made to carry out a transmission having a time window in profiles and being outside that schedule.
* ZTP0420: THE REMOTE FICTIONAL LU IS IN REL C: XX D: XX
> A release C:00 D:43 is received, which may be from the remote ISARD X.25 because the fictional LU is in Rel. It may be received from other environments, in which case the interpretation made of the release is meaningless. It is usually a remote system problem, not an editran/P one, related to some difficulty in redirecting the call to the application.
* ZTP0425: RELEASE OF CNID. C: XX D: =XX
> A call that did not reach the connected state has been released (NPSI-DATE or GATE).
* ZTP0435: RELEASE BY REMOTE OPERATOR
> The remote operator has requested the release.
* ZTP0440: RELEASE DUE TO CALL CROSSING C: XX D: XX
> When a call crossing occurs between the local and the remote side, editran/P with lower local code releases with C:00 D:04. In this case it is the local side that has released. It is assumed that the remote call proceeds.
* ZTP0445: RELEASE BY THE OPERATOR C: XX D: XX
> A release C:00 D:08 has been received, possibly originating from a remote editran/P due to a request from the corresponding operator.
* ZTP0450: NOT USED.
> Not used. In previous versions (editran < 2.1) it meant release due to compression error.
* ZTP0455: RELEASE BECAUSE A CHANNEL ALREADY EXISTS C: XX D: XX
> A call is released with C:00 D:05 because a circuit already exists for the session. The most likely cause is that local editran/P has the session recorded as connected even though the remote side does not know it.
* ZTP0460: INVALID FACILITIES RELEASE C: XX D: XX
> A release with C:00 D:0A has occurred due to invalid facilities in the call packet. Analyze the call packet.
* ZTP0465: RELEASE DUE TO INCORRECT SCHEDULE C: XX D: XX
> A release with C:00 D:0C has occurred because the call was made outside the time interval specified in the session profile.
* ZTP0470: UNACCEPTED REVERSED CHARGE C: XX D: XX
> A release with C:00 D:06 has occurred because it came with collect-call facility and the session has COLLECT CALL = N.
* ZTP0475: RELEASE DUE TO NO FREE CHANNELS C: XX D: XX
> Circuit limitation: the connection can be established once another established session is released, or the maximum number of cvcs in the local environment can be modified.
* ZTP0480: RELEASE DUE TO NETWORK RESTART C: XX D: XX
> Local or remote release C:00 D:09 due to network restart.
* ZTP0485: INVALID PAYMENT METHOD RELEASE C:XX D:XX
> A release with C:00 D:07 occurs because the PAYMENT TYPE of the session profile does not match what is indicated in the call packet. Specifically, it occurs when Payment Type = L and the remote call is not collect call, or when Payment Type = R and the call is collect call.
* ZTP0490: TRANSMISSION RELEASE C: XX D: XX
> A circuit release has occurred that is not translated into a specific message. It must come with the release Cause and Diagnosis. For more information see Appendix C.
* ZTP0495: LOCAL CANNOT TRANSMIT (PROFILES)
> Transmission request rejected because the parameter 'traffic-direction' is not specified with value 'E' or 'X'.
* ZTP0500: LOCAL CANNOT CALL (PROFILES)
> Connection request rejected because the parameter 'calling-end = R' is specified, so only the remote side can call.
* ZTP0501: LOCAL CANNOT CALL (SESSION NOT ENABLED)
> Connection request rejected because the parameter SESSION ENABLED = 'N' is specified in the session profile.
* ZTP0505: LOCAL CANNOT RECEIVE (PROFILES)
> Check the 'traffic direction' parameter.
* ZTP0507: CALL WITH FACILITIES NOT CONTEMPLATED
> A call is received with facilities not contemplated by the transport protocol.
* ZTP0510: REMOTE CALL REJECTED (OUTSIDE SCHEDULE)
> Connection request outside schedule. Check profiles.
* ZTP0513: WITH VERSION 5.2 THE TRANSMISSION LENGTH MUST BE 4050.
> Transmission length 4050 is only allowed starting with editran version 5.2.
* ZTP0515: REMOTE CALL REJECTED (LOCAL-REMOTE NRI, FICTITIOUS LUs, TC)
> The incoming remote call is rejected with C:00 D.0D because the following parameters do not match between the incoming call packet and the session profiles: the lengths of the NRIs (called-calling), the NRIs (called-calling), the fictitious LU or the terminal code. Check the parameters described with the remote side and in the session.
* ZTP0517: REMOTE CALL REJECTED (INVALID NRIs)
> Similar to the previous message.
* ZTP0520: REMOTE CALL ACCEPTED
> The remote call has passed all checks for session profile existence, local and remote NRI's, and other connection parameters. A confirmation is sent to the remote side.
* ZTP0521: CONFIDENTIALITY ALGORITHM IN 2.2 MUST BE SPACES OR DES
> In cryptographic version 2.2, the confidentiality algorithm can only take the values DES or Spaces.
* ZTP0525: REMOTE CALL ACCEPTED (CROSSING)
> Both ends have requested the connection establishment and the remote one was handled first.
* ZTP0530: PREVIOUS REMOTE CALL
> Both ends have requested the connection establishment and the remote one was handled first.
* ZTP0540: REMOTE CALL REJECTED (COLLECT CALL)
> The remote call is rejected with C:00 D.06 because it comes with collect-call facility and the session has COLLECT CALL = N.
* ZTP0541: CONFID. ALG. CAN BE DES TD2C TD3C AES AES2 AES3 OR SPACES
* ZTP0542: AUTH. ALG. CAN BE DES OR RSA FOR V3.0 AND RSA FOR V4.0
* ZTP0543: WITH SEPARATE SIGNATURE (D), YOU MUST SPECIFY A DIRECTORY
> For the DETTACHED signature type, the file name or directory field for signature files must be filled in.
* ZTP0545: REMOTE CALL REJECTED (CROSSING)
> When a call crossing occurs between the local and the remote side, editran/P with the lower local code releases with C:00 D:04. In this case it is the local side that has released. It is assumed that the remote call proceeds.
* ZTP0550: REMOTE CALL REJECTED (CALLING END)
> The remote call is rejected with C:00 D:0E because CALLING END = L (Local) in the session profile.
* ZTP0551: REMOTE CALL REJECTED (SESSION NOT ENABLED)
> The remote call is rejected with C:00 D:0D because SESSION ENABLED = 'N' in the session profile.
* ZTP0555: REMOTE CALL REJECTED (SESSION/UNKNOWN PARAMETERS)
> The incoming call from the remote side is rejected because the session is not defined on the local side. It may also be due to a mismatch in the editran/P version, the connection type, or the access identifier in the local and remote session profiles. The remote side receives a release with Cause 00 and Diagnosis 0D.
* ZTP0560: REMOTE CALL REJECTED (NO CHANNEL)
> The remote call is rejected because it exceeds the maximum number of cvcs reflected in the local environment.
* ZTP0565: REMOTE CALL REJECTED (PAYMENT METHOD)
> The remote call is rejected with C:00 D:07 because the PAYMENT METHOD in the session profile does not match what is indicated in the call packet. Specifically, it occurs when Payment Method = L (local) and the remote call is not collect call, or when Payment Method = R (Remote) and the call is collect call.
* ZTP0570: REMOTE CALL REJECTED (ALREADY THERE IS A CVC)
> A remote call is released with C:00 D:05 because a circuit already exists for the session. The most likely cause is that local editran/P has the session recorded as connected even though the remote side does not know it. The local side must request the release with option 3 of the editran/P Operator.
* ZTP0575: INCORRECT NPSI/DATE MESSAGE
> An unknown message (NPSI-DATE) has been received.
* ZTP0580: INCORRECT NOTIFICATION MESSAGE
> A notification message has been received that is outside specifications.
* ZTP0585: RECEIVED MESSAGE WITH INVALID CRC
> A message has been received from the remote side and, when calculating its CRC, it does not match the one contained in the message itself. This is an integrity problem in the received message. It should be very infrequent, since otherwise there may be malfunction in some of the communications equipment, line configurations unsuitable to their characteristics, etc. It may require line traces at both ends for diagnosis.
* ZTP0590: NO CONNECTION
> A request has been made that required connection establishment beforehand.
* ZTP0595: NO PROCEDURE EXISTS IN PROFILES
> An application has requested editran/P to launch a process before/after transmission/reception, and the corresponding procedure does not exist in the session profile.
* ZTP0605: NO SESSION EXISTS IN PROFILES
> A session request has been made to editran/P and it is not defined in profiles.
* ZTP0607: DOES NOT CALL. FICTIONAL LU XXXX IN REL
> An attempt is made to make a call and the fictional LU is in REL; activation is attempted and, after exhausting the retries, it still is not activated. Check the X.25 line.
* ZTP0610: NOT TRANSMITTING
> While connected, a local request is received from the end-of-transmission interface.
* ZTP0612: NOT RECEIVING
> While connected, a local request is received from the end-of-receipt interface.
* ZTP0620: NO FREE CHANNELS (MAX. CVC NO. EXHAUSTED)
> There are already as many sessions managed by editran/P as specified in MAXIMUM CVC NO. in the profile of the Main Local Environment, so another connection request is not accepted.
* ZTP0625: BATCH NOTIFICATION: SENDER BUFFER READY
> The application interface notifies the core that data has been loaded into the transmission buffer file and it is available for local or remote editran/P.
* ZTP0627: BATCH NOTIFICATION: RECEIVER BUFFER READY
> The application interface notifies the core that the receipt buffer file has been initialized and it is available for editran/P.
* ZTP0630: INCOMPATIBLE EXCHANGE SESSION NUMBER
> The Exchange Session Number of the receiver and sender buffer file for the Local and Remote sides do not match. They must match at both ends. Initialize the editran states by setting the correct exchange session number. Normally the receiver has to do it, since if the sender does it, the file must be loaded again. Request the receipt again.
* ZTP0635: OPERATOR MUST CHECK MCH
> An error-information report (NPSI-DATE) message has come in. editran may fix the problem. Otherwise, refer to the message.
* ZTP0645: SEQUENCE LOSS IN SENDER PROCESS
> A jump in the message sequence number has been detected. Possible invalid CRC problem.
* ZTP0650: SEQUENCE LOSS IN RECEIVER PROCESS
> A jump in the message sequence number has been detected. Possible invalid CRC problem.
* ZTP0655: INCOMPATIBLE PROFILES (COMPRESSION)
> The remote transmission request is rejected because the COMPRESSION parameter differs in the session profiles. This message should not occur because this parameter is checked beforehand during session establishment. It comes from earlier versions of editran/P.
* ZTP0660: INCOMPATIBLE PROFILES (TRAFFIC DIRECTION)
> The remote transmission request is rejected because the session profile's TRAFFIC DIRECTION does not allow it.
* ZTP0670: PROFILES WITHOUT LOCAL CHARACTERISTICS
> Create an environment record.
* ZTP0675: BATCH REQUEST TO UNLOAD TRANSMISSION
> A batch request has been received to launch the post-transmission process specified in profiles.
* ZTP0680: BATCH REQUEST TO UNLOAD RECEIPT
> A batch request has been received to launch the post-receipt process specified in profiles.
* ZTP0685: BATCH REQUEST FOR START OF TRANSMISSION
> A batch request has been received to begin local transmission.
* ZTP0690: BATCH REQUEST FOR START OF RECEIPT
> A batch request has been received to begin local receipt.
* ZTP0700: BATCH REQUEST FOR LOAD AND START OF TRANSMISSION
> A batch request has been received to launch a job specified in profiles.
* ZTP0705: BATCH REQUEST FOR TRANSMISSION LOAD
> A batch request has been received to launch a job specified in profiles.
* ZTP0710: BATCH REQUEST FOR PREP. AND START OF TRANSMISSION
> A batch request has been received to launch a job specified in profiles.
* ZTP0715: BATCH REQUEST FOR RECEIPT PREPARATION
> A batch request has been received to launch a job specified in profiles.
* ZTP0720: BATCH REQUEST FOR RECEIPT TO THE REMOTE SIDE
> A local request has been received to begin remote transmission.
* ZTP0735: POST-TRANSMISSION FINISHED CORRECTLY
> The interface reports that the post-transmission process requested from editran/P has finished.
* ZTP0740: POST-RECEPTION COMPLETED SUCCESSFULLY
> Similar to the previous one, referring to the post-reception process.
* ZTP0745: PRE-TRANSMISSION COMPLETED SUCCESSFULLY
> Similar to the previous one, referring to the pre-transmission process.
* ZTP0750: PRE-RECEPTION COMPLETED SUCCESSFULLY
> Similar to the previous one, referring to the pre-reception process.
* ZTP0752: PRE-PROCEDURE POSSIBLY RUNNING
> Without having received a response from the process launched by editran/P, a new request is made.
* ZTP0755: START OF SESSION. LOCAL TRANSMISSION
> The first burst of the transmission has been sent.
* ZTP0760: MAKES THE CALL
> The local editran/P makes a call to the remote as a result of a connection request from the operator (option 2) or of a transmission or reception request from the operator or interface when there is no connection and AUTOMATIC CONNECTION = S in the session profile.
* ZTP0765: MAKES CALL DUE TO INF. REPORT
> An error-information report message has been received in NPSI-DATE, with a diagnosis to retry the call.
* ZTP0770: REMOTE OPERATOR NETWORK RESTART
> A release request is received from the remote due to a restart of its network.
* ZTP0780: CORRECT AND COMPLETED RECEPTION
> When a transmit-receive operation is considered finished.
* ZTP0790: INCORRECT MESSAGE RECEIVED FROM BATCH
> Batch request out of protocol.
* ZTP0800: INCORRECT MESSAGE RECEIVED IN TRANSMISSION
> Message out of protocol.
* ZTP0805: INCORRECT MESSAGE RECEIVED IN RECEPTION
> Message out of protocol.
* ZTP0810: CIRCUIT RECOVERY
> In ISARD X.25, an FB network restart message has been received, which may have been caused by an operator request from editran/P with option 9, or it may be due to a dummy LU associated with a local line having been acquired (ACQ) by the CICS where editran/P runs. It may also be triggered by the first local connection request for a given dummy LU. Obsolete.
* ZTP0815: RETRY TO ESTABLISH SESSION
> A timeout to establish the session is detected and the remote is requested to do so.
* ZTP0816: SAP WAIT RETRY
> A timeout is detected while waiting for the remote to send us SAP. It is relaunched until retries are exhausted.
* ZTP0820: INCORRECT SESSION/PARAMETERS ON REMOTE C: XX D: XX
> A release C:00 D:0D is received; the most likely case is that remote editran/P rejects the local call because it cannot identify the session or due to NRI checking (see release diagnostics).
* ZTP0825: SBP RECEIVED IN INCORRECT STATE
> Message out of protocol.
* ZTP0835: REMOTE TOTALS MISMATCH RECEIVED
> Obsolete message. In a transmission of an application with totals control (T value in profiles), the remote has a mismatch in the sum of the amounts for that application.
* ZTP0840: TRANSMITTING. BATCH REQUEST IGNORED
> A batch transmission request has been received, which will not be processed because a transmission is in progress.
* ZTP0845: RECEIVING. BATCH REQUEST IGNORED
> A batch reception request has been received, which will not be processed because reception is in progress.
* ZTP0847: EXCEPTION BATCH LAUNCHED. REF: XXXX
> An exception process has been launched according to the profiles with a reference code.
* ZTP0850: POST-TRANSMISSION BATCH HAS BEEN LAUNCHED
> A batch process has been launched according to the profiles.
* ZTP0855: POST-RECEPTION BATCH HAS BEEN LAUNCHED
> A batch process has been launched according to the profiles.
* ZTP0860: PRE-TRANSMISSION BATCH HAS BEEN LAUNCHED
> A batch process has been launched according to the profiles.
* ZTP0865: PRE-RECEPTION BATCH HAS BEEN LAUNCHED
> A batch process has been launched according to the profiles.
* ZTP0870: USER EXIT ERROR. CGO.RESULTADO
> Process error in the user exit coded in profiles.
* ZTP0871: USER EXIT ERROR. PGMIDERR. EXIT: XXXXXXXX
> The user exit specified in profiles does not exist.
* ZTP0872: PROCESS INTERRUPTED BY USER EXIT. XXXXXXXX
> The user exit interferes with a process and does not allow editran to perform an action.
* ZTP0885: SEP RECEIVED IN INCORRECT STATE
> Message out of protocol.
* ZTP0895: SESSION ESTABLISHED
> Notification messages have been exchanged and both ends are in session.
* ZTP0900: SESSION NOT ESTABLISHED
> A request has been received from the remote or local operator without the session being established.
* ZTP0905: SESSION REJECTED BY PROFILES (ASCII/EBCDIC)
> Both ends do not agree on that parameter.
* ZTP0910: SESSION REJECTED BY PROFILES (CRC CALCULATION)
> Both ends do not agree on that parameter.
* ZTP0915: SESSION REJECTED BY PROFILES (SERVICE QUALITY)
> Both ends do not agree on that parameter.
* ZTP0920: SESSION REJECTED BY PROFILES (TOTALS CONTROL)
> Both ends do not agree on that parameter.
* ZTP0925: SESSION REJECTED BY PROFILES (COMPRESSION)
> Both ends do not agree on that parameter.
* ZTP0930: SESSION REJECTED BY PROFILES (CRYPTOGRAPHY)
> Both ends do not agree on that parameter.
* ZTP0935: SESSION REJECTED BY PROFILES (RECORD LENGTH)
> Both ends do not agree on that parameter.
* ZTP0940: SESSION REJECTED BY PROFILES (APPLICATION TYPE)
> Both ends do not agree on that parameter.
* ZTP0945: SESSION REJECTED BY PROFILES (CONNECTION TYPE)
> Both ends do not agree on that parameter.
* ZTP0950: SESSION REJECTED BY PROFILES (VERSION)
> Both ends do not agree on that parameter.
* ZTP0951: REMOTE EDI VERSION DIFFERENT. PROCESS CONTINUES
> Both ends do not agree on that parameter, but the process continues as if nothing had happened.
* ZTP0955: LOCAL KEY CHANGE REQUESTED
> During session establishment, the local end asks the remote to change its key.
* ZTP0960: REMOTE KEY CHANGE REQUESTED
> During session establishment, the remote end asks the local end to change its key.
* ZTP0965: RELEASE REQUESTED BY LOCAL OPERATOR
> The local operator has requested session release.
* ZTP0966: RELEASE REQUESTED DUE TO EXCESS TIME
> The session was idle. More than 1 hour has elapsed since the last event. It is released and, if it was transmitting, reconnected.
* ZTP0970: RESTART REQUEST C: XX D: XX
> Restart request by operator (ISA/X.25 and NPSI-DATE or GATE).
* ZTP0975: START TO WRONG TRANSACTION XXXX
> Review the transactions specified in the environment or in the application query request (wrong mailbox).
* ZTP0980: START TO UNAUTHORIZED TRANSACTION
> Transaction protected by the system.
* ZTP0985: REMOTE SENDER BUFFER FILE INACCESSIBLE
> Response to remote send file query.
* ZTP0990: REMOTE RECEIVER BUFFER FILE INACCESSIBLE
> Response to remote receive file query.
* ZTP0992: REMOTE FILE NOT READY (LAUNCH PREVIOUS)
> The remote rejects the local request because its buffer file is not prepared. Its corresponding previous automation has been launched for the request. If the remote allows it in the session profile, its editran/P will take the initiative when its sender buffer has been prepared; otherwise the local side must request reception again.
* ZTP0993: REMOTE FILE NOT READY (PREVIOUS DOES NOT EXIST)
> The remote does not have the file prepared and does not have automations specified (previous procedure in profiles)
* ZTP0994: REMOTE FILE NOT READY (NOT AVAILABLE)
> The remote buffer file is in a state unavailable to editran; the interface has it.
* ZTP0995: REMOTE FILE INCOMPATIBLE (SESSION NUMBER)
> The transmission is rejected because the exchange session number of the two buffers does not match. That number must be coordinated with the remote. The procedure to follow depends on the interface used. If it is editran, the most common case, the local side must initialize the reception state with the number indicated by the remote and initialize the receiver buffer.
* ZTP0996: REMOTE FILE INCOMPATIBLE (TOTAL RECORDS-CREATION DATE)
> The number of total records in the remote reception buffer file is different from that of the local transmission file. It can also occur with the same number of records. In all cases, this is because the receiver already had part of the file received, the transmission was released, and the sender loaded again (same or different content), so the receiver detects it through the creation date of its receiver buffer. Since the receiver does not know whether the content changed between one load and another, it rejects it. The way out is to notify the receiver so that it initializes reception and start again from the beginning. The creation date of the receiver buffer is updated with that of the sender buffer only at the first start of the first transmission (when it still has no confirmed record).
* ZTP0997: REMOTE FILE INCOMPATIBLE (APPLICATION CONFIR. ID)
> The remote receiver buffer file expects to receive the same application identifier that is simulated in the SCP, but it does not match and the remote end has application synchronization 'Q'.
* ZTP1000: INVALID NETWORK TERMINAL XXXX
> Review the terminal and IDNUM registered in profiles.
* ZTP1003: TERMINAL NOT ACQUIRED XXXX
> When sending a message to the remote, it is detected that the real LU has not been acquired by CICS. The status of that LU must be checked. In ISARD X.25, the LOCAL TERMINAL and IDNUM must be correct and match. In NPSI, the LUs of the switched major node must specify correct IDNUMs according to line generation, and the local line parameters in the session profile must be correct.
* ZTP1005: PRIVATE PAD CONNECTION TYPE CANNOT CALL
> A local connection request is received for a remote defined with PRIVATE PAD connection type.
* ZTP1007: PUBLIC PAD CONNECTION TYPE CANNOT CALL
> A local connection request is received for a remote defined with PUBLIC PAD connection type.
* ZTP1008: EDTX CONNECTION TYPE VIA PAD CANNOT CALL
> A local connection request is received for a remote defined with EDI/TX connection type with PUBLIC PAD.
* ZTP1010: STILL TRANSMITTING
> Request not processed because transmission is in progress.
* ZTP1020: TRANSPORT CONNECTION ALREADY EXISTS
> A session connection has been requested by the editran/P operator or by an interface and that session is already connected.
* ZTP1025: ALREADY RECEIVING
> Duplicate request received from the operator.
* ZTP1030: ALREADY TRANSMITTING
> Duplicate request received from the operator.
* ZTP1035: ALREADY CALLED BEFORE
> A connection request has been received when a previous one for the same session was already being processed.
* ZTP1040: BUFFER LOADED WITH LENGTH XXXX (<> PROFILES)
> The buffer file has been loaded with a length different from that specified in profiles. Reload the buffer or modify the transmission length in the session profile.
* ZTP1045: BUFFER WITH COMPRESSION (INCOMPATIBLE WITH PROFILES)
> The sender buffer file has already been loaded by batch with compression (LZW compressor) and line compression is specified in profiles. The two compressions are not compatible.
* ZTP1050: ENCRYPTED BUFFER INCOMPATIBLE WITH PROFILE: XXXXXXXX
* ZTP1055: NO KEY EXISTS THAT ENCRYPTED THE SENDER BUFFER
> While a batch data load with encryption is being performed, a key change is made.
* ZTP1060: KEY CHANGE INCOMPATIBLE WITH ENCRYPTED BUFFER
> A batch data load has been performed and encrypted. A key change is not allowed when batch encryption has been used.
* ZTP1065: TRANS. LENGTH INCOMPATIBLE WITH RECEIVER BUFFER
> An attempt is made to perform a transmission with a data length and the receiver expects another.
* ZTP1070: REAL LU DOWN. X25 GATE MESSAGE NOT SENT
> Cannot release because the real LU is out of service.
* ZTP1075: REAL LU DOWN. GATE DATA MESSAGE NOT SENT
> The real LU has not entered data traffic. Check with CEMT.
* ZTP1080: CVC ERROR NOT FOUND IN STATES QUEUE
> Message ignored because CVC was not found.
* ZTP1085: CONNECTED CIRCUIT. RELEASE IMPOSSIBILITY
> A release packet has not arrived and the local side cannot release because the real LU is not in ACQ.
* ZTP1090: CALL REJECTED. WRONG PACKET SIZE
> Packet size is not correct.
* ZTP2005: CICS ERROR FN: XXXX RES: XX/XX TRN: XXXX R: XXXXXXXX
> This happens when an ABEND occurs in CICS. FN: is the CICS command being executed at that moment. RES: is the EIBRESP response code. TRN: is the transaction causing the ABEND. R: is the resource used.
* ZTP2010: SESSION REJECTED BY VARIABLE PARAMETERS
> Internal error.
* ZTP2015: SESSION REJ. BY REPRESENTATION TYPE.
> Internal error.
* ZTP2020: SESSION REJ. BY VAR. PARM. LENGTH.
> Internal error.
* ZTP2025: VARIABLE ERROR XXXXXXXXXXXXXXX CODE. XXXX
> That variable corresponds to the session parameters that must be coded in the same way at both ends. If it does not match at either end, this error will appear indicating the variable.
* ZTP2026: RDO. VARIABLE XXXXXXXXXXXXXXX CODE.: XXXX
> That variable corresponds to the session parameters that DO NOT have to be coded in the same way at both ends. If it does not match at either end, this error will appear indicating the variable, although the process continues normally.
* ZTP2030: SAR IGNORED BY SESSION IDENTIFIER.
> An attempt is made to establish a session, and an SAP message remains queued to be sent to the remote or received from the remote. In a later transmission, that message appears, in addition to the SAP corresponding to the current transmission. To the remote, first comes the one from the first transmission (the queued one), so it responds with an SAR. When the SAR reaches the end that initiated the SAP of the second transmission, it realizes that it does not correspond to it, so it rejects it. This prevents something from being accepted that will later fail if the profiles have changed between the two transmissions. Normally, the situation clears automatically; if not, retry the transmission.
* ZTP2035: INCONGRUENT STATE IN MONITORING FILE
* ZTP2040: TRANSMISSION INITIALIZATION REQUESTED BY APP INTERFACE.
* ZTP2045: RECEPTION INITIALIZATION REQUESTED BY AP INTERFACE.
* ZTP2050: START OF TRANSMISSION WITHOUT END OF POST PROCESS.
* ZTP2060: TCP ERROR MACRO XXXXXXXXXXXXXX XX-XX. ERRNO=XXXXX
> An error has occurred in the macro specified for TCP/IP. Consult IBM-specific documentation. For cause and diagnosis XX-XX you can consult the “TCP/IP ERROR CAUSES AND CODES” option in the ZTBM menu.
* ZTP2061: TCP ERROR MACRO XXXXXXXXXXXXXX XX-XX. RTCD=XXXXX
> An error has occurred in the macro specified for TCP/IP. Consult IBM-specific documentation. For cause and diagnosis XX-XX you can consult the “TCP/IP ERROR CAUSES AND CODES” option in the ZTBM menu.
* ZTP2062: TCP ERROR PROGRAM XXXXXXXXXXXXXX XX-XX. RTCD=XXXXX
> An error has occurred in the IBM programs specified for TCP/IP. Consult IBM-specific documentation. For cause and diagnosis XX-XX you can consult the “TCP/IP ERROR CAUSES AND CODES” option in the ZTBM menu.
* ZTP2063:ERROR TCP/IP. XXXXXXXXXXXXXX XX-XX.
> An error has occurred in TCP/IP processes. For cause and diagnosis XX-XX you can consult the “TCP/IP ERROR CAUSES AND CODES” option in the ZTBM menu.
* ZTP2161: TCP/IP CONNECTION TYPE ERR. CLIENT TRAN. IN ENVIRONMENT
> An attempt is made to request a TCP/IP connection, and the TCP client transid (TCP API TRANSID) has not been included in the environment. Modify the environment including that parameter.
* ZTP2162: TCP/IP CONNECTION TYPE ERR. SERVER TRAN. IN ENVIRONMENT.
> Obsolete message.
* ZTP2163: TCP/IP CONNECTION TYPE WITHOUT TCPNAME IN ENVIRONMENT
> An attempt is made to request a TCP/IP connection, and the TCP stack address space (TCPNAME) has not been included in the environment. Modify the environment including that parameter.
* ZTP2164: SERVER ERROR (API-CONNECTION) : XXXX- XXXXX
> Error establishing the connection with the editran/CD server. The causes-diagnostics of the error are specified in Annex F.
* ZTP2165: LOCAL CERTIFIED CHANNEL REQUESTED
> A local certified channel is requested, via a call to editran/CD.
* ZTP2166: REMOTE CERTIFIED CHANNEL REQUESTED
> The remote end has requested a certified channel, via a call to editran/CD.
* ZTP2167: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Error text indicated by editran/CD. It is also used to report detailed errors.
* ZTP2170: CONTROL RECORD DOES NOT EXIST XXXXXX
> Edltran/P tries to access the buffer and the control record does not exist. Sometimes this can be a correct situation. In most cases it is an informational message.
* ZTP2175: RETRY SCHEDULED. TIME WINDOW- XXXXXXXX
> Edltran/P, when it receives a local transmission or reception request, checks that the retry time-window parameter is active, so it schedules that request at the start time indicated in the session (either for that day or the next).
* ZTP2180: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Error text indicated by the license control. Contact INDRA to update your license.
* ZTP2185: EDI VERSION IGNORED BY DATE CONTROL.
> Edltran/P, when it receives a session establishment request, detects that the date difference between the local and remote systems is greater than 48 hours. Notify the remote so that it enters the correct date.
* ZTP2190: PROXY CONNECTION TYPE WITHOUT IP-PROXY IN ENVIRONMENT
> An attempt is made to request a PROXY connection, and the proxy IP address has not been included in the environment. Modify the environment including that parameter.
* ZTP2191: PROXY CONNECTION TYPE WITH REMOTE VERSION < 41.
> With proxy connection type, only remote editran/P version 4.1 is allowed. Modify the version and tell the remote to do the same.
* ZTP2195: RECEIVED SWIFT MSG. INAPPROPRIATE PROFILE IN SESSION .
> A SWR indication is received (from the editran swift server), but the session does not have the swift parameter active.
* ZTP2196: POST-TRANSMISSION NOT LAUNCHED. DATA IN SWIFT.
> In the session defined with the swift parameter active, the post-transmission process is not launched until confirmation is received from the swift server.
* ZTP2197: RECEIVED SWIFT MSG. UNKNOWN MESSAGE TYPE.
> Internal error.
* ZTP2198: RECEIVED SWIFT MSG. UNKNOWN IDENTIFIER.
> In the session defined with the swift parameter active, a confirmation is received from the server that does not correspond to the last known transmission.
* ZTP2199: RECEIVED SWIFT MSG. INCOMPATIBLE BUFFER STATE.
> In the session defined with the swift parameter active, a confirmation is received from the server, but the sender buffer is no longer in the proper state.
* ZTP2200: RECEIVED SWIFT MSG. TRANSMISSION NOT YET PROCESSED.
> In the session defined with the swift parameter active, a confirmation is received from the server indicating that it does not yet know the result of the SWIFT transmission process.
* ZTP2201: LAUNCH SIMULATED POST-TRANSMISSION BY DOWNLOAD CONFIRMATION.
* ZTP2202: LAUNCH SIMULATED POST-RECEPTION BY DOWNLOAD CONFIRMATION.
* ZTP2203: POST-TRANSMISSION NOT LAUNCHED BY DOWNLOAD CONFIRMATION '.
* ZTP2205: REMOTE CALL REJECTED (TRANSPORT ID FORMAT)'.
> Obsolete message.
* ZTP2210: REEMISSION IGNORED. WAITING FOR SWIFT RESPONSE'.
* ZTP2215: SENDER BUFFER FILE CLOSED OR NOT INITIALIZED '.
* ZTP2220: RECEIVER BUFFER FILE CLOSED OR NOT INITIALIZED.'.
* ZTP2225: RECEIVED LOCAL DOWNLOAD QUERY MESSAGE '.
* ZTP2230: RECEIVED CORRECT REMOTE DOWNLOAD MESSAGE
* ZTP2235: RECEIVED REMOTE DOWNLOAD MESSAGE NOT COMPLETED
* ZTP2240: RECEIVED INCORRECT REMOTE DOWNLOAD MESSAGE
* ZTP2245: ERROR READ STATES. DOWNLOAD CONFIRMATION IGNORED
* ZTP2250: ERROR WRITE STATE. DOWNLOAD CONFIRMATION IGNORED
* ZTP2255: ERROR STATE PRESE. DOWNLOAD CONFIRMATION IGNORED
* ZTP2260: BUFFER ERROR. DOWNLOAD CONFIRMATION IGNORED
* ZTP2265: TRANSLATION ERROR. DOWNLOAD CONFIRMATION IGNORED
* ZTP2270: ERROR SESSION BUFFER NO. DOWNLOAD CONFIRMATION IGNORED
* ZTP2275: ERROR CSB HEADER. DOWNLOAD CONFIRMATION IGNORED
* ZTP2280: ERROR READING TRANSMISSION SESSION PERF-G
* ZTP2285: ERROR READING PRESENTATION SESSION PERF-G
* ZTP2290: RECEIVED DOWNLOAD CONFIRMATION MESSAGE IGNORED
* ZTP2295: CONNECTION REQUEST REQUESTED BY XXXXXXXX
* ZTP2300: RELEASE REQUEST REQUESTED BY XXXXXXXX
* ZTP2305: NETWORK RESTART REQUEST REQUESTED BY XXXXXXXX
* ZTP2310: REMOTE SENDER BUFFER QUERY REQUESTED BY XXXXXXXX
* ZTP2315: REMOTE RECEIVER BUFFER QUERY REQUESTED BY XXXXXXXX
* ZTP2320: TRANSMISSION REQUEST REQUESTED BY XXXXXXXX
* ZTP2325: RECEPTION REQUEST REQUESTED BY XXXXXXXX
* ZTP2330: END OF TRANSMISSION REQUEST REQUESTED BY XXXXXXXX
* ZTP2335: END OF RECEPTION REQUEST REQUESTED BY XXXXXXXX
* ZTP2340: REMOTE DATA REQUEST REQUESTED BY XXXXXXXX
* ZTP2345: REMOTE RESPONSE REQUEST REQUESTED BY XXXXXXXX
* ZTP2350: OPERATOR MESSAGE SEND REQUEST REQUESTED BY XXXXXXXX
* ZTP2355: READ ERROR IN ZTBPFPE BY SEP-SER
* ZTP2365: READ ERROR REM. ZTBGFPER BY SEP-SER
* ZTP2370: UPDATE ERROR REM. ZTBGFPE BY SEP-SER
* ZTP2375: UPDATE ERROR S.PR. ZTBGFPE BY SEP-SER
* ZTP2380: NO VALID LINES FOUND TO CALL
* ZTP2385: SPECIFIC PROXY LINE NOT FOUND. REF:XX
* ZTP2390: SPECIFIC TCPIP LINE NOT FOUND. REF:XX
* ZTP2400: ERROR IN MODULE ZTBPOCR9. R:XXX (XX-XXXXX)
* ZTP2405: ERROR START TRANSID:XXXX TERMID:XXXX RESP:XXXX
* ZTP2410: ERROR SET FILE:XXXXXXXX RESP:XXXX RES2:XXXX
* ZTP2415: LICENSE ERROR (CPUID). CONTACT INDRA.
* ZTP2420: SLOW TCP. CORE FINISHES THE MESSAGE BURST
* ZTP2425: NO BUFFER FILE EXISTS IN TREATED SESSION
* ZTP2430: LOCK ERROR ZTBGB020 ON MATRIX BUFFER
* ZTP2435: BUFFER KEY:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
* ZTP2440: ERROR LINK XXXXXXXX FILE:XXXXXXXX RESP:XXXX
---
# 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/utilities-and-codes/appendix-a.-editran-messages-to-the-operator-and-log.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.