> 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-comun-z-os-en/interfaz-generica-de-aplicacion/anexo-a.-mensajes-de-onesait-editran.md). # Appendix A. Onesait Editran messages Messages recorded in the LOG during the execution of the Editran/G procedures. They are specified in ascending order of message code, with an explanation in some of them if their meaning is not obvious. The messages contain variables whose meaning is as follows: * xxxxxxxx: Program that generates the message * yyyyyyyy: Resource related to the message * zz: File-status obtained when accessing files * zzzz: Resulting return code generated by the notification The File-status (F-S) returned when accessing VSAM files can be consulted in the vendor's COBOL manuals. * ZTG0013: Loading of yyyyyyy Converter issue completed R-C: zzzz * ZTG0014: Presentation load correct and completed * ZTG0015: Output request is sent to the Editran transmission module (A1R) * ZTG0016: Reception request is sent to the Editran transmission module (A2R) * ZTG0017: xxxxxxxx: Error in Converter yyyyyyyy process. R-C: zzzz Another more specific error message must exist. * ZTG0018: Request to process presentation after output * ZTG0019: Request to load output presentation * ZTG0020: Request for presentation output * ZTG0021: Request for cumulative presentation output. Output has been requested for a session with cumulative load type. * ZTG0022: Request to end presentation output * ZTG0023: Request to initialize reception * ZTG0024: Request to unload presentation reception * ZTG0025: Request for presentation reception * ZTG0026: Request to end presentation reception * ZTG0027: xxxxxxx: Inconsistency in presentation states. An attempt is made to determine the state of the presentation session by checking the transmission sessions it consists of, and these are not consistent with each other. A manipulation, external to Editran, of the transmission session states may have occurred. * ZTG0028: End of reception unload of Converter yyyyyyyy. R-C: zzzz * ZTG0029: xxxxxxxx: Error reading buffer reg-0 yyyyyyyy. F-S: zz. This type of error should not occur. It happens when trying to process a certain record that should exist and an error occurs. This case refers to the control record of a buffer. * ZTG0030: xxxxxxxx: Error reading buffer reg-1 yyyyyyyy. F-S: zz. Same type as ZTG0029 but referring to the second record of the buffer, which may have a special meaning depending on the case. * ZTG0031: xxxxxxxx: App. record length incompatible with transmission. In compatibility mode, the application record length must not exceed the transmission data length. * ZTG0032: xxxxxxxx: Error accessing the DB yyyyyyyy. R-C: zz. Not applicable to the CICS version. * ZTG0033: xxxxxxxx: Error accessing file yyyyyyyy. R-C: zz. Not applicable to the CICS version. * ZTG0034: Presentation state incompatible with the request. Before launching the corresponding procedure, Editran checks that the presentation state is compatible with the request made by the operator, interactive or batch. This circumstance is also checked during procedure execution, and if there is an error this message is issued, since they may have been launched directly by JCL, by the Editran transmission module, or even by the Editran presentation module operator himself repeatedly before the state is changed by the previous execution. * ZTG0035: xxxxxxxx: Error performing chkp R-C: zz. Not applicable to the CICS version. * ZTG0036: xxxxxxxx: Error writing buffer reg-0 yyyyyyyy. F-S: zz. This message and the next three are of the type ZTG0029 and 30. * ZTG0037: xxxxxxxx: Error writing buffer reg-1 yyyyyyyy. F-S: zz * ZTG0038: xxxxxxxx: Error rewriting buffer reg-0 yyyyyyyy. F-S: zz * ZTG0039: xxxxxxxx: Error rewriting buffer reg-1 yyyyyyyy. F-S: zz * ZTG0040: xxxxxxxx: Catalog. error (no space or file already exists). Error in the allocation of reception application files. An extended message must exist in ZTGPRINT. * ZTG0041: xxxxxxxx: Error in process, no Converter exists in profiles. The converter programs before output and after reception are mandatory in order to perform the load and unload respectively. * ZTG0042: xxxxxxxx: Error inserting/retrieving message R-C: zz. Not applicable to the CICS version. * ZTG0043: xxxxxxxx: Error in process, no procedure exists in profile. This message can only occur during batch operator execution. * ZTG0044: xxxxxxxx: Error in process, no EDI session exists in profiles. Same as the previous one. * ZTG0045: xxxxxxxx: Error in process, no IGA session exists in profiles. It can occur during batch operator execution and when procedures launched directly are run (an incorrect PARM has been set) or by Editran (the transmission session is not included in any presentation). * ZTG0046: End of application file yyyyyyyy load * ZTG0047: Request to process presentation after output * ZTG0048: Request to load output presentation * ZTG0049: Request for presentation output * ZTG0050: Request for dynamic presentation output * ZTG0051: Request to end presentation output * ZTG0052: Request to initialize reception * ZTG0053: Request to unload presentation reception * ZTG0054: Request for presentation reception * ZTG0055: Request to end presentation reception * ZTG0056: Uncataloged application file yyyyyyyy. The file specified in the profiles cannot be found. Loading continues with other application files, if any. * ZTG0057: Empty output application file yyyyyyyy * ZTG0058: Invalid transmission length detected for Editran 2.0: zzzz. In compatible mode, the transmission length must be 252 or 4050. Not used * ZTG0059: Request to end output is sent to Editran/P. * ZTG0060: Request to end reception is sent to Editran/P. * ZTG0061: Editran/P notified of post-output end (A3R) * ZTG0062: Editran/P notified of reception unload end (A4R) * ZTG0063: Editran/P notified of output load error (A1R) * ZTG0064: Editran/P notified of reception initialization error (A2R) * ZTG0065: Editran/P notified of error in post-output (A3R) * ZTG0066: Editran notified of error in reception unload (A4R) * ZTG0067: Reception initialization correct and completed * ZTG0068: xxxxxxxx: Buffer definition incompatible with transm. length. A matrix buffer is used whose record length is less than transmission length + 36. * ZTG0069: Presentation output unload correct and completed * ZTG0070: Presentation reception unload correct and completed * ZTG0071: xxxxxxxx: Reception application file yyyyyyyy already exists. In reception unload, one of the application files was found to already exist, and "Delete if they exist" = N was specified in the profile. * ZTG0072: xxxxxxxx: No session exists in the status register. Possible inconsistency in the transmission sessions defined in the local and remote presentation sessions. * ZTG0073: Application file yyyyyyyy has not been received. In 2.0 compatibility mode, there is no file with the identifier defined in the reception files part of the presentation session profile in the reception buffer index record. Not used * ZTG0074: Empty application file yyyyyyyy received * ZTG0075: Application file yyyyyyyy received * ZTG0076: Reception application file yyyyyyyy deleted * ZTG0077: File yyyyyyyy not fully unloaded. In 2.0 compatibility mode, possible difference in the number of remote output files and local reception files. Not used. * ZTG0078: Error in decompression. Record no. yyyyyyyy R-C: zz * ZTG0079: Incompatible request for remote Editran version < 2.1 * ZTG0080: xxxxxxxx: No application file exists in profiles. It can occur in output load and reception unload in compatibility mode. * ZTG0081: xxxxxxxx: Recovery error. File yyyyyyyy not valid. Not applicable to the CICS version. * ZTG0082: User application program yyyyyyyy is called * ZTG0083: End of transmission session load: buffer yyyyyyyy * ZTG0084: Application file not unloaded: yyyyyyyy. Not applicable to the CICS version. * ZTG0085: Recovery unload of file: yyyyyyyy. Not applicable to the CICS version. * ZTG0086: xxxxxxxx: Unknown application file characteristics. Editran can only load application files of types F, FB, V, VB. * ZTG0087: Normalized CSB file load completed successfully * ZTG0088: Transmission session initialized: buffer yyyyyyyy * ZTG0089: Transmission session unload: buffer yyyyyyyy * ZTG0090: Normalized CSB file unload completed successfully * ZTG0091: Reception buffer without Editran header: yyyyyyyy (empty). This may occur if the remote loads an empty file in compatible mode and the local side tries to unload it in native mode. Check the remote Editran load and unload version. * ZTG0092: xxxxxxxx: Editran header with incorrect transmission session. This usually occurs if the remote Editran is on an ASCII platform and EBCDIC has not been specified as the remote alphabet. It also occurs if the transmission sessions of the presentation do not match locally and remotely. * ZTG0093: xxxxxxxx: Editran header not found in transmission sessions. It is usually due to the remote loading in compatible mode and the local side trying to unload in native mode (check the remote Editran load and unload version). It also occurs when a remote ASCII system indicates in its presentation session profiles that it will transmit against an ASCII one (the remote has indicated ASCII-EBCDIC=A). This error has also occurred if, after initializing reception with a transmission length, this is increased before reception. Also if reception has been initialized and, without receiving anything, reception is interrupted and unloaded. Another situation is when the remote side (Windows-Unix environment) has loaded a file as binary, with Editran compression, and has version 3.1 installed; in that case the version must be updated or output must be sent without LZW compression (Editran). * ZTG0094: Incomplete normalized CSB reception file detected. It can only be due to an Editran incident. x files are received in the header and when unloading, it is detected that fewer are being unloaded. * ZTG0095: xxxxxxxx: No complete data batch received. * ZTG0096: xxxxxxxx: Incomplete profile parameters for reception. No data has been specified on the 5th screen of the presentation session, reception files, and an unload is attempted. * ZTG0097: xxxxxxxx: Inconsistency of profile sessions and states. The transmission sessions in the presentation profile have been modified and the states have not been initialized. * ZTG0098: xxxxxxxx: Incorrect-length application reg. detected. This can only occur due to a product issue in reception unload. * ZTG0099: xxxxxxxx: Buffer with incorrect Editran header detected. This error should not occur under normal circumstances. After loading the buffer or buffers, one of them is detected with an incorrect header. * ZTG0100: Erroneous parameter in Editran profiles: yyyyyyyy. The remote Editran version specified in the presentation session profile is not consistent with the converters used. * ZTG0101: Request not implemented for remote Editran version 2.1. Refers to dynamic output. * ZTG0102: xxxxxxxx: Editran sessions must have the same matrix buffer * ZTG0103: xxxxxxxx: JCL files to submit do not exist in profiles * ZTG0104: xxxxxxxx: Recovery. Session previously processed. Not applicable to the CICS version. * ZTG0105: xxxxxxxx: Recovery. Session processed successfully. Not applicable to the CICS version. * ZTG0106: xxxxxxxx: Unknown Editran profile key length. This may be due to specifying, in the procedure, a profile file from a previous version. * ZTG0107: xxxxxxxx: Incorrect local Editran version * ZTG0108: Interruption notification, code: yyyy. In an exception procedure launched by Editran, the reason for that exception is reported; for its meaning, consult the manual [Administration and operation](https://gitlab.devops.onesait.com/onesait/disruptors/ecosystems-editran/editran-documentation/-/blob/public/IBM/5.3/zOS/interfaz-generica-de-aplicacion/broken-reference/README.md). * ZTG0109: User application program yyyyyyyy is called * ZTG0110: User process completed successfully * ZTG0111: xxxxxxxx: Error in user process yyyyyyyy. R-C: zzzz * ZTG0112: xxxxxxxx: Unknown buffer file type for I.G.A. Editran cannot process public buffers. * ZTG0113: Notification to Editran that output buffer is ready (A8R) * ZTG0114: Notification to Editran that reception buffer is ready (AAr) * ZTG0115: Editran is notified that the transmission session was not loaded. This occurs when the presentation session consists of several transmission sessions, but some of the associated buffers fail to load because the amount of information to be loaded does not exceed the minimum established per session. * ZTG0116: xxxxxxxx: Process error. Incorrect field yyyyyyyy. Internal error. * ZTG0117: External static allocation of application file detected * ZTG0118: xxxxxxxx: Incorrect DCB (CSB-N: RECFM=yyyyyyyy LRECL=zzzzz) * ZTG0119: Request to modify states PARAM=yyyyyyyy * ZTG0120: xxxxxxxx: State transmission session is not in profiles * ZTG0121: Bytes in compressed file differ from those of the sender. It is detected that the number of bytes obtained by the local LZW expander does not match the theoretical number reported by the remote side. * ZTG0122: xxxxxxxx: Input file is not in compressed format. The local expander detects that the received file is uncompressed. * ZTG0123: xxxxxxxx: Error returned by module yyyyyyyy ERR=zzzzz. Error returned by the compressor or expander. ERR refers to the codes specified in the vendor's "C 370 Programming Guide". * ZTG0124: xxxxxxxx: Application file bytes differ from the sender's. This is usually due to a bad load. Another situation is when the remote side (Windows-Unix environment) has loaded a file as binary, with Editran compression, and has version 3.1 installed; in that case the version must be updated or output must be sent without LZW compression (Editran). * ZTG0125: Unload detected in finished state * ZTG0126: Request to delete presentation states * ZTG0127: State modification correct and completed * ZTG0128: State deletion correct and completed * ZTG0129: xxxxxxxx: No buffer file exists in Editran session profile * ZTG0130: Sessions must have the same transmission length. This message and the next two refer to the transmission sessions of a particular presentation. * ZTG0131: Sessions must have specific files or the same matrix * ZTG0132: Sessions must have the same JCL files or none at all * ZTG0133: Interruption detected in finished state * ZTG0134: With V2.2 cryptography, you must authenticate in Editran. If you want to use batch cryptography in Editran * ZTG0135: With batch cryptography, key change must be "N". If batch cryptography is used, the key cannot be changed before transmission is completed. * ZTG0136: xxxxxxxx: Error encrypting data. RC=yyyyy Reason=zzzzz. Error returned by the specific cryptography interface installed by the user. * ZTG0137: xxxxxxxx: Error decrypting data. RC=yyyyy Reason=zzzzz. Same as ZTG0136 * ZTG0138: xxxxxxxx: Error generating key. RC=yyyyy Reason=zzzzz. Same as ZTG0136 * ZTG0139: xxxxxxxx: Error reencrypting key. RC=yyyyy Reason=zzzzz. Same as ZTG0136 * ZTG0140: xxxxxxxx: Error encrypting key. RC=yyyyy Reason=zzzzz. Same as ZTG0136 * ZTG0141: With batch compression, compression in Editran is incompatible * ZTG0142: File compression correct and completed * ZTG0143: File decompression correct and completed * ZTG0144: Buffer encryption ends successfully * ZTG0145: Buffer decryption ends successfully * ZTG0146: xxxxxxxx: Error writing compressed file: zzzzz. It is usually a space problem because a file allocation has been too small. It is usually solved by increasing the number of records in the presentation session. * ZTG0147: Interruption in "finished" not allowed with Delete-buffer = S * ZTG0148: xxxxxxxx: Last character of the parameter is not a separator. Refers to the macrofile load process. * ZTG0149: xxxxxxxx: Parameter length and identifier length are not equal. This occurs in the macrofile load process if the identifier field length, in the Presentation session parameter, does not match the number of characters between separators in the mentioned identifier field. * ZTG0150: xxxxxxxx: Error verifying uncertainty. * ZTG0151: Error checking the file hash (sender-receiver do not match). * ZTG0152: xxxxxxxx: Error verifying signature (authentication). * ZTG0153: CSB file loaded in a previous process detected. The normalized CSB file is an intermediate file used both in load and unload, and it is deleted after a normal process. If a process fails and this file has been loaded successfully, checking the output or reception state would show it as "loaded". A new process request would, in this situation, start from the mentioned normalized CSB file. This message indicates that, in the normal load or unload process, this intermediate file obtained in a previous execution has been found. * ZTG0154: xxxxxxxx: Error locking matrix file (Lock) RC = zzzzz. Applicable to VSE version. * ZTG0155: xxxxxxxx: Error unlocking matrix file (Unlock) RC = zzzz. Applicable to VSE version. * ZTG0156: With cryptographic version 3.0, the RSA key length must be 1024. * ZTG157: Editran sessions with different cryptographic versions. This error occurs in two cases: when there is more than one transmission session and they do not have the same cryptography version, and when the cryptography version in Editran is 4.0 and the remote Editran version is lower than 5.2. * ZT0158: Error calculating the application file hash * ZTG0159: The file to be sent is a directory YYYYYYYY * ZTG0160: NOT USED. * ZTG0161: xxxxxxxx: Invalid application parameters. In the macrofile load process, the Presentation session parameter contains an identifier position or length, or data length or position, with non-numeric values, zeros, or values greater than 32752. It also occurs if the position and length of the data or identifier, added together, exceed the effective record length of the macrofile. * ZTG0162: xxxxxxxx: Empty ZTBGFSES file. In the macrofile process using JCL ZTBGJMCR for several presentation sessions, the ZTBGFSES file must contain a list of the sessions to be loaded. * ZTG0163: xxxxxxxx: Error writing the expanded file: zzzzz. It is usually a space problem due to SMS management. * ZTG0164: Call to the reception exit yyyyyyyy * ZTG0165: User exit completed successfully * ZTG0166: xxxxxxxx: Error in user exit yyyyyyyy. R-C: zzzz. This message is shown if the reception exit returns a non-zero return code to Editran. The process is stopped. * ZTG0167: Editran session with an output buffer where there was none in the previous one. This error message is shown when, in an Editran presentation session with several Editran transmission sessions, it is detected that one of these sessions has no output buffer and another one (the next one in profile order) does have one. * ZTG0168: Reception buffer required in Editran sessions. This error message is shown when a reception request is made in an Editran presentation session that does not have a reception buffer in any of its associated transmission sessions. * ZTG0169: Key interface or Authentication Alg. missing in cryptography higher than 2.2. All Editran transmission sessions associated with the presentation that will encrypt/decrypt information using an external key management interface must have the same key interface ("on-line" program, "batch" program, and parameters). * ZTG0170: Editran session profile incompatible with Key Interface. Detected in Editran profiles that, despite having an external key management interface specified, do not have the parameters CRIPTOGRAFIA='S' and CAMBIO-CLAVE='N'. Editran endpoint authentication is mandatory, and there must be no key change when there is "batch" encryption/decryption according to a key interface. * ZTG0171: Buffer encrypted correctly. KEY-ID: XXXXXXXX. The presentation data corresponding to the current output buffer has been correctly encrypted, using the local exchange/"exporter" key with "Label" XXXXXXXX (the last 8 octets, different from blanks, of the 64 in the label identifying the key), as indicated by the external key interface specified in the profiles. * ZTG0172: Buffer decrypted correctly. KEY-ID: XXXXXXXX. The presentation data corresponding to the current reception buffer has been correctly decrypted, using the remote exchange/"importer" key with "Label" XXXXXXXX (the last 8 octets, different from blanks, of the 64 in the label identifying the key), as indicated by the external key interface specified in the profiles. * ZTG0173: XXXXXXXX: Key Interface error. RC=yyyyy, Reason=zzzzz. The "XXXXXXXX" external key management interface returns an error with return code "yyyyy" for reason "zzzzz". Consult the documentation corresponding to the key interface used for these codes. * ZTG0174: XXXXXXXX: Incompatible profiles for buffer decryption. A buffer has been received from the remote side, encrypted according to a cryptographic system defined by an external key management interface. That interface has not been specified in the profiles of the transmission session associated with this presentation. Most likely, those profiles were modified after the presentation was received. * ZTG0175: XXXXXXXX: Error encrypting the application file. * ZTG0176: XXXXXXXX: Error decrypting the application file. * ZTG0177: Application file encryption correct and completed. * ZTG0178: Application file decryption correct and completed. * ZTG0179: Editran sessions must have the same encryption versions. In an Editran presentation session with several EDITRAN transmission sessions, the cryptography version does not match across all Editran sessions. * ZTG0180: Expected remote Editran version is not the one received: ZZZZ. Check that the remote Editran version is correct. * ZTG0181: XXXXXXXX: Profile change after CSB load. Profiles cannot be modified once the data load has been performed. If this is necessary, states would have to be initialized, the profiles modified, and the data loaded again. * ZTG0182: Possible error in profile definition. Generational file. * ZTG0183: Inconsistent monitoring state in the presentation. * ZTG0184: Number of records to be written exceeds the capacity of the history. * ZTG0185: Monitoring error in post-proc. end of session in previous proc. * ZTG0186: PRESENTATION SESSION NOT LOADED. * ZTG0187: UNENCRYPTED PRESENTATION RECEIVED. The presentation session profile indicates that the information must be received encrypted and it comes in clear text. If the data is desired, it can be unloaded by modifying the reception session profile. * ZTG0188: PROFILE INCOMPATIBLE WITH BUFFER V2.2 ENCRYPTION. The cryptography of the presentation session profile is different from the one used by the sender. If the data is desired, it can be unloaded by modifying the reception session profile. * ZTG0189: PROFILE INCOMPATIBLE WITH APPLICATION FILE V4.0 ENCRYPTION. The cryptography of the presentation session profile is different from the one used by the sender. If the data is desired, it can be unloaded by modifying the reception session profile. * ZTG0190: PROFILE INCOMPATIBLE WITH APPLICATION FILE V3.0 ENCRYPTION. The cryptography of the presentation session profile is different from the one used by the sender. If the data is desired, it can be unloaded by modifying the reception session profile. * ZTG0191: XXXXXXXX: LOCK ERROR IN THE STATES FILE RC =ZZZZZ * ZTG0192:XXXXXXXX: UNLOCK ERROR IN THE STATES FILE RC =ZZZZZ * ZTG0193: ATTENDED BUFFER NOT SPECIFIED IN THE PROCEDURE. The buffer file with ddname “TAMPON01” is not specified in the procedure. * ZTG0194: ATTENDED BUFFER DIFFERENT FROM THE ONE SPECIFIED IN PROFILES. The procedure buffer dsname does not match the Editran profile one. * ZTG0195: ERROR IN THE CHARACTERISTICS OF THE ATTENDED BUFFER. The procedure buffer file is not a KSDS, does not have the proper key length, or its record length is incorrect. * ZTG0196: EXCI ERROR.RES: RRRRR REAS.: SSSSS ABEN:YYYY FUNC.:ZZZZZ. Error that occurred when accessing the EXCI interface for managing "C" type buffer files. * ZTG0197: EXCI ERROR.RES: RRRRR REAS.: SSSSS ABEN:YYYY FUNC.:ZZZZZ * Error that occurred when accessing the EXCI interface for managing "C" type buffer files or error that occurred when accessing the EXCI interface for notifying CICS messages. * ZTG0198: CICS ERROR.RES: RRRRR RES2: SSSSS FND.:YYYY FUNC.:ZZZZZ. Error that occurred in the CICS module for managing "C" type buffer files. FUNC is the function with which it was invoked. FND corresponds to the CICS command that gives the error. RES and RES2 are the RESP and RESP2 values resulting from the CICS command. * ZTG0199: XXXXXXXX: ABEND DETECTED: SSSS MOD.:YYYYYYYY FUNC.:ZZZZZ. ABEND occurred in the CICS module for managing "C" type buffer files. FUNC is the function with which it was invoked. MOD is the module in which the abend occurs. ABEND is the abend code. * ZTG0200: ERROR GENERATING SIGNATURE * ZTG0201: XXXXXXXX: Error opening file YYYYYYYY. F-S: ZZ * ZTG0202: XXXXXXXX: Error closing file YYYYYYYY. F-S: ZZ * ZTG0203: XXXXXXXX: Error reading file YYYYYYYY. F-S: ZZ * ZTG0204: XXXXXXXX: Error writing to file YYYYYYYY. F-S: ZZ * ZTG0205: XXXXXXXX: Error rewriting file YYYYYYYY. F-S: ZZ * ZTG0206: XXXXXXXX: Error deleting file YYYYYYYY. F-S: ZZ * ZTG0207: XXXXXXXX: Error allocating file YYYYYYYY. R-C: ZZZZ. There must be an extended message in ZTBGFPRI referring to a dynamic allocation, whose codes can be consulted in the constructor's manual "Requesting SVC 99 Functions". The most common cause is that there is not enough space on the volume to satisfy the request. * ZTG0208: XXXXXXXX: Error deallocating file YYYYYYYY. R-C: ZZZZ. Same as the previous one for a deallocation. * ZTG0209: XXXXXXXX: DCB file request error YYYYYYYY. R-C: ZZZZ. File characteristics are requested from the ZTBGB002 program and it returns an error return code. * ZTG0210: XXXXXXXX: INVALID INPUT PARAMETERS YYYYYYYY. The procedure's main program receives incorrect parameters. The most common cause is that the wrong procedures have been entered in the Editran profiles, for example, a pre-reception procedure instead of a post-emission one. * ZTG0211: xxxxxxxx: There is no cataloged application file. In a presentation emission load, none of the specified application files is found. * ZTG0212: xxxxxxxx: Error returned by UTILITY yyyyyyy R‑C:zzzz. In the procedure execution listing, the execution part of the specific utility can be found. It is usually IDCAMS due to lack of space when defining buffers or because they are open to CICS. * ZTG0213: XXXXXXXX: CSB RECORD DOES NOT EXIST IN YYYYYYYY. NREG = ZZZZZ * ZTG0214: XXXXXXXX: Buffer definition incompatible with load type. With cumulative load type, specific files are not allowed. * ZTG0215: XXXXXXXX: Cumulative load request for emission presentation. The load has been requested for a session with cumulative load type. * ZTG0216: XXXXXXXX: Load error due to transmission in progress. A buffer reload has been requested (cumulative load type), but transmission had already started. Wait until it finishes before reloading the buffer. * ZTG0217: XXXXXXXX: Incorrect application file characteristics. The application file format specified in ZTBGFCAR or the fields that define it (format, alphabet, compression, translation) do not have a valid format. * ZTG0218: XXXXXXXX: Number of application files exceeds the maximum allowed. More than 99 files are being loaded. Check the load type (cumulative) and the ones already loaded. * ZTG0219: XXXXXXXX: Key change with loaded buffer file With cumulative load type, new files are being loaded and the keys have been modified. * ZTG0220: XXXXXXXX: Duplicate reception application file Several reception files are being downloaded to different application files, but two repeated names are generated. Check the reception application file name and the single-file parameter in reception, then restart the download. Download to a single file or provide a name with enough '%' variables. * ZTG0221: XXXXXXXX: Invalid reception application file name. The name generated for an application file in reception does not conform to the syntax of an MVS DSNAME. Verify the reception application file name and restart the download. * ZTG0222: XXXXXXXX: Conversion table does not exist in ZTBGFTCO. A conversion table has been specified in Editran profiles and no table exists in the ZTBGFTCO file. * ZTG0223: Conversion table applied to application file. A conversion table has been applied to the application file before performing the load. * ZTG0224: Conversion table to apply according to alphabet does not exist. A conversion table has been specified in Editran profiles and it has not been applied because the original alphabet of the data (in emission) or the alphabet of the data in the file once translated (in reception) does not match it. * ZTG0225: XXXXXXXX: Not all file start/end variables are received * ZTG0226: NOT USED. * ZTG0227: NOT USED. * ZTG0228: NOT USED. * ZTG0229: XXXXXXXX: Empty emission file list. The list of files that must be included in the emission application file to perform the load is empty. * ZTG0230: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX. Error text indicated by the license control. Contact INDRA to update your license. * ZTG0231: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX. Error text in administrator cases. * ZTG0232: FILE ADAPTATION CORRECT AND COMPLETED. Informational text shown when the remote Editran version is > 4.0 and it passes through the translator-converter. * ZTG0233: ERROR NUMBER OF DATA FILES LESS THAN REQUIRED. Error in Editran/FF during load. Not as many files to load as specified in INPUT have been found. * ZTG0234: ERROR MISSING RECORD. TYPE 1 OR 2. Error in Editran/FF (RF parameter). No file collection option type was specified with INPUT (1) or with ZTBGFITS (2). * ZTG0235: ERROR MISSING RECORD. TYPE 1. Error in Editran/FF. The file enablement record was not found in INPUT. * ZTG0236: ERROR FILE RECORD TYPE 1 ENABLEMENT TYPE. Error in Editran/FF. The enablement type parameter has an incorrect value in INPUT. * ZTG0237: ERROR SIGNATURE NUMBER OF FILE RECORD TYPE 1. Error in Editran/FF. The signature number parameter has an incorrect value in INPUT. * ZTG0238: ERROR RECORDING TYPE OF FILE RECORD TYPE 1. Error in Editran/FF. The recording type parameter has an incorrect value in INPUT. * ZTG0239: ERROR EXISTING FILE COUNT OF FILE RECORD TYPE 1. Error in Editran/FF. The existing file count parameter has an incorrect value in INPUT. * ZTG0240: NUMBER OF FILES TO LOAD GREATER THAN 99. Error in Editran/FF. There are more than 99 files to load. * ZTG0241: ERRONEOUS INPUT PARAMETERS. Error in Editran/FF. Incorrect input parameters to the procedure. * ZTG0242: THERE ARE EMISSION FILES IN PROFILES. Error in Editran/FF. Not used. * ZTG0243: ERROR SENDING ALARM. CHECK ALARM LOG. An alarm (external manager, e-mail or SMS) was attempted and failed. Check the alarm log. * ZTG0244: ERROR IN Editran/FF. CHECK JCL OUTPUT. Verify the job output. * ZTG0245: ERROR IN DOWNLOAD. NUMBER OF RECEIVED FILES GREATER THAN 99. More than 99 files have been received. Contact the remote side so that it loads at most 99 in the current presentation. * ZTG0246: FILE NOT LOADED. APPLICATION PROGRAM YYYYYYYY. R-C: ZZZZ. An error occurred while loading a file with Editran/IC when calling a pre-emission application program. Check that program in the Editran profiles. * ZTG0247: XXXXXXXX: HISTORICAL CONFIRMATION DB FULL. YYYYYYYY. When writing to the Editran/IC historical file, it is detected that it is full. Create a new segment. * ZTG0248: XXXXXXXX: HISTORICAL CONFIRMATION DB AT 90% YYYYYYYY. When writing to the Editran/IC historical file, it is detected that it is at 90 percent. * ZTG0249: FILE PROCESSED BY APPLICATION PROGRAM YYYYYYYY. R-C: ZZZZ. An error occurred while downloading a file with Editran/IC when calling a post-reception application program. Check that program in the Editran profiles. * ZTG0250: ONLY LOAD TYPE N IS ALLOWED FOR THIS SESSION PROFILE. Only normal load is allowed in the session profile. * ZTG0251: RECEIVED CONFIRMATION FILE WITH UNKNOWN VERSION. In Editran/IC, when downloading the confirmation file, it is detected that the version is incorrect. * ZTG0252: RECEIVED INCORRECT CONFIRMATION FILE (see display). In Editran/IC, when downloading the confirmation file, it is detected that it is incorrect. Restart the session at both ends. * ZTG0253: XXXXXXXX: ERROR VALIDATING SIGNATURE. RC=YYYYY REASON=ZZZZZ. In Editran/IC, when downloading the confirmation file, it is detected that it is incorrect during signature validation. * ZTG0254: INCORRECT CONFIRMATION FILE (Number of files). In Editran/IC, when generating the confirmation file or when downloading it, it is detected that the number of files is incorrect. * ZTG0255: IC PRESENTATION TYPE (CSB HEADER) DOES NOT MATCH PROFILES. It is detected in a download that the indicated presentation type does not match the one expected in profiles. Check the PRESENTATION-TYPE parameter in the Editran profile. * ZTG0256: IC SESSION STATUS MODIFICATION CORRECT AND COMPLETED. Statuses have been modified in an Editran/IC session. * ZTG0257: REQUEST FOR IC STATUS MODIFICATION. P= XXXXXXXX. A status modification has been requested in an Editran/IC session. * ZTG0258: NOT USED. * ZTG0259: ERROR IN VALIDATION OF HISTORICAL FILE MAC. When validating the Editran/IC historical file, it is detected that it may have been tampered with. * ZTG0260: XXXXXXXX: HISTORICAL CONF. FILE FULL. YYYYYYYY. When writing to the Editran/IC historical file, it is detected that it is full. Create a new segment. * ZTG0261: XXXXXXXX: HISTORICAL CONF. FILE AT 90% YYYYYYYY. When writing to the EDITRAN/IC historical file, it is detected that it is at 90 percent. * ZTG0262: NOT USED. * ZTG0263: NOT USED. * ZTG0264: NOT USED. * ZTG0265: XXXXXXXX: FILE INTEGRITY FAILURE- YYYYYYYY. The API that controls the integrity of IC statuses detects a file with an incorrect hash or signature. * ZTG0266: PROCEDURE OR JCL HAS BEEN STARTED: XXXXXXXX. This message is an informational one issued from batch autooperator (ZTBGBUOP), when the request file specifies that a procedure-JCL should be triggered. It is used to know the name of the procedure-JCL launched. * ZTG0267: NOT USED. * ZTG0268: APPLICATION WITH FILE-QUEUE LOADING IS INACTIVE. Verify the file-queue profile that has the activity "active". * ZTG0269: THE LOAD CANNOT BE PERFORMED, THERE ARE FILES IN EMISSION. Wait until the current transmission finishes. * ZTG0270: THE PROFILE FOR PROCESSING BY FILE QUEUES DOES NOT EXIST. You must create the record in file queues. * ZTG0271: THE PRESENTATION SESSION DOES NOT HAVE LOAD TYPE "Q". Check the presentation profile. * ZTG0272: FILE PREVIOUSLY SAVED AND PENDING EMISSION : zzzz. An attempt is made to load a file that has already been loaded previously. * ZTG0273: ENCRYPTED SUBSYSTEM DIFFERENT FROM PROFILE: YYYYYYYY. The version of the exchanged keys or the subsystem is different between the received file and the presentation profile. * ZTG0274: THE LOAD CANNOT BE PERFORMED, IT DOES NOT MEET THE DEPTH CRITERION. * ZTG0275: REMOTE DOWNLOAD COMPLETED. The remote download has been confirmed. * ZTG0276: DOWNLOAD CONFIRMATION REQUEST. Confirmation of the download is requested from the remote side. * ZTG0277: CONFIRMATION NOT ALLOWED BY PROFILES. The remote side requests download confirmation, but the local profile does not allow it. --- # 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-comun-z-os-en/interfaz-generica-de-aplicacion/anexo-a.-mensajes-de-onesait-editran.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.