> 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-iseries-en/administracion-y-operacion/appendix-a.-messages-from-onesait-editran-to-the-operator-and-log..md). # Appendix A. Messages from Onesait Editran to the operator and log. These messages appear in the OPERATOR TERMINAL (and are always recorded in the Log file) of each editran session, as a result of events in the transmissions. The following messages are detailed below, in alphabetical order, with their explanation or the recommended action to take. START OF TRANSMISSION Comment A transmission request is sent to the remote. CONNECTION ESTABLISHED Comment Both a local and a remote connection request have been accepted. The connection exists and the real terminal has been activated. STATUS QUERY Comment Message outside the protocol. REMOTE SENDER FILE QUERY Comment The query of the remote transmission buffer control file record has been requested. REMOTE RECEIVER FILE QUERY Comment The query of the remote reception buffer control file record has been requested. TOTALS MISMATCH IN SENDER PROCESS Comment In applications with totals control, the confirmed exchanged totals do not match (synchronization). TOTALS MISMATCH IN RECEIVER PROCESS Comment In applications with totals control, the confirmed exchanged totals do not match (synchronization). TRANSMISSION CORRECT AND FINISHED Comment A transmission is considered finished. ERROR. A5P WITH INCORRECT QUALIFIER Action Correct A5P request type. ERROR OPENING FILE XXXXXXXX Action The file cannot be opened. It probably does not exist. ERROR: INCOMPATIBLE KEYS. (ERR9) Comment Error in key authentication. The local operational key does not match the remote one. See annex C. CRC CALCULATION ERROR IN SENDER PROCESS Comment Before sending a message to the remote, there is a local error in calculating its CRC. The message is ignored. CRC CALCULATION ERROR IN RECEIVED MESSAGE Comment When receiving a message from the remote, there is a local error in calculating its CRC. The message is ignored. ERROR IN COMPRESSION Comment A local compression/decompression error occurs. ERROR IN REMOTE BATCH PROCESS Comment It has occurred in some automatic batch process on the remote, with the consequent release. ERROR IN TRANSPARENCY IN RECEIVED MESSAGE Comment When receiving a message in Public or Private PAD connection type, a local error occurs in calculating its transparency. LOCAL COMPRESSION/DECOMPRESSION ERROR Comment An error has been detected when compressing/decompressing data, with the consequent release of the circuit. REMOTE CRYPTOGRAPHY ERROR. (ERRx) Comment A remote cryptography error has been detected. See ERRx at the end of this section. REMOTE COMPRESSION/DECOMPRESSION ERROR Comment The remote had an error when compressing/decompressing data, with the consequent release of the circuit. EXCESS OF TRANSMISSION BLOCK RETRIES Comment All transmission block retries have been exhausted according to the maximum number of profile synchronization retries. EXCESS OF CONNECTION RETRIES Comment All connection retries have been exhausted, according to the number of retries in the editran session profiles. EXCESS OF SYNCHRONIZATION RETRIES Comment All synchronization retries have been exhausted, according to the number of retries in the editran session profiles. EXCESS OF RETRIES IN THE SENDER PROCESS Comment All retries with duplicates in the sender process for messages that require a response have been exhausted. EXCESS OF RETRIES IN THE RECEIVER PROCESS Comment All retries with duplicates in the receiver process for messages that require a response have been exhausted. EXCESS OF RETRIES TO SEND Comment When a synchronization request exhausts the retries while waiting for a response. EXCESS OF RETRIES TO ESTABLISH SESSION Comment All parameter notification retries for session establishment have been exhausted without receiving a response from the remote. EXCESS OF RETRIES TO END TRANSMISSION Comment When a transmission end request exhausts the retries while waiting for a response. EXCESS OF RETRIES TO RECEIVE Comment When a synchronization request exhausts the retries while waiting for a response. CALLING END INVALID (PROFILES) Comment Incompatibility in the values of that field in the profiles record. TRANSMISSION FILE NOT READY Comment The control record information exchanged between the two ends, in the transmission start request/response message, does not allow data exchange to begin. The exchange session number contained in the control records does not match. The transmission/reception file is not loaded, or is not available for editran (the batch process specified in profiles is triggered). PROFILES FILE NOT CREATED (PERFTAM) Action Define this file and create the local environment. RECEPTION FILE NOT READY Comment The control record information exchanged between the two ends, in the transmission start request/response message, does not allow data exchange to begin. The exchange session number contained in the control records does not match. The transmission/reception file is not loaded, or is not available for editran (the batch process specified in profiles is triggered). BUFFER FILES IN AN INCOMPATIBLE STATE Comment The remote rejects the local request because its buffer file is not ready. It may have launched the corresponding pre-automation for the request. END OF LOCAL TRANSMISSION Comment When the transmission for the session is considered finished, following a local operator request. END OF TRANSMISSION REQUESTED BY LOCAL IGA Comment: When Local IGA requests forced end of transmission. END OF TRANSMISSION REQUESTED BY OPERATOR Comment: When the operator requests forced end of transmission. END OF LOCAL RECEPTION Comment When the transmission for the session is considered finished, at the request of the local operator. END OF RECEPTION REQUESTED BY LOCAL IGA Comment: When Local IGA requests forced end of reception. END OF RECEPTION REQUESTED BY OPERATOR Comment When the operator requests forced end of reception. END OF REMOTE TRANSMISSION Comment End of transmission due to a remote problem. END OF LOCAL TRANSMISSION REQUESTED BY THE REMOTE Comment When the remote requests end of reception/transmission. LOCAL IGA REJECTS THE BATCH REQUEST Comment IGA rejects the request made because it is in a situation incompatible with the request. START OF RECEPTION Comment When the reception of the remote file begins. INABILITY TO TRANSMIT DUE TO PROFILES Action Check the processes defined in the session profile. INABILITY TO RECEIVE DUE TO PROFILES Action Check the processes defined in the session profile. THE REMOTE FICTIONAL LU IS IN OUT Action Call the remote and have it acquire the fictional LU. THE REMOTE FICTIONAL LU IS IN REL Action Call the remote and have it acquire the fictional LU. RELEASE OF THE REMOTE OPERATOR Comment The remote operator has requested release. RELEASE DUE TO CALL CROSSING Comment The call that was processed last is released. RELEASE BY THE OPERATOR Comment It occurs as a result of an operator release request. RELEASE DUE TO COMPRESSION ERROR Comment Release is requested when a compression/decompression error occurs in a message. RELEASE DUE TO ANOTHER CHANNEL BEING ESTABLISHED Comment A circuit is released because another one is connected for a given session. RELEASE DUE TO INVALID FACILITIES Action The type of facilities used when requesting the connection will be checked. editran only manages reverse-charge use. RELEASE DUE TO INCORRECT SCHEDULE Action Check the schedule given in the session profile and modify it. RELEASE DUE TO NOT ACCEPTING REVERSE CHARGE Action Check the reverse-charge field in the session profile. RELEASE DUE TO NO FREE CHANNELS Action Circuit limitation: the connection can be established once another already established session is released, or the maximum number of cvc in the environment can be modified. RELEASE DUE TO INVALID PAYMENT TYPE (PROFILES) Action Check the session payment type in anticipation of conflicts. One end must support charges. TRANSMISSION RELEASE Comment A circuit release has occurred. LOCAL CANNOT TRANSMIT (PROFILES) Comment Transmission request rejected because parameter 'traffic direction' is not specified with value 'E' or 'X'. LOCAL CANNOT CALL (PROFILES) Comment Connection request rejected because the parameter 'calling end = R' is specified, so only the remote can call. LOCAL CANNOT RECEIVE (PROFILES) Comment Check the 'traffic direction' parameter. CALL REJECTED (INVALID TIME) Action Connection request outside schedule. Check profiles. CALL REJECTED INVALID NRI (PROFILES) Action Correct the session NRI in profiles. REMOTE CALL ACCEPTED Comment The remote connection request has been accepted. The connection is established. REMOTE CALL ACCEPTED (CROSSING) Comment Both ends have requested the connection establishment and the remote one was handled first. REMOTE CALL REJECTED Comment The incoming call from the remote is rejected. REMOTE CALL REJECTED (REVERSE CHARGE) Comment The specification for that parameter is incompatible at both ends. REMOTE CALL REJECTED (CROSSING) Comment Both ends have requested the connection establishment and the local one was handled first. REMOTE CALL REJECTED (CALLING END) Comment The specification for that parameter does not match at both ends. REMOTE CALL REJECTED (UNKNOWN SESSION) Action Register the remote session in profiles or notify the remote of the impossibility of communicating. It may also be due to an invalid code in the remote environment. REMOTE CALL REJECTED (NO CHANNEL) Comment The remote call is rejected because the maximum number of cvc registered in the local environment has been exceeded. REMOTE CALL REJECTED (PAYMENT TYPE) Comment The specification for that parameter does not match at both ends. REMOTE CALL REJECTED (CVC ALREADY EXISTS) Comment Remote connection request rejected because a cvc already exists. INCORRECT NOTIFICATION MESSAGE Comment A notification message has been received outside specifications. MESSAGE RECEIVED WITH INVALID CRC Comment A message has been received from the remote in a session defined in profiles with CRC validation, and it is incorrect. NO CONNECTION EXISTS Comment A request has been made that required a connection to be established beforehand. NO PROCEDURE EXISTS IN PROFILES Action Register it in the session profile. NO SESSION EXISTS Action Register the session in profiles. NO SESSION EXISTS IN PROFILES Action Register the session in profiles. THERE ARE NO FREE CHANNELS Action The connection can be established once another already established one has been released. This is due to the limitation of physical circuits in the local environment. INCOMPATIBLE EXCHANGE SESSION NUMBER Comment The Exchange Session Number of the receiver and sender buffer file on the Local and Remote sides do not match. They must match at both ends. Action Run the procedure that increments this number at the end that is behind, or start from Session Number 0001. LOST SEQUENCE IN SENDER PROCESS Comment A jump in the message sequence number has been detected. LOST SEQUENCE IN RECEIVER PROCESS Comment A jump in the message sequence number has been detected. INCOMPATIBLE PROFILES (COMPRESSION) Comment The specified value for the compression parameter does not match at both ends. INCOMPATIBLE PROFILES (TRANSMISSION DIRECTION) Comment The specified value for the transmission direction parameter does not match at both ends. INCOMPATIBLE PROFILES (SESSION AND TERMINAL) Comment The session codes in the incoming message do not match the terminal specified in profiles. PROFILES WITHOUT LOCAL CHARACTERISTICS Action Register environment record. BATCH REQUEST TO UNLOAD TRANSMISSION Comment A batch request has been received to launch a job specified in profiles. BATCH REQUEST TO UNLOAD RECEPTION Comment A batch request has been received to launch a job that had been specified in profiles. BATCH REQUEST TO START TRANSMISSION Comment A batch request to begin local transmission has been received. BATCH REQUEST TO START RECEPTION Comment A batch request to begin local reception has been received. BATCH REQUEST FOR PREPARATION AND START OF TRANSMISSION Comment A batch request has been received to launch a job specified in profiles. BATCH REQUEST FOR PREPARATION AND START OF RECEPTION Comment A batch request has been received to launch a job specified in profiles. REMOTE TRANSMISSION REQUEST Comment A remote request has been received for the start of local transmission. RECEPTION REQUEST Comment When the request is processed by the local or remote operator. LOCAL RECEPTION REQUEST Comment A local request has been received for the start of remote transmission. POST-TRANSMISSION FINISHED CORRECTLY Comment Response received from batch confirming correct completion of a process. POST-RECEPTION FINISHED CORRECTLY Comment Response received from batch confirming correct completion of a process. PRE-TRANSMISSION FINISHED CORRECTLY Comment Response received from batch confirming correct completion of a process. PRE-RECEPTION FINISHED CORRECTLY Comment Response received from batch confirming correct completion of a process. START OF SESSION. LOCAL TRANSMISSION Comment The first burst of the transmission has been sent. MAKE THE CALL Comment Local connection request. RECEPTION CORRECT AND FINISHED Comment When a reception transmission is considered finished. RECEIVED MESSAGE WITH UNKNOWN LOCAL CODE Action Check remote session in profiles. INCORRECT MESSAGE RECEIVED FROM BATCH Comment Batch request outside the protocol. INCORRECT MESSAGE RECEIVED IN SENDER PROCESS Comment Message outside the protocol. INCORRECT MESSAGE RECEIVED. RECEIVER PROCESS Comment Message outside the protocol. RECOVERY OF CIRCUITS Comment The fictional LU has been acquired. RETRY TO ESTABLISH SESSION Comment A timeout is detected while establishing the session and it is requested from the remote. REMOTE WITHOUT SESSION/REGISTERED NRI (PROFILES) Comment The NRI of an incoming call does not match the one of the session registered in profiles. SBP RECEIVED IN INCORRECT STATE Comment Message outside the protocol. SBR WITH TOTALS MISMATCH Comment Negative response to a totals synchronization because the totals in the receiver process do not match. SCP RECEIVED IN INCORRECT STATE Comment Message outside the protocol. RECEIVING IN PROGRESS. BATCH REQUEST IGNORED Comment A batch reception request has been received, which cannot be processed because reception is in progress. TRANSMITTING IN PROGRESS. BATCH REQUEST IGNORED Comment A batch transmission request has been received, which cannot be processed because transmission is in progress. BATCH LAUNCHED AFTER TRANSMISSION Comment Batch process launched according to profiles. BATCH LAUNCHED AFTER RECEPTION Comment Batch process launched according to profiles. BATCH LAUNCHED BEFORE TRANSMISSION Comment Batch process launched according to profiles. BATCH LAUNCHED BEFORE RECEPTION Comment Batch process launched according to profiles. SEP RECEIVED IN INCORRECT STATE Comment Message outside the protocol. UNKNOWN SESSION (PROFILES) Action Register the session in profiles. SESSION ESTABLISHED Comment Notification messages have been exchanged correctly. Both ends are in session. SESSION NOT ESTABLISHED Comment A request has been received from the remote or local operator without the session being established. SESSION REJECTED BY PROFILES (ASCII/EBCDIC) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (CRC CALCULATION) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (SERVICE QUALITY) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (TOTALS CONTROL) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (COMPRESSION) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (CRYPTOGRAPHY) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (RECORD LENGTH) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (APPLICATION TYPE) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (CONNECTION TYPE) Comment Both ends do not agree on that parameter. SESSION REJECTED BY PROFILES (VERSION) Comment Both ends do not agree on that parameter. LOCAL KEY CHANGE REQUESTED Comment During session establishment, the local end asks the remote to change its key. REMOTE KEY CHANGE REQUESTED Comment During session establishment, the remote end asks the local end to change its key. RELEASE REQUESTED BY OPERATOR Comment The local operator has requested the release of the cvc. REMOTE SENDER BUFFER INACCESSIBLE Comment The remote has a file access error on the sender file. REMOTE RECEIVER BUFFER INACCESSIBLE Comment The remote has a file access error on the receiver file. RTC CONNECTION TYPE CANNOT CALL Comment A local connection request is received for a remote defined with RTC connection type. TRANSMISSION STILL IN PROGRESS Comment Request not processed because transmission is in progress. CONNECTION ALREADY EXISTS Comment A connection request has been made to a session that was already connected. TRANSPORT CONNECTION ALREADY EXISTS Comment A circuit connection at the physical level has been detected. --- # 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-iseries-en/administracion-y-operacion/appendix-a.-messages-from-onesait-editran-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.