D–F

This group includes messages for the Control-M for z/OS, Control-M/Analyzer, Control-D, Control-O, Control-V, and IOA products.

DAS messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages DAS600 through DAS6xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

DAS613I DELETE OF ARCHIVED SYSOUTS STARTEDLink copied to clipboard

Explanation: This information message indicates that the New Day procedure started deleting archived SYSDATA sysouts.

Corrective Action: No action is required.

DAS614I DELETE OF ARCHIVED SYSOUTS ENDEDLink copied to clipboard

Explanation: This information message indicates that the New Day procedure finished deleting archived SYSDATA sysouts.

Corrective Action: No action is required.

DAS615W DELETION OF `num` ARCHIVED SYSOUT DATASET(S) FAILEDLink copied to clipboard

Explanation: Some Archived Sysout Data Sets were not deleted by the Control-M New Day procedure or during compression of the Control-M Active Jobs file.

This message follows other messages that explain the nature of the error for each archived sysout data set.

The New Day procedure or CTMCOP utility continues processing.

Corrective Action: See the messages that precede this message for the reasons for deletion failure.

DAS616E INVALID CARD IN THE "DASCRLST" FILE - `data`Link copied to clipboard

Explanation: During deletion of unneeded SYSDATA, a record describing archived SYSDATA contained invalid information. Control-M creates records with data describing SYSDATA to be deleted.

This record is skipped. Processing continues.

Corrective Action: Save the console and job output listing, and contact BMC Customer Support for assistance.

DAS617I `dsn` ARCHIVED DATASETS DELETEDLink copied to clipboard

Explanation: This information message indicates that the FORMAT or COPY process deleted SYSDATA files.

Corrective Action: No action is required.

DAS617E number SYNTAX ERRORS WERE DETECTED IN THE SCRATCH LIST (JOBLIST DATA SET)Link copied to clipboard

Explanation: This error message indicates that syntax errors were found in the scratch list.

Corrective Action: Manually delete all DSN names with syntax errors from the scratch file.

DAS618W COMPRESS OF JOBLIST NOT PERFORMEDLink copied to clipboard

Explanation: This warning message indicates that compression of JOBLIST was not performed.

Corrective Action: If this message is accompanied by message DAS617E, perform the corrective action for that message. Otherwise, no action is required.

Messages DASL00 through DASLxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

DASL71E INVALID RECORD FOUND ON AJF - FILE USAGE VERIFICATION SKIPPEDLink copied to clipboard

Explanation: The CDAM file deletion utility detected an invalid record type when verifying the CDAM records in the Active Jobs file (AJF). Before deleting a CDAM file, the CDAM file deletion utility verifies that the file names in the JOBLIST file are not referenced by any jobs in the AJF.

Verification of the AJF is aborted, and deletion of CDAM files proceeds based on previous checks of the AJF.

Corrective Action: Check the integrity of the AJF with the IOAVERFY utility.

DCI messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages DCID00 through DCIDxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DCIDA0I CTDCITSB PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err`Link copied to clipboard

Explanation: This information message indicates that the CTDCITSB program failed due to an internal error. The CTDCITSB program builds a temporary storage queue containing data from input CDAM files for transfer to a PC using the CICS 3270-PC file Transfer Program.

Where the error is a result of an EXEC CICS command, func indicates the function code and err indicates the error code.

The CTDCITSB program stops executing and a CICS transaction dump is produced.

Corrective Action: Check the dump and any relevant messages in the system log. If the problem is related to CICS customization, or to storage violations as a result of user transactions, correct the problem. Otherwise, have your CICS system programmer contact BMC Customer Support.

DCIDA1I CTDCITSB PROGRAM ABEND: ABEND= `abend`Link copied to clipboard

The CTDCITSB program stops executing and a CICS transaction dump is produced.

DCIDA2I INVALID INPUT DATA LENGTHLink copied to clipboard

Explanation: This information message indicates that the CTDCITSB program detected an error in the input data while processing input data for transaction DPCT. The correct format for data for transaction DPCT is DPCT dsn, where dsn is the name of the CDAM file to be transferred to the PC.

The CTDCITSB program stops executing.

Corrective Action: Verify that in the GOTOCICS.SCR script file, the DPCT transaction is correctly specified, and that a valid data set name is included in the data. If you cannot determine the cause of the error, have your CICS system programmer contact BMC Customer Support for assistance.

DCIDA3I INVALID INPUT DATA SPECIFIEDLink copied to clipboard

Explanation: This information message indicates that the CTDCITSB program detected an error in the input data while processing input data for the DPCT transaction. The correct format for data for the DPCT transaction is DPCT dsn, where dsn is the name of the CDAM file to be transferred to the PC.

The CTDCITSB program stops executing.

DCIDA4I DDNAME= `ddName` NOT DEFINED IN FCTLink copied to clipboard

Explanation: This information message indicates that the CICS FCT does not contain an entry DD name that can be used by the CTDCITSB program to read the CDAM file in order to set up Control-D/WebAccess Server file transfer.

The CTDCITSB program allocates the CDAM file in CICS using the DD name convention specified by ddName. The allocated file is then read, using standard CICS BDAM file access. Therefore, an entry must exist in the CICS FCT for the CDAM files.

The CTDCITSB program stops executing.

Corrective Action: Define at least one FCT entry in the format indicated by ddName, where the first five characters are a fixed prefix, followed by three digit numbers in ascending order, beginning with 000. For a full description of the required FCT definitions, see the $$DOCDPC member in the IOA CICSSAMP library.

DCIDA5I CONCURRENT USER LIMIT REACHED - TRY LATERLink copied to clipboard

Explanation: This information message indicates that the maximum number of CICS FCT entries defined for Control-D/WebAccess Server file transfer was reached. The CTDCITSB program attempted to initiate a file transfer session, but found that there were no file transfer FCT entries available for use.

The CTDCITSB program stops executing.

Corrective Action: Wait until the current file transfer sessions have ended. If more concurrent sessions are required, contact your CICS system programmer for assistance.

DCIDA6I FILE IS DISABLED - CANNOT BE ACCESSEDLink copied to clipboard

Explanation: This information message indicates that the CDAM file allocated by the CTDCITSB program to a DD name defined in the CICS FCTfile for Control-D/WebAccess Server file transfer was disabled, and could not be opened for processing.

The CTDCITSB program stops executing.

Corrective Action: Make sure that all FCT entries used for Control-D/WebAccess Server file transfer are enabled.

DCIDA7I SECURITY AUTHORIZATION REQUIRED FN= `func`Link copied to clipboard

Explanation: This information message indicates that the CTDCITSB program could not perform the func function because the necessary security authorization was not available.

The CTDCITSB program stops executing.

Corrective Action: Contact your CICS system programmer to define the correct security level in the CICS PCT entry of the DPCT and DPCC transactions using the RSL parameter.

DCIDA8I I/O ERROR OCCURRED DURING FILE ACCESSLink copied to clipboard

Explanation: This information message indicates that an I/O error occurred while attempting to read a CDAM file. This error message is issued by the CTDCITSB program, while it is reading a CDAM file in preparation for transfer to the PC.

The CTDCITSB program stops executing.

Corrective Action: Verify that the file being accessed is a CDAM file and that the contents of the file have not been corrupted. If possible, correct the problem. If the error persists, have your CICS system programmer contact BMC Customer Support.

DCIDA9I I/O ERROR ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: This information message indicates that an I/O error occurred while attempting to write to the CICS Temporary Storage file. This error message is issued by the CTDCITSB program, which writes the data from a CDAM file to CICS Temporary Storage in preparation for transfer to the PC.

Possible causes are:

invalid record size
CICS customization error
file corruption

The CTDCITSB program stops executing.

Corrective Action: Check the status of the Temporary Storage file, and, if possible, correct the problem. If the error persists, contact BMC Customer Support.

DCIDB0I NO SPACE ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: This information message indicates that a NOSPACE condition occurred during an attempt to write to the CICS Temporary Storage file. This error message is issued by the CTDCITSB program, which writes the data from a CDAM file to CICS Temporary Storage in preparation for transfer to the PC.

The CTDCITSB program stops executing.

Corrective Action: Delete unnecessary records from the Temporary Storage file or increase the file size.

DCIDB1I FILE PROCESSING COMPLETELink copied to clipboard

Explanation: This information message indicates that the CDAM file was successfully placed in Temporary Storage. It is now ready for transfer to the PC by means of the CICS 3270-PC file Transfer Program.

Corrective Action: No action is required.

DCIDB2I QUEUE DELETION PROCESSING COMPLETELink copied to clipboard

Explanation: This information message indicates that transaction DPCC has successfully deleted the Temporary Storage Queue used for transferring the CDAM file to the PC.

Corrective Action: No action is required.

DCIDB3I ERROR INVOKING DYNAMIC ALLOCATION SUBTASK. INLINE SVC WILL BE USEDLink copied to clipboard

Explanation: This information message indicates that an error occurred during an ATTACH of a dynamic allocation subtask. The CTDCITSB program, which writes the data from a CDAM file to CICS Temporary Storage in preparation for transfer to the PC, issues this message.

The dynamic allocation SVC is invoked from the CTDCITSB mainline program.

Corrective Action: Check the CICS job log for any additional messages. If the cause of the error cannot be determined, have your CICS system programmer contact BMC Customer Support for assistance.

DCIDB4I DYNAMIC ALLOCATION ERROR= `rc error reason`Link copied to clipboard

Explanation: This information message indicates that the CTDCITSB program attempted to allocate a CDAM file in CICS. However, an error occurred during file allocation processing. The specified return code (rc), error, and reason are produced by the dynamic allocation routine.

The CTDCITSB program stops executing.

Corrective Action: For an explanation of the return codes, see the IBM manual MVS Programming: Authorized Assembler Services Guide. Contact your CICS system programmer for assistance if necessary.

DCIDB5I DYNAMIC UNALLOCATION ERROR= `rc err rsn`Link copied to clipboard

Explanation: This information message indicates that the CTDCITSB program attempted to deallocate a CDAM file in CICS. However, an error occurred during file deallocation processing. The specified return code (rc), err, and rsn are produced by the dynamic allocation routine.

The CTDCITSB program stops executing.

DCIDB6I FILE OPEN ERROR: EIBFN= `func` EIBRCODE= `errCode`Link copied to clipboard

Explanation: This information message indicates that an error occurred while attempting to open a CDAM file allocated to CICS. This error message is issued by the CTDCITSB program, which writes the data from a CDAM file to CICS Temporary Storage in preparation for transfer to the PC.

The CTDCITSB program stops executing.

Corrective Action: Check the appropriate CICS manual for an explanation of error errCode for function func. If the cause of the error cannot be determined, have your CICS system programmer contact BMC Customer Support.

DCIDB7I FILE CLOSE ERROR: EIBFN= `func` EIBRCODE= `errCode`Link copied to clipboard

Explanation: This message indicates that an error occurred while attempting to close a CDAM file allocated to CICS. This error message is issued by the CTDCITSB program, which writes the data from a CDAM file to CICS Temporary Storage in preparation for transfer to the PC.

The CTDCITSB program stops executing.

Corrective Action: Check the appropriate CICS manual for an explanation of the errCode error for the func function. If the cause of the error cannot be determined, have your CICS system programmer contact BMC Customer Support for assistance.

DCIDB8I UNABLE TO LOAD CTDPARMLink copied to clipboard

Explanation: This information message indicates that the CTDCITSB program failed to load CTDPARM, because CTDPARM was disabled or was not defined in the CICS PPT. The CTDCITSB program builds the Temporary Storage Queue containing data from input CDAM files for transfer to a PC using the IBM CICS 3270-PC file Transfer Program. CTDCITSB attempted to load the module because it requires some data from CTDPARM.

The CTDCITSB program stops executing.

Corrective Action: Check that the CTDPARM program is enabled, and that it is correctly defined in the CICS PPT. For more information, refer to the installation instructions in the IOA CICSSAMP library.

DCIDB9I TRANSACTION `transid` NOT RECOGNIZEDLink copied to clipboard

Explanation: This information message indicates that transaction transid is not recognized by the CTDCITSB program. The CTDCITSB program builds a temporary storage queue containing data from input CDAM files for transfer to a PC using the IBM CICS 3270-PC file Transfer Program.

The CTDCITSB program stops executing.

Corrective Action: Check that the correct transactions are defined for the CTDCITSB program. The required transactions are DPCT and DPCC. For more information, refer to the installation instructions in the IOA CICSSAMP library.

DDI messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages DDIG00 through DDIGxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DDIG01I UTILITY CTDDIG STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDDIG utility started normally.

The CTDDIG utility checks the integrity of the following types of User Report List files:

Active
Permanent
History
Migration

Corrective Action: No action is required.

DDIG02E ERROR DETECTED IN `func` RC= `rc` DURING ACCESS TO IOA ACCESS METHOD FILELink copied to clipboard

Explanation: The CTDDIG utility detected an internal error while accessing the IOA Access Method (IAM) file.

In this message, func is the function that was executing when the error occurred.

The requested function func is not performed.

Corrective Action: Note the values of func and rc and contact BMC Customer Support.

DDIG03I file INDEX ENTRY DETECTED WITHOUT DATA RECORDLink copied to clipboard

Explanation: While checking the integrity of the User Report List file, the CTDDIG utility found an index record without a corresponding data record.

In this message, file is name of the IOA Access Method component.

The problematic index record is printed out.

Corrective Action: Rebuild the index of the User Report List file.

DDIG04I INDEX ENTRY DOES NOT MATCH DATA RECORD.Link copied to clipboard

Explanation: The CTDDIG utility reads the User Report List file to determine if either a data record exists without an index to this record, or an index record exists without a corresponding data record. If such a index or data record is found, this message is issued.

The problematic index and data records are printed out.

Corrective Action: Rebuild the index of the User Report List file.

DDIG05I DATA RECORD DETECTED WITHOUT `file` INDEXLink copied to clipboard

Explanation: While checking the integrity of the User Report List file, the CTDDIG utility found a data record without a corresponding index record.

In this message, file is name of the IOA Access Method component.

The problematic data record is printed out.

Corrective Action: Rebuild the index of the User Report List file.

DDIG06I UTILITY CTDDIG ENDED.Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility ended.

Corrective Action: No action is required.

DDIG07E ERROR DETECTED IN `func` RC= `rc` DURING ACCESS TO IOA ACCESS METHOD FILELink copied to clipboard

Explanation: The CTDDIG utility detected an internal error while accessing the IOA Access Method (IAM) file.

In this message, func is the function that was executing when the error occurred.

The requested function (func) is not performed.

Corrective Action: Note the values of func and rc and contact BMC Customer Support.

DDIG09S INVALID VALUE IN PARAMETER DBFILE. VALID VALUES ARE: ACT, PRM, HST, MIG, MG1-MG9.Link copied to clipboard

Explanation: An attempt has been made to run the CTDDIG utility when the DBFILE parameter value was invalid or missing.

The DBFILE parameter in the CTDDIG utility must be set to one of the following values:

ACT - Active User file
PRM - Permanent User file
HST - History User file
MIG - Migrated User file
MG n - Migrated User file partition, where n is the partition number

The CTDDIG utility terminates.

Corrective Action: Insert the appropriate valid value in the DBFILE parameter and rerun the utility.

DDIG0AI DUPLICATE RECORD FOUND IN `file` DATA FILELink copied to clipboard

Explanation: This information message indicates that a duplicate record has been found in the data file.

In this message, file is name of the IOA Access Method component.

Duplication of a record in the data file may be the result of a computer malfunction.

The problematic record is printed out. The CTDDIG utility continues processing.

Corrective Action: No action is required.

DDIG0CE INVALID PARAMETER, VALID MODE PARAMETER: TEST, TESTMRK OR CHANGELink copied to clipboard

Explanation: A MODE parameter error was detected for the CTDDIG utility.

The CTDDIG utility terminates with a condition code of 28.

Corrective Action: Correct the JCL and rerun the job. The MODE parameter in the CTDDIG utility must be set to one of the following values:

TEST - Messages are issued about detected problems, but errors are not fixed. Default.
TESTMRK - Messages are issued about detected problems, but errors are not fixed. If no errors are detected, all alternative index components are marked as ready to use.
CHANGE - Messages are issued and errors are fixed. If no errors are detected, all alternative index components are marked as ready to use.

DDIG10I NUMBER OF RECORDS READ FROM DATA FILE= `num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility read num records from the IOA Access Method data file.

Corrective Action: No action is required.

DDIG11I NUMBER OF INDEXES READ FROM INDEX `file` FILE= `num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility read num records from the IOA Access Method index file.

In this message, file is name of the IOA Access Method component.

Corrective Action: No action is required.

DDIG12I NUMBER OF DUPLICATE RECORDS IN `file` DATA FILE= `num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility found num duplicate records in the IOA Access Method data file.

In this message, file is name of the IOA Access Method component.

Corrective Action: No action is required.

DDIG13I NUMBER OF RECORDS DELETED FROM `file` DATA FILE= `num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility deleted num records from the IOA Access Method data file.

In this message, file is name of the IOA Access Method component.

Corrective Action: No action is required.

DDIG14I NO ERRORS DETECTED.Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility ended with no errors detected.

Corrective Action: No action is required.

DDIG15I NUMBER OF INDEXES TO BE UPDATED IN `file` FILE= `num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility found in the IOA Access Method index file num records that are to be updated.

In this message, file is name of the IOA Access Method component.

Corrective Action: No action is required.

DDIG16I NUMBER OF INDEXES TO BE DELETED FROM `file` FILE= `num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility found num records that are to be deleted from the IOA Access Method index file.

In this message, file is name of the IOA Access Method component.

Corrective Action: No action is required.

DDIG17I NUMBER OF INDEXES TO BE ADDED TO `file` FILE= `num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIG utility found num records that are to be added to the IOA Access Method index file.

In this message, file is name of the IOA Access Method component.

Corrective Action: No action is required.

DDIG18I file INDEX IS MARKED AS READY TO USELink copied to clipboard

Explanation: This information message indicates that the CTDDIG utility checked or repaired, or both, the alternative index component and marked it as ready to use in a report list search.

In this message, file is the name of an IOA Access Method component.

Corrective Action: No action is required.

DDR messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages DDRJ00 through DDRJxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

DDRJ81I UTILITY IOADDR STARTEDLink copied to clipboard

Explanation: This information messages indicates that IOADDR utility started.

Corrective Action: No action is required.

DDRJ82I UTILITY IOADDR ENDEDLink copied to clipboard

Explanation: This information message indicates that the IOADDR utility ended.

Corrective Action: No action is required.

DDRJ83S INVALID PARAMETER SPECIFICATIONLink copied to clipboard

Explanation: The parameter passed to the IOADDR utility was either invalid or missing.

The IOADDR utility terminates.

Corrective Action: Verify that a valid DSNAME was passed as a parameter to the IOADDR utility.

DDRJ84S OPEN OF FILE "SYSPRINT" FAILEDLink copied to clipboard

Explanation: Opening of the print file failed.

Possible causes are:

The SYSPRINT DD statement is missing from the step.
The file allocated to the SYSPRINT DD statement is not a valid print file.

The IOADDR utility terminates.

Corrective Action: Correct the JCL for the IOADDR utility so that it contains a valid SYSPRINT DD statement.

DDRJ85S OPEN OF CONTROL FILE FAILED. DDNAME " `ddName` "Link copied to clipboard

Explanation: The IOADDR utility failed to open one of its control files.

The IOADDR utility terminates.

Corrective Action: Correct the JCL for the IOADDR utility so that it has a correct control member allocated to it.

DDRJ86S ALLOCATION FOR MEMBER `memName` LIBRARY `lib` FAILEDLink copied to clipboard

Explanation: Allocation of the specified member failed because the member does not exist in the specified library or is inaccessible.

The IOADDR utility terminates.

Corrective Action: Verify that the @IDCNTL control member contains a valid library and member name for each user.

DDRJ87S ALLOCATION FOR TABLE FAILEDLink copied to clipboard

Explanation: Allocation of one of the IOADDR members failed, because one of the members pointed to by @IDCNTL does not exist or is inaccessible.

The missing member is skipped. Processing continues for the following members.

Corrective Action: Verify that the @IDCNTL control member contains a valid library and member name for each user.

DDRJ88S BAD OP-CODE " `op_code` "Link copied to clipboard

Explanation: A user table contained an invalid operation code.

The event definition with the bad OP-CODE is skipped. Processing continues with the following entries.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

DDRJ89S LOAD FAILED FOR MEMBER " `memName` "Link copied to clipboard

Explanation: Load of one the IOA modules failed.

The IOADDR utility terminates.

Corrective Action: Verify that your STEPLIB DD statement points to the IOA LOAD library.

DDRJ8AW NO TRIGGERED EVENTS MATCHED TRIGGER `dsn`Link copied to clipboard

Explanation: A CONNECT DIRECT request dsn did not match any of the triggered events specified in the @@IDCNTL event lists.

No further action is taken in respect of this CONNECT DIRECT request.

Corrective Action: Check whether any trigger event in the event lists specified in the @@IDCNTL parameter member matches the trigger dsn. If you wish, add a trigger event that matches the dsn, then repeat the CONNECT DIRECT request.

DDRJ8BW NO SUCCESSFULLY TRIGGERED EVENTS WERE PROCESSED FOR TRIGGER `dsn`Link copied to clipboard

Explanation: During the processing of a CONNECT DIRECT request, no triggered events were successfully processed.

If a file-in-use condition occurs during the execution of a CONNECT DIRECT request, Control-M may try again to execute it, depending on the values set for the FORCE#RT and FORCE#WI installation parameters.

For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

DDRJ90S ACCESS RC= `rc` FOR LIBRARY `lib` MEMBER `memName`Link copied to clipboard

Explanation: An error occurred in the IOADDR utility when reading the memName member from the lib PDS library. The return code (rc) describes the reason for the error.

Possible return codes are:

Return Code	Explanation
4	Premature end of file.
8	Storage allocation error.
12	Member not found.
16	Data set name is not the name of a PDS library.
20	Data set is not a fixed format dataset.
24	Logical record length of the file is not 80.
28	Data set in use.
32	Internal error.
36	Data set is not cataloged.
40	Data set allocation failed.
44	Invalid request.
48	Internal error.
52	Error accessing the directory.

The entry that caused the error is skipped.

Corrective Action: Correct the cause of the error, and retry the operation. In case of an internal error, supply BMC Customer Support with a copy of the input file and the parameters specified for the IOADDR utility.

DDRJ91S INSUFFICIENT STORAGE FOR PROCESSLink copied to clipboard

Explanation: The IOADDR utility failed to allocate storage for its operation.

The IOADDR utility terminates.

Corrective Action: Increase the REGION size.

DDRJ92S JOB `jobName` NOT FOUND IN TABLE `tableName` OF LIB `lib`Link copied to clipboard

Explanation: A request to order a job could not be fulfilled because the job did not exist in the scheduling table.

The event definition pointing to the missing job is skipped. Processing continues with the subsequent entries.

Corrective Action: Add the missing definition to the specified scheduling table.

DDRJ93S BAD DATE `date` SPECIFIEDLink copied to clipboard

Explanation: The order date specified in the event definition is invalid.

The event definition with the bad date is skipped. Processing continues with the subsequent entries.

Corrective Action: Correct the date in the event definition.

DDRJ94I USER: `userId` TABLE: `tableName` LIBRARY: `lib`Link copied to clipboard

Explanation: This information message completes a preceding message stating the reason for the error.

Corrective Action: Use this information to locate the cause of the error.

DDRJ9CE QNAME TABLE ENTRY ERROR. FLAG= `num` STC= `stcName` STR= `structName` LSN= `logStreamName` HLQ= `hiLevelQualifier`Link copied to clipboard

Explanation: The IOADDC program found an invalid entry in the QNAME table for the QNAME specified by the IOADDC request.

The variables in this message are:

num - a hexadecimal number representing the communication vehicle used to transfer the IOADDC input trigger to Control-MPossible values are:
- 40 - use the MVS system logger
- 20 - call the IOADDR routine directly
stcName - the name of the started task
structName - the name of the CF structure
logStreamName - the name of the log stream
hiLevelQualifier - the high-level qualifier of the log stream file

The IOADDC request is aborted.

Corrective Action: Rerun the IOADDI job for the specified IOA installation, and verify that it was successful.

DDRJ9DE `cbName` CONTROL BLOCK NOT FOUND - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

Explanation: The IOADDC program was unable to find the cbName system-wide control block.

The IOADDC request is aborted.

Corrective Action: Run the IOADDI job for each IOA installation that requires it.

DDRJ9EE `qName` QNAME TABLE ENTRY NOT FOUND - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

Explanation: The IOADDC program was unable to find an entry in the QNAME table that matched the qName QNAME.

The IOADDC request is aborted.

Corrective Action: Rerun the IOADDI job for the specified IOA installation, and verify that it was successful.

DDRJA1I IOADDS: `dsn`Link copied to clipboard

Explanation: This information message indicates that the IOADDC utility was activated in an environment with no authorization to issue modify commands to the IOADDS started task. It can be used to issue a MODIFY command to IOADDS by a console automation product, such as Control-O.

Execution continues.

Corrective Action: If you have already defined this message to your console automation software, no intervention is required. Otherwise, make sure either that IOADDC is activated in an APF-authorized environment, or that measures have been taken to handle this message.

DDRJA2S IOADDS FUNCTIONAL SERVER IS NOT OPERATIONAL. DATASET TRIGGERING REQUESTS MAY BE LOST.Link copied to clipboard

Explanation: The IOADDS started task was not operational during an IOADDC-related data set event. The IOADDC utility attempted to start the IOADDS started task automatically, but IOADDS was not initialized.

The event that triggered this action is not processed.

Corrective Action: Check the output of the IOADDS utility. It should point to the problem which prevented the initialization. Proceed accordingly.

DDRJA3I AJF IS BEING FORMATTED. IOADDS WILL WAIT TILL FORMAT FINISHES.Link copied to clipboard

Explanation: The CONNECT DIRECT interface module has attempted to order a job as a result of a user request but the AJF is currently being formatted.

The interface module waits until the formatting has completed and then retries the request.

Corrective Action: No action is required.

DDRJA4S SYSPLEX TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

Explanation: The CONNECT DIRECT interface module has attempted to read the Sysplex table and failed.

Possible causes are:

The Sysplex table is not in the PARM library
The Sysplex table has an invalid internal format.

The interface module aborts the request.

Corrective Action: Do one of the following, then retry the request:

If the Sysplex table is not in the PARM library, determine why, and correct the problem.
If the internal format of the Sysplex table is invalid, correct the problem.

DDRJA5S CMMPLEX TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

Explanation: The CONNECT DIRECT interface module has attempted to read the CMMPLEX table and failed.

Possible causes are:

The CMMPLEX table is not in the PARM library.
The CMMPLEX table has an invalid internal format.

The interface module aborts the request.

Corrective Action: Do one of the following, then retry the request:

If the CMMPLEX table is not in the PARM library, determine why, and correct the problem.
If the internal format of the CMMPLEX table is invalid, correct the problem.

DDRJA6E SYSTEM LOGGER REQUEST `log_req` FAILED: R15= `r15` RETURN= `rc` REASON= `rsn` Link copied to clipboard

Explanation: One of the following System Logger requests failed:

DEFCFS, IXGINVNT (define the coupling facility structure)
DEFLGS, IXGINVNT (define the log stream)
CONLGS, IXGCONN (connect to the log stream)
WRITEL, IXGWRITE (write a log stream log block)
DISLGS, IXGCONN (disconnect from log stream)
DELLGS, IXGINVNT (delete the log stream)
DELCFS, IXGINVNT (delete coupling facility structure)

r15 has one of the following values:

08 - minor System Logger request error
12 - intermediate System Logger request error
16 - major System Logger request error
20 - permanent System Logger request error
28 - operating system does not support System Logger interface

For information about the System Logger request that failed (log_req), and the return and reason codes (r15, rc and rsn), see the IBM manual MVS Programming: Assembler Services Reference.

Corrective Action: No action is required.

DDRJA7E NAME/TOKEN SERVICES REQUEST `serviceRequest` FAILED: R15= `r15`Link copied to clipboard

Explanation: One of the following MVS name or token services requests failed:

CREATE, IEANTCR (name or token create)
RETRIEVE, IEANTRT (name or token retrieve)
DELETE, IEANTDL (name or token delete)

For information about the service request that failed (serviceRequest), and the return code (r15), see the IBM manual MVS Programming: Assembler Services Reference.

Corrective Action: No action is required.

DDRJA8E PARAMETER (DATA SET NAME) LENGTH ERROR - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

Explanation: The data set name used as a CONNECT DIRECT interface trigger was either not specified, or longer than 44 characters.

The interface module aborts the request.

Corrective Action: Set the data set name trigger to a value comprised of 44 characters or less, and retry the request.

DDRJA9S IOACPRM TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

Explanation: The CONNECT DIRECT interface module has attempted to read the IOACPRM table and failed.

Possible causes are:

The IOACPRM table is not present in the PARM library
The table has an invalid internal format.

The interface module aborts the request.

Corrective Action: Do one of the following, then retry the request:

If the IOACPRM table is not in the PARM library, determine why, and correct the problem.
If the internal format of the IOACPRM table is invalid, correct the problem.

DDRJAAS SYSTEM LOGGER INTERFACE NOT ENABLED BY USER - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

Explanation: The system logger interface was not enabled in the IOACPRM table.

The interface module aborts the request.

Corrective Action: Set the value of SYSTLOGR in the IOACPRM table to Y.

DDRJABW SYSTEM LOGGER INTERFACE NOT OPERATIVE - DATA SET TRIGGERING REQUEST PROCESSED BY IOADDRLink copied to clipboard

Explanation: The System Logger interface is not enabled (the SYSTLOGR parameter value in the IOACPRM parm member is set to 'N') so IOADDC cannot pass the data set name argument to Control-M by the System Logger.

Instead of passing the data set name argument to Control-M using the System Logger, IOADDC directly calls to IOADDR to trigger the corresponding data set event. For more information, see the Control-M chapter in the INCONTROL for z/OS Administrator Guide.

Corrective Action: If required, set up the System Logger interface. For information on setting up the System Logger, see the Control-M chapter in the INCONTROL for z/OS Installation Guide.

DDRJACI `qName` QNAME TABLE ENTRY SUCCESSFULLY REGISTEREDLink copied to clipboard

Explanation: The IOADDI job successfully registered the qName QNAME table entry.

Corrective Action: No action is required.

DDRJADE `cbName` CONTROL BLOCK CREATION ERROR - REGISTRATION ABORTEDLink copied to clipboard

Explanation: The IOADDI job was unable to build the cbName system-wide control block.

The IOADDI job does not register the required IOA installation.

Corrective Action: Rerun the IOADDI job for the required IOA installation, and verify that it was successful.

DDRJAEE NO AVAILABLE ENTRIES IN QNAME TABLE - REGISTRATION ABORTEDLink copied to clipboard

Explanation: The IOADDI job was unable to register the required IOA installation because no remaining QNAME table entries are available.

The IOADDI job does not register the required IOA installation.

Corrective Action: Delete any entries in the QNAME table that are no longer required. If all existing entries are required, prepare the Control-M monitor full output and contact BMC Customer Support.

DET messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages DETH00 through DETHxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

DETH51I LOGICAL CONNECTION IS INTERRUPTED WHILE THE ACTIVE JOBS FILE IS BEING FORMATTEDLink copied to clipboard

Explanation: This information message indicates that the logical connection between the Control-M Application Server and Control-M/Enterprise Manager (Control-M/EM) Workstation Gateway is temporarily suspended because the Active Jobs file is currently being formatted.

The workstation database is not up-to-date, and no requests issued by the Control-M/EM GUI will be handled, until the format of the Active Jobs file is completed.

Corrective Action: No action is required.

DETH52I LOGICAL CONNECTION RESUMED AFTER FORMAT OF THE ACTIVE JOBS FILELink copied to clipboard

Explanation: This information message indicates that the logical connection between the Control-M Application Server and Control-M/Enterprise Manager (Control-M/EM) Workstation Gateway has resumed because the process of formatting the Active Jobs file has finished.

The workstation database may now request synchronization, and other requests issued by the Control-M/EM GUI will now be handled.

Corrective Action: No action is required.

DETH53E FORMAT OF ACTIVE JOBS FILE ABENDEDLink copied to clipboard

Explanation: An abend occurred when the Active Jobs file (AJF) was last formatted. The New Day process did not finish OK. ECSGATE cannot work with the AJF, because the AJF might be corrupted.

The Control-M Application Server shuts down.

Corrective Action: Inform your INCONTROL administrator.

DETH55E FILE ALLOCATED TO DDNAME "DARESF" OR "DACNDF" IS NOT YOUR IOA SYNCHRONIZATION FILELink copied to clipboard

Explanation: The data set pointed to by the "DARESF" OR "DACNDF" DD statement is not your IOA Synchronization file. This error message is issued by the CTWDET Control-M Application Server program, and is due to one of the following:

The file allocated to the DARESF or DACNDF DD statement is not the IOA Synchronization file.
The file allocated to the DARESF or DACNDF DD statement is the IOA Synchronization file, but it is of a different version or from a different Control-M monitor.

The Control-M Application Server shuts down.

Corrective Action: Correct the JCL for the Control-M Application Server and restart it.

DETH56E THE NEW JOB RECORDS ARE INCOMPLETE. CONTINUATION RECORD IS MISSING. RBA `add`Link copied to clipboard

Explanation: The Control-M Application Server detected that a job on the Active Jobs file does not have all related continuation records.

In this message, add is the Relative Byte address of the problematic job.

The problematic job is ignored, meaning that it is not downloaded to Control-M/Enterprise Manager. The Application Server continues to work, handling other jobs.

Corrective Action: Have your system programmer call BMC Customer Support.

DETH57I ACTIVE JOBS FILE IS BEING FORMATTEDLink copied to clipboard

Explanation: This information message indicates that the Control-M Active Jobs File (AJF) is currently being formatted.

The Control-M Application Server holds updates. After formatting is finished, it executes a full download to the Control-M/Enterprise Manager.

Corrective Action: No action is required.

DETH58E DATA BASE UPDATES SENT TO THE WORKSTATION GATEWAY HAVE NOT BEEN CONFIRMED IN TIMELink copied to clipboard

Explanation: The Control-M Application Server sent database updates to the Control-M/Enterprise Manager (Control-M/EM) Workstation Gateway, but did not receive confirmation for them in time. This error message is issued by the CTWDET Control-M Application Server program, and is due to one of the following:

The Control-M/EM Workstation Gateway has stopped responding, due to an error condition in the software or hardware.
Responses are delayed because of poor performance.

Corrective Action: Check if the workstation is hanging and if there are any error messages at the workstation which indicate the cause of the problem. If the workstation is not hanging, there must be some performance bottleneck in the system. Try to determine whether this bottleneck is at the workstation side, in the communication media, or at the mainframe.

DETH59E CONFIRMATION SEQUENCE NUMBER ERROR. EXPECTED= `exp_num` RECEIVED= `rcv_num`Link copied to clipboard

Explanation: The Control-M Application Server has received an out of order confirmation of a database update.

This error message is issued by the CTWDET Control-M Application Server program. The Mainframe Gateway expects to receive confirmations for database updates in increasing order, but a confirmation with a sequence number of rcv_num has been received, when a confirmation with a sequence number of at least exp_num was expected.

The Control-M Application Server continues executing.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

DETH60W RUN NUMBERS `run_num1` TO `run_num2` OF `jobName` HAVE NOT BEEN CAPTUREDLink copied to clipboard

Explanation: The Control-M Application Server detected that during its last sleeping period it missed some events.

This message is issued by the CTWDET Control-M Application Server program. The Mainframe Gateway has detected that the run number of the jobName job in the Control-M Active Jobs file has changed by more than one during the Mainframe Gateway’s last sleeping period. This means that run numbers run_num1 to run_num2 of the job have not been captured by the Mainframe Gateway.

Corrective Action: Consider decreasing the SLEEPINT parameter in the relevant APSERVER statement in the ECAPARM member.

DETH61E DETECTOR INTERNAL ERROR TYPE `type`Link copied to clipboard

Explanation: The detector program detected an internal error. This error message is issued by the Control-M Application Server, and is due to reasons not in user control.

The Control-M Application Server shuts down.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

DETH67I DOWNLOAD PROCESS WILL TAKE PLACE SINCE < `rsnText` >Link copied to clipboard

Explanation: This information message indicates that a download will be executed, and the reason.

Possible causes of this message are:

The Control-M Active Jobs File (AJF) was formatted since the last Application Server cycle.
The Control-M Application Server received a STARTLINK modify command.

Possible values for rsnText are:

ACTIVE JOBS FILE WAS FORMATTED
STARTLINK COMMAND WAS ISSUED

The Control-M Application Server requests and will execute a full download to the Control-M/Enterprise Manager.

Corrective Action: No action is required.

DFG messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages DFG400 through DFG4xxLink copied to clipboard

This group includes messages for the Control-O product.

DFG410I ALLOCATION OF GLOBAL AUTOEDIT LIBRARY STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTODFG program that allocates the Global library.

Corrective Action: No action is required.

DFG411E INVALID PARAMETERS: parmsLink copied to clipboard

Explanation: The CTODFG program detected invalid parameters.

The program terminates with a return code of 08.

Corrective Action: Verify the parameters, correct them, and resubmit the utility.

DFG412W THIS CPU HAS SMFID `cpuSmfId` AND NOT `parmSmfId`Link copied to clipboard

Explanation: The SMFID of the CPU on which the CTODFG program is running (cpuSmfId) does not match the SMFID passed as a parameter to the program (parmSmfId).

No error is issued when the systems share the catalog, where the file is cataloged, and the disk, where the file was allocated.

The program terminates with a condition code of 04.

A problem starting Control-O monitor might occur when the systems do not share the catalogs or the disk. This usually occurs when the file should have been cataloged in the MASTER catalog of the target system (parmSmfId) and not the Master catalog of the system where the job was executed (cpuSmfId). In such a case, messages CTM686E and CTO458S are issued and Control-O monitor terminates with RC 8.

Corrective Action: Verify that the file was cataloged in the correct CATALOG. If it was not, DELETE the file and rerun the job on the correct system where parmSmfId and cpuSmfId are the same.

DFG416E DYNAMIC ALLOCATION ERROR RC=`rc`, ERROR=`rsn`, DSN=`dsn`Link copied to clipboard

Explanation: The CTODFG program failed while attempting to dynamically allocate the Global library.

The CTODFG program terminates with a condition code of 08.

Corrective Action: Refer to the IBM OS/390 Authorized Assembler Services Guide for an explanation of the return and reason codes.

DFG417E CTMMEM ERROR, RC=`rc`Link copied to clipboard

Explanation: The CTODFG program received the return code rc from the CTMMEM module while attempting to update the Global library. The error occurred when the CTODFG program attempted to create the $$GLOBAL member in the Global library.

Possible causes indicated by values of rc are:

08 - The region size is too small.
28 - The data set is in use.
32 - Internal error.
56 - The library is full or an abend occurred.
64 - The member already exists.

The CTODFG program terminates with a condition code of 08.

Corrective Action: If possible, correct the problem with the library, and resubmit the utility. If the error persists, contact BMC Customer Support.

DFG418E ALLOCATION OF GLOBAL AUTOEDIT LIBRARY FAILEDLink copied to clipboard

Explanation: Allocation of the Global library failed. This error message, which is issued by the CTODFG program, is preceded by another message detailing the reason for the failure.

The CTODFG program terminates with a condition code of 08.

Corrective Action: See the preceding message.

DFG419I ALLOCATION OF GLOBAL AUTOEDIT ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTODFG program successfully allocated the Global library.

Corrective Action: No action is required.

DFL messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages DFL0 through DFL0xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

DFL030I TAPE PULL UTILITY IS SUBMITTING JOBS WITH TYPRUN=SCANLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Tape Pull List is currently submitting jobs with TYPRUN set to SCAN. To perform JCL checking, the tape pull utility submits jobs through the internal reader with the TYPRUN parameter set to SCAN. It then reads the sysout of the jobs being submitted, and deletes the sysout from the spool.

Corrective Action: No action is required.

DFL031I UNKNOWN TYPE OF JCL CARD - `stmt`Link copied to clipboard

Explanation: This information message indicates that an unknown type of JCL statement was found while reading sysout from the spool.

Corrective Action: Check the JCL statement. If the format is valid, have your INCONTROL administrator call BMC Customer Support for assistance.

DFL032E READING OF SIMULATION ACTIVE JOBS FILE FAILEDLink copied to clipboard

Explanation: The reading of the file allocated to the DACKPTIN DD statement failed. Possible causes are:

The file allocated to the DACKPTIN DD statement is not the Active Jobs file.
The file allocated to the DACKPTIN DD statement is the Active Jobs file, but of a different version of the Control-M.
There is insufficient memory to read the Active Jobs file into storage.
The DACKPTIN DD statement is missing.

The utility terminates with a condition code of 08.

Corrective Action: Look for previous error messages that describe the type of error.

DFL033E OPEN OF SIMULATION LOG FILE FAILED. DD NAME "DALOGIN"Link copied to clipboard

Explanation: Open of the simulation facility output log file failed. Possible causes are:

The DALOGIN DD statement is missing.
The file allocated to the DALOGIN DD statement is neither the IOA Log file nor the log file which was produced by the Control-M simulation.

The utility is terminated with a condition code of 08.

Corrective Action: Correct the JCL of the job.

DFL034E SUBMIT OF MEMBER `memName` FROM THE LIBRARY `lib` FAILEDLink copied to clipboard

Explanation: The specified member in the specified library was not submitted by the Tape Pull List utility.

Corrective Action: Look for the previous error messages which will describe the type of error.

DFL035E MEMBER `memName` SHOULD BE SUBMITTED BUT IS NOT IN THE ACTIVE JOBS FILELink copied to clipboard

Explanation: A message indicating job submission was found in the simulation output log file, but the Active Jobs file does not contain an entry for that job. The Tape Pull List utility submits a job only if a message indicating job submission is found in the log file and the Active Jobs file contains the entry for that job.

Corrective Action: Check whether the Active Jobs file allocated to the DACKPTIN DD statement was changed since the last run of the simulation.

DFL036E UNRESOLVED VOL=AFF= IN DDNAME `ddName`Link copied to clipboard

Explanation: The VOL=AFF= val parameter was specified for the ddName DD statement but it could not be resolved within the job.

The information for this DD statement is ignored by the utility.

Corrective Action: Look for the next message to identify the job name and step name where the error was detected.

DFL037E JCL ERROR WAS FOUND IN MEMBER `memName`Link copied to clipboard

Explanation: A JCL error was found in the indicated member.

Corrective Action: Look for earlier error messages that describe the type of error.

DFL038I TAPE PULL LIST UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the Tape Pull List utility started.

Corrective Action: No action is required.

DFL039I TAPE PULL LIST UTILITY ENDEDLink copied to clipboard

Explanation: This information message indicates that the Tape Pull List utility ended.

Corrective Action: No action is required.

DFL045S SIMULATION LOG DOES NOT CONTAIN MESSAGES ON JOB SUBMISSIONLink copied to clipboard

Explanation: Messages indicating job submission were not found in the log file allocated to the DALOGIN DD statement.

The utility is terminated with a condition code of 08.

Corrective Action: Check the results of the Control-M Simulation Facility.

DFL049W DATASET `dsn` IS NOT FOUND IN CATALOG. DDNAME `ddName`Link copied to clipboard

Explanation: The specified data set is not cataloged in the computer where the utility is executing.

This data set is ignored during utility processing.

Corrective Action: Look for the next error message to identify the job name and step name where the error was detected. This data set may fail the job on execution JCL error.

DFL050E INVALID DISPOSITION IS SPECIFIED IN DDNAME `ddName`Link copied to clipboard

Explanation: The disposition specified for the ddName DD statement is invalid or conflicts with the current status of the DSNAME.

The information for the ddName DD statement is ignored by the utility.

Corrective Action: Look for the next error message to identify the job name and step name where the error was detected.

Messages DFL100 through DFL1xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

DFL185E ERROR WHILE READING SYSOUT FOR MEMBER `memName` JOBID `jobId`Link copied to clipboard

Explanation: Reading of sysout for the specified job failed. The tape pull list performs JCL checking by submitting the jobs with TYPRUN set to SCAN and reading the results from spool. A typical cause is a manual purge at the job from spool.

Corrective Action: Check earlier error messages that describe the type of error.

DFL187W UNRESOLVED BACKWARD REFERENCE FOR DDNAME `ddName`Link copied to clipboard

Explanation: Backward reference was not resolved for the ddName DD statement.

The information for this DD statement is ignored by the utility.

Corrective Action: Check the next error message to identify the job name and step name where the error was detected.

DFL188W UNIT NAME NOT SPECIFIED FOR NEW DATASET IN DDNAME `ddName`Link copied to clipboard

Explanation: No UNIT specification was found for the NEW data set allocated to the specified DD name.

The information for this DD statement is ignored by utility.

Corrective Action: Look for the next error message to identify the job name and step name where the error was detected.

DFL189I MEMBER `memName` PGMSTEP `pgmStep` PROCSTEP `procStep`Link copied to clipboard

Explanation: The information message identifies the location of the errors described by the previous message.

Corrective Action: No action is required.

DFL190W NOT CATLGD2 MAY BE ENCOUNTERED FOR DDNAME `ddName`Link copied to clipboard

Explanation: The data set allocated to the specified DD statement is already cataloged. It is possible that the data set is not currently cataloged, but will be created and cataloged before the execution of the specified job.

Corrective Action: Look for the next error message to identify the job name and step name where the error was detected.

DIB messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages DIB900 through DIB9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

DIB911I UTILITY IOADBIB STARTEDLink copied to clipboard

Explanation: This information message indicates that utility IOADBIB has started creating an IOA Access Method index file based on existing data.

Corrective Action: No action is required.

DIB912E ERROR `err` AT LINE line. CURRENT STATEMENT: `stmt`Link copied to clipboard

Explanation: Control-M/Analyzer utility CTBDBIB failed while reading the indicated input statement from the data set referenced by the SYSIN DD statement.

The utility stops executing with a condition code of 08.

Corrective Action: Notify your INCONTROL administrator.

DIB914I PROGRAM ENDED: `num` KEYS BUILTLink copied to clipboard

Explanation: This information message indicates the normal termination message of Control-M/Analyzer Index file rebuilding utility CTBDBIB.

Corrective Action: No action is required.

DIB915S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: An error was detected during an attempt to open the file referenced by the SYSPRINT DD statement.

The file referenced by the SYSPRINT DD statement is not opened.

Corrective Action: the system job log, and correct the problem accordingly. Rerun the job.

DIB916E NO INPUT PARAMETERS. PROGRAM STOPPEDLink copied to clipboard

Explanation: The input file for the CTBDBIB Control-M/Analyzer utility is empty (the SYSIN DD statement).

The utility stops executing with a condition code of 04.

Corrective Action: Fill in the input statements and rerun the job.

DIB917S INTERNAL ERROR WHILE PROCESSING DDNAME `ddName`Link copied to clipboard

Explanation: Control-M/Analyzer utility CTBDBIB failed while processing of the data set referenced by the indicated DD name. This message is followed by message DIB918S, which contains additional details about the error.

The utility stops executing with a nonzero condition code.

Corrective Action: Contact your INCONTROL administrator with the details displayed in this and the following message.

DIB918S RETURN CODE `rc` FROM `routineName` ROUTINE, FUNCTION `func`Link copied to clipboard

Explanation: Control-M/Analyzer utility CTBDBIB failed while processing the data set referenced by the DD name indicated in message DIB917S.

The utility stops executing with the indicated return code.

Corrective Action: Notify your INCONTROL administrator.

DIB919E INPUT PARAMETERS CONTAIN DUPLICATE DDNAMESLink copied to clipboard

Explanation: The CTBDBIB parameter Control-M/Analyzer utility could not process the input parameters due to duplicate DD names in the input statements.

The utility stops executing with a condition code of 36.

Corrective Action: Correct the input statements, and rerun the job.

DIB91AS INSUFFICIENT STORAGE TO RUN UTILITY IOADBIBLink copied to clipboard

Explanation: The IOADBIB parameter requires more storage to rebuild an index file.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size, and rerun the job.

DIB91BS INDEX FILE IS FULL. UNABLE TO ADD A KEYLink copied to clipboard

Explanation: The utility that builds index entries for the IOA Access Method file was not able to add an index element to the index file because it was full.

The utility stops.

Corrective Action: Allocate a new index file with more space than the original, and rerun this utility.

Messages DIBG00 through DIBGxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

DIBG60I BUILD INDEX UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the index file creation process started. This message is issued by the CTDDIB utility, which generates an index file based on an existing data file.

Corrective Action: No action is required.

DIBG61I INDEX BUILT SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the index file was successfully built based on the existing data file. This message is issued by the CTDDIB utility.

Corrective Action: No action is required.

DIBG62S BUILD INDEX UTILITY ENDED WITH ERRORLink copied to clipboard

Explanation: An error was encountered during index file creation. This message is issued by the CTDDIB utility. Other error messages indicate the cause of the error.

The index file is not usable.

Corrective Action: Correct the problem, and rerun the CTDDIB utility to generate the index based on the existing data file.

DIBG63S TOO MANY ERRORS DETECTEDLink copied to clipboard

Explanation: The number of errors detected exceeds a fixed threshold.

The CTDDIB utility terminates.

Corrective Action: Correct the errors, and resubmit the job.

DIBG64S NOT ENOUGH SPACE IN INDEX FILELink copied to clipboard

Explanation: There is insufficient space for the CTDDIB utility to add a new index element to the index file.

The CTDDIB utility terminates with a return code of 28.

Corrective Action: Expand the index file using the IOADBF utility, and resubmit the job.

DIBG66S INVALID VALUE IN PARAMETER DBFILE. VALID VALUES ARE: ACT, PRM, HST, MIG, MG1-MG9Link copied to clipboard

Explanation: The DBFILE parameter in the CTDDIB utility is not set to ACT, PRM, HST, MIG or MG n. The CTDDIB utility creates an index file from an existing data file. The user tried to run the CTDDIB utility without a valid DBFILE parameter.

The CTDDIB utility terminates.

Corrective Action: Rerun the CTDDIB utility after setting the DBFILE parameter to ACT, PRM, HST, MIG, or MG n depending on the type of file for which the index is being created, as follows:

ACT - Active User file
PRM - Permanent User file
HST - History User file
MIG - Migrated User file
MG n - Migrated User file partition, where n is the partition number

DIBG67E BUILD INDEX DETECTED AN ERROR WHILE ADDING A NEW INDEX RECORDLink copied to clipboard

Explanation: An error was encountered by function ADDI (Add Index) of the CTDDIB utility.

After a number of attempts to write the record, the CTDDIB utility terminates with an error code of 22. The problematic record is not indexed but is written to file DATRACE.

Corrective Action: If necessary, correct data file records in accordance with other error messages and resubmit the job.

DIBG68I DUPLICATE RECORD FOUND IN DATA FILELink copied to clipboard

Explanation: This information message indicates that a duplicate record exists in the data file. The duplicate record may be the result of a computer malfunction.

The CTDDIB utility continues processing.

Corrective Action: No action is required.

DIBG69E A DATA FILE READ ERROR WAS DETECTED, PROBLEMATIC RECORD WRITTEN TO FILE DATRACELink copied to clipboard

Explanation: An error occurred while reading an IOA Access Method data file.

The problematic record is written to file DATRACE.

Corrective Action: Correct data file records and resubmit the job.

DIBG6AI NUMBER OF RECORDS READ FROM DATA FILE=`num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIB utility read num records from the IOA Access Method data file to be indexed.

Corrective Action: No action is required.

DIBG6BI NUMBER OF RECORDS ADDED TO `file` INDEX FILE=`num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIB utility added num records to the IOA Access Method index file.

In this message, file is name of the IOA Access Method component.

Corrective Action: No action is required.

DIBG6CI NUMBER OF DUPLICATE RECORDS IN DATA FILE=`num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIB utility found num duplicate records in the IOA Access Method data file to be indexed.

Duplicate records are not indexed.

Corrective Action: No action is required.

DIBG6DE `file` INDEX FILE MUST BE REFORMATTED PRIOR TO REBUILDING INDEXLink copied to clipboard

Explanation: The index file was not reformatted. The index component of the IOA Access Method must be reformatted prior to running the CTDDIB utility.

In this message, file is name of the IOA Access Method component.

The CTDDIB utility terminates.

Corrective Action: Reformat the index file with the IOADBF utility and resubmit the job.

DIBG6EE ERROR IN THE SORT PROGRAM. SEE SORT MESSAGES.Link copied to clipboard

Explanation: The SORT program called by the CTDDIB utility ended with errors. This error probably indicates that insufficient storage was allocated for sort processing.

The CTDDIB utility terminates.

Corrective Action: Allocate more space for the SORT program and rerun the CTDDIB utility.

DIBG6FI NUMBER OF DUPLICATE RECORDS NOT ADDED TO `file` INDEX FILE= `num`Link copied to clipboard

Explanation: This information message indicates that the CTDDIB utility detected duplicated records in a data component. The corresponding index records were not added to the alternative index component.

In this message, file is the name of the IOA Access Method component.

Corrective Action: No action is required.

DIG messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages DIG900 through DIG9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

DIG901I UTILITY IOADIG STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the IOADIG utility. The IOADIG utility performs IOA Access Method data file integrity checking.

Corrective Action: No action is required.

DIG902S WARNING: RBA INCONSISTENT AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: An RBA error was detected by the IOADIG utility while checking the rec record of the input IOA Access Method data file. This message indicates the specific block and record that contain the error.

The IOADIG utility continues executing.

Corrective Action: Rerun the IOADIG utility with ACT set to W to correct the error. If the error remains, save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you continue to encounter problems with the IOA Access Method files, see the section on reorganizing the IOA Access Method File in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG903S HEADER CORRUPT. POINTER TO START OF FREE RECORD CHAIN INVALIDLink copied to clipboard

Explanation: An error was detected by the IOADIG utility in the header of the input IOA Access Method data file.

The IOADIG utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG904I NO FREE RECORDS DETECTED. CHECK NOT REQUIREDLink copied to clipboard

Explanation: This information message indicates normal termination of data file integrity checking by the IOADIG utility when the file to be checked is full.

Corrective Action: No action is required.

DIG905S INTEGRITY CHECK ENDED ABNORMALLY. FREE RECORD CHAIN CREATION FAILEDLink copied to clipboard

Explanation: The IOADIG utility is unable to perform integrity checking on the requested IOA Access Method data file.

The IOADIG utility terminates with a condition code of 32.

DIG906I CHECK COMPLETED NORMALLY. ERRORS CORRECTEDLink copied to clipboard

Explanation: This information message indicates that the IOADIG utility ended normally, and errors were corrected successfully.

Corrective Action: No action is required.

DIG907I DATABASE INTEGRITY CHECK ENDED OK: NO ERRORS DETECTEDLink copied to clipboard

Explanation: This information message indicates that the IOADIG utility ended and no errors were detected.

Corrective Action: No action is required.

DIG908S NUMBER OF FREE RECORDS IN HEADER DOES NOT MATCH THE ACTUAL NUMBER OF FREE RECORDSLink copied to clipboard

Explanation: The IOADIG utility detected in the header of the IOA Access Method data file that the number of free records in the data file and the number of free records recorded in the header record are not the same.

The utility continues executing.

DIG909S ACTIVE RECORD ENCOUNTERED IN FREE RECORD CHAINLink copied to clipboard

Explanation: The IOADIG utility detected an active record in the free record chain of the IOA Access Method data file.

The utility continues executing.

DIG90AS INVALID FREE LIST POINTER ENCOUNTEREDLink copied to clipboard

Explanation: The IOADIG utility detected an invalid free list pointer while integrity checking the IOA Access Method data file. One or more records pointed to by the free list pointer are not free records.

The utility continues executing.

DIG90BS CROSS-LINKED FREE RECORDS ENCOUNTEREDLink copied to clipboard

Explanation: The IOADIG utility detected a recursive pointer error in the free record chain while integrity checking the IOA Access Method data file.

The utility continues executing.

DIG90CS INVALID RECORD ID IN THE RECORD HEADERLink copied to clipboard

Explanation: The IOADIG utility detected an invalid record ID in the data file header while integrity checking the IOA Access Method data file.

The utility continues executing.

DIG90DS FREE RECORD OUT OF CHAIN AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: While integrity checking the IOA Access Method data file, the IOADIG utility detected a free record that is not in the free record chain.

The utility continues executing.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG90ES INSUFFICIENT STORAGE TO RUN UTILITYLink copied to clipboard

Explanation: The IOADIG utility requires more storage to perform an integrity check on the IOA Access Method data file.

The utility terminates with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the utility.

DIG90FS OPEN OF FILE FAILEDLink copied to clipboard

Explanation: The IOA Access Method data file for which integrity checking was requested cannot be opened. Possible causes are causes:

The DD statement which references the data file is missing.
The file referenced by the DD statement is not an IOA Access Method data file.
An internal error occurred while attempting to open the file referenced by the DD statement.

The IOADIG utility terminates with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job. If the error persists, notify your INCONTROL administrator.

DIG911S ERROR DETECTED: BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: The IOADIG utility detected an error in the rec record in the blk block.

The utility continues executing.

DIG912S POINTER TO THIS RECORD IS AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: The IOADIG utility detected an error in a pointer at the rec record in the blk block.

The utility continues executing.

DIG913I DATABASE INTEGRITY ERRORS DETECTED. TO CORRECT, SPECIFY "FUNC=W"Link copied to clipboard

Explanation: This information message indicates that the IOADIG utility detected one or more integrity errors.

The utility terminates with a return code of 32.

Corrective Action: To correct the errors, rerun the IOADIG utility after setting the FUNC parameter to W. If the problem persists, save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

DIG914S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: An error occurred while opening the SYSPRINT DD statement. The DD statement is probably missing.

The IOADIG utility terminates with a return code of 8.

Corrective Action: Notify your INCONTROL administrator.

DIG916S DATABASE INTEGRITY ERRORS DETECTEDLink copied to clipboard

Explanation: The IOADIG utility detected one or more integrity errors.

The IOADIG utility continues executing.

DIG917S WARNING: INCORRECT RBA IN BLOCK `blk`Link copied to clipboard

Explanation: The IOADIG utility detected an invalid Relative Block Address (RBA) in the blk block.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility and contact BMC Customer Support. Include all the extents of the files.

DIG918S WARNING: INCORRECT RECORD ID IN BLOCK `blk`Link copied to clipboard

Explanation: The IOADIG utility detected an invalid record ID in the block identified in the message.

The utility continues executing.

DIG919S HEADER CORRUPT: INCORRECT {BLOCK SIZE | RECORD LENGTH | DATASET NAME}Link copied to clipboard

Explanation: The IOA Access Method data file header does not contain the correct block size, record length, or data set name information (as indicated in the wording of the message). The error was detected by the IOADIG utility.

The utility stops executing.

DIG920S QUANTUM NOT IN ASCENDING ORDER - PROBLEM NOT CORRECTEDLink copied to clipboard

Explanation: The values specified for the QUANT1, QUANT2 and QUANT3 parameters are not in ascending order. These parameters are used with variable record length IOA Access Method Database file components for managing free space areas when new records are written. They must correlate with the BLKSIZE parameter as follows: QUANT1 < QUANT2 < QUANT3 < BLKSIZE.

The utility continues executing.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG921S WARNING: INCORRECT FREE SPACE COUNTER IN BLOCK `blk`Link copied to clipboard

Explanation: The free space counter in the blk block is not accurate. This error was detected by the IOADIG utility.

The utility continues executing.

DIG922S WARNING: INCORRECT RECORD ORDER IN BLOCK `blk`Link copied to clipboard

Explanation: One or more records are out of sequence in the block identified in the message. This error was detected by the IOADIG utility.

The utility continues executing.

DIG923S WARNING: INCORRECT RECORD COUNTER IN BLOCK `blk`Link copied to clipboard

Explanation: The IOADIG utility detected that the record counter in the blk block is not accurate.

The utility continues executing.

DIG924W WARNING: INCORRECT FREE SPACE QUANTUM FOR BLOCK `blk`Link copied to clipboard

Explanation: The IOADIG utility detected that the amount of free space designated for the blk block is incorrect. These parameters are used with variable record length IOA Access Method Database file components for managing free space areas when new records are written. They must correlate with the BLKSIZE parameter as follows: QUANT1 < QUANT2 < QUANT3 < BLKSIZE.

The utility continues executing.

Corrective Action: Check that all started tasks or jobs in Control-D or Control-V that are working with user files are running on LPARs which are synchronized by software such as GRS or MIM.

DIG925S HEADER CORRUPTED: INCORRECT TYPE IN RECORD ZEROLink copied to clipboard

Explanation: The IOADIG utility detected that the record type recorded in the IOA Access Method data file header record is incorrect.

The utility continues executing.

DIG926S DYNAMIC ALLOCATION ERROR OF EXTENT= `dsn` RC= `rc` REASON= `rsc`Link copied to clipboard

Explanation: The IOADIG utility detected an error during allocation of an extent.

The utility terminates with a return code of 12.

Corrective Action: For a description of the reason code received, refer to the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, report the reason code to BMC Customer Support.

DIG927I INTEGRITY CHECKED OK FOR DATASET `dsn`Link copied to clipboard

Explanation: This information message indicates that the IOADIG utility did not find any integrity problems in the dsn data set.

The utility continues executing.

Corrective Action: No action is required.

DIG928I DATABASE INTEGRITY CHECKED OK: NO ERRORS DETECTEDLink copied to clipboard

Explanation: This information message indicates the normal end of the IOADIG utility. No errors were detected.

The utility terminates with a return code of 0.

Corrective Action: No action is required.

DIG929I INTEGRITY CHECKED OK FOR MAIN DATASETLink copied to clipboard

Explanation: This information messages indicates that the IOADIG utility found no errors in the main data set.

Corrective Action: No action is required.

DIG92AS DEALLOCATION ERROR FOR DATASET `dsn`Link copied to clipboard

Explanation: The IOADIG utility detected an error during deallocation of an extent of the dsn data set.

The utility terminates with a return code of 12.

Corrective Action: For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, report the reason code to BMC Customer Support.

DIG92BS FOR DSN=Link copied to clipboard

Explanation: This message is the header for other messages which indicate the relevant data set names.

Corrective Action: No action is required.

DIG92CS INVALID PARAMETER, VALID PARAMETERS ARE ACT=R/W, TYPE=F/VLink copied to clipboard

Explanation: An invalid parameter was passed to the IOADIG utility.

Valid values for the ACT parameter:

R - Perform a read-only check. Do not correct detected errors.
W - If an error is detected, correct it.

Valid values for the ACT parameter:

F - Fixed length records in data file.
V - Variable length records in data file.

The utility terminates with a return code of 24.

Corrective Action: Rerun the IOADIG utility after setting its parameters to valid values.

DIG92DI INPUT PARAMETERS ARELink copied to clipboard

Explanation: This information message is the header for a list of input parameters.

Corrective Action: No action is required.

DIG92ES DATASET NAME `dsn` IN CONTROL BLOCK IS TOO LONGLink copied to clipboard

Explanation: This message indicates that the IOADIG utility detected that the dataset name (dsn), in the control block of the IOA Access Method data file, is longer then 38 bytes.

The utility terminates with a condition code of 16.

Corrective Action: Use the following procedure:

Save the output of the job.
Use the IEBGENER utility to create a copy of the IOA Access Method index and data files. Be sure to include all the extents of the files.
Contact BMC Customer Support.

If you encounter more problems with the IOA Access Method files, see the INCONTROL for z/OS Administrator Guide for information on how to reorganize the files.

DII messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages DII900 through DII9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

DII941I UTILITY IOADII STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOADII utility started performing IOA Access Method index file integrity checking.

Corrective Action: No action is required.

DII942S OPEN OF INDEX FILE FAILEDLink copied to clipboard

Explanation: The IOA Access Method index file could not be opened.

Processing is stopped.

Corrective Action: Check the IOA log and system job log for more information. Correct the problem and rerun the utility.

DII943S INDEX INTEGRITY ERRORS DETECTED. SEE DATRACE FILELink copied to clipboard

Explanation: The IOADII utility detected an integrity error in the IOA Access Method index file. The problematic record is written to file DATRACE.

Processing is stopped.

Corrective Action: Rebuild the index using the CTDDIB utility.

DII945I NUMBER OF RECORDS READ FROM INDEX FILE=`num`Link copied to clipboard

Explanation: This information message indicates that nnnn records were read from the IOA Access Method index file.

Corrective Action: No action is required.

DII945S INDEX INTEGRITY ERRORS DETECTED AT: BLOCK=`block` RECORD=`record`Link copied to clipboard

Explanation: The Control-M/Analyzer CTBDBII utility found integrity problems in the Index file at the indicated location.

The utility stops executing with a condition code of 32.

Corrective Action: Inform your INCONTROL administrator.

DII946S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: The IOADII utility detected an error when opening the file referenced by the SYSPRINT DD statement.

The file referenced by the SYSPRINT DD statement is not opened.

Corrective Action: Check the system job log, and correct the problem accordingly. Rerun the job.

DII947I UTILITY IOADII ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the IOADII utility ended normally.

Corrective Action: No action is required.

DIP messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages DIP900 through DIP9xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DIP930I DELETE PAGES STARTED IN `mode` MODELink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility starts.

In this message, mode is the mode in use. Valid values are:

TEST - simulation mode
PROD - production mode

Corrective Action: No action is required.

DIP931I DELETE PAGES ENDEDLink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility ends.

Corrective Action: No action is required.

DIP932I LAST PHASE ENDED WITH ERRORSLink copied to clipboard

Explanation: This information message is issued when the last phase of the operation of the CTDDIP utility ended with severe errors. The problem is identified in accompanying messages.

The utility ends with a return code of 08.

Corrective Action: Correct the problem identified in the accompanying messages and rerun the utility.

DIP933E DELETE PAGES ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTDDIP utility ended with errors. The errors are described in the accompanying messages.

The CTDDIP utility ends with a return code of 04 or 08.

Corrective Action: Correct the problem identified in the accompanying messages and rerun the job.

DIP934I numStmts INPUT STATEMENTS WERE SPECIFIED, `numErrors` ERRORS WERE DETECTEDLink copied to clipboard

Explanation: This information message provides statistics about the input stream statements that have been processed by the CTDDIP utility.

The variables in this message are:

numStmts - the number of input statements
numErrors - the number of errors

Corrective Action: No action is required.

DIP935I `numIndexVals` INDEX VALUES AND `numPages` PAGES WERE DELETEDLink copied to clipboard

Explanation: This information message provides statistics about the index values in index files, and pages in CDAM, that the CTDDIP utility identified for deletion.

When operating in TEST mode, the identified index values and CDAM pages will be deleted.
When operating in production mode, the CTDDIP utility deleted the identified index values and CDAM pages.

The variables in this message are:

numIndexVals - the number of index values deleted (or to be deleted) from index files
numPages - the number of CDAM pages deleted (or to be deleted)

Corrective Action: No action is required.

DIP936E INVALID PARAMETER `parm` IN STMT `stmt`Link copied to clipboard

Explanation: An invalid parameter was encountered in the input data stream of the CTDDIP utility.

The variables in this message are:

parm - the identity of the invalid parameter
stmt - the number of the statement that contains parm

The CTDDIP utility continues, but will end with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: Correct the parameter syntax in the input statement of the CTDDIP utility.

DIP937E MISSING PARAMETER `parm` IN STMT `stmt`Link copied to clipboard

Explanation: A parameter was missing from the input data stream of the CTDDIP utility.

The variables in this message are:

parm - the identity of the missing parameter
stmt - the number of the statement that contains parm

The CTDDIP utility continues, but ends with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: Correct the parameter syntax in the input statement of the CTDDIP utility.

DIP938E ILLEGAL `comp` IN STMT `stmt`Link copied to clipboard

Explanation: The CTDDIP utility detected in an input statement a reference to a prohibited component.

The variables in this message are:

comp - the prohibited component Valid values are:
- INDEX LEVEL - The specified index is a record level index, and values cannot be deleted in the case of such an index.
- NO. OF REPORTS - The number of reports that have been selected exceeds the value of the specified RMODE parameter.
- MIGR MEDIA TYPE - the last stage migration media type is either not specified in the IOASPRM member of the IOA PARM library, or is not the specified DASD.
stmt - the number of the problematic statement

The CTDDIP utility continues, but ends with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: The user response varies according to the value of comp, as follows:

INDEX LEVEL - The CTDDIP utility cannot be used to delete the specified index values. Therefore, take into account that the specified values remain undeleted.
NO. OF REPORTS - Do one of the following:
- Set the criteria of report selection more accurately, so as to select only necessary reports.
- To delete indexes from multiple reports, set the value of the RMODE parameter to M.
MIGR MEDIA TYPE - The CTDDIP utility cannot be used to delete the specified index values. Therefore, take into account that the specified values remain undeleted from the migrated CDAM and index files.

DIP939W DUPLICATED INDEX VALUE FOUND FOR STMT `stmt`Link copied to clipboard

Explanation: A duplicate index value was found in the input data stream of the CTDDIP utility.

In this message, stmt is the number of the problematic statement.

The CTDDIP utility continues, but ends with a condition code of 04.

Corrective Action: Correct the input statement of the CTDDIP utility as necessary.

DIP93AE DYNAMIC ALLOCATION ERROR RC= `rc` RSN= `rsn` FOR STMT `stmt`Link copied to clipboard

Explanation: During the execution of the CTDDIP utility, dynamic allocation failed (SVC 99).

Additional information is provided in the DIP94AE message, which follows this message.

The variables in this message are:

rc - the return code
rsn - the reason code
stmt - the number of the problematic statement

For information about the return code (rc) and the reason code (rsn), see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CTDDIP utility continues, but ends with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: No action is required.

DIP93BI `numValues` GLOBAL INDEX VALUES WERE DELETEDLink copied to clipboard

Explanation: This information message indicates the number of global index values identified by the CTDDIP utility for deletion from the DB2 Global Index database.

The system action depends on whether the utility is operating in PROD mode or TEST mode, as follows:

In PROD mode, the message indicates the number of global index values that were deleted.
In TEST mode, the message indicates the number of global index values that will be deleted when the utility is run in PROD mode.

In this message, numValues is the number of global index values deleted, or to be deleted, from the DB2 Global Index database.

Corrective Action: No action is required.

DIP93FI INPUT PARAMETERS: STAMP= `stmp`, CHAR= `chr` , REPLIST= `rlist`, PORTION= `portn`Link copied to clipboard

Explanation: This message is displayed by the CTDDIP utility and provides information about the values of EXEC input parameters.

The variables in this message are:

stmp - the value of the STAMP input parameter
chr - the value of the CHAR input parameter
rlist - the value of the REPLIST input parameter
portn - the value of the PORTION input parameter

Corrective Action: No action is required.

DIP93GI 1. INPUT STREAM TESTEDLink copied to clipboard

Explanation: This information message is issued routinely when data testing of the CTDDIP utility input stream has ended.

Corrective Action: No action is required.

DIP93HI 2. REPORT ENTRIES SELECTEDLink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility has completed the selection of report entries in the Active and Migrated User files.

Corrective Action: No action is required.

DIP93II 3. SYSDATA AND INDEX RECORDS SELECTEDLink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility has completed the selection of SYSDATA and index records in the Active and Migrated User files.

Corrective Action: No action is required.

DIP93JI 4. INDEX VALUES SELECTEDLink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility has completed the selection of index values in the Index files.

Corrective Action: No action is required.

DIP93KI 5. NUMBER OF REPORTS PER STATEMENT CHECKEDLink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility has finished checking the number of selected records in each CTDDIP input statement.

Corrective Action: No action is required.

DIP93LI 6. CDAM FILES UPDATEDLink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility has finished updating the CDAM files.

Corrective Action: No action is required.

DIP93MI 7. GLOBAL INDEX DATABASES UPDATEDLink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility has finished updating the index values in the Global Index Database tables.

Corrective Action: No action is required.

DIP93NI 8. INDEX FILES UPDATEDLink copied to clipboard

Explanation: This information message is issued routinely when the CTDDIP utility has finished updating the index values in the Index files.

Corrective Action: No action is required.

DIP93OI 9. GLOBAL INDEXES ARE NOT USEDLink copied to clipboard

Explanation: This information message is issued routinely instead of the DIP93MI message when the Global Index Database is not used.

Corrective Action: No action is required.

DIP93PI LIST OF INPUT STATEMENTSLink copied to clipboard

Explanation: This information message is issued routinely at the beginning of a list of the CTDDIP utility input statements.

Corrective Action: No action is required.

DIP93QI LIST OF SELECTED REPORTSLink copied to clipboard

Explanation: This information message is issued routinely at the beginning of a list of the reports selected by the CTDDIP utility.

Corrective Action: No action is required.

DIP93RI END OF LIST OF SELECTED REPORTSLink copied to clipboard

Explanation: This information message is issued routinely at the end of a list of the reports selected by the CTDDIP utility.

Corrective Action: No action is required.

DIP940E elem NOT FOUND FOR STMT `stmt`Link copied to clipboard

Explanation: During execution of the CTDDIP utility, a report element was not found in the database or index file.

The variables in this message are:

elem - the missing report element

Valid values of elem are:

elem	Meaning
REPORT ENTRY	any user record for the report that fits the specified criteria in the input statement but was not found in the Active user file nor in the Migrated user file.
INDEX NAME	the specified index for the report that fits the specified criteria in the input statement but was not found in the Active user file nor in the Migrated user file
INDEX VALUE	the specified index value was not found in the Index file for the report that matches the specified criteria in the input statement

stmt - the number of the problematic statement

The CTDDIP utility continues, but ends with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: Correct the criteria in the input statement of the CTDDIP utility.

DIP941E MISSING `filetyp elem` FOR STMT `stmt` KEY= `recordId`Link copied to clipboard

Explanation: During execution of the CTDDIP utility, a database element was not found.

The variables in this message are:

filetyp - the type of user file that lacked elemValid values are:
- ACTIVE
- MIGRATED
elem - the type of database element that was missingValid values are:
- USER RECORD
- SYSDATA RECORD
- INDEX RECORD
- USER RBA ENTRY
stmt - the number of the problematic statement
recordId - the user record database key

The CTDDIP utility continues, but ends with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.

DIP942E INVALID `filetyp elem` FOR STMT `stmt`Link copied to clipboard

Explanation: During execution of the CTDDIP utility, an invalid database element was detected.

Additional information is provided in the DIP94AE message, which follows this message.

The variables in this message are:

filetyp - the type of user file that contained the invalid database element Valid values are:
- ACTIVE
- MIGRATED
elem - the invalid database elementValid values are:
- CDAM RBA - The CDAM RBA in an Index file does not refer to the start or end position in the CDAM page, or exceeds the block or file space. The Index file is identified in the DIP94AE message.
- INDEX RBA - The internal index RBA exceeds the block or file space in the Index file. The Index file is identified in the DIP94AE message.
- USER RBA ENTRY - The first and last page numbers of the CDAM RBA in the user record of the Active or Migrated user file are unbalanced. The last page number precedes the first page number.
- INDEX RBA ENTRY - The first and last page numbers of the CDAM RBA in the index value entry of the Index file are unbalanced. The last page number precedes the first page number. The CDAM and the Index file are identified in the DIP94AE message.
- CDAM FDB BLOCK - Either the header or the version of the File Description Block (FDB) of the migrated CDAM is invalid. The CDAM and the Index file are identified in the DIP94AE message.
stmt - the number of the problematic statement

The CTDDIP utility continues, but ends with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.

DIP943E MIGRATED `elem` CONVERSION ERROR WHILE PROCESSING STMT `stmt`Link copied to clipboard

Explanation: During execution of the CTDDIP utility, a return code was received that indicated an invalid conversion of a database element from an original to a migrated file

Additional information is provided in the DIP94AE message, which follows this message.

The variables in this message are:

elem - the problematic database element Valid values are:
- CDAM RBA - The invalid conversion was of the original CDAM RBA from an Index file to a migrated CDAM RBA. The CDAM and Index files are identified in the DIP94AE message.
- CDAM NAME - The invalid conversion was of the original CDAM name to a migrated CDAM name. The CDAM file is identified in the DIP94AE message.
- INDEX FILE NAME - The invalid conversion was of the original Index file name to a migrated Index file name. The Index file is identified in the DIP94AE message.
stmt - the number of the problematic statement

The CTDDIP utility continues, but ends with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.

DIP944E OPEN FILE ERROR WHILE PROCESSING STMT `stmt`Link copied to clipboard

Explanation: During execution of the CTDDIP utility, the opening of an Index or CDAM file failed.

Additional information is provided in the DIP94AE message, which follows this message.

In this message, stmt is the number of the problematic statement

The CTDDIP utility continues, but ends with a condition code of 04. The index values and CDAM pages identified in the stmt statement are not deleted.

Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.

DIP945S UNEXPECTED RC= `rc` AFTER PHASE `phase` FOR STMT `stmt`Link copied to clipboard

Explanation: An unexpected internal return code was issued at the conclusion of some phase of the execution of the CTDDIP utility.

The variables in this message are:

rc - the internal return code
phase - the identity of the phase that had concluded
stmt - the number of the problematic statement

The CTDDIP utility ends with a condition code of 08.

Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.

DIP946S SORT ERROR RC= `rc`Link copied to clipboard

Explanation: During execution of the CTDDIP utility, a sort program was activated internally, but the sort program ended with an unexpected internal return code.

In this message, rc is the unexpected internal return code.

The CTDDIP utility ends with a condition code of 08.

Corrective Action: Examine the messages issued by the sort program and the documentation relating to that program to determine the cause of the error, and take appropriate corrective action.

DIP947S OPEN FILE `ddName` ERRORLink copied to clipboard

Explanation: During execution of the CTDDIP utility, the opening of a file failed.

Possible causes are:

The ddName DD statement is missing.
The data set described by the ddName DD statement contains incorrect DCB parameters.
The data set described by the ddName DD statement cannot be opened for sequential read or write operations.

In this message, ddName is the name of the problematic DD statement.

The CTDDIP utility ends with a condition code of 08.

Corrective Action: Do one of the following:

Correct the JCL of the CTDDIP utility and rerun the job.
Delete either the two working data sets or the input data set, and rerun the job. In this case, when the job is rerun, CTDDIP recreates the necessary data sets.

DIP948S INSUFFICIENT MEMORYLink copied to clipboard

Explanation: There is insufficient available storage to run the CTDDIP utility.

The CTDDIP utility ends with a condition code of 08.

Corrective Action: Increase the REGION size of the utility, and rerun the utility.

DIP94AE `dsn_typ` DSN= `dsn`Link copied to clipboard

Explanation: An invalid data set name was encountered.

This message is accompanied by another message providing more information.

The variables in this message are:

dsn_typ - the data set type of the data set with the invalid nameValid values are:
- CDAM FILE
- INDEX FILE
dsn - the invalid data set name

Corrective Action: Examine the accompanying messages for information about the error and the resulting System Action, and take the appropriate corrective action.

DIV messagesLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

Messages DIV900 through DIV9xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

DIV961I CONTROL-M/ANALYZER UTILITY CTBDBVIG STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTBDBVIG Control-M/Analyzer database integrity-checking utility.

Corrective Action: No action is required.

DIV962S INSUFFICIENT STORAGE TO RUN UTILITY CTBDBVIGLink copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility requires more storage to perform an integrity check on a Control-M/ Data file.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size, and rerun the job.

DIV963S CONTROL-M/ANALYZER DATA FILE OPEN FAILEDLink copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility could not open the Control-M/Analyzer Data file for which integrity checking was requested. Possible causes are:

The DAMODD DD statement is missing.
The DAVARD DD statement is missing.
The file referenced by the DAMODD or DAVARD DD statement is not a Control-M/Analyzer data file.
An error occurred while attempting to open one of the files pointed to by the DAMODD or DAVARD DD statement.

The utility stops executing with a condition code of 20.

Corrective Action: Correct the JCL, and rerun the job. If the error persists, notify your INCONTROL administrator.

DIV965I INTEGRITY ERRORS DETECTED. TO CORRECT, SPECIFY "ACT=W"Link copied to clipboard

Explanation: This information message indicates that the CTBDBVIG Control-M/Analyzer utility detected integrity errors while checking the Control-M/Analyzer database.

The utility stops executing with a condition code of 32.

Corrective Action: Notify your INCONTROL administrator before rerunning the utility.

DIV966S ERROR UPDATING CONTROL-M/ANALYZER DATA FILESLink copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility failed due to an internal error.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

DIV967S BAD RBA ENCOUNTERED WHILE SCANNING MODELS FILE AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility detected an invalid RBA while checking the rec record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

DIV968S INCONSISTENT NAMING AT BLOCK= `blk` RECORD= `rec` IN MODELS FILELink copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility detected an error while checking the rec record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

DIV969S BAD RBA ENCOUNTERED WHILE SCANNING VARIABLES AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility detected an error while checking the rec record in the modules file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

DIV96AS MULTIPLE REFERENCES TO BASE AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility detected an error while checking the rec record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

DIV96BS MULTIPLE REFERENCES TO VARIABLE AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility detected an error while checking the rec record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

DIV96CS UNREFERENCED VARIABLE AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility detected an unreferenced variable while checking the rec record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

DIV96DI CONTROL-M/ANALYZER UTILITY CTBDVIG ENDEDLink copied to clipboard

Explanation: This information message indicates the normal termination of the CTBDBVIG Control-M/Analyzer utility, the Control-M/Analyzer database integrity-checking utility.

Corrective Action: No action is required.

DIV96ES INCONSISTENT NAMING AT BLOCK= `blk` RECORD= `rec` IN VARIABLES FILELink copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility detected an error while checking the record identified in the message.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

DIV96FI VARIABLES DATA BASE INTEGRITY HAS BEEN VALIDATEDLink copied to clipboard

Explanation: This information message indicates the database integrity validation process has been completed by the CTBDBVIG Control-M/Analyzer utility.

Corrective Action: No action is required.

DIV970S UNREFERENCED BASE AT BLOCK= `blk` RECORD= `rec`Link copied to clipboard

Explanation: The CTBDBVIG Control-M/Analyzer utility detected an error while checking the record indicated in the message.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

DIV971S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: This information message indicates that the CTBDBIV Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

The SYSPRINT DD statement is missing.
The data set referenced by the SYSPRINT DD statement cannot be accessed for sequential write.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

DIX messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages DIXG00 through DIXGxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DIXGA0I DELETE OF UNNEEDED INDEX FILES STARTEDLink copied to clipboard

Explanation: This information message identified that the CTVDELI utility began execution. This utility scans the Migrated User Report List file and erases index files and index records that are no longer needed.

Corrective Action: No action is required.

DIXGA1I DELETE OF UNNEEDED INDEX FILES ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTVDELI utility finished executing without errors. This utility scans the Migrated User Report List file and erases index files and index records which are no longer needed.

Corrective Action: No action is required.

DIXGA2S DELETE OF UNNEEDED INDEX FILES ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTVDELI utility ended with errors. This utility scans the Migrated User Report List file and erases index files and index records that are no longer needed. The problem is described in one or more preceding messages.

The CTVDELI utility terminates with a return code of 08.

Corrective Action: Check preceding error messages, correct the problem, and rerun the job.

DIXGA3I DATASET dsn WILL BE DELETEDLink copied to clipboard

Explanation: This information message indicates that the CTVDELI utility will delete the dsn index file. The CTVDELI utility scans the Migrated User Report List file and erases index files that are no longer needed.

Corrective Action: No action is required.

DIXGA4E INVALID PARAMETER: - `parm`Link copied to clipboard

Explanation: The parm parameter is not valid for the CTVDELI utility. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

The CTVDELI utility terminates with a condition code of 08.

Corrective Action: Correct the parameter syntax and resubmit the job. For more information, refer to the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.

DIXGA5E MISSING PARAMETER AFTER: - `parm`Link copied to clipboard

Explanation: A subparameter of the parm parameter is missing. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

The CTVDELI utility terminates with a condition code of 08.

Corrective Action: Correct the parameter syntax, and resubmit the job. For more information, refer to the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.

DIXGA6E REDUNDANT PARAMETER: - `parm`Link copied to clipboard

Explanation: The parm parameter is specified more than once in the CTVDELI utility. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

The CTVDELI utility terminates with a condition code of 08.

Corrective Action: Remove the redundant parameter, and resubmit the job. For more information, see the CTVDELI utility in the iNCONTROL for z/OS Utilities Guide.

DIXGA7E OPEN OF MIGRATED USER REPORTS LIST FILE FAILED. DDNAME "DAVMIG"Link copied to clipboard

Explanation: Open of the Control-V Migrated User Report List file failed. This file is referenced by the DAMIG DD statement. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file and erases index files that are no longer needed.

Possible causes are:

The DAMIG DD statement is missing.
The data set referenced by the DAMIG DD statement is not a Control-V Migrated User Report List file.
The Migrated User Report List file referenced by the DAMIG DD statement belongs to another monitor, or was produced by a different version of Control-V.

The CTVDELI utility terminates with a condition code of 08.

Corrective Action: Correct the JCL for the CTVDELI utility, and rerun the job. For more information, refer to the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.

DIXGA8E OPEN OF PARAMETERS FILE FAILED. DDNAME DADELINLink copied to clipboard

Explanation: Open of the Parameters file for the CTVDELI utility failed. Possible causes are:

The DADELIN DD statement is missing.
The data set referenced by the DADELIN DD statement cannot be opened for sequential read.

The CTVDELI utility terminates with a condition code of 12.

Corrective Action: Correct the JCL, and rerun the job. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.

DIXGA9E OPEN OF SORT FILE FAILED. DDNAME `ddName`Link copied to clipboard

Explanation: The SORT utility invoked by the CTVDELI utility failed to open the data set referenced by the ddName DD statement.

The CTVDELI utility stops.

Corrective Action: Ensure all DD statements are valid. Rerun the CTVDELI utility. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.

DIXGAAE INVALID RETURN CODE FROM SORT, RC=`rc`Link copied to clipboard

Explanation: The internal sort program ended with errors. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file and erases index files that are no longer needed. The utility uses the site sort program.

The CTVDELI utility terminates with a condition code of 08.

Corrective Action: Check the explanations of the sort messages for the job in the manual for your sort facility.

DIXGABI WAITING FOR A CTDDELRP, RESTORE OR ANOTHER CTVDELI JOB TO TERMINATELink copied to clipboard

Explanation: This information message indicates that the CTVDELI utility is waiting for a CTDDELRP job, a restore job, or another CTVDELI job to terminate. The CTVDELI utility scans the Migrated User Report List file, and erases index files that are no longer needed. To ensure data integrity, CTVDELI cannot run concurrently with the CTDDELRP utility, a restore job, or another CTVDELI job.

When the contending job terminates, the CTVDELI utility resumes processing.

Corrective Action: No action is required.

DIXGACE NO INPUT PARAMETERS WERE SUPPLIEDLink copied to clipboard

Explanation: The CTVDELI utility did not receive input parameters by means of a SYSIN DD statement.

The CTVDELI utility scans the Migrated User Report List file, and erases index files that are no longer needed. The utility requires input parameters indicating which actions it should perform.

The CTVDELI utility terminates with a condition code of 08.

Corrective Action: Verify that input parameters are specified by means of a SYSIN DD statement. Rerun the CTVDELI utility.

DIXGADI * PARM=TEST SPECIFIED - SIMULATION MODE *Link copied to clipboard

Explanation: This information message indicates that the CTVDELI utility is running in SIMULATION mode. In SIMULATION mode, the CTVDELI utility produces a report that indicates which indexes would have been deleted if the utility were running in PRODUCTION mode.

Corrective Action: Examine CTVDELI output to determine if the proper indexes would have been deleted from disk. Make any changes required to prevent the incorrect deletion of indexes that are needed for any reason. Rerun the utility in PRODUCTION mode to actually delete unneeded indexes from disk.

DIXGAEE LOCATE ERROR FOR INDEX `dsn`Link copied to clipboard

Explanation: The CTVDELI utility encountered index dsn, which could not be located, possibly because the data set is not cataloged. The CTVDELI utility scans the Migrated User Report List file and erases unneeded index files.

The index whose data set name is dsn is not deleted.

Corrective Action: Determine why the data set could not be located. Correct the problem. Rerun the CTVDELI utility if necessary.

DIXGAFE ERROR DELETING INDEX `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The CTVDELI utility encountered index dsn, which could not be deleted. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file, and erases index files that are no longer needed. Possible reasons:

The data set was not found on the device indicated in the catalog.
The device on which the data set exists is not online.
Another reason.

The index whose data set name is dsn is not deleted.

Corrective Action: Determine why the data set could not be deleted. Correct the problem. Rerun the job if necessary.

DIXGAGE ERROR UNCATALOGING INDEX `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The CTVDELI utility encountered the dsn index, which could not be uncataloged. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

The index is not uncataloged.

Corrective Action: Determine why the data set could not be uncataloged. Correct the problem. Rerun the job if necessary.

DLD messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages DLD900 through DLD9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

DLD952S ERROR OPENING SEQUENTIAL FILELink copied to clipboard

Explanation: The IOADLD utility detected an error while opening a sequential file from which it is to read the records.

The IOADLD utility terminates with a return code of 16.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error, and rerun the job. If the error persists, contact BMC Customer Support.

DLD953S ERROR OPENING DATABASE FILE, RC=`rc`Link copied to clipboard

Explanation: The IOADLD utility detected an error while opening the IOA Access Method Database file. For a list of possible rc values from the Access Method, see message CTD908S.

The IOADLD utility terminates with a return code of 20.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error, and rerun the job. If the error persists, contact BMC Customer Support.

DLD955I UTILITY IOADLD STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the IOADLD utility. The IOADLD utility creates an IOA Access Method data file from the data in a sequential file that was previously created by the IOADUL utility.

Corrective Action: No action is required.

DLD956I UTILITY ENDED WITH RETURN CODE `num`Link copied to clipboard

Explanation: This information message indicates that the IOADLD utility terminated.

The IOADLD utility terminates with a return code of num.

Corrective Action: If the IOADLD utility ended with a non-zero return code, check for other error messages to determine the problem.

DLD957S ERROR IN IOAPARM LOADINGLink copied to clipboard

Explanation: The IOADLD utility detected an error while loading the IOAPARM member.

The IOADLD utility terminates with a return code of 4.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error, and rerun the job. If the error persists, contact BMC Customer Support.

DLD958S ERROR IN WRITING INTO THE DATABASE FILE, RC=`rc`Link copied to clipboard

Explanation: The IOADLD utility detected an error while adding records to the IOA Database Access Method. A likely reason is that there is not enough space for the IOA Database Access Method. For a list of possible rc values from the Access Method, see message CTD908S.

The IOADLD utility terminates with a return code of 24.

Corrective Action: Do the following:

Check the system job log for more information.
Use the IOADBF utility to allocate a new file with bigger SPACE parameter values.
Re-run the job.
If the error persists, contact your INCONTROL administrator.

DLD960S ERROR WHILE CLOSING THE DATABASE FILE, RC=`rc`Link copied to clipboard

Explanation: The IOADLD utility detected an error while closing the IOA Access Method file. For a list of possible rc values from the Access Method, see message CTD908S.

The IOADLD utility terminates with a return code of 30.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error, and rerun the job. If the error persists, contact BMC Customer Support.

DLD961I NUMBER OF COPIED RECORDS = `number_of_records`Link copied to clipboard

Explanation: The IOADLD utility has completed loading IOA Access Method File contents. This information message notifies you how many records were copied by the utility.

Corrective Action: No action is required.

DLD970I RENUM INDICATOR IS RLink copied to clipboard

Explanation: This information message indicates that the RENUM parameter was specified when running the IOADLD load utility.

Corrective Action: No action is required.

DLD971S OFFSET IS NOT NUMERICLink copied to clipboard

Explanation: A nonnumeric offset value was specified for the RENUM parameter. Three values are specified for the RENUM parameter. The second value, the offset, must be numeric.

The IOADLD utility terminates with a return code of 32.

Corrective Action: Correct the parameter values, and resubmit the job. For more information, see the IOADLD utility in the INCONTROL for z/OS Utilities Guide.

DLD972S LENGTH IS NOT NUMERICLink copied to clipboard

Explanation: A nonnumeric length was specified for the RENUM parameter. Three values are specified for the RENUM parameter. The third, length, must be numeric.

The IOADLD utility terminates with a return code of 34.

Corrective Action: Correct the parameter values, and resubmit the job. For more information, see the IOADLD utility in the INCONTROL for z/OS Utilities Guide.

DLD973S INPUT FILE IS NOT SORTED CORRECTLYLink copied to clipboard

Explanation: When loading the input file to the Control-O Variables file, the RENUM parameter was specified for the IOADLD load utility. However, the input file had not been sorted. This message occurs when loading the input file to the Control-O Variables file.

If the RENUM parameter is specified for the IOADLD utility, the records of the input file are sorted, renumbered, and then sorted in the positions specified by the offset and length values. However, after the renumbering process, the IOADLD utility found that the records were not sorted properly.

The IOADLD utility terminates with a return code of 36.

Corrective Action: Correct the parameter values, and resubmit the job. For more information, see the IOADLD utility in the INCONTROL for z/OS Utilities Guide.

DMI messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages DMI600 through DMI6xxLink copied to clipboard

This group includes messages for the Control-O product.

DMI670E ACB CONTROL BLOCK IS NOT VALIDLink copied to clipboard

Explanation: The alternate subsystem encountered an ACB control block that does not have a valid identifier.

The Control-O subsystem terminates the connection between the alternate subsystem and the Control-O subsystem.

Corrective Action: Contact BMC Customer Support.

DMI671E SSI ROUTINE SUBSYSTEM IS INACTIVELink copied to clipboard

Explanation: The CTODMI alternate subsystem module failed to invoke the Control-O subsystem. Because the Control-O subsystem is not active, there is no connection between the alternate subsystem and the Control-O subsystem.

Communication between the alternate subsystem and the Control-O subsystem fails.

Corrective Action: Reactivate Control-O in order to reestablish communication.

DMI672E SSI ROUTINE DETECTED AN ERRORLink copied to clipboard

Explanation: Control-O encountered an internal error (a return code of 16) while attempting to process the SSI request to transmit information from the alternate subsystem to the Control-O subsystem.

The information is not transmitted.

Corrective Action: Contact BMC Customer Support.

DMI673E SSI ROUTINE RETURNED AN UNDEFINED RETURN CODELink copied to clipboard

Explanation: Control-O encountered an internal error (a return code of 20) while processing an SSI request. The alternate subsystem was trying to transmit data to the Control-O subsystem.

The data is not transmitted.

Corrective Action: Contact BMC Customer Support.

DMI674E CTO SSCT POINTER NOT SET - SSI ROUTINE INVOCATION BYPASSEDLink copied to clipboard

Explanation: The pointer to the Control-O subsystem SSCT was not set. The initialization process normally sets the pointer to the Control-O subsystem SSCT.

Communication between the Control-O subsystem and the alternate subsystem terminates.

Corrective Action: Contact BMC Customer Support.

DSH messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages DSH900 through DSH9xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DSH947I TAPE `num` - EXPIREDLink copied to clipboard

Explanation: This is an information message of the CTVCLMIG utility, which indicates that all datasets residing on the specified tape volume are expired. All entries referred to this volume are deleted from the Migrated User File.

Corrective Action: Return the expired tape to the Global Tape Pool.

DSH948E INSUFFICIENT MEMORY TO COMPLETE PROCESSING OF THE FILE. RUN THE UTILITY AGAIN

Explanation: Insufficient memory for the CTVCLMIG utility to finish cleaning entries from the Migrated User Report List file.

Corrective Action: Increase the REGION size. Increase the memory allocation for $SYSDATA records that can be set as the DATA parameter in optional Wish WD2403. Run the CTVCLMIG utility again.

Messages DSHD00 through DSHDxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DSHD73E INVALID RETURN CODE FROM SORT, RC=`rc`Link copied to clipboard

Explanation: A failure was detected in the SORT utility phase of the CTVCLMIG utility. The main program of the CTVCLMIG utility received a return code higher than zero from the SORT utility phase.

The program terminates with a return code of 08.

Corrective Action: Additional information is in the Job log and the SORT messages. Correct all reported problems, and rerun the CTVCLMIG utility.

DSHD74E OPEN OF SORT FILE FAILED. DDNAME `dsn`Link copied to clipboard

Explanation: An OPEN failure for the dsn DD name was detected for the CTVCLMIG utility. The main program of the CTVCLMIG utility could not open the dsn DD statement. The specified DD statement is probably missing in the JCL for the CTVCLMIG utility.

The program terminates with a return code of 08.

Corrective Action: Add the missing DD statement and rerun the CTVCLMIG utility.

DSHD75I WAITING FOR CTVCLMIG JOB TO TERMINATE `dsn`Link copied to clipboard

Explanation: This information message indicates that the CTVCLMIG Control-D utility is waiting for another CTVCLMIG job to terminate. The CTVCLMIG utility clears unnecessary entries from the Migrated User Report List file. To maintain data integrity, the CTVCLMIG utility cannot run concurrently with another CTVCLMIG job.

When the contending job terminates, CTVCLMIG resumes processing.

Corrective Action: No action is required.

DSHD76E INVALID PARAMETER, VALID PARAMETER: MODE=TEST OR MODE=PRODLink copied to clipboard

Explanation: An invalid MODE parameter was specified when running for the CTVCLMIG utility.

The CTVCLMIG utility terminates with a return code of 12.

Corrective Action: Correct the MODE parameter to either TEST or PROD, and rerun the CTVCLMIG utility.

DSHD77I * PARM=TEST SPECIFIED - SIMULATION MODE *Link copied to clipboard

Explanation: This information message indicates that the CTVCLMIG utility ran in simulation mode. In this mode, messages are generated that indicate what actions would normally be performed. These actions are not performed, nor are any files changed.

Corrective Action: Before rerunning the CTVCLMIG utility in production mode, check its sysout.

DSHD78I NUMBER OF DELETED USER RECORDS = `num`Link copied to clipboard

Explanation: This information message indicates how many user records were deleted by the CTVCLMIG utility.

Corrective Action: No action is required.

DSHD79I NUMBER OF DELETED SYSDATA RECORDS = `num`Link copied to clipboard

Explanation: This information message indicates how many SYSDATA records were deleted by the CTVCLMIG utility.

Corrective Action: No action is required.

DSHD7AI NUMBER OF DELETED NOTEPAD RECORDS = `num`Link copied to clipboard

Explanation: This information message indicates how many notepad records were deleted by the CTVCLMIG utility.

Corrective Action: No action is required.

DSHD7BI NUMBER OF DELETED $INDEX RECORDS = `num`Link copied to clipboard

Explanation: This information message indicates how many index records were deleted by the CTVCLMIG utility.

Corrective Action: No action is required.

DSHD7CI RECORD WITH INCORRECT TYPE `type` FOR `userName jobName` IS DELETEDLink copied to clipboard

Explanation: This information message indicates that the CTVCLMIG utility found a record with an invalid type for the Migrated Report List file. Records of type type cannot appear in the Migrated Report list. The problematic record might have been created by a previous version of Control-D.

The variables in this message are:

userName - the value in the USERNAME field of the problematic record
jobName - the value in the JOBNAME field of the problematic record

The problematic record is deleted by the CTVCLMIG utility.

Corrective Action: No action is required.

DSHD7DI DELETING ORPHAN INDEX RECORDSLink copied to clipboard

Explanation: This information message is issued by the CTVCLMIG utility and indicates that the utility has entered the stage where it is deleting orphaned INDEX records.

Corrective Action: No action is required.

DSHD7GI DELETING USER AND ORPHAN INDEX RECORDSLink copied to clipboard

Explanation: This information message is issued by the CTVCLMIG utility and indicates that the utility has entered the stage where it is deleting expired USER and orphaned INDEX records.

Corrective Action: No action is required.

Messages DSHG00 through DSHGxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DSHG80I CLEANING OF MIGRATED USER REPORTS LIST FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTVCLMIG utility, which cleans entries from the Migrated User Report List file, has started.

Corrective Action: No action is required.

DSHG82E LOCATE ERROR FOR "`dsn`", RC=`rc`Link copied to clipboard

Explanation: The CTVCLMIG utility encountered a CDAM file name that could not be found in the catalog. The dsn data set may have been deleted or uncataloged.

The dsn data set is ignored.

Corrective Action: Check the output of the CTVCLMIG utility, and try to resolve the problem.

DSHG83I CLEANING OF MIGRATED USER REPORTS LIST FILE ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTVCLMIG utility, which cleans entries from the Migrated User Report List file, has ended without errors.

Corrective Action: No action is required.

DSHG84S CLEANING OF MIGRATED USER REPORTS LIST FILE ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTVCLMIG utility, which cleans entries from the Migrated User Report List file, ended with errors. The problem is described by earlier messages.

The utility ends with a return code of 08.

Corrective Action: Check the earlier error messages, correct the problem, and rerun the job.

DSHG85S INVALID INPUT PARAMETERLink copied to clipboard

Explanation: An invalid parameter was specified in the PARM field of the EXEC JCL statement activating the CTVCLMIG utility and passed to the CTVCLMIG utility. The only valid parameter values are MIG or blank.

The utility ends with a return code of 08.

Corrective Action: Correct the JCL and rerun the job.

DSHG86W NOLOCATE OPTION IS NOT ALLOWED WHEN TAPE LIST IS REQUIREDLink copied to clipboard

Explanation: The NOLOCATE parameter was specified for the CTVCLMIG utility while the utility was being used to produce a list of expired tapes. To produce a list of expired tapes, CTVCLMIG must issue a LOCATE option for migrated files.

LOCATE is issued for the migrated files.

Corrective Action: Refer to the INCONTROL for z/OS Utilities Guide to determine what parameters are required for CTVCLMIG to produce a list of current tapes. Adjust the utility parameters as necessary and rerun CTVCLMIG.

DSHG88I READING SYSDATA RECORDSLink copied to clipboard

Explanation: This information message indicates that the CTVCLMIG utility started reading SYSDATA records. To calculate the time used for this stage of the utility, compare the time stamp of this message with the time stamp of the next DSHG8AI message.

Corrective Action: No action is required.

DSHG89I `num` SYSDATA RECORDS READLink copied to clipboard

Explanation: This information message indicates the number of records in the SYSDATA file.

Corrective Action: No action is required.

DSHG8AI DELETING USER RECORDSLink copied to clipboard

Explanation: This information message indicates that the CTVCLMIG utility started deleting user records. To calculate the time used for this stage of the utility, compare the time stamp of this message with the time stamp of message the next DSHG8BI message.

Corrective Action: No action is required.

DSHG8BI DELETING SYSDATA RECORDSLink copied to clipboard

Explanation: This information message indicates that the CTVCLMIG utility started deleting SYSDATA records. To calculate the time used for this stage of the utility, compare the time stamp of this message with the time stamp of the next DSHG8CI message.

Corrective Action: No action is required.

DSHG8CI `num` USER RECORDS READLink copied to clipboard

Explanation: This information message indicates the total number of records that have been read.

Corrective Action: No action is required.

DSHG8DE SYSDATA RECORD NOT FOUND FOR USER RECORD `userName jobName`ODATE= `recordOdate` UKEY= `recordKey`Link copied to clipboard

Explanation: During a run of the CTVCLMIG utility, Control-V found a USER record with no matching SYSDATA record. Unless requested by means of the NOSYS parameter, the utility scans all user records in the Migrated User Report file, and checks if each has a matching SYSDATA record. If a SYSDATA record is not found, this message is issued and the user record is deleted.

The variables in this message are:

userName - User name for the report entry.
jobName - Job name for the report entry.
recordOdate - ODATE for the report entry.
recordKey - Full key for the report entry.

The user record is deleted. IOA should not be able to delete SYSDATA records from the User screen.

Corrective Action: Investigate the cause of this error. This error may indicate a problem with the SORT utility used by the CTVCLMIG utility.

DSHG8EE SYSDATA RECORD NOT FOUND FOR INDEX RECORD `jobName` ODATE = `odate` XKEY = `key`Link copied to clipboard

Explanation: During a run of the CTVCLMIG utility, Control-V found an index record with no matching SYSDATA record. The CTVCLMIG utility scans all index records in the Migrated User Report List file and checks if they have a matching SYSDATA record.

The variables in this message are:

jobName - the job name for the index record
odate - the ODATE for the index record
key - the index key for the index record

The index record and the index file are deleted. IOA should not be able to delete SYSDATA records from the User Report List screen.

Corrective Action: Investigate the cause of this error. If the cause is not found, contact BMC Customer Support.

DSHG8FE USER RECORD IS NOT FOUND FOR SYSDATA RECORD `jobName` ID `jobId` ODATE= `odate` XKEY= `counter`Link copied to clipboard

Explanation: The Migrated User Report file contains an "orphan" SYSDATA record, meaning a record that is not referred to by any USER record.

This message might also be issued when the CTVCLMIG utility is called with the NOSYS parameter set to S.

The variables in this message are:

jobName - the name of the job to which the orphan SYSDATA record belongs
jobId - the MVS identifier of the job to which the orphan SYSDATA record belongs
odate - the originating date of the report to which the orphan SYSDATA record belongs
counter - the counter part of the orphan SYSDATA record key

The orphan SYSDATA record is removed from the Migrated User Report file.

Corrective Action: No action is required.

DSHG8GE CONTROL-M/TAPE API START ERROR RC= `rc` REASON= `rsn` URC= `urc`Link copied to clipboard

Explanation: An error occurs when the CTVCLMIG utility tries to start the Control-M/TAPE interface CTTAPI.

The variables in this message are:

rc - return code from CTTAPI
rsn - reason code from CTTAPI
urc - user reason code from CTTAPI

The CTVCLMIG utility ends with a return code of 08.

Corrective Action: Perform the following steps:

Examine the return and reason code to identify the problem. Refer to message CTT203I for an explanation of these codes.
Correct the problem.
Rerun the utility.

DSHG8HE CTT SCRATCH ERROR `dsname` VOL= `volser` LAB= `label` RC= `rc` REASON= `rsn` URC= `urc`Link copied to clipboard

Explanation: An error occurs when the CTVCLMIG utility calls CTTAPI to scratch data set dsname stored on volume volser with seq.number label.

The variables in this message are:

dsname - the data set name
volser - the volume name
label - the sequence number of the volume
rc - return code from CTTAPI
rsn - reason code from CTTAPI
urc - user reason code from CTTAPI

The CTVCLMIG utility continues to work.

Corrective Action: Perform the following steps:

Examine the return and reason code to identify the problem. Refer to message CTT203I for an explanation of these codes.
Contact your INCONTROL administrator.

DSHG8IE CTT SCRATCH ERROR VOLSER= `volser` RC= `rc` REASON= `rsn` URC= `urc`Link copied to clipboard

Explanation: An error occurs when the CTVCLMIG utility calls CTTAPI to scratch volume volser.

The variables in this message are:

volser - the volume name
rc - return code from CTTAPI
rsn - reason code from CTTAPI
urc - user reason code from CTTAPI

The CTVCLMIG utility continues to work.

Corrective Action: Perform the following steps:

Examine the return and reason code to identify the problem. Refer to message CTT203I for an explanation of these codes.
Contact your INCONTROL administrator.

DSHG8KE PARAMETER CTT IS SPECIFIED WHEN CONTROL-M/TAPE IS NOT ACTIVELink copied to clipboard

Explanation: The user specified the CTT parameter to the CTVCLMIG utility to notify Control-M/Tape of deleted Control-V data sets or released volumes, but Control-M Tape is not active in the system.

The CTVCLMIG utility ends with a return code of 08.

Corrective Action: Start the CTTINIT procedure to activate Control-M/TAPE. Then rerun the CTVCLMIG utility.

DSHG8ME PARAMETER CTT IS SPECIFIED WHEN PARAMETER CTVINTR IN CTTPARM IS NONELink copied to clipboard

Explanation: The user specified the CTT parameter to the CTVCLMIG utility to notify Control-M/Tape of deleted Control-V datasets or released volumes, but parameter CTVINTR in the CTTPARM member is set to NONE.

The CTVCLMIG utility ends with a return code of 08.

Corrective Action: Check the CTTPARM member. Refer Control-M/Tape experts to set the needed value of the parameter CTVINTR. Then rerun the CTVCLMIG utility.

DSHG8NE INVALID EXPDATE PARAMETERLink copied to clipboard

Explanation: An invalid date is specified in the EXPDATE parameter or this parameter is specified in the PROD mode, although it should be specified in the TEST mode only.

The CTVCLMIG utility ends with a return code of 12.

Corrective Action: Correct the EXPDATE parameter and rerun the utility.

DSHG8PW FILE `dsName` MOVED FROM `vsavol` TO `catvol` OUTSIDE OF CONTROL-VLink copied to clipboard

Explanation: The CTVCLMIG utility detected an expired migrated file, which was moved from the tape volume to which it was migrated to another volume outside of Control-V. This warning message is issued when the utility runs in the modes LOC=NOLOCATE and TAPELIST=YES.

The variables in this message are:

dsName - Migrated dataset name.
vsavol - Volume serial number to which the file was migrated.
catvol - Volume serial number where the file currently resides.

Corrective Action: This message warns the user that the list of expired tapes issued by the utility can be incorrect. The user should try to find out if the vsavol tape volume has been completely moved to catvol, or only some files have been moved to catvol. In the first case, the list of expired tapes issued by the utility is correct and the message can be ignored. In the second case, the message means that the list of expired tapes issued by the utility can be incorrect and should not be used. If the migrated files are moved from one tape volume to another outside of Control-V, CTVCLMIG can issue a correct list of expired tapes in LOC=LOCATE mode only.

DSM messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages DSMC00 through DSMCxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DSMC01I UPDATING OF ACTIVE USER REPORTS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDDSM program started. The CTDDSM program is the second step of the CTDDELRP utility. It updates and deletes records from the Active User Report file according to information in the work file built by the first step of the CTDDELRP utility.

Corrective Action: No action is required.

DSMC02I UPDATING OF ACTIVE USER REPORTS FILE ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDDSM program ended without errors. The CTDDSM program is the second step of the CTDDELRP utility. It updates and deletes records from the Active User Report file, according to information in the work file built by the first step of the CTDDELRP utility.

Corrective Action: No action is required.

DSMC03S UPDATING OF ACTIVE USER REPORTS FILE ENDED WITH ERRORSLink copied to clipboard

Explanation: An unrecoverable processing error was encountered by the CTDDSM program. The CTDDSM program, which is the second step of the CTDDELRP utility, updates and deletes records from the Active User Report file, according to information in the work file built by the first step of the CTDDELRP utility.

The CTDDSM program terminates with a condition code of 8.

Corrective Action: Check previously issued IOA Log file and system log messages to determine the cause of the error. Correct the problem and rerun the job.

DSMC05E OPEN OF INPUT FILE FAILED. DDNAME ‘DADSOIN’Link copied to clipboard

Explanation: The CTDDSM program failed to open the work file referenced by the DADSOIN DD statement.

The CTDDSM program is the second step of the CTDDELRP utility. It updates and deletes records from the Active User Report file, according to information in the work file built by the first step of the CTDDELRP utility.

The CTDDSM program terminates with a condition code of 08.

Corrective Action: Check previously issued IOA Log file and system log messages to determine the cause of the error. Correct the problem and rerun the job.

DSMC06E OPEN OF REPORT LIST FAILED. DDNAME "DAREPLA "Link copied to clipboard

Explanation: The CTDDELRP utility was called with the REPLIST parameter set to YES, but one of the following occurred:

It failed to open the data set specified in the DAREPLA DD statement.
The JCL of the utility contains no DAREPLA DD statement.

The utility terminates with a return code of 8.

Corrective Action: Correct the JCL and recall the utility.

DSMC07E INVALID PARAMETER: - `parmValue`Link copied to clipboard

Explanation: The CTDDELRP utility has been called with the REPLIST parameter set to a value that is invalid.

Valid values for the REPLIST parameter are:

In this message, parmValue is the incorrect value that was entered for the REPLIST parameter.

The utility terminates with a return code of 8.

Corrective Action: Call your INCONTROL administrator.

DSO messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages DSO900 through DSO9xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DSO930I DELETE OF UNNEEDED REPORTS STARTEDLink copied to clipboard

Explanation: This information message is the normal start message of the CTDDELRP utility. CTDDELRP is used to clean unnecessary entries from the Active User Report List file, and to erase the compressed sysout data sets that belong to them from the disk.

Corrective Action: No action is required.

DSO931I DELETE OF UNNEEDED REPORTS ENDED OKLink copied to clipboard

Explanation: This information message is the normal end message of the CTDDELRP utility. CTDDELRP is used to clean unnecessary entries from the Active User Report List file, and to erase the compressed sysout data sets that belong to them from the disk.

Corrective Action: No action is required.

DSO933S DELETE OF UNNEEDED REPORTS ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTDDELRP utility ended with errors. Earlier messages describe the problem.

The CTDDELRP utility ends with a return code of 08.

Corrective Action: Check the earlier messages, correct the problem, and rerun the job.

DSO934E INSUFFICIENT STORAGE. ATTEMPT TO RERUNLink copied to clipboard

Explanation: Insufficient storage to run the CTDDELRP utility.

Corrective Action: Increase the REGION size of the utility and rerun.

DSO935I DATASET dsn WILL BE DELETED

Explanation: This information message is from the CTDDELRP utility, which is cleans unnecessary entries from the Active User Report List file and deletes CDAM data sets. It is issued when the compressed data set is added to list of data sets to be scratched. The data set is deleted in the next step of the job.

Corrective Action: No action is required.

DSO936I JOB `jobName` JOBID `jobId` IS WAITING FOR BACKUP BY `missionName missionName missionName missionName missionName missionName`Link copied to clipboard

Explanation: This information message from the CTDDELRP utility, which cleans unnecessary entries from the Active User Report List file, indicates that the jobName job is ready for backup by any of the Backup Missions listed. The sysout compressed data sets for the jobName job are not deleted until one of the Backup Missions listed runs successfully.

Corrective Action: No action is required.

DSO937E INVALID PARAMETER: - `parm`Link copied to clipboard

Explanation: Invalid parameter for the CTDDELRP Control-D utility. This error message is issued by the CTDDELRP Control-D utility, which cleans unnecessary entries from the Active User Report List file. For more details, refer to the CTDDELRP utility in the INCONTROL for z/OS Utilities Guide.

The CTDDELRP Control-D utility terminates with a condition code of 08. The Active User Report List file is not cleaned.

Corrective Action: Correct the parameter syntax in the CTDDELRP utility.

DSO938E MISSING PARAMETER AFTER: - `parm`Link copied to clipboard

Explanation: The subparameter after parm is missing. This error message is issued by the CTDDELRP Control-D utility, which cleans unnecessary entries from the Active User Report List file. For details, refer to the CTDDELRP utility in the INCONTROL for z/OS Utilities Guide.

The CTDDELRP Control-D utility terminates with a condition code of 08. The Active User Report List file is not cleaned.

Corrective Action: Correct the parameter syntax in the CTDDELRP utility.

DSO939E REDUNDANT PARAMETER: - `parm`Link copied to clipboard

Explanation: There is a redundant parameter for the CTDDELRP Control-D utility. The CTDDELRP Control-D utility, which cleans unnecessary entries from the Active User Report List file, issues this message. For details, refer to the CTDDELRP utility in INCONTROL for z/OS Utilities Guide.

The CTDDELRP Control-D utility terminates with a condition code of 08. The Active User Report List file is not cleaned.

Corrective Action: Correct the parameter syntax in the CTDDELRP utility.

DSO93CI PRIMARY RECORD IS MISSING FOR USER `recipient` JOB `jobname` JOBID `JobID`Link copied to clipboard

Explanation: The CTDDELRP utility cannot find the primary USER record (the first record in a chain of metadata records describing a report) in the Active User Reports file. CTDDELRP removes any metadata records related to the report from the Active User Report file.

Corrective Action: No user response is required.

DSO93DS THERE ARE REPORTS REQUESTED FOR MIGRATION. CONTROL-V SHOULD BE INSTALLEDLink copied to clipboard

Explanation: The CTDDELRP utility discovered that although in the Active User Reports file there are reports requested for migration, no Control-V environment is installed. CTDDELRP is terminated.

Corrective Action: Install a Control-V environment.

DSO93EI JOB `jobname` JOBID `JobID` IS HELD BY BACKUP MISSION `mission` OR `mission` OR ... ODATE= `orgdate` TIMESTAMP= `timestamp`Link copied to clipboard

Explanation: The CTDDELRP utility did not delete the jobname report from the Active User Report file, because the report is held by the pending or running backup mission.

Corrective Action: You can use the BKPRESET utility to reset the status of pending backup missions and their reports.

DSO93FI JOB `jobname` JOBID `JobID` IS HELD BY MIGRATION `migration` MISSION `mission` TIMESTAMP=`timestamp`Link copied to clipboard

Explanation: The CTDDELRP utility did not delete the jobname report from the Active User Report file, because the report is held by the pending or running migration mission.

Corrective Action: You can use the MIGRESET utility to reset the status of pending migration missions and their reports.

DSO942E OPEN OF PARAMETERS FILE FAILED. DDNAME "DADELIN"Link copied to clipboard

Explanation: Open of parameters file for the CTDDELRP utility failed. Possible causes are:

The DADELIN DD statement is missing.
The data set described by the DADELIN DD statement cannot be opened for sequential read.

The utility stops executing with condition code 12.

Corrective Action: Correct the JCL of the job, and rerun it.

DSO943I JOB `jobName` JOBID `jobID` USER `usr` IS WAITING FOR PRINT BY `missionName missionName missionName missionName`Link copied to clipboard

Explanation: This information message indicates that the jobName job is ready for printing by any of the Printing Missions listed. The sysout compressed data sets for the jobName job is not deleted until one of the Printing Missions listed runs successfully, that is, until the report is printed.

The information about the requested report is provided in message CTDI0CI, which follows this message.

Corrective Action: No action is required.

DSO945I JOB `jobName` ODATE `odate` USER `user` IS REJECTED BY `approvalName` Link copied to clipboard

Explanation: This information message indicates that the report with the specified jobName, odate, user has not been deleted by the utility because it has been rejected by the approvalName. The report name is provided in the CTDI0CI message which follows this message. CTDDELRP does not delete such reports, if the special parameter REJECTED is not specified for this utility.

Corrective Action: No action is required.

Messages DSOA00 through DSOAxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DSOA30E OPEN OF SORT FILE FAILED. DDNAME `ddName`Link copied to clipboard

Explanation: The SORT utility invoked by the CTDDELRP utility failed to open ddName DD name.

The CTDDELRP utility stops.

Corrective Action: Ensure all DD statements are valid. Restart the CTDDELRP utility.

DSOA31E INVALID RETURN CODE FROM SORT, RC= `rc`Link copied to clipboard

Explanation: Internal sort program ended with errors. This message is from the CTDDELRP utility, which cleans unnecessary entries from the Active User Report List file. The utility uses the site sort program internally.

The utility terminates with a condition code of 08.

Corrective Action: Refer to the sort messages for the job and to the user manual for the sort facility used at your site.

DSOA32I SYSDATA RECORD IS MISSING FOR USER `userId` JOB `jobName` JOBID `jobID reportName`Link copied to clipboard

Explanation: This information message indicates that the CTDDELRP utility cannot find a SYSDATA record indicated by a user record in the Active User Report List file.

CTDDELRP cleans unnecessary entries from the Active User Report List file. The SYSDATA record was probably manually deleted from the Active User Reports List.

The user record is deleted to maintain database integrity; processing continues.

Corrective Action: No action is required.

DSOA33I SYSDATA RECORD WITHOUT USERS: JOB `jobName` JOBID `jobID`Link copied to clipboard

Explanation: This information message indicates that no user report entry points to this SYSDATA record in the Active User Report List file. The CTDDELRP utility, which is used to clean unnecessary entries from the Active User Report List file and to delete CDAM data sets, issues this message. The user records were probably deleted from the Active User Report List. The report does not belong to any user.

If the NOREPORT parameter was specified, the SYSDATA record and CDAM data set are deleted to maintain database consistency, and processing continues.

Corrective Action: No action is required.

DSOA34E OPEN OF SCRATCH LIST FAILED. DDNAME "DASCRLST"Link copied to clipboard

Explanation: The CTDDELRP Control-D utility, which cleans unnecessary entries from the Active User Report List file, failed to open the scratch list file using a DASCRLST DD statement.

Possible causes are:

The DASCRLST DD statement is missing.
The data set described by the DASCRLST DD statement cannot be opened for a sequential write.

The utility terminates with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

DSOA35I WAITING FOR ANOTHER CTDDELRP OR RESTORE JOB TO TERMINATELink copied to clipboard

Explanation: This information message indicates that the CTDDELRP utility is waiting for another CTDDELRP job or a restore job to terminate. CTDDELRP is cleans unnecessary entries from the Active User Report List file. To maintain data integrity, CTDDELRP cannot run concurrently with another CTDDELRP or a restore job.

When the contending job terminates, CTDDELRP resumes processing.

Corrective Action: No action is required.

DSOA36E OPEN OF "DAWORK" DD CARD FAILEDLink copied to clipboard

Explanation: Open of the Active Transition file failed. This file is referenced by the DAWORK DD statement. The DAWORK DD statement is probably missing.

This error message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

CTDDSO terminates with a condition code of 08.

Corrective Action: Check for previous messages indicating the reason for the open failure. Correct the problem, and rerun the CTDDELRP utility.

DSOA37I JOB `jobName` JOBID `jobID` IS WAITING FOR MIGRATION BY `missionName`Link copied to clipboard

Explanation: This information message is produced by the CTDDELRP utility. It indicates the jobName job is ready for migration by the missionName Migration Mission. The sysout compressed data sets for the jobName job is not deleted until the Migration Mission runs successfully.

Corrective Action: No action is required.

DSOA38I SYSDATA RECORD IS MISSING FOR INDEX `index`. JOB `jobName` JOBID `jobID` WILL BE DELETEDLink copied to clipboard

Explanation: This information message indicates that the CTDDELRP utility, which cleans unnecessary entries from the Active User Report List file, cannot find a SYSDATA record that corresponds to an index record in the Active User Report List file. The SYSDATA record was probably manually deleted from the Active User Reports List file.

The index record and index file are deleted to maintain database integrity. Processing continues.

Corrective Action: No action is required.

DSOA39E NO INPUT PARAMETERS WERE SUPPLIEDLink copied to clipboard

Explanation: The CTDDELRP Control-D utility, which is used to clean unnecessary entries from the Active User Report List file, did not receive input parameters from a DADELIN DD statement. The CTDDELRP Control-D utility should be supplied with input parameters indicating actions for the utility to perform.

The CTDDSO program terminates with a condition code of 08.

Corrective Action: Verify that input parameters are specified by means of a DADELIN DD statement, and rerun the job.

DSOA3AE OPEN OF "DAXREP" FAILEDLink copied to clipboard

Explanation: The CTDDELRP utility, which cleans unnecessary records from the Active User Report List file, failed to open the Print Control Record Scratch file referenced by the DAXREP DD statement. The DAXREP DD statement is probably missing.

This error message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

The CTDDSO program terminates with a condition code of 08.

Corrective Action: Correct the error, and rerun the CTDDELRP utility.

DSOA3BE I/O ERROR WRITING TO XREP DELETE FILE. DDNAME "DAXREP"Link copied to clipboard

Explanation: An I/O error occurred while writing the file referenced by the DAXREP DD statement.

This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

The CTDDELRP utility terminates.

Corrective Action: Run the CTDBLXRP utility to rebuild the Print Control Record. Rerun the CTDDELRP utility.

DSOA3CE INSUFFICIENT SPACE ALLOCATED TO XREP DELETE FILE. DDNAME "DAXREP"Link copied to clipboard

Explanation: The file referenced by the DAXREP DD statement has insufficient space allocated. This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

The CTDDELRP utility continues processing.

Corrective Action: To prevent this problem in the future, allocate more space to the file referenced by the DAXREP DD statement. Run the CTDBLXRP utility to rebuild the Print Control Record.

DSOA3DE "FE" PRINT SUPPORT ERROR. RETURN CODE `rc`Link copied to clipboard

Explanation: An error was encountered while trying to delete a Print Control Record. This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

Possible values of rc are:

016 - Invalid Function.
024 - Open Error.
028 - Error in Sort.

The CTDDELRP utility continues processing.

Corrective Action: Run the CTDBLXRP utility to rebuild the Print Control Record.

DSOA3EI * PARM=TEST SPECIFIED - SIMULATION MODE *Link copied to clipboard

Explanation: This information message indicates that the CTDDELRP utility is running in SIMULATION mode. In SIMULATION mode, the CTDDELRP utility produces a report that indicates which entries would have been deleted and which data sets would have been erased if the utility were running in PRODUCTION mode.

Corrective Action: Examine the output of the CTDDELRP utility to determine if the proper entries would have been deleted from the Active User Report List file and the proper CDAM data sets would have been erased. Make any changes required to prevent the deletion of needed Active User Report List entries or CDAM data sets.

Rerun the utility in PRODUCTION mode to delete unneeded entries in the Active User Report List file and to erase CDAM data sets that no longer have references in that file.

DSOA3FI MESSAGE= `integer msg`Link copied to clipboard

Explanation: This information message is issued during the first step of the termination of the CTDDELRP utility. It provides statistics about the number of records processed by the CTDDELRP utility.

Possible values for msg, which explains integer, are shown in the following table:

msg	Explanation
RECORDS READ FROM ACTIVE USER FILE	The total number of records in the Active User file
USER RECORDS WILL BE DELETED	The number of user records to be deleted from the Active User file
USER RECORDS COPIED TO HISTORY FILE	The number of user records copied from the Active User file to the History Report List file
USER RECORDS COPIED TO MIGRATION FILE	The number of user records copied from the Active User file to the Migrated Report List file
SYSDATA RECORDS WILL BE DELETED	The number of sysdata records to be deleted from the Active User file
SYSDATA RECORDS COPIED TO HISTORY FILE	The number of sysdata records copied from the Active User file to the History Report List file
SYSDATA RECORDS COPIED TO MIGRATION FILE	The number of sysdata records copied from the Active User file to the Migrated Report List file
INDEX RECORDS WILL BE DELETED	The number of index records to be deleted from the Active User file
NOTEPAD RECORDS WILL BE DELETED	The number of Notepad records to be deleted from the Active User file
NOTEPAD RECORDS COPIED TO HISTORY FILE	The number of Notepad records copied from the Active User file to the History Report file
NOTEPAD RECORDS COPIED TO MIGRATION FILE	The number of Notepad records copied from the Active User file to the Migrated Report List file

Corrective Action: No action is required.

Messages DSOB00 through DSOBxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

DSOB39I RC=16 IN READKEY FROM HST. RECORD WITH KEY= `userName jobName counter` IS ADDEDLink copied to clipboard

Explanation: This information message indicates that the CTDDELRP utility added the record with the specified key, because it did not find that record when it was performing the READKEY function.

A return code of 16 means that the specified record was not in the History User file.

The record key is composed of the user name (8 characters), the job name (8 characters), and the counter (16 characters).

The CTDDELRP utility adds the missing record.

Corrective Action: No action is required.

DSP messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages DSP100 through DSP1xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

DSP1A0I `mediaName` - NUMBER OF DEVICES = `iii` NUMBER OF ACTIVE DEVICES = `jjj`Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command to indicate the following:

iii devices are assigned to media mediaName.
jjj active devices are assigned to media mediaName.

This message is preceded by message IOA1A1I or DSP1A1I, which supplies the IOA Archive Server name and media name for which the DISPLAY message was issued.

Corrective Action: No action is required.

DSP1A1I `server` - MEDIA `mediaName` STATUS DISPLAY:Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. This message is the header for messages that provide information about the status of media mediaName.

Corrective Action: No action is required.

DSP1A2I `mediaName` - MEDIA TYPE = `media_typ` SYSTEM UNIT NAME = `name`Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. This message identifies the media type and system unit name defined in the IOASPRM member in the IOA Archive Server Installation Parameters.

Corrective Action: No action is required.

DSP1A3I `mediaName` - STATUS = `status`Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command to provide information about the current status of media mediaName.

Corrective Action: No action is required.

DSP1A4I `mediaName` - NUMBER OF PENDING REQUESTS = `num`Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command to provide information about the number of pending requests for media mediaName.

Corrective Action: No action is required.

DSP1A5I `mediaName` - DEVICE STATUS PLATTER VOLSER DSNLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. It is the header for IOA1A6I or DSP1A6I messages, which provide information about the status of each device assigned to media mediaName.

Corrective Action: No action is required.

DSP1A6I `mediaName` - `device status platter volser dsn`Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. Each message describes a device assigned to media mediaName. This message follows message IOA1A5I or DSP1A5I, which provides the header for each field.

Corrective Action: No action is required.

DSP1A7I `mediaName` - DEVICE USE STATUS USER-ID VOLSER DSNLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. It is the header for IOA1A8I or DSP1A8I messages, which provide information about the status of each device assigned to media mediaName.

Corrective Action: No action is required.

DSP1A8I `mediaName` - `device use status userId volume dsn`Link copied to clipboard

Explanation: This information message is sent by the IOA Archive server to the console in response to a DISPLAY command. It follows message IOA1A7I, which provides the header for each field. Each occurrence of this message describes a device assigned to media mediaName.

The variables in this message are:

device - the name of the assigned device
use - Dedicated or Dynamic
status - Active, Inactive or Idle
userId - the user ID of the owner of the data set being retrieved by the device
volume - the serial number of the volume on which the data set is found
dsn - the data set name

The userId, volume, and dsn fields have values only when the device is active.

Corrective Action: No action is required.

DSP1A9I `mediaName` - DEVICE STATUS USER-ID DSNLink copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. This message is the header for message IOA1AAI, which provides information about the status of each device assigned to the media identified in the message.

Corrective Action: No action is required.

DSP1AAI `mediaName` - `deviceStatus userId dsn`Link copied to clipboard

Explanation: This information message is sent by the IOA Archive Server to the console in response to a DISPLAY command. Each message provides information about a device assigned to the media identified in the message. A message is issued for each device defined in the MAXCONN parameter in IOASPRM. These messages are preceded by message IOA1A9I, which provides the header for each field.

Possible values of deviceStatus are:

INACTIVE - Device not yet activated.
ACTIVE - Retrieving data requested by specified user from specified data set.
IDLE - Device is ACTIVE, but currently not working on any request.

Corrective Action: No action is required.

DSP1AEI `mediaName` - TVL: OWNER-ID `deviceTask`, NUM OF REQUESTS - `num` DSN `dsn`Link copied to clipboard

Explanation: This information message displays the content of the TVL, an element in the queue of the retrieval requests for tape mediaName.

The variables in this message are:

deviceTask - the owner-ID of the device task currently working on the request
num - the number of pending requests on that tape volume
dsn - the name of the data set

Corrective Action: No action is required.

DSR messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS product.

Messages DSR100 through DSR1xxLink copied to clipboard

This group includes messages for the Control-M for z/OS product.

DSR100E INVALID [DATE|TIME] PARAMETER `parameter`Link copied to clipboard

Explanation: This error message indicates that the time or date parameter contains invalid values.

Corrective Action: Correct the parameters and resubmit the job.

DSR101E THE PARM FORMAT MUST BE YYMMDDHHMM,YYMMDDHHMMLink copied to clipboard

Explanation: This error message indicates an incorrect format in the time and date parameters

Corrective Action: Correct the parameters according to the format in the message and resubmit the job.

DSR102E ERROR LOADING "CTMDSRR" ROUTINELink copied to clipboard

Explanation: This error message indicates that the load module of the CTMDSRR routine is missing.

Corrective Action: Contact BMC Customer Support.

DSR103E ERROR OPENING THE `ddname` DDLink copied to clipboard

Explanation: This error message indicates that an error occurred when opening the dataset referred by the DD statement.

Corrective Action: Validate the dataset referred by the DD statement.

DSR104E FAILED TO INIT 'IOAENV'Link copied to clipboard

Explanation: This error message indicates a problem during the initiation of the IOA environment.

Corrective Action: Contact BMC Customer Support.

DSR105E DD-CARD `ddcard_name` NOT FOUNDLink copied to clipboard

Explanation: This error message indicates a missing DD statement in the JCL for the CTMDSR utility.

Corrective Action: Complete the missing DD statement in the JCL and resubmit the job.

DSR106E INVALID KEYWORD `'keyword'`Link copied to clipboard

Explanation: This error message indicates an incorrect keyword in the SYSIN DD statement of the CTMDSR utility.

Corrective Action: Correct the syntax of the keyword or the keyword value and resubmit the job.

DSR107E KEYWORD `keyword` ALREADY DEFINEDLink copied to clipboard

Explanation: This error message indicates that a keyword defined in the SYSIN DD statement appears more than once.

Corrective Action: Remove redundant keywords in the SYSIN DD statement.

DSR108W UNKNOWN SYSOUT OPTION ENCOUNTEREDLink copied to clipboard

Explanation: CTMDSR did not recognize a SYSOUT option. In the report, an option with an unknown type might be displayed.

Corrective Action: Contact BMC Customer Support.

DSR109E INTERNAL ERROR IN 'CTMDSRR' ROUTINE. RETURN CODE `return_code`, REASON CODE `reason_code`Link copied to clipboard

Explanation: This error message indicates that an internal error was encountered in the CTMDSRR routine.

Corrective Action: Contact BMC Customer Support.

DSR10AE THE SPECIFIED END TIME IS EARLIER THAN THE START TIMELink copied to clipboard

Explanation: The report end time specified in the SYSIN DD is earlier than the report start time.

Corrective Action: Correct the REPSTART and/or REPEND values and resubmit the job.

DUL messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages DUL900 through DUL9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

DUL951S INSUFFICIENT STORAGE TO RUN UTILITYLink copied to clipboard

Explanation: There is insufficient memory to run the IOADUL utility.

The utility terminates with a return code of 12.

Corrective Action: Increase the REGION size and rerun the utility.

DUL952S ERROR OPENING SEQUENTIAL FILELink copied to clipboard

Explanation: The IOADUL utility detected an error while opening a sequential file to which it is to unload the data.

The utility terminates with a return code of 16.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error and rerun the job. If error persists, contact BMC Customer Support.

DUL953S ERROR OPENING FILELink copied to clipboard

Explanation: The IOADUL utility detected an error when opening the IOA Access Method file referenced by the DADBS DD statement.

The utility terminates with a return code of 20.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error and rerun the job. If error persists, contact BMC Customer Support.

DUL955I UTILITY IOADUL STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOADUL utility started. The IOADUL utility unloads the records of an IOA Access Method file to a sequential file.

Corrective Action: No action is required.

DUL956I UTILITY ENDED WITH RETURN CODE `num`Link copied to clipboard

Explanation: This information message indicates that the IOADUL utility terminated with a return code of num.

The IOADUL utility terminates.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error and rerun the job. If error persists, contact BMC Customer Support.

DUL957S ERROR IN IOAPARM LOADINGLink copied to clipboard

Explanation: The IOADUL utility detected an error while loading the IOAPARM member.

The IOADUL utility terminates with a return code of 4.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error, and rerun the job. If the error persists, contact BMC Customer Support.

DUL958S ERROR READING THE DATABASELink copied to clipboard

Explanation: The IOADUL utility detected an error while reading the IOA Access Method file.

The IOADUL utility terminates with a return code of 24.

Corrective Action: Check the IOA Log and the system job log for more information. Correct the error, and rerun the job. If the error persists, contact BMC Customer Support.

DUL959S INVALID INPUT PARAMETERSLink copied to clipboard

Explanation: Invalid input parameters were specified when running the IOADUL utility.

The IOADUL utility ends with a return code of 28.

Corrective Action: Rerun the IOADUL utility using valid input parameters. For information on the valid parameters, see the IOADUL utility in the INCONTROL for z/OS Utilities Guide.

DUL960S MISSING INPUT PARAMETERSLink copied to clipboard

Explanation: No input parameters were specified for the IOADUL utility.

The IOADUL utility ends with a return code of 32.

Corrective Action: Rerun the IOADUL utility using valid input parameters. See the IOADUL utility in the INCONTROL for z/OS Utilities Guide for valid parameters.

DUL961I NUMBER OF COPIED RECORDS `num`Link copied to clipboard

Explanation: This information message displays the number of records copied from a database to a sequential file by the IOADUL utility.

Corrective Action: No action is required.

DVB messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages DVB300 through DVB3xxLink copied to clipboard

This group includes messages for the Control-O product.

DVB331S AUTOMATION LOG FILE MUST CONTAIN AT LEAST 100 RECORDSLink copied to clipboard

Explanation: The specified Automation Log file contains less that one hundred records. The CTODVB program checks the value specified for the ALREC# parameter in the CTOPARM member. It must indicate at least one hundred records.

Formatting of the Automation Log ends with a return code of 08.

Corrective Action: Check the ALREC# parameter in the CTOPARM member.

DVB332S ERROR OPENING AUTOMATION LOG FILELink copied to clipboard

Explanation: The CTODVB program was unable to open the Automation Log file.

The formatting of the Automation Log ends with a return code of 08.

Corrective Action: Do both of the following:

Check the CTOPARM member.
Ensure that the JCL matches the parameters specified in the CTOPARM member.

DVB333S ERROR FORMATTING AUTOMATION LOG FILELink copied to clipboard

Explanation: An I/O error was detected. The CTODVB program failed to execute an I/O operation with the Automation Log file.

Formatting of the Automation Log ends with a return code of 08.

Corrective Action: Check associated MVS messages detailing the cause of the error, for example, disk failure, incorrect data set, incorrect name or allocation parameters.

DVB334I FORMATTING OF AUTOMATION LOG FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that formatting of the Automation Log file has begun.

Corrective Action: No action is required.

DVB335I FORMATTING OF AUTOMATION LOG FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that formatting of the Automation Log file has ended successfully.

Corrective Action: No action is required.

DVB336S AUTOMATION LOG FILE WAS NOT BUILTLink copied to clipboard

Explanation: Formatting of the Automation Log file failed. This message follows other messages detailing the problem.

The formatting of the Automation Log ends with a return code of 08.

Corrective Action: Consult previous messages detailing the reason for the error.

DVB337S AUTOMATION LOG DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`Link copied to clipboard

Explanation: A dynamic allocation problem occurred. The CTODVB program attempted to dynamically allocate the Automation Log file but failed.

Formatting of the Automation Log file ends with return code 08.

Corrective Action: Do the following:

Refer to the IBM OS/390 Authorized Assembler Services Guide for an explanation of return code (rc) and the reason (rsn), and proceed accordingly.
Check the CTOPARM member.
Verify that an Automation Log file already exists for this CPU.

DVB338S INVALID PARAMETERS PASSED TO PROGRAMLink copied to clipboard

Explanation: The CTODVB program detected an error in the parameters passed to it.

Formatting of the Automation Log file ends with a return code of 08.

Corrective Action: Check the parameters passed to the program and correct them.

DVB339S NULL PARAMETERS PASSED TO PROGRAMLink copied to clipboard

Explanation: The CTODVB program was called with no parameters.

Formatting of the Automation Log file ends with a return code of 08.

Corrective Action: Check and correct the JCL.

DVL messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages DVL300 through DVL3xxLink copied to clipboard

This group includes messages for the Control-O product.

DVL341S AUTOMATION LOG FILE LEVEL INCONSISTENT WITH LEVEL OF CONTROL-OLink copied to clipboard

Explanation: The Automation Log file is not compatible with this release of Control-O. While opening an Automation Log file, the CTODVL program checks the file validity and usability. A mismatch was found between the release number of the Automation Log file and the release number of the program accessing it.

Action fails. The Automation Log file is not accessed.

Corrective Action: Do either or both of the following:

Check if the libraries specified in the STEPLIB and LINKLIST concatenation contain modules from different releases.
Check the Automation Log file data set name. If you are using an older release of the program or an old file, correct the error.

DVL342S ERROR OPENING AUTOMATION LOG FILELink copied to clipboard

Explanation: The CTODVL program was unable to open the Automation Log file.

The action fails. The Automation Log file is not accessed.

Corrective Action: Do any or all of the following:

Check the definitions in the CTOPARM member.
Check the JCL for errors.
Check the data set name for the Automation Log file.

DVL343S AUTOMATION LOG DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`Link copied to clipboard

Explanation: The CTODVL program was unable to dynamically allocate the Automation Log file.

Action fails. The Automation Log file is not accessed.

Corrective Action: Do any or all of the following:

See documentation on dynamic allocation in the IBM authorized guide to Assembler services for explanations of the return code (rc) and the reason code (rsn), and proceed accordingly.
Check the CTOPARM member.
Ensure that an Automation Log file exists for this CPU.

DVL344S AUTOMATION WRITE ERRORLink copied to clipboard

Explanation: An I/O error occurred. The CTODVL program did not succeed in performing an I/O operation on the Automation Log file.

Action fails. The Automation Log file is not accessed.

Corrective Action: If you cannot determine the reason for this I/O error (for example, a disk failure), contact BMC Customer Support.

DVL345S ERROR EXECUTING RDJFCBLink copied to clipboard

Explanation: The CTODVL program received a non-zero return code from system service RDJFCB. The CTODVL program failed to read the JFCB of the dynamically allocated Automation Log file.

Action fails. The Automation Log file is not accessed.

Corrective Action: Contact BMC Customer Support.

DVL346S ABEND `abCode` INTERCEPTED WHILE PROCESSING THE AUTOMATION LOGLink copied to clipboard

Explanation: The CTODVL program intercepted an abend while processing the Automation Log.

The action fails. The Automation Log file is not accessed.

Corrective Action: Contact BMC Customer Support.

DVL347S THE ALLOCATED AUTOMATION LOG FILE BELONGS TO ANOTHER CONTROL-O INSTALLATIONLink copied to clipboard

Explanation: The specified Automation Log file refers to another Control-O. While opening an Automation Log file, the CTODVL program checks the validity and usability of the file being opened. A mismatch was found between the current value specified for the CTOQNAME parameter in the CTOPARM member and the value of that parameter when the Automation Log file was formatted.

Action fails. The Automation Log file is not accessed.

Corrective Action: Do either or both of the following:

Ensure that you are not using load libraries that belong to another installation of Control-O.
Check if the CTOPARM member has changed.

DVL348S FILE NOT AN AUTOMATION LOG FILELink copied to clipboard

Explanation: The specified file is not a Control-O Automation Log file. While opening an Automation Log file, CTODVL checks the validity and usability the file. The specified file was not an Automation Log file.

Action fails. The Automation Log file is not accessed.

Corrective Action: Check if the formatting of the Automation Log file ended successfully. If it failed, redefine (reformat) the Automation Log.

DVL349S AUTOMATION LOG FILE IS BEING FORMATTED IT CANNOT BE ACCESSEDLink copied to clipboard

Explanation: The specified Automation Log file is currently being formatted. While opening the Automation Log file, the CTODVL program checks the validity and usability of the file. The specified file has a status incompatible with the requirements of the program.

Action fails. The Automation Log is not accessed.

Corrective Action: Check if the formatting of the Automation Log file ended successfully. If it failed, redefine (reformat) the Automation Log.

DVT messagesLink copied to clipboard

This group includes messages for the Control-V product.

Messages DVT100 through DVT1xxLink copied to clipboard

This group includes messages for the Control-V product.

DVT170I `mediaName` - DEVICE `deviceId` - IS STARTINGLink copied to clipboard

Explanation: This information message indicates that IOA Archive Server device deviceId allocated to media mediaName started.

Corrective Action: No action is required.

DVT171I `mediaName` - DEVICE `deviceId` - SHUT DOWN UPON REQUEST OF MAIN TASKLink copied to clipboard

Explanation: This information message indicates that the main task requested shutting down IOA Archive Server mediaName device deviceId.

Corrective Action: No action is required.

DVT172I `mediaName` - DEVICE `deviceId` - REASON: AN EMPTY REQUEST RECEIVEDLink copied to clipboard

Explanation: This message indicates that due to an internal error, a cache request received by the IOA Archive Server from device deviceId was empty. See accompanying message DVT178I or IOA178I for the name of the requested file.

The cache request is ignored.

Corrective Action: Notify your INCONTROL administrator.

DVT173E `mediaName` - DEVICE `deviceId` - REASON: EXTENT `ext` IS OUT OF FILELink copied to clipboard

Explanation: The IOA Archive Server received a cache request from device deviceId for a relative byte address (RBA) with an extent that is not included in the migrated file. See accompanying message DVT178I or IOA178I for the name of the requested file.

The cache request is ignored.

Corrective Action: Check the validity of the RBA ranges in the user record. Notify your INCONTROL administrator.

DVT174E `mediaName` - DEVICE `deviceId` - REASON: RC `rc` IN TRANSLATION TTRZ `ttttrrzz`Link copied to clipboard

Explanation: An internal error occurred when the IOA Archive Server translated a relative block number to a relative block address (RBA). See accompanying message DVT178I or IOA178I for the name of the requested file.

The request is ignored.

Corrective Action: Notify your INCONTROL administrator.

DVT175E `mediaName` - DEVICE `deviceId` - REASON: BLOCK `blockNum` IS OUT OF FILELink copied to clipboard

Explanation: The IOA Archive Server received a cache request from device deviceId with a relative block address (RBA) that caused return code rc in translating the TTR to a relative block number. See accompanying message DVT178I or IOA178I for the name of the requested file.

The request is ignored.

Corrective Action: Check the validity of the RBA ranges in the user record. Notify your INCONTROL administrator.

DVT176E `mediaName` - DEVICE `deviceId` - REASON: RC `rc` IN TRANSLATION BLOCK `blk_num`Link copied to clipboard

The request is ignored.

Corrective Action: Notify your INCONTROL administrator.

DVT177I `mediaName` - DEVICE `deviceId` - REASON: USER DOES NOT EXISTLink copied to clipboard

Explanation: This information message indicates that a user who issued a cache request to the IOA Archive Server is no longer logged on. See accompanying message DVT178I or IOA178I for the name of the requested file.

The cache request is ignored.

Corrective Action: Notify your INCONTROL administrator if this message is issued while the user is still logged on.

DVT178I `mediaName` - DEVICE `deviceId` - REQUEST FOR FILE `dsn` IGNOREDLink copied to clipboard

Explanation: This information message indicates that the user that issued a cache request to the IOA Archive Server is no longer logged on.

See messages: DVT172I or IOA172I, DVT173E or IOA173E, DVT174E or IOA174E, DVT175E or IOA175E, DVT176E or IOA176E, DVT177E or IOA177E, or DVT17DI or IOA17DI.

The cache request is ignored.

Corrective Action: If this message is issued while the user is still logged on, notify your INCONTROL administrator.

DVT179W `mediaName` - DEVICE `deviceId` - TEST ENQ FOR USER OF FILE `dsn` FAILED, RC `rc`Link copied to clipboard

Explanation: A system error occurred while testing the ENQ that indicates whether a user is logged on.

The system assumes that the user who issued the cache request is still logged on. The request is performed.

Corrective Action: Notify your INCONTROL administrator.

DVT17AI `mediaName` - DEVICE `deviceId` - UNABLE TO ALLOCATE DEDICATED DEVICELink copied to clipboard

Explanation: This information message indicates that the IOA Archive Server could not allocate device deviceId even though it is dedicated to the Server explicitly by means of the DEVADDR parameter or implicitly by a quantity of a unit name in the DEVQTY parameter.

If dedicated explicitly, the device possibly is disconnected. If dedicated implicitly, probably no device in the device group specified in the IOASPRM member for the mediaName media is available. See messages DVT190E or IOA190E and DVT192E or IOA192E in the IOA Log file for the error code and information code.

The Server tries to allocate the device at 3-minute intervals until stopped by a MODIFY command.

Corrective Action: Use the error code and information code to determine why the allocation failed. See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the return code received. Ask the operator to correct the problem and restart the device.

DVT17BI `mediaName` - DEVICE `deviceId` - UNABLE TO ALLOCATE DEVICE DYNAMICALLYLink copied to clipboard

Explanation: This information message indicates that the IOA Archive Server could not allocate device deviceId which should be allocated dynamically. Probably none of the devices in the device group specified in the IOASPRM member for the mediaName media is available. See messages DVT190E or IOA190E and DVT192E or IOA192E in the IOA Log file for the error code and info code.

The Archive Server tries to allocate the device five times, at two minute intervals. If it does not succeed, device deviceId is terminated.

DVT17CI `mediaName` - DEVICE `deviceId` - SHUT DOWN BECAUSE OF INTERNAL ERRORLink copied to clipboard

Explanation:Highlighted, unrollable message.

This message indicates that an internal error occurred while accessing device deviceId.

The cache request that generated the error is ignored. The activity that used this device is restarted.

Corrective Action: Notify your INCONTROL administrator.

DVT17DI `mediaName` - DEVICE `deviceId` - SHUT DOWN BECAUSE OF ABEND `Snnn`Link copied to clipboard

Explanation:Highlighted, unrollable message.

This message indicates that an abend occurred while accessing device deviceId.

The cache request which caused the abend is ignored. The activity which used this device will be restarted.

Corrective Action: Notify your INCONTROL administrator.

DVT17EE `mediaName` - DEVICE `deviceId` - ERROR IN FDB OF FILE `fileName`Link copied to clipboard

Explanation: The file descriptor block that is the first block of the migrated CDAM file contains invalid information.

The migrated report cannot be accessed.

Corrective Action: Print the first block of the migrated CDAM file, for example, using IDCAMS Print Dump. Then, contact BMC Customer Support.

DVT17GI `mediaName` USER: `userId`, TIME: `time`, READS: `reads`, CPU: `cpu`, BLOCKS: `blocks`, FILE: `dsName`Link copied to clipboard

Explanation: This information message is sent to IOALOG when the cache request is performed by the IOA Archive Server. The message is optional. It is issued only when the STATV parameter in the IOASPRM member is set to Y.

The variables in this message are:

mediaName - name of the media where the migrated CDAM resides
userId - the ID of the user who issued the request
time - the elapsed time (seconds)
reads - the total number of blocks read from the migrated CDAM
cpu - the CPU usage time (milliseconds)
blocks - the number of blocks cached
dsName - the CDAM dataset name

Corrective Action: No action is required.

DVT180S `mediaName` - DEVICE `deviceId` - UNABLE TO ACQUIRE STORAGE FOR `blockId`, RC IS `rc`Link copied to clipboard

Explanation: IOA Archive Server device deviceId is unable to acquire storage space for a BLKLST, FDB, CMP, CACHE or RDBUF block. See accompanying message DVT178I or IOA178I for the name of the requested file.

Execution of the task on device deviceId is terminated.

Corrective Action: Restart the IOA Archive Server. Re-IPL if necessary. Notify your INCONTROL administrator.

DVT181S `mediaName` - DEVICE `deviceId` - UNABLE TO {ENQ | DEQ} ON `resourceName`. RC IS `rc`Link copied to clipboard

Explanation: The IOA Archive Server for device deviceId was unable to ENQ or DEQ on a key resource, where resourceName is the name of a volume, platter or device.

Execution of the task on device deviceId is terminated.

Corrective Action: Restart the IOA Archive Server. Re-IPL if necessary. Notify your INCONTROL administrator.

DVT190E `mediaName` - DEVICE `deviceId` - UNABLE TO ALLOCATE FILE `dsn`Link copied to clipboard

Explanation: File dsn could not be dynamically allocated on media mediaName by the IOA Archive Server device deviceId. See message DVT192E or IOA192E for the error code and info code.

The request is ignored.

Corrective Action: Use the error code and information code to determine why the allocation failed. See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the return code received. Correct the problem. Restart the IOA Archive Server.

DVT191E `mediaName` - DEVICE `deviceId` - UNABLE TO DEALLOCATE FILE `dsn`Link copied to clipboard

Explanation: The specified file could not be deallocated on the specified media when switching to another file in the IOA Archive Server device task. See message DVT192E or IOA192E for the error code and info code.

The next request and all future requests are ignored until deallocation succeeds.

Corrective Action: Use the error code and information code to determine why deallocation failed. Correct the problem. Restart the IOA Archive Server.

DVT192E `mediaName` - DEVICE `deviceId` - ERR + INFO CODE IS `error`+ `infoCode`Link copied to clipboard

Explanation: This message accompanies messages IOA190E or DVT190E and IOA191E or DVT191E. It provides the error code and information code for a failed dynamic allocation or deallocation.

Corrective Action: Use the error code and information code to determine the problem and correct it.

DVT193E `mediaName` - DEVICE `deviceId` - I/O ERROR `error`Link copied to clipboard

Explanation: The I/O error identified in this message occurred.

The request that caused the I/O error is ignored.

Corrective Action: Correct the problem in the file. Retry.

DVT194E `mediaName` - DEVICE `deviceId` - UNABLE TO OPEN FILE `dsn`Link copied to clipboard

Explanation: IOA Archive Server device deviceId could not open the specified file.

The request is ignored.

Corrective Action: Verify that the file exists and can be accessed.

DVT195I `mediaName` - DEVICE `deviceId` - PLEASE MOUNT REQUIRED VOLUME, OR ANSWER NOLink copied to clipboard

Explanation: This information message indicates that a request was issued to mount a tape volume on device deviceId, and the requested tape volume was not mounted. The previous tape mount message was issued after an attempt to open a file on a tape volume that was not mounted on the device.

If this WTOR is answered NO, the mount request is canceled and the user request is ignored.

Corrective Action: If the requested volume cannot be mounted, or to cancel the mount request for any reason, reply NO to this WTOR. Otherwise, mount the requested volume.

DVT196E `mediaName` - DEVICE `num` - ERROR IN READ SMN `st.maName` SSN `smName` DSN `dsn` RC: `rc`Link copied to clipboard

Explanation: The FileTek storage-machine ASREAD_RECORD function that was activated by an IOASMON monitor failed.

The variables in this message are:

mediaName - the Filetek storage machine media defined in IOASPRM
num - the number of the IOASMON device in which the error occurred
st.maName - the name of the Filetek storage machine When this does not appear in the message, the name indicates the storage machine defined in the storage machine configuration member.
smName - SM subsystem name
dsn - the name of the file in which the ASREAD_RECORD function failed
rc - the return code from the ASREAD_RECORD function

Online viewing or printing of the report from the Filetek storage machine fails.

Corrective Action: Check the return code of the ASREAD_RECORD function against the Filetek documentation, and correct the problem accordingly.

DVT197E `mediaName` - DEVICE `num` - ECBADDR FAILED SMN `st.maName` SSN `smName` DSN `dsn` RC: `rc`Link copied to clipboard

Explanation: The Filetek storage-machine ECBADDR function that was activated by an IOASMON monitor after the ASREAD_RECORD function failed.

The variables in this message are:

mediaName - the Filetek storage machine media defined in IOASPRM
num - the number of the IOASMON device in which the error occurred
st.maName - the name of the Filetek storage machineWhen it does not appear in the message, the name is that of the storage machine defined in the storage machine configuration member.
smName - the SM subsystem name
dsn - the name of the file in which the ECBADDR function failed
rc - the return code from the ECBADDR function

Online viewing or printing of the report from the Filetek storage machine fails.

Corrective Action: Check the return code of the ECBADDR function against the Filetek documentation, and correct the problem accordingly.

DVT198E `mediaName` - DEVICE `num` - CHECK FAILED SMN `st.maName` SSN `smName` DSN `dsn` RC: `rc`Link copied to clipboard

Explanation: The Filetek storage-machine CHECK function that was activated by an IOASMON monitor after the ECBADDR function failed.

The variables in this message are:

mediaName - Name of the Filetek storage machine media defined in IOASPRM.
num - Number of the IOASMON device in which the error occurred.
st.maName - Name of the Filetek storage machine. When it does not appear in the message, the name is that of the storage machine defined in the storage machine configuration member.
smName - SM subsystem name.
dsn - Name of the file in which the CHECK function failed.
rc - Return code from the CHECK function.

Online viewing or printing of the report from the Filetek storage machine fails.

Corrective Action: Check the return code of the CHECK function against the Filetek documentation, and correct the problem accordingly.

DWL messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages DWLI00 through DWLIxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

DWLI00I DOWNLOAD OF IOA DATABASE STARTEDLink copied to clipboard

Explanation: This information message is issued by the Enterprise Controlstation Download utility to indicate that downloading of the IOA and Control-M database is currently in progress.

Corrective Action: No action is required.

DWLI01I DOWNLOAD OF IOA DATABASE ENDED SUCCESSFULLYLink copied to clipboard

Explanation: Information message issued by the Enterprise Controlstation Download utility, indicating that the download of the IOA and Control-M database has ended successfully.

Corrective Action: No action is required.

DWLI02E RESOURCE `resourceName` CONTAINS NULLS, INTERNAL CODE `code`Link copied to clipboard

Explanation: A resource containing nulls in its name was encountered during download or database update. A null is not valid in the name of a quantitative or control resource.

The Control-M Application Server terminates with a condition code of 08.

Corrective Action: Report the occurrence to BMC Customer Support.

DWLI03E OPEN OF ENTERPRISE/CS INFO DOWNLOAD FILE FAILED. DDNAME "DWNINFO"Link copied to clipboard

Explanation: The Enterprise Controlstation Download utility could not open the Download Info file (the DWNINFO DD statement).

Possible causes are:

The DWNINFO DD statement is missing.
The download JCL procedure or the JCL of the download job has been modified.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Correct the download JCL procedure or the JCL for the download job and rerun the download job.

DWLI04E OPEN OF ENTERPRISE/CS JOBS DOWNLOAD FILE FAILED. DDNAME "DWNJOBS"Link copied to clipboard

Explanation: The Enterprise Controlstation Download utility could not open the Download Jobs file (the DWNJOBS DD statement).

Possible causes are:

The DWNJOBS DD statement is missing.
The download JCL procedure or the JCL of the download job has been modified.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Correct the download JCL procedure or the JCL for the download job and rerun the download job.

DWLI06E INSUFFICIENT STORAGE FOR THE ENTERPRISE/CS DOWNLOAD UTILITYLink copied to clipboard

Explanation: The Enterprise Controlstation Download utility requires more storage in order to execute.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Increase the REGION size and rerun the download job.

DWLI07E DOWNLOAD INTERNAL ERROR TYPE `type`Link copied to clipboard

Explanation: An internal error occurred during execution of the Enterprise Controlstation Download utility.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

DWLI08E OPEN OF ENTERPRISE/CS APPLICATION-GROUP DEFINITION FILE FAILED. DDNAME "DAGROUP"Link copied to clipboard

Explanation: The Control-M Application Server or Download utility is unable to open the Application-Group Definition file (the DAGROUP DD statement). This may be due to one of the following:

The DAGROUP DD statement is missing.
The Control-M Application Server JCL procedure, or the download JCL procedure or the JCL of the download job has been modified.

The Control-M Application Server or Download utility continues executing, but without processing the applications.

Corrective Action: Correct the Control-M Application Server JCL procedure and restart the Control-M Application Server, or correct the download JCL procedure or the JCL for the download job and rerun the download job.

DWLI09E MAXIMUM APPLICATIONS IN ENTERPRISE/CS APPLICATION-GROUP DEFINITION FILE EXCEEDED. DDNAME "DAGROUP"Link copied to clipboard

Explanation: The Control-M Application Server or Download utility is unable to process all the applications in the Application-Group Definition file (the DAGROUP DD statement). Too many applications were defined in the Application-Group Definition file.

The Control-M Application Server or Download utility continues executing, but processes only some of the applications.

Corrective Action: Check the Application-Group Definition file, and if it is correct, contact BMC Customer Support.

DWLI10E MAXIMUM GROUPS IN ENTERPRISE/CS APPLICATION-GROUP DEFINITION FILE EXCEEDED. DDNAME "DAGROUP"Link copied to clipboard

Explanation: The Control-M Application Server or Download utility is unable to process all the groups in the Application-Group Definition file (the DAGROUP DD statement). Too many groups were defined in the Application-Group Definition file.

The Control-M Application Server or Download utility continues executing, but processes only some of the groups.

Corrective Action: Check the Application-Group Definition file, and if it is correct, contact BMC Customer Support.

DWLI11E INVALID STATEMENT IN ENTERPRISE/CS APPLICATION-GROUP DEFINITION FILE. DDNAME "DAGROUP"Link copied to clipboard

Explanation: The Control-M Application Server or Download utility is unable to process a statement in the Application-Group Definition file (the DAGROUP DD statement). An invalid statement appeared in the Application-Group Definition file.

The Control-M Application Server or Download utility continues executing, but skips processing of the invalid instruction.

Corrective Action: Correct the syntax in the Application-Group Definition file, and restart the Control-M Application Server or rerun the Enterprise Controlstation Download utility.

DWLI14E OPEN OF ENTERPRISE/CS CONTROL RESOURCES DOWNLOAD FILE FAILED. DDNAME "DWNCNTRL"Link copied to clipboard

Explanation: The Enterprise Controlstation Download utility could not open the Download Control Resources file (the DWNCNTRL DD statement).

Possible causes are:

The DWNCNTRL DD statement is missing.
The download JCL procedure or the JCL of the download job has been modified.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Correct the download JCL procedure or the JCL for the download job and rerun the download job.

DWLI15E OPEN OF ENTERPRISE/CS QUANTITATIVE RESOURCES DOWNLOAD FILE FAILED. DDNAME "DWNQUANT"Link copied to clipboard

Explanation: The Enterprise Controlstation Download utility is unable to open the Download Quantitative Resources file (the DWNQUANT DD statement).

Possible causes are:

The DWNQUANT DD statement missing.
The download JCL procedure or the JCL of the download job has been modified.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Correct the download JCL procedure or the JCL for the download job and rerun the download job.

ECA messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages ECAA00 through ECAAxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAA00I APPLICATION SERVER(D001) MANAGER STARTED, RELEASE(`releaseId`) CREATED (`timeStamp`) CCID(`changeLevel`)Link copied to clipboard

Explanation: This information message indicates normal startup of the address space of the application server.

The variables in this message are:

releaseId - the official release and the maintenance level of the IOAGATE
timeStamp - the date and time when the main module of the application server manager was compiled
changeLevel - the level of the change that was last applied to the main module of the manager of the application server

Corrective Action: No action is required.

ECAA01I APPLICATION SERVER GOES DOWN DUE TO IOAGATE SHUTDOWNLink copied to clipboard

Explanation: This information message indicates that the manager of the application server detected that the IOAGATE is down. The shutdown may be due to an operator request or to an error.

The server address space shuts down.

Corrective Action: If the shutdown was due to a problem, check the IOAGATE messages for errors that may have caused the shutdown.

ECAA02I APPLICATION SERVER GOES DOWN DUE TO STOP REQUEST FROM CONSOLE(`consoleId`)Link copied to clipboard

Explanation: This information message indicates that the application server was shut down because a STOP command was issued to its address space.

In this message, consoleId is the identity of the console from which the STOP request was issued. The value of consoleId depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of consoleId may coincide with the user ID of the operator who issued this request, depending on your local configuration.

The address space of the application server shuts down.

Corrective Action: No action is required.

ECAA03I APPLICATION SERVER EXCLUSIVELY OWNS HEARTBEAT RESOURCE Q(`qName`)R(`rName`)Link copied to clipboard

Explanation: This information message indicates that the application server successfully acquired the specified heartbeat resource.

During initialization, an application server issues an ENQ request to acquire the indicated resource exclusively. The resource acts as a heartbeat mechanism between the IOAGATE and the address space of the server. If the resource becomes available in the address space of the IOAGATE, it indicates an application server failure.

The variables in this message are:

qName - major name of a heartbeat resource of the application server
rName - minor name of a heartbeat resource of the application server

Corrective Action: No action is required.

ECAA04S ECAAMGR INTERNAL ERROR, TASKLIST EXHAUSTEDLink copied to clipboard

Explanation: The manager of an application server encountered a severe internal error.

The address space of the server shuts down with a return code of 44.

Corrective Action: Contact BMC Customer Support.

ECAA05E APPLICATION SERVER ENDED DUE TO CRITICAL TASK TERMINATIONLink copied to clipboard

Explanation: A critical server task terminated. A server task may be defined as critical in the address space of an application server. If a critical task fails, the server address space goes down. The CD server task is always critical.

The server address space shuts down with a return code of 68.

Corrective Action: Check the error messages of the server address space for the cause of the critical task termination. If there are no other active application server address spaces, recycle the IOAGATE.

ECAA06W SERVER TASK(`type. taskId`) TERMINATEDLink copied to clipboard

Explanation: This message warns that one server task of the server address space terminated. The message may be accompanied by error messages issued by the failed server task itself.

The variables in this message are:

type - server task type:
- CM - manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal ID of a server task

If the terminated task was critical or was a single CS task, the server address space shuts down. Otherwise, normal processing continues, and, if recovery is not blocked for this server task, the IOAGATE tries to recover the server task, when message ECAB41I may be issued.

Corrective Action: If there are any error messages that relate to the server address space, check them to determine and fix the cause of the task termination. Restart the server task using the F IOAGATE,STARTTID=taskId command.

ECAA07E APPLICATION SERVER GOES DOWN DUE TO TERMINATION OF ALL CS SERVER TASKSLink copied to clipboard

Explanation: The last CS server task ended. The application server address space cannot function when there is no CS server task available.

The server address space shuts down with a return code of 12.

Corrective Action: Check the other error messages that relate to the server address space to determine the cause of the CS task termination. If there are no other active server address spaces, recycle the IOAGATE.

ECAA08E APPLICATION SERVER GOES DOWN DUE TO IOAGATE NOT RESPONDINGLink copied to clipboard

Explanation: IOAGATE does not respond to the application server address space. The IOAGATE probably experienced internal problems and could not respond to an application server.

The server address space shuts down with a return code of 64.

Corrective Action: Do the following:

Examine the error messages that relate to the IOAGATE.
Increase the system priority of both
- the IOAGATE
- an application server address space
Recycle the IOAGATE.

ECAA09E APPLICATION SERVER GOES DOWN DUE TO CHANNEL(`channelId`) DISABLINGLink copied to clipboard

Explanation: Application server manager ended. An application server address space cannot function when there is no channel available to communicate with the partner or client.

The server address space shuts down.

Corrective Action: Examine the error messages that relate to the channelId channel. Recycle the IOAGATE.

ECAA0AI CHAN PROT TASK VENDOR SUBS PORT/LU STATUS LINKS APPLLink copied to clipboard

Explanation: This information message provides header information about communication channels defined in the ECAPARM configuration file. ECAA0BI messages that follow provide details for each channel. This message is issued once, in response to an F IOAGATE,CHANNEL (or CHAN) command.

Corrective Action: No action is required.

ECAA0BI `channelId protocol task softwareVendor subsystem port / luName status links applications`Link copied to clipboard

Explanation: This information message provides detailed information about a single communication channel. It is issued for each communication channel in response to an F IOAGATE,CHANNEL (or CHAN) command.

Each occurrence of this message identifies a communication channel defined in the ECAPARM configuration file. If you have enabled a DC (dual connection) communication channel, the information is provided in two ECAA0BI messages. A set of these messages provides information about all the channels. The ECAA0AI message provides headings for the set.

The variables in this message are:

channelId - This channel ID consists of two subfields:
- the communication model specifier for the channel
- a 2-character channel ID assigned by the user in the ECAPARM configuration file. Valid communication model specifiers are: MC - a multiple connection channel, DC - a dual connection channel
protocol - The current channel uses this communication protocol. Valid values are:
- TCP -TCP/IP communication protocol
- SNA -SNA communication protocol
task - the name of a communication task. This variable is used only for an enabled DC channel. Valid values are:
- SNDR - the sender communication task of the DC channel
- RCVR - the receiver communication task of the DC channel
softwareVendor - the vendor of the TCP/IP software. Valid values are:
- IBM - IBM TCP/IP software is used by the channel
- CA - TCPaccess software of Computer Associated International, Inc. is used by the channel
subsystem - subsystem name for the TCPaccess software
port - the TCP/IP communication port number used by a TCP channel to listen for connection. In the case of an enabled DC communication channel, two consecutive port numbers are used, and these are identified in two ECAA0BI messages.
luName - VTAM LU 6.2 (APPC) application ID used by an SNA channel to communicate over the APPC network
status - the current status of the channel. Valid values are:
- DOWN - the channel is not started
- UP/OPEN - the channel is open, up and running
- UP/CLOSED - the channel has been closed for new incoming connections, but it is still up and running
- DISABLED - the channel was disabled, either in the ECAPARM configuration file by the CHANNEL parameter set to DISABLE, or by IOAGATE during initialization
links - the number of current connections for this channel
links% -the percentage of the supported number of connections currently utilized
applications - a list of application identities that refer to this channel in the ECAPARM configuration file

Corrective Action: No action is required.

ECAA0CS INVALID ECAPARM(`suffix`) OBTAINED, THERE’S NO APSERVER STATEMENT FOR APPL.SERVERLink copied to clipboard

Explanation: The application server address space obtained an improper ECAPARM configuration member. The most likely cause was an incorrect PARM library allocated by the DAPARM DD statement.

In this message, suffix is a 1-character ID that specifies a unique ECAPARM configuration file.

The server address space shuts down with a return code of 60.

Corrective Action: Check and correct the ECAPARM configuration file, the DAPARM DD allocation, or both.

ECAA0DS APPL.SERVER FAILED TO ACQUIRE HEARTBEAT RESOURCE Q(`qName`)R(`rName`)Link copied to clipboard

Explanation: An application server failed to acquire the specified heartbeat resource.

During initialization, an application server issues an ENQ request to acquire the indicated resource exclusively. The resource acts as a heartbeat mechanism between the IOAGATE and the address space of the server. An application server failure is indicated if the resource becomes available in the address space of the IOAGATE. Failure to acquire the heartbeat resource by an application server is a severe error.

The variables in this message are:

qName - the major name of a heartbeat resource of the application server
rName - the minor name of a heartbeat resource of the application server

The application server shuts down.

Corrective Action: Do the following:

Examine the other error messages that relate to the server address space to determine the cause of the failure.
Try to correct the problem.
Restart IOAGATE.
If the problem persists, call your systems programmer for assistance.

ECAA0ES UNRECOVERABLE INTERNAL ERROR ENCOUNTERED: `rsn`Link copied to clipboard

Explanation: The application server manager encountered a severe internal error when handling the MAXMSGSZ ECAAPPL parameter.

Valid values for rsn are:

no SDT address
no SDT of CS
no MAXMSGSZ

The address space of the server shuts down with a return code of 96.

Corrective Action: Contact BMC Customer Support.

ECAA0FS UNRECOVERABLE APPLICATION ERROR ENCOUNTEREDLink copied to clipboard

Explanation: A severe internal application error occurred in the application server.

The application server shuts down.

Corrective Action: Examine any other error messages that relate to the server address space to determine the cause of the failure, take appropriate corrective action, and restart IOAGATE.

ECAA0HI IOAGATE HAS GONE DOWNLink copied to clipboard

Explanation: This information message in an application server address space indicates that this application has detected IOAGATE going down.

The application server address space goes down with a return code of 112.

Corrective Action: Attempt to identify and correct the problem that caused IOAGATE to go down.

ECAA0IW SERVER TASK(`type. taskId`) CANCELLED(U007) BY `ioagateName` BECAUSE THE TASK WAS BUSY FOR TOO LONGLink copied to clipboard

Explanation: The ioagateName application server manager cancelled the taskId task of the application server with a completion code of U007.

When a server task is busy for longer than the period defined for this application server by the BUSYDUR parameter, the following events occur:

A request to cancel the task is generated automatically by IOAGATE.
Message ECAB4BW is issued.

This message (ECAA0IW) is followed by message ECAA06W.

The variables in this message are:

type - the server task type. Valid values are:
- CM - manager of the address space of the application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal ID of a server task
ioagateName - the name of the IOAGATE started task that generated the cancel request

The system action depends on the nature of the terminated task, as follows:

If the terminated task was either critical or a single CS task, the server address space shuts down. If recovery is not blocked for this application server, the IOAGATE tries to recover the server.
Otherwise, normal processing continues, and, if recovery is not blocked for this server task, the IOAGATE tries to recover the server task.

Corrective Action: Attempt to find the cause for the cancellation of the taskId server task. Try increasing the value of the BUSYDUR parameter.

ECAA0JW SERVER TASK(`type. taskId`) CANCELED(U007) FROM CONSOLE (`consoleId`)Link copied to clipboard

Explanation: This message warns that the application server manager has cancelled a server task of the application server with a completion code of U007. This is the result of a CANCTID= taskId request issued by the operator in the IOAGATE address space.

This message is followed by message ECAA06W.

The variables in this message are:

type - the server task type. Valid values are:
- CM - manager of the address space of the application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal ID of a server task
consoleId - the identity of the console from which the CANCTID request was issuedThe value of consoleId depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of consoleId may coincide with the user ID of the operator who issued this request, depending on your local configuration.

The system action depends on the nature of the terminated task, as follows:

If the terminated task was either critical or a single CS task, the server address space shuts down. If recovery is not blocked for this application server, the IOAGATE tries to recover the server.
Otherwise, normal processing continues, and, if recovery is not blocked for this server task, the IOAGATE tries to recover the server task.

Corrective Action: No action is required.

ECAA0LW APPL.SERVER TASK(`type.taskId`) ABENDED; COMPLETION CODE ({Sxxx | Uxxx})Link copied to clipboard

Explanation: This message warns that one server task of the application server address space abended.

The variables in this message are:

type - server task type:Valid values are:
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identity of a server task
compCode - completion code

If the terminated task was critical or was a single CS task, the server address space shuts down. Otherwise, normal processing continues, and, if recovery is not blocked for this server task, IOAGATE tries to recover the server task, when message ECAB41I may be issued.

Corrective Action: If there are any error messages that relate to the server address space, check them to determine and fix the cause of the task abend. Restart the server task using the MODIFY IOAGATE,STARTTID=taskId command.

ECAA0MS SSL=NO FOR CTM/ `appl1` DOESN'T MATCH SSL=YES FOR CTM/ `appl2` ON `ioagateName`/ `systemID`Link copied to clipboard

Explanation: When IOAGATE started, it discovered that SSL support is not defined the same way (whether YES, AT-TLS, or NO) in the corresponding channels for CTMAS and for CTMCAS, which are defined in different IOAGATEs.

The IOAGATE that issues this message has SSL=NO in the ECAPARM configuration file, while another IOAGATE that is already up has SSL=YES or SSL=AT-TLS in its ECAPARM configuration file.

The variables in this message are:

appl1 - either EM or CM, depending on whether this IOAGATE supports CTMAS or CTMCAS
appl2 - either EM or CM, depending on whether the other IOAGATE supports CTMAS or CTMCAS
ioagateName - the name of the other IOAGATE
systemID - the system identification of the other IOAGATE

Since the other IOAGATE has SSL=YES or SSL=AT-TLS and this IOAGATE has SSL=NO, the lower security level for this IOAGATE is not accepted. IOAGATE disables the channel and goes down if there is no other active channel.

Corrective Action: ECAPARM channel definitions should be corrected so that the channel definitions for both CTMAS and CTMCAS will have either SSL=YES, SSL=AT-TLS, or SSL=NO.

ECAA0MW SSL=YES FOR CTM/ `appl1` DOESN'T MATCH SSL=NO FOR CTM/ `appl2` ON `ioagateName`/ `systemID`Link copied to clipboard

The IOAGATE that issues this message has SSL=YES or SSL=AT-TLS in the ECAPARM configuration file, while another IOAGATE that is already up has SSL=NO in its ECAPARM configuration file.

The variables in this message are:

appl1 - either EM or CM, depending on whether this IOAGATE supports CTMAS or CTMCAS
appl2 - either EM or CM, depending on whether the other IOAGATE supports CTMAS or CTMCAS
ioagateName - the name of the other IOAGATE
systemID - the system identification of the other IOAGATE

IOAGATE continues the startup.

Corrective Action: ECAPARM channel definitions should be corrected so that the channel definitions for both CTMAS and CTMCAS will have either SSL=YES, SSL=AT-TLS, or SSL=NO.

ECAA0NS SSL=NO FOR CTM/ `appl1` DOESN'T MATCH SSL=YES FOR CTM/ `appl2`Link copied to clipboard

This was discovered when the second channel was initializing and had SSL=NO, while another channel that was already initialized had SSL=YES or SSL=AT-TLS.

The variables in this message are:

appl1 - either EM or CM, depending on whether this channel supports CTMAS or CTMCAS
appl2 - either EM or CM, depending on whether the other channel supports CTMAS or CTMCAS

IOAGATE disables the channel that has SSL=NO and goes down if there is no other active channel.

Corrective Action: ECAPARM channel definitions should be corrected so that the channel definitions for both CTMAS and CTMCAS will have either SSL=YES, SSL=AT-TLS, or SSL=NO.

ECAA0NW SSL=YES FOR CTM/ `appl1` DOESN'T MATCH SSL=NO FOR CTM/ `appl2`Link copied to clipboard

This was discovered when the second channel was initializing and had SSL=YES or SSL=AT-TLS, while another channel that was already initialized had SSL=NO.

The variables in this message are:

appl1 - either EM or CM, depending on whether this channel supports CTMAS or CTMCAS
appl2 - either EM or CM, depending on whether the other channel supports CTMAS or CTMCAS

IOAGATE continues the initialization of the channel with SSL=YES or SSL=AT-TLS.

Corrective Action: ECAPARM channel definitions should be corrected so that the channel definitions for both CTMAS and CTMCAS will have either SSL=YES, SSL=AT-TLS, or SSL=NO.

ECAA0OS IOAGATE `name` IS ALREADY ACTIVE FOR THE SAME ENVIRONMENT ON `lpar`Link copied to clipboard

Explanation: An attempt to start IOAGATE failed because another IOAGATE for the same Control-M environment is already active on another LPAR.

Corrective Action: If the IOAGATE is required to run on this LPAR, first stop IOAGATE name on LAPR lpar.

ECAA0PE CHANNEL(channelId.TCP) TASK(taskId.type) CONNECTION REJECTED. SSL=AT-TLS SPECIFIED, BUT IS NOT ACTIVE ON CONNECTION

Explanation: This message indicates that SSL=AT-TLS was specified in ECAPARMx for this channel, indicating that a secure connection is required to be handled by AT-TLS, but AT-TLS is not active on the connection. The connection is terminated.

The variables in this message are:

channelId - identity of the TCP channel that is listening to the specified port
taskId - internal identity of this communication task
type - internal type of this communication task

Corrective Action: Configure a suitable TTLSRule statement in the system's AT-TLS Policy Agent Configuration file, and refresh the Policy Agent (PAGENT) address space.

ECAA0QW CHANNEL(`channelId`.TCP) TASK(`taskId`.`type`) SSL=NO SPECIFIED, BUT AT-TLS IS ACTIVE ON THIS CONNECTION Link copied to clipboard

Explanation: This warning message indicates that SSL=NO was specified in ECAPARMx for this channel, indicating that a secure connection is not required, but AT-TLS is active on the connection.

The variables in this message are:

channelId - identity of the TCP channel that is listening to the specified port
taskId - internal identity of this communication task
type - internal type of this communication task

Corrective Action: To eliminate this message, specify SSL=AT-TLS in ECAPARMx.

ECAA0RE CHANNEL(`channelId`.TCP) TASK(`taskId.type`) CONNECTION CLOSED - POSSIBLY BY AT-TLS. SEE TRACE/TCPIP FOR DETAILSLink copied to clipboard

Explanation: A TCP connection was established, and then was immediately closed by a component other than IOAGATE. This may occur when AT-TLS is configured for the connection, but the handshake fails or non-encrypted data is sent. In this case, additional information may be available in the TCPIP started task, or in the IOAGATE trace output if trace level=200 is active.

The variables in this message are:

channelId - identity of the TCP channel that is listening to the specified port
taskId - internal identity of this communication task
type - internal type of this communication task

Corrective Action: Examine the relevant TCPIP started task and/or IOAGATE traces, and remediate the issue, as required. For example, set the client to use SSL, or ensure that certificates match.

ECAA0SI CHANNEL(`channelId`.TCP) TASK(`taskId`.`type`) AT-TLS IS ACTIVE ON THIS CONNECTIONLink copied to clipboard

Explanation: This information message indicates that AT-TLS is active on the connection that was just established with an Enterprise Manager or Control-M Configuration Manager client. This message follows message ECAT02I.

The variables in this message are:

channelId - identity of the TCP channel that is listening to the specified port
taskId - internal identity of this communication task
type - internal type of this communication task

Corrective Action: No action is required.

ECAA0TE CHANNEL(`channelId`.TCP) TASK(`taskId`.`type`) CONNECTION REJECTED. SSL=YES SPECIFIED AND AT-TLS IS ACTIVE ON CONNECTIONLink copied to clipboard

Explanation: This message indicates that SSL=YES was specified in ECAPARMx, indicating that IOAGATE is to handle the secure connection using native SSL support, but AT-TLS is also active on the connection. In this case, double encryption would occur and IOAGATE would not be able to successfully communicate with the client. The connection is terminated.

The variables in this message are:

channelId - identity of the TCP channel that is listening to the specified port
taskId - internal identity of this communication task
type - internal type of this communication task

Corrective Action: If the secure connection should be handled by AT-TLS, specify SSL=AT-TLS in ECAPARMx. Otherwise, disable the AT-TLS rule and refresh PAGENT.

ECAA0UI CHANNEL(`channelId`.TCP) TASK(`taskId`.`type`) AT-TLS IS ACTIVE ON THIS CONNECTIONLink copied to clipboard

Explanation: This information message indicates that AT-TLS is active on the connection that was just established with a WebAccess client. This message follows message ECAG62I.

The variables in this message are:

channelId - identity of the TCP channel that is listening to the specified port
taskId - internal identity of this communication task
type - internal type of this communication task

Corrective Action: No action is required.

ECAA10S IOAGATE MIGHT BE DOWN, HEARTBEAT RESOURCE Q(`qName`)R(`rName`) AVAILABLELink copied to clipboard

Explanation: An application server determined that the specified IOAGATE heartbeat resource is available.

During initialization, an application server checks the IOAGATE heartbeat resource availability to see if the IOAGATE is up and running. If the resource is available, then the IOAGATE is down. For more information, see the ECAG38I message.

The variables in this message are:

qName - the major name of a heartbeat resource of the IOAGATE
rName - the minor name of a heartbeat resource of the IOAGATE

The application server address space shuts down with a return code of 16.

Corrective Action: Check the IOAGATE logs to determine why IOAGATE is down, try to fix the problem and restart IOAGATE.

ECAA11S ECAAMGR INTERNAL ERROR, `func` CALL FAILED WITH RC(`rsn`)Link copied to clipboard

Explanation: The application server manager encountered a severe internal error when trying to call the func function.

Possible func and rsn (reason code) combinations, and their explanations, are shown in the following table:

call	rsn	Explanation
MBXATTC1	20	ATTACH for the first mailbox failed.
MBXATTC2	24	ATTACH for the second mailbox failed.
MBXREAD	28	A mailbox READ failed.
MBXWRIT1	32	WRITE of the first Ready message after ATTACH failed.
MBXWRIT2	36	WRITE of the Task Terminated message failed.
MBXWRIT3	40	WRITE of the Communication Update or Service Done internal management message failed.

The application server address space shuts down.

Corrective Action: Contact BMC Customer Support.

ECAA12I INITIALIZATION PROCEDURE(`mod`) COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the application server invoked the mod initialization module, and that the module completed successfully. During initialization, an application server invokes an initialization module if it is specified in the ECAPARM configuration file for that server.

Corrective Action: No action is required.

ECAA13E INITIALIZATION PROCEDURE(`mod`) FAILED WITH RC(`rsn`)Link copied to clipboard

Explanation: The application server invoked the mod initialization module, and the module failed. During initialization, an application server invokes an initialization module if it is specified in the ECAPARM configuration file for the application server.

The variables in this message are:

mod - the module that failed
rsn - the reason code indicating the failure level. Failure levels of 08 and above are fatal, and bring the application server down

The application server address space shuts down with a return code of 56.

Corrective Action: Do the following.

Examine the log of the application server for other error messages.
Correct any problems.
Restart IOAGATE.
If the problem persists, report the module name and reason code to BMC Customer Support.

ECAA14I MODIFY HANDLER (`modName`) WAS LOADEDLink copied to clipboard

Explanation: This information message indicates that the application server successfully loaded the modName module. The loaded module is a handler that performs MODIFY commands dedicated for the application server. The application server loads this module during initialization.

Corrective Action: No action is required.

ECAA15I PINGING(`pingId`) NODE(`node`)Link copied to clipboard

Explanation: Message indicates that the F CTOAS,PING MODIFY command was issued in the Control-O application server address space and a PING message was sent to the partner Control-O application server.

The variables in this message are:

pingId - the internal identity of this ping message
node - the node identity of the partner application server

Corrective Action: No action is required.

ECAA16I PING(`pingId`) REQUEST RECEIVED FROM(`node`) SERVER(`serverId`)Link copied to clipboard

Explanation: This information message indicates that the F CTOAS,PING MODIFY command was issued in the Control-O application server of the partner and a PING request message has arrived at the local Control-O application server.

The variables in this message are:

pingId - the internal identity of this PING message
node - the node identity of the partner application server
serverId - The started task identity of the partner Control-O application server

Corrective Action: No action is required.

ECAA17I PING(`pingId`) RESPONSE FROM(`node`) ARRIVED IN `nnn` MILLISECONDsLink copied to clipboard

Explanation: This information message indicates that the F CTOAS,PING MODIFY command was issued in the Control-O Application server and the response ping message has arrived from the pinging partner Control-O application server.

The variables in this message are:

pingId - the internal identity of this ping message
node - the node identity of the partner Control-O application server
nnn - the time interval in milliseconds required for a ping message to travel in both directions

Corrective Action: No action is required.

ECAA18W PING DROPPED, NODE (`node`) `rsn`Link copied to clipboard

Explanation: This information message indicates that the F CTOAS,PING MODIFY command was issued in the Control-O Application server, but the command was not performed for the reason rsn.

Valid values for rsn are:

NOT FOUND IN PDT - severe internal error
NOT FOUND IN PLT - severe internal error
MBX WRITE DISABLED - mailbox error encountered
COMMUNICATION ERROR - an IOAGATE-to-IOAGATE connection was not established

Corrective Action: No action is required.

ECAA19I `ctrl_msg` received for Server(`servr_id`).Link copied to clipboard

Explanation: The application server servr_id received the internal control message ctrl_msg from IOAGATE.

Valid values for ctrl_msg are:

INITIALIZE - internal control command to initialize an application server
ATTACHSERVER - internal control command to start an application server task
CONNECTIONUP - internal control command to inform an application server task that the communication channel is up and running

Corrective Action: No action is required.

Messages ECAB00 through ECABxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAB01I CHANNEL(`channelId`) ECAPARM PORT SUCCESSFULLY OVERRIDDEN BY THE EXEC PARM VALUELink copied to clipboard

Explanation: This information message indicates that the PORT value specified in the EXEC PARM parameters successfully replaced the ECAPARM PORT value of the indicated channel.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. If a TCP/IP port number was specified in EXEC PARM, then IOAGATE replaces the PORT value specified in the ECAPARM configuration file for the indicated channel with the value from EXEC PARM. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

In this message, channelId identifies the channel with the PORT value that was replaced.

Corrective Action: No action is required.

ECAB02I CHANNEL(`channelId`) ECAPARM APPLIDS SUCCESSFULLY OVERRIDDEN BY THE EXEC PARM VALUELink copied to clipboard

Explanation: This information message indicates that the APPLIDS values specified in the EXEC PARM parameters successfully replaced the ECAPARM APPLIDS values of the specified channel.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. If VTAM LU 6.2 (APPC) APPLIDS was specified in EXEC PARM, IOAGATE tries to replace the APPLIDS values specified in the ECAPARM configuration file for the indicated channel with values from EXEC PARM. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

In this message, channelId identifies the channel with the APPLIDS values that were replaced.

Corrective Action: No action is required.

ECAB03W PORT AND APPLID CANNOT BE SPECIFIED FOR THE SAME CHANNEL SIMULTANEOUSLYLink copied to clipboard

Explanation: A PORT value and an APPLID value were specified in the EXEC PARM parameters simultaneously.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. A TCP/IP port number and a VTAM LU 6.2 (APPC) APPLID were specified in the EXEC PARM parameters simultaneously. These values cannot be specified together.

Both the PORT and APPLID values are ignored. Normal processing continues.

Corrective Action: Correct the indicated parameters and restart IOAGATE.

ECAB04I CHANNEL(`channelId`) ECAPARM APPLID SUCCESSFULLY OVERRIDDEN BY THE EXEC PARM VALUELink copied to clipboard

Explanation: This information message indicates that the APPLID value specified in the EXEC PARM parameters successfully replaced the ECAPARM APPLID value of the specified channel.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. If VTAM LU 6.2 (APPC) APPLID was specified in EXEC PARM, IOAGATE tries to replace the APPLID value specified in the ECAPARM configuration file for the indicated channel, with the value from EXEC PARM. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

In this message, channelId identifies the channel for which the APPLID value was replaced.

Corrective Action: No action is required.

ECAB05W PORT(`port`) SPECIFIED BY THE EXEC PARM WAS NOT APPLIEDLink copied to clipboard

Explanation: The PORT value in the EXEC PARM parameters was not used, and the ECAPARM PORT value is still valid.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. When a TCP/IP port number is specified in EXEC PARM, the IOAGATE tries to replace the PORT value specified in the ECAPARM configuration file for the intended channel with the value from EXEC PARM.

The current attempt failed and the ECAPARM PORT value is still valid. The channel for which the specified PORT value was intended may have been disabled during initialization.

In this message, port is the TCP/IP communication port value specified in EXEC PARM.

Corrective Action: Do the following:

Look for more information in
- IOAGATE JES log
- the DAIGLOG log
- the DATRACE log
Try to correct the problem.
If you cannot correct the problem, contact BMC Customer Support.

ECAB06W APPLIDS(`applId1, applId2`) SPECIFIED BY THE EXEC PARM WERE NOT APPLIEDLink copied to clipboard

Explanation: The APPLIDS values specified in the EXEC PARM parameters were not used, and the ECAPARM APPLIDS values are still valid.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup. When VTAM APPLIDS application IDs are specified in EXEC PARM, the IOAGATE tries to replace the APPLIDS values specified in the ECAPARM configuration file for the intended channel with the values from EXEC PARM.

The current attempt failed and the ECAPARM APPLIDS values are still valid. The channel for which the specified APPLIDS values were intended may have been disabled during the initialization.

In this message, applId1 and applId2 are VTAM LU 6.2 (APPC) application IDs specified by the APPLIDS parameter in EXEC PARM for a dual connection (DC) SNA channel.

Corrective Action: Do the following:

Look for more information in
- the IOAGATE JES log
- the DAIGLOG log
- the DATRACE log
Try to correct the problem.
If you cannot correct the problem, contact BMC Customer Support.

ECAB08E PORT SPECIFIED BY THE EXEC PARM FOR SNA CHANNEL(`channelId`) CANNOT BE USEDLink copied to clipboard

Explanation: A PORT value that was specified in the EXEC PARM parameters was not applied.

During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup, and tries to modify the channel that is explicitly specified in the EXEC PARM parameters. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

The TCP/IP port number was specified in the EXEC PARM parameters. However, IOAGATE could not apply the PORT value.

In this message, channelId is the identity of the SNA channel.

Possible causes are:

A specific CHAN parameter was specified in EXEC PARM parameters, but this is an SNA channel.
IOAGATE tried to apply the PORT value to the first ECAPARM channel, but this channel is an SNA channel.

The PORT parameter in EXEC PARM is ignored. Normal processing continues.

Corrective Action: Correct the EXEC PARM parameters and restart IOAGATE.

ECAB09E `applIdParm` SPECIFIED BY THE EXEC PARM FOR CHANNEL(`channelId`.TCP) CANNOT BE USEDLink copied to clipboard

Explanation: The APPLID or APPLIDS values set in the EXEC PARM parameters cannot be used. During initialization, IOAGATE checks for any EXEC PARM parameters specified at startup, and tries to modify the channel that is explicitly specified in the EXEC PARM parameters. If the channel is not specified, IOAGATE modifies the first channel in the ECAPARM configuration file.

APPLID or APPLIDS values were specified in the EXEC PARM parameters. However, IOAGATE could not apply the specified values.

Possible causes are:

An explicit CHAN parameter was specified in the EXEC PARM parameters, but this is a TCP channel.
IOAGATE tried to apply the specified value to the first ECAPARM channel, but this channel is a TCP channel.

The variables in this message are:

applIdParm - the APPLID or APPLIDS parameter specified by the user in the EXEC PARM parameters
channelId - the identity of the TCP channel

The APPLID or APPLIDS EXEC PARM parameter is ignored. Normal processing continues.

Corrective Action: Correct the EXEC PARM parameter applIdParm and restart IOAGATE.

ECAB0AE IMPROPER CHANNEL(`channel. chEntryId`) SPECIFIED TO SUPPORT MAP(`mapId`), APSERVER(`applName. apEntryId`) DISABLEDLink copied to clipboard

Explanation: IOAGATE detected an invalid channel reference from an APSERVER definition in the ECAPARM configuration file.

During initialization, IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. The specified channel cannot serve IOAGATE-to-IOAGATE communication over a multiple connection (MC) channel with the network map specified.

The variables in this message are:

channel - the channel identity assigned by the user in the ECAPARM configuration file
chEntryId - the sequential number of the channel definition entry in the ECAPARM configuration file
mapId - the name of a member in the IOA PARM library that describes a map of network connections between IOAGATEs allowing one IOAGATE to communicate with another over a multiple connection (MC) channel
applName - the full name of the application declared by an APSERVER definition
apEntryId - the sequential number of an APSERVER definition entry in the ECAPARM configuration file

The specified APSERVER definition is disabled. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAB0BE CHANNEL(`channel. chEntryId`) MAP MUST BE SPECIFIED, APSERVER(`applName`. `apEntryId`) DISABLEDLink copied to clipboard

Explanation: IOAGATE detected an improper channel specification for the application.

During initialization, IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. It detected that the specified channel does not have a network map specification that is required for the indicated application server.

The variables in this message are:

channel - the channel identity assigned by the user in an APSERVER definition
chEntryId - the sequential number of the channel definition entry in the ECAPARM configuration file
applName - the full name of the application declared by an APSERVER definition
apEntryId - the sequential number of an APSERVER definition entry in the ECAPARM configuration file

The specified APSERVER definition is disabled. Processing continues.

Corrective Action: Correct the APSERVER and CHANNEL definitions and restart IOAGATE.

ECAB0DI `processor` PROCESSOR CREATED(`timeStamp`) CCID(`changeLevel`)Link copied to clipboard

Explanation: This information message indicates the program level of the specified processor of IOAGATE.

The variables in this message are:

processor - the name of the parameter member. Valid values are:
- ECAAPPL
- ECAPARM
- NWORKMAP
timeStamp - the date and time when the specified processor was compiled
changeLevel - the level of the change that was last applied to the specified processor

Corrective Action: No action is required.

ECAB10W EXEC PARM PARAMETER CHAN= MUST BE 2 CHARACTERS EXACTLY, PARAMETER IGNOREDLink copied to clipboard

Explanation: The value of the CHAN parameter that was specified at startup of the IOAGATE is invalid.

The channel ID specified by the CHAN parameter must have two characters exactly.

Corrective Action: Correct the value of the CHAN parameter and restart IOAGATE.

ECAB11S INSUFFICIENT MEMORY(`area_size`) GETMAIN FOR (`area_id`) FAILEDLink copied to clipboard

Explanation: The GETMAIN request issued by IOAGATE or the application server address space failed.

IOAGATE issued a GETMAIN request during initialization to obtain main storage for the specified area. However the call failed because there was not enough main storage.

The variables in this message are:

area_size - the size of the area GETMAIN requested
area_id - the internal identity of the area for which main storage resources were requested.

The IOAGATE or application server address space shuts down with a return code of 56 or 08, respectively.

Corrective Action: Increase the region size and restart the IOAGATE. If you cannot resolve the problem, contact BMC Customer Support.

ECAB17W EXEC PARM PARAMETER PORT= MUST BE A NUMERIC VALUE IN THE RANGE FROM 1024 TO 65534Link copied to clipboard

Explanation: The value set for the PORT parameter in the EXEC PARM parameters is invalid.

The PORT parameter value must be in the range from 1024 through 65534.

The PORT parameter value specified in the ECAPARM configuration file remains valid.

Corrective Action: Specify a valid value for the PORT parameter in the EXEC PARM parameters, and restart IOAGATE.

ECAB18W EXEC PARM PARAMETER APPLID= MUST BE UP TO 8 ALPHANUMERIC CHARACTERSLink copied to clipboard

Explanation: The APPLID parameter value specified in the EXEC PARM parameters is invalid.

The APPLID parameter must comply with VTAM naming conventions.

The value of the APPLID parameter specified in the ECAPARM configuration file is still valid.

Corrective Action: Specify a valid value for the APPLID parameter in the EXEC PARM parameters and restart IOAGATE.

ECAB22I EXEC PARM PARAMETERS: `parms`Link copied to clipboard

Explanation: This information message displays the EXEC PARM parameters that were specified in the PARM field of the EXEC JCL statement.

Corrective Action: No action is required.

ECAB27I START FOR SERVER TASK(`type. taskId. addrSpaceId`) INITIATEDLink copied to clipboard

Explanation: This information message indicates that the operator issued the F IOAGATE,STARTTID=taskId command. IOAGATE submitted a STARTTID command for the specified task.

The variables in this message are:

type - the CS (application server) task type
taskId - the internal identity of a server task
addrSpaceId - the internal identity of the application server address space to which this task belongs

Corrective Action: No action is required.

ECAB30E AN ATTEMPT TO LAUNCH SERVER TASK(`taskId`) FAILEDLink copied to clipboard

Explanation: An attempt to launch an application server task failed.

During initialization or automatic recovery, IOAGATE launches the server tasks for all application servers defined in the ECAPARM configuration file. However, an attempt to launch a server task failed.

In this message, taskId identifies the server task that failed.

Corrective Action: Examine the IOAGATE JES log, DAIGLOG, DATRACE logs for more information about the problem. Try to find the cause and correct the problem.

ECAB32S ECAGTW INTERNAL ERROR, ADDRESS/VALUE(`value_id`) LOSTLink copied to clipboard

Explanation: IOAGATE encountered a severe internal error.

IOAGATE may shut down or continue, depending on the severity of the error.

Corrective Action: Contact BMC Customer Support.

ECAB36E SERVER TASK(`type`. `taskId`. `addrSpaceId`) CANNOT BE STOPPED BY OPERATORLink copied to clipboard

Explanation: IOAGATE rejected an F IOAGATE,STOPTID=taskId command, because an operator is not allowed to stop this task. A STOPTID command was issued for a CM, CD or CU server task. The specified server task can be stopped only if an entire application server address space is stopped.

The variables in this message are:

type - the server task type Possible values are:
- CM - the manager of the address space of an application server
- CD - a detector server
- CU - an updater server
taskId - the internal identity of a server task
addrSpaceId - the internal identity of the application server address space to which this task is assigned

The modify command is rejected.

Corrective Action: Use the F IOAGATE,STATUS command to specify the task ID, and reissue the command.

ECAB38I AUTOMATIC RECOVERY (`recoveryId`) FOR APPL.SERVER (`applServerName`. `addrSpaceId`) INITIATEDLink copied to clipboard

Explanation: This information message indicates that an application server address space abended, and IOAGATE initiated an automatic recovery. IOAGATE initiates an automatic recovery for an abended server address space if a nonzero value is specified for the MAXRECOV parameter in the APSERVER definition for this application server.

The variables in this message are:

recoveryId - the internal sequence number of this recovery incident
applServerName - the full name of the application server
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAB39W APPL.SERVER (`applServerName`. `addrSpaceId`) CANNOT BE RECOVERED, THRESHOLD(`threshold`) REACHEDLink copied to clipboard

Explanation: An application server address space abended, and IOAGATE cannot initiate the automatic recovery for the server. IOAGATE does not initiate an automatic recovery for the abended application server, because the maximum number of subsequent recovery retries was already performed. This threshold is specified by the MAXRECOV parameter in the APSERVER definition in the ECAPARM configuration file for this application server.

Recovery retries are subsequent if the interval between retries is shorter than the time specified by the RECVRSET parameter in the ECAPARM configuration file.

The variables in this message are:

applServerName - the name of the application server
addrSpaceId - the internal identity of the application server address space
threshold - the maximum number of subsequent recovery retries

Corrective Action: Examine the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more messages about the problem. Try to determine why the application server failed and correct the problem. If you cannot correct the problem, call your system programmer for assistance.

ECAB40W SERVER TASK (`type.taskId.addrSpaceId`) CANNOT BE RECOVERED, THRESHOLD(`threshold`) REACHEDLink copied to clipboard

Explanation: A server task abended, and IOAGATE cannot initiate an automatic recovery for this server task.

IOAGATE does not initiate an automatic recovery for the abended application server task, because the maximum number of subsequent recovery retries was already performed. The MAXRECOV parameter in the APSERVER definition in the ECAPARM configuration file for this application server specifies the maximum number of subsequent retries allowed.

Recovery retries are subsequent if the interval between retries is shorter than the time specified by the RECVRSET parameter in the ECAPARM configuration file.

The variables in this message are:

type - the CS (application server) task type
taskId - the internal identity of a server task
addrSpaceId - the internal identity of the application server address space to which this task belongs
threshold - the maximum number of subsequent recovery retries

Corrective Action: Call your system programmer for assistance.

ECAB41I AUTOMATIC RECOVERY (`recoveryId`) FOR SERVER TASK(`type.taskId.addrSpaceId`) INITIATEDLink copied to clipboard

Explanation: This information message indicates that an application server task abended, and IOAGATE initiated an automatic recovery.

IOAGATE initiates an automatic recovery for the abended application server task, if a nonzero value was specified for the MAXRECOV parameter in the APSERVER definition for this application server.

The variables in this message are:

recoveryId - the internal sequence number of this recovery incident
type - the CS application server task type
taskId - the internal identity of the server task
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAB42I * `text date` *Link copied to clipboard

Explanation: This information message displays the current local date at the system on which the IOAGATE is running. It is first issued when IOAGATE initialization is completed. It is issued again, at the beginning of each day.

The variables in this message are:

text - Valid values are:
- LOCAL CURRENT DATE (after initialization)
- NEW DAY STARTED (beginning of new day)
date - the local current date. The date format is defined in the IOAPARM member. The format can be redefined for IOAGATE by the DATETYPE parameter in the ECAPARM configuration file. Valid formats are:
- MMDDYYYY
- DDMMYYYY (default)
- YYYYDDD
- YYYYMMDD

Corrective Action: No action is required.

ECAB43W SERVER TASK(`type.taskId.addrSpaceId`) BUSY `duration units`, WARNING `interval(repeater)` SECs USER(`userId`) SIID(`serviceInstanceId`)Link copied to clipboard

Explanation: The status of the application server task stayed BUSY with the same SIID service for longer than the warning interval allowed by the ECAPARM configuration file. This message indicates a possible internal problem in IOAGATE.

The variables in this message are:

type - the server task type Valid values are:
- CM - the manager of the address space of an application server
- CS - an application server
- CD - a detector server
- CU - an updater server
taskId - the internal identity of the problematic server task If this server task is busy handling a request for an alias application, taskId is the short application code of the alias.
addrSpaceId - the internal identity of the server address space to which this task is assigned
duration - the number of time units during which the server task handles the same service for the same user
units - the type of time unit in which the actual duration is expressed Valid values are:
- secs - The duration is expressed in seconds
- mins - The duration is expressed in minutes

If the actual duration is less than 5 minutes, duration is expressed in seconds. If the actual duration is 5 minutes or more, duration is expressed in minutes.

interval - the number of units to wait before issuing this message The first time this message is issued, interval is defined by the SERVDUR parameter in the ECAPARM configuration file.

The value of interval for the second warning, and all subsequent warnings, is defined by the SERVDUR and NWARNING parameters that can be set in the ECAPARM configuration file. If both parameters are set, then interval is the value of SERVDUR multiplied by the value of NWARNING.

Setting SERVDUR to 0 in the ECAPARM configuration file for this server disables the message completely for this server. Setting NWARNING to 0 disables the second and all subsequent warnings. The default for SERVDUR is 60 seconds; the default for NWARNING is 10.

repeater - the number of interval periods before a second or subsequent warning is issued The value of repeater can be specified in the NWARNING parameter in the ECAPARM configuration file. Valid values are 0 through 99. The default is 0, meaning that this message (ECAB43W) is issued only once.
userId - the identity of the user whose request is in process
serviceInstanceId - the service instance identity (SIID) that determines the which service request is handled by the server task

Corrective Action: Examine the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to determine the cause and correct the problem. Consider reassigning the SERVDUR and NWARNING parameters. If the problem persists, contact BMC Customer Support.

ECAB44W APPL.SERVER(`addrSpaceId`) DOES NOT EXISTLink copied to clipboard

Explanation: An attempt to stop a specified application server using an F IOAGATE,STOPASID=addrSpaceId command failed, because the specified application server address space identity is incorrect. The application server address space identity addrSpaceId must be the correct internal identity of an application server address space.

The modify command is rejected. Normal processing continues.

Corrective Action: Use the F IOAGATE,STATUS command to identify the correct application server address space identity, and then reissue the command correctly.

ECAB47I SERVER TASK(`applServerName .type.taskId.addrSpaceId`) RECOVERED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that an application server task recovered successfully.

The variables in this message are:

applServerName - the name of the application server
type - the CS server task type
taskId - the internal identity of the server task
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAB48I APPL.SERVER (`applServerName.addrSpaceId.stcId`) RECOVERED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the specified application server recovered successfully.

The variables in this message are:

applServerName - the name of the application server
addrSpaceId - the internal identity of the application server address space
stcId - the name of the JCL procedure used to start the application server address space

Corrective Action: No action is required.

ECAB49I SERVER TASK(`applServerName.type.taskId.addrSpaceId`) STARTED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that IOAGATE launched the specified application server task, and it started successfully.

The variables in this message are:

applServerName - the full name of the application server
type - the server task type Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - a detector server
- CU - updater server
taskId - the internal identity of the server task
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAB4AW CHANNEL(`channelId.protocol`) TASK(`taskId`) TIMEOUT OCCURRED WHILE AWAITING REPLY FROM USER(`userId`) SIID(`serviceInstanceId`) SID(`serviceId`)Link copied to clipboard

Explanation: This warning message indicates that a time-out occurred while awaiting reply from a partner or client because the partner or client did not respond to the message sent by IOAGATE during the time-out interval.

The variables in this message are:

channelId - the identity of the channel that detected the event
protocol - the communication protocol used by the channel Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the communication task that detected the event Valid values are:
- COMTASK
- RECEIVER
userId - the identity of the user whose request was in process
serviceInstanceId - the service instance identity (SIID) that indicates the service request being handled by IOAGATE
serviceId - the code of a transaction to be performed by IOAGATE

The connection is assumed to be broken and the service is discarded.

Corrective Action: Check status of the partner or client and its communication link to IOAGATE.

ECAB4BW SERVER TASK(`type.taskId.addrSpaceId`) WILL BE CANCELLED DUE TO BEING BUSY FOR `duration` MINs, USER(`userId`) SIID(`serviceInstanceId`)Link copied to clipboard

Explanation: The application server task is going to be terminated, because it has been in BUSY status with the same SIID service for more than the maximum time allowed by the BUSYDUR parameter in the ECAPARM configuration file. This may indicate a potential internal problem in IOAGATE or in the application server address space.

The variables in this message are:

type - the server task type Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identifier of the problematic server task
addrSpaceId - the internal identifier of a server address space of this task
duration - the time a server task handles the same service for the same user
userId - the identifier of a user whose request is in process.
serviceInstanceId - the service instance identifier (SIID) that determines the service request being handled by the server task

The specified application server task is terminated. If it is a critical task, then the whole application server address space is terminated due to this server task failure.

Corrective Action: Do the following:

If the problem persists, examine the IOAGATE JES log, DAIGLOG log, and DATRACE log for additional information about the potential problem.
Try to find the cause and correct the problem.
Consider re-assigning a BUSYDUR parameter.
If the problem is not resolved, contact BMC Customer Support.

ECAB50I APPL.SERVER(`applServerName.addrSpaceId.proc.stcId.channelId/jobId`) STARTED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the specified application server started successfully.

The variables in this message are:

applServerName - the name of the application server
addrSpaceId - the internal identity of the application server address space
proc - the name of the procedure of the application server address space
stcId - the name of the JCL procedure used to start the application server address space
channelId - the channel identity referenced from the APSERVER definition that creates this application server
jobId - the STC JOBID of the application server assigned by JES to its address space

Corrective Action: No action is required.

ECAB51W APPL.SERVER(`applServerName.addrSpaceId.stcId.channelId`) HAS NOT BECOME AVAILABLE IN THE LAST `interval` SECONDSLink copied to clipboard

Explanation: The application server has not started in the specified time interval, either since IOAGATE launched the application server, or since the last occurrence of the same warning. There might be a problem that prevents the application server from starting in time.

The variables in this message are:

applServerName - the name of the application server
addrSpaceId - the internal identity of the application server address space
stcId - the name of the JCL procedure used to start the application server
channelId - the channel identity referenced from the APSERVER definition that creates this application server
interval - the number of seconds to wait before issuing this warning messageThe default is 180 seconds.

Corrective Action: Check the application server log, the IOAGATE log, the JES log, the DAIGLOG log, and the DATRACE log for more information. If you cannot correct the problem, contact BMC Customer Support.

ECAB52W TIMER WAS NOT SET FOR THE SERVER TASK (`type.taskId.addrSpaceId`)Link copied to clipboard

Explanation: An internal timer did not start for the specified server task due to an internal problem.

The variables in this message are:

type - the server task type Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space

Corrective Action: If the problem persists, contact BMC Customer Support.

ECAB54W SERVER TASK (`type.taskId.addrSpaceId`) IS IN STATUS(`status_id`) FOR MORE THAN `interval` SECONDSLink copied to clipboard

Explanation: IOAGATE detected that the specified server task has had the same temporary status for longer than the maximum time interval defined in the ECAPARM configuration file.

This condition might indicate an internal problem in IOAGATE.

The variables in this message are:

type - the server task type Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identity of the problematic server task
addrSpaceId - the internal identity of the application server address space to which the indicated task belongs
status_id - the internal identity of the status in which the server task staysValid values are:
- WAIT
- PENDING
interval - the number of seconds to wait before issuing this warning messageThis value can be assigned by the STATDUR parameter in the ECAPARM configuration file. The default is 60 seconds.

Normal processing continues. However, the further consequences of the event are unpredictable.

Corrective Action: If the problem persists, call BMC Customer Support.

ECAB55W SERVER TASK (`type.taskId.addrSpaceId`) HAS NOT BECOME AVAILABLE IN THE LAST `interval` SECONDSLink copied to clipboard

Explanation: The server task did not start within the indicated time interval.

There might be a problem that prevents a server task from being started in time.

The variables in this message are:

type - the server task type Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identity of the server task
addrSpaceId - the internal identity of the application server address space to which the indicated server task belongs
interval - the time interval in seconds to wait before issuing this warning

Corrective Action: Check the application server log, the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. If you cannot correct the problem, contact BMC Customer Support.

ECAB56W SERVER TASK (`type.taskId.addrSpaceId`) FAILED TO RECOVER IN THE LAST `interval` SECONDSLink copied to clipboard

Explanation: The specified server task did not recover successfully during the specified time interval. There might be a problem that prevented the application server task from recovering in time.

The variables in this message are:

type - the CS server task type
taskId - the internal identity of the server task
addrSpaceId - the internal identity of the server address space
interval - The actual time in seconds during which the server task did not recover

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to fix the problem. Consider reassigning a SERVDUR parameter. For more assistance, contact BMC Customer Support.

ECAB57W APPL.SERVER (`applServerName.addrSpaceId.stcId.channelId`) FAILED TO RECOVER IN THE LAST `time` SECONDSLink copied to clipboard

Explanation: The specified application server did not recover successfully within the specified time interval. There might be a problem that prevented the application server from recovering in time.

The variables in this message are:

applServerName - the name of the application server
addrSpaceId - the internal identity of the server address space
stcId - the JCL procedure used to start the application server address space
channelId - the channel used by this application server
time - the actual time in seconds during which the application server did not recover

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to correct the problem. Consider reassigning a SERVDUR parameter. For more assistance, contact BMC Customer Support.

ECAB60I STATISTICS COLLECTION STARTED. INTERVAL IS `interval` MINUTESLink copied to clipboard

Explanation: This information message indicates that statistics collection for IOAGATE communication started. It is issued during IOAGATE startup when STAT is set to YES in the ECAPARM configuration file, and when the command F IOAGATE,STATON,INTERVAL= interval is issued.

Up to six columns of statistics are collected and saved. After that, existing columns are overwritten. For example, the seventh column of statistics replaces the first.

In this message, interval is the number of minutes during which statistics are collected for each column. After interval minutes, statistics collection for the next column begins.

Corrective Action: No action is required.

ECAB61I STATISTICS COLLECTION STOPPEDLink copied to clipboard

Explanation: This information message indicates that statistics collection stopped in response to an F IOAGATE,STATOFF command. Collected data is purged and will not be available.

Corrective Action: No action is required.

ECAB62I STATISTICS DATA WAS RESETLink copied to clipboard

Explanation: This information message indicates that the command F IOAGATE,STATRESET was issued.

Data collected earlier is purged, and collection of new data restarts immediately.

Corrective Action: No action is required.

ECAB63W STATISTICS COLLECTION IS ALREADY ONLink copied to clipboard

Explanation: An F IOAGATE,STATON command was issued, but statistics collection for IOAGATE was already active. To reset the statistics collected data, use the command F IOAGATE,STATRESET instead.

IOAGATE statistics collection is not restarted. The modify command is rejected.

Corrective Action: No action is required.

ECAB64W STATISTICS COLLECTION IS ALREADY OFFLink copied to clipboard

Explanation: An F IOAGATE,STATOFF command was issued, but statistics collection for IOAGATE was not active.

The modify command is rejected. Normal processing continues.

Corrective Action: No action is required.

ECAB65W INVALID STATISTICS INTERVAL WAS SPECIFIEDLink copied to clipboard

Explanation: The value of interval in the command F IOAGATE,STATON,INTERVAL=interval is not valid.

The statistics interval sets the time scale for statistics collection and presentation. It must be in the range from 1 through 999 (minutes). For example, if INTERVAL is set to 5, the statistics report will maintain and present the figures at intervals of 5 minutes.

The modify command is rejected. Normal processing continues.

Corrective Action: Correct the value of interval and reissue the command.

Messages ECAC00 through ECACxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAC60E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) SIB ALLOCATION FAILED FOR `msgType.reqType` MESSAGELink copied to clipboard

Explanation: IOAGATE encountered an internal problem when trying to allocate a SIB (Service Instance Block) control block for the current transaction (message).

The variables in this message are:

channelId - the identity of the channel that detected the problem
protocol - the current channel uses this communication protocol. Valid values are:
- TCP -TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that detected the problem
type - the internal type of the channel task that detected the problem
msgType - the type of the messageValid values are:
- INCOMING
- OUTGOING
- INTERNAL
reqType - the type of the requestThis variable may not appear.Valid values are:
- NOTIFY
- STOP
- CANCEL
- MODIFY
- INIT
- ATTTACH

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC61E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) SIB LOCK FAILED FOR `msgType.reqType` MESSAGELink copied to clipboard

Explanation: IOAGATE encountered an internal problem when processing the SIB (Service Instance Block) control block of the current transaction (message).

The variables in this message are:

channelId - the identity of the channel that detected the problem
protocol - the current channel uses this communication protocol Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that detected the problem
type - the internal type of the channel task that detected the problem
msgType - the type of the messageValid values are:
- INCOMING
- OUTGOING
- INTERNAL
reqType - the type of the requestThis variable may not appear.Valid values are:
- NOTIFY
- STOP
- CANCEL
- MODIFY
- INIT
- ATTTACH

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC62E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE FAILED DUE TO DISCONNECTION, PORT`(port)` /APPLID(`applId`)Link copied to clipboard

Explanation: IOAGATE failed to process the specified message due to disconnection on the indicated port (TCP protocol) port or the VTAM application ID (SNA protocol) applId.

The variables in this message are:

channelId - the identity of the channel that detected the problem
protocol - the current channel uses this communication protocol Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that detected the problem
type - the internal type of the channel task that detected the problem
msgType - the type of the messageValid values are:
- INCOMING
- OUTGOING
- INTERNAL
port - the port number for TCP disconnection
applId - the VTAM application identity for SNA disconnection

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC63I CHANNEL(`channelId.` SNA) DEALLOCATE SENT TO PARTNER LU(`luName`) OUT_CONVID(`out_conversation_id`) IN-CONVID(`in_conversation_id`)Link copied to clipboard

Explanation: This information message indicates that a DEALLOCATE command was sent to the partner IOAGATE, because either the partner or the local IOAGATE terminated.

The variables in this message are:

channelId - the identity of the channel with which the specified partner was communicating
luName - VTAM LU 6.2 (APPC) LU name of the partner IOAGATE
out_conversation_id - VTAM LU 6.2 (APPC) outgoing conversation identity
in_conversation_id - VTAM LU 6.2 (APPC) incoming conversation identity

If the partner IOAGATE is terminating, the local IOAGATE sends a termination message to the partner IOAGATE. If the local IOAGATE is terminating, it sends termination messages to its partner IOAGATEs.

Corrective Action: No action is required.

ECAC64E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, NO APPL SERVER IS AVAILABLELink copied to clipboard

Explanation: IOAGATE rejected the specified message because no Application server was available.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protocol Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the messageValid values are:
- INCOMING
- OUTGOING
- INTERNAL

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC65E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, REQUIRED ADDR. SPACE(`addrSpaceId`) IS DOWNLink copied to clipboard

Explanation: IOAGATE rejected the specified message because the required Application server was down.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protocol. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the message. Valid values are:
- INCOMING
- OUTGOING
- INTERNAL
addrSpaceId - the internal identity of the address space of the Application

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC66E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, CHANNEL DOES NOT SUPPORT APPLICATION(`applCode`)Link copied to clipboard

Explanation: IOAGATE rejected the specified message because an invalid application was specified in the message.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this protocolValid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the messageValid values are:
- INCOMING
- OUTGOING
- INTERNAL
applCode - the application code

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC67E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, APPL. SERVER(`applServer`) IS UNAVAILABLELink copied to clipboard

Explanation: IOAGATE rejected the specified message because the required application server was unavailable.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protocolValid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the messageValid values are:
- INCOMING
- OUTGOING
- INTERNAL
applServer - the name of the unavailable application server

Corrective Action: Contact BMC Customer Support if the message persists.

ECAC68E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `hshakeType` HANDSHAKE(FROM=`local_node_id` TO=`target_node_id`) `action`Link copied to clipboard

Explanation: IOAGATE is about to ignore or reject the specified handshake message for the reason indicated in the message that accompanies this ECAC68E message.

The variables in this message are:

channelId - the identity of the channel that rejected the handshake
protocol - the current channel uses this communication protocolValid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that detected the problem
type - the internal type of the channel task that detected the problem
hshakeType - the type of the handshakeValid values are:
- CONNECT
- CONFIRM
- REJECT
- INFORM
- UNKNOWN
local_node_id - the identity of the local node in which the local IOAGATE is running
target_node_id - the identity of the partner node in which the partner IOAGATE is running
action - the action that IOAGATE is about to perform to the received handshake Valid values are:
- TO BE REJECTED
- RECEIVED
- TO BE PRINTED

IOAGATE disconnects from the IOAGATE that sent this handshake message.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map. For more information on configuring the network map, see the INCONTROL for z/OS Installation Guide.

ECAC69I REASON: NO PARTNER NODE IN MAP(`mapId`) MATCHES SENDER NODE(`node_id`) IN HANDSHAKELink copied to clipboard

Explanation: This message follows the ECAC68E message, and specifies the exact reason for the handshake rejection, which is that the network map does not contain the node name obtained in the handshake message.

The variables in this message are:

mapId - the identity of the network map
node_id - the identity of the partner node in which the partner IOAGATE is running

IOAGATE disconnects from the IOAGATE that sent this handshake message.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map. For more information on configuring the network map, refer to the INCONTROL for z/OS Installation Guide.

ECAC6AI LOCAL NODE(`local_node_id`) OF CHANNEL(`channel`) DOES NOT MATCH TARGET NODE(`target_node_id`) OF HANDSHAKELink copied to clipboard

Explanation: The message follows the ECAC68E message, and specifies an exact reason for the handshake rejection, that is, the local node name does not match the target node name obtained in the handshake message.

The variables in this message are:

local_node_id - the identity of the local node in which the local IOAGATE is running
channel - the identity of the channel that detected the problem
target_node_id - the identity of the partner node in which the partner IOAGATE is running

IOAGATE disconnects from the partner IOAGATE that sent this handshake message.

Corrective Action: Correct IOAGATE-to-IOAGATE connection configuration in the network map. For more information on configuring the network map, see the INCONTROL for z/OS Installation Guide.

ECAC6BI REASON: INVALID HANDSHAKE RECEIVED: `rsn`Link copied to clipboard

Explanation: This message follows the ECAC68E message, and specifies an exact reason for the handshake rejection, which is that the handshake message has an illegal format.

In this message, rsn is the reason for the identification of the handshake as invalid. Valid values are:

Bad HANDSHAKE ID
Bad Type-Message
Bad Type-Record
Bad Product-ID
Bad Software-Lvl

IOAGATE disconnects from the IOAGATE that sent the handshake message.

Corrective Action: Contact BMC Customer Support.

ECAC6CE CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, INVALID SEQUENCE NUMBER(`seqNumber`)Link copied to clipboard

Explanation: IOAGATE rejected the specified message due to an invalid sequence number in the message.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protocolValid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the messageValid values are:
- INCOMING
- OUTGOING
- INTERNAL
seqNumber - the invalid sequence number that appears in the message

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6DE CHANNEL(`channelId.protocol`) TASK(`taskId.type`) ALLOCATED SIB NOT FOUND FOR `msgType.reqType` MESSAGELink copied to clipboard

Explanation: IOAGATE encountered an internal problem. It was unable to find the SIB (Service Instance Block) control block for the current transaction although this SIB must exist.

The variables in this message are:

channelId - the identity of the channel that detected the problem
protocol - the current channel uses this communication protocol. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that detected the problem
type - the internal type of the channel task that detected the problem
msgType - the type of the message. Valid values are:
- INCOMING
- OUTGOING
- INTERNAL
reqType - the type of the request This variable may not appear.Valid values are:
- NOTIFY
- STOP
- CANCEL
- MODIFY
- INIT
- ATTACH

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6EE CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, INVALID SERVICE ID (`serviceId`)Link copied to clipboard

Explanation: IOAGATE rejected the specified message due to an invalid service identity (or transaction code) in the message.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protocol. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that detected the problem
type - the internal type of the channel task that detected the problem
msgType - the type of the message. Valid values are:
- INCOMING
- OUTGOING
- INTERNAL
serviceId - the transaction code

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6FE CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, INVALID ADDR.SPACE ID(`addrSpaceId)`Link copied to clipboard

Explanation: IOAGATE rejected the specified message because there was an invalid address space internal ID in the message.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protoco. lValid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the message. Valid values are:
- INCOMING
- OUTGOING
- INTERNAL
addrSpaceId - the internal identity of the application address space

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6GE CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, SERVICE(`serviceId)` DISABLEDLink copied to clipboard

Explanation: IOAGATE rejected the specified message because the service indicated by the service_ id transaction code was disabled by IOAGATE.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protocol. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the message. Valid values are:
- INCOMING
- OUTGOING
- INTERNAL
serviceId - the code of a transaction to be performed by IOAGATE

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6HE CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` EXTENDED MESSAGE REJECTED, INVALID APPLICATION(`appl`)Link copied to clipboard

Explanation: IOAGATE rejected the specified extended message due to an invalid application code specified in the message. An extended message format is used in IOAGATE-to-IOAGATE communication.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protocol. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the message. Valid values are:
- INCOMING
- OUTGOING
- INTERNAL
appl - the invalid application code

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6IE CHANNEL(`channelId.protocol`) TASK(`taskId.type`) `msgType` MESSAGE REJECTED, INVALID APPLICATION CODE(`appl`)Link copied to clipboard

Explanation: IOAGATE rejected the specified message due to an invalid application code specified in the message.

The variables in this message are:

channelId - the identity of the channel that rejected the message
protocol - the current channel uses this communication protocol. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
msgType - the type of the message. Valid values are:
- INCOMING
- OUTGOING
- INTERNAL
appl - the invalid application code

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6JI REASON: LOCAL NODE(`local_node_id`) ALREADY CONNECTED TO PARTNER(`partner_node_id`)Link copied to clipboard

Explanation: This message follows the ECAC68E message and specifies an exact reason for the handshake rejection. The reason is that the local IOAGATE received a handshake message from the partner IOAGATE, but connection between these IOAGATEs had been already established. This may happen when both IOAGATEs are configured with the CONNECTOR parameter set to LOCAL and the local IOAGATE had already succeeded in initiating and establishing the connection.

The variables in this message are:

local_node_id - the identity of the local node in which the local IOAGATE is running
partner_node_id - the identity of the partner node in which the partner IOAGATE is running

Corrective Action: No action is required.

ECAC6KI REASON: LOCAL NODE(`local_node_id`) IS CONNECTING TO PARTNER(`partner_node_id`)Link copied to clipboard

Explanation: This message follows the ECAC68E message and specifies an exact reason for the handshake rejection. The reason is that both IOAGATEs are configured with the CONNECTOR parameter set to LOCAL and the local IOAGATE is not able to accept a handshake because it has been connecting to the specified Partner node.

The variables in this message are

local_node_id - the identity of the local node in which the local IOAGATE is running
partner_node_id - the identity of the partner node in which the partner IOAGATE is running

IOAGATE ignores the handshake message.

ECAC6LI REJECTION NOTICE (`msgId`) RECEIVED FROM PARTNER(`partnerId`):Link copied to clipboard

Explanation: A diagnostic message has been received from the partnerId partner IOAGATE.

This ECAC6LI message is followed by the ECAC6QI message, which displays the diagnostic message that was received.

The variables in this message are:

msgId - the identity of the diagnostic message
partnerId - the identity of the partner IOAGATE

Corrective Action: No action is required.

ECAC6ME CHANNEL(`channelId.protocol`) TASK(`taskId.type`) GET-IOAGATE-ID REQUEST REJECTED, `rsn`Link copied to clipboard

Explanation: The message indicates that either IOAGATE received an invalid GET-IOAGATE-ID request from a client or IOAGATE failed to create a response to this request.

The variables in this message are:

channelId - the identity of the channel that detected the problem
taskId - the internal identity of the channel task that detected the problem
type - the internal type of the channel task that detected the problem
rsn - the reason for the rejection of the request. Valid values for rsn are:
- Failure to set the IP address/Hostname
- Invalid request received

Processing continues. The client that sent the invalid request has been disconnected.

Corrective Action: If the message persists, contact BMC Customer Support.

ECAC6NE CHANNEL(`channelId`.TCP) TASK(`taskId.type`) CHECKSUM ENCRYPTION REQUEST REJECTED, `rsn`Link copied to clipboard

Explanation: The message indicates that IOAGATE rejected a checksum encryption request from a client for the reason rsn.

The variables in this message are:

channelId - the identity of the channel that rejected the request
taskId - the internal identity of the channel task that rejected the request
type - the internal type of the channel task that rejected the request
rsn - the reason for the rejection of the requestValid values for rsn are:
- Invalid CheckSum request
- Encryption not configured
- Encryption disabled
- No Encryption processor
- No CheckSum prepared
- Invalid CheckSum arrived
- Invalid algorithm given
- Channel is not eligible

Processing continues. The client that sent the request has disconnected.

Corrective Action: Do the following:

Ensure that IOAGATE and the client use the same file of encryption keys.
Examine the JES log, DAIGLOG, and DATRACE outputs from IOAGATE for additional error indications and try to correct the problem.
If the message persists, contact BMC Customer Support.

ECAC6OE CHANNEL(`channelId`.TCP) TASK(`taskId.type`) INCOMING MESSAGE REJECTED, `rsn`.Link copied to clipboard

Explanation: IOAGATE rejected an incoming message from a client for the reason rsn.

The variables in this message are:

channelId - the identity of the channel that rejected the message
taskId - the internal identity of the channel task that rejected the message
type - the internal type of the channel task that rejected the message
rsn - the reason for the rejection of the messageValid values for rsn are:
- Message must be encrypted
- Encryption not configured
- Encryption disabled

Processing continues. The client that sent the message has disconnected.

Corrective Action: Do the following:

Ensure that IOAGATE and the client use the same file of encryption keys.
Examine the JES Log, DAIGLOG, and DATRACE outputs from IOAGATE for further information about the error and take appropriate corrective action.
If the message persists, contact BMC Customer Support.

ECAC6PI REASON NOTICE (`msgId`) RECEIVED FROM PARTNER(`partnerId`):Link copied to clipboard

Explanation: The message indicates that a diagnostic message has come from the partner IOAGATE.

This ECAC6PI message is followed by the ECAC6QI message that displays the diagnostic message itself.

The variables in this message are:

msgId - the identity of the diagnostic message
partnerId - identity of the partner IOAGATE

Corrective Action: No action is required.

ECAC6QI `diagMsg`Link copied to clipboard

Explanation: This information message follows messages ECAC6LI and ECAC6PI, and displays the diagnostic message that arrived from the partner IOAGATE that issued it.

In this message, diagMsg is the text of the diagnostic message that arrived from the partner IOAGATE.

Corrective Action: No action is required.

ECAC70I PROBABLE LOGMODE DEFINITIONS ERRORLink copied to clipboard

Explanation: This information message indicates that the probable cause of the error reported in the preceding message is that an IOAGATE attempted to connect to a partner IOAGATE over the multiple connection (MC) SNA communication channel. However, the LOGMODE definitions of the partners probably do not match.

When two IOAGATEs attempt to connect, both send their LOGMODE parameters during the BIND process. If these parameters do not match, connection fails.

The ECAG89W, ECAG90E, or ECAG95E message, which precedes this message, provides more details about the error.

The ECAC70I message is issued for a multiple connection (MC) SNA communication channel only.

Connection between IOAGATEs fails.

Corrective Action: Check the LOGMODE definition for each partner in the appropriate SYS1.VTAMLST library. Ensure they are defined according to instructions in the appropriate step of the Control-O chapter of the INCONTROL for z/OS Installation Guide, and restart the IOAGATE.

ECAC71I PROBABLE ALLOCATION FAILURE NO RETRYLink copied to clipboard

Explanation: This information message indicates that the probable cause of the connection failure reported in the preceding message is that a local IOAGATE attempted to connect to a partner IOAGATE over the multiple connection (MC) SNA communication channel, and perform a VTAM LU 6.2 allocation request. It also indicates that no attempt will be made to connect again.

The ECAG89W, ECAG90E, or ECAG95E message, which precedes this message, provides more details about the error.

The ECAC70I message is issued for a multiple connection (MC) SNA communication channel only.

Corrective Action: Check that the partner Gateway LU is active in VTAM and that it is defined according to instructions in the appropriate step in the Control-O chapter of the INCONTROL for z/OS Installation Guide. Then restart the IOAGATE. If the problem persists, call your system programmer for assistance.

ECAC72I PROBABLE ALLOCATION FAILURE RETRYLink copied to clipboard

Explanation: This information message indicates that the probable cause of the connection failure reported in the preceding message is that a local IOAGATE attempted to establish a connection with a partner IOAGATE over the multiple connection (MC) SNA communication channel and performed a VTAM LU 6.2 allocation request. It also indicates that an attempt will be made to connect again.

The ECAG89W, ECAG90E, or ECAG95E message, which precedes this message, provides more details about the error.

The ECAC70I message is issued for a multiple connection (MC) SNA communication channel only.

Processing continues. Connection is retried after one minute.

Corrective Action: Ensure that the partner Gateway LU is active in VTAM and that it is defined according to instructions in the appropriate step in the Control-O chapter of the INCONTROL for z/OS Installation Guide. Then restart the IOAGATE. If the problem persists, call your system programmer for assistance.

ECAC73I PROBABLE MISMATCH IN VTAM DEFINITIONSLink copied to clipboard

Explanation: This information message indicates that the probable cause of the connection failure reported in the preceding message, is that there is a mismatch in the IOAGATE LU definitions. An IOAGATE attempted to establish connection with a partner IOAGATE over the multiple connection (MC) SNA communication channel. However, the VTAM 6.2 LU is defined incorrectly.

The ECAG89W, ECAG90E, or ECAG95E message, which precedes this message, provides more details about the error.

The ECAC70I message is issued for a multiple connection (MC) SNA communication channel only.

The multiple connection SNA channel shuts down. Processing continues.

Corrective Action: Define the IOAGATE VTAM 6.2 LU according to instructions in the appropriate step in the Control-O chapter of the INCONTROL for z/OS Installation Guide. Then restart the IOAGATE.

Messages ECAE00 through ECAExxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAE01I ENCRYPTION ENVIRONMENT INITIALIZED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that ENCRYPT was set to YES in the ECAPARM configuration file for at least one Application server, and that IOAGATE has successfully initialized the encryption environment.

Corrective Action: No action is required.

ECAE02W CHANNEL(`channelId`.TCP) TASK(`taskId.type`) ENCRYPTION PROPAGATED ON APPL.SERVER(`applServerName.addrSpaceId`)Link copied to clipboard

Explanation: This message indicates that more than one application server is linked in the ECAPARM configuration file to the channelId channel, and that ENCRYPT was set to YES for at least one of these servers. The specified channel automatically propagates the ENCRYPT=YES setting on all the servers linked to the channel.

The variables in this message are:

channelId - the identity of the channel that propagates ENCRYPT=YES for all application servers linked to this channel
taskId - the internal identity of the channel task that propagates ENCRYPT=YES for each application server linked to this channel
type - the internal type of the channel task that propagates ENCRYPT=YES for each application server linked to this channel
applServerName - the full name of the application server for which ENCRYPT was set to YES
addrSpaceId - the internal ID of the application server address space

IOAGATE has propagated the setting of ENCRYPT to YES for the indicated Application server. Normal processing continues.

Corrective Action: No action is required.

ECAE0VE FAILURE TO DECRYPT AN INCOMING MESSAGE: `rsn`Link copied to clipboard

Explanation: IOAGATE encountered an internal error when trying to decrypt an incoming message.

In this message, rsn is a reason code that shows the reason for the failure.

Valid values for rsn are:

Failure to get ENC_key - failure to retrieve an encryption key
ENC_decr function failed - the decryption function failed

Corrective Action: Contact BMC Customer Support.

ECAE0WE APPL.SERVER(`applServerName.addrSpaceId`) HAS BEEN DISABLED DUE TO FAILURE TO INITIALIZE ENCRYPTIONLink copied to clipboard

Explanation: IOAGATE failed to initialize the encryption environment requested by the setting of ENCRYPT to YES in the ECAPARM configuration file for the Application server applServerName.

The variables in this message are:

applServerName - the name of the Application server that requested the encryption
addrSpaceId - the internal identity of the address space of the Application server that requested the encryption

Processing continues. The indicated Application server is not started.

Corrective Action: Check the JES log, DAIGLOG, and DATRACE outputs of IOAGATE for additional error indications. Try to correct the problem. If the problem persists, contact BMC Customer Support.

ECAE0XE ENCRYPTION DISABLED DUE TO FAILURE TO LOAD THE FILE OF KEYSLink copied to clipboard

Explanation: When establishing the encryption environment, IOAGATE failed to load the file of keys that is used to perform encryption and decryption.

Processing continues. The encryption function has been disabled. The Application server that requests encryption is not started.

Corrective Action: Transfer the appropriate file of keys from the client side. If the problem persists, contact BMC Customer Support.

ECAE0YS ENCRYPTION PROCESSOR FAILED: INVALID ACTION CODE(`actn_code`) RECEIVEDLink copied to clipboard

Explanation: IOAGATE encountered a severe internal error when trying to perform an internal encryption or decryption function.

In this message, actn_code is the invalid action code that was received by the encryption processor.

The Application server that tried to perform the internal encryption or decryption function shuts down.

Corrective Action: Contact BMC Customer Support.

ECAE0ZS ENCRYPTION PROCESSOR FAILED: MCT UNAVAILABLELink copied to clipboard

Explanation: IOAGATE encountered a severe internal error when trying to perform an internal encryption or decryption function.

The Application server that tried to perform the internal encryption or decryption function shuts down.

Corrective Action: Contact BMC Customer Support.

ECAE40I CHANNEL(`channelId`.TCP) ALL TASKS STARTED, PORT(`port`) APPLICATION(`applicId`)Link copied to clipboard

Explanation: This information message indicates that all communication tasks belonging to the specified dual connection (DC) TCP communication channel started successfully. During initialization, IOAGATE starts the tasks of all communication channels defined in the ECAPARM configuration file.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
port - the TCP/IP communication port number used by the specified TCP channel to listen for connection
applicId - the application linked to the specified channel

Corrective Action: No action is required.

ECAE41I CHANNEL(`channelId`.SNA) ALL TASKS STARTED, APPLIDS(`applId1,applId2`) APPLICATION(`applicId`)Link copied to clipboard

Explanation: This information message indicates that all communication tasks of the indicated dual connection (DC) SNA communication channel started successfully. During initialization, IOAGATE starts the tasks of all communication channels defined in the ECAPARM configuration file.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
applId1, applId2 - VTAM 6.2 (APPC) LU application IDs specified by the APPLIDS parameter in the ECAPARM configuration file for the channel
applicId - the application linked to the channel

Corrective Action: No action is required.

ECAE42I CHANNEL(`channelId.`TCP) ALL TASKS STARTED, PORT(`port`) APPLICATIONS(`applicId`)Link copied to clipboard

Explanation: This information message indicates that all communication tasks of the specified multiple connection (MC) TCP communication channel started successfully. During initialization, IOAGATE starts the tasks of all communication channels defined in the ECAPARM configuration file.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
port - the number of the TCP/IP communication port that the specified TCP channel uses to listen for connection
applicId - a list of the applications linked to the channel

Corrective Action: No action is required.

ECAE43I CHANNEL(`channelId.`SNA) ALL TASKS STARTED, APPLID(`applId`) APPLICATIONS(`applicId`)Link copied to clipboard

Explanation: This information message indicates that all communication tasks belonging to the indicated multiple connection (MC) SNA channel started successfully. During initialization, IOAGATE starts the tasks of all communication channels defined in the ECAPARM configuration file.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
applId - VTAM 6.2 (APPC) LU APPLID parameter specified in the ECAPARM configuration file for a multiple connection SNA channel
applicId - List of applications linked to the channel

Corrective Action: No action is required.

ECAE44I CHANNEL(`channelId.protocol`) RUNNING IN NODE(`node_id`) WITH NETWORK MAP(`mapId`)Link copied to clipboard

Explanation: This information message indicates that the indicated multiple connection (MC) communication channel supporting IOAGATE to IOAGATE communication started successfully. During initialization, IOAGATE starts the communication channels defined in the ECAPARM configuration file.

The variables in this message are:

protocol - the communication protocol used by the current channel, which may be TCP (TCP/IP) or SNA
channelId - the channel identity assigned by the user in the ECAPARM configuration file
node_id - the node in which the local IOAGATE is running
mapId - a member in the IOA PARM library that describes a map of network connections between IOAGATEs that enables one IOAGATE to communicate with another over a multiple connection SNA channel

Corrective Action: No action is required.

ECAE45I CHANNEL(`channelId.`TCP) IS UP, PORT(`port`) APPLICATION(`applicId`)Link copied to clipboard

Explanation: This information message indicates that the specified dual connection (DC) TCP communication channel of the IOAGATE is up. The dual connection TCP communication channel was initialized successfully, and is ready for communication.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
port - the number of the TCP/IP communication port used by the TCP channel to listen for connection
applicId - the identity of the application supported by the application server that is linked to the channel

Corrective Action: No action is required.

ECAE46I CHANNEL(`channelId`.TCP) IS UP, PORT(`port`) APPLICATIONS(`applicId`)Link copied to clipboard

Explanation: This information message indicates that the specified multiple connection (MC) TCP communication channel of the IOAGATE is up. The multiple connection TCP communication channel was initialized successfully, and is ready for communication.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
port - the number of the TCP/IP communication port that the TCP channel uses to listen for connection
applicId - the identity of the application supported by the application server that is linked to the channel

Corrective Action: No action is required.

ECAE47I CHANNEL(`channelId.`SNA) IS UP, APPLIDS(`applId1,applId2`) APPLICATION(`applicId`)Link copied to clipboard

Explanation: This information message indicates that the specified dual connection (DC) SNA communication channel of the IOAGATE is up. The dual connection SNA communication channel was initialized successfully, and is ready for communication.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
applId1, applId2 - VTAM 6.2 (APPC) LU application identities specified by the APPLIDS parameter in the ECAPARM configuration file for the channel
applicId - the identity of the application supported by the application server that is linked to the channel

Corrective Action: No action is required.

ECAE48I CHANNEL(`channelId.`SNA) IS UP, APPLID(`applId`) APPLICATIONS(`applicId`)Link copied to clipboard

Explanation: This information message indicates that the specified multiple connection (MC) SNA communication channel is up. The multiple connection SNA communication channel was initialized successfully, and is ready for communications.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
applId - VTAM 6.2 (APPC) LU application ID specified by APPLID parameter in the ECAPARM configuration file for the channel
applicId - the identity of the application supported by the application server that is linked to the channel

Corrective Action: No action is required.

ECAE49W CHANNEL(`channelId`.TCP) PORT(`port`), RECYCLING INITIATED DUE TO APPL.SERVER (`applServerName.addrSpaceId`) FAILURELink copied to clipboard

Explanation: IOAGATE detected a failure of the specified application server. As a result of the application server failure, IOAGATE initiated recycling of the indicated TCP channel.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
port - the number of the TCP/IP communication port that the TCP channel uses to listen for connection
applServerName - the name of the failed application server
addrSpaceId - the internal identity of the failed application server address space

Corrective Action: No action is required.

ECAE4AW CHANNEL(`channelId.`SNA) APPLIDS(`applId1,applId2`), RECYCLING INITIATED DUE TO APPL.SERVER (`applServerName.addrSpaceId`) FAILURELink copied to clipboard

Explanation: IOAGATE detected a failure of the specified application server. As a result of the application server failure, IOAGATE initiated recycling of the indicated SNA channel.

The variables in this message are:

channelId - the channel identity assigned by the user in the ECAPARM configuration file
applId1, applId2 - VTAM 6.2 (APPC) LU application identities specified by APPLIDS parameter in the ECAPARM configuration file for the channel
applServerName - the name of the failed application server
addrSpaceId - the internal identity of the failed application server address space

Corrective Action: No action is required.

ECAE50S LOAD FAILED FOR MODULE(`mod`)Link copied to clipboard

Explanation: An attempt to load the mod module into the main memory of either the IOAGATE or application server address space failed. The system completion code indicates the exact reason for the failure.

Possible causes are:

The mod module is not in the IOA Load library,
There is not enough storage.

The IOAGATE or application server address space shuts down, with a return code of 52 in either case.

Corrective Action: Do the following:

Examine the reason code for the failure in the system log.
Try to correct the problem.
If necessary, increase the region size.
If the problem persists, call your system programmer for assistance.

ECAE51W ERROR IN MODASID COMMAND `rsn`Link copied to clipboard

Explanation: IOAGATE detected an error in the F IOAGATE,MODASID modifyCommand, modifyCommandParms command that was issued. The MODASID command is used to submit a modify command, expressed as MODASID parameters, that will be executed in the address space of the application server.

Possible values of rsn are:

COMMAND IS EMPTY - there are no parameters in the MODASID command
ADDR.SPACE IS DOWN - the address space of the application server specified in the MODASID command is not active
BAD APPL.SERVER ID - the address space of the application server specified in the MODASID command does not exist

The MODASID command is not processed. Normal processing continues.

Corrective Action: Correct and reissue the MODASID command.

ECAE52I MODIFY(`modifyCommand, modifyCommandParms`) FOR SERVER(`applServerName.type.taskId.addrSpaceId`) SUBMITTEDLink copied to clipboard

Explanation: This information message indicates that IOAGATE accepted and submitted the command F IOAGATE,MODASID=modifyCommand, modifyCommandParms. The MODASID command is used to submit a modify command, expressed as MODASID parameters, that will be executed in the address space of the application server.

The variables in this message are:

modifyCommand - the modify command to be performed in an application server address space
modifyCommandParms - the parameters, if any, required by modifyCommand
applServerName - the name of the application server
type - the CD server task type
taskId - the internal identity of the server task
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAE53W NO APPLICATION SERVER HAS BECOME AVAILABLE IN THE LAST `interval` MINUTESLink copied to clipboard

Explanation: No application server address space started in the specified time interval, either since IOAGATE launched the application servers defined in the ECAPARM configuration file or since the previous ECAE53W warning. There might be a problem that prevents an application server from being started in time.

In this message, interval is the number of minutes between occurrences of this warning message. The default interval is three minutes.

Processing continues. If the STAYUP parameter is set to YES in the ECAPARM configuration file, this message is issued every three minutes until at least a single application server becomes available. Otherwise, after issuing five ECAE53W warnings, IOAGATE shuts down.

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to correct the problem. If the problem persists, contact BMC Customer Support.

ECAE54S IOAGATE IS GOING DOWN, NO APPLICATION SERVER HAS BECOME AVAILABLE IN THE LAST `num` MINUTESLink copied to clipboard

Explanation: No application server address started in the specified number (num) of minutes since IOAGATE launched the application servers defined in the ECAPARM configuration file. Some problem is preventing application servers from starting in time. Several ECAE53W warnings precede this message.

This message can be issued only if the STAYUP parameter is set to NO in the ECAPARM configuration file. For more information, see message ECAE53W.

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log, and the DATRACE log for more information. Try to correct the problem. If the problem persists, contact BMC Customer Support.

ECAE56S `module` INTERNAL ERROR, INVALID PARAMETERS PASSED TO `module`Link copied to clipboard

Explanation: IOAGATE encountered a severe internal problem during initialization.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAE57I `monitorId` is staying up due to STAYUP=YES specification in ECAPARMLink copied to clipboard

Explanation: This information message indicates that all Application servers either failed or did not start. IOAGATE cannot go down, because the STAYUP parameter is set to UP in the ECAPARM configuration file.

In this message, monitorId is the started task (STC) name of the IOAGATE.

The IOAGATE monitor continues to run.

Corrective Action: No action is required.

Messages ECAF00 through ECAFxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAF01I CHANNEL(`channelId`.TCP) COMTASK(`taskId`) SOCKET(`socket`) FILE TRANSFER(`transfer_id`) STARTED, FILE(`file`)Link copied to clipboard

Explanation: This information message indicates that the specified multiple connection (MC) TCP channel successfully initiated a file transfer in response to the current request from a client of the Control-D File Transfer Option (FTO) client request.

The variables in this message are:

channelId - the identity of the channel that performs the file transfer
taskId - the internal identity of the communication task that performs the file transfer
socket - the TCP/IP socket number assigned to the connection with the file transfer client within the indicated communication task
transfer_id - the internal identity assigned by the channel to this file transfer
file - the name of the file transferredIf the client that resides on the mainframe platform initiated the request, then this is the DD name by which the file was allocated.

Corrective Action: No action is required.

ECAF07I TRANSFER(`transfer_id`) ProtVer(`protocol_versn`) Elapsed=(`elapsed_time`) Blocks=(`blocks_no`) Bytes=(`bytes_no`) Compr.rate=`compression_rate%`Link copied to clipboard

Explanation: This information message follows the ECAF08I message issued for the transfer_id file transfer and provides statistical data for that transfer.

The variables in this message are:

transfer_id - the internal identity assigned by IOAGATE to this file transfer
protocol_versn - 2-digit version of the communication file transfer protocol supported by the client
elapsed_time - the amount of time that elapsed from the beginning of the file transfer to its completion, in the format hh:mm:ss.tht where
- hh - hours
- mm - minutes
- ss - seconds
- tht - tenths, hundredths and thousandths of a second
blocks_no - the total number of blocks received during the entire file transfer
bytes_no - the total number of bytes received during the entire file transfer
compression_rate - the rate (in percent) at which data bytes were compressed in the transfer_id file transferIf there was no compression, 00% is displayed.Compression is supported only in relation to clients that support a communication file transfer protocol version of 40 or higher.

Corrective Action: No action is required.

ECAF08I CHANNEL(`channelId.`TCP) COMTASK(`taskId`) SOCKET(`socket`) FILE TRANSFER(`transfer_id`) `complCode`, FILE(`file`)Link copied to clipboard

Explanation: This information message indicates that the specified multiple connection (MC) TCP channel finished processing the current request from a client of the Control-D Option (FTO).

This message may be followed by the ECAF07I message, which provides statistical data relating to the file transfer that has just been completed.

The variables in this message are:

channelId - the identity of the channel that handled the file transfer
taskId - the internal identity of the communication task that handled the file transfer
socket - the TCP/IP socket number assigned to the connection with the Control-D File Transfer option client within the indicated communication task
transfer_id - the internal identity assigned by the channel to this file transfer
complCode - a code indicating how the specified file transfer ended Valid values are:
- COMPLETED - the file transfer completed successfully
- REJECTED - the application server rejected the file
file - the name of the file to be transferredIf the client that resides on the mainframe platform initiated the request, then this is a DD name by which the file was allocated.

Corrective Action: No action is required.

ECAF09S CHANNEL(`channelId.`TCP) COMTASK(`taskId`) SOCKET(`socket`), FTC CONNECTION CELL NOT FOUNDLink copied to clipboard

Explanation: A severe internal error occurred during processing of the current request from a client of Control-D File Transfer Option (FTO).

The variables in this message are:

channelId - the identity of the channel that encountered the error
taskId - the internal identity of the communication task that encountered the error
socket - the TCP/IP socket number assigned to the connection with the Control-D FTO client within the specified communication task

The current request is discarded, and processing continues.

Corrective Action: Contact BMC Customer Support.

ECAF0AS CHANNEL(`channelId.`TCP) COMTASK(`taskId`) ECAFTCM FAILED, RC(`rsn`)Link copied to clipboard

Explanation: The ECAFTCM internal routine failed to perform the required function during processing of an incoming request from a client of the Control-D File Transfer Option (FTO). This is a severe internal error.

The variables in this message are:

channelId - the identity of the channel that encountered the error
taskId - the internal identity of the communication task that encountered the error
rsn - the reason code returned by the ECAFTCM internal routine to indicate the severity of the failure Valid values are:
- 08 - the error enables processing to continue
- 12 - unrecoverable error

If an unrecoverable error occurred, processing stops. Otherwise, processing continues.

Corrective Action: Contact BMC Customer Support.

ECAF0BS CHANNEL(`channelId.`TCP) COMTASK(`taskId`) ECAFTCM OBTAINED BAD PARAMETER(`parameter`) FUNCTION(`func`)Link copied to clipboard

Explanation: This is a severe internal error. During processing of an incoming request from the Control-D File Transfer Option (FTO) client, the ECAFTCM internal routine obtained an invalid value for the indicated parameter.

The variables in this message are:

channelId - the identity of the channel that encountered the error
taskId - the internal identity of the communication task that encountered the error
parameter - the name of the parameter for which the invalid value was obtained
func - the identity of the function that was passed to the routine when it was invoked

Corrective Action: Contact BMC Customer Support.

ECAF0CW CHANNEL(`channelId.`TCP) COMTASK(`taskId`) COUNTER OF CTD/FTO CONNECTIONS HAS BEEN RESETLink copied to clipboard

Explanation: The ECAFTCM internal routine reset the internal counter of connections initiated by the Control-D File Transfer Option (FTO) client, because the counter exceeded the allowed maximum during processing of an incoming request.

Corrective Action: No action is required.

ECAF0DS CHANNEL(`channelId.`TCP) COMTASK(`taskId`) CLIENT(`client`) ECAFLTR OBTAINED BAD CALLMODE(`callmode`)Link copied to clipboard

Explanation: This is a severe internal error. The ECAFLTR internal routine of the specified multiple connection (MC) TCP channel was invoked with an invalid parameter during processing of a request.

The variables in this message are:

channelId - the identity of the channel processing the request
taskId - the internal identity of the communication task processing the request
client - 1-character code of the client associated with the request
callmode - the internal mode that is passed to the specified communication task as a parameter Valid values are:
- R - the call occurred after the communication task performed a RECEIVE
- S - the call occurred before the communication task performed a SEND
- T - the call occurred after the communication task performed a SEND
- E - the call occurred before the communication task performed a SEND of the error message

Corrective Action: Contact BMC Customer Support.

Messages ECAG00 through ECAGxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAG00I IOAGATE STARTED, RELEASE(`relId`) CCID(`changeLevel`)Link copied to clipboard

Explanation: This information message indicates that the IOAGATE monitor started normally.

The variables in this message are:

relId - the official release and the maintenance level of the IOAGATE
changeLevel - the change that was last applied to the main module of IOAGATE

Corrective Action: No action is required.

ECAG01W MAINTENANCE LEVEL MODULE(ECALVL) UNAVAILABLELink copied to clipboard

Explanation: The ECALVL module that contains the release and maintenance level information relating to IOAGATE was not found in the STEPLIB load library.

Corrective Action: No action is required.

ECAG02E IOAGATE NOT APF AUTHORIZEDLink copied to clipboard

Explanation: IOAGATE is not APF-authorized. The main module of IOAGATE either resides in a non-APF-authorized library or does not have the AC=1 attribute. All Load libraries concatenated to IOAGATE STEPLIB must be APF authorized.

IOAGATE shuts down.

Corrective Action: Either add all STEPLIB library names to the IEAAPF00 member in SYS1.PARMLIB, or use some other means available at the site to make the STEPLIB libraries APF-authorized.

ECAG03I .`channelId.protocol` SECTION OF THE `mapId` NETWORK MAP Link copied to clipboard

Explanation: This message is a header for the section of the network map that is in use by the indicated channel.

The variables in this message are:

channelId - the identity of the channel that uses the network map mapId
protocol - the communication protocol used by the current channelValid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
mapId - the name of the member in the IOA PARM library that describes a map of network connections between IOAGATEs that enable one IOAGATE to communicate with another over a multiple connection (MC) channel

Corrective Action: No action is required.

ECAG04E ATTACH FOR(`mod`) HAS FAILEDLink copied to clipboard

Explanation: IOAGATE could not attach an internal IOAGATE task during initialization. The system completion code indicates the exact reason for the failure.

Possible causes are:

The mod module is not in the IOA Load library.
There is not enough storage available for the IOAGATE.

IOAGATE shuts down.

Corrective Action: Find the reason code in the system log, and try to fix the problem. If necessary, increase the region size. If the problem persists, call your system programmer for assistance.

ECAG05S task (`taskId.type-channelId`) UNRECOVERABLE ERROR ENCOUNTERED, REASON (`rsn`): `explanation`Link copied to clipboard

An unrecoverable error occurred in the identified channel task.

The variables in this message are:

task - the name of the channel task in which the error occurred
taskId - the internal identity of the channel task in which the error occurred
type - the internal type of the task in which the error occurred
channelId - the identity of the channel to which the task belongs
rsn - the reason code of the error
explanation - short explanation for the error

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG06S FAILURE(`rsn`) TO OBTAIN A NEW LINKAGE INDEXLink copied to clipboard

Explanation: IOAGATE failed to obtain a new linkage index from MVS. The first time IOAGATE starts with a specific ECAPARM configuration file, it requests a new linkage index from the operating system during initialization to perform cross memory communication with its partner application server address spaces. However, the attempt to obtain a linkage index failed.

The reason code rsn is an internal identifier that the operating system assigned to this specific problem.

IOAGATE shuts down.

Corrective Action: Call your system programmer for assistance.

ECAG07I SHUT DOWN UPON REQUEST FROM CONSOLE(`console_id`)Link copied to clipboard

Explanation: This information message confirms that an operator issued the STOP command, which requests shutdown of the IOAGATE. The IEF404I message follows this message to indicate that shutdown is complete.

In this message, console_id is the identity of the console from which the STOP request was issued.

The value of console_id depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of console_id may coincide with the user ID of the operator who issued this request, depending on your local configuration.

Corrective Action: No action is required.

ECAG08I * LIST OF CURRENT ALLOCATIONS *Link copied to clipboard

Explanation: This information message indicates that IOAGATE allocated data sets to be used by IOAGATE or an application server manager in this run. It is a header for the full list of allocated data sets. Each occurrence of message ECAG09I that follows this message specifies a different allocated data set.

Corrective Action: No action is required.

ECAG09I `ddNametype dsn`Link copied to clipboard

Explanation: This information message identifies a data set allocated by IOAGATE for use by IOAGATE or an application server manager in this run. It is issued separately for each data set allocated.

The variables in this message are:

ddName - the name of the DD statement that allocates the data set
type - the type of allocation Valid values are:
- JCL - a DD statement specified permanently in JCL
- DYN - a DD statement allocated dynamically
dsn - the name of the data set allocated by the DD statement

Corrective Action: No action is required.

ECAG0AI MODIFY COMMAND ISSUED FROM CONSOLE (`console_id`) ACCEPTED, COMMAND(`cmd`)Link copied to clipboard

Explanation: This information message indicates that a valid modify command was issued.

The variables in this message are:

console_id - the identity of the console from which the modify command was issued.The value of console_id depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of console_id may coincide with the user ID of the operator who issued this request, depending on your local configuration.
cmd - the command that was issued

Corrective Action: No action is required.

ECAG0BW MODIFY COMMAND ISSUED FROM CONSOLE (`console_id`) REJECTED, COMMAND(`cmd`)Link copied to clipboard

Explanation: The modify command that has been issued is invalid. The ECAG0CI and ECAG25I messages that follow this ECAG0BW message provide a list of valid modify commands.

The variables in this message are:

console_id - the identity of the console from which the modify command was issued.The value of console_id depends on whether this request was issued from a physical or virtual console. If it was a virtual console, the value of console_id may coincide with the user ID of the operator who issued this request, depending on your local configuration.
cmd - the command that was issued

The modify command is rejected. Normal processing continues.

Corrective Action: Issue a valid modify command.

ECAG0CI VALID MODIFY COMMANDS ARE:Link copied to clipboard

Explanation: This information message introduces a list of valid modify commands after an invalid modify command was issued. Each of the ECAG25I messages that follows contains a valid modify command.

Corrective Action: No action is required.

ECAG0DI * FOLLOWING ECAPARM(`suffix`) CONFIGURATION FILE IS USED *Link copied to clipboard

Explanation: This information message is the header for the specified ECAPARM configuration file that IOAGATE or an application server will use in this run. ECAG0EI messages follow this message. Each ECAG0EI message displays a line of the ECAPARM configuration file.

In this message, suffix is a 1-character ID that specifies a unique ECAPARM configuration file.

Corrective Action: No action is required.

ECAG0EI `lineNumlineText`Link copied to clipboard

Explanation: Each occurrence of this message is a line of an ECAPARM configuration file that IOAGATE or an application server is currently using.

The variables in this message are:

lineNum - the sequential number of the current line of the ECAPARM configuration file
lineText - the contents of the current line of the ECAPARM configuration file

Corrective Action: No action is required.

ECAG0FI ISSUE "F `monitorId,?` " TO GET VALID COMMANDSLink copied to clipboard

Explanation: The message indicates that the command F IOAGATE,modifyCommand was issued, but the modifyCommand modify command is invalid.

Corrective Action: Issue the command F IOAGATE,modifyCommand with a valid modify command.

To obtain a list of available modify commands, issue the command F IOAGATE,?

ECAG0GW THERE IS NO ACTIVE APPLICATION SERVER, `monitorId` TERMINATINGLink copied to clipboard

Explanation: IOAGATE tried to launch an application server address space, but no such address space started, and STAYUP is not set to YES in the ECAPARM configuration file.

IOAGATE shuts down.

Corrective Action: No action is required.

ECAG0HI ENABLED FOR THE AUTOMATIC RESTART MANAGEMENT FUNCTIONLink copied to clipboard

Explanation: A valid ARMELEM parameter was specified in the ECAPARM configuration file, and was registered as an element of automatic restart management (ARM) for IOAGATE.

Corrective Action: No action is required.

ECAG0II AUTOMATIC RESTART IN PROGRESS AFTER UNEXPECTED FAILURELink copied to clipboard

Explanation: The message indicates that IOAGATE failed unexpectedly, but ARM support is enabled, and the operating system is automatically restarting IOAGATE.

IOAGATE restarts and normal processing continues.

Corrective Action: No action is required.

ECAG0JW AUTOMATIC RESTART MANAGEMENT REQUEST FAILED R15(`rc`) REASON (`rsn`) `short_explan`Link copied to clipboard

Explanation: The message indicates that when starting up, IOAGATE failed to activate automatic restart management (ARM).

The meaning of the variables in this message is shown in the following table:

rc	rsn	short_explan	Explanation
08	002C	ELEMENT NAME INVALID	An invalid element name was specified.
08	0150	ELEMENT NAME IN USE	The element name is registered in a different address space.
12	0004	NO ARM SUPPORT	The release of MVS or JES in use does not support the ARM function.
12	0104	MAX ARM USERS	The number of ARM users registered is the maximum permissible.
12	0160	NO ACCESS TO ARM CDS	This system provides no access to an ARM CDS.

ARM is not enabled. Normal processing continues.

Corrective Action: Correct the problem identified by the diagnostic information in this message, then restart IOAGATE.

ECAG0KW MODIFY(`cmd`) REJECTED, `rsn`Link copied to clipboard

Explanation: The message indicates that an F IOAGATE,modifyCommand command was issued, and that the command was rejected for the reason specified in the message.

The variables in this message are:

cmd - the modify command issued by the operator. Valid values are:
- CLOSE
- OPEN

rsn - the reason for the rejection of the modify command Possible reasons are:
- NO PARAMETER SPECIFIED
- INVALID CHANNEL SPECIFIED
- SPECIFIED CHANNEL WAS NOT CLOSED

The command is ignored. Normal processing continues.

Corrective Action: Correct the command and if necessary reissue it.

ECAG10I IOAGATE HAS BEEN INITIALIZED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that IOAGATE completed the initialization process successfully.

Corrective Action: No action is required.

ECAG11S FUNCTION(`func`) STD(`taskId.type`) ECAGNRL OBTAINED ZERO STD ADDRESSLink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG12S FUNCTION(`func`) STD(`taskId.type`) ECAGNRL OBTAINED ZERO STDIDLink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG13W CHANNEL(`channelId.`TCP) CONNECTION REJECTED, MAXIMUM NUMBER OF LINKS REACHEDLink copied to clipboard

Explanation: The maximum number of users is already connected to IOAGATE over the multiple connection TCP channel.

In this message, channelId is the identity of the channel over which communication was attempted.

The attempt to connect to IOAGATE over the specified multiple connection TCP channel fails, and normal processing continues.

Corrective Action: Try again later.

ECAG14I task (`taskId.type.channelId`) STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of an IOAGATE internal channel task.

The variables in this message are:

task - the IOAGATE task
taskId - the internal identity of the task
type - the internal type of the task
channelId - the identity of the channel to which the task belongs

Corrective Action: No action is required.

ECAG15I task (`taskId.type.channelId`) SHUT DOWNLink copied to clipboard

Explanation: This information message indicates normal termination of an IOAGATE internal channel task.

The variables in this message are:

task - the IOAGATE task
taskId - the internal identity of the task
type - the internal type of the task
channelId - the identity of the channel to which the task belongs

Corrective Action: No action is required.

ECAG16S FUNCTION(`func`) STD(`taskId.type`) ECAGNRL OBTAINED INVALID MCT ADDRESS IN STDLink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG17S FUNCTION(`func`) ECAGNRL OBTAINED INVALID MCTLink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

In this message, func is the internal numeric code of the function that IOAGATE tried to perform.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG18S FUNCTION(`func`) STD(`taskId.type`) ECAGNRL OBTAINED ZERO FUNCTION ADDRESSLink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG19S FUNCTION(`func`) STD(`taskId.type`) ECAGNRL OBTAINED ZERO FUNCTION CODELink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG1AS FUNCTION(`func`) STD(`taskId.type`) ECAGNRL OBTAINED INVALID STDIDLink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

func - the internal numeric code of the function that IOAGATE tried to perform
taskId - the internal ID of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG1BS FUNCTION(`func`) ECAGNRL FAILED TO LOCATE MCT TOKENLink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

In this message, func is the internal numeric code of the function that IOAGATE tried to perform.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG1CS FUNCTION(`func`) ECAGNRL OBTAINED ZERO MCT IN TOKENLink copied to clipboard

Explanation: IOAGATE detected a severe internal error. An IOAGATE task tried to run the ECAGNRL internal service routine.

In this message, func is the internal numeric code of the function that IOAGATE tried to perform.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG1DS CHANNEL (`channelId.` TCP) FAILED, NO COMM. TASK IS AVAILABLELink copied to clipboard

Explanation: A severe error has arisen in the IOAGATE TCP multiple connection channel channelId, and no active communication task is under the control of that channel.

The specified multiple connection channel (channelId) goes down. If it is the only channel configured in IOAGATE, IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG20I IOAGATE SHUTTING DOWNLink copied to clipboard

Explanation: This information message indicates that IOAGATE is shutting down, either as a result of a STOP command, or internal IOAGATE events.

IOAGATE shuts down.

Corrective Action: If the shutdown is not the result of an operator request, check the IOAGATE JES log, the DAIGLOG log and the DATRACE log for more information about the cause of the shutdown. If necessary, call your system programmer for assistance.

ECAG21S IOAGATE HAS FAILED (`rsn`) TO INITIALIZELink copied to clipboard

Explanation: IOAGATE failed to complete initialization. The reason code (rsn) is an internal ID that IOAGATE assigned to this specific problem.

IOAGATE shuts down.

Corrective Action: Check the IOAGATE JES log, the DAIGLOG log and the DATRACE log for more information about the cause of the failure. Try to restart the IOAGATE. If necessary, call your system programmer for assistance.

ECAG24W task (`taskId.type.channelId`) DETACHED BY FORCELink copied to clipboard

Explanation: IOAGATE forced a DETACH of an IOAGATE internal channel task. When this message is issued during IOAGATE termination, it indicates that an internal problem probably prevented the task from shutting down smoothly.

The message ECAG15I is issued after a smooth shutdown.

The variables in this message are:

task - the IOAGATE task
taskId - the internal identity of the task
type - the internal type of the task
channelId - the identity of the channel to which the task belongs

Termination continues.

Corrective Action: No action is required.

ECAG25I `modify_command`Link copied to clipboard

Explanation: This information message usually follows messages ECAG0BW and ECAG0CI, which indicate that an invalid modify command was issued. This message might appear more than once. Each occurrence displays a valid modify command.

Corrective Action: No action is required.

ECAG29E ECAGNRL FAILED. STD(`taskId.type`) FUNCTION(`func`) RC(`rsn`)Link copied to clipboard

Explanation: IOAGATE detected an internal error. The IOAGATE task tried to run the ECAGNRL internal service routine.

The variables in this message are:

taskId - the internal identity of the IOAGATE task that tried to run the service routine
type - the internal type of IOAGATE task that tried to run the service routine
func - the internal numeric code of the function that IOAGATE tried to perform
rsn - an internal identity that IOAGATE assigned to this specific problem

IOAGATE may shut down or continue, depending on the severity of the failure.

Corrective Action: If IOAGATE shuts down, contact BMC Customer Support.

ECAG2AE FILE OF KEYS IS UNAVAILABLE, ENCRYPTION DISABLEDLink copied to clipboard

Explanation: IOAGATE failed to allocate the file of encryption keys that is needed to initialize the encryption environment that is requested because ENCRYPT is set to YES in the ECAPARM configuration file.

The encryption environment is not established. Processing continues without encryption.

Corrective Action: Prepare a valid file of encryption keys of the type required for encryption to operate, both on IOAGATE and the workstation. For more information, see the description of the ENCRYPT parameter in the IOA chapter of the INCONTROL for z/OS Installation Guide.

ECAG2BE ENCRYPTION ROUTINE `routineName` IS UNAVAILABLE, ENCRIPTION DISABLEDLink copied to clipboard

Explanation: IOAGATE failed to load the encryption and decryption routine routineName when trying to initialize the encryption environment requested because ENCRYPT was set to YES in the ECAPARM configuration file.

The encryption environment is not established. Processing continues without encryption.

Corrective Action: Contact BMC Customer Support.

ECAG30E ECAPUT FAILED(`rsn:text`) CALLID (`module.call_typ.call_id.queue_typ`) TASK(`taskId.type.channelId`)Link copied to clipboard

Explanation: IOAGATE detected an internal error. The IOAGATE task tried to run the ECAPUT internal service routine.

The variables in this message are:

rsn - an internal identity that IOAGATE assigned to this specific problem
text - a description of the failure
module - the module that requested the service
call_typ - the internal call type Valid values are:
- SHORT - a short configuration of parameters was used in the call
- CONID - a conversation identity was specified in the call
- SOCKT - a TCP socket number was specified in the call
call_id - an internal call identity indicating the specific call inside the module
queue_typ - the type of internal queue for which this call was issued Valid values are:
- INQ - the input queue
- OUQ - the output queue
taskId - the internal identity of the task that requested the service
type - the internal type of the task that requested the service
channelId - the identity of the channel to which the task belongs

IOAGATE continues processing or shuts down, depending on the failure severity.

Corrective Action: If IOAGATE shuts down, contact BMC Customer Support.

ECAG31W IOAGATE(`monitorId`) WITH ECAPARM(`suffix`) ALREADY ACTIVE IN SYSTEM(`systemId`) LINDEX(`linkageIndex`)Link copied to clipboard

Explanation: Start of IOAGATE was attempted while IOAGATE was already active in the system. Two IOAGATEs with the same ECAPARM configuration file cannot run concurrently.

The variables in this message are:

monitorId - the started task (STC) name of the IOAGATE
suffix - a 1-character identity that specifies a unique ECAPARM configuration file used in this IOAGATE run
systemId - the unique identity of the MVS system on which the IOAGATE is running
linkageIndex - the MVS linkage index that enables cross-memory communication between IOAGATE and its partner application server address spaces

The newly started IOAGATE shuts down.

Corrective Action: If you must run a second IOAGATE in the same system concurrently, create and use an ECAPARM configuration file with a unique suffix.

ECAG32I IOAGATE(`monitorId`) WITH ECAPARM(`suffix`) RUNNING IN SYSTEM(`systemId`)Link copied to clipboard

Explanation: This information message displays some main system attributes of the active IOAGATE. The ECAG33I message follows this message with more main system attributes.

The variables in this message are:

monitorId - the started task (STC) name of the IOAGATE
suffix - a unique 1-character suffix that specifies the ECAPARM configuration file used in this IOAGATE run
systemId - the unique identity of the MVS system on which the IOAGATE is running

Corrective Action: No action is required.

ECAG33I LINDEX(`linkageIndex`) OBTAINED(`date`) QNAME(`qName`) RNAME(`rName`)Link copied to clipboard

Explanation: This message displays some main system attributes of the active IOAGATE. During initialization, IOAGATE retrieves an MVS linkage index to perform cross memory communication with its partner application server address spaces. The linkage index obtained from MVS is kept by IOAGATE in an MVS name/token pair.

The ECAG32I message precedes this message and displays different system attributes.

The variables in this message are:

linkageIndex - the MVS linkage index
date - the date the MVS linkage index was obtained
qName - the major name of the IOAGATE system resource
rName - the minor name of the IOAGATE system resource

Corrective Action: No action is required.

ECAG34I SERVER TASK S T A T U S JOB/CHANNEL/SIID STEP/JOBID/MODULE UTILIZATIONLink copied to clipboard

Explanation: This information message indicates that an F IOAGATE,STATUS command was issued. It is a header for subsequent ECAG35I messages.

The STATUS command can be issued manually by the operator, or automatically by IOAGATE, as a result of internal problems.

Corrective Action: No action is required.

ECAG35I `type taskId.addrSpaceId status channelId/siId step/jobId/mod utilization`Link copied to clipboard

Explanation: This information message specifies a server task of an application server address space that was issued.

The variables in this message are:

type - the server task type Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identity of the server task assigned by IOAGATE during initializationThe first character is a code that indicates the application. If this server task is busy handling a request for an alias application, this code indicates the alias. The next three digits form a unique sequential number of the task.
addrSpaceId - the internal identity of the application server address space to which the specified task belongs
status - This variable has a primary status field (START, READY, UP, DOWN, BUSY, WAIT, SUSPEND, FAILED, PENDING or X'hexvalue'), and may include a secondary status filed and additional information next to it. Each status field is described in the following table, in the order listed, with its secondary status fields and additional information that may overflow into fields that follow.

Primary Status	Description, Secondary Status, and Information
START	The server task is starting. It may also show Time in seconds to handle a request, or be in a primary status. Startup timed out - The server did not startup within the required time.
READY	The server task started and is ready to handle requests. It may also show recovered to indicate that the server recovered successfully.
UP	Server task started, for a task that does not use cross-memory communication with the IOAGATE address space.
DOWN	The server task is down. It may also show one of the following to indicate an automatic recovery status or the reason for the DOWN status: awaits recovery - Recovery was suspended for this server task because of internal temporary problems. recovery disabled - Recovery was disabled for this server task because the MAXRECOV parameter of the ECAPARM configuration file is set to zero. recovery timed out - The server failed to recover before maximum time elapsed. recovery failed of threshold - Recovery was blocked for this server task because the MAXRECOV parameter of the ECAPARM configuration file is at its maximum value. stopped - The DOWN status is the result of automatic recovery stopping. failed - The DOWN status is the result of the failure of automatic recovery. unknown - There is no known reason for the DOWN status. timer on - The timer for the DOWN status is running.
BUSY	The server task is busy handling a request. May also show the time in seconds to handle a request.
WAIT	The non-CM server task is down and cannot be recovered until its CM server is ready. This may also show: Time in seconds to handle a request or being in a WAIT state. CM to be ready - Non CM server is waiting for its CM server to be ready.
SUSPEND	The server task failed and cannot be recovered for the time being due to temporary internal problems. May also show the time in seconds to handle a request or be in a SUSPEND state.
FAILED	The server task failed. May also show: timer on timer is running.
PENDING	IOAGATE is waiting for this server task to send an internal acknowledgment to IOAGATE address space. May also show: ACK pending - A server is in PENDING status. Time in seconds to handle a request or be in a PENDING state.
X’ `hex_value`'	The status of a server task is unknown. May also show: unexpected status - Unknown status is represented by the combination of internal status flags. SST damaged - An internal control block that describes a server task is damaged.

channelId/ siId - This field shows more status field information, or specifies the channel and service request in two parts, channelId and siId, where
channelId is the ID of the channel linked to the indicated server task in the ECAPARM configuration file The first two characters specify the channel ID assigned in the ECAPARM configuration file. The rest of channelId is MULTI or DUAL, where MULTI is for a multiple connection (MC) model of a communication channel, and DUAL is for a dual connection (DC) model of a communication channel.
siId is a Service Instance ID (SIID) that specifies the service request being handled by a server taskThe value is displayed only when the status of a server task is BUSY.
step- the step name of a startup JCL procedure used to run the application server address spaceThis is displayed for a CM server task only.
jobId - the STC JOBID of the application server assigned to its address space by JES This is displayed for a CM server task only.
mod - the name of the program that implements the server task This is displayed for a CM server task only.
utilization - the percent of time the server task was busy handling the request during the last 40 seconds

Corrective Action: No action is required.

ECAG36W APPL.SERVER(`addrSpaceId`) CANNOT BE STOPPEDLink copied to clipboard

Explanation: An attempt to issue an F IOAGATE,STOPASID= addrSpaceId command failed. Either the specified address space ID is not ready or the server address space is already down.

In this message, addrSpaceId is the internal ID of the application server address space.

The modify command is rejected. Normal processing continues.

Corrective Action: Use the F IOAGATE,STATUS command to check the status of the server address space.

ECAG37I STOP FOR APPL.SERVER (`applServer.addrSpaceId`) INITIATEDLink copied to clipboard

Explanation: This information message indicates that an F IOAGATE,STOPASID=addrSpaceId command was performed successfully. A STOPASID command shuts down a specific application server address space.

The variables in this message are:

applServer - the full name of the application server
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAG38I IOAGATE(`monitorId`) WITH ECAPARM(`suffix`) EXCLUSIVELY OWNS HEARTBEAT RESOURCE Q(`qName`) R(`rName`)Link copied to clipboard

Explanation: This information message displays the name of the heartbeat resource of the running IOAGATE for a specific application server. When the application server is launched, IOAGATE issues a heartbeat ENQ request to acquire the specified resource exclusively as a heartbeat mechanism between the application server and IOAGATE. If the resource is available in the application server address space, it means that the IOAGATE stopped.

IOAGATE acquires a heartbeat resource for each application server it launches.

The variables in this message are:

monitorId - the STC name of the IOAGATE
suffix - a unique 1-character suffix identifying the ECAPARM configuration file that is used in this IOAGATE run
qName - the major name of the heartbeat resource
rName - the minor name of the heartbeat resourceAn application server ID acts as the minor name.

Corrective Action: No action is required.

ECAG39W SERVER TASK(`taskId`) CURRENTLY CANNOT BE STOPPEDLink copied to clipboard

Explanation: An attempt to issue an F IOAGATE,STOPTID=taskId command to stop the specified server task failed. The specified server task is either not ready, or is already down.

In this message, taskId is the internal ID of a server task.

The modify command is rejected. Normal processing continues.

Corrective Action: Use the F IOAGATE,STATUS command to check the status of the server task, and reissue the command later.

ECAG3AS FAILURE(`rsn`) TO CREATE A NEW NAME/TOKEN PAIR ON SYSTEM LEVELLink copied to clipboard

Explanation: IOAGATE failed to create a new MVS name or token pair in which to keep a linkage index. During initialization, IOAGATE obtains a linkage index to perform cross memory communication with its partner application server address spaces. IOAGATE keeps the linkage index in an MVS name or token pair.

Possible values of rsn are:

04 - duplicated name used
16 - user not authorized
28 - parameter LEVEL invalid
32 - parameter NAME invalid
36 - parameter PERSIST invalid
64 - unexpected error

IOAGATE shuts down.

Corrective Action: Call your system programmer for assistance.

ECAG3BW SERVER TASK(`taskId`) DOES NOT EXISTLink copied to clipboard

Explanation: An attempt to issue an F IOAGATE,STOPTID=taskId command to stop the specified server task failed, because the specified server task ID was incorrect. The variable taskId must be a correct internal ID of a server task.

The modify command is rejected. Normal processing continues.

Corrective Action: Use the F IOAGATE,STATUS command to identify the correct taskId, and reissue the command.

ECAG3CI PUTTER(`taskId.type`) submitting `controlMsg` for Server(`serverId`)Link copied to clipboard

Explanation: This information message indicates that a PUTTER task of IOAGATE submitted the internal control message controlMsg for the application server serverId.

Corrective Action: No action is required.

ECAG3DI GETTER(`taskId.type`) `controlMsg` confirmed for Server(`serverId`)Link copied to clipboard

Explanation: An IOAGATE GETTER task of IOAGATE received a confirmation for the internal control message controlMsg sent earlier by an IOAGATE PUTTER task. The confirmation control message controlMsg was sent by the application server serverId.

Corrective Action: No action is required.

ECAG3EW PUTTER(`taskId.type`) Obsolete SIB thrown away, SIID=`siId` APPL=`appl` SID=`serviceId` Time difference=`timeDiff`Link copied to clipboard

Explanation: An IOAGATE PUTTER task discovered an irrelevant SIB internal control block with the attributes identified in this message. The problematic control block was created before the specified PUTTER task was started.

The variables in this message are:

taskId - the internal ID of this PUTTER task
type - the type of this PUTTER task
siId - the Service Instance ID
appl - the application code
serviceId - the identity of the Service
timeDiff - The time difference between the time when the problematic SIB block was created and the time when the PUTTER task started.

The SIB control block is destroyed. Normal processing continues.

Corrective Action: No action is required.

ECAG3FW FAILURE TO UNLOCK CHAIN OF SIBs:ALREADY UNLOCKED UNLOCKER (`taskId.type.callId`):`module`Link copied to clipboard

Explanation: This warning message is issued if the chain of SIB control blocks is already unlocked when attempting to unlock it.

Corrective Action: No action is required.

ECAG3GS FAILURE TO UNLOCK CHAIN OF SIBs:LOCKED BY (`taskId`) UNLOCKER (`taskId.type.callId`):`module`Link copied to clipboard

Explanation: This severe error message is issued if the chain of SIB control blocks has been locked by some other task, indicated by LOCKED BY (taskId) when attempting to unlock it. In this case, the unrecoverable error indicator is set to ON, SVCDUMP is initiated, and IOAGATE goes down.

Corrective Action: No action is required.

ECAG3HI IOAGATE Token: Name=`tokenName` LX=`index` Obtained=`date` System=`systemName`Link copied to clipboard

Explanation: This information message indicates that the F IOAGATE,SHOWTOKEN modify command was issued in the IOAGATE address space to display the MVS token of the current IOAGATE.

The variables in this message are:

tokenName - the name of the MVS token of the current IOAGATE
index - the Linkage Index used by this IOAGATE to establish cross-memory communication
date - the date when the Linkage Index of IOAGATE was obtained from MVS
systemName - the name of the MVS system on which the current IOAGATE is running

Corrective Action: No action is required.

ECAG3IW LAST READY CS SUBTASK IN (`xxxx.yyyy`) ASSIGNED. OCCURED (`nnn`) TIMES.Link copied to clipboard

Explanation: The message is issued when IOAGATE assigns a transaction to the last ready CS server subtask in an application server address space that serves Control-D/Page ON Demand requests. This message will not be issued more than once per minute in order not to flood the console with such messages.

The variables in this message are:

xxxx is the procedure name of the application server.
yyyy is the qualifier (after the dot) of the specific application server address space. The qualifier allows distinguishing between the address spaces when multiple application server address spaces are started.
nnn is the number of times the last ready CS has been assigned since the last time message ECAG3IW has been issued, including the current occurrence for which this ECAG3IW is issued.

For example, if the following messages appear:

10:05:00 ECAG3IW ...OCCURED (001) TIMES.

10:06:00 ECAG3IW ...OCCURED (005) TIMES.

This means that at 10:05:00 the last ready CS has been assigned and that in the following minute the last ready CS has been assigned 5 times.

When the last ready CS is assigned, it means that any new request must wait until a busy CS in the same address space finishes handling its request and becomes ready.

Corrective Action: In general, BMC recommends that you define enough CS subtasks and application server address spaces so that this situation rarely, if ever, occurs.

ECAG40W APPL.SERVER (`applServer.addrSpaceId`) CANNOT BE STARTED, CHANNEL(`channelId`) DISABLEDLink copied to clipboard

Explanation: The specified application server cannot be started. During initialization, IOAGATE detected errors in the indicated CHANNEL definition and disabled it. As a result, the application server that referenced this channel became unusable.

Variables in this message are:

applServer - the full name of the application server
addrSpaceId - the internal identity of an application server address space
channelId - the channel identity referenced by the application server

Corrective Action: Check the IOAGATE DAIGLOG log and the DATRACE log for more information. Try to correct the CHANNEL definition, and restart IOAGATE.

ECAG41E SERVER TASK (`applServer.type.taskId.addrSpaceId`) FAILED WHEN HANDLING A REQUEST, USER(`userId`) SIID(`serviceInstanceId`)Link copied to clipboard

Explanation: IOAGATE detected a server task failure. The server task was handling the specified user request when IOAGATE detected the failure.

Attributes of the failed server are:

applServer - the name of the application server
type - the server task type. Valid values are:
- CM - the manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space to which the specified server task belongs
userId - the identity of the user whose request was in process
serviceInstanceId - the service instance ID (SIID) that determines the service request being handled by the server task

IOAGATE does the following:

clears resources allocated by cross memory communication with the failed server task
initiates automatic recovery for the failed server task, if the option was not blocked by MAXRECOV parameter in the ECAPARM configuration file
continues communication with other server tasks.

Corrective Action: Check the error messages of the application server address space to determine why the server task terminated. Fix the problem and try again.

ECAG43W AN ATTEMPT TO CREATE A MESSAGE FOR `appl` REMOTE APPLICATION FAILED `rsn`Link copied to clipboard

Explanation: IOAGATE failed to create a notification message for a remote IOAGATE that supports the application appl. The reason for the failure is identified by the variable rsn.

This message is issued only when the IOAGATE is configured for IOAGATE-to-IOAGATE communication.

Possible values for rsn are:

No PDTs are available
The proper PDT is not available
The PLT table is not available
No PLTs are available
The proper PLT is not available

Corrective Action: Contact BMC Customer Support.

ECAG46W APPL.SERVER (`applServer.type.taskId.addrSpaceId. channelId`) ALREADY ACTIVELink copied to clipboard

Explanation: An F IOAGATE,STARTASID= addrSpaceId command failed. Either the specified ID is invalid, or this server address space is already up.

The variables in this message are:

applServer - the name of the application server
type - the CM server task type
taskId- the internal identity of this server task
addrSpaceId - the internal identity of this application server address space
channelId - the identity of the channel to which the specified application server is linked

The modify command is rejected.

Corrective Action: Correct the application server address space ID, and reissue the command.

ECAG47I START FOR APPLICATION SERVER(`applServer.addrSpaceId`) INITIATEDLink copied to clipboard

Explanation: This information message indicates that an F IOAGATE,STARTASID=addrSpaceId command was performed successfully. The STARTASID command starts a specific application server address space.

The variables in this message are:

applServer - the name of the application server
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAG49I CHANNEL(`channelId`.SNA) USER(`userId`) LOGGED ON, CONVID(`conversation_id`) APPLID(`applId`)Link copied to clipboard

Explanation: This information message indicates that the specified user successfully logged on to IOAGATE over a multiple connection (MC) SNA channel.

The variables in this message are:

channelId - the identity of the channel over which the specified user logged on to IOAGATE
userId- the identity of the user whose logon request was performed
conversation_id- VTAM LU 6.2 (APPC) conversation identity
applId - VTAM LU 6.2 (APPC) application identity of the partner

Corrective Action: No action is required.

ECAG4AI STOP FOR SERVER TASK (`applServer.type.taskId.addrSpaceId`) INITIATEDLink copied to clipboard

Explanation: This information message indicates that an F IOAGATE,STOPASID=addrSpaceId command was issued and performed successfully. The STOPASID command shuts down a specific application server address space.

The variables in this message are:

applServer - the name of the application server shut down
type - the CS server task type
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space

Corrective Action: No action is required.

ECAG4BE SERVER TASK(`applServer.type.taskId.addrSpaceId`) FAILED WHEN BEING STARTEDLink copied to clipboard

Explanation: IOAGATE detected a server task failure before the task completed its startup.

The variables in this message are:

applServer - the full name of the application server
type - the server task type Valid values are:
- CD - detector server
- CS - application server
- CU - updater server

taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space to which the failed server task is assigned

Automatic recovery is initiated for the failed server task if the option was not blocked by the MAXRECOV parameter in the ECAPARM configuration file, and processing continues.

Corrective Action: Check the error messages of the application server address space to determine why the server task failed, try to fix the problem, and try again.

ECAG4CE APPL.SERVER (`applServer.type.task-id.addrSpaceId. channelId`) FAILED WHEN BEING STARTEDLink copied to clipboard

Explanation: IOAGATE detected an application server failure before the server completed its startup.

The variables in this message are:

applServer - the name of the application server
type - the CM server task type
taskId- the internal identity of this application server task
addrSpaceId - the internal identity of the application server address space
channelId - the identity of the channel to which the application server is linked

Automatic recovery is initiated for the failed application server if the option was not blocked by the MAXRECOV parameter in the ECAPARM configuration file. Processing continues.

Corrective Action: Check the error messages of the application server address space to determine why the application server failed, try to fix the problem, and restart IOAGATE.

ECAG4DE SERVER TASK (`applServerName.type.taskId.addrSpaceId`) FAILEDLink copied to clipboard

Explanation: IOAGATE detected a server task failure.

The variables in this message are:

applServer - the name of the application server
type - the server task typeValid values are:
- CD - detector server
- CS - application server
- CU - updater server
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space to which the failed server task is assigned

IOAGATE does the following:

clears resources allocated for cross memory communication with the failed server task
initiates automatic recovery for the failed server task, if the option was not blocked by MAXRECOV parameter in the ECAPARM configuration file
continues communication with other server tasks.

Corrective Action: Check the error messages of the application server address space to determine why the server task failed, try to fix the problem, and restart IOAGATE.

ECAG4GI SERVER TASK (`applServerName.type.taskId.addrSpaceId`) HAS BEEN STOPPED BY OPERATORLink copied to clipboard

Explanation: This information message indicates that the operator issued the command F IOAGATE,STOPTID=taskId, and that command was successfully performed. The STOPTID command shuts down a specific server task.

The variables in this message are:

applServerName - the name of the application supported by the server that was stopped
type - the internal type of the server task that was stopped
taskId - the internal identity of this server task
addrSpaceId - the internal identity of the application server address space to which this server task is assigned

Corrective Action: No action is required.

ECAG4HW APPL.SERVER(`addrSpaceId`) DOES NOT EXISTLink copied to clipboard

Explanation: An F IOAGATE,STARTASID=addrSpaceId command was issued by the operator, and failed. The STARTASID command starts a specific application server address space that either was shut down or failed. The specified address space ID (addrSpaceId) is not a valid address space ID.

In this message, addrSpaceId is the invalid address space ID that was specified.

Corrective Action: Correct the address space ID and reissue the command.

ECAG4IW APPL.SERVER (`applServerName.type.taskId.addrSpaceId.channelId/jobId`) WENT DOWN BECAUSE OPERATOR STOPPED SERVER TASK(`taskId`)Link copied to clipboard

Explanation: The specified application server address space went down because an operator stopped the single or last active CS server task running under the control of the identified application server.

The variables in this message are:

applServer - name of the application supported by the server that has gone down
type - the internal type of the server task that has gone down
taskId - the internal identity of the server task that has gone down
addrSpaceId - the internal identity of the application server address space to which the server task that has gone down is assigned
channelId - the identity of the channel to which the identified application server is linked
jobId - STC JOBID of the application server assigned to its address space by JES

Corrective Action: No action is required.

ECAG4JI TERMINATION FOR SERVER TASK(`applServer.type.taskId.addrSpaceId`) INITIATEDLink copied to clipboard

Explanation: An F IOAGATE, CTID= taskId CANCEL TASK modify command has been issued by the user.

The variables in this message are:

applServer - the name of the application supported by the server to which the modify command was issued
type - the internal type of the server task which is to be terminated
taskId - the internal identity of the server task which is to be terminated
addrSpaceId - the internal identity of the application server address space to which the task taskId is assigned

IOAGATE issues an internal control message that causes the application server address space addrSpaceId to terminate the server task taskId. Normal processing continues.

Corrective Action: No action is required.

ECAG4KW SERVER TASK(`applServer.type.taskId.addrSpaceId`) HAS BEEN TERMINATED BY IOAGATE, USER(`userId`) SIID(`serviceInstanceId`)Link copied to clipboard

Explanation: The specified server task has been terminated by IOAGATE.

The variables in this message are:

applServer - the name of the application supported by the server on which the task was terminated
type - the internal type of the server task that was terminated
taskId - the internal identity of the server task that was terminated
addrSpaceId - the internal identity of the application server address space to which the terminated server task taskId is assigned

Corrective Action: Analyze the IOAGATE outputs to identify the reason of the termination. If the problem persists, contact BMC Customer Support.

ECAG4LE APPL.SERVER (`applServerName.addrSpaceId.proc.stcId-channelId/jobId`) FAILEDLink copied to clipboard

Explanation: The specified application server address space failed.

The variables in this message are:

applServer - name of the application supported by the server that has gone down
addrSpaceId - the internal identity of the application server address space to which the server task that has gone down is assigned
proc - the name of the procedure of the application server address space
stcId - the name of the JCL procedure used to start the application server address space
channelId - the identity of the channel to which the identified application server is linked
jobId - STC JOBID of the application server assigned to its address space by JES

Normal processing continues, and, if recovery is not blocked for this application server, the IOAGATE tries to recover the server.

Corrective Action: No action is required.

ECAG50I CHANNEL(`channelId.`SNA) DEALLOCATE RECEIVED FROM PARTNER, APPLID(`applId`) CONVID(`conversation_id`)Link copied to clipboard

Explanation: This information message indicates that a DEALLOCATE APPC command was received from a client or partner IOAGATE for the specified conversation ID.

The variables in this message are:

channelId - the identity of the channel over which the conversation that was deallocated was established
applId - VTAM LU 6.2 (APPC) application ID of the IOAGATE
conversation_id - VTAM LU 6.2 (APPC) internal conversation identity

Corrective Action: No action is required.

ECAG55W CHANNEL(`channelId.protocol`) TASK(`taskId.type`) IS STARTING UP ALTHOUGH NO APPL.SERVER HAS COME UP YETLink copied to clipboard

Explanation: A communication channel has waited for at least one application server linked to the channelId channel to become ready, but none has come up.

The variables in this message are:

channelId - the identity of the channel to which the problematic application server is linked
protocol - the communication protocol used by the current channel. Valid values are:
- TCP - TCP/IP
- SNA - SNA

taskId - the internal identity of this channel task
type - the internal type of this channel

IOAGATE discontinues waiting until at least one application server linked to the channelId channel is ready. The channelId channel continues initializing.

Corrective Action: This warning message may, but does not necessarily, indicate a real problem on the application server. Examine the JES logs of all application servers linked to the channelId channel and try to find the cause for the failure of the application server to start in time.

ECAG56I REJECTED:SID=`serviceId` SIID=`serviceInstanceId` SEQ= `seqNumber` APPLIC=`appl` ASID=`addressSpaceId` LAST=`turn_around` C/E=`compression/encryption` TYPE=`t1 /t2 /t3`. USER=`userId`Link copied to clipboard

Explanation: This message follows the messages ECAC60E, ECAC61E, ECAC62E, ECAC64E, ECAC65E, ECAC66E, ECAC67E, ECAC68E, ECAC6CE, ECAC6DE, ECAC6EE, ECAC6FE, ECAC6GE, ECAC6HE, ECAC6IE, ECAC6ME, ECAG58E, and provides details of the rejected transaction.

The variables in the message are:

serviceId - the type of the transaction that was rejected
serviceInstanceId - the service instance identity (SIID) of the transaction rejected by IOAGATE
seqNumber - the sequential number of the rejected message in a given direction within the same transactionThese numbers start from 000001.
appl - the short code of the application to which the rejected transaction was assigned
addressSpaceId - the internal address space identity of the application server to which the rejected transaction was assigned
turn_around - internal indication of the nature of the transaction. Valid values are:
- T - Turn AroundThis was the last message in this direction and a response was required
- L - LastThe current message was the last in the service, meaning, the end of transaction.
- ' ' (Blank) - the current message was not the last in the service, and more messages are expected
compression - whether compression is in use. Valid values are:
- A (Accept) - Used only by D applications, to indicate that the D client will accept compressed data from IOAGATE.
- D (Compressed) - Used only by D applications, to indicate that this message contains compressed data.
- Y - Compression is in use.
- I (Ignore) - The compression indication field is used differently.
- ' ' (Blank) - No compression is in use.
encryption - whether encryption is in use. Valid values are:
- Y (Yes) - DES or 3DES encryption is in use.
- ' ' (Blank - No encryption is in use.
t1 - whether the message is regular or extended. Valid values are:
- R (Regular) - The message is regular.
- E (Extended) - The message is extended.
t2 - indicates the message type. Valid values are:
- B - Big message
- C - Confirmation
- D - Data
- E - Error
- F - End of download or upload
- R - Request
- S - Start of download or upload
- ( - Start of file transfer
- ) - End of file transfer
t3 - indicates the record type. Valid values are:
- ! - Do not Process the message indication
- A - Handshake CONNECT message
- C - Handshake CONFIRM message
- R - Handshake REJECT message
- I - Handshake Information message
- A - Active job file record
- A - Attach request
- B - Short database update
- C - Condition
- C - Communication update message
- D - Cancel request
- F - Modify server request
- F - Force job
- G - Synchronization record
- H - Control resource
- I - Initialization
- J - Edit JCL
- L - Log
- M - Internal IOAGATE message
- N - New job
- O - Order job
- Q - Quantitative resource
- R - Control resource
- S - Statistics record
- T - Alert
- V - View sysout file
- Z - WS Synchronization record
userId - the identity of the user associated with this transaction

Corrective Action: No action is required.

ECAG57W CHANNEL(`channelId.protocol`) TASK(`taskId.type`) IS STARTING UP ALTHOUGH APPL.SERVER(`applServerId -addrSpaceId`) HAS NOT COME UP YETLink copied to clipboard

Explanation: The channelId communication channel has waited for the applServer application server that is linked to become ready, but applServer has not come up.

The variables in this message are:

channelId - the identity of the channel to which the problematic application server is linked
protocol - the communication protocol used by the current channel. Valid values are:
- TCP - TCP/IP
- SNA - SNA
taskId - the internal identity of this channel task
type - the internal type of the channelId channel
applServerId - the internal identity of the application server linked to the channelId channel
addrSpaceId - the internal identity of the application server address space linked to the channelId channel

IOAGATE discontinues waiting until at the application server linked to the channelId channel is ready. The channelId channel continues initializing.

Corrective Action: This warning message may, but does not necessarily, indicate a real problem on the application server. Examine the JES log of the applicId application server and try to find out why the application server failed to start in time.

ECAG58E CHANNEL(`channelId.protocol`) TASK(`taskId.type`) TIMEOUT OCCURRED WHILE WAITING FOR A MESSAGE FROM PARTNERLink copied to clipboard

Explanation: This information message indicates that a request was canceled because an expected message did not arrive within a defined time-out interval.

The variables in this message are:

channelId - the identity of the channel in which the specified time-out occurred
protocol - the communication protocol used by the current channel. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal ID of this channel task
type - the internal type of this channel

If the expected message is not critical, IOAGATE continues executing. If the expected message is critical, the corresponding SNA channel goes down.

Corrective Action: If the problem persists, call BMC Customer Support for assistance.

ECAG59W CHANNEL(`channelId.protocol`) TASK(`taskId.type`) "DO NOT PROCESS" INDICATION RECEIVED, MESSAGE DISCARDEDLink copied to clipboard

Explanation: This information message indicates that the specified channel received a request with a "Do not process (!)" indication.

The variables in this message are:

channelId - the identity of the channel in which the specified event occurred
protocol - the communication protocol used by the current channel. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal ID of this channel task
type - the internal type of this channel

Corrective Action: No action is required.

ECAG5AI DISCARDED: `msg`Link copied to clipboard

Explanation: This message follows ECAG59W or ECAG5BW and displays the discarded transaction.

Corrective Action: No action is required.

ECAG5BW CHANNEL(`channelId.protocol`) TASK(`taskId.type`) HANDSHAKE MESSAGE REJECTED: THERE IS NO MAP SPECIFIEDLink copied to clipboard

Explanation: This message warns that the specified channel received a handshake used by IOAGATE-to-IOAGATE communication, but the local IOAGATE is not configured to be a partner IOAGATE.

The variables in this message are:

channelId - the identity of the channel that detected the event
protocol - the communication protocol used by the channe. Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
taskId - the internal identity of the channel task that detected the event
type - the internal type of the channel task that detected the event

Corrective Action: No action is required.

ECAG5CI CHANNEL(`channelId.protocol`) `processed` FOR INCOMING CONNECTIONS, APPLICATION(`applicId`)Link copied to clipboard

Explanation: This information message indicates that an F IOAGATE,<cmd_modify> command was successfully performed.

The variables in this message are:

channelId - the identity of the channel against which the modify command was performed
protocol - the communication protocol used by channelId. Valid values are:
- TCP - TCP/IP
- SNA - SNA
processed - the type of action. Valid values are:
- CLOSED - channelId has been successfully closed for incoming connections
- OPENED - channelId has been successfully opened for incoming connections
applicId - the identity of the application that channelId serves

Corrective Action: No action is required.

ECAG5DI IOAGATE WILL BE SHUT DOWN AS SOON AS ALL CLIENTS HAVE DISCONNECTEDLink copied to clipboard

Explanation: This information message indicates that an F IOAGATE,CLOSE=ALL,SHUT modify command was successfully performed.

Processing continues. IOAGATE will be shut down as soon as all active clients have been disconnected.

Corrective Action: No action is required.

ECAG5EW SHUT SPECIFICATION REJECTED, THERE ARE OPEN CHANNELSLink copied to clipboard

Explanation: An F IOAGATE,CLOSE=channelId,SHUT modify command was issued but the SHUT subcommand was rejected because a channel was found to be open and active.

Corrective Action: If required, close the open channels and re-issue the F IOAGATE,CLOSE=ALL,SHUT modify command.

ECAG5FW MODIFY(OPEN=ALL) IGNORED, ALL CHANNELS OPENLink copied to clipboard

Explanation: An F IOAGATE,OPEN=ALL modify command was issued, but was rejected because all active channels are already open.

Corrective Action: No action is required.

ECAG5GI SHUT COMMAND ISSUED EARLIER BY "CLOSE,SHUT" HAS BEEN CANCELEDLink copied to clipboard

Explanation: An F IOAGATE,OPEN=ALL/ channelId modify command was issued, but the CLOSE=ALL,SHUT command had already been issued.

The action that was ordered by the SHUT subcommand has been canceled.

Corrective Action: No action is required.

ECAG5HI IOAGATE GOES DOWN DUE TO COMMAND "CLOSE=.,SHUT" ISSUED EARLIERLink copied to clipboard

Explanation: An F IOAGATE,OPEN=ALL,SHUT modify command was issued some time ago, and all active clients have been disconnected.

IOAGATE goes down.

Corrective Action: No action is required.

ECAG5II CHANNEL(`channelId.protocol`) TASK(`taskId.type`) INCOMING CONNECTION REJECTED: CHANNEL CLOSEDLink copied to clipboard

Explanation: This information message indicates that an F IOAGATE,CLOSE=ALL/ channelId modify command was issued against the channelId channel, and this channel was closed.

The variables in this message are:

channelId - the identity of the channel that was closed by the modify command
protocol - the communication protocol used by channelId. Valid values are:
- TCP - TCP/IP
- SNA - SNA
taskId - the internal identity of the channel task that detected the connection attempt
type - the internal type of the taskId channel task

The attempt to connect to the channelId channel is rejected. Normal processing continues.

Corrective Action: No action is required.

ECAG5TE LE PREINITIALIZATION FAILED, MOD=`modname`,FUNC=`function`,RC=`return_code`Link copied to clipboard

Explanation: Language Environment Preinitialization services is used to create a persistent C environment for INCONTROL C programs. An error occurred while using this facility. The subtask involved will be abended with code U0186.

The variables are defined as follows:

modname - name of the program that issued the call
function – one of the following:
- INIT – environment initialization
- CSUB,TRM-CSUB – calling a C program
- TERM – terminating the environment
return_code (selection):
- rc= 8: failure to load a C program. Program might be missing from STEPLIB.
- rc=12: insufficient storage for the preinitialization environment
- rc=16: An active environment already exists
- rc=32: Abend occurred in preinitialization services

Corrective Action:

For INIT return codes 8 or 12, check your environment. In other cases, notify BMC Customer Support.
For a Control-D PC transfer, a previous error (such as, an error reading the file during the transfer or an abend in the transmission program) might have caused this error. For immediate transfers, exit and enter the online session before trying more transfers.
For IOAGATE or Control-M monitor, if they shut down, restart them.

ECAG5UE TCP/IP STACK `stack` UNAVAILABLE, ERRNO=`errno`. CHANNEL `channelId` DISABLED.Link copied to clipboard

Explanation: An IOAGATE channel was defined with ESTACK=stack in ECAPARMx. The z/OS system has dual stack mode TCP/IP, but the specified stack is not running.

Corrective Action: Either bring up the started task specified in ESTACK parameter, or remove the ESTACK parameter. Then recycle IOAGATE.

ECAG61S CHANNEL`(channelId.`SNA) IOAGATE INTERNAL COMMUNICATION ERROR, SEND INDICATION NOT RECEIVEDLink copied to clipboard

Explanation: IOAGATE discovered a protocol violation. After the sending side of a dual connection (DC) SNA channel allocates a conversation with its partner or client, the partner application should reverse the conversation direction. Due to a protocol violation, the conversation direction was not reversed. This message can occur only for dual connection (DC) SNA channels.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAG62I CHANNEL(`channelId.`TCP) COMTASK(`taskId`) SOCKET(`socket`) USER(`userId`) LOGGED ON FROM `ipAdd`Link copied to clipboard

Explanation: This information message indicates that a user successfully logged on to IOAGATE over a multiple connection (MC) TCP channel.

The variables in this message are:

channelId - the identity of the channel on which this user logged on to IOAGATE
taskId - the identity of the TCP/IP communication task to which this user was assigned
socket - TCP/IP socket number of this connection
userId - the identity of the user who logged on
ipAdd - IP address of the user that logged on

Corrective Action: No action is required.

ECAG63I CHANNEL(`channelId`.SNA) DEALLOCATE SENT TO PARTNER, APPLID(`applId`) LU(`luName`)Link copied to clipboard

Explanation: This information message indicates that a DEALLOCATE APPC command was sent to a partner or client.

Conversation parameters:

channelId - the identity of the channel this partner or client was using
applId - VTAM LU 6.2 (APPC) application ID of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client

Corrective Action: No action is required.

ECAG64I CHANNEL(`channelId.`SNA) CONVERSATION STARTED WITH PARTNER APPLID(`applId`) LU(`luName`) MODE(`mode`)Link copied to clipboard

Explanation: This information message indicates that a conversation started between IOAGATE and its partner or client. The specified partner or client started a conversation with IOAGATE. The message can be issued for a dual connection (DC) SNA channel only.

Conversation parameters are:

channelId - the identity of the channel on which the specified conversation started
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client
mode - the mode in use. Valid values are:
- SENDER - the sender mode of the DC SNA channel conversation
- RECEIVER - the receiver mode of the DC SNA channel conversation

Corrective Action: No action is required.

ECAG65I CHANNEL(`channelId.`SNA) DEALLOCATE RECEIVED FROM PARTNER APPLID(`applId`) LU(`luName`)Link copied to clipboard

Explanation: This information message indicates that a DEALLOCATE APPC command was received from a partner or client. The partner deallocated the conversation with IOAGATE.

Conversation parameters are:

channelId - the identity of the channel over which the specified conversation was occurring when it was terminated
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client

Corrective Action: No action is required.

ECAG66W CHANNEL(`channelId.`SNA) TPEND EXIT INVOKED, APPLID(`applId`) LU(`luName`) REASON(`rsn`)Link copied to clipboard

Explanation: The VTAM operator broke the connection between the partner or client and the indicated SNA channel. This message indicates that the TPEND exit was invoked.

Attributes of the connection are:

channelId - the identity of the SNA channel that was connected to the partner or client
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client
rsn - code indicating what happenedFor the explanation for each value of rsn, see the VTAM Programming for LU 6.2 Manual

Processing continues, and IOAGATE tries to recycle the specified SNA channel.

Corrective Action: For an explanation of TPEND reason codes, see the VTAM Programming for LU 6.2 Manual. Call your system programmer for assistance.

ECAG67W CHANNEL(`channelId.`SNA) ATTN LOSS EXIT INVOKED, APPLID(`applId`) LU(`luName`)Link copied to clipboard

Explanation: The partner or client and IOAGATE were disconnected. This message precedes the message ECAG68I, which contains VTAM diagnostic information.

The attributes of the broken connection are:

channelId - the identity of the channel on which the disconnection occurred
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE
luName - VTAM LU 6.2 (APPC) LU name of the partner or client

IOAGATE attempts to recycle the indicated SNA channel.

Corrective Action: Read the message ECAG68I to identify and fix the problem, if possible. If you cannot resolve the problem, call your system programmer for assistance.

ECAG68I RPL6SNSI(`rpl6sns_code`) RPL6RC(`rpl6rsn_code`) RPL6DETP(`rpl6detp_code`) RPLSONCD(`rplsoncd_code`)Link copied to clipboard

Explanation: This information message displays VTAM diagnostic information for a network systems programmer. It follows message ECAG67W, which announces disconnection of IOAGATE from its partner or client.

RPL6 fields that are documented in the VTAM Programming for LU 6.2 are:

rpl6sns_code - sense code returned by VTAM
rpl6rsn_code - RPL6 reason code returned by VTAM
rpl6detp_code - DETP reason code returned by VTAM
rplsoncd_code - SONCD UNBIND type code returned by VTAM

Corrective Action: Try to determine the cause of the problem, and correct it. If you cannot resolve the problem, call your system programmer for assistance.

ECAG69I CHANNEL(`channelId`.SNA) READY FOR COMMUNICATIONS, APPLID(`applId`)Link copied to clipboard

Explanation: This information message indicates that the SNA channel of the IOAGATE is waiting for an ALLOCATE request from a partner or client. This message is issued during a multiple connection (MC) SNA channel startup.

Attributes of the SNA channel are:

channelId - the identity of the channel that is ready for communications
applId - VTAM LU 6.2 (APPC) application ID of the IOAGATE

Corrective Action: No action is required.

ECAG70I PROBABLE CAUSE: TEMPORARY STORAGE SHORTAGELink copied to clipboard

Explanation: This information message indicates that the probable reason for the failure of a VTAM request is a temporary shortage of main storage for VTAM. This message follows a message that announces failure of a VTAM request, such as an APPC command, or an OPEN or CLOSE ACB command, and precedes message ECAG81I, ECAG84I, or ECAG85I, which indicates the action that will be taken by IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: If the problem persists, consider tuning the VTAM buffer. Call your system programmer for assistance.

ECAG71I PROBABLE CAUSE: VTAM IS HALTINGLink copied to clipboard

Explanation: This information message indicates that VTAM is probably going down. This message follows a message that announces failure of a VTAM request, such as an APPC command, or an OPEN or CLOSE ACB command. It precedes message ECAG81I, ECAG84I, or ECAG85I, which indicates the action that will be taken by IOAGATE. This message can be issued for an SNA channel only.

SNA channel fails. Processing continues.

Corrective Action: If the problem persists, call your system programmer for assistance.

ECAG72I PROBABLE CAUSE: APPLID NOT DEFINEDLink copied to clipboard

Explanation: This information message indicates that the probable reason for the failure of a VTAM OPEN ACB command is that VTAM does not recognize the VTAM LU 6.2 (APPC) application ID specified in the OPEN ACB command. This message follows message ECAG91W, which announces the command failure, and precedes message ECAG83E, which specifies the action that will be taken by IOAGATE. This message can be issued for an SNA channel only.

Possible causes are:

The Major node where APPLID is defined is not active.
The APPLID defined to VTAM does not match the APPLID or APPLIDS defined to IOAGATE in the ECAPARM SNA channel declaration.

Processing continues, but the SNA channel fails.

Corrective Action: Activate the Major node, or correct the APPLID or APPLIDS specifications in the SNA channel declaration in the ECAPARM configuration file. If the problem persists, call your system programmer for assistance.

ECAG73I PROBABLE CAUSE: APPLID DEFINED IMPROPERLYLink copied to clipboard

Explanation: This information message indicates that the probable reason for failure of a VTAM OPEN ACB command is that the VTAM LU 6.2 (APPC) application ID specified in the OPEN ACB command is probably not a valid application definition, although it is known to VTAM. This could happen, for instance, if the APPLID or APPLIDS defined to IOAGATE in the ECAPARM configuration file is incorrect, but happens to match the name of another resource known to VTAM.

This message follows a message that announces failure of the VTAM OPEN ACB command, and precedes message ECAG83E, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Correct the APPLID or APPLIDS specifications in the SNA channel declaration in the ECAPARM configuration file. If the problem persists, call your system programmer for assistance.

ECAG74I PROBABLE CAUSE: ACB HAS ALREADY BEEN OPENEDLink copied to clipboard

Explanation: This information message indicates that the probable reason for the failure of a VTAM OPEN ACB command is that the VTAM LU 6.2 (APPC) application ID specified in the OPEN ACB command is already open and in use by another application.

Possible causes are:

Another IOAGATE with the same APPLID is already up.
The APPLID defined to the IOAGATE in the ECAPARM configuration file is incorrect, but matches the name of another resource known to VTAM.

This message precedes message ECAG85I, which specifies the action that will be taken by IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Correct the APPLID specifications in the SNA declaration in the ECAPARM configuration file, or shut down the address space that uses the same APPLID. If the problem persists, call your system programmer for assistance.

ECAG75I PROBABLE CAUSE: APPLID INACTIVATEDLink copied to clipboard

Explanation: This information message indicates that the probable cause of the failure of a VTAM OPEN ACB command is that the VTAM LU 6.2 (APPC) application ID is inactive. This message precedes message ECAG81I, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Activate the application defined by the APPLID. If the problem persists, call your system programmer for assistance.

ECAG76I PROBABLE CAUSE: VTAM IS NOT ACTIVELink copied to clipboard

Explanation: This information message indicates that the probable cause of the failure of a VTAM request, such as an APPC command, or an OPEN or CLOSE ACB command, is that VTAM is down. This message precedes message ECAG85I, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Call your network systems programmer for assistance.

ECAG77I PROBABLE CAUSE: PARTNER DISCONNECTEDLink copied to clipboard

Explanation: This information message indicates that the probable cause of the failure of a VTAM APPC command is that the conversation was lost due to disconnection from the partner or client. This message follows message ECAG90E, which announces that an APPC command failed, and precedes message ECAG81I, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Check the message issued by the partner or client and proceed accordingly. If the problem persists, call your system programmer for assistance.

ECAG78I PROBABLE CAUSE: CONNECTION LOSTLink copied to clipboard

Explanation: This information message indicates that the probable cause of failure of a VTAM APPC command is a communication disruption. This may be due to a resource failure on the route to or from the partner or client. This message precedes message ECAG81I, which specifies the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Try to determine the cause of the communication disruption and correct it. If the problem persists, call your system programmer for assistance.

ECAG79I PROBABLE CAUSE: SESSION TERMINATEDLink copied to clipboard

Explanation: This information message indicates that the probable cause of failure of a VTAM APPC command is the termination of a VTAM session, possibly because of a protocol error. This message precedes message ECAG81I, which indicates the action that will be taken by the IOAGATE. This message can be issued for an SNA channel only.

Processing continues, but the SNA channel fails.

Corrective Action: Call your system programmer for assistance. If the problem persists, contact BMC Customer Support.

ECAG81I CHANNEL(`channelId`.SNA) RE-START COMMUNICATION WILL BE ATTEMPTEDLink copied to clipboard

Explanation: This information message indicates that an attempt will be made to restart the specified SNA channel. Restarting an SNA channel involves preparing to receive a conversation allocation request from the partner or client LU, including opening the ACB if it is not already open. This message follows other messages that provide details about an error that occurred.

In this message, channelId is the identity of the problematic SNA channel.

IOAGATE attempts to restart the indicated channel.

Corrective Action: No action is required.

ECAG82I CHANNEL(`channelId`.SNA) RE-CYCLE COMMUNICATION WILL BE ATTEMPTEDLink copied to clipboard

Explanation: This information message indicates that an attempt will be made to recycle the SNA channel. Communication is recycled when VTAM is going down, or when the retry limit is exceeded. Recycling communication for a SNA channel involves deallocating the conversation (if there is any), closing and re-opening the ACB, and preparing to receive a conversation allocation request from the partner or client LU. This message follows other messages that provide details about the error that occurred.

In this message, channelId is the identity of the problematic SNA channel.

IOAGATE attempts to recycle the indicated SNA channel.

Corrective Action: No action is required.

ECAG83E IOAGATE WILL BE SHUT DOWNLink copied to clipboard

Explanation: IOAGATE will shut down because of an error that occurred. This message follows other messages that provide details about the error.

IOAGATE shuts down.

Corrective Action: If the shutdown is due to an error in the IOAGATE, contact BMC Customer Support.

ECAG84I OPERATION WILL BE RE-ATTEMPTEDLink copied to clipboard

Explanation: This information message indicates that a failed operation will be retried. This message follows other messages that provide details about an error that occurred. This message can be issued for an SNA channel only.

Normal processing continues, and the failed operation is retried until it succeeds or until the retry limit is reached. When the retry limit is exceeded, an attempt is made to recycle the SNA channel.

Corrective Action: No action is required.

ECAG85I OPERATION WILL BE RE-ATTEMPTED IN A MINUTELink copied to clipboard

Explanation: This information message indicates that a failed operation will be retried after one minute. This message follows other messages that provide details about an error that occurred. This message can be issued for a SNA channel only.

Normal processing continues, and the failed operation is retried after one minute.

Corrective Action: No action is required.

ECAG87I CHANNEL(`channelId`.SNA) ESTABLISHED CNOS APPLID(`applId`) LU(`luName`) LOGMODE(`logmode`) MINWNL(`minwnl`) MINWNR(`minwnr`) SESLIM(`seslim_code`)Link copied to clipboard

Explanation: This information message indicates that a multiple connection (MC) SNA channel established CNOS connection with a partner IOAGATE.

Parameters of the established connection are:

channelId - Channel ID of the local IOAGATE
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
luName - VTAM LU 6.2 (APPC) application identity of the partner IOAGATE
logmode - LOGMODE used in this connection
minwnl - Minimum contention winner sessions for the local IOAGATE
minwnr - Minimum contention winner sessions for the partner IOAGATE
seslim - Maximum number of sessions between the local and the partner IOAGATEs

Corrective Action: No action is required.

ECAG88I CHANNEL(`channelId.`SNA) SESSION ALLOCATED LU(`luName`) CONVID(`conversation_id`) SID(`session_id`)Link copied to clipboard

Explanation: This information message indicates that the sending conversation with a partner IOAGATE was allocated over a multiple connection (MC) SNA channel.

The variables in this message are:

channelId - the identity of the channel over which the specified session was allocated
luName - VTAM LU 6.2 (APPC) LU name of the partner IOAGATE
conversation_id - VTAM LU 6.2 (APPC) conversation identity
session_id - Session identity

Corrective Action: No action is required.

ECAG89W CHANNEL(`channelId`.SNA) APPCCMD(`appc_command`) FAILED APPLID(`applId`) R15(`r15_rc`) R0(`r0_rsn`) RPL6RC(`rpl6_rsn`) PARTNER LU(`luName`)Link copied to clipboard

Explanation: An APPC command issued by a multiple connection (MC) SNA channel failed. This message precedes message ECAG84I, which specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the APPC command
appc_cmd - the failed APPC command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
r15_rc - Return code returned by VTAM in R15
r0_rsn - Reason code returned by VTAM in R0
rpl6_rsn - RPL6 reason code returned by VTAM in RPL6
luName - VTAM LU 6.2 (APPC) application ID of the partner IOAGATE

For more information on appc_cmd, r15_rc, r0_rsn, and rpl6_rc, see the VTAM Programming for LU 6.2 Manual.

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG90E CHANNEL(`channelId.`SNA) APPCCMD(`appc_cmd`) FAILED APPLID(`applId`) R15(`r15_rc`) R0(`r0_rsn`) RPL6RC(`rpl6_rsn`) PARTNER LU(`luName`)Link copied to clipboard

Explanation: An APPC command issued by a multiple connection (MC) SNA channel failed.

This message precedes message ECAG84I, which specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the APPC command
appc_cmd - the failed APPC command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
r15_rc - return code returned by VTAM in R15
r0_rsn - reason code returned by VTAM in R0
rpl6_rsn - RPL6 reason code returned by VTAM in RPL6
luName - VTAM LU 6.2 (APPC) application identity of the partner IOAGATE

For more information on appc_cmd, r15_rc, r0_rsn, and rpl6_rc, see the VTAM Programming for LU 6.2 Manual.

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG91W CHANNEL(`channelId.`SNA) OPEN ACB FAILED, APPLID(`applId`) ACBERFLG(`acb_err_flag`)Link copied to clipboard

Explanation: An OPEN ACB command issued by a multiple connection SNA channel failed. This message precedes a message that specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the OPEN command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
acb_err_flag - ACBERFLG flags returned by VTAM

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG93W CHANNEL(`channelId`.SNA) CLOSE ACB FAILED, APPLID(`applId`) ACBERFLG(`acb_err_flag`)Link copied to clipboard

Explanation: A CLOSE ACB command issued by a multiple connection SNA channel failed. This message precedes a message that specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the CLOSE command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
acb_err_flag - ACBERFLG flags returned by VTAM

Corrective Action: If another message follows with a probable cause of the error, perform the action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG94W CHANNEL(`channelId`.SNA) SETLOGON FAILED, APPLID(`applId`) R15(`r15_rc`) R0(`r0_rsn`) RPLRTNCD(`rplrtncd_code`) RPLFDBK2(`rplfdbk2_code`)Link copied to clipboard

Explanation: A SETLOGON command issued by a multiple connection (MC) SNA channel failed. This message precedes a message that specifies the action that will be taken by IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the SETLOGON command
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
r15_rc - return code returned by VTAM in R15
r0_rsn - reason code returned by VTAM in R0
rplrtncd_code - RPLRTNCD returned by VTAM in RPL
rplfdbk2_code - RPLFDBK2 returned by VTAM in RPL

For more information on r15_rc, r0_rsn, rplrtncd_code, and rplfdbk2_code, see the VTAM Programming for LU 6.2 Manual.

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG95E CHANNEL(`channelId.`SNA) APPCCMD(`appc_cmd`) FAILED AFTER `num` RETRIES APPLID(`applId`) PARTNER LU(`luName`)Link copied to clipboard

Explanation: An APPC command issued by a multiple connection (MC) SNA channel failed after a number of retries. This message precedes a message that specifies the action that will be taken by the local IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message for the system programmer are:

channelId - the identity of the channel that issued the APPC command
appc_cmd - the failed APPC command
num - the number of retries before failure
applId - VTAM LU 6.2 (APPC) application identity of the SNA channel
luName - VTAM LU 6.2 (APPC) application identity of the partner IOAGATE

Corrective Action: For more information on appc_cmd, see the VTAM Programming for LU 6.2 Manual.

The IOAGATE recycles the specified SNA channel.

If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG96E CHANNEL(`channelId`.SNA) APPCCMD SEND NOT COMPLETED WITHIN 10 MINUTES, APPLID(`applId`) PARTNER LU(`luName`)Link copied to clipboard

Explanation: A SEND operation issued by a multiple connection (MC) SNA channel was not completed within the specified time interval. This message precedes a message that specifies the action that will be taken by the local IOAGATE. This message may follow another message that provides more information about the error.

The variables in this message are:

channelId - the identity of the channel that issued the APPC command
applId - VTAM LU 6.2 (APPC) application identity of the SNA channel
luName - VTAM LU 6.2 (APPC) LU name of the partner IOAGATE

The IOAGATE recycles the specified SNA channel.

Corrective Action: If another message follows with a probable cause of the error, perform the user action recommended for that message. Otherwise, call your system programmer for assistance.

ECAG97E CHANNEL(`channelId`.SNA) GENCB FAILED, APPLID(`applId`) R15(`r15_rc`) R0(`r0_rsn`) RPLRTNCD(`rplrtncd_code`) RPLFDBK2(`rplfdbk2_code`)Link copied to clipboard

Explanation: A GENCB operation issued by a multiple connection SNA channel failed. This message precedes a message that specifies the action that will be taken by the local IOAGATE.

The variables in this message for the system programmer are:

channelId - the identity of the SNA channel that issued the GENCB operation
applId - VTAM LU 6.2 (APPC) application ID of the SNA channel
r15_rc - return code returned by VTAM in R15
r0_rsn - reason code returned by VTAM in R0
rplrtncd_code - RPLRTNCD returned by VTAM in RPL
rplfdbk2_code - RPLFDBK2 returned by VTAM in RPL

For more information on r15_rc, r0_rsn, rplrtncd_code, and rplfdbk2_code, see the VTAM Programming for LU 6.2 Manual.

IOAGATE shuts down.

Corrective Action: Try to determine the cause of the failure using the diagnostic information in the message. If you cannot resolve the problem, call your system programmer for assistance.

ECAG98I CHANNEL(`channelId`.SNA) CONVERSATION STARTED, LU(`luName`) CONVID(`conversation_id`) SID(`session_id`) APPLID(`applId`)Link copied to clipboard

Explanation: This information message indicates that the specified conversation started between the IOAGATE and its partner. A specific partner started a conversation with the IOAGATE.

The variables in this message are:

channelId - the identity of the SNA channel on which the conversation was started
luName - VTAM LU 6.2 (APPC) LU name of the partner IOAGATE
conversation_id - VTAM LU 6.2 (APPC) conversation identity
session_id - session identity
applId - VTAM LU 6.2 (APPC) application identity of the IOAGATE

Corrective Action: No action is required.

ECAG99W CHANNEL(`channelId`.SNA) ATTN LOSS EXIT INVOKED, LU(`luName`) APPLID(`applId`) SID(`session_id`)Link copied to clipboard

Explanation: A session between the specified LU and the local IOAGATE ended. A partner IOAGATE ended the connection to the local IOAGATE.

The variables in this message are:

channelId - the identity of the SNA channel on which the connection was terminated
luName - VTAM LU 6.2 (APPC) application identity of the partner IOAGATE
applId - VTAM LU 6.2 (APPC) application identity of the local IOAGATE
session_id - session identity

Corrective Action: No action is required.

Messages ECAH00 through ECAHxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAH01W APPL.SERVER(`svr`) SUSPECTED HANGING IN THE LAST `num1` INTERVALS OF `num2` seconds:Link copied to clipboard

Explanation: The Hanging Detection mechanism in IOAGATE suspected a hanging transaction in the application server.

The variables in this message are:

svr - the identity of the application server
num1 - the duration in seconds of one time interval
num2 - the number of time intervals that this hanging situation continues

This message is followed by message ECAH0AI.

Corrective Action: No action is required.

ECAH02W IOAGATE SUSPECTED HANGING IN THE LAST `num1` INTERVALS OF `num2` seconds:Link copied to clipboard

Explanation: The Hanging Detection mechanism in IOAGATE suspected a hanging transaction in IOAGATE.

The variables in this message are:

num1 - the duration in seconds of one time interval
num2 - the number of time intervals that this hanging situation continues

This message is followed by message ECAH0BI.

Corrective Action: No action is required.

ECAH03W CHANNEL (`chan`) SUSPECTED HANGING IN THE LAST `num1` INTERVALS OF `num2` seconds:Link copied to clipboard

Explanation: The Hanging Detection mechanism in IOAGATE suspected a hanging transaction in a communication channel.

The variables in this message are:

chan - the identity of the communication channel
num1 - the duration in seconds of one time interval
num2 - the number of time intervals that this hanging situation continues

This message is followed by message ECAH0CI.

Corrective Action: No action is required.

ECAH0AI MESSAGES HAVE BEEN ACCUMULATED FOR THE APPL.SERVER BUT IT HAS NOT BEEN READY TO PROCESS THEMLink copied to clipboard

Explanation: This information message describes the result of the hanging transaction that was described in message ECAH01W.

Corrective Action: No action is required.

ECAH0BI ROUTING PROCESS DOES NOT TAKE PLACELink copied to clipboard

Explanation: This information message describes the result of the hanging transaction that was described in message ECAH02W.

Corrective Action: No action is required.

ECAH0CI MESSAGES HAVE BEEN ACCUMULATED FOR THE CHANNEL TO BE SENT, BUT NO MESSAGE HAS BEEN SENTLink copied to clipboard

Explanation: This information message describes the result of the hanging transaction that was described in message ECAH03W.

Corrective Action: No action is required.

Messages ECAL00 through ECALxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAL00I Module Source Compilation date Change level Size CSECT ofLink copied to clipboard

Explanation: This information message provides header information about IOAGATE software level. ECAL01I messages that follow provide details for load modules of IOAGATE.

Corrective Action: No action is required.

ECAL01I `module source compDate changeLevel size CSECT of`Link copied to clipboard

Explanation: This message follows the message ECAL00I, which provides header information. The set of ECAL01I information messages provides detailed software level information about a separate load module or CSECT of a load module.

The variables in this message are:

module - the name of a load module or CSECT when SAS/C is the source
source - the type of the source
compDate - a compilation timestamp
changeLevel - the last change identity applied to this module or CSECT
size - the hexadecimal size of a load module
CSECT of - the load module name that this CSECT is part of. If the load module name and the CSECT are the same, then this field is empty.

Corrective Action: No action is required.

ECAL02S MCT ADDRESS UNAVAILABLELink copied to clipboard

Explanation: A severe internal error occurred when trying to retrieve the detailed software level information of IOAGATE.

Level information about IOAGATE is not displayed. Processing continues.

Corrective Action: Contact BMC Customer Support.

ECAL03S NO PARAMETER SPECIFIED FOR ECASLVLLink copied to clipboard

Explanation: A severe internal error occurred.

The ECAB0DI message ("ECAAPPL PROCESSOR CREATED...") is not displayed. Processing continues.

Corrective Action: Contact BMC Customer Support.

ECAL04S LOAD FAILED FOR MODULE(ECAAPL)Link copied to clipboard

Explanation: A severe error occurred when trying to load the ECAAPPL processor.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAL05E FAILURE TO RECOGNIZE LEVEL OF (ECAAPL)Link copied to clipboard

Explanation: An internal error occurred.

The ECAB0DI message ("ECAAPPL PROCESSOR CREATED...") is not displayed. Processing continues.

Corrective Action: Contact BMC Customer Support.

ECAL06I Operating System Level(`lvl`) FMID(`fmid`)Link copied to clipboard

Explanation: This information message displays the level of the Operating System under which control of IOAGATE is currently running.

The variables in this message are:

lvl - the level identity of the operating system
fmid- the FMID identity of the operating environment

Corrective Action: No action is required.

ECAL07I IOAGATE STARTED TO DISPLAY SOFTWARE LEVEL ONLY, RELEASE(`rel`) CCID(`lvl_id`)Link copied to clipboard

Explanation: This information message indicates that IOAGATE was started with the A parameter set to L. This special mode serves to display the level information of the IOAGATE code only.

IOAGATE displays the requested level information, and goes down.

Corrective Action: No action is required.

ECAL09E FAILURE TO RECOGNIZE ECVTPNAM VALUE: `val`.Link copied to clipboard

Explanation: An internal error occurred when trying to identify the operating system level.

Corrective Action: Contact BMC Customer Support.

Messages ECAP00 through ECAPxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAP01S READING FAILED WITH RC(`rc`) REASON(`rsn`)Link copied to clipboard

Explanation: An attempt to process a network map specified in the ECAPARM configuration file failed.

The message ECAP0XE precedes this message, and identifies the problematic network map.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization, and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this network map. To get the name of the network map, the Control-O monitor loads the same ECAPARM configuration file.

The variables in this message are:

rc - the return code

Valid values for rc are:

Return Code	Explanation
12	Member not found
16	Data set is not a library
24	LRECL is not 80
28	Data set in use
36	Data set not in the catalog
56	STAE detected an abend

rsn - the system failure reason code

IOAGATE disables the Control-O application defined in the network map definitions, and processing continues.

Corrective Action: Correct the problem indicated by the reason code rsn, and restart IOAGATE.

ECAP02E LUNAME= VALUE LONGER THAN 8 CHARACTERSLink copied to clipboard

Explanation: The LUNAME parameter value in the specified line in the specified network map in the ECAPARM configuration file is too long.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this network map. To get the name of the network map, the Control-O monitor loads the same ECAPARM configuration file.

IOAGATE discards the line containing the problem, and processing continues. If the line is a part of a PARTNER statement that defines a connection for the current IOAGATE, processing of the map fails, and the application linked to the channel with this map is disabled.

Corrective Action: Change the value of LUNAME so that it complies with VTAM naming conventions, and restart IOAGATE.

ECAP03E NON-ALPHANUMERIC CHARACTER IN LUNAME= VALUELink copied to clipboard

Explanation: The LUNAME parameter value in the specified line in the specified network map in the ECAPARM configuration file contains a character that is not alphanumeric.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this network map. To get the network map name, the Control-O monitor loads the same ECAPARM configuration file.

Corrective Action: Change the value of LUNAME so that it complies with VTAM naming conventions, and restart IOAGATE.

ECAP04E INVALID FIRST CHARACTER IN LUNAME= VALUELink copied to clipboard

Explanation: The first character of the LUNAME parameter value in the specified line in the specified network map in the ECAPARM configuration file is invalid.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this network map. To get the network map name, the Control-O monitor loads the same ECAPARM configuration file.

Corrective Action: Change the value of LUNAME so that it complies with VTAM naming conventions, and restart IOAGATE.

ECAP05W THE STATEMENT IS OUT OF PLACELink copied to clipboard

Explanation: An invalid order of statements was discovered in the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP06E `port / host` = REQUIRED IN TCP PARTNER IF CONNECTOR=LOCAL SPECIFIEDLink copied to clipboard

Explanation: Either the PORT or the HOST parameter in the TCP partner statement of the network map must be specified if the CONNECTOR parameter in that TCP partner is set to LOCAL.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP07E MAP DOES NOT BEGIN WITH LOCAL STATEMENTLink copied to clipboard

Explanation: The network map must begin with a LOCAL statement.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP08W UNRECOGNIZED STATEMENT (`stmt`)Link copied to clipboard

Explanation: The network map statement stmt was not recognized as valid.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP09E INVALID `stmt` STATEMENTLink copied to clipboard

Explanation: The invalid statement stmt was discovered in the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, and restart IOAGATE.

ECAP0AW IMPROPER PARAMETER IN THE LOCAL STATEMENTLink copied to clipboard

Explanation: An invalid parameter was discovered in the LOCAL statement of the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0CE INVALID IP ADDRESS SPECIFIED IN HOST= PARAMETERLink copied to clipboard

Explanation: An invalid IP address value was discovered in the HOST parameter of the network map.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Correct the IP address.

ECAP0DE NON-DIGIT CHARACTER IN PORT= PARAMETERLink copied to clipboard

Explanation: A non-digit character was discovered in the PORT parameter of the network map.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Correct the PORT value.

ECAP0EE PORT= VALUE GREATER THAN 65534Link copied to clipboard

Explanation: An invalid PORT parameter value was discovered.

The PORT parameter value must be in the range from 1024 through 65534.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER and tries to continue processing the network map.

Corrective Action: Correct the PORT value.

ECAP0FS NO LINE FOUNDLink copied to clipboard

Explanation: The network map is not valid because it contained no line.

IOAGATE disables the channel that uses the network map identified in the ECAP0XI message that precedes the ECAP0FS message.

Corrective Action: Specify the correct network map member.

ECAP0GE PORT= VALUE LESS THAN 1024Link copied to clipboard

Explanation: The value of the PORT parameter is invalid. The value of the PORT parameter must be in the range from 1024 through 65534.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Correct the PORT value.

ECAP0HW NO VALUE SPECIFIED IN THE PORT= PARAMETERLink copied to clipboard

Explanation: The PORT parameter has no value specified.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Set a value for the PORT parameter.

ECAP0IE LACK OF REQUIRED PARAMETERS IN `protocol` PARTNER STATEMENTLink copied to clipboard

Explanation: Some required parameters were not found in the Partner statement of the network map.

In this message, protocol is the communication protocol to be used by the channel to which the network map is defined (the partner statement).

Valid values are:

TCP - the partner statement uses the network map defined in TCP channel
SNA - the partner statement uses to the network map defined in SNA channel

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0KE INVALID APPL= PARAMETER SPECIFIEDLink copied to clipboard

Explanation: An invalid APPL parameter value was discovered in the SNA partner of the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0LE NODE= PARAMETER REQUIRED IN THE PARTNER STATEMENTLink copied to clipboard

Explanation: No NODE parameter was found in the PARTNER statement. The NODE parameter must be defined in the PARTNER statement of the network map.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0ME NO LOCAL STATEMENT REFERS TO THE CHANNEL NODE(`node`)Link copied to clipboard

Explanation: The network map must have a LOCAL statement with a NODE parameter that matches the NODE value from the appropriate CHANNEL declaration.

In this message, node is the value of the NODE parameter in the CHANNEL declaration referring to the network map that is being analyzed.

IOAGATE disables the channel that uses the indicated network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0OW CONNECTOR=LOCAL ALTERED TO CONNECTOR=PARTNERLink copied to clipboard

Explanation: This warning message is displayed by IOAGATE when the CONNECTOR value has changed from LOCAL to PARTNER.

IOAGATE tries to continue processing the network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0PW INVALID CONNECTOR= VALUE SPECIFIED, SET TO CONNECTOR=PARTNERLink copied to clipboard

Explanation: The value of the CONNECTOR parameter is invalid.

IOAGATE changes the CONNECTOR value from LOCAL to PARTNER, and tries to continue processing the network map.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map and restart IOAGATE.

ECAP0QW INVALID LINE DROPPEDLink copied to clipboard

Explanation: IOAGATE could neither recognize the indicated line, nor detect any specific error in the line.

The line is ignored.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0RE LUNAME= SPECIFIED FOR TCP CHANNELLink copied to clipboard

Explanation: The SNA parameter LUNAME has been specified for a TCP channel.

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing the network map.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0SE `parm` = PARAMETER IS INVALID FOR SNA CHANNELLink copied to clipboard

Explanation: The TCP parameter parm has been specified for a SNA channel.

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing the network map.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0TS INTERNAL ERROR OCCURRED WHEN DISABLING `parm/stmt`Link copied to clipboard

Explanation: A severe internal error occurred when IOAGATE tried to disable the parm parameter or the stmt statement.

In this message, parm/stmt is the parameter or statement that IOAGATE tried to disable.

This message is only issued when IOAGATE is configured for IOAGATE-to-IOAGATE communication.

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing the network map.

Corrective Action: Contact BMC Customer Support.

ECAP0WE DUPLICATE NODE= SPECIFIEDLink copied to clipboard

Explanation: The same NODE parameter value has been entered twice.

This message is only issued when IOAGATE is configured for IOAGATE-to-IOAGATE communication.

IOAGATE disables the channel that uses the indicated network map and tries to continue processing the network map.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0XI ERROR DETECTED, MAP(`mapId-channelId.protocol`), LINE=`lineNum` :Link copied to clipboard

Explanation: This message is a header message, and is followed by another message that describes precisely an error discovered in line lineNum.

The variables in this message are:

mapId - the identity of the network map in which IOAGATE discovered the error
channelId - the identity of the channel that uses the indicated network map
protocol - the current channel uses this communication protocol Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
lineNum - sequential number of the line in which IOAGATE discovered the error

Corrective Action: Correct the network map and restart IOAGATE.

ECAP0YE TCPVENDR PARAMETER MUST HAVE THE SAME VALUE IN ALL CHANNELSLink copied to clipboard

Explanation: An error occurred while IOAGATE was checking ECAPARM. The TCPVENDR parameter in the channels defined in ECAPARM had different values.

IOAGATE goes down.

Corrective Action: Ensure that the TCPVENDR parameter has the same value in all channels of ECAPARM, then restart IOAGATE.

ECAP0ZE REQUESTED MAP NOT FOUND IN THE PARM LIBRARYLink copied to clipboard

Explanation: IOAGATE failed to load the network map specified in the channel.

IOAGATE disables the channel that uses the indicated network map and tries to continue processing.

Corrective Action: Correct the name of the network map and restart IOAGATE.

ECAP10I IOAENV `memName` BUILT BY CCID(`changeLevel`) ON `date` is usedLink copied to clipboard

Explanation: This information message displays level information for the memName IOAENV parameters member used by IOAGATE in the current run.

The variables in this message are:

memName - the name of the parameters member Valid values are:
- ECAAPPL - table of supported applications
- ECAPDEF - table of defaults of numeric parameters
- ECASRVT - table of services (transactions)
changeLevel - the level of the change that was last applied to the indicated member
date - the date this member was last changed

Corrective Action: No action is required.

ECAP11S `memName type` PARAMETERS MEMBER UNAVAILABLELink copied to clipboard

Explanation: A severe error occurred when IOAGATE tried to load the specified IOAENV parameters member.

The variables in this message are:

memName - name of the parameters memberValid values are:
- ECAPARM - configuration file
- ECAAPPL - table of supported applications
- ECAPDEF - table of defaults of numeric parameters
- ECASRVT - table of services (transactions)
type - name of the parameters memberValid values are:
- SOURCE
- IOAENV

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP12S ECATMEM FAILED, `rsn`Link copied to clipboard

Explanation: A severe internal error occurred when IOAGATE tried to verify an internal parameters member.

In this message, possible values for rsn are:

RC= return_code REASON= reason_code
INSUFFICIENT STORAGE
DDNAME NOT PROVIDED
MEMBER NAME NOT PROVIDED

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP13S `memName type` PARAMETERS MEMBER IS EMPTYLink copied to clipboard

Explanation: A severe internal error occurred when IOAGATE tried to read the indicated IOAENV parameters member.

The variables in this message are:

memName - name of the parameters memberValid values are:
- ECAPARM - configuration file
- ECAAPPL - table of supported applications
- ECAPDEF - table of defaults of numeric parameters
- ECASRVT - table of services (transactions)
type - Name of the parameters member Valid values are:
- SOURCE
- IOAENV

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP16W NO IOAGATE-TO-IOAGATE CONNECTION WAS DEFINEDLink copied to clipboard

Explanation: The F IOAGATE,MAP modify command was issued, to display a network map, but failed because no IOAGATE-to-IOAGATE connection was configured in the current run of the local IOAGATE.

If a network map is specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The NETWMAP parameter was not specified in the ECAPARM configuration file, or the multiple connection SNA channel was either disabled or not configured to function with a network map.

The F IOAGATE,MAP modify command is ignored. Normal processing continues.

Corrective Action: No action is required.

ECAP17E MAP(`mapId -channelId.protocol`) PROCESSING FAILED, RC(`rc`)Link copied to clipboard

Explanation: An error was encountered in the network map identified by the variables in this message.

The variables in this message are:

mapId - the name of a member in the IOA PARM library that describes a map of network connections between IOAGATEs that allows one IOAGATE to communicate with another over a multiple connection (MC) channel
channelId - the identity of the channel that uses the network map mapId
protocol - the communication protocol used by the current channel Valid values are:
- TCP - TCP/IP communication protocol
- SNA - SNA communication protocol
rc - the return code

Valid values for rc are:

Return Code	Explanation
8	"Disable map" error encountered
12	"Stop processing" error encountered

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing.

Corrective Action: Correct the network map and restart IOAGATE.

ECAP18W NETWORK MAP(`mapId`) HAS BEEN PROCESSED WITH RC(`rc`)Link copied to clipboard

Explanation: The network map mapId of IOAGATE connections was processed with a nonzero reason code (rc).

The variables in this message are:

mapId - the name of the member in the IOA PARM library that determines the map of IOAGATE connections, and enables one IOAGATE to communicate with another over a multiple connection (MC) channel
rc - the return code

Valid values for rc are:

Return Code	Explanation
04	Minor errors were detected in the map, or errors were detected that do not relate to a PARTNER statement describing the connections of the current IOAGATE. The network map is enabled.
12	severe errors were detected in the network map. Processing of the map failed.

Corrective Action: Do the following:

Check any error messages that precede this one.
Check the network map.
Correct the ECAPARM configuration file.
Restart IOAGATE.

ECAP19I NETWORK MAP(`mapId`) HAS BEEN PROCESSED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the mapId network map of IOAGATE connections was successfully processed.

To get the name of the network map, the Control-O monitor loads the same ECAPARM configuration file.

In this message, mapId identifies the member in the IOA PARM library that determines the map of IOAGATE connections, and enables one IOAGATE to communicate with another over a multiple connection (MC) channel.

Corrective Action: No action is required.

ECAP1AW NETWORK MAP(`mapName`) WAS SPECIFIED BUT NOT PROCESSEDLink copied to clipboard

Explanation: The network map mapName that is specified in the ECAPARM configuration file by the NETWMAP parameter has not been processed.

Other messages may clarify why the map has not been processed.

The Control-O monitor continues its startup, but without communication services through IOAGATE.

Corrective Action: If possible, determine from other messages why the map has not been processed. Correct the problem and restart IOAGATE and Control-O.

ECAP1BW NETWORK MAP (OR NODE) WAS NOT SPECIFIED IN ECAPARM(`suffix`)Link copied to clipboard

Explanation: The ECAPARM configuration file with suffix suffix has been defined for Control-O, but either the NETWMAP (network map name) parameter or the NODE parameter or both have not been specified in this ECAPARM file.

The Control-O monitor continues its startup but without communication services through IOAGATE

Corrective Action: Specify both parameters, and restart IOAGATE and Control-O.

ECAP1XE DUPLICATE NODE `nodeId` DETECTED IN CHANNEL(`channelId`), CHANNEL DISABLEDLink copied to clipboard

Explanation: A duplicate node has been detected in the channelId channel, and IOAGATE has disabled that channel.

The variables in this message are:

nodeId - the identity of the node that is duplicated
channelId - the identity of the problematic channel

IOAGATE disables the channel that uses the indicated network map, and tries to continue processing.

Corrective Action: Correct the problem, using the diagnostics issued by the message, and restart IOAGATE.

ECAP20I IOAGATE-TO-IOAGATE CONNECTIONS NODE=node MAP=mapId APPL=CONTROL-OLink copied to clipboard

Explanation: This message is the response to the F IOAGATE,MAP modify command, and is the header for ECAP22I messages.

The variables in this message are:

node - the identity of the current local node for which IOAGATE-to-IOAGATE connections are displayed
mapId - the name of the member in the IOA PARM library that determines the map of IOAGATE connections, and enables one IOAGATE to communicate with another over a multiple connection (MC) channel

Corrective Action: No action is required.

ECAP21I CHAN LUNAME LOGMODE PARTNER CONVERSATION ID STATUSLink copied to clipboard

Explanation: This information message follows an ECAP20I message, which identifies the current local node, and is a header for ECAP22I messages, which specify the SNA connections that are available for the current local node.

The ECAP23I and ECAP24I messages may also follow.

This group of messages is displayed as a result of an F IOAGATE,MAP command.

Corrective Action: No action is required.

ECAP22I `channelId luName logmode partner_id conversation_id status`Link copied to clipboard

Explanation: This information message specifies one of the available SNA IOAGATE-to-IOAGATE connections for the current local IOAGATE, using the network map specified in the last ECAP20I message. The ECAP20I message precedes and acts as a header for a single ECAP22I message, or a group of ECAP22I messages.

If a network map was specified in the ECAPARM configuration file, IOAGATE reads the map during initialization and builds internal tables of connections in the main storage. The same network map is processed by a Control-O monitor and by each Control-O application server that participates in the communication described by this map.

The variables in this message are:

channelId - the identity of the channel that controls the connection
luName - the Logical Unit name of the partner IOAGATE
logmode - the LOGMODE used by this connection
partner_id - the conversation ID of the outgoing conversation
conversation_id - the conversation identity of the incoming conversation
status - Status of the connection Valid values are:
- NOTALLOC - the conversation is not allocated.
- ALLOCTED - the conversation is allocated.
- ALLOCSND - the Send channel is allocated.
- ALLOCRCV - the Receive channel is allocated.

Corrective Action: No action is required.

ECAP23I CHAN TASK PARTNER PORT CONNECTOR STATUS SOCKET HOSTLink copied to clipboard

Explanation: This information message is a response to the F IOAGATE,CHAN modify command. It follows an ECAP20I message, which identifies the current local node, and is a header for ECAP24I messages, which identify the available TCP connections for the current local node.

Corrective Action: No action is required.

ECAP24I `channelId taskId partner port connector status socket host`Link copied to clipboard

Explanation: This information message specifies one of the available TCP/IP connections for the current local IOAGATE using the network map specified in the last ECAP20I message. The ECAP23I message precedes and acts as a header for a single ECAP24I message, or a group of ECAP24I messages.

The variables in this message are:

channelId - the identity of the channel that controls this TCP/IP connection
taskId - the identity of the communication task of the channel that controls this TCP/IP connection
partner - the identity of the node on which the partner IOAGATE is running
port - the TCP/IP port number used to connect to the partner IOAGATE
connector - the mode of the current local IOAGATE specified by the CONNECTOR parameter in a network map. Valid values are:
- LOCAL - the current IOAGATE is an initiator of the connection to the partner IOAGATE, that is, CONNECTOR is set to LOCAL
- PARTNER - the current IOAGATE is not an initiator of the connection to the partner IOAGATE, that is, CONNECTOR is set to PARTNERThe current IOAGATE can accept connection from its partner IOAGATE.
status - Status of the connection. Valid values are:
- HNDSHAKE RCVD - A handshake message has been received.
- HNDSHAKE SENT - A handshake message has been sent.
- CONNECTED - A connection was successfully established with the partner IOAGATE.
- TAKING SOCKET - The connection is being taken by the recipient communication task.
- CONNECTED/TAKE - Connection has been established. The taking-socket process is about to be completed.
- GIVING SOCKET - Connection is being giving by the Listener task of the channel to the recipient communication task.
- CONNECTED/GIVE - Connection has been established. The giving-socket process is about to begin.
- GIVE REQUIRED - Connection has been established. The giving-socket process is being requested.
- GIVE FAILED - Connection has been established. The giving-socket process failed.
- H-SHAKE FAILED - The handshaking process has failed.
- RETRYING - The attempt to connect to the partner IOAGATE failed. Another attempt will be made in the time interval specified in the ALLOCINT parameter in the ECAPARM configuration file.
- CONNECTION IN PROGRESS - A Connect action has been initiated.
- CONNECTING - The Connect action is being processed.
- DISABLED - The IOAGATE-to-IOAGATE connection entry is disabled
- READY TO CONNECT - The local IOAGATE is ready to begin a Connect action.
- WAITING FOR CONNECTION - The local IOAGATE is ready to accept connection from its partner IOAGATE.
- DISCONNECTED - The connection to the partner IOAGATE has been disrupted.
- RECONNECTED - The connection has been re-established.
socket - the TCP/IP socket number assigned to connect (CONNECT is set to YES), or to be connected (CONNECT is set to NO) to the partner IOAGATE
host - The host name or IP address of the partner IOAGATE This data exactly reflects the specification in the network map.

Corrective Action: No action is required.

ECAP30E APSERVER ENTRY(`entryId`), INVALID ALIAS APPLICATION CODE(`applicId`) SPECIFIED, ALIAS DISABLEDLink copied to clipboard

Explanation: An invalid application code was specified as an alias in the APPL=(,) parameter of an APSERVER definition.

The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE. The APPL parameter of an APSERVER statement can be used to specify a list of alias codes. Each alias code specifies an application that can be served by the same application server as the others in the list, concurrently with the main application.

The variables in this message are:

entryId - a sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file
applicId - the invalid application code that was specified as an alias

The specified alias application code is ignored, and processing continues.

Corrective Action: Check the ECAPARM configuration file, correct the file, and restart IOAGATE.

ECAP31E ECAPRM INTERNAL ERROR, APPLICATION ALIASES PROCESSING FAILEDLink copied to clipboard

Explanation: An internal error occurred during the processing of application aliases specified in an APPL parameter of an APSERVER statement.

Corrective Action: Contact BMC Customer Support.

ECAP32E NO RAW APSERVER ENTRIES FOUNDLink copied to clipboard

Explanation: An internal error occurred when IOAGATE was processing the ECAPARM configuration file. No APSERVER entry was found in the ECAPARM configuration file.

During initialization, IOAGATE reads and verifies the definitions specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

IOAGATE shuts down.

Corrective Action: Correct the ECAPARM configuration file, and restart IOAGATE. If the problem persists, contact BMC Customer Support.

ECAP33S ECAPRM INTERNAL ERROR WORK AREA, SIZE(`size`) EXCEEDED ALLOWED MAXIMUM 64KLink copied to clipboard

Explanation: A severe internal error occurred during checking of the ECAPARM configuration file. The size of the internal work area is invalid.

In this message, size is the size of the internal work area that exceeded the maximum.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP34E PARAMETER ARMELEM=`arm_element_id` INVALID, IMPROPER CHARACTER(`chara`) SPECIFIEDLink copied to clipboard

Explanation: While processing the ECAPARM configuration file, an invalid character was detected in the ARMELEM parameter.

The variables in this message are:

arm_element_id - the IOAGATE automatic restart management (ARM) element name
chara - the invalid character detected in the IOAGATE ARM element

The ARMELEM parameter is ignored. Normal processing continues.

Corrective Action: Using the diagnostics issued by the message, correct the problem, and restart IOAGATE.

ECAP35S ECAPRM INTERNAL ERROR, APSERVER ENTRY(`entryId`), SERVER= VALUE NOT SPECIFIEDLink copied to clipboard

Explanation: A severe internal error occurred in the ECAPARM configuration file because no value was specified for the SERVER parameter in the APSERVER definition.

In this message, entryId is a sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file.

The specified APSERVER definition is disabled, and processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP37E MORE THAN 99 APPLICATION SERVERS DEFINEDLink copied to clipboard

Explanation: The number of APSERVER statements specified in the ECAPARM configuration file exceeds the maximum permitted. A maximum of 99 APSERVER statements may be specified in the ECAPARM configuration file.

During initialization, IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

IOAGATE shuts down.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP38E APSERVER ENTRY(`entryId`), UNKNOWN APPL(`value`) SPECIFIED, SERVER DISABLEDLink copied to clipboard

Explanation: An invalid application name was specified in an APPL parameter of an APSERVER definition in the ECAPARM configuration file. During initialization, IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

entryId - the sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file
value - the value specified by the user in the APPL parameter

The identified APSERVER definition entryId is ignored. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP39W CHANNEL(`entryId`), MAXIMUM NUMBER OF SERVERs PER CHANNEL(`channelId`) REACHED, APSERVER(`server_id`) DISABLEDLink copied to clipboard

Explanation: The number of APSERVER definitions linked to the identified channel exceeded the maximum number allowed, namely eight.

The variables in this message are:

entryId - the sequential number that identifies the CHANNEL definition entry in the ECAPARM configuration file
channelId - the identity of the channel to which the problematic APSERVER is linked
server_id - the identity of the problematic APSERVER

The identified APSERVER definition is disabled. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3AE TOTAL NUMBER OF APPLICATION SERVER TASKS CANNOT EXCEED 500Link copied to clipboard

Explanation: An internal error occurred because the number of application server tasks defined in the ECAPARM configuration file exceeds the maximum permitted. A maximum of 500 application server tasks may be defined in the ECAPARM configuration file.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP3BE APSERVER ENTRY (`entryId.entry_typ.model`), IMPROPER CHANNEL(`channel`) SPECIFIED FOR THE APPL (`applName`), SERVER DISABLEDLink copied to clipboard

Explanation: The communication model in the ECAPARM configuration file in an APSERVER definition does not match the communication model of the referenced channel. During initialization, IOAGATE reads and verifies the definitions in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

entryId - a sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file
entry_typ - the type of application server defined by this APSERVER statement. Valid values are:
- CM - manager of the address space of an application server
- CS - application server
- CD - detector server
- CU - updater server
model - the communication model of the channel required by the application
channel - the identity of the channel referenced from the APSERVER definition
applName - the identity of the application server

The indicated APSERVER definition is ignored, and processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3CS NO APPLICATION SERVER DEFINED IN ECAPARMLink copied to clipboard

Explanation: A severe internal error occurred during initialization. No application server was defined in ECAPARM.

IOAGATE shuts down.

Corrective Action: Define at least one application server in ECAPARM.

ECAP3DE APSERVER ENTRY(`entryId`), UNKNOWN CHANNEL(`value`) SPECIFIED, SERVER DISABLEDLink copied to clipboard

Explanation: The server is disabled because a channel reference in an APSERVER definition does not exist in the ECAPARM configuration file.

During initialization, IOAGATE reads and verifies the definitions from the ECAPARM configuration file. IOAGATE, and each application server that communicates with this IOAGATE, process the same ECAPARM configuration file.

The variables in this message are:

entryId - the sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file
value - the invalid value specified by the user as a channel reference

The specified APSERVER definition is disabled, and processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3EE APSERVER ENTRY(`entryId`), MANDATORY PARAMETER APPL= WAS NOT SPECIFIED, SERVER DISABLEDLink copied to clipboard

Explanation: The server is disabled because no value was set for the APPL parameter in the APSERVER definition.

During initialization, IOAGATE reads and verifies the definitions specified in the ECAPARM configuration file. The IOAGATE, and each application server that communicates with this IOAGATE, process the same ECAPARM configuration file.

In this message, entryId is a sequential number that identifies the APSERVER definition entry in the ECAPARM configuration file.

The specified APSERVER definition is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3FS INTERNAL ERROR. EXPANDED AND RAW APPL ENTRIES DIFFERLink copied to clipboard

Explanation: A severe internal error occurred during the processing of the ECAPARM configuration file. Differences were found between the expanded and the raw application entries.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP3GW APSERVER ENTRY(`entryId`), IMPROPER COMPRESS= SPECIFIED(`code`), CHANGED TO DEFAULT(`default_code`)Link copied to clipboard

Explanation: The value of the COMPRESS parameter in the ECAPARM configuration file is invalid. The COMPRESS parameter must be set to YES or NO.

The variables in this message are:

entryId - a sequential number that identifies the problematic APSERVER definition entry in the ECAPARM configuration file
code - the current invalid value of the COMPRESS parameter
default_code - the default value set by IOAGATE for the COMPRESS parameter for this application

The value specified for COMPRESS is replaced by the default value. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP3HE APSERVER ENTRY(`entryId`), ENCRYPT= PARAMETER IS NOT SUPPORTED FOR `applId`Link copied to clipboard

Explanation: A value cannot be set for the ENCRYPT parameter for the application applId.

The variables in this message are:

entryId - a sequential number that identifies the problematic APSERVER definition entry in the ECAPARM configuration file
applId - the identity of the application for which encryption is not supported

The value set for the ENCRYPT parameter is ignored. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP41S NO CHANNEL ENTRY AVAILABLELink copied to clipboard

Explanation: A severe error occurred during checking of the ECAPARM configuration file. There is no valid CHANNEL definition in the ECAPARM configuration file.

IOAGATE shuts down.

Corrective Action: Do the following:

Check any error messages that precede this one.
Correct the ECAPARM configuration file.
Restart IOAGATE.

ECAP42W CHANNEL ENTRY(`entryId`), MANDATORY PARAMETER ID= WAS NOT SPECIFIED, CHANNEL DISABLEDLink copied to clipboard

Explanation: The ID parameter is not specified for the indicated channel in the CHANNEL definition.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP43W CHANNEL ENTRY(`entryId`), MANDATORY PARAMETER MODEL= WAS NOT SPECIFIED, CHANNEL DISABLEDLink copied to clipboard

Explanation: The MODEL parameter is not specified for the indicated channel in the CHANNEL definition.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP44W CHANNEL ENTRY(`entryId`), OPTIONAL PARAMETER SUBSYSTM= CAN BE USED WITH TCPVENDR=CA ONLY, PARAMETER IGNOREDLink copied to clipboard

Explanation: The optional SUBSYSTM parameter was specified in the ECAPARM configuration file with TCPVENDR set to IBM for an SNA channel or a TCP channel. The optional SUBSYSTM parameter is only valid for a TCP channel, and only with TCPVENDR set to CA.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The SUBSYSTM parameter is ignored, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP45W CHANNEL ENTRY(`entryId`), ID(`channelId`) NOT UNIQUE, CHANNEL DISABLEDLink copied to clipboard

Explanation: The same channel ID is used in more than one CHANNEL definition in the ECAPARM configuration file. The channel ID must be unique for each CHANNEL definition in the ECAPARM configuration file.

During initialization IOAGATE reads and verifies definitions specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

entryId - a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file
channelId - the channel identity assigned by the user in the ECAPARM configuration file

The specified CHANNEL definition is disabled, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP46W CHANNEL ENTRY(`entryId`), MANDATORY PARAMETER PORT= WAS NOT SPECIFIED, CHANNEL DISABLEDLink copied to clipboard

Explanation: The PORT parameter is not specified for the indicated TCP channel in the CHANNEL definition.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled, and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP47W APPL.SERVER (`applServer.addrSpaceId`) DISABLED IN ECAPARM(`suffix`)Link copied to clipboard

Explanation: During initialization, IOAGATE detected that the value of the SERVER parameter in the ECAPARM configuration file is DISABLE for the specified application server applServer. Therefore it will not be started.

The SERVER parameter can be specified manually in the APSERVER definition of the ECAPARM configuration file to enable or disable the definition. The default value is ENABLE.

The variables in this message are:

applServer - the name of the application server with the SERVER parameter set to DISABLE
addrSpaceId - the internal identity assigned to the application server address space
suffix - unique 1-character suffix identifying the ECAPARM configuration file that contains the SERVER parameter set to DISABLE

The specified application server is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP48W CHANNEL ENTRY(`entryId`), PARAMETERS APPLID= OR APPLIDS=(,) REQUIRED WHEN PROTOCOL=SNA AND MODEL=DC, CHANNEL DISABLEDLink copied to clipboard

Explanation: Either the APPLID or APPLIDS parameters is missing for the SNA channel entry in the ECAPARM configuration file. When the PROTOCOL parameter is SNA and the MODEL parameter is DC, either the APPLID or the APPLIDS parameter must be specified in the ECAPARM configuration file.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP49E CHANNEL ENTRY(`entryId`), MANDATORY PARAMETER PROTOCOL= WAS NOT SPECIFIED, CHANNEL DISABLEDLink copied to clipboard

Explanation: The PROTOCOL parameter is not defined for the specified channel.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled. Normal processing continues.

Corrective Action: Set a value for the PROTOCOL parameter in the ECAPARM configuration file and restart IOAGATE.

ECAP4AS TASK-TO-ATTACH ENTRY(`x`) CHANNEL(`channelId`) INVALID STDTYPE(`type`) IN DESCRIPTORLink copied to clipboard

Explanation: A severe internal error occurred during processing of the ECAPARM configuration file.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP4BW CHANNEL(`channelId`) NUMBER OF SUPPORTED APPLICATIONS PER CHANNEL EXCEEDED MAXIMUM(`num`) APPLICATION(`applicId`) IGNOREDLink copied to clipboard

Explanation: Too many APSERVER definitions reference the same channel. During initialization, IOAGATE reads and checks the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

channelId - the identity of the problematic channel
num - the maximum number of applications each channel can support
applicId - the identity of the application that exceeded the maximum number of applications

The identified application is ignored. Processing continues.

Corrective Action: Reduce the number of applications that reference the same channel, and restart IOAGATE.

ECAP4CW CHANNEL ENTRY(`entryId`) APPLID= NOT SPECIFIED, SNA CHANNEL DISABLEDLink copied to clipboard

Explanation: No APPLID parameter is specified for an SNA communication channel in the ECAPARM configuration file. For an SNA channel, an APPLID parameter must be specified. It may be specified with or without a NETWMAP parameter.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4DW CHANNEL ENTRY(`entryId`), PORT= VALUE MUST BE IN THE RANGE FROM 1024 THROUGH 65534Link copied to clipboard

Explanation: This warning message indicates that the PORT parameter value specified in the ECAPARM configuration file is invalid.

The PORT parameter value must be in the range from 1024 through 65534.

In this message, entryId is the identity of the channel for which the PORT parameter was defined.

The specified channel is disabled and processing continues.

Corrective Action: Correct the value of the PORT parameter in the ECAPARM configuration file and restart IOAGATE.

ECAP4EW CHANNEL ENTRY(`entryId`), SUBPARAMETERS OF APPLIDS= PARAMETER ARE EQUAL, CHANNEL DISABLEDLink copied to clipboard

Explanation: The same subparameter value is specified twice for the APPLIDS parameter for the specified channel in the ECAPARM configuration file.

In this message, entryId is a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file.

The specified CHANNEL definition is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4FW CHANNEL ENTRY(`entryId`), SUBPARAMETER(`subparm`) OF APPLIDS= IS INVALIDLink copied to clipboard

Explanation: An invalid subparameter is specified for the APPLIDS parameter for the channel entry in the ECAPARM configuration file.

The variables in this message are:

entryId - a sequential number that identifies the problematic CHANNEL definition in the ECAPARM configuration file
subparm - the identity of the invalid subparameter

The specified CHANNEL definition is disabled and normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4GE NO APPLICATION SERVER AVAILABLELink copied to clipboard

Explanation: There is no valid APSERVER definition in the ECAPARM configuration file. If there are any APSERVER definitions in the ECAPARM configuration file, they are invalid or disabled.

IOAGATE shuts down.

Corrective Action: Do the following:

Check any other error messages that precede this one.
Correct the ECAPARM configuration file.
Restart IOAGATE.

ECAP4HS PROCESSING TABLE OF DEFAULTS(ECAPDEF) FAILEDLink copied to clipboard

Explanation: A severe internal error occurred during the processing of the ECAPDEF table of numeric parameters defaults.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP4IE ECAPARM(`suffix`) VALIDITY CHECK FAILED, `handler` WAS THE LAST WORKED PROCESSORLink copied to clipboard

Explanation: One or more errors occurred during the processing of the ECAPARM configuration file. This caused the file to fail a validity check, and processing of the file stopped.

The variables in this message are:

suffix - a 1-character suffix that identifies the ECAPARM configuration file
handler - the subroutine that was last active during the processing of the ECAPARM configuration file

IOAGATE shuts down.

Corrective Action: Do the following:

Check other error messages that precede this one.
Correct the ECAPARM configuration file.
Restart IOAGATE.

ECAP4JW GATEWAY PARAMETER(`parm`) OUT OF RANGE(`min-max`), DEFAULT(`defaultValue`) SETLink copied to clipboard

Explanation: When processing the GATEWAY section of the ECAPARM configuration file, IOAGATE detected that the value of the numeric parameter parm predefined in the ECAPDEF table of numeric defaults is invalid.

The variables in this message are:

parm - the name of the parameter with the invalid value
min - the minimum valid value of the parm parameter
max - the maximum valid value of the parm parameter
defaultValue - the default value of the parm parameter

The parm parameter is set to the default value defaultValue. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4KW entryType ENTRY(`entryId`), PARAMETER(`parm`) OUT OF RANGE(`min-max`), VALUE(`value`) SETLink copied to clipboard

Explanation: When processing the ECAPARM configuration file, IOAGATE found that the value of the numeric parameter parm was invalid.

The variables in this message are:

entryType - the section of the ECAPARM configuration file that contains the invalid parameter. Valid values are:
- CHANNEL - the channel definitions section
- APSERVER - the application server definitions section
entryId - a sequential number that identifies the definition entry in the ECAPARM configuration file that contains the invalid parameter
parm - the name of the invalid parameter
min - the minimum valid value of the parm parameter
max - the maximum valid value of the parm parameter
value - the value of the parm parameter that has been set

The parm parameter is set to the default value value. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4LE `entryType` ENTRY(`entryId`), MANDATORY PARAMETER(`parm`) OUT OF RANGE(`min -max`)Link copied to clipboard

Explanation: When processing the ECAPARM configuration file, IOAGATE found that the value of the mandatory numeric parameter parm was invalid.

The variables in this message are:

entryType - the section of the ECAPARM configuration file that contains the invalid mandatory numeric parameter parm. Valid values are:
- CHANNEL - the channel definitions section
- APSERVER - the application server definitions section
entryId - a sequential number that identifies the definition entry in the ECAPARM configuration file that contains the invalid parameter
parm - the name of the invalid parameter
min - the minimum valid value of the parm parameter
max - the maximum valid value of the parm parameter

The parm parameter is ignored. IOAGATE tries to continue processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4ME `entryType` ENTRY(`entryId`), MANDATORY PARAMETER(`parm`) WAS NOT SPECIFIEDLink copied to clipboard

Explanation: When processing the ECAPARM configuration file, IOAGATE found that no value had been set for the mandatory parameter parm.

The variables in this message are:

entryType - the section of the ECAPARM configuration file that contains the mandatory parameter parm. Valid values are:
- CHANNEL - the channel definitions section
- APSERVER - the application server definitions section
entryId - a sequential number that identifies the definition entry in the ECAPARM configuration file that contains the parameter that lacks a value
parm - the name of the mandatory parameter that lacks a value

The parm parameter is ignored. IOAGATE tries to continue processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4NE GATEWAY MANDATORY PARAMETER(`parm`) OUT OF RANGE(`min -max`)Link copied to clipboard

Explanation: When processing the GATEWAY section of the ECAPARM configuration file, IOAGATE detected that the value of the mandatory numeric parameter parm is invalid.

The variables in this message are:

parm - the name of the invalid parameter
min - the minimum valid value of the parm parameter
max - the maximum valid value of the parm parameter

The parm parameter is ignored. IOAGATE tries to continue processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4OE GATEWAY MANDATORY PARAMETER(`parm`) WAS NOT SPECIFIEDLink copied to clipboard

Explanation: When processing the GATEWAY section of the ECAPARM configuration file, IOAGATE detected that no value had been set for the mandatory parameter parm.

In this message, parm is the name of the mandatory parameter that lacks a value.

The parm parameter is ignored. IOAGATE tries to continue processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4PE CHANNEL(`channelId`) NETWORK MAP REQUIRED BY APSERVER, APPL.SERVER(`applicId`) DISABLEDLink copied to clipboard

Explanation: The channel channelId does not contain any network map specification. A network map specification is required by the application server applicId linked to this channel.

The variables in this message are:

channelId - the identity of the problematic channel
applicId - the identity of the application server that requires network map specification

The channel channelId is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4QW CHANNEL(`channelId`) DISABLEDLink copied to clipboard

Explanation: When trying to process a network map specified in the channel channelId, IOAGATE found the channel disabled.

In this message, channelId is the identity of the disabled channel.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4RW APPL.SERVER(`applicId -add_space_id. channelId`) DISABLEDLink copied to clipboard

Explanation: The application server identified in the message is disabled.

The variables in this message are:

applicId - the identity of the disabled application
add_space_id - the identity of the application server address space of the disabled application
channelId - the identity of the channel to which the problematic application server was linked

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4SS ALL CHANNELS DISABLED, PROCESSING STOPPEDLink copied to clipboard

Explanation: IOAGATE monitor has shut down, because all channels were disabled during the processing of the ECAPARM configuration file.

IOAGATE has shut down.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4TE CHANNEL(`channelId`) DISABLED, PARAMETER BIND= CANNOT BE SPECIFIED FOR SNA CHANNELLink copied to clipboard

Explanation: The TCP parameter BIND has been specified for channelId, an SNA channel. This channel has been disabled. The TCP parameter BIND cannot be specified for a SNA channel.

In this message, channelId is the identity of the disabled channel.

The channel is disabled. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4UE CHANNEL(`channelId`) DISABLED, BAD IP ADDRESS SPECIFIED IN BIND= PARAMETERLink copied to clipboard

Explanation: An invalid IP address was specified in the BIND parameter.

In this message, channelId is the identity of the TCP channel that detected the problem.

The channel is disabled. Processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4VS ALL CHANNELs DISABLED, `monitorId` IS GOING DOWN.Link copied to clipboard

Explanation: IOAGATE monitor is shutting down because all channels have become disabled.

In this message, monitorId is the STC name of the IOAGATE started task.

IOAGATE shuts down.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4WS VALUE OF THE `parm` NUMERIC PARAMETER(`val`) EXCEEDS WORKABLE MAXIMUMLink copied to clipboard

Explanation: When processing the ECAPARM configuration file, IOAGATE found that the value val set for the numeric parameter parm exceeds a workable maximum.

The variables in this message are:

parm - the identity of the parameter in which the error was found
val - the invalid value of the problematic parameter

The parm parameter is ignored. Normal processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4XS `entry_typ` NUMERIC PARAMETER(`parm`) NOT FOUND IN ECAPDEFLink copied to clipboard

Explanation: A severe internal error occurred during the processing of the ECAPDEF table of numeric parameter defaults. A numeric parameter was not found in the ECAPARM configuration file.

The variables in this message are:

entry_typ - the name of the section of the ECAPARM configuration file that should contain the parm parameter. Valid values are:
- GATEWAY - the global IOAGATE definitions section
- CHANNEL - the channel definitions section
- APSERVER - the application server definitions section
parm - the identity of the problematic parameter

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP4YE CHANNEL(`channelId`) DISABLED, PARAMETER SHRDBIND= CANNOT BE SPECIFIED FOR SNA CHANNELLink copied to clipboard

Explanation: The TCP parameter SHRDBIND was encountered in an SNA channel. The TCP parameter SHRDBIND cannot be specified for an SNA channel.

In this message, channelId is the identity of the TCP channel that detected the problem.

IOAGATE disables the specified channel and tries to continue normal processing.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP4ZW CHANNEL ENTRY(`channelId`), LOGINMSG= CANNOT BE SPECIFIED FOR THE DC CHANNEL, PARAMETER IGNOREDLink copied to clipboard

Explanation: The LOGINMSG parameter was specified for the channelId channel, but channelId is not an MC channel.

The LOGINMSG parameter can only be specified for an MC channel.

IOAGATE disables the LOGINMSG parameter. Normal processing continues.

Corrective Action: Correct the channel definition.

ECAP50I ECAPARM(`suffix`) HAS BEEN PROCESSED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that processing of the ECAPARM configuration file has ended successfully.

In this message, suffix is a 1-character suffix that identifies the ECAPARM configuration file

Corrective Action: No action is required.

ECAP51S PROCESSING OF ECAAPPL(`suffix`) SUPPORTED APPLICATIONS TABLE HAS FAILEDLink copied to clipboard

Explanation: A severe error occurred during the processing of the internal table of applications supported by IOAGATE.

During initialization, IOAGATE reads and verifies the declarations specified in the internal table of applications supported by IOAGATE. The same table is processed by IOAGATE and by each application server that communicates with this IOAGATE.

In this message, suffix is a unique 1-character suffix that identifies an ECAAPPL table of supported applications.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP52I ECAAPPL(`suffix`) SUPPORTED APPLICATIONS TABLE HAS BEEN PROCESSED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that processing of the internal table of the applications supported by the IOAGATE succeeded.

In this message, suffix is a unique 1-character suffix that identifies an ECAAPPL table of supported applications.

Corrective Action: No action is required.

ECAP53S ECAPRM INTERNAL ERROR, DESCRIPTOR ADDRESS UNAVAILABLELink copied to clipboard

Explanation: A severe internal error occurred during the processing of the ECAPARM configuration file. A descriptor address was not found.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP54S ECAPRM INTERNAL ERROR, FAILURE TO LOCATE MCT TOKENLink copied to clipboard

Explanation: A severe internal error occurred during processing of the ECAPARM configuration file. An MCT token was not found.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP55W APSERVER(`applicId`), PARAMETER `parm` (`val`) CANNOT BE MODIFIED WITH VERSION(`version`)Link copied to clipboard

Explanation: The specified parameter parm cannot be modified by the VERSION parameter, because the value of parm already has eight characters, which is the maximum. The VERSION parameter modifies a parameter by adding a 1-character version code to the existing value.

During initialization, IOAGATE reads and verifies the declarations specified in the ECAPARM configuration file. The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

applicId - the identity of the application
parm - the parameter to be modified
val - the current value of the parameter
version - the value of the VERSION parameter that cannot be used

The VERSION parameter is ignored and processing continues.

Corrective Action: Correct the value assigned to VERSION and restart IOAGATE.

ECAP56S THERE IS A SEVERE STRUCTURE ERROR IN ECAAPPL(`suffix`) SUPPORTED APPLICATIONS TABLELink copied to clipboard

Explanation: A severe internal error occurred during ECAAPL processing. The structure of the internal table of applications supported by IOAGATE was found to be invalid.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP57W APPL APSERVER ENTRY(`entryId`), ALIAS= VALUE CAN BE DEFINED IN CM ENTRY ONLYLink copied to clipboard

Explanation: The value specified for the ALIAS parameter in the internal table of supported applications is valid only for a CM type application server.

In this message, entryId is a sequential number that identifies the problematic APSERVER definition in the internal table of supported applications.

Initialization continues.

Corrective Action: Contact BMC Customer Support.

ECAP58S ECAPRM INTERNAL ERROR, BAD MCT ADDRESS OBTAINEDLink copied to clipboard

Explanation: A severe internal error occurred during the processing of the ECAPARM configuration file. The MCT address is not valid.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP59E APPL APSERVER(`applicId`), CMPRSTYP= PARAMETER IS A MUST WHEN COMPRESS=YES SPECIFIEDLink copied to clipboard

Explanation: An internal error encountered during the processing of the ECAAPPL table of internal parameters. The CMPRSTYP parameter is not specified in the internal table of supported applications, but the COMPRESS parameter is set to YES.

During initialization, IOAGATE reads and verifies the declarations specified in the internal table of applications supported by the IOAGATE. The same table is processed by IOAGATE and by each application server that communicates with this IOAGATE.

In this message, applicId is the problematic APSERVER definition in the internal table of supported applications.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5AE ECAPARM `(suffix`) PROCESSING FAILED, RC=`rc`Link copied to clipboard

Explanation: An internal error occurred during the processing of the ECAPARM configuration file.

The variables in this message are:

suffix - a 1-character suffix that identifies a unique ECAPARM configuration file used in this IOAGATE run
rc - a return code indicating the failure levelValid values for rc are:

Return Code	Explanation
08	An error occurred during ECAPARM processing. The ECAPARM processor is able to continue ECAPARM processing.
12	An error occurred during ECAPARM processing. The ECAPARM processor is NOT able to continue ECAPARM processing.

As indicated in the valid values for rc.

Corrective Action: Do the following:

Examine the IOAGATE logs, and try to determine the cause of the problem.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAP5BS ECAAPL INTERNAL ERROR, ECAAPPL DESCRIPTOR ADDRESS UNAVAILABLELink copied to clipboard

Explanation: A severe internal error occurred during the processing of the specified table of internal parameters during initialization. The ECAAPL internal routine did not get the address of the ECAAPPL descriptor.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5CS ECAAPL INTERNAL ERROR, NO PARAMETERS OBTAINEDLink copied to clipboard

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5DS ECAAPL INTERNAL ERROR, NO APPLICATION ENTRY OBTAINEDLink copied to clipboard

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5EE IMPROPER CHANNEL(`channelId.protocol`) SPECIFIED FOR APPL.SERVER (`applServer.addrSpaceId`), APPL.SERVER DISABLEDLink copied to clipboard

Explanation: The channel specified by the CHANID parameter in an APSERVER definition in the ECAPARM configuration file is not appropriate for the application declared by the definition.

During initialization, IOAGATE reads and checks the ECAPARM configuration file The same ECAPARM configuration file is processed by IOAGATE and by each application server that communicates with this IOAGATE.

The variables in this message are:

channelId - the identity of the problematic channel
protocol - the communication protocol of the problematic channel
applServer - the identity of the problematic application server
addrSpaceId - the internal identity of the problematic application server address space

The indicated application server applServer is disabled and processing continues.

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP5FS ECAAPL INTERNAL ERROR, FAILURE TO LOCATE MCT TOKENLink copied to clipboard

Explanation: A severe internal error occurred during the processing of the specified table of internal parameters during initialization. The ECAAPL internal routine did not find the MCT token.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP5GI ECAPARM(`suffix`) CONFIGURATION FILE HAS BEEN PROCESSED WITH RC(04)Link copied to clipboard

Explanation: This information message indicates that processing of the ECAPARM configuration file has ended with minor errors.

In this message, suffix is a 1-character suffix that identifies the ECAPARM configuration file

Corrective Action: Correct the ECAPARM configuration file and restart IOAGATE.

ECAP60I ECASRVT SERVICES TABLE HAS BEEN PROCESSED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that processing of the ECASRVT internal table of services succeeded. During initialization, IOAGATE processes the ECASRVT internal table of services or request types supported by IOAGATE.

Corrective Action: No action is required.

ECAP61S PROCESSING OF ECASRVT SERVICES TABLE FAILEDLink copied to clipboard

Explanation: Processing of the ECASRVT internal table of services or types of transactions supported by IOAGATE failed. This is a severe internal error.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP6BS ECASRV INTERNAL ERROR, ECASRVT DESCRIPTOR ADDRESS UNAVAILABLELink copied to clipboard

Explanation: This is a severe internal error. The ECASRV internal routine did not get a descriptor address to process during processing of the ECASRVT internal table of services.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP6CS ECASRV INTERNAL ERROR, NO PARAMETERS OBTAINEDLink copied to clipboard

Explanation: This is a severe internal error. The ECASRV internal routine did not get any parameters during processing of the ECASRVT internal table of services.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP6DS ECASRV INTERNAL ERROR, NO SERVICE ENTRY OBTAINEDLink copied to clipboard

Explanation: This is a severe internal error. The ECASRV internal routine did not get any entry to process during processing of the ECASRVT internal table of services.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP6FS ECASRV INTERNAL ERROR, FAILURE TO LOCATE MCT TOKENLink copied to clipboard

Explanation: This is a severe internal error. The ECASRV internal routine could not find an MCT token during processing of the ECASRVT internal table of services.

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAP80S CHANNEL(`channelId.`TCP) HAS GONE DOWN DUE TO NO COMTASK AVAILABLELink copied to clipboard

Explanation: This is a severe error that can be issued for a multiple connection (MC) TCP communication channel only. All communication tasks that belong to the specified channel terminated.

In this message, channelId is the identity of the problematic channel.

This message follows ECAP88S. For more information, see messages ECAP86W, ECAP87W and ECAP88S.

The multiple connection (MC) TCP channel goes down, and processing continues.

Corrective Action: Do the following:

Examine IOAGATE logs to try to determine why the communication tasks went down.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAP82S CHANNEL(`channelId`.TCP) NO COMTASK INITIALIZED DURING LAST `interval` secLink copied to clipboard

Explanation: A severe error was encountered during initialization of the multiple connection TCP channel. No communication task launched by the channel started during the specified time interval.

The variables in this message are:

channelId - the identity of the problematic TCP channel
interval - the time interval (in seconds) during which no communication task succeeded in initializing

The specified TCP channel goes down. IOAGATE tries to continue processing.

Corrective Action: Do the following:

Examine the IOAGATE logs to try to determine the cause of the failure.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAP83W CHANNEL(`channelId`.TCP) DISABLEDLink copied to clipboard

Explanation: This message warns that the channelId MC TCP channel has been disabled because an EADDRINUSE error occurred while IOAGATE was trying to bind the port specified in the BIND parameter in ECAPARM.

When IOAGATE goes down, this message is issued for a DC type channel
When CTMAS of the same installation is active on the same or another LPAR in the SYSPLEX, the DC channel used for communications with Control-M/EM is disabled. IOAGATE will go down if no other channels are defined for the same IOAGATE, but will stay up if there are additional channels which are OK.

Corrective Action: No action is required.

ECAP86W CHANNEL(`channelId`.TCP) COMTASK(`taskId`) CANNOT BE STARTED ANY MORE, THRESHOLD OF RESTARTS(`threshold`) REACHEDLink copied to clipboard

Explanation: A communication task of a multiple connection TCP channel has already shut down and restarted the maximum number of times. When an error prevents a TCP communication task from working normally, the TCP channel tries to resolve the problem by recycling the task. However, beyond a defined limit, the TCP channel assumes a severe problem, and prevents further recycling of the task.

This message can be issued for a multiple connection TCP channel only.

The variables in this message are:

channelId - the identity of the channel that has the problematic task
taskId - the internal identity of the problematic TCP communication task
threshold - the internally defined maximum number of times to recycle a communication task

Corrective Action: Do the following:

Examine the IOAGATE logs to try to determine the cause of the failure.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAP87W CHANNEL(`channelId`.TCP) `num` COMTASKS AMONG(`channel_amount`) DEFINED TO CHANNEL TERMINATEDLink copied to clipboard

Explanation: The specified number (num) of communication tasks became unavailable to a multiple connection (MC) TCP communication channel. A serious problem may be preventing the specified TCP channel from working properly. An ECAP86W message is issued before this message for each communication task that terminated.

This message can only be issued for a multiple connection (MC) TCP communication channel.

The variables in this message are:

channelId - the identity of the problematic channel
num - the number of communication tasks that terminated
channel_amount - the number of communication tasks configured to the specified channel

Corrective Action: Do the following:

Examine the IOAGATE logs to try to determine the cause of the failure.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAP88S CHANNEL(`channelId`.TCP) ALL COMTASKS DEFINED TO CHANNEL(`num`) TERMINATEDLink copied to clipboard

Explanation: No more active communication tasks are available for the specified channel. All communication tasks terminated, and none is allowed to restart. ECAP86W warning messages were previously issued for each communication task that went down. This message precedes message ECAP80S. For more information, see message ECAP86W.

This message can only be issued for a multiple connection (MC) TCP communication channel.

The variables in this message are:

channelId - the identity of the problematic channel
num - the number of communication tasks configured to the specified channel in the ECAPARM configuration file

The specified channel goes down and processing continues. If the indicated channel is the only one configured to IOAGATE, IOAGATE shuts down.

Corrective Action: Do the following:

Examine the IOAGATE logs to try to determine the cause of the failure.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAP90I ECAIPLS(`suffix`) IP LIST HAS BEEN {PROCESSED | REFRESHED} SUCCESSFULLY FOR CHANNEL(`channel`)Link copied to clipboard

Explanation: This information message indicates that the IP list member was specified in the ECAPARM member for channel channel by means of the IPLIST parameter, and the IP list member was processed or refreshed (if the REFRESH command was issued) successfully.

The variables in this message are:

suffix - one-character suffix used to specify the individual ECAIPLS x IP list member name
channel - channel identity that the indicated ECAIPLS x IP list specified

Corrective Action: No action is required.

ECAP91I CHANNEL(`channel`) ECAIPLS(`suffix`) IP LIST MEMBER IS BEING CHECKEDLink copied to clipboard

Explanation: This information message indicates which specific IP list member is being processed. The message is issued in DAIGLOG output as a header for the group of ECAP93I messages issued for each line in the IP list member.

The variables in this message are:

channel - channel identity for which the indicated ECAIPLS x IP list was specified
suffix - one-character suffix used to specify the individual ECAIPLS x IP list member name

Corrective Action: No action is required.

ECAP92I END OF ECAIPLS(`suffix`) IP LIST MEMBERLink copied to clipboard

Explanation: This information message indicates which specific IP list member was processed. The message is issued in DAIGLOG output as a footer after the group of ECAP93I messages issued for each line in the IP list member.

In this message, suffix is a one-character suffix used to specify the individual ECAIPLS x IP list member name.

Corrective Action: No action is required.

ECAP93I `indication number: IPListLine`Link copied to clipboard

Explanation: This information message is issued in DAIGLOG output for each source IPListLine in the IP list member.

The variables in this message are:

indication - a short string indicating the result of a source IPListLine processing

Valid values of indication are:

indication	Explanation
no indication	Indicates that no error was detected in an IP list source line.
ERROR `code` FOUND	Indicates that an error with hexadecimal code `code` was found in an IP list source line. When such an indication is issued, message ECAP94I follows message ECAP93I and specifies an approximate column where the error detected. Additionally, another error message follows message ECAP94I to specify the exact reason for the error.
RECORD IGNORED	Indicates that an IP list source line was ignored because another line in the IP list repeats the current line. Message ECAP9BW that follows message ECAP93I specifies the sequential number of the duplicate line.
ALLOW IGNORED	Indicates that an IP list source line was ignored because there is a FORBID line in the IP list that was specified for the same IP address and a mask. Message ECAP9CE that follows message ECAP93I specifies the number of the FORBID line.
COMMENT LINE	Indicates that an IP list source line has an asterisk in the first column. The line is not processed.
BLANKED LINE	Indicates that an IP list source line contains no valid characters. The line is not processed.

number - the sequential number of an IP list source line
IPListLine - the contents of an IP list source line

Corrective Action: No action is required.

ECAP94I NEAR COLUMN NUM.`column`:Link copied to clipboard

Explanation: This information message is issued in DAIGLOG output. It follows message ECAP93I when an error is detected in an IP list source line and indicates the approximate column where the error was detected. The message is issued for a source IP line when an error is detected in the line.

In this message, column is the approximate sequential number of the column in the IP list source line where the error was detected.

Corrective Action: No action is required.

ECAP95E EMPTY `section` SECTIONLink copied to clipboard

Explanation: No character was found between dots that form a section in a mask or IP address in the IP list source line indicated by message ECAP93I.

In this message, section is a portion of a mask or an IP address string between dots. Valid values are:

ADDRESS
MASK

The following system actions occur:

The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP96E VALUE IN SECTION EXCEEDS 255Link copied to clipboard

Explanation: A value specified in a separate section of a mask or IP address exceeds 255 in the IP list source line indicated by message ECAP93I. The section is a portion of a mask or an IP address string between dots.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP97E WRONG USAGE OF AN ASTERISK IN `section`Link copied to clipboard

Explanation: An asterisk was improperly specified in a separate section of a mask or IP address in an IP list source line indicated by message ECAP93I. An asterisk can be specified in the first through fourth contiguous right-to-left sections of an IP address. An asterisk in a mask is not allowed.

In this message, section is a portion of a mask or an IP address string between dots. Valid values are:

ADDRESS
MASK

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP98E WRONG NUMBER OF SECTIONS IN {ADDRESS | MASK}Link copied to clipboard

Explanation: The number of sections in a mask or IP address is not exactly four in the IP list source line indicated by message ECAP93I.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP99E NEITHER ALLOW NOR FORBID STATEMENTLink copied to clipboard

Explanation: A main keyword in the IP list source line indicated by message ECAP93I could not be identified. Each valid IP line must have either ALLOW or FORBID as a keyword.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP9AE INVALID CHARACTER DETECTEDLink copied to clipboard

Explanation: An invalid character was detected in the IP list source line indicated by message ECAP93I. Message ECAP94I, which precedes message ECAP9AE, specifies the exact column where the invalid character was detected.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP9BW DUE TO DUPLICATE RECORD NUMBER:`number`Link copied to clipboard

Explanation: An IP list source line was ignored because there is a duplicate line in the IP list.

In this message, number is the number of the duplicate IP list source line.

Corrective Action: Correct the IP list member and try again.

ECAP9CW DUE TO FORBID RECORD NUMBER:`number` SPECIFIED FOR THE SAME ADDRESSLink copied to clipboard

Explanation: This warning indicates that the ALLOW IP list source line was ignored because the FORBID line in the IP list was specified for the same IP address and a mask as in the ignored line.

In this message, number is the number of the FORBID line in the IP list.

Corrective Action: Correct the IP list member and try again.

ECAP9DE WRONG MASK: INCONSECUTIVE (FROM LEFT TO RIGHT) BITS DETECTEDLink copied to clipboard

Explanation: Inconsecutive bits were detected in a mask specified in the IP list source line that was indicated by message ECAP93I. The mask should be built with consecutive, left-to-right bits only.

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP9ES SEVERE ERROR ENCOUNTERED; ROUTINE(`routine`) RC(`rc`) REASON(`reason`)Link copied to clipboard

Explanation: A severe error, with an rc return code and reason reason, was detected by the routine internal routine.

The variables in this message are:

routine - the name of the routine in which the indicated error case was detected.Valid values for routine are:
- IOAIPCV
- IOAIPLS
- IOAIPSH
rc - a non-zero error return code
reason - the hexadecimal error code specifying an exact error case.

The following system actions occur:

Processing stops.
The channel for which the IP list is defined is disabled.

Corrective Action: Contact BMC Customer Support.

ECAP9FS INTERNAL ERROR ENCOUNTERED; ROUTINE(`routine`) RC(`rc`) REASON(`reason`)Link copied to clipboard

Explanation: A severe internal error, with an rc return code and reason reason, was detected by the routine internal routine.

The variables in this message are:

routine - the name of the routine in which the indicated error case was detected.Valid values for routine are:
- IOAIPCV
- IOAIPLS
- IOAIPSH
rc - a non-zero error return code
reason - the hexadecimal error code specifying an exact error case.

The following system actions occur:

Processing stops.
The channel for which the IP list is defined is disabled.

Corrective Action: Contact BMC Customer Support.

ECAP9GE IOAMEM SERVICE DETECTED AN ERROR; ROUTINE(`routine`) RC(`rc`) REASON(`reason`)Link copied to clipboard

Explanation: The IOAMEM service detected an error when handling an IP list member. The IOAMEM routine is used when reading PDS members.

The variables in this message are:

routine - the name of the routine in which the indicated error case was detected.Valid values for routine are:
- IOAIPLS
- IOAIPSH
rc - a non-zero error return code
reason - the hexadecimal error code specifying an exact error case.

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: If it is not possible to locate the source of the error, contact BMC Customer Support.

ECAP9HW SYNTAX ERROR DETECTED IN ECAIPLS(`suffix`) IP LIST MEMBER, CHANNEL(`channel`)Link copied to clipboard

Explanation: A syntax error was detected in an IP list member. Detailed messages specifying both the exact error and its location are issued in DAIGLOG output. See message ECAP93I.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

Processing continues.
The channel for which the IP list is defined is disabled.

Corrective Action: Correct the IP list member and try again.

ECAP9IS UNKNOWN ERROR ENCOUNTERED; ROUTINE(`routine`) RC(`rc`) REASON(`reason`)Link copied to clipboard

Explanation: An unknown error, with an rc return code and reason reason, was detected by the routine internal routine.

The variables in this message are:

routine - the name of the routine in which the indicated error case was detected.Valid values for routine are:
- IOAIPCV
- IOAIPLS
- IOAIPSH
rc - a non-zero error return code
reason - the hexadecimal error code specifying an exact error case.

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.

Corrective Action: Contact BMC Customer Support.

ECAP9JE FAILURE TO LOAD MODULE `module`Link copied to clipboard

Explanation: The module module failed to load.

In this message, module is the name of the module that failed to load.

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.

Corrective Action: Contact BMC Customer Support.

ECAP9KE SPECIFIED IP LIST MEMBER ECAIPLS(`suffix`) DOES NOT EXIST, CHANNEL(`channel`)Link copied to clipboard

Explanation: The specified IP list member could not be located in a dataset allocated by DAPARM DD statement.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9LE EMPTY IP LIST MEMBER ECAIPLS(`suffix`) SPECIFIED, CHANNEL(`channel`)Link copied to clipboard

Explanation: The specified IP list member was found to be empty.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9ME INVALID IP LIST MEMBER `member`(`suffix`) NAME SPECIFIED, CHANNEL(`channel`)Link copied to clipboard

Explanation: This error message indicates that an invalid name was specified for the channel channel in ECAPARM as an IP list. A valid name should be ECAIPLS(suffix).

The variables in this message are:

member - the member name specified in the IPLIST channel parameter.
suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9NE MORE THAN 999 RECORDS SPECIFIED IN IP LIST MEMBER ECAIPLS(`suffix`), CHANNEL(`channel`)Link copied to clipboard

Explanation: The specified IP list member contains more than 999 lines.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9OE THERE IS NO VALID RECORD IN SPECIFIED IP LIST MEMBER ECAIPLS(`suffix`), CHANNEL(`channel`)Link copied to clipboard

Explanation: No valid lines were found in the specified IP list member.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9PE HEADER RECORD NOT FOUND IN SPECIFIED IP LIST MEMBER ECAIPLS(`suffix`), CHANNEL(`channel`)Link copied to clipboard

Explanation: No header record was found in the specified IP list member. The IP list member must have ALLOW * or FORBID* as its first valid record.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

IP list processing stops.
The channel for which the IP list is defined is disabled.
Processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9QW FAILURE TO REFRESH IP LIST MEMBER ECAIPLS(`suffix`) FOR CHANNEL(`channel`)Link copied to clipboard

Explanation: The F monitor,REFRESH=IPListMember modify command was issued but was unsuccessful, probably due to syntax errors detected in the specified IP list member.

The variables in this message are:

suffix - the one-character suffix used to specify the individual ECAIPLS x IP list member name.
channel - the channel identity for which the indicated ECAIPLS x IP list is specified

The following system actions occur:

No changes are performed.
Normal processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9RW CANNOT REFRESH MEMBER `member`: NOT DEFINED IN A CHANNELLink copied to clipboard

Explanation: The F monitor,REFRESH=IPListMember modify command specified an IP list member name that is not defined in any channel.

In this message, member is the IP list (ECAIPLS x) member name.

No changes are performed. Normal processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9SE REFRESH FOR(`member`) FAILED WITH RC(`rc`) REASON(`reason`)Link copied to clipboard

Explanation: The F monitor,REFRESH=IPListMember modify command was issued but was unsuccessful, probably due to internal errors encountered when processing the specified IP list member.

The variables in this message are:

member - the IP list (ECAIPLS x) member name.
rc - the return code value
reason - the cause of the error

No changes are performed. Normal processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9TE WRONG OR NO VALID DATALink copied to clipboard

Explanation: Wrong or invalid data was detected in the IP list source line indicated by message ECAP93I.

No changes are performed. Normal processing continues.

Corrective Action: Correct the IP list member and try again.

ECAP9UE INVALID IPV6 RECORDLink copied to clipboard

Explanation: A string in an IP source line contains the colon (:) character, but is not a syntactically valid IPv6 address.

The following system actions occur:

If the error occurs during IOAGATE startup, the channel for which the IP list is defined is disabled. If it is the only channel, then IOAGATE will terminate.
If the error occurs during a MODIFY REFRESH command, the refresh fails, but processing continues.

Corrective Action: Correct the IP list member and try again.

Use the following valid IPv6 address formats:

full 39-character format,for example:
- AA12:EF01:2345:FDD6:ABCD:EF01:2345:6789,
zero-suppressed formats, for example:
- 2001:DB8:0:0:8:800:200C:417A
- 2001:DB8::8:800:200C:417A
- ::1

Do not use '/' to abbreviate addresses.

Do not use IPv4-mapped IPv6 addresses. For example:

::ffff:137.72.214.55 – incorrect
137.72.214.55 – correct representation of the above address

ECAP9VE INVALID IPV6 ADDRESS RANGELink copied to clipboard

Explanation: An IP source line contains a range of IPv6 addresses, but the second address is not higher than the first address.

If the range was specified in 2 lines:

ALLOWTO or FORBIDTO was specified before ALLOWFR or FORBIDFR, respectively.
ALLOWFR was not followed immediately by ALLOWTO, or FORBIDFR by FORBIDTO.

The following system actions might occur:

If the error occurs during IOAGATE startup, the channel for which the IP list is defined is disabled. If it is the only channel, then IOAGATE will terminate.
If the error occurs during a MODIFY REFRESH command, the refresh fails but processing continues.

Corrective Action: Correct the IP list member and try again.

ECAPA1E KEYRING PARAMETER IS A MUST IF SSL=YES SPECIFIED, CHANNEL(`channelId`) DISABLEDLink copied to clipboard

Explanation: When SSL=YES is specified in the ECAPARM configuration file, the KEYRING parameter must also be specified.

In this message, channelId is the identity of the channel.

The channel is disabled. If there are no other enabled channels in IOAGATE, IOAGATE shuts down.

Corrective Action: Specify a KEYRING parameter.

ECAPA2E USERID/KEYRING PARAMETER INVALID, CHANNEL(`channelId`) DISABLEDLink copied to clipboard

Explanation: The syntax of the KEYRING parameter is invalid.

In this message, channelId is the identity of the channel.

The channel is disabled. If there are no other enabled channels in IOAGATE, IOAGATE shuts down.

Corrective Action: Specify a proper KEYRING parameter. Refer to the chapter about installing IOA in the INCONTROL for z/OS Installation Guide.

ECAPA3E SSL NOT SUPPORTED BY IOAGATE IN z/OS LEVEL LOWER THAN z/OS 1.4, CHANNEL(`channelId`) DISABLEDLink copied to clipboard

Explanation: SSL support in IOAGATE requires z/OS 1.4 or later.

In this message, channelId is the identity of the channel.

The channel is disabled. If there are no other enabled channels in IOAGATE, IOAGATE shuts down.

Corrective Action: Specify SSL=NO in the ECAPARM configuration file.

ECAPB1I PARAMETER `xxxxxx` SUCCESSFULLY | replaced in | retrieved from | MEMBER `member_name`Link copied to clipboard

Explanation: A parameter in a IOA PARM library member was retrieved or updated by Control-M/Enterprise Manager.

Corrective Action: No action is required.

ECAPB2E RC=(04) REASON=(`reason`) PROCESSING FAILEDLink copied to clipboard

Explanation: An IOA PARM library parameter, which was needed to process a request from the Control-M/Enterprise Manager, could not be located.

Corrective Action:Review recent changes to the CTMAA section of the CTMPARM member in the IOA PARM library and to the member referred to by the ECAPARM parameter in the CTMAA section. Browse or edit the IOA PARM library, to ensure that it is not held exclusively by a TSO user or a job (for example, for compression). If no problem is found, save the IOAGATE and Application Server sysouts and call BMC Customer Support.

ECAPB3E RC=(08) REASON=(`reason`) |INVALID PARAMETER (`n`) RECEIVED| `additional_details`Link copied to clipboard

Explanation:The IOA PARM library editor program was called with invalid parameters. The invalid parameter is identified by n, which is the parameter number in the ECAPMED parameter list.

ECAPB4E RC=(12) REASON=(`reason`) FAILURE TO READ | WRITE | STOW MEMBER `member_name`Link copied to clipboard

Explanation:A failure occurred while reading/writing/saving an IOA PARM library member.

Corrective Action:The failure might occur if the member is being edited in TSO, or the IOA PARM library needs to be compressed. If the problem persists, save the IOAGATE and Application Server sysouts and call BMC Customer Support.

ECAPB5E RC=(24) REASON=(`reason`) INTERNAL ERROR OCCURREDLink copied to clipboard

Explanation:The IOA PARM library editor program encountered a logical error.

Corrective Action:Save the Application Server sysouts and call BMC Customer Support.

Messages ECAT00 through ECATxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

ECAT00I CHANNEL (`channelId.`TCP) `task` (`taskId.type`) LISTENING ON PORT(`port`), IP(`hostIpAdd/*`), APPLICATION (`appl`)Link copied to clipboard

Explanation: This information message displays the host IP address and TCP/IP communication port number on which IOAGATE is listening. The message indicates that the TCP channel has initialized and is waiting for the partner or client to initiate the connection.

The variables in this message are:

channelId - the identity of the TCP channel that is listening to the specified port
task - the name of the communication task of channelId. Valid values are:
- SENDER - the sender side of the dual connection (DC) TCP channel
- RECEIVER - the receiver side of the dual connection (DC) TCP channel
- LISTENER - the manager task of the multiple connection (MC) TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
port - the number of the TCP/IP communication port that the TCP channel is using to listen for connection
hostIpAdd - the IP address on which IOAGATE is listening for incoming connections, which corresponds with the IP address specified in the BIND parameter in ECAPARM
* (Asterisk) - IOAGATE is listening for incoming connections on all IP address (adapters) of the z/OS. Default.
appl - the application supported by the specified channel

Corrective Action: No action is required.

ECAT01E PROBABLE CTM/EM SET UP ERROR: DATACENTER PLATFORM WRONGLY DEFINED AS 'DISTRIBUTED' INSTEAD OF AS 'Z/OS'Link copied to clipboard

Explanation: IOAGATE received a synchronization message from Control-M/Enterprise Manager that is encoded for non z/OS platforms. The error is probably because the Control-M for z/OS is incorrectly defined in the Control-M Configuration Manager.

Corrective Action: Ensure that in the Platform field of the Control-M Definition dialog box, the Control-M is defined as 'z/OS', not as 'distributed'.

ECAT02I CHANNEL(`channelId`.TCP) `task` (`taskId.type`) ESTABLISHED CONNECTION WITH HOST(`hostIpAdd`), APPLICATION(`appl`)Link copied to clipboard

Explanation: This information message indicates that a dual connection (DC) TCP communication channel succeeded in connecting to the specified partner or client.

The variables in this message are:

channelId - the identity of the channel that established connection with a partner or client
task - the communication task of the indicated TCP channel. Valid values are:
- SENDER - the sender side of the dual connection TCP channel
- RECEIVER - the receiver side of the dual connection TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
hostIpAdd - the IP address of the host of the partner or client
appl - the identity of the application supported by the specified channel

Corrective Action: No action is required.

ECAT03I CHANNEL(`channelId`.TCP) `task` (`taskId.type`) TERMINATED CONNECTION WITH HOST(`hostIpAdd`)Link copied to clipboard

Explanation: This information message indicates that the communication task of the specified dual connection (DC) TCP communication channel terminated the connection with its partner or client.

The variables in this message are:

channelId - the identity of the channel that terminated connection with a partner or client
task - the name of the terminated communication task of the specified TCP channel that terminated connection. Valid values are:
- SENDER - the sender side of the dual connection TCP channel
- RECEIVER - the receiver side of the dual connection TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
hostIpAdd - the IP address of the host of the partner or client

Normal processing continues. The dual connection TCP channel will try to re-establish connection to the specified partner or client.

Corrective Action: No action is required.

ECAT04W CHANNEL(`channelId`.TCP) `task` (`taskId.type`) FAILED TO INITIALIZE, WILL RETRY IN A MINUTELink copied to clipboard

Explanation: This message warns that initialization failed during startup of the specified TCP channel. The ECAT05I or the ECAT09I message may accompany this message and explain the reason for the failure.

The variables in this message are:

channelId - the identity of the channel that failed to initialize
task - the communication task of channelId. Valid values are:
- SENDER - the sender side of the dual connection (DC) TCP channel
- RECEIVER - the receiver side of the dual connection (DC) TCP channel
- LISTENER - the manager task of the multiple connection (MC) TCP channel
- COMTASK - the communication task of the multiple connection (MC) TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task

Normal processing continues. After one minute, initialization of the indicated TCP channel is attempted again.

Corrective Action: No action is required.

ECAT05W CHANNEL(`channelId`.TCP) `task` (`taskId.type`) DETECTED EVENT(`errno.errno_id`) STAGE(`stage`) API(`api`) ACTION(`action`)Link copied to clipboard

Explanation: This message warns that the dual connection (DC) TCP channel detected a TCP/IP internal errno event while trying to connect or during data exchange with a partner or client.

Internal TCP/IP errno events are network activities that are intercepted, identified, and processed by TCP/IP software. A unique name and a standard numeric code identify each event.

Internal TCP/IP events usually reflect normal network activity, including error recovery. Only codes that point to application program interface (API) errors indicate potential software defects.

This message ECAT05W is always followed by the ECAT0EI message, which explains the errno event.

The variables in this message are:

channelId - the identity of the channel that detected the event
task - the name of the communication task of the specified TCP channel that detected the event. Valid values are:
- SENDER - the sender side of the dual connection (DC) TCP channel
- RECEIVER - the receiver side of the dual connection (DC) TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
errno - the name of the internal TCP/IP eventFor a description of possible values of errno, refer to the ECAT0EI message that always follows this message.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.
stage - the internal ID of the processing stage at which the event was detected
api - the TCP/IP socket API function that was active when the event was detected
action - the internal action identity that describes how the dual connection (DC) TCP channel will handle the event. Valid values are:
- GO_DOWN - shut down the specified communication task
- CLOSE_GO_DOWN - disconnect, and shut down the specified communication task
- CLOSE_REINIT - disconnect, reset, and initialize the specified communication task
- REINIT - try to initialize the specified communication task again
- IGNORE - ignore the event
- DISABLE - disable the channel

Normal processing continues, and the specified TCP channel handles the event as described by the value of action.

Corrective Action: For information about the detected errno event, refer to the appropriate TCP/IP vendor documentation. If the problem persists, call your network systems programmer for assistance.

ECAT06I CHANNEL(`channelId`.TCP) `task` (`taskId.type`) PARTNER DISCONNECTED APPLICATION(`appl`)Link copied to clipboard

Explanation: This information message indicates that the partner or client disconnected because the dual connection (DC) channel detected an End-Of-File TCP/IP internal errno event.

The variables in this message are:

channelId - the identity of the channel to which the partner was connected
task - the identity of the communication task of channelId. Valid values are:
- SENDER - the sender side of the dual connection channel
- RECEIVER - the receiver side of the dual connection TCP channel
taskId - the internal identity of this communication task
type - the internal type of this communication task
appl - the identity of the application supported by channelId

Normal processing continues. The TCP channel channelId shuts down, is reset, and is initialized again.

Corrective Action: No action is required.

ECAT07I CHANNEL(`channelId`.TCP) `task` (`taskId.type`) READY, APPLICATIONS(`appls`)Link copied to clipboard

Explanation: This information message indicates that a communication task of the specified multiple connection (MC) TCP channel initialized successfully. This information message is issued during multiple connection (MC) TCP channel initialization.

The variables in this message are:

channelId - the identity of the multiple connection (MC) TCP channel that initialized successfully
task - the communication task of the channelId channel. Valid values are:
- LISTENER - the manager task of the multiple connection TCP channel
- COMTASK - the communication task of the multiple connection TCP channel
taskId - the internal identity of the task communication task
type - the internal type of the task communication task
appls - list of the applications supported by the channelId channel

Corrective Action: No action is required.

ECAT08W CHANNEL(`channelId`.TCP) TASK(`taskId`) CONNECT FROM IP(`IPAddress`) FORBIDDENLink copied to clipboard

Explanation: An attempt to connect to IOAGATE has been rejected because the incoming IP address is specified as forbidden in the IP validation list member that is defined for this channel.

The variables in this message are:

channelId - the identity of the channel that received and rejected the connection request
taskId - the internal identity of the channel task that received and rejected the connection request
IPAddress - the IP address from which the connection has been initiated

The connection is closed and normal processing continues.

Corrective Action: No action is required.

ECAT09W CHAN(`channelId`.TCP) `task` (`taskId.type`) EVENT(`errno.errno_id`) SOCK(`socket`) API(`stage.api`) ACT(`action`), RHOST(`hostId`)Link copied to clipboard

Explanation: This message warns that the multiple connection (MC) TCP channel detected a TCP/IP errno event while trying to connect or during data exchange with a partner or client.

Internal TCP/IP errno events are network activities that are intercepted, identified and processed by TCP/IP software. A unique name and a standard numeric code identify each event. Internal TCP/IP events usually reflect normal network activity, including error recovery. Only codes that point to application program interface (API) errors indicate potential software problems.

This message ECAT05W is always followed by the ECAT0EI message, which explains the errno event.

The variables in this message are:

channelId - the identity of the channel that detected the event
task - the name of the communication task of channelId. Valid values are:
taskId - the internal identity of the communication task of channelId
- LISTENER - the manager task of channelId
- COMTASK - the communication task of channelId
type - the internal type of the communication task of channelId
errno - the name of the internal TCP/IP event. For a description of possible errno values, refer to the ECAT0EI message that always follows this message
errno_id - the numeric identifier of the internal TCP/IP event. For a description of possible values of errno_id, see the appropriate TCP/IP vendor documentation
socket - the TCP/IP socket number assigned to this connection within the indicated task
stage - the internal identity of the processing stage at which the event was detected
api - the TCP/IP socket API function that was active when the event was detected
action - the internal action identity that describes how the multiple connection TCP channel will handle the event. Valid values are:
- GO_DOWN - Shut down the specified communication task.
- REINIT - Try to establish the connection again.
- CLEAR - Free resources assigned by the channel to handle this connection.
- DISABLE - Disable the channel.
- IGNORE - Ignore the event.
hostId - the host IP address of the remote partner or client with which channelId is communicating.

Normal processing continues, and the specified TCP channel handles the event as described by the value of action.

Corrective Action: Refer to the appropriate TCP/IP vendor documentation for information about errno_id. If the problem persists, call your network systems programmer for assistance.

ECAT0AI CHANNEL(`channelId`.TCP) `task` (`taskId.type`) SETTING TCPACCESS SUBSYSTEM(`subsystemName`)Link copied to clipboard

Explanation: This information message indicates that the channelId channel is setting up the TCPaccess subsystem name. This message is issued during startup, when the TCP communication channel is configured with the TCPaccess TCP/IP software of Computers Associates International, Inc.

The message is issued only when both the TCPVENDR=CA and SUBSYSTM parameters are specified in the ECAPARM configuration file.

The variables in this message are:

channelId - the identity of the channel for which the TCPVENDR and SUBSYSTM parameters were specified
task - the communication task assigned to channelId. Valid values are:
- RECEIVER - the receiver side of the dual connection (DC) TCP channel
- LISTENER - the manager task of the multiple connection (MC) TCP channel
taskId - the internal identity of task
type - the internal type of task
subsystemName - the subsystem name that the TCPaccess software will use in this IOAGATE run

Corrective Action: No action is required.

ECAT0BI CHANNEL(`channelId.` TCP) `task` (`taskId.type`) PARTNER(`node`) CONNECTED, SOCKET(`socket`) HOST(`host`)Link copied to clipboard

Explanation: The IOAGATE-to-IOAGATE connection has been established. This message is issued when the local IOAGATE has CONNECTOR set to LOCAL.

The variables in this message are:

channelId - the identity of the TCP channel that established the connection
task - the name of the communication task of the indicated TCP channel that established the connection
taskId - the internal identity of task
type - the internal type of task
node - the node identity of the partner IOAGATE with which the connection has been established
socket - the TCP/IP socket number assigned to this connection within the indicated task
host - the identity of the remote host with which the connection has been established

Corrective Action: No action is required.

ECAT0CI CHANNEL(`channelId`.TCP) `task` (`taskId.type`) CONNECTION ACCEPTED FROM NODE(`node`), SOCKET(`socket`) HOST(`host`)Link copied to clipboard

Explanation: The IOAGATE-to-IOAGATE connection has been established. This message is issued when the partner node has CONNECTOR set to local.

The variables in this message are:

channelId - the identity of the TCP channel that established the connection
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the identity of the node of the partner IOAGATE with which the connection has been established
socket - the TCP/IP socket number assigned to this connection within task
host - the identity of the remote host with which the connection has been established

Corrective Action: No action is required.

ECAT0DW CHANNEL(`channelId`.TCP) `task` (`taskId.type`) PARTNER(`node`) DISCONNECTED(`errno`), SOCKET(`socket`)Link copied to clipboard

Explanation: The IOAGATE-to-IOAGATE connection has been disrupted.

The variables in this message are:

channelId - the identity of the TCP channel to which the partner IOAGATE was connected
task - the name of the communication task of channelId to which the partner IOAGATE was connected
taskId - the internal identity of task
type - the internal type of task
node - the identity of the node of the partner IOAGATE to which the partner IOAGATE was connected
errno - the reason of the disconnectionFor a description of possible values of errno, see to the appropriate TCP/IP vendor documentation
socket - the TCP/IP socket number assigned to this connection within task

Normal processing continues. IOAGATE tries to reestablish connection.

Corrective Action: No action is required.

ECAT0EI Event(`errno : explan`)Link copied to clipboard

Explanation: This message always follows the ECAT05W and ECAT09W messages. It displays a short explanation of the errno event that is identified in the preceding ECAT05W or ECAT09W message.

The variables in this message are:

errno - the name of the internal TCP/IP or IOAGATE channel event
explan - short explanation of the errno event specified by the first variable

Corrective Action: No action is required.

ECAT0FS CHANNEL(`channelId`.TCP) `task` (`taskId.type`) BAD IP ADDRESS(`ipAdd`) SPECIFIEDLink copied to clipboard

Explanation: The specified IP address is invalid.

The variables in this message are:

channelId - the identity of the TCP channel that detected the problem
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
ipAdd - the invalid IP address value that caused the problem

The channelId TCP channel goes down.

Corrective Action: Correct the IP address and restart IOAGATE.

ECAT0GS CHANNEL(`channelId`.TCP) `task` (`taskId.type`) UNKNOWN HOST(`hostId`) SPECIFIEDLink copied to clipboard

Explanation: IOAGATE failed to resolve the specified Hostname.

The variables in this message are:

channelId - the identity of the TCP channel that detected the problem
task - the name of the communication task of channelId
taskId - the internal identity of task
type - Internal type of task
hostId - the Hostname that caused the problem

The specified channel goes down.

Corrective Action: Correct the Hostname, or try specifying the IP address instead, and restart IOAGATE.

ECAT0HS CHANNEL(`channelId`.TCP) `task` (`taskId.type`) SOCKET GETTING FAILEDLink copied to clipboard

Explanation: A severe socket API error occurred while trying to get a socket.

The variables in this message are:

channelId - the identity of the TCP channel that detected the problem
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task

IOAGATE shuts down.

Corrective Action: Contact BMC Customer Support.

ECAT0IW CHANNEL(`channelId`.TCP) `task` (`taskId.type`) CONNECT TO PARTNER(`node`) WILL BE RETRIED IN `nn` secLink copied to clipboard

Explanation: An attempt to establish an IOAGATE-to-IOAGATE connection has failed. IOAGATE will retry the attempt after the time interval nn. This message is issued only when the local IOAGATE has CONNECTOR set to LOCAL.

The variables in this message are:

channelId - the identity of the TCP channel that attempted to connect
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the identity of the node of the partner IOAGATE with which connection was attempted
nn - the time interval (in seconds) before another attempt is made to connect

IOAGATE will retry establishing the IOAGATE-to-IOAGATE connection after the time specified (nn seconds).

Corrective Action: No action is required.

ECAT0JE CHANNEL(`channelId`.TCP) `task` (`taskId.type`) HANDSHAKE SENDING TO PARTNER(`node`) FAILED(`errno`)Link copied to clipboard

Explanation: An attempt to send a handshake message to a partner IOAGATE failed.

The variables in this message are:

channelId - the identity of the TCP channel that performed a handshaking attempt
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the node identity of the partner with which IOAGATE was atttempting a handshake
errno - the reason for the disconnectionFor a description of possible values of errno, see the appropriate TCP/IP vendor documentation

Corrective Action: Do the following:

Examine the IOAGATE logs to try to determine the cause of the failure.
If possible, correct the problem and restart IOAGATE.
If the problem persists, contact BMC Customer Support.

ECAT0KE CHANNEL(`channelId`.TCP) `task` (`taskId.type`) CONNECT TO PARTNER(`node`) FAILED, HOST(`hostId`) UNAVAILABLELink copied to clipboard

Explanation: IOAGATE is unable to establish IOAGATE-to-IOAGATE connection because the specified Hostname cannot be resolved by TCP/IP.

The variables in this message are:

channelId - the identity of the TCP channel that attempted to connect
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the node identity of the partner to which IOAGATE attempted to connect
hostId - the identity of the Host that caused the problem

IOAGATE disables the indicated channel, and tries to continue processing.

Corrective Action: Try to specify the IP address instead of a Hostname, and restart IOAGATE.

ECAT0LW CHANNEL(`channelId`.TCP) `task` (`taskId.type`) BOTH PARTNER(`node`) AND IOAGATE ARE CONNECTORsLink copied to clipboard

Explanation: The message warns that both sides of the IOAGATE-to-IOAGATE connection were configured with CONNECTOR set to LOCAL.

The variables in this message are:

channelId - the identity of the TCP channel that detected the error
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
node - the node identity of the partner IOAGATE

IOAGATE continues trying to establish an IOAGATE-to-IOAGATE connection.

Corrective Action: Correct the IOAGATE-to-IOAGATE connection configuration in the network map, by setting CONNECTOR to LOCAL on one side of the connection and to PARTNER on the other side, then restart the IOAGATEs.

ECAT0ME CHANNEL(`channelId`.TCP) `task` (`taskId.type`) PARAMETER(`parm`) INVALID IP ADDRESS(`hostIpAdd`) SPECIFIED, CHANNEL DISABLEDLink copied to clipboard

Explanation: The specified IP address is invalid.

The variables in this message are:

channelId - the identity of the TCP channel that detected the problem
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
parm - the name of the parameter that specifies the invalid IP address.
hostIpAdd - the invalid IP address that caused the problem

IOAGATE disables the indicated channel and tries to continue processing.

Corrective Action: Correct the IP address and restart IOAGATE.

ECAT0NE CHANNEL(`channelId`.TCP) `task` (`taskId.type`) PARAMETER(`parm`) UNKNOWN HOST(`hostId`) SPECIFIED, CHANNEL DISABLEDLink copied to clipboard

Explanation: IOAGATE failed to resolve the specified Hostname.

The variables in this message are:

channelId - the identity of the TCP channel that detected the problem
task - the name of the communication task of channelId
taskId - the internal identity of task
type - the internal type of task
parm - the name of the parameter that specifies the invalid Hostname
hostId - the invalid Hostname that caused the problem

IOAGATE disables the indicated channel, and tries to continue processing.

Corrective Action: Either correct the Hostname, or specify the IP address instead of a Hostname, then restart IOAGATE.

ECAT0OI CHANNEL(`channelId`.TCP) `task` (`taskId.type`) SOCKIMP(`socket_typ`) CLIENTID(`client_id`)Link copied to clipboard

Explanation: This information message displays the socket implementation and client identity information that currently in use by IOAGATE.

The variables in this message are:

channelId - the identity of the TCP channel for which the socket and client ID information is issued
task - the name of the communication task for which the socket and clientid information is issued
taskId - the internal identity of task
type - the internal type of task
socket_typ - the type of socket implementation currently used by IOAGATE. Valid values are:
- OE - integrated socket (OpenEdition socket)The value is explicitly specified in the ECAPARM configuration file.
- COM - non-integrated socketThe value is explicitly specified in the ECAPARM configuration file.
- NONE - no value assigned in the ECAPARM configuration file, default in use
client_id - the internal identity of task assigned by TCP/IP

Corrective Action: No action is required.

ECAT0PS BAD PARAMETERS RECEIVED(REASON:`reason`) WHEN VALIDATING INCOMING IP ADDRESSLink copied to clipboard

Explanation: An internal error encountered when performing validation of an incoming IP address.

In this message, reason is the hexadecimal error code specifying an exact error case.

Corrective Action: Contact BMC Customer Support.

ECAT0QE PROBABLE CTM/EM SET UP ERROR: CTM/CONFIGURATION MANAGER DISCOVERY PORT WRONGLY SET TO THE CTM/EM PORT Link copied to clipboard

Explanation: IOAGATE received a message from Control-M/Enterprise Manager that was intended for CTMCAS on the port assigned for CTMAS. The error is probably because the Control-M for z/OS is incorrectly defined in the Control-M Configuration Manager.

Corrective Action: Ensure that the Control-M for z/OS Configuration Agent Port is defined in the Control-M Definition dialog box with the value of the port assigned for CTMCAS, not with the value of the port assigned for CTMAS.

ECAT0SI EVENT(`event`) OCCURRED ON PORT(`port`)Link copied to clipboard

Explanation: This information message indicates that the event error occurred on port port number. Details about the error are provided in message ECAT09W that precedes message ECAT0SI.

Corrective Action: No action is required.

ECAT0TI IOAGATE(`monitorId`) RUNNING ON HOST (`hostId,hostIpAdd`)Link copied to clipboard

Explanation: This information message displays

the STC name of IOAGATE
the name and the IP address of the host on which IOAGATE is currently running

The variables in this message are:

monitorId - the name of the IOAGATE started task
hostId - the identity of the host on which the specified IOAGATE is running
hostIpAdd - the IP address on which the specified IOAGATE is running

Corrective Action: No action is required.

ECAT0XI CHANNEL(`channelId`.TCP) `task` (`taskId.type`) ADDITIONALLY LISTENING FOR CONNECTION ON PORT(`port`), IP(`hostIpAdd`)Link copied to clipboard

Explanation: This information message displays the host IP address and the TCP/IP communication port number on which IOAGATE is listening because the SHRDBIND parameter has been specified in the ECAPARM configuration file for the indicated channel. This message is only issued when the SHRDBIND parameter is specified in the ECAPARM configuration file.

The message indicates that the indicated TCP channel has initialized and is waiting for the partner or client to initiate the connection.

The variables in this message are:

channelId - the identity of the TCP channel that is listening to the specified port
task - the name of the communication task of channelId. Valid values are:
- SENDER - the sender side of the dual connection (DC) TCP channel
- RECEIVER - the receiver side of the dual connection (DC) TCP channel
- LISTENER - the manager task of the multiple connection (MC) TCP channel
taskId - the internal ID of this communication task
type - the internal type of this communication task
port - the number of the TCP/IP communication port on which channelId is listening
hostIpAdd - the address to which channelId is listening

Corrective Action: No action is required.

ECAT0YI codename (`codeval`)Link copied to clipboard

Explanation: This message displays additional diagnostic information when an errno event occurs.

The variables in this message are:

codename - the identity of the code of the problematic macro or service. Valid values are:
- "Return Code of the failing service"
- "Reason Code of the failing service"
- "Information Code of the failing service"
- "EVENT(EADDRINUSE) OCCURRED ON PORT"
- "EVENT(EADDRNOTAVAIL) OCCURRED ON PORT"
codevalue - the value of the code of the problematic macro or service, or port number

Corrective Action: Keep the DAIGLOG output for possible later analysis.

ECAT0ZI Macro or Service that failed (`mserv`)Link copied to clipboard

Explanation: This message displays additional diagnostic information when an errno event occurs.

In this message, mserv is the identity of the problematic macro or service.

Corrective Action: Keep the DAIGLOG output for possible later analysis.

ECATS0E CHANNEL(`channelId`.TCP) TASK(`taskId.type`) SSL HANDSHAKE FAILED. RC(`rc`)Link copied to clipboard

Explanation: The SSL handshake with the client failed. The reason for the failure is described in message ECATS1E, which follows this message.

The variables in this message are:

channelId - the identity of the TCP channel that is listening to the specified port
taskId - the internal identity of this communication task
type - the internal type of this communication task
rc - System SSL return code value

Common values for rc are:

rc	Meaning	Most Probable Cause
6	Key label is not found	A bad KEYLAB parameter was specified in the ECAPARM configuration file
406	Error while reading or writing data	A CTM/EM client attempted to communicate using TCP/IP without SSL

For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03 ,z/OS V1R4.0-V1R5.0 System SSL Programming.

The connection is terminated. IOAGATE resumes listening for incoming connections on the DC channel.

Corrective Action: If the return code is 406 and after this failure the SSL handshake succeeds, no action is required. It is normal for CTM/EM to first attempt to connect using TCP/IP without SSL, and if this attempt fails, it retries with SSL.

If the return code is 406 and the error persists, the client side has probably not enabled SSL. Otherwise, refer to message ECATS1E and to the above-mentioned IBM publication.

ECATS1E `system_ssl_api_call` rc(`rc`): `textual_explanation_of_the_rc`Link copied to clipboard

Explanation: This message is issued after messages ECATS0E, ECATS2E, ECATS4E, and ECATS5E. The message includes more details about the failure reported by the preceding message.

The variables in this message are:

system_ssl_api_call - the internal System SSL API call that failed
rc - the return code that appeared in the preceding message
textual_explanation_of_the_rc - textual explanation of the return code

For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03, z/OS V1R4.0-V1R5.0 System SSL Programming.

Corrective Action: No action is required.

ECATS2E CHANNEL(`channelId`.TCP) TASK(`taskId.type`) SSL INIT FAILED. RC(`rc`)Link copied to clipboard

Explanation: After connection is established and before the SSL handshake takes place, the SSL initialization fails. The subsequent message (message ECATS1E) includes more details about the failure.

The variables in this message are:

channelId - the identity of the TCP channel that is listening to the specified port
taskId - the internal identity of this communication task
type - the internal type of this communication task
rc - System SSL return code value

A common value for rc is:

rc	Meaning	Most Probable Cause
202	Error detected while opening the key database	A bad KEYRING parameter is specified in the ECAPARM configuration file.

For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03, z/OS V1R4.0-V1R5.0 System SSL Programming.

The connection is terminated. The task resumes listening for new connections on the DC channel.

Corrective Action: Refer to message ECATS1E and to the above-mentioned IBM publication.

ECATS3I CHANNEL(`channelId`.TCP) TASK(`taskId.type`) SSL HANDSHAKE SUCCEEDEDLink copied to clipboard

Explanation: This information message indicates that an SSL handshake with the client succeeded.

The variables in this message are:

channelId - the identity of the TCP channel that is listening to the specified port
taskId - the internal identity of this communication task
type - the internal type of this communication task

Corrective Action: No action is required.

ECATS4E CHANNEL(`channelId`.TCP) TASK(`taskId.type`) SSL READ FAILED. RC(`rc`)Link copied to clipboard

Explanation: An internal call to decrypt a received message failed. The subsequent message (message ECATS1E) includes more details about the failure.

The variables in this message are:

channelId - the identity of the TCP channel that is listening to the specified port
taskId - the internal identity of this communication task
type - the internal type of this communication task
rc - System SSL return code value

For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03, z/OS V1R4.0-V1R5.0 System SSL Programming.

The connection is terminated. The task resumes listening for new connections on the DC channel.

Corrective Action: Refer to message ECATS1E and to the above-mentioned IBM publication.

ECATS5E CHANNEL(`channelId`.TCP) TASK(`taskId.type`) SSL SEND FAILED. RC(`rc`)Link copied to clipboard

Explanation: An internal call to encrypt a message before sending failed. The subsequent message (message ECATS1E) includes more details about the failure.

The variables in this message are:

channelId - the identity of the TCP channel that is listening to the specified port
taskId - the internal identity of this communication task
type - the internal type of this communication task
rc - System SSL return code value

For a full explanation of the return codes, please refer to the IBM manual SC24-5901-03, z/OS V1R4.0-V1R5.0 System SSL Programming.

The connection is terminated. The task resumes listening for new connections on the DC channel.

Corrective Action: Refer to message ECATS1E and to the above-mentioned IBM publication.

ECATS6E CHANNEL(`channelID`.TCP) TASK(`taskID`) SSL OPEN FAILED. RC(`rc`)Link copied to clipboard

Explanation: After an incoming TCP/IP connection was accepted for a channel with SSL=YES, IOAGATE attempted and failed to allocate and initialize a secure socket instance in the SSL subtask. The failure was in one of the following System SSL API calls:

gsk_secure_socket_open()
gsk_attribute_set_buffer()
gsk_attribute_set_numeric_value()

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
rc - the return code of the API call

The connection is closed.

Corrective Action: If the problem persists, contact BMC Customer Support.

ECATS7E CHANNEL(`channelID`.TCP) TASK(`taskID`) SSL CLOSE FAILED. RC(`rc`)Link copied to clipboard

Explanation: After an incoming TCP/IP connection was closed for a channel with SSL=YES, IOAGATE attempted and failed to close the corresponding secure socket instance in the SSL subtask. The failure was in the gsk_secure_socket_close() System SSL API call.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
rc - the return code of the API call

IOAGATE operations continue.

Corrective Action: If the problem persists, contact BMC Customer Support.

ECATS8E CHANNEL(`channelID`.TCP) TASK(`taskID`) INTERNAL ERROR IN ECAGCCB. RC(`rc`)Link copied to clipboard

Explanation: An internal error occurred when an IOAGATE communications subtask attempted to get an internal message from the SSL subtask.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
rc - the return code of the API call

IOAGATE disables the channel, and goes down if there is no other active channel.

Corrective Action: Contact BMC Customer Support.

ECATS9E CHANNEL(`channelID`.TCP) TASK(`taskID`) INTERNAL ERROR IN ECAPCCB. RC(`rc`)Link copied to clipboard

Explanation: An internal error occurred when an IOAGATE communications subtask attempted to put an internal message to the SSL subtask.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
rc - the return code of the API call

IOAGATE disables the channel, and goes down if there is no other active channel.

Corrective Action: Contact BMC Customer Support.

ECATSAE CHANNEL(`channelID`.TCP) TASK(`taskID`) ALLOCBUF FAILED. SOCK(`socket`)Link copied to clipboard

Explanation: An internal error occurred when an IOAGATE communications subtask attempted to allocate an internal buffer for an SSL connection.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
socket - the socket for which the error occurred

IOAGATE disables the channel, and goes down if there is no other active channel.

Corrective Action: Contact BMC Customer Support.

ECATSBE CHANNEL(`channelID`.TCP) TASK(`taskID`) FREEBUF FAILED. SOCK(`socket`)Link copied to clipboard

Explanation: An internal error occurred when an IOAGATE communications subtask attempted to free an internal buffer for an SSL connection.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
socket - the socket for which the error occurred

IOAGATE disables the channel, and goes down if there is no other active channel.

Corrective Action: Contact BMC Customer Support.

ECATSCE CHANNEL(`channelID`.TCP) TASK(`taskID`) INVALID REPLY(`reply`) FROM SSL SUBTASK. REQ(`request`)Link copied to clipboard

Explanation: An internal error occurred when an IOAGATE communications subtask read an invalid internal reply from the SSL subtask.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
reply - the invalid reply
request - the request for which the invalid reply was received

IOAGATE disables the channel, and goes down if there is no other active channel.

Corrective Action: Contact BMC Customer Support.

ECATSDE CHANNEL(`channelID`.TCP) TASK(`taskID`) INVALID REQUEST(`request`) IN CCB AFTER GETLink copied to clipboard

Explanation: An internal error occurred when an IOAGATE communications subtask read an invalid internal request from the SSL subtask.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
request - the invalid request

IOAGATE disables the channel, and goes down if there is no other active channel.

Corrective Action: Contact BMC Customer Support.

ECATSEW CHANNEL(`channelID`.TCP) TASK(`taskID`) SSLPUT CALL WHILE SSLPUT IN PROCESS. SOCK(`socket`)Link copied to clipboard

Explanation: An internal error (a previous internal put did not end) occurred when an IOAGATE communications subtask attempted to put an internal message to the SSL subtask.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
socket - the socket for which the error occurred

IOAGATE disables the channel, and goes down if there is no other active channel.

Corrective Action: Contact BMC Customer Support.

ECATSFE CHANNEL(`channelID`.TCP) TASK(`taskID`) MALLOC FAILED. SIZE(`size`) SOCK(`socket`)Link copied to clipboard

Explanation: An internal error occurred when an IOAGATE communications subtask attempted to allocate storage.

The variables in this message are:

channelID - the identity of the channel that detected the problem
taskID - the internal identity of the channel task that detected the problem
size - the size of the storage request that failed
socket - the socket for which the error occurred

IOAGATE disables the channel, and goes down if there is no other active channel.

Corrective Action: Contact BMC Customer Support.

EDA messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages EDAL00 through EDALxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

EDAL43I NEW DAY PROCEDURE COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the New Day procedure ended successfully. The CTMEDA program is executed as the last step in the New Day procedure to inform the Control-M monitor that the procedure ended successfully.

The Control-M monitor resumes execution.

Corrective Action: No action is required.

EDAL44E NEW DAY PROCEDURE ENDED WITH ERRORSLink copied to clipboard

Explanation:Highlighted, unrollable message.

The last phase in the New Day procedure, the CTMEDA program, ended with errors. This message follows a message that describes the specific cause of the error.

The Control-M monitor remains in a suspended state.

Corrective Action: Correct the error according to the description in the previous message and rerun the New Day procedure to invoke the CTMEDA program.

EXO messagesLink copied to clipboard

This group includes messages for the Control-O CMEM product.

Messages EXO200 through EXO2xxLink copied to clipboard

This group includes messages for the Control-O CMEM product.

EXO200I {CONTROL-O | CTMCMEM} EXECUTOR STARTEDLink copied to clipboard

Explanation: This information message is the normal start message of the Control-O or CMEM Executor task that handles tasks that cannot be executed by the Control-O or CMEM subsystem. Certain of these actions require communication with other IOA products.

Corrective Action: No action is required.

EXO201I {CONTROL-O | CTMCMEM} EXECUTOR ENDEDLink copied to clipboard

Explanation: This information message is the normal termination message of the CONTROLO or CMEM Executor task that handles tasks that cannot be executed by the CONTROLO or CMEM subsystem. Certain of these actions require communication with other IOA products.

Corrective Action: No action is required.

EXO202S ERROR ALLOCATING THE SUBSYSTEM-TO- MONITOR COMMUNICATION DATASETLink copied to clipboard

Explanation: The CONTROLO or CMEM monitor failed to allocate the subsystem-to-monitor communication file. The communication file links the CONTROLO or CMEM and Control-M monitors. Possible causes are:

The communication file is not cataloged on the correct disk.
The communication file is cataloged in a catalog that cannot be accessed from the local CPU.
The MVS allocation exit failed the allocation request.
A security product failed the allocation request.
The data set was not specified correctly in the Control-M CPU Installation Parameter in the IOACPRM member.
The data set was never allocated. That is, the Control-M Console Subsystem was not installed in the current computer.

The Control-O or CMEM monitor shuts down.

Corrective Action: Check the potential reasons for the error listed above. Correct as necessary, and restart the Control-O or CMEM monitor.

EXO203S THE SUBSYSTEM-TO-MONITOR COMMUNICATION DATASET COULD NOT BE OPENEDLink copied to clipboard

Explanation: The Control-O monitor failed to open a subsystem-to-monitor communication file. The communication file links the Control-O or CMEM and Control-M monitors. Possible causes are:

A communication file was incorrectly defined.
The MVS DADSM exit failed the open request.
A security product failed the open request.

The Control-O or CMEM monitor shuts down.

Corrective Action: Check the communication files that are in use, and make sure that they were properly defined, formatted, and cataloged. In addition, make sure that no restrictions are imposed, for example by MVS or a security package, and the like.

EXO204S I/O ERROR WHILE READING THE MONITOR-TO-SUBSYSTEM COMMUNICATION DATASETLink copied to clipboard

Explanation: The Control-O monitor could not read a monitor-to-subsystem communication file due to an I/O error. The communication file links the Control-O or CMEM and Control-M monitors. The Control-O monitor-to-subsystem communication file may not have been formatted correctly during Control-M Installation Procedure, or may have been incorrectly modified.

The Control-O or CMEM monitor shuts down.

Corrective Action: For formatting information, see the section that describes how to install the Control-M Event Manager Subsystem (CMEM) in the Control-M chapter of the INCONTROL for z/OS Installation Guide. Reformat or restore as necessary, and restart the Control-O or CMEM monitor.

EXO205S ERROR ALLOCATING THE MONITOR-TO-SUBSYSTEM COMMUNICATION DATASETLink copied to clipboard

Explanation: The Control-O monitor failed to allocate the monitor-to-system communication file. The communication file links the Control-O or CMEM and Control-M monitors.

Possible causes are:

The communication file is not cataloged on the correct disk.
The communication file is cataloged in a catalog that cannot be accessed from the local CPU.
The MVS allocation exit failed the allocation request.
A security product failed the allocation request.
The data set was not specified correctly in the Control-M CTM2SBS Installation Parameter in IOACPRM.

The Control-O or CMEM monitor shuts down.

Corrective Action: Check the potential reasons for the error listed above. Correct as necessary, and restart the Control-O or CMEM monitor.

EXO206S THE MONITOR-TO-SUBSYSTEM COMMUNICATION DATASET COULD NOT BE OPENEDLink copied to clipboard

Explanation: The Control-O or CMEM monitor failed to open a monitor-to-subsystem communication file. The communication file links the Control-O or CMEM and Control-M monitors. Possible causes are:

A communication file was incorrectly defined.
The MVS DADSM exit failed the open request.
A security product failed the open request.

The Control-O or CMEM monitor shuts down.

Corrective Action: Check the communication files that are in use, and make sure that they were properly defined, formatted and cataloged. In addition, make sure that no restrictions are imposed by MVS, a security package, and so on.

EXO207S I/O ERROR WHILE READING THE SUBSYSTEM-TO-MONITOR COMMUNICATION DATASETLink copied to clipboard

Explanation: The Control-O or CMEM monitor could not read a subsystem-to-monitor communication file due to an I/O error. The communication file links the Control-O or CMEM and Control-M monitors. The Control-O or CMEM subsystem-to-monitor communication file may not been formatted correctly during Control-M Installation procedure, or may have been incorrectly modified.

The Control-O or CMEM monitor shuts down.

EXO208S INVALID FORMAT OF THE SUBSYSTEM-TO-MONITOR COMMUNICATION DATASETLink copied to clipboard

Explanation: The Control-O or CMEM subsystem-to-monitor communication file has not been formatted correctly during the Control-M Installation Procedure or may have been incorrectly modified.

The Control-O or CMEM monitor shuts down.

EXO209S OPEN OF THE CONTROL-O TRACE FILE FAILED. DDNAME DAACTLOGLink copied to clipboard

Explanation: The Control-O monitor failed to open the trace file used when Control-O is operating in LOG and TEST modes.

The Control-O monitor shuts down.

Corrective Action: Make sure that DD name DAACTLOG is allocated to the Control-O monitor, or if no trace is required, to DUMMY.

EXO20AS SYSPLEX TABLE MISSING - SYSTEM LOGGER INTERFACE DISABLEDLink copied to clipboard

Explanation: CMEM attempted to read the Sysplex Table and could not find the table or encountered errors while reading the Sysplex Table. Possible causes are:

Sysplex Table is not in the STEPLIB concatenation of load libraries.
The Sysplex Table has an invalid internal format.
The Sysplex Table has no valid, active table entries.

CMEM attempts to allocate, open, and use the subsystem-to-monitor (S2M) communication files to implement CMEM-Control-M communication.

Corrective Action: Determine if the Sysplex Table is not in the load library or has an invalid format. Correct the problem and recycle CMEM.

EXO20BE SYSTEM LOGGER REQUEST `req` FAILED: R15=`r15` RETURN=`rc` REASON=`rsn`Link copied to clipboard

Explanation: One of the following System Logger requests failed:

DEFCFS, IXGINVNT - Define coupling facility structure.
DEFLGS, IXGINVNT - Define log stream.
CONLGS, IXGCONN - Connect to log stream.
WRITEL, IXGWRITE - Write a log stream log block.
BRWSEL, IXGBRWSE - Browse a log stream log block.
DELETL, IXGDELET - Delete a log stream log block.
DISLGS, IXGCONN - Disconnect from log stream.
DELLGS, IXGINVNT - Delete log stream.
DELCFS, IXGINVNT - Delete coupling facility structure.

CMEM issues r15. Possible values of r15 are:

08 - Minor System Logger request error.
12 - Intermediate System Logger request error.
16 - Major System Logger request error.
20 - Permanent System Logger request error.
24 - Internal CMEM error
28 - Operating system does not support System Logger interface.
32 - Internal CMEM error.

To determine the system action, check the descriptions of return and reason codes in the IBM manual MVS Programming: Assembler Services Reference, where they are described for each System Logger request separately.

Corrective Action: If you cannot correct the problem, call BMC Customer Support.

EXO20CI SYSTEM LOGGER INTERFACE ACTIVATEDLink copied to clipboard

Explanation: This information message indicates that CMEM has successfully initialized the System Logger interface. CMEM can now begin communicating with Control-M.

Corrective Action: No action is required.

EXO20CW IOACPRM NOT DEFINED. CMEM FUNCTION IS NOT SUPPORTEDLink copied to clipboard

Explanation: During Control-O or CMEM start up, the IOACPRM member was not found in the IOA PARM library, and therefore could not be loaded.

Initiation of CMEM fails. The CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.

Corrective Action: Have the INCONTROL administrator check if the situation is valid. If not, create the IOACPRM member in the IOA PARM library, and restart the Control-O or CMEM monitor.

EXO20DW NO CPU ENTRY FOR THIS SYSTEM WAS DEFINED. CMEM FUNCTION IS NOT SUPPORTEDLink copied to clipboard

Explanation: During the start up of Control-O or CMEM, the IOACPRM member in the IOA PARM library does not contain the definition for the system where the Control-O or CMEM monitor is active.

Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.

Corrective Action: Have the INCONTROL administrator check if the situation is valid. If not, add the definitions for the current system to the IOACPRM member in the IOA PARM library, and restart the Control-O or CMEM monitor.

EXO20EW S2M FILE WAS NOT DEFINED IN CPU ENTRY. CMEM FUNCTION NOT SUPPORTEDLink copied to clipboard

Explanation: During Control-O or CMEM start up, Control-O or CMEM could not allocate the Subsystem-to-Monitor file, because the name of the file is missing from the definition of the current system in the IOACPRM.

Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.

Corrective Action: Call the INCONTROL administrator to check if the situation is valid. If not, add the name of the Subsystem-to-Monitor file and the definitions for the current system to the IOACPRM in the IOA PARM library, and restart the Control-O or CMEM monitor.

EXO20FE NO CMMPLEX MEMBER. CMEM FUNCTION NOT SUPPORTEDLink copied to clipboard

Explanation: During Control-O or CMEM start up, the CMEM Logger facility was required, but the CMMPLEX member containing the definition of the Logger was not found.

Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.

Corrective Action: If the Logger should be used, create the CMMPLX member in the IOA PARM library. If the Logger facility is not required, set the SYSLOGR parameter in the CMEMCOMM section of the IOACPRM member in the IOA PARM library to N. Once the member definitions are correct, restart the Control-O or CMEM monitor.

EXO210E INVALID DATE `date` IN A DO COND STATEMENTLink copied to clipboard

Explanation: An invalid date reference format was used in a DO COND statement.

Valid date reference formats are:

ODAT - Control-O or CMEM working date (default)
DATE - Current Gregorian computer date
PREV - Previously scheduled activation date for rule
NEXT - Next scheduled activation date for rule
mmdd - Month and day of the scheduling date
ddmm - Day and month of the scheduling date
%%xx - An AutoEdit symbol

Corrective Action: Correct the date format, and reorder the rule table.

EXO212W CONTROL-O WAITING FOR SUBSYSTEM CONSOLELink copied to clipboard

Explanation: A Command-Response rule could not obtain a subsystem console because all valid subsystem consoles were in use by other Command-Response rules.

Command execution is delayed until the next Control-O interval, when a new attempt to obtain a subsystem console will be made.

Corrective Action: Check the Status screen for Command-Response rules which are executing. Verify that the number of Command-Response rules with a status of EXECUTING matches the number of subsystem consoles.

If this message is issued frequently, there may be an insufficient number of subsystem consoles to handle the Command-Response rules. In this case, increase the number of subsystem consoles in CTOPARM, and define new subsystem consoles to MVS accordingly. For information about defining subsystem consoles, see the Control-O chapter of the INCONTROL for z/OS Installation Guide.

EXO213E NO VALID SUBSYSTEM CONSOLE EXISTSLink copied to clipboard

Explanation: A Command-Response rule could not obtain a subsystem console because no valid subsystem consoles were allocated by Control-O. The cause of the problem is probably in the subsystem console definition.

The command is not executed.

Corrective Action: Make sure that the NUMCONS parameter in CTOPARM is greater than zero, and that the correct number of subsystem consoles is defined in MVS. For information about defining subsystem consoles, see the Control-O chapter of the INCONTROL for z/OS Installation Guide.

If the console subsystem definition does not seem to be the cause of the problem, check for previous console allocation error messages, and contact BMC Customer Support.

EXO214E MAXIMUM NUMBER OF DO TSO/KSL/SHELL REQUESTS WAS EXCEEDED. TSO/KSL/SHELL PROCESSING IS ABORTEDLink copied to clipboard

Explanation: In the process of executing DO TSO, DO KSL, or DO SHELL requests, all of the TSP (TSO PARM) blocks in CSA or ECSA were used. Possible causes are:

A JCL error in the TSO or KSL procedure.
Started tasks in the system are not being processed due to system corrective measures, such as auxiliary storage shortage.

Further TSO, KSL, or SHELL requests are temporarily suspended until at least one TSP is available.

Corrective Action: If started tasks are not processed due to system corrective measures, wait until they run and their corresponding TSP blocks are freed.

If a started task failed due to a JCL error, perform the following recovery action:

Correct the JCL error.
Manually reissue the START command that Control-O previously issued, that is, S O2TTSOCM,PARM=parm, where parm is in the console log or the Control-O JES log.

This action frees one TSP, and message EXO215I is issued when the next TSO or KSL request is processed. TSPs also become available when Control-O is brought down after a standard shutdown or an IPL.

EXO215I TSO/KSL/SHELL PROCESSING IS RESUMEDLink copied to clipboard

Explanation: This information message indicates that normal TSO, KSL, or SHELL processing resumed. TSO, KSL, or SHELL processing was suspended as a result of a shortage of TSP blocks. For more details see message EXO214E.

Corrective Action: No action is required.

EXO216W REQUEST PROCESSING BYPASSED DUE TO CONTROL-O STANDALONE MODELink copied to clipboard

Explanation: A DO RESOURCE or DO FORCEJOB request was made when Control-M was not installed. These statements are not supported if Control-M is not installed.

The rule is not ordered.

Corrective Action: Correct the rule or install Control-M.

EXO217E COND `name date` NOT `action` BY CONTROL-O - SECURITY VIOLATIONLink copied to clipboard

Explanation: Control-O issued a DO COND request, but the prerequisite condition was not added or deleted. There is no authorization by the security exit to add or delete this condition in the IOA Conditions file.

The DO COND request is ignored and the rule continues execution.

Corrective Action: Contact your INCONTROL administrator.

EXO218E COMMAND `cmdName` NOT ISSUED BY CONTROL-O - SECURITY VIOLATIONLink copied to clipboard

Explanation: There is no authorization for the requested DO COMMAND statement. Security exit IOASE012 detected a violation. This exit is invoked for each command issued by a rule in which value OWNER or TRIGGER was specified for the RUNTSEC parameter.

The DO COMMAND statement is ignored and the rule continues execution.

Corrective Action: Contact your INCONTROL administrator.

EXO219E RUNTIME SECURITY CACHE INITIALIZATION ERROR - `rsn`Link copied to clipboard

Explanation: This message indicates an internal error.

Control-O or CMEM continues to perform security checks without a security cache.

Corrective Action: Contact BMC Customer Support.

EXO21AE M2S FILE IS OF ANOTHER INSTALLATION QNAME `qname1`. IOA QNAME `qName2` DSN `dsn`Link copied to clipboard

Explanation: The Control-O or the CMEM monitor could not allocate the monitor to the Monitor to Subsystem (M2S) file of another IOA environment. During initialization the Control-O or the CMEM monitor compares the qName in the IOA environment with the qName in the M2S file. They should match.

CMEM stops. Control-O issues the CTO21FS and CTO21SE messages.

Corrective Action: Respond to the CTO21SE message. Then check the CTMPARM member and do one of the following:

If it points to the wrong file, correct the name and start a new monitor.
If there is no problem in the CTMPARM member, the M2S file was created in a different IOA environment. Delete the file and create a new M2S file using the correct IOA environment (IOAPARM).

EXO21BE S2M FILE FOR SMFID `smfid` IS OF ANOTHER INSTALLTION QNAME `qName1`. IOA QNAME `qName2` DSN `dsn`Link copied to clipboard

Explanation: The Control-O or the CMEM monitor could not allocate the subsystem to the Subsystem-to-Monitor (S2M) file of another IOA environment. During initialization the Control-O or the CMEM monitor compares the qName1 in the IOA environment with the qName2 in the S2M file. They should match.

CMEM stops. Control-O issues the CTO21FS and CTO21SE messages.

Corrective Action: Respond to the CTO21SE message. Then check the IOACPRM member and do one of the following:

If it points to the wrong file, correct the name, compile the member and start a new monitor.
If there is no problem in the IOACPRM member, the S2M file was created in a different IOA environment. Delete the file and create a new S2M file using the correct IOA environment.

EXO21CI M2S FILE FOR IOA QNAME `qName`. DSN=`dsn`Link copied to clipboard

Explanation: This information message identifies the Monitor to Subsystem (M2S) file that the Control-O or the CMEM monitor allocated for communication with the Control-M monitor.

QNAME is defined in the M2S file whose DSN is dsn.

Corrective Action: No action is required.

EXO21DI S2M FILE FOR SMFID `smfid` QNAME `qName` DSN=`dsn`Link copied to clipboard

Explanation: This information message identifies the Subsystem-to-Monitor (S2M) file that the Control-O or the CMEM monitor allocated for communication with the Control-M monitor. QNAME is defined in the S2M file whose DSN is dsn.

Corrective Action: No action is required.

EXO21EE REPLY ABORT, CONTINUE OR TERMINATELink copied to clipboard

Explanation: The error described in message EXO21ES prevents communication between the Control-O monitor and Control-M. The response to this message determines the next action.

The subtask is suspended until a response to this message is received.

Corrective Action: Select one the following responses:

ABORT - Abend the Control-O monitor.
CONTINUE - Disable communication with Control-M.
TERMINATE - End Control-O monitoring with a return code of 8.

EXO21EI THE REPLY TO MESSAGE EX021EE WAS: `reply`Link copied to clipboard

Explanation: The information message echoes the response to the message EXO21EE.

Corrective Action: No action is required.

EXO21ES SUBSYSTEM TO CONTROL-M MONITOR FUNCTION DISABLEDLink copied to clipboard

Explanation: An error occurred during initialization of Subsystem-to-Monitor (S2M) communication for the Control-O or the CMEM monitor. Initialization checks failed for the function that communicates with the. Control-M monitor. For details, see earlier error messages in the JOBLOG or IOA Log file.

CMEM stops with a return code of 8. Control-O issues the message EXO21EE.

Corrective Action: Correct the problem and restart the CMEM monitor, or respond to the EXO21EE message.

EXO21FE SUPPORT FOR 'DO FORCEJOB' AND 'DO RESOURCE' IS DISABLEDLink copied to clipboard

Explanation: Either Control-O disabled communication with Control-M because of a CONTINUE response to the message EXO21EE, or a DO FORCEJOB or DO RESOURCE statement was encountered during execution of a Control-O rule with communication disabled.

DO FORCEJOB, DO RESOURCE and NEWCONLIST requests from Control-M are ignored.

Corrective Action: No action is required.

EXO21GE JOB `jobname` JOBID `jobid` DID NOT PERFORM 'DO FORCEJOB' `jobnametablelibrary`Link copied to clipboard

Explanation: The specified Control-O rule failed to perform the specified DO FORCEJOB statement. Details are provided for the Control-O rule and for the job that contains the DO FORCEJOB statement.

This message appears after message EXO21FE. Additional previous messages explain the nature of the failure.

Corrective Action: Use the provided details to correct each occurrence of this failure.

EXO21HE JOB `jobname` JOBID `jobid` DID NOT PERFORM 'DO RESOURCE' `resource name and size`Link copied to clipboard

Explanation: The specified Control-O rule failed to perform the specified DO RESOURCE statement. Details are provided for the Control-O rule and for the resource.

This message appears after message EXO21FE. Additional previous messages explain the nature of the failure.

Corrective Action: Use the provided details to correct each occurrence of this failure.

EXO21IE S2M FILE IS 80% FULL. WHEN FULL, REQUESTS TO CONTROL-M WILL BE LOSTLink copied to clipboard

Explanation: When Control-M processes events (received through the Subsystem-to-Monitor communication dataset) slower than CMEM or Control-O adds them, file space shortage may occur, and this could eventually lead to lost events.

The message is issued when the Subsystem-to-Monitor (S2M) communication dataset reaches 80% utilization.

Corrective Action: Perform the following actions:

Eliminate the cause of the delay in event processing by Control-M.
Consider increasing the size of the Subsystem-to-Monitor communication dataset.

EXO21JI S2M FILE RECORDS SHORTAGE HAS BEEN RELIEVEDLink copied to clipboard

Explanation: The Subsystem-to-Monitor (S2M) communication dataset space shortage that was reported by message EXO21IE has been relieved.

Dataset utilization returned to a level below 60%.

Corrective Action: No action is required.

EXO250E RUNTIME SECURITY CLEANUP FAILED, RC=`rc`Link copied to clipboard

Explanation: An error with the return code rc occurred during interface with the locally used security product.

Control-O or CMEM continues working.

Corrective Action: Contact BMC Customer Support.

EXO251I RUNTIME SECURITY REFRESH ENDED OKLink copied to clipboard

Explanation: This information message indicates a normal response to operator command F CONTROLO,NEWSECDEF or F CTMCMEM,NEWSECDEF. The runtime security cache containing previously handled security definitions was successfully refreshed.

If security definitions were changed, the new definitions are used.

Corrective Action: No action is required.

EXO252I SNMP REQUEST HOST=`hostname` PORT=`portNumber` SEVERITY=`s` TEXT=`msgText`Link copied to clipboard

Explanation: This information message is an audit message that logs a DO SNMP request executed by Control-O.

Corrective Action: No action is required.

EXO253E SNMP REQUEST ERROR, RETURN CODE=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: Control-O tried to send an SNMP request using a DO SNMP statement, but the request contained an error.

Possible return and associated reason codes are described in the following table:

Return Code ( rc )	Reason Code ( rsn )	Explanation
04	00	Successful completion, minor errors discovered.
	04	SHL value exceeds 70, truncated.
08	04	Failed to get local IP address.
	08	Failure to get storage for an SNMP trap.
	12	Allocation storage has failed.
	16	Hostname could not be resolved.
	20	SNMP trap sending failed.
	24	Socket call failed.
	28	Internal error; buildTrapMessage() failed.
	96	ISTACK parameter is specified in the IOAPARM member and the system has TCP/IP dual stack mode, but the specified stack is not running.
	100	Invalid IPv6 destination. The destination contains the colon (:) character, but the address is not a syntactically valid IPv6 address.
	104	SNMP destination contains the colon (:) character, but IPv6 is not enabled in the z/OS system.
12	04	Missing SNMP message address.
	08	Invalid or missing SNMP message length.
	12	Neither Destination Table nor HOST and PORT provided.
	20	Bad or missing HOST parameter when no Destination Table.
	24	Bad or missing PORT parameter when no Destination Table.
	28	Invalid Destination Table.
	32	Specified Destination Table unavailable.
	36	Specified Translation Table unavailable.
	40	An invalid IP address was provided in HOST
20		Internal error.

The DO SNMP request is not sent, and fails.

Corrective Action: Notify the INCONTROL administrator.

EXO254E {CONTROL-O | CTMCMEM} SECURITY ENVIRONMENT CLEANUP FAILED BY USER EXIT RC=`rc` REASON=`rsn`Link copied to clipboard

Explanation: The IOASECUR security module was unable to delete the security environment. This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

EXO255W CONTROL-O SERVER ERROR. SERVER id-`rsn`Link copied to clipboard

Explanation: A server action cannot be performed because the server is not in the expected status. An action was attempted on a server that is either stuck or has disappeared.

Server status is set to IN ERROR.

Corrective Action: Do the following:

Check the sysout of the server in error for the cause of the error.
Correct the detected errors, such as errors in the JCL.
Restart the server.

EXO256W DO `request` WAITING FOR `id` SERVER WAS REROUTED TO IMMEDIATE SERVERLink copied to clipboard

Explanation: A DO KSL, DO TSO, or DO SHELL request waited for a server longer than the QWAIT time specified in the server definition in the CTOPARM member.

The request is routed for execution in an Immediate server.

Corrective Action: To prevent this problem in the future, do one of the following:

Define more servers.
Increase the QWAIT time specification.

EXO257E DO `request` BY USER `user` WAS CANCELED - SECURITY VIOLATIONLink copied to clipboard

Explanation: A DO KSL, DO TSO, or DO SHELL request is not executed, because security exit CTOSE03 detected a security violation. Exit CTOSE03 is invoked for every DO KSL, DO TSO, or DO SHELL request issued by a rule in which value OWNER or TRIGGER is specified for the RUNTSEC parameter.

The DO KSL, DO TSO, or DO SHELL request is not performed.

Corrective Action: Contact your IOA security administrator.

EXO258W DO `request` WAS DELAYED. NO IMMEDIATE SERVER AVAILABLELink copied to clipboard

Explanation: A DO KSL, DO TSO, or DO SHELL request designed for an Immediate server cannot be performed because all defined Immediate servers are busy.

The request is executed in the next available Immediate server.

Corrective Action: Consider increasing the number of Immediate servers to be defined. The number of Immediate servers is specified in the SRVIMD# parameter in the CTOPARM member.

EXO259I VM/CP COMMAND EXECUTED, VMRC=`rc`, COMMAND=`vm_cmnd`Link copied to clipboard

Explanation: This information message indicates that a DO COMMAND statement specifying the VM CP command vm_cmnd was successfully executed. This message also supplies the return code rc returned by the VM execution.

Corrective Action: No action is required.

EXO25AI TRAN `transaction_id action_typ jobnam` (`jobId`) STATUS=`stat`Link copied to clipboard

Explanation: This information message provides information about a job request that either the Control-O or the CMEM monitor sent to Control-M in the communication file. It is output to the SYSPRINT SYSOUT file of the Control-O or the CMEM monitor. The next message provides more details about the request.

The variables in this message are:

action_typ - Possible values are: FORCEJOB, RESOURCE, or COND (CMEM) monitor only
jobnam(jobId) - The kind of job and the specific JES job ID that created the request.
stat - Possible values are: S (Started), E (Ended), or O (Control-O event, On Spool job)

Corrective Action: Check the message that follows for more information about the job request.

EXO25BI TRAN `transaction_id transaction_info`Link copied to clipboard

Explanation: This information message provides detailed information about a job request that either the Control-O or the CMEM monitor executed and sent to Control-M in the communication file (S2M). It is output to the SYSPRINT SYSOUT file of the Control-O or the CMEM monitor, and it always follows EXO25AI.

Corrective Action: No action is required.

EXO25CI CTD REQUEST MISSION `date` FORCE MISSION=`missn` CATEGORY=`catgry`Link copied to clipboard

Explanation: This information message is an audit message that logs a DO CTD REQ executed by Control-O. It is always followed by EXO25GI.

Corrective Action: No action is required.

EXO25EE CTDCMI ERROR RETURN CODE=`rc`, CHECK CONTROL-O MONITOR SYSPRINT OR IOALOG FOR MORE INFORMATIONLink copied to clipboard

Explanation: Control-O tried to have Control-D force a mission using a DO CTD REQUEST statement, but the mission was not forced. The Control-D error message should appear on the SYSPRINT monitor or in the IOA log.

The DO CTD REQUEST fails. The mission is not forced.

Corrective Action: Notify the INCONTROL administrator.

EXO25FW MONITOR USE SYSPRINT SYSOUT INSTEAD OF ACTLOG SYSOUTLink copied to clipboard

Explanation: Control-O monitor or CMEM monitor tries to write a message to ACTLOG sysout. The ACTLOG DD statement is missing from the Control-O or CMEM procedure.

The monitor writes the message to the SYSPRINT sysout. In the monitor address space this may cause ABEND S02A with a return code of 0C in some cases. Since the Monitor can recover itself from the abend, the monitor is not immediately terminated.

Corrective Action: Add the following DD statement to the Control-O procedure (CTOTROLO) and the CMEM procedure (CTMCMEM):

//ACTLOG DD &OUTLIST,SYSOUT=&OUT

EXO25GI CTD REQUEST MISSION `date` FORCE LIBRARY=`library`Link copied to clipboard

Explanation: This information message is a continuation of message EXO25CI, and includes the library name.

Corrective Action: No action is required.

EXO25HE REQUEST TO OBTAIN LOAD-INDEX LIST FAILED. RC=`rc` REASON=`rsn`Link copied to clipboard

Explanation: Control-O or CMEM issued a CTMAPI request for a list of MVA-type Load-Indexes, but the request failed. The message provides the return code and reason code from CTMAPI. The message is always followed by message EXO25JS.

As a result of the failed request, setting of levels for MVA-type Load-Indexes was disabled.

Corrective Action: Check the reasons for the error. Correct as necessary, and restart the Control-O or CMEM monitor.

EXO25IE FAILED TO BUILD LOAD-INDEX LIST DUE TO MEMORY SHORTAGELink copied to clipboard

Explanation: Control-O or CMEM faced a private memory shortage when attempting to obtain buffers for a CTMAPI request for a list of MVA-type Load-Indexes. The message is always followed by message EXO25JS.

As a result of this issue, setting of levels for MVA-type Load-Indexes was disabled.

Corrective Action: Contact BMC Customer Support.

EXO25JS UPDATING LOAD-INDEXES BASED ON MAINVIEW ALARMS STOPPEDLink copied to clipboard

Explanation: Control-O or CMEM failed to build a list of MVA-type Load-Indexes, due to the reason described in message EXO25HE or message EXO25IE. This message always follows one of those messages.

Corrective Action: See message EXO25HE or message EXO25IE.

EXO25KI UPDATING OF LOAD-INDEXES BASED ON MAINVIEW ALARMS STARTEDLink copied to clipboard

Explanation: Control-O or CMEM successfully built a list of MVA-type Load-Indexes, and is ready to set Load-Index levels based on MainView Alarms.

Corrective Action: No action is required.

EXO25LI UPDATING OF LOAD-INDEXES BASED ON MAINVIEW ALRAMS {STOPPED | NOT STARTED}, NO LOAD-INDEXES FOUNDLink copied to clipboard

Explanation: Control-O or CMEM issued a CTMAPI request for a list of MVA-type Load-Indexes, but no defined MVA-type Load-Indexes were found.

As a result of this issue, setting of levels for MVA-type Load-Indexes was disabled.

Corrective Action: If no MVA-type Load-Indexes exist, consider setting OPTMVLID=N in CTMPARM, to disable setting levels for MVA-type Load-Indexes based on MainView Alarms.

EXO260E EXECUTION OF VM/CP COMMAND ABORTED. RC=`rc`Link copied to clipboard

Explanation: A DO COMMAND statement specifying a VM CP command failed. The return code rc indicates the cause of the error.

The specified command is ignored.

Corrective Action:The user response depends on the value of the return code (rc). The following table displays possible values for rc, together with their explanations and the appropriate user action.

RC	Explanation	User Action
4	MVS not running under VM.	Correct the rule containing this DO COMMAND statement.
8	Insufficient space (GETMAIN failed).	Increase the region size of the Control-O monitor.
12	IOAVMC not APF authorized.	Contact BMC Customer Support for assistance.
16	FREEMAIN error.	Contact BMC Customer Support for assistance.

EXO261I ATTEMPTING TO RECONNECT TO MVS SYSTEM LOGGER DUE TO ERROR `rsn`Link copied to clipboard

Explanation: Control-O or CMEM has detected an MVS System Logger error, and is attempting to reconnect to the MVS System Logger.

In this message, rsn is a reason code that is documented in the IBM manual MVS Programming: Assembler Services Reference. Check that publication for the system action relevant to the reason code in the message. Each System Logger request is in a separate section of the guide. The reason codes are described in the topic “Return and Reason Codes” for the IXGWRITE System Logger request.

Control-O or CMEM tries several times to reconnect to the MVS System Logger.

Corrective Action: No action is required.

EXO262E ATTEMPT TO RECONNECT TO MVS SYSTEM LOGGER FAILEDLink copied to clipboard

Explanation: Control-O or CMEM detected an MVS System Logger error, and attempted several times to reconnect to the MVS System Logger, without success.

Corrective Action: No action is required.

EXO263E MVS SYSTEM LOGGER ERROR - CMEM FEATURE DISABLEDLink copied to clipboard

Explanation: Control-O or CMEM detected an MVS System Logger error. Either this error was so severe as not to be recoverable, or Control-O or CMEM attempted several times to reconnect to the MVS System Logger, without success.

Control-O or CMEM has stopped attempting to reconnect to the MVS System Logger. The CMEM facility is deactivated.

Corrective Action: If and when the MVS System Logger becomes operational, stop and restart the Control-O or CMEM monitor.

EXO264E INCORRECT PORT PARAMETER `portNumber` WAS SPECIFIED. ONLY NUMERIC VALUE IS ALLOWEDLink copied to clipboard

Explanation: Control-O tried to send an SNMP request using a port number parameter (portNumber) that was incorrect.

The DO SNMP request is not sent, and fails.

Corrective Action: Ensure that a correct port number is specified. Only numeric characters (from 0 through 9) are allowed.

EXO281I `user_message`Link copied to clipboard

Explanation: This information message displays the message issued from a Control-O rule.

Corrective Action: No action is required.

F34 messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages F34400 through F344xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

F34491S OPEN OF DDNAME "DA34F" FAILEDLink copied to clipboard

Explanation: Open of the file containing the operator commands failed (the DA34F DD statement). The CTM34F program is usually activated as part of the New Day procedure. Possible causes are:

The DA34F DD statement missing.
The data set described by the DA34F DD statement does not exist, or cannot be opened for sequential read, or record length is not 80.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL of the job. For more information, see the INCONTROL for z/OS Administrator Guide.

F34492S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of IOA Log file failed at the DALOG DD statement. The CTM34F program is usually activated as part of the New Day procedure.

Possible causes are:

The DALOG DD statement missing.
The data set described by the DALOG DD statement is not the IOA Log file.
The data set described by the DALOG DD statement is the IOA Log file but of another IOA monitor, or of a different IOA version.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL of the job.

F34493I {IOA34F | CTM34F} STARTS EXECUTING COMMANDSLink copied to clipboard

Explanation: This information message indicates that the IOA34F or CTM34F program is ready to execute the operator commands from the supplied list. This program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

F34494W EXECUTING COMMAND `command`Link copied to clipboard

Explanation: The specified operator command was issued by the CTM34F Control-M utility, probably as part of the New Day procedure. Every operator command executed by the Daily Subsystem is written to the IOA Log for security reasons.

Corrective Action: No action is required.

F34495I {IOA34F | CTM34F} FINISHED EXECUTING COMMANDSLink copied to clipboard

Explanation: This information message indicates that the IOA34F or CTM34Fprogram finished executing the list of operator commands. This program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

F34496E PROGRAM {IOA34F | CTM34F} IS NOT APF-AUTHORIZEDLink copied to clipboard

Explanation: The MVS operating system rejected the operator commands issued by the CTM34F program. The CTM34F program should reside in an APF-authorized library and must be link edited with the AC=1 attribute in order to be able to issue operator commands.

The issued commands are rejected. The CTM34F program terminates with a condition code of 08.

Corrective Action: The CTM34F program already has the AC=1 attribute. The INCONTROL administrator should verify that the library in which CTM34F resides is APF-authorized.

F34497S VM HOST NOT AVAILABLELink copied to clipboard

Explanation: An attempt was made to issue a VM command while MVS was not running under VM. A command whose name starts with the prefix CP was passed to the IOAOPR utility. This prefix signals to Control-M that the command is intended for a host VM operating system, but the IOAOPR utility detected that no VM environment was available.

Corrective Action: Verify that a VM environment is running before issuing VM CP commands.

F34498S LOAD OF MODULE IOAVMC FAILEDLink copied to clipboard

Explanation: The IOAOPR utility could not load the IOAVMC module.

Corrective Action: Verify that the IOAVMC module resides in the STEPLIB library.

F34499E INVALID VALUE "`value` " FOR "RESPONSE" KEYWORDLink copied to clipboard

Explanation: The user entered a value other than YES or NO for the Response keyword.

Corrective Action: Correct the entry to either YES or NO.

Messages F34500 through F345xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

F34500I EXECUTING VM COMMAND `cmd`Link copied to clipboard

Explanation: This information message is issued by the IOAOPR utility to indicate execution of a VM CP command cmd.

Corrective Action: No action is required.

F34501I CTM501I REPLY: `reply`Link copied to clipboard

Explanation: The IOAOPR utility issues this information message to display the reply received as a result of issuing a VM CP command.

Corrective Action: No action is required.

F34502E CONVCON INVALID RC=`rc` REASON =`rsn` CONSOLE ID=`cons_id` CONSOLE NAME=`consName`Link copied to clipboard

Explanation: A command was issued to a console identified as cons_id or by the console name consName, and the CONVCON service return code rc is not 0. When a command is issued to a console, the CONVCON service is called to verify the console. The return code from the CONVCON service that validates the console response is rc.

The command may be rejected depending on the CONVCON action.

Corrective Action: Refer to the authorized Assembler services guide to determine the reason for the error. Correct the error, and reissue the command.

FLW messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages FLW0 through FLW0xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

FLW001S OPEN OF DDNAME "DAFLOW" FAILEDLink copied to clipboard

Explanation: Open of jobs flow printout file failed in the DAFLOW DD statement of the CTMRFLW or CTMRAFL utility.

Possible causes are:

The DAFLOW DD statement missing.
The data set described by the DAFLOW DD statement cannot be accessed for sequential write.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW002S OPEN OF DDNAME "DAJOB" FAILEDLink copied to clipboard

Explanation: Open of the scheduling tables file failed in the DAJOB DD statement of the CTMRFLW utility, or open of the Control-M Active Jobs file failed in the DACKPTIN DD statement of the CTMRAFL utility.

The DAJOB DD statement describes the production parameters tables on which a job flow report is requested. Many data sets or members can be concatenated to this DD statement. The DACKPTIN DD statement describes the Control-M Active Jobs file.

Possible causes are:

The DAJOB (DACKPTIN) DD statement missing.
The data set described by the DAJOB (DACKPTIN) DD statement cannot be opened for sequential read or record length is not 80 (600).

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW003E SCHEDULING TABLE(S) CONTAINS TOO MANY CARDSLink copied to clipboard

Explanation: There are too many statements in the scheduling table or tables of the CTMRFLW utility. There are too many jobs to be analyzed in one run of the utility.

The program stops executing with a condition code of 08.

Corrective Action: Divide the scheduling tables list into two runs of the utility.

FLW004E SCHEDULING TABLE IS EMPTYLink copied to clipboard

Explanation: The scheduling table does not contain any scheduling parameters for the CTMRFLW utility, or the Active Jobs file does not contain any job for the CTMRAFL utility. Scheduling tables described by the DAJOB DD statement do not contain any scheduling data for CTMRFLW.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW005W A CYCLIC FLOW DETECTED IN GROUP `grp`, JOB FLOW MAY CONTAIN ERRORSLink copied to clipboard

Explanation: A cyclic job flow detected in a group processed by the CTMRFLW or CTMRAFL utility. A cyclic flow detected inside a specific group may contain errors because there is no recognized parent to start a chain. The job flow of the specific group is terminated where the cyclic job flow is detected.

Corrective Action: Check the specified group using the Online Scheduling Definition Facility.

FLW006S OPEN OF DDNAME "SORTIN" FAILEDLink copied to clipboard

Explanation: Open of work file failed in the SORTIN DD statement of the CTMRFLW or CTMRAFL utility.

Possible causes are:

The SORTIN DD statement missing.
The data set described by the SORTIN DD statement cannot be opened for sequential write.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW007S OPEN OF DDNAME "SORTOUT" FAILEDLink copied to clipboard

Explanation: Open of work file failed in DD statement SORTOUT of the CTMRFLW or CTMRAFL utility.

Possible causes are:

The DD statement SORTOUT is missing.
The data set described by the DD statement SORTOUT cannot be opened for sequential read.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW008S SORT FAILED RC = `code`Link copied to clipboard

Explanation: Internal sort failed in the CTMRFLW or CTMRAFL utility. The CTMRFLW or CTMRAFL utility activates the regular sort program of the installation. The return code is specific to the sort program.

The program stops executing with a condition code of 08.

Corrective Action: Check the sort program literature for the meaning of the sort return code, and correct the JCL for the job accordingly.

FLW009E A JOB FLOW LOOP DETECTED. CHART CANNOT BE COMPLETED FOR GROUP `grp`Link copied to clipboard

Explanation: Although the input is valid for the Job Flow Report, a cyclic job flow, or loop, was detected in the specified group. As a result, a Job Flow Chart cannot be generated. In a job flow loop, it is impossible to determine which job is first. Therefore, the Job Flow Report program breaks the loop at a job it selects arbitrarily, places an asterisk (*) to the left of the job selected, and issues this message.

Report generation continues, but the Job Flow Chart is not produced.

Corrective Action: No action is required.

FLW010E MAXIMUM NUMBER OF DEPENDENCIES FOR JOB `jobName` EXCEEDED. ONLY FIRST 50 ARE TAKENLink copied to clipboard

Explanation: At least one job in the input tables depends on more than 50 other jobs. The Job Flow Chart can analyze up to 50 dependencies per job.

The chart is produced, but only the 50 first dependencies of that job are included.

Corrective Action: No action is required.

FLW011I CHART CONSISTS OF `pg_count` VERTICAL PAGES AND `pg_count` HORIZONTAL PAGESLink copied to clipboard

Explanation: This information message indicates the number of logical pages produced.

Corrective Action: No action is required.

FLW012W INTERNAL ERROR DETECTED. CHART MAY CONTAIN ERRORS, CODE=`errCode`Link copied to clipboard

Explanation: An internal error occurred.

The program proceeds, but it may contain a logical error.

Corrective Action: Provide the INCONTROL administrator with the message code and the error code specified in the error message.

FLW013I MESSAGES OF JOB FLOW REPORT Link copied to clipboard

Explanation: This information message is the title of the Messages List and indicates the beginning of the list.

Corrective Action: No action is required.

FLW014E INTERNAL ERROR (CODE=`err_cod`), PROCESSING STOPPEDLink copied to clipboard

Explanation: An internal error occurred.

Processing stops.

Corrective Action: Provide the INCONTROL administrator with the Control-M message code and the error code specified in the error message.

FLW015S NUMBER OF LINES PER PAGE MUST BE A MULTIPLE OF 4Link copied to clipboard

Explanation: The value specified in the PAGESIZE parameter is not a multiple of 4. For additional information regarding the PAGESIZE parameter, see the job flow chart in the chapter that describes KSL and the Reporting facility in the Control-M for z/OS User Guide.

Reports and charts are not produced.

Corrective Action: Correct the PAGESIZE parameter.

FLW016S LINE SIZE MUST BE A MULTIPLE OF 16 CHARACTERSLink copied to clipboard

Explanation: The subparameter specified in the LINESIZE parameter is not a multiple of 16. See the job flow chart in the chapter that describes KSL and the Reporting facility in the KeyStroke Language (KSL) User Guide for additional information regarding the LINESIZE parameter.

Reports and charts are not produced.

Corrective Action: Correct the LINESIZE parameter.

FLW017I PREPARING CHART FOR GROUP `grp` (`job_count` JOBS IN GROUP)Link copied to clipboard

Explanation: This information message indicates that CTMRFLW began preparing a chart for the specified group.

Corrective Action: No action is required.

FLW018E MAXIMUM CHART SIZE FOR GROUP `grp` EXCEEDEDLink copied to clipboard

Explanation: There are too many jobs and dependencies in the specified group. Internal capacity exceeded.

Chart cannot be produced for that group.

Corrective Action: If this occurs when the GROUP UNITED parameter is specified in the CTMRFLW batch utility, avoid using the UNITED subparameter for these tables. If the GROUP UNITED parameter was not specified, separate this group into several groups.

If the error occurred while you were trying to see a graphic jobflow in the Graphic Jobflow online screen, the limit of 15 levels of dependencies has probably been exceeded. In such a case, use the CTMRFLW utility to display the graphic jobflow.

FLW019I CHARS=(`char_set`,`char_set`) IN DD STATEMENT `ddName`Link copied to clipboard

Explanation: This informative message indicates the character sets and DD name used for printing the chart.

Corrective Action: No action is required.

FLW01AE PROCESSING OF AJF FILE TERMINATED `rsn`Link copied to clipboard

Explanation: A problem arose while the Active Jobs file (AJF) was being processed.

In this message, rsn identifies the problem that caused this message to be issued. The explanation, system action, and user response depend on the value of rsn.

If the value of rsn is GETMAIN, there is insufficient storage space and the processing of the AJF stops.

If the value of rsn is nnnnnn/ mmmmm/ jobName, an invalid field format was detected in an entry in the AJF. The variables in this version of the message identify the problematic entry. They are:

nnnnnn - the Relative Block Address (RBA)
mmmmm - the order ID
jobName - the job name

Processing of the AJF stops.

Corrective Action: The user response depends on the value of rsn:

If the value of rsn is GETMAIN, increase the REGION size.
If the value of rsn is nnnnnn/ mmmmm/ jobName, do the following:
Use the Zoom facility (Screen 3.Z) to check the entry, and print the contents of Screen 3.Z.
Copy the Active Jobs file, for use (if necessary) by BMC Customer Support.
Run the CTMRFLW utility, and print the output.
Send the printed contents of Screen 3.Z and the printed output of the CTMRFLW utility to your local BMC representative.

FLW0A1W SPECIFIED LINESIZE TOO LARGE FOR CHARACTER SETSLink copied to clipboard

Explanation: The specified LINESIZE is too large to be printed by the specified character sets. For example, standard English character set GS10 supports up to 132 characters per line while GS12 supports up to 160 characters per line. If GS10 was specified with a LINESIZE of 144, this warning message would be displayed. If GS12 was specified, this warning message would not be displayed.

Corrective Action: Either correct the specified LINESIZE or change the character sets which are specified in the JCL procedure.

FLW0A2E TOO MANY GROUP PARAMETER CARDS ARE SPECIFIEDLink copied to clipboard

Explanation: The number of GROUP parameter statements exceeded the maximum allowed. Do not specify more than 10 GROUP statements for CTMRFLW.

The utility terminates without processing.

Corrective Action: Decrease the number of GROUP statements.

FLW0A3E SPECIFIED GROUPS WERE NOT FOUND IN THE TABLE(S)Link copied to clipboard

Explanation: None of the names specified in the GROUP parameter was found in the table or tables. No table contains a job whose group name matches the GROUP name parameters. It is also possible that the table is empty.

The utility terminates without processing.

Corrective Action: Delete or correct the GROUP parameter statements.

FLW0A4W MEMBER `memName` DEPENDS ON "|" CONDITIONS. THE "|" SIGN WAS IGNOREDLink copied to clipboard

Explanation: Normal message issued by the CTMRFLW utility, when the memName member depends on | (OR) conditions.

When processing OR conditions, the utility ignores the | sign. Conditions are displayed without the | sign.

Corrective Action: No action is required.

FLW0A5S OPEN OF DDNAME "DACTO" FAILEDLink copied to clipboard

Explanation: Open of the Control-O rule tables specified by the DACTO DD statement failed. Possible causes are:

The DACTO DD statement is missing.
The data set described by the DACTO DD statement cannot be opened for sequential processing.

The CTMRFLW utility ends with errors.

Corrective Action: Check the JCL for the job. Correct it, and rerun the utility.

FLW0A6I MANUAL CONDITIONS PRECEDED BY "*" WERE DETECTED AS CONTROL-O "DO COND" CONDITIONSLink copied to clipboard

Explanation: This information message indicates that the CTMRFLW utility detected the addition of manual conditions by Control-O rules using DO COND statements.

Manual conditions added by DO COND statements are marked with an asterisk * by the utility.

Corrective Action: No action is required.

FMG messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages FMGI00 through FMGIxxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

FMGI50I BUILDING OF ECS COMMUNICATION DATASET STARTEDLink copied to clipboard

Explanation: This information message indicates that the Enterprise Controlstation Communication Dataset formatting utility started allocating and formatting the Enterprise Controlstation Communication Dataset file.

Corrective Action: No action is required.

FMGI51I BUILDING OF ECS COMMUNICATION DATASET ENDEDLink copied to clipboard

Explanation: This information message indicates that the Enterprise Controlstation Communication Dataset formatting utility completed allocation and formatting of the Enterprise Controlstation Communication Dataset file normally.

Corrective Action: No action is required.

FMGI52E BUILDING OF ECS COMMUNICATION DATASET FAILEDLink copied to clipboard

Explanation: The Enterprise Controlstation Communication Dataset formatting utility failed.

The utility fails.

Corrective Action: Look for an earlier error message that describes the type of error.

FMGI53E OPEN OF DDNAME DAM2G FAILEDLink copied to clipboard

Explanation: The Enterprise Controlstation Communication Dataset formatting utility failed to open the Enterprise Controlstation Communication Dataset file that is allocated to the DAM2G DD statement. Possible causes are:

The DAM2G DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

FMGI54E I/O ERROR OCCURRED WHILE BUILDING THE ECS COMMUNICATION DATASETLink copied to clipboard

Explanation: An I/O error occurred in the Enterprise Controlstation Communication Dataset formatting utility while formatting the Enterprise Controlstation Enterprise Controlstation Communication Dataset file.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the file DCB parameters, and rerun the job. If necessary, contact BMC Customer Support.

FMGI55E THE SIZE OF SHOUT TO ECS COMMUNICATION DATASET IS NOT SET CORRECTLYLink copied to clipboard

Explanation: An invalid value was specified on installation for the M2GSIZE parameter. The utility stops executing with a condition code of 08.

Corrective Action: Specify a valid value for the M2GSIZE parameter, and rerun the file creation process.

If this message was issued in a customized installation, do the following to set a valid value for the M2GSIZE parameter:

Open the IOA Installation and Customization Engine (ICE).
On the ICE Main Menu, select Installation.
On the IOA Installation screen, select Customized installation.
Set the Product ID to IOA, type 2 (INSTALL IOA) in the OPTION field, and press Enter.
Select Major Step 21 (Install Control-M Application Server), Minor Step 2 (Shout to Control-M/EM Parameters).
Change the value of the M2GSIZE parameter.

If this message was issued in a Default installation, save and exit the installation, change the value using the ICE Main Menu Customization option, run the job, and then return to the Default installation.

If this message was issued in a cloning installation, you first need to finish the cloning installation and then change the value using the ICE Main Menu Customization option. For more information, see the “Customizing INCONTROL products” section of the INCONTROL for z/OS Installation Guide.

FMGI56W SHOUT TO ECS COMMUNICATION DATASET OVERFLOWED. SOME MESSAGES MAY BE LOSTLink copied to clipboard

Explanation: The number of Shout messages written to the Enterprise Controlstation Communication Dataset file exceeded the available space. The Enterprise Controlstation Communication Dataset file contains a fixed number of blocks determined by the M2GSIZE parameter. Each block may contain one Shout message. Each time a Shout message is read from the file, a block is freed. Messages are being written to the file faster than they are read.

Old messages in the file are overwritten by newer Shout messages.

Corrective Action: If this condition occurs regularly, increase the size of the Enterprise Controlstation Communication Dataset file.

FOR messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages FORM00 through FORMxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

FORM20I CONTROL-D FOREIGN REPORT RESTORE ENDED O.K.Link copied to clipboard

Explanation: This information message indicates that a foreign report was successfully restored as a Control-D report.

Corrective Action: No action is required.

FORM21E CONTROL-D FOREIGN REPORT RESTORE FAILEDLink copied to clipboard

Explanation: The CTDFOR utility failed to restore the foreign report file.

The CTDFOR utility terminates. The foreign report is not restored.

Corrective Action: Examine other messages to determine the cause of the failure. Fix the problem, and rerun the CTDFOR utility.

FORM27E THE PARAMETER `parm` MUST BE SPECIFIED FOR CTDFOR UTILITYLink copied to clipboard

Explanation: The parm parameter must be specified for the CTDFOR utility.

The CTDFOR utility terminates.

Corrective Action: Add the missing parm parameter, and rerun the CTDFOR utility.

FORM28E INVALID PARAMETER:- `parm`Link copied to clipboard

Explanation: An invalid parameter (parm) was provided to the CTDFOR utility.

The CTDFOR utility terminates.

Corrective Action: Fix the invalid parm parameter, and rerun the CTDFOR utility.

FORM29E REDUNDANT PARAMETER:- `parm`Link copied to clipboard

Explanation: The same parameter (parm) was specified twice for the CTDFOR utility.

The CTDFOR utility terminates.

Corrective Action: Remove the redundant parm parameter, and rerun the CTDFOR utility.

FORM2AE INVALID DATE SPECIFIED:- `dateVal`Link copied to clipboard

Explanation: The date value (dateVal) specified in the REPDATE input parameter is a non-numeric value.

The CTDFOR utility terminates.

Corrective Action: Correct the invalid value in the REPDATE input parameter and rerun the utility.

FORM2BE GETPRM ROUTINE FAILED RC = `rc`Link copied to clipboard

Explanation: An invalid parameter was specified for the CTDFOR utility. The parameter name, parameter content, or parameter syntax is invalid.

The CTDFOR utility is terminated.

Corrective Action: Fix the parameters following the SYSIN DD statement, and rerun the CTDFOR utility.

FORM2CE SYSDATA RECORD ALREADY EXISTS IN ACTUSR. SKEY=`key`Link copied to clipboard

Explanation: The CTDFOR utility tried to add a sysdata to the Active User Report List file (ACTUSR) but the sysdata already exists. The sysdata probably exists because the utility was previously run with the same input data.

The CTDFOR utility continues processing.

Corrective Action: No action is required.

FORM2DE USER RECORD ALREADY EXISTS IN ACTUSR. UKEY=`key`Link copied to clipboard

Explanation: The CTDFOR utility tried to add a user record to the Active User Report List file (ACTUSR) but the record already exists. The user record probably exists because the utility was previously run with the same input data.

The CTDFOR utility continues processing.

Corrective Action: No action is required.

FORM2EI USER PARAMETERS FOR FOREIGN REPORT RESTORE: `inputStmt`Link copied to clipboard

Explanation: This information message displays the input parameters provided by the user for the CTDFOR utility.

Corrective Action: No action is required.

FORM2FS UNKNOWN PRODUCT NAME PROVIDED IN PRODUCT= PARAMETER: `parm`Link copied to clipboard

Explanation: A product name specified in the parm PRODUCT parameter is unknown to the CTDFOR utility. It is not the name of a product supported by the utility.

The CTDFOR utility terminates.

Corrective Action: Set the PRODUCT parameter to the name of a supported product.

FORM30E CONVERSION ROUTINE FAILED. RC = `rc`Link copied to clipboard

Explanation: The conversion routine called by the CTDFOR utility failed to convert the report file to a CDAM file.

The CTDFOR utility terminates.

Corrective Action: Examine other messages to determine the cause for the conversion routine failure. Correct the problem and rerun the CTDFOR utility.

FRM messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS and Control-D products.

Messages FRM400 through FRM4xxLink copied to clipboard

This group includes messages for the Control-M for z/OS and Control-D products.

FRM450S OPEN OF WORK FILE FAILED - DDNAME "DAJOBLST". PLEASE CHECK THE MESSAGES AND CODES MANUALLink copied to clipboard

Explanation: The New Day procedure was unable to open the file pointed to by the DAJOBLST DD name for update.

After reading the list of CDAM files to be deleted from the file pointed to by DAJOBLST, the New Day procedure empties the file and writes one record indicating that there are no more entries. Possible causes are:

File not found on the disk.
Incorrect security authorization.

Corrective Action: Determine the reason for the problem, and correct it. Reinstall Control-M/Restart.

FRM451I `taskType taskName` ODATE `odate` ORDERID `orderId` DELETED - MAXWAIT EXCEEDEDLink copied to clipboard

Explanation: This information message is issued during the New Day procedure. It indicates that a job or group entity has been deleted from the Active Jobs file because the MAXWAIT of the job or group entity was exceeded.

The MAXWAIT parameter sets a maximum limit to the time that a task can wait for execution. For more information, see the description of the MAXWAIT parameter in the Control-M for z/OS User Guide.

The variables in this message are:

taskType - the type of task that was deleted

Valid values are:

taskType	Explanation
JOB	The task was a job.
GRP ENTITY	The task was a group entity.

taskName - the name of the job or group entity that was deleted
odate - the ODATE of the job or group entity that was deleted
orderId - the order ID of the job or group entity that was deleted

The taskName job or group entity is removed from the Active Jobs file.

Corrective Action: No action is required.

FRM452I FORMATTING OF `activeFile` STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) is currently being formatted.

Corrective Action: No action is required.

FRM453S OPEN OF DATES CONTROL RECORD FAILED. DDNAME "DACHK"Link copied to clipboard

Explanation: Open of Control-M or Control-D Date Control record failed in the DACHK DD statement). This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program as part of the New Day procedure.

Possible causes are:

The DACHK DD statement is missing.
The data set (member) described by the DACHK DD statement is not the Control-M or Control-D Date Control Record.

Corrective Action: Correct the JCL for the New Day procedure.

FRM454E FORMAT (`format_pgm`) ALREADY RUN TODAYLink copied to clipboard

Explanation: An attempt was made to run the New Day procedure twice in the same day. The New Day procedure issues format_pgm. This program should not run more than once a day.

Possible values of format_pgm:

CTMFRM - formats the Active Jobs file (AJF) in Control-M
CTDFRM - formats the Active Missions file (AMF) in Control-D

The AJF or AMF is not formatted, but the New Day procedure continues to execute other programs in the program list.

Corrective Action: Check why the New Day procedure is being run twice, and whether jobs or missions were accidentally ordered twice because the General Date Control Record was erroneously modified.

FRM455S LAST FORMAT DATE GREATER THAN ORIGINAL SCHEDULING DATE IN DATES CONTROL RECORDLink copied to clipboard

Explanation: The last format date is later than the original scheduling date in the Control-M Date Control record or the Control-D Date Control record. The New Day procedure issues this message. For more details refer to the appropriate user guide.

New Day processing stops.

Corrective Action: Correct the Control-M or Control-D Date Control record, and run the New Day procedure again.

FRM456S OPEN OF `activeFile` FAILED. DDNAME "`ddName` "Link copied to clipboard

Explanation: Open of the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) defined in the ddName DD statement failed. The New Day procedure calls the program that issues this message.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes of this message:

The ddName DD statement is missing.
The data set described by the ddName DD statement is not the AJF or the AMF.
The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure, and rerun it.

FRM457S OPEN OF BACKUP FILE FAILED. DDNAME "DABKUP"Link copied to clipboard

Explanation: Open of backup file for the Active Jobs file (AJF) or Active Missions file (AMF) defined in the DABKUP DD statement failed.

This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

Possible causes of this message are:

The DABKUP DD statement is missing.
The data set described by the DABKUP DD statement is not the Active Jobs Backup file or Active Missions Backup file.
The data set described by the DABKUP DD statement is the Control-M Active Jobs Backup file or the Control-D Active Missions Backup file, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure, and rerun it.

FRM458S ERROR IN `activeFile`, RECORD 0. SHOULD BE FORMAT OR FREELink copied to clipboard

Explanation: Record 0 of the activeFile file contains incorrect data.

This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

In Control-M activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Possible causes of this message are:

activeFile is corrupt.
The data set described by the DACKPT DD statement (Control-M) or the DAAMF DD statement (Control-D) is not activeFile but is very similar to it.

Program execution stops with a condition code of 08.

Corrective Action: Check the validity of the data set described by the DACKPT or DDAMF DD statement. If necessary, correct the JCL, and rerun the New Day procedure.

If activeFile is corrupt, use a standard copy utility, like IEBGENER, to copy activeFile, and send it to BMC Customer Support. If necessary, run the FORMCKP utility to reformat the Active Jobs file or the CTDFRAMF utility to reformat the Active Missions file. However, these utilities also erase all the jobs or missions in the respective files.

FRM459I `activeFile` IS RESTORED FROM BACKUPLink copied to clipboard

Explanation: This information message indicates the beginning of a rerun of the New Day procedure after an earlier abend during the format of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

activeFile is restored from the appropriate backup file and processing continues normally.

Corrective Action: No action is required.

FRM45AI `taskType memName` ODATE `odate` OID=`orderId` CYCLIC ATTRIBUTE REMOVED - MAXWAIT EXCEEDEDLink copied to clipboard

Explanation: This information message indicates that the New Day procedure removed the cyclic attribute of the job to prevent further recycling. The cyclic job identified in the message was executing when the New Day procedure was being run. Therefore, it could not be removed from the Active Jobs file (AJF), although its MAXWAIT period had expired. To prevent further recycling of the job, its cyclic attribute is removed.

The job remains in the AJF with its changed taskType.

Corrective Action: No action is required.

FRM45BI `taskType memName` ODATE `odate` CYCLIC ATTRIBUTE REMOVED - MAXWAIT EXCEEDEDLink copied to clipboard

Explanation: This information message indicates that the New Day procedure removed the cyclic attribute of the job to prevent its further recycling. The cyclic job identified in the message was executing when the New Day procedure was being run. Therefore, it could not be removed from the Active Jobs file (AJF), although its MAXWAIT period had expired. To prevent further recycling of the job, its cyclic attribute is removed.

The job remains in the AJF with its changed task type.

Corrective Action: No action is required.

FRM45CE `func` OPERATION FOR "COM" FILE FAILED. RC=`rc`Link copied to clipboard

Explanation: An internal error occurred in the CTDCIO internal module while the Active Mission file was being formatted.

The Active Mission file is not formatted.

Corrective Action: Note the values of func and rc and contact BMC Customer Support.

FRM460S DATE CONTROL RECORD IS EMPTYLink copied to clipboard

Explanation: The DACHKDD statement describes an empty data set or member.

For more information, see the descriptions of NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M or Control-D Date Control Record and run the New Day procedure again.

FRM461S ERROR WHILE FORMATTING IOA CONDITIONS FILELink copied to clipboard

Explanation: I/O error while formatting the IOA Conditions file. Possible causes are:

The data set described by the DARESF DD statement is not the IOA Conditions file.
An I/O error occurred while reading the IOA Conditions file.

Program execution stops with a condition code of 08.

Corrective Action: Correct and run the New Day procedure again. In case of an I/O error, you may need to recreate the IOA Conditions file. This erases all the conditions from the file.

FRM462S INVALID LAST FORMAT DATE IN DATE CONTROL RECORDLink copied to clipboard

Explanation: Invalid format of last format date in the Date Control Record. This message is issued by the CTMFRM or CTDFRM program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy.

Possible causes are:

Someone has modified the contents of the Date Control Record incorrectly.
The record described by the DACHK DD statement is not the Control-M Date Control Record or the Control-D Date Control Record.

For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

Correct the JCL for the Daily Subsystem, and rerun it.
Correct the format date in the Date Control Record, and rerun the New Day procedure.

FRM463S INVALID ORIGINAL SCHEDULING DATE IN DATE CONTROL RECORDLink copied to clipboard

Explanation: Invalid original scheduling date in the Date Control Record. This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy.

Possible causes are:

The record described by the DACHK DD statement is not the Control-M General Date Control Record or the Control-D General Date Control Record.
Someone modified the contents of the General Date Control Record incorrectly.

See the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide for more information.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

Correct the JCL for the New Day procedure and rerun it.
Correct the original scheduling date in the General Date Control Record and rerun the New Day procedure.

FRM464S FILE ALLOCATED TO DDNAME "`ddName` " IS NOT YOUR `activeFile`Link copied to clipboard

Explanation: The data set described by the ddName DD statement is not the file specified by activeFile.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes are:

The data set described by the ddName DD statement is not the AJF or the AMF.
The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the problem in the data set name indicated by the specified DD statement, and run the New Day procedure again.

FRM465S FILE ALLOCATED TO DDNAME "DABKUP" IS NOT A BACKUP OF THE `activeFile`Link copied to clipboard

Explanation: The data set described by the DABKUP DD statement is not a backup of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF). Possible causes are:

The data set described by the DABKUP DD statement is not the AJF or the AMF.
The data set described by the DABKUP DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M Date Control Record and rerun the affected procedure.

FRM466S NEED MORE MEMORY TO FORMAT `activeFile`Link copied to clipboard

Explanation: There is not enough memory to format activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08. Control-M and Control-D monitors will not start after this error.

Corrective Action: To enable monitors to start, increase REGION size and rerun the affected procedure.

FRM467I `taskType memName` ODATE `odate` OID=`orderId` DISREGARDED - MAXWAIT EXCEEDEDLink copied to clipboard

Explanation: The New Day procedure issues this information message to indicate that the MAXWAIT of a task was exceeded. The maximum waiting time for a task or mission is specified in the MAXWAIT parameter.

For more information, see MAXWAIT in the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

The task or mission is erased from the AJF or AMF. In the case of a task, the memName member of the odate original date is removed from the AJF.

Corrective Action: No action is required.

FRM468I FORMATTING OF `activeFile` ENDEDLink copied to clipboard

Explanation: This information message indicates that the New Day procedure finished formatting activeFile. This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Corrective Action: No action is required.

FRM469S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of IOA Log file failed. The message is produced by the New Day procedure. Possible causes are:

The DALOG DD statement is missing.
The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL and run the Daily again.

FRM46AI `memName` ODATE `odate` DISREGARDED - MAXWAIT EXCEEDEDLink copied to clipboard

Explanation: This information message is issued by the Control-D New Day procedure. It indicates that the MAXWAIT of a job or mission has been exceeded.

The memName member is deleted from the Active Jobs file or Active Missions file.

Corrective Action: No action is required.

FRM470S ERROR WHILE FORMATTING THE `activeFile`, FILE WAS NOT FORMATTEDLink copied to clipboard

Explanation: An error occurred during formatting of activeFile. The New Day procedure issues this message.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08.

Corrective Action: Look for a previous message that describes the type of error. Correct it and rerun the New Day procedure.

FRM475S DATE IN AMF FILE GREATER THAN CURRENT DATELink copied to clipboard

Explanation: The DATE field in the Active Mission file is incorrect because it is greater than the current date. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

Reformat the Active Mission file using the CTDFRAMF utility.
Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

FRM476S DATE IN AMF FILE WAS MORE THAN 28 DAYS AGOLink copied to clipboard

Explanation: The Control-D monitor was inactive for more than 28 days. The DATE field in the Active Mission file differs from the current date by more than 28 days. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

Reformat the Active Mission file using the CTDFRAMF utility.
Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

FRM477S INVALID DATE IN AMF FILELink copied to clipboard

Explanation: The DATE field in the Active Mission file is incorrect. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

Reformat the Active Mission file using the CTDFRAMF utility.
Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

FRM481S OPEN OF WORK FILE FAILED - DDNAME "DAJOBLST". DELETE OF ARCHIVED SYSOUTS FAILEDLink copied to clipboard

Explanation: Open for the DAJOBLST file failed during the execution of the Control-M New Day procedure.

This error message is issued by the CTMDAS program, which is usually activated as part of the New Day procedure. The DAJOBLST DD statement is probably missing.

Program execution stops with a condition code of 16.

Corrective Action: Make sure that CTR (CONTROL-M/Restart) is set to Y in IOAPARM, in the PRODUCTS section.

FRM482S INIT OF RES FILE FAILEDLink copied to clipboard

Explanation: The New Day procedure failed to initialize the Control-M Resources file. An accompanying message identifies the reason for the failure.

The New Day procedure stops with an error, a return code of 12.

Corrective Action: Check the accompanying message to determine the reason for the problem, and correct the problem accordingly.

FRM484I FORMAT OF RESOURCE FILE HAS STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-M Resources file is currently being formatted. This procedure is usually part of the New Day procedure.

Corrective Action: No action is required.

FRM485I RESOURCE `quantResource` QUANTITY `num` WAS RELEASED BY CTMFRMLink copied to clipboard

Explanation: This information message indicates that the CTMFRM format program cannot find the job that holds the specified quantity (num) of quantResource quantitative resources.

The system releases the quantitative resources for use by other jobs.

Corrective Action: No action is required.

FRM486E RESOURCE `quantResource` FOUND TO BE NOT BALANCED BY CTMFRM. CHECK AND ADJUST MANUALLYLink copied to clipboard

Explanation: The number of quantResource quantitative resources currently in use exceeds the maximum defined for this resource. An error probably occurred during the monitor run on the previous day, since it is supposed to keep the resources balanced.

Corrective Action: Use the ADD, CHANGE and DELETE options on screen 4 to balance the Control-M Resources file.

FRM487I RESOURCE `contResource` IS HELD `type` - RELEASED BY FORMATLink copied to clipboard

Explanation: This information message indicates that the specified Control resource was released.

Valid values for type are:

type	Explanation
S	The resource is being used in Shared mode.
E	The resource is being used in Exclusive mode.
R	An unfulfilled critical path request for the resource.

The system releases the resource.

Corrective Action: No action is required.

FRM488I FORMAT OF RESOURCE FILE HAS ENDEDLink copied to clipboard

Explanation: This information message indicates that formatting of the new Control-M Resources file is complete and the resource is available.

Corrective Action: No action is required.

FRM489E OID=`orderId` FORMAT DETECTED MIT AND RESOURCE `quantResource` MISMATCHLink copied to clipboard

Explanation: The quantResource Quantitative resource points to a job record (MIT) that is not its owner. Each resource in the Control-M Resources file points to the job record that owns it.

The system deletes the specified quantitative resource from the Control-M Resources file.

Corrective Action: No action is required.

FRM48AE FORMAT DETECTED MIT AND RESOURCE `contResource` MISMATCHLink copied to clipboard

Explanation: The contResource Control resource points to a job record (MIT) that is not its owner. Each resource in the Control-M Resources file points to the job record that owns it.

The system deletes the specified Control resource from the Control-M Resources file.

Corrective Action: No action is required.

FRM48CI Preceding clear history did not complete. Process may run longer.Link copied to clipboard

Explanation: During the AJF compression process, Control-M detected that the last clear process of the history file (HST), which followed the preceding AJF compression, did not successfully complete or did not run at all.

The AJF compression process continues, but the process might take longer than usual to complete.

Corrective Action: Usually the issue is resolved automatically by the next run of the history clear process, which either runs by default as part of the Control-M Daily run (step CLRHIST, program CTMHSC) or as a standalone utility (CTMHCLN). Make sure that the clear history process is included in the Control-M Daily run, or that the CTMHCLN utility runs on a daily basis. Make sure the process ends without errors.

Messages FRM600 through FRM6xxLink copied to clipboard

This group includes messages for the Control-M for z/OS and Control-D products.

FRM617E INTERNAL ERROR - INVALID NAME OF THE ARCHIVED SYSOUT DATASET. DSNAME=`dsn`Link copied to clipboard

Explanation: The name of Archived Sysout Data Set does not follow the Control-M/Restart naming conventions for this type of data set. This message is issued either by the Control-M New Day procedure, or by the CTMCOP utility during compress of the Control-M Active Jobs file.

Corrective Action: Contact BMC Customer Support for assistance.

FRM618E TOO MANY SYSOUT DATASETS SCHEDULED FOR DELETE - SOME WILL BE SKIPPED THIS TIMELink copied to clipboard

Explanation: The number of Archived Sysout Data Sets scheduled for deletion exceeds the permitted number. This message is issued either by the Control-M New Day procedure or by the CTMCOP utility during compress of the Control-M Active Jobs file. The permitted value is one fifth of the Active Jobs file size.

Deletion of Archived Sysout Data Sets will be resumed during the next run of the New Day procedure or the CTMCOP utility.

Corrective Action: No action is required.

FRM637E THIS AUTOEDIT SYMBOL IS NOT ALLOWED HERELink copied to clipboard

Explanation: An AutoEdit symbol was specified in an environment in which it is not valid. Some AutoEdit symbols can be used in one environment only. For example, %%OYEAR cannot be used in utilities which are not submitted under Control-M.

The current process terminates.

Corrective Action: Specify an AutoEdit symbol that is valid for your environment.

FRM638S AUTOEDIT FAILED RC=`rc`Link copied to clipboard

Explanation: An AutoEdit error occurred. An invalid AutoEdit statement or variable was encountered (with a return code of 12 or higher), or there was insufficient memory to perform the AutoEdit operation (a return code of 8).

The process terminates.

Corrective Action: If the return code was 8, increase memory. If the return code was 12 or higher, check the preceding message, and correct the erroneous statement or variable accordingly.

FRM639S ACTIVE JOBS FILE (CKP) SIZE - PARM TABLE MISMATCHLink copied to clipboard

Explanation: The CKPSIZE parameter in CTMPARM is not the same as when the Active Jobs file (AJF) referenced by DD DACKPT was formatted. A change was made in the CKPSIZE parameter in CTMPARM after the Active Jobs file was formatted.

The job step or request terminates without performing the requested function.

Corrective Action: Adjust the CKPSIZE parameter according to the real size of the AJF, or reformat the AJF.

FRM640I `taskType taskName` ODATE `odate` ORDERID `orderId` DELETEDLink copied to clipboard

Explanation: This information message indicates that a job or group entity was deleted from the Active Jobs file.

The variables in this message are:

taskType - the type of task that was deleted

Valid values for taskType are:

taskType	Explanation
JOB	The task was a job.
GRP ENTITY	The task was a group entity.

taskName - the name of the job or group entity that was deleted
odate - the ODATE of the job or group entity that was deleted
orderId - the order ID of the job or group entity that was deleted

The taskName job or group entity is deleted from the Active Jobs file.

Corrective Action: No action is required.

FRM641S INVALID JOB RECORD DETECTED: `jobName`Link copied to clipboard

Explanation: A job record with an invalid format was detected during the New Day procedure. If the User Daily is run on a different computer without proper ENQ distribution software, such as GRS or MIM, a faulty record may be created in the Active Jobs file.

The faulty record is erased from the Active Jobs file.

Corrective Action: To avoid this problem, run all User Daily procedures on the CPU in which the Control-M monitor is running.

Messages FRMB00 through FRMBxxLink copied to clipboard

This group includes messages for the Control-M for z/OS and Control-D products.

FRMB55E ERROR WHILE OPENING DD "DASCRLST". OLD PRINT PLAN FILES WILL NOT BE DELETEDLink copied to clipboard

Explanation: An error occurred while trying to write a print plan file name to the scratch list. The message is issued by the AMF formatting program. This program could not open the file referenced by DD DASCRLST. This could be because the entire corresponding DD statement is missing.

AMF formatting program continues processing.

Corrective Action: Verify that the DASCRLST DD statement exists in the JCL and that it references an existing file.

Messages FRML00 through FRMLxxLink copied to clipboard

This group includes messages for the Control-M for z/OS and Control-D products.

FRML61E COPY TO HISTORY FILE FAILED: `rsn` REASON CODE: `rc`Link copied to clipboard

Explanation: An error occurred while copying records from the Active Jobs file to the History Jobs file.

The variables in this message are:

rsn - the cause of the error
rc - the reason code; this may contain additional information in certain cases

The Control-M New Day procedure terminates.

Corrective Action: Correct the cause of the error and rerun the Control-M New Day procedure. The enhanced checkpoint record can be used to continue the New Day procedure processing from the point at which the error occurred.

FRML63E HISTORY FILE PROCESSING MODULE NOT FOUNDLink copied to clipboard

Explanation: The attempt to load the CTMHCP or CTMFRH module failed. The name of the module that was not loaded appears in a previous error message. The load may have failed because the module does not exist in the IOA Load library.

The Control-M New Day procedure terminates.

Corrective Action: If History Jobs file processing is specified in the CTMPARM member, verify that the IOA Load library contains the required module.

FRML64I CTMFRM IS RUNNING IN HISTORY FILE CLEANUP MODELink copied to clipboard

Explanation: This information message indicates that the CTMFRM utility is currently cleaning the History Jobs file.

Corrective Action: No action is required.

FRML65W HISTORY FILE FREESPACE THRESHOLD REACHEDLink copied to clipboard

Explanation: This message is issued during New Day processing when there is insufficient free space in the History file to accommodate the entire Active Jobs file (AJF). The History file becomes full and New Day processing, processing stops.

New Day processing stops.

Corrective Action: Do the following:

Use the CTMHCLN utility to clean the History file.
If the error message is still displayed, use the CTMHCOP utility to increase the size of the History file.

FRML66S OPEN OF CONTROL-M HISTORY FILE FAILED. DDNAME "DAHIST"Link copied to clipboard

Explanation: The Control-M History Jobs file (HST) defined in the DAHIST DD statement could not be opened. The New Day procedure calls the program that issues this message.

A possible cause of this message is that the DAHIST DD statement is missing.

Program execution stops with a condition code of 08.

Corrective Action: Add the statement KEY=DAHIST to the ALCMDAS member in the IOA ENV library, and rerun the DELARCH step of the New Day procedure.

FRML67S INTERNAL ERROR - ARCHIVED SYSOUT POINTER IS INVALID. ORDERID: `jobId`Link copied to clipboard

Explanation: During the New Day procedure, the Control-M Active Jobs file (AJF) was found to be corrupt, due to an internal error. The archived sysout of a job cannot be read.

In this message, jobId is the identity of the job that produced the archived sysout that cannot be read.

The New Day procedure does not delete the archived sysout for the jobId job.

Corrective Action: No action is required.

FRML68I `file` WRITE PROCESSING STARTEDLink copied to clipboard

Explanation: This information message indicates that the CONTROL-M process of writing the updated AJF or HST file has started.

Corrective Action: No action is required.

FRML69I `file` WRITE PROCESSING ENDEDLink copied to clipboard

Explanation: This information message indicates that the CONTROL-M process of writing the updated AJF or HST file has ended.

Corrective Action: No action is required.

FRS messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages FRS400 through FRS4xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

FRS471S OPEN OF IOA CONDITIONS FILE FAILED. DDNAME "DARESC"Link copied to clipboard

Explanation: Open of IOA Conditions file failed (the DARESC DD statement).

This error message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day Procedure.

Possible causes are:

The DARESC DD statement is missing.
The data set described by the DARESC DD statement is not the IOA Conditions file.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the Daily Subsystem and rerun it.

FRS472S OPEN OF IOA SYNCHRONIZATION FILE FAILED. DDNAME "DASINC"Link copied to clipboard

Explanation: Open of IOA Synchronization file failed in the DASINC DD statement.

This error message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day procedure.

Possible causes are:

The DASINC DD statement is missing.
The data set described by the DASINC DD statement is not the IOA Synchronization file.
The data set described by the DASINC DD statement is an IOA Synchronization file, but it is of another Control-M or Control-D monitor, or of a different Control-M or Control-D version.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure and rerun it.

FRS475S INVALID LAST FORMAT DATE IN DATE CONTROL RECORDLink copied to clipboard

Explanation: Invalid format of last format date in the Date Control record. This message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy. Possible causes are:

The record described by the DACHK DD statement is not the Control-M or Control-D Date Control record.
Someone modified the contents of the Date Control Record incorrectly.

For more information, see the descriptions of NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

Correct the JCL for the New Day procedure, and rerun it.
Correct the format date in the Date Control Record.

FRS476S LAST FORMAT DATE IN DATE CONTROL RECORD WAS MORE THAN 28 DAYS AGOLink copied to clipboard

Explanation: The difference between the current working date (date-1) and the last format date in the Date Control Record is greater than 28 days. Possible causes are:

Someone modified the contents of the Date Control Record incorrectly.
The Control-M or Control-D monitor has not been used for more than 28 days. Correct the date to “yesterday.”

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the Date Control Record in the DACHK DD statement, and rerun the Daily Subsystem.

FRS477S FILE ALLOCATED TO DDNAME "DACNDF" IS NOT YOUR IOA CONDITION FILELink copied to clipboard

Explanation: The data set described by the DACNDF DD statement is not the required IOA Conditions file.

The CTMFRM or CTDFRM program issues this error message as part of the New Day procedure when one of the following occurs:

The file allocated to the DACNDF DD statement is not the IOA Conditions file.
The file allocated to the DACNDF DD statement is an IOA Conditions file, but for a different version, or for a different Control-M or Control-D monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure and rerun it.

FRS478I FORMATTING OF IOA CONDITIONS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the formatting of the IOA Conditions file was started by the New Day procedure. The CTMFRM or CTDFRM program clears all the conditions from the day following the last formatting date until the next working date, that is, the first date in the General Date Control Record.

Corrective Action: No action is required.

FRS479I FORMATTING OF IOA CONDITIONS FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the New Day procedure formatted the IOA Conditions file. The CTMFRM or CTDFRM formatting program that the New Day procedure called ended.

Corrective Action: No action is required.

FRS480S ERROR WHILE FORMATTING IOA CONDITIONS FILELink copied to clipboard

Explanation: An error occurred while formatting the IOA Conditions file by the New Day procedure. An earlier error message describes the type of error.

Program execution stops with a condition code of 08.

Corrective Action: Check the IOA Log or the utility output for a previous message concerning the error.

FRS481I CORRUPTED CONDITION WAS ERASED FROM FILELink copied to clipboard

Explanation: This information message indicates that the New Day procedure detected a corrupted condition in the IOA Condition file, and deleted it from the file.

The New Day procedure runs to completion.

Corrective Action: Try to identify the condition involved, and consider whether to add it manually to the file. If necessary, have your INCONTROL administrator contact BMC Customer Support for a fix to the problem.

FST messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages FST700 through FST7xxLink copied to clipboard

This group includes messages for the Control-O product.

FST720I FORMATTING OF STATISTICS FILE STARTEDLink copied to clipboard

Explanation: This informative message is issued when the CTOFST Statistics Formatting utility starts formatting the Statistics file.

Corrective Action: No action is required.

FST721S STATISTICS FILE DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`Link copied to clipboard

Explanation: Dynamic allocation of the Statistics file dsn failed with the return code rc and reason code rsn.

The CTOFST Statistics Formatting utility terminates with the return code 08.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide to determine the cause of the error, and correct the error accordingly. If not successful, contact BMC Customer Support.

FST722W STATISTICS FILE ALLOCATION ERROR - ACTIVE SMF ID DOES NOT MATCH PARAMETER SMF IDLink copied to clipboard

Explanation: The SMF ID specified for the CTOFST Statistics Formatting utility does not match the active MVS SMF ID. The SMF ID for the CTOFST utility is specified in the input PARM string (parmSmfId). The current MVS SMF ID is specified in IEASMFxx of SYS1.PARMLIB(cpuSmfId). These SMF IDs must match.

No error is issued when the systems share the catalog, where the file is cataloged, and the disk, where the file was allocated.

A problem starting the Statistics task, in Control-O monitor, occurs when the systems do not share the catalogs or the disk. This usually occurs when the file should have been cataloged in the MASTER catalog of the target system (parmSmfId) and not the Master catalog of the system where the job was executed (cpuSmfId). In such a case, messages IKJ56228I, CTO196S, and CTO185S will be issued and Control-O monitor will continue to work without collecting statistics.

The CTOFST utility terminates with a condition code of 04.

Corrective Action: Verify that the file was cataloged in the correct CATALOG. If it was not, DELETE the file and rerun the job on the correct system, where parmSmfId and cpuSmfId are the same. After reallocating the Statistics file start Control-O monitor or issue command ‘F control, STARTSTAT’ to start collecting the Control-O statistics.

FST723S STATISTICS FILE IN USE. FORMATTING CANNOT BE PERFORMEDLink copied to clipboard

Explanation: The CTOFST Statistics Formatting utility failed to format the Statistics file because the file is allocated to another user. The CTOFST Statistics Formatting utility attempts to allocate the Statistics file with DISP set to OLD.

The utility terminates with a return code of 08.

Corrective Action: Make sure that no user is allocated to the Statistics file, and rerun the job.

FST724E OPEN OF STATISTICS FILE FAILEDLink copied to clipboard

Explanation: The CTOFST Statistics Formatting utility could not successfully open the Statistics file.

The utility terminates with a return code of 08.

Corrective Action: Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.

FST725E OPEN OF MESSAGES FILE FAILEDLink copied to clipboard

Explanation: The CTOFST Statistics Formatting utility unsuccessfully attempted to open the Messages file specified in the SYSPRINT DD statement. An OPEN request was issued to the Messages file but was unsuccessful. A possible cause is that the SYSPRINT DD statement may not have been specified in the job stream.

The utility terminates with return code 08.

Corrective Action: Look for earlier MVS error messages regarding the opening of the Messages file. Correct the error, and rerun the job.

FST726S FORMATTING OF STATISTICS FILE ENDED WITH ERRORLink copied to clipboard

Explanation: The formatting of the Statistics file was unsuccessful.

The CTOFST Statistics Formatting utility terminates with a return code of 08.

Corrective Action: Look for earlier error messages to determine the cause of the error. Correct the error and rerun the job.

FST729S WRITE OPERATION TO THE STATISTICS FILE FAILEDLink copied to clipboard

Explanation: A WRITE request failed during the formatting of the Statistics file.

The CTOFST Statistics Formatting utility terminates with a return code of 08.

Corrective Action: Delete the Statistics file. Then rerun the job, specifying the SMFID volser and unit. Earlier MVS error messages regarding the Statistics file may indicate the cause of the error.

FST730I FORMATTING OF STATISTICS FILE ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message is issued when the CTOFST Statistics Formatting utility completes with no errors.

Corrective Action: No action is required.

FST731E INVALID PARAMETERSLink copied to clipboard

Explanation: The DEFSTAT utility was called with incorrect parameters.

The utility terminates with the return code 08.

Corrective Action: Correct the parameters and rerun the utility.

FTM messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages FTM100 through FTM1xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

FTM1T0I FILE TRANSFER STARTEDLink copied to clipboard

Explanation: This information message indicates that the File Transfer monitor was started.

Corrective Action: No action is required.

FTM1T3E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:Link copied to clipboard

Explanation: An invalid parameter was passed to the File Transfer monitor by an operator modify command. A list of valid modify parameters is displayed on the operator console following this message.

The modify command is rejected.

Corrective Action: Enter an operator modify command with valid parameters.

FTM1T4S BLDL/ATTACH FAILED FOR TASK `taskName`Link copied to clipboard

Explanation: Initialization of a File Transfer monitor internal task failed. The reason, system code, is on the computer log. Possible causes are:

The task is not in the IOA Load library.
There is insufficient memory for File Transfer monitor.

The File Transfer monitor shuts down.

Corrective Action: Refer to your system programmer for assistance. If necessary, increase the monitor REGION size.

FTM1T5S UNRECOVERABLE ERROR ENCOUNTEREDLink copied to clipboard

Explanation: An unrecoverable error occurred during operation of the File Transfer monitor, while trying to access to the Active Transfer file.

The File Transfer monitor shuts down.

Corrective Action: Examine relevant CTD9B1S-CTD9B9S messages, and take appropriate corrective action. If the problem is not resolved, send the IOA log and the CTDFTM file transfer monitor print-out to BMC Customer Support.

Messages FTM200 through FTM2xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

FTM2T0I FILE TRANSFER MONITOR SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the File Transfer monitor is shutting down.

Corrective Action: No action is required.

FTM2T1S FILE TRANSFER MONITOR ENDED WITH ERRORLink copied to clipboard

Explanation: This information message indicates that the File Transfer monitor ended with an error.

Corrective Action: In the printout of the File Transfer monitor, check the messages which preceded this FTM121S message for an indication of the cause of the error, and take appropriate corrective action.

FTM2T2W FILE TRANSFER MONITOR IS ACTIVE. QNAME "`qName`"Link copied to clipboard

Explanation:Highlighted, unrollable message.

The user attempted to activate the File Transfer monitor when it was already active. More than one File Transfer monitor cannot be active at the same time.

The new File Transfer monitor is not activated.

Corrective Action: No action is required.

FTM2T5I `validModifyParm`Link copied to clipboard

Explanation: This information message displays a valid modify parameter that can be used in File Transfer monitor operator commands. It is issued together with the FTM103E message.

Corrective Action: No action is required.

FTM2T8S RECIPIENT TREE WAS NOT LOADED BECAUSE OF ERROR - MONITOR IS TERMINATING

Explanation: The attempt to load the Recipient Tree failed. As part of the initialization process, the File Transfer monitor attempts to load the Recipient Tree.

The File Transfer monitor shuts down.

Corrective Action: Check other messages in the IOA log and JES log to determine why the Recipient Tree could not be loaded. Fix the Recipient Tree. Then try again to start the File Transfer monitor.

FTM2T9S NO RECIPIENTS WERE FOUND WITH IP ADDRESS. MONITOR IS TERMINATINGLink copied to clipboard

Explanation: The File Transfer monitor was unable to find a recipient with an IP address.

The File Transfer monitor terminates.

Corrective Action: Contact BMC Customer Support.

FTM2TAS SUBTASK IS TERMINATED BY TIMEOUT FOR IPA =`ipAdd`.'Link copied to clipboard

Explanation: The subtask has timed out and been terminated.

The monitor main task periodically checks the status of all its subtasks. When the CPU of a subtask has not changed since the last check, the subtask is considered to be inactive ("hanging"), and the main task of the monitor interrupts the subtask.

The subtask is terminated.

Corrective Action: In the printout of the File Transfer monitor, and in the log of your PC session manager, check the messages which preceded this FTM121S message for an indication of the reason why the subtask was left inactive, and take appropriate corrective action.

FTM2TBS SUBTASK IS TERMINATED BY CANCEL REQUEST FOR IPA = `ipAdd`. PORT = `portNumber`.Link copied to clipboard

Explanation: The File Transfer monitor subtask with the IP address identified in this message has been terminated by an operator modify CANCEL command.

The identified subtask is terminated.

Corrective Action: No action is required.

FTM2TCS THERE ARE NO ACTIVE SUBTASKSLink copied to clipboard

Explanation: This information message indicates that the File Transfer monitor has no active subtasks.

Corrective Action: No action is required.

FTM2TDS FORMAT OF THE MODIFY COMMAND IS NOT CORRECTLink copied to clipboard

Explanation: An invalid operator modify command has been entered.

The command is rejected.

Corrective Action: Correct and reissue the operator modify command.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

FTM2TES THE SUBTASK NUMBER IS NOT DIGITALLink copied to clipboard

Explanation: An invalid subtask number has been specified in an operator modify CANCEL command.

The command is rejected.

Corrective Action: Enter a valid subtask number and reissue the command.

FTM2TFS THE SUBTASK NUMBER EXCEEDS THE TOTAL NUMBER OF THE ACTIVE SUBTASKSLink copied to clipboard

Explanation: The subtask number entered in an operator modify CANCEL command is invalid, because it is greater than the total number of active subtasks.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

The command is rejected.

Corrective Action: Enter a valid subtask number in the operator modify CANCEL command and reissue the command.

FTM2TGS SUBTASK IS ALREADY NOT ACTIVE FOR IPA = `ipAdd` PORT = `portNumber`Link copied to clipboard

Explanation: The File Transfer monitor subtask with the IP address and port number identified in this message is already inactive.

The command is rejected.

Corrective Action: No action is required.

FTM2THS SUBTASK IS TERMINATED BY SUSPEND FOR IPA = `ipAdd` PORT = `portNumber`Link copied to clipboard

Explanation: The File Transfer monitor subtask with the IP address and port number identified in this message has been terminated by an operator modify SUSPEND command.

The subtask is terminated.

Corrective Action: No action is required.

FTM2TIS IPA SPECIFIED IN THE CANCEL COMMAND IS NOT CORRECT.Link copied to clipboard

Explanation: An invalid IP address was specified in an operator modify CANCEL command.

The command is rejected.

Corrective Action: Enter a correct IP address in the CANCEL command and reissue the command.

FTM2TJS THE INTERVAL PARAMETER VALUE IS NOT DIGITAL.Link copied to clipboard

Explanation: An invalid File Transfer monitor sleeping interval has been specified in an operator modify command.

The File Transfer monitor sleeping interval must be a 3-digit number from 1 through 999 seconds.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

The operator modify command is rejected.

Corrective Action: Enter a valid value for the File Transfer monitor sleeping interval and reissue the command.

FTM2TKI THE MODIFY COMMAND `cmdText` IS ACCEPTEDLink copied to clipboard

Explanation: This information message indicates that the cmdText modify command has been accepted by the File Transfer monitor.

Corrective Action: No action is required.

FTO messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages FTOT00 through FTOTxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

FTOT01I TRANSFER START GROUP `groupId` REPORT `repId`Link copied to clipboard

Explanation: This information message indicates that the transfer of the repId report in the groupId group from the Control-D Session Agent started.

Corrective Action: No action is required.

FTOT02I TRANSFER ENDED OK GROUP `groupId`, BYTES `numBytes` (`trfr_rate` BYTES/SEC), REPORT `repId`Link copied to clipboard

Explanation: This information message indicates that the transfer of the repId report in the groupId group from the Control-D Session Agent ended successfully.

The variables in this message are:

groupId - the identity of the group that contains repId
repId - the identity of the report that was transferred
numBytes - the number of bytes transferred
trfr_rate - the transfer rate, in bytes per second

Corrective Action: No action is required.

FTOT04E FUNCTION `func` WAS SUPRESSED BY CTDSE27/CTDX027 EXIT GROUP `groupId` REPORT `repId`Link copied to clipboard

Explanation: A File Transfer option function has been suppressed, either by Control-D Security Exit 27, or by Control-D User Exit 27.

The variables in this message are:

func - the File Transfer option function that was suppressed
groupId - the identity of the group that contains repId
repId - the identity of the report that was to be transferred

The repId report is not transferred.

Corrective Action: If you use Control-D Security Exit 27 to perform some special function instead of or in addition to the standard function, no intervention is required.

Otherwise, correct Control-D Security Exit 27 or Control-D User Exit 27.

FTOT05E UNEXPECTED RETURN CODE `rc` FOR FUNCTION `func` FROM CTDSE27/CTDX027 EXIT GROUP `groupId` REPORT `repId`Link copied to clipboard

Explanation: An unexpected return code was returned by either Control-D User Exit 27 or Control-D Security Exit 27.

The variables in this message are:

rc - the return code
func - the function that was being performed when rc was returned
groupId - the identity of the group that contains repId
repId - the identity of the report on which the function was being performed

The transfer of repId from the Control-D Session Agent is terminated.

Corrective Action: Correct Control-D Security Exit 27 or Control-D User Exit 27.

FTOT06E ERROR IN FTOPARM `errorText`Link copied to clipboard

Explanation: An error was found in the text of a member in the Control-D FTOPARM library.

The transfer of the current message from the Control-D Session Agent is terminated.

Corrective Action: Correct the problematic text in the Control-D FTOPARM library.

FTOT07E TRANSFER HAS BEEN TERMINATED GROUP `groupId`, BYTES `numBytes` (`trfr_rate` BYTES/SEC), REPORT `repId`Link copied to clipboard

Explanation: The transfer of a report has been terminated.

The variables in this message are:

groupId - the identity of the group that contains repId
numBytes - the number of bytes transferred
trfr_rate - the transfer rate, in bytes per second
repId - the identity of the report that was being transferred

The transfer of repId is terminated.

Corrective Action: Examine accompanying messages that explain the reason for the termination of this transfer.

FTOT08E TRANSFER ENDED NOT OK GROUP `groupId`, BYTES `numBytes` (`trfr_rate` BYTES/SEC), REPORT `repId`Link copied to clipboard

Explanation: The transfer of a report ended unsuccessfully (NOT OK).

The variables in this message are:

groupId - the identity of the group that contains repId
numBytes - the number of bytes transferred
trfr_rate - the transfer rate, in bytes per second
repId - the identity of the report that was being transferred

Corrective Action: Examine accompanying messages that explain the reason for the transfer ending NOT OK.

FTOT09E INVALID AFP FILE - repIdLink copied to clipboard

Explanation: You attempted to transfer an invalid AFP report through the FTO Application Server.

The repId variable in this message indicates the identity of the report that was being transferred.

Corrective Action: Examine the AFP file and check its validity.

FTOT0AE TRANSFER CANCELED - FILE IS EMPTY, GROUP groupId REPORT repIdLink copied to clipboard

Explanation: The transfer was canceled because the transferred file is empty.

The variables in this message are:

groupId - the identity of the group that contains the report
repId - the identity of the report that was being transferred

Corrective Action: Check the transferred file, and ensure that it is not empty.

D–F

DAS messagesLink copied to clipboard

Messages DAS600 through DAS6xxLink copied to clipboard

DAS613I DELETE OF ARCHIVED SYSOUTS STARTEDLink copied to clipboard

DAS614I DELETE OF ARCHIVED SYSOUTS ENDEDLink copied to clipboard

DAS615W DELETION OF num ARCHIVED SYSOUT DATASET(S) FAILEDLink copied to clipboard

DAS616E INVALID CARD IN THE "DASCRLST" FILE - dataLink copied to clipboard

DAS617I dsn ARCHIVED DATASETS DELETEDLink copied to clipboard

DAS617E number SYNTAX ERRORS WERE DETECTED IN THE SCRATCH LIST (JOBLIST DATA SET)Link copied to clipboard

DAS618W COMPRESS OF JOBLIST NOT PERFORMEDLink copied to clipboard

Messages DASL00 through DASLxxLink copied to clipboard

DASL71E INVALID RECORD FOUND ON AJF - FILE USAGE VERIFICATION SKIPPEDLink copied to clipboard

DCI messagesLink copied to clipboard

Messages DCID00 through DCIDxxLink copied to clipboard

DCIDA0I CTDCITSB PROCESSING ERROR: EIBFN= func EIBRCODE= errLink copied to clipboard

DCIDA1I CTDCITSB PROGRAM ABEND: ABEND= abendLink copied to clipboard

DCIDA2I INVALID INPUT DATA LENGTHLink copied to clipboard

DCIDA3I INVALID INPUT DATA SPECIFIEDLink copied to clipboard

DCIDA4I DDNAME= ddName NOT DEFINED IN FCTLink copied to clipboard

DCIDA5I CONCURRENT USER LIMIT REACHED - TRY LATERLink copied to clipboard

DCIDA6I FILE IS DISABLED - CANNOT BE ACCESSEDLink copied to clipboard

DCIDA7I SECURITY AUTHORIZATION REQUIRED FN= funcLink copied to clipboard

DCIDA8I I/O ERROR OCCURRED DURING FILE ACCESSLink copied to clipboard

DCIDA9I I/O ERROR ON TEMPORARY STORAGE FILELink copied to clipboard

DCIDB0I NO SPACE ON TEMPORARY STORAGE FILELink copied to clipboard

DCIDB1I FILE PROCESSING COMPLETELink copied to clipboard

DCIDB2I QUEUE DELETION PROCESSING COMPLETELink copied to clipboard

DCIDB3I ERROR INVOKING DYNAMIC ALLOCATION SUBTASK. INLINE SVC WILL BE USEDLink copied to clipboard

DCIDB4I DYNAMIC ALLOCATION ERROR= rc error reasonLink copied to clipboard

DCIDB5I DYNAMIC UNALLOCATION ERROR= rc err rsnLink copied to clipboard

DCIDB6I FILE OPEN ERROR: EIBFN= func EIBRCODE= errCodeLink copied to clipboard

DCIDB7I FILE CLOSE ERROR: EIBFN= func EIBRCODE= errCodeLink copied to clipboard

DCIDB8I UNABLE TO LOAD CTDPARMLink copied to clipboard

DCIDB9I TRANSACTION transid NOT RECOGNIZEDLink copied to clipboard

DDI messagesLink copied to clipboard

Messages DDIG00 through DDIGxxLink copied to clipboard

DDIG01I UTILITY CTDDIG STARTEDLink copied to clipboard

DDIG02E ERROR DETECTED IN func RC= rc DURING ACCESS TO IOA ACCESS METHOD FILELink copied to clipboard

DDIG03I file INDEX ENTRY DETECTED WITHOUT DATA RECORDLink copied to clipboard

DDIG04I INDEX ENTRY DOES NOT MATCH DATA RECORD.Link copied to clipboard

DDIG05I DATA RECORD DETECTED WITHOUT file INDEXLink copied to clipboard

DDIG06I UTILITY CTDDIG ENDED.Link copied to clipboard

DDIG07E ERROR DETECTED IN func RC= rc DURING ACCESS TO IOA ACCESS METHOD FILELink copied to clipboard

DDIG09S INVALID VALUE IN PARAMETER DBFILE. VALID VALUES ARE: ACT, PRM, HST, MIG, MG1-MG9.Link copied to clipboard

DDIG0AI DUPLICATE RECORD FOUND IN file DATA FILELink copied to clipboard

DDIG0CE INVALID PARAMETER, VALID MODE PARAMETER: TEST, TESTMRK OR CHANGELink copied to clipboard

DDIG10I NUMBER OF RECORDS READ FROM DATA FILE= numLink copied to clipboard

DDIG11I NUMBER OF INDEXES READ FROM INDEX file FILE= numLink copied to clipboard

DDIG12I NUMBER OF DUPLICATE RECORDS IN file DATA FILE= numLink copied to clipboard

DDIG13I NUMBER OF RECORDS DELETED FROM file DATA FILE= numLink copied to clipboard

DDIG14I NO ERRORS DETECTED.Link copied to clipboard

DDIG15I NUMBER OF INDEXES TO BE UPDATED IN file FILE= numLink copied to clipboard

DDIG16I NUMBER OF INDEXES TO BE DELETED FROM file FILE= numLink copied to clipboard

DDIG17I NUMBER OF INDEXES TO BE ADDED TO file FILE= numLink copied to clipboard

DDIG18I file INDEX IS MARKED AS READY TO USELink copied to clipboard

DDR messagesLink copied to clipboard

Messages DDRJ00 through DDRJxxLink copied to clipboard

DDRJ81I UTILITY IOADDR STARTEDLink copied to clipboard

DDRJ82I UTILITY IOADDR ENDEDLink copied to clipboard

DDRJ83S INVALID PARAMETER SPECIFICATIONLink copied to clipboard

DDRJ84S OPEN OF FILE "SYSPRINT" FAILEDLink copied to clipboard

DDRJ85S OPEN OF CONTROL FILE FAILED. DDNAME " ddName "Link copied to clipboard

DDRJ86S ALLOCATION FOR MEMBER memName LIBRARY lib FAILEDLink copied to clipboard

DDRJ87S ALLOCATION FOR TABLE FAILEDLink copied to clipboard

DDRJ88S BAD OP-CODE " op_code "Link copied to clipboard

DDRJ89S LOAD FAILED FOR MEMBER " memName "Link copied to clipboard

DDRJ8AW NO TRIGGERED EVENTS MATCHED TRIGGER dsnLink copied to clipboard

DDRJ8BW NO SUCCESSFULLY TRIGGERED EVENTS WERE PROCESSED FOR TRIGGER dsnLink copied to clipboard

DDRJ90S ACCESS RC= rc FOR LIBRARY lib MEMBER memNameLink copied to clipboard

DDRJ91S INSUFFICIENT STORAGE FOR PROCESSLink copied to clipboard

DDRJ92S JOB jobName NOT FOUND IN TABLE tableName OF LIB libLink copied to clipboard

DDRJ93S BAD DATE date SPECIFIEDLink copied to clipboard

DDRJ94I USER: userId TABLE: tableName LIBRARY: libLink copied to clipboard

DDRJ9CE QNAME TABLE ENTRY ERROR. FLAG= num STC= stcName STR= structName LSN= logStreamName HLQ= hiLevelQualifierLink copied to clipboard

DDRJ9DE cbName CONTROL BLOCK NOT FOUND - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

DDRJ9EE qName QNAME TABLE ENTRY NOT FOUND - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

DDRJA1I IOADDS: dsnLink copied to clipboard

DDRJA2S IOADDS FUNCTIONAL SERVER IS NOT OPERATIONAL. DATASET TRIGGERING REQUESTS MAY BE LOST.Link copied to clipboard

DDRJA3I AJF IS BEING FORMATTED. IOADDS WILL WAIT TILL FORMAT FINISHES.Link copied to clipboard

DDRJA4S SYSPLEX TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

DAS615W DELETION OF `num` ARCHIVED SYSOUT DATASET(S) FAILEDLink copied to clipboard

DAS616E INVALID CARD IN THE "DASCRLST" FILE - `data`Link copied to clipboard

DAS617I `dsn` ARCHIVED DATASETS DELETEDLink copied to clipboard

DCIDA0I CTDCITSB PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err`Link copied to clipboard

DCIDA1I CTDCITSB PROGRAM ABEND: ABEND= `abend`Link copied to clipboard

DCIDA4I DDNAME= `ddName` NOT DEFINED IN FCTLink copied to clipboard

DCIDA7I SECURITY AUTHORIZATION REQUIRED FN= `func`Link copied to clipboard

DCIDB4I DYNAMIC ALLOCATION ERROR= `rc error reason`Link copied to clipboard

DCIDB5I DYNAMIC UNALLOCATION ERROR= `rc err rsn`Link copied to clipboard

DCIDB6I FILE OPEN ERROR: EIBFN= `func` EIBRCODE= `errCode`Link copied to clipboard

DCIDB7I FILE CLOSE ERROR: EIBFN= `func` EIBRCODE= `errCode`Link copied to clipboard

DCIDB9I TRANSACTION `transid` NOT RECOGNIZEDLink copied to clipboard

DDIG02E ERROR DETECTED IN `func` RC= `rc` DURING ACCESS TO IOA ACCESS METHOD FILELink copied to clipboard

DDIG05I DATA RECORD DETECTED WITHOUT `file` INDEXLink copied to clipboard

DDIG07E ERROR DETECTED IN `func` RC= `rc` DURING ACCESS TO IOA ACCESS METHOD FILELink copied to clipboard

DDIG0AI DUPLICATE RECORD FOUND IN `file` DATA FILELink copied to clipboard

DDIG10I NUMBER OF RECORDS READ FROM DATA FILE= `num`Link copied to clipboard

DDIG11I NUMBER OF INDEXES READ FROM INDEX `file` FILE= `num`Link copied to clipboard

DDIG12I NUMBER OF DUPLICATE RECORDS IN `file` DATA FILE= `num`Link copied to clipboard

DDIG13I NUMBER OF RECORDS DELETED FROM `file` DATA FILE= `num`Link copied to clipboard

DDIG15I NUMBER OF INDEXES TO BE UPDATED IN `file` FILE= `num`Link copied to clipboard

DDIG16I NUMBER OF INDEXES TO BE DELETED FROM `file` FILE= `num`Link copied to clipboard

DDIG17I NUMBER OF INDEXES TO BE ADDED TO `file` FILE= `num`Link copied to clipboard

DDRJ85S OPEN OF CONTROL FILE FAILED. DDNAME " `ddName` "Link copied to clipboard

DDRJ86S ALLOCATION FOR MEMBER `memName` LIBRARY `lib` FAILEDLink copied to clipboard

DDRJ88S BAD OP-CODE " `op_code` "Link copied to clipboard

DDRJ89S LOAD FAILED FOR MEMBER " `memName` "Link copied to clipboard

DDRJ8AW NO TRIGGERED EVENTS MATCHED TRIGGER `dsn`Link copied to clipboard

DDRJ8BW NO SUCCESSFULLY TRIGGERED EVENTS WERE PROCESSED FOR TRIGGER `dsn`Link copied to clipboard

DDRJ90S ACCESS RC= `rc` FOR LIBRARY `lib` MEMBER `memName`Link copied to clipboard

DDRJ92S JOB `jobName` NOT FOUND IN TABLE `tableName` OF LIB `lib`Link copied to clipboard

DDRJ93S BAD DATE `date` SPECIFIEDLink copied to clipboard

DDRJ94I USER: `userId` TABLE: `tableName` LIBRARY: `lib`Link copied to clipboard

DDRJ9CE QNAME TABLE ENTRY ERROR. FLAG= `num` STC= `stcName` STR= `structName` LSN= `logStreamName` HLQ= `hiLevelQualifier`Link copied to clipboard

DDRJ9DE `cbName` CONTROL BLOCK NOT FOUND - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

DDRJ9EE `qName` QNAME TABLE ENTRY NOT FOUND - DATA SET TRIGGERING REQUEST ABORTEDLink copied to clipboard

DDRJA1I IOADDS: `dsn`Link copied to clipboard

DDRJA6E SYSTEM LOGGER REQUEST `log_req` FAILED: R15= `r15` RETURN= `rc` REASON= `rsn` Link copied to clipboard

DDRJA7E NAME/TOKEN SERVICES REQUEST `serviceRequest` FAILED: R15= `r15`Link copied to clipboard

DDRJACI `qName` QNAME TABLE ENTRY SUCCESSFULLY REGISTEREDLink copied to clipboard

DDRJADE `cbName` CONTROL BLOCK CREATION ERROR - REGISTRATION ABORTEDLink copied to clipboard

DETH56E THE NEW JOB RECORDS ARE INCOMPLETE. CONTINUATION RECORD IS MISSING. RBA `add`Link copied to clipboard

DETH59E CONFIRMATION SEQUENCE NUMBER ERROR. EXPECTED= `exp_num` RECEIVED= `rcv_num`Link copied to clipboard

DETH60W RUN NUMBERS `run_num1` TO `run_num2` OF `jobName` HAVE NOT BEEN CAPTUREDLink copied to clipboard

DETH61E DETECTOR INTERNAL ERROR TYPE `type`Link copied to clipboard

DETH67I DOWNLOAD PROCESS WILL TAKE PLACE SINCE < `rsnText` >Link copied to clipboard

DFG412W THIS CPU HAS SMFID `cpuSmfId` AND NOT `parmSmfId`Link copied to clipboard

DFG416E DYNAMIC ALLOCATION ERROR RC=`rc`, ERROR=`rsn`, DSN=`dsn`Link copied to clipboard

DFG417E CTMMEM ERROR, RC=`rc`Link copied to clipboard

DFL031I UNKNOWN TYPE OF JCL CARD - `stmt`Link copied to clipboard

DFL034E SUBMIT OF MEMBER `memName` FROM THE LIBRARY `lib` FAILEDLink copied to clipboard

DFL035E MEMBER `memName` SHOULD BE SUBMITTED BUT IS NOT IN THE ACTIVE JOBS FILELink copied to clipboard

DFL036E UNRESOLVED VOL=AFF= IN DDNAME `ddName`Link copied to clipboard

DFL037E JCL ERROR WAS FOUND IN MEMBER `memName`Link copied to clipboard

DFL049W DATASET `dsn` IS NOT FOUND IN CATALOG. DDNAME `ddName`Link copied to clipboard

DFL050E INVALID DISPOSITION IS SPECIFIED IN DDNAME `ddName`Link copied to clipboard

DFL185E ERROR WHILE READING SYSOUT FOR MEMBER `memName` JOBID `jobId`Link copied to clipboard

DFL187W UNRESOLVED BACKWARD REFERENCE FOR DDNAME `ddName`Link copied to clipboard

DFL188W UNIT NAME NOT SPECIFIED FOR NEW DATASET IN DDNAME `ddName`Link copied to clipboard

DFL189I MEMBER `memName` PGMSTEP `pgmStep` PROCSTEP `procStep`Link copied to clipboard

DFL190W NOT CATLGD2 MAY BE ENCOUNTERED FOR DDNAME `ddName`Link copied to clipboard

DIB912E ERROR `err` AT LINE line. CURRENT STATEMENT: `stmt`Link copied to clipboard

DIB914I PROGRAM ENDED: `num` KEYS BUILTLink copied to clipboard

DIB917S INTERNAL ERROR WHILE PROCESSING DDNAME `ddName`Link copied to clipboard

DIB918S RETURN CODE `rc` FROM `routineName` ROUTINE, FUNCTION `func`Link copied to clipboard