Messages CTMJ00 through CTMJxx

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.

CTMJ02E ddName BEING FORMATTED. TRY AGAIN LATER

Explanation: The ddName file is currently being formatted.

This error message may be issued as part of the New Day procedure, or some other component that formats the file. It is also possible that a component attempted to format the file, but failed, leaving the file unusable (in status “FORMAT”).

Corrective Action: Try again later. If no component is currently formatting the file, the file must be reformatted before it can be used.

CTMJ03E ddName - PARM QNAME qName1 DIFFERENT THAN IN FILE qName2

Explanation: QNAME qName1 defined in CTMPARM differs from QNAME qName2 specified in the file pointed to by the ddName DD statement. The QNAMEs of the files must be identical to the QNAME specified in CTMPARM.

Processing of the current command stops with a return code of 8.

Corrective Action: Reformat the file pointed to by the ddNameDD statement, using the proper installation procedures.

CTMJ81I UTILITY IOADDR STARTED

Explanation: This information messages indicates that the IOADDR utility started.

Corrective Action: No action is required.

CTMJ82I UTILITY IOADDR ENDED

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

Corrective Action: No action is required.

CTMJ83S INVALID PARAMETER SPECIFICATION

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.

CTMJ84S OPEN OF FILE "SYSPRINT" FAILED

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.

CTMJ85S OPEN OF CONTROL-FILE FAILED. DDNAME "ddName"

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.

CTMJ86S ALLOCATION FOR MEMBER memName LIBRARY lib FAILED

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.

CTMJ87S ALLOCATION FOR TABLE FAILED

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.

CTMJ88S BAD OP-CODE "op_code"

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.

CTMJ89S LOAD FAILED FOR MEMBER "memName"

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.

CTMJ90S ACCESS RC=rc FOR LIBRARY lib MEMBER memName

Explanation: An error occurred in the IOADDR utility when reading a member from a PDS library. The return code describes the reason for the error.

Valid values for the return code (rc) are:

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.

CTMJ91S INSUFFICIENT STORAGE FOR PROCESS

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

The IOADDR utility terminates.

Corrective Action: Increase the REGION size.

CTMJ92S JOB jobName NOT FOUND IN TABLE tableName OF LIB lib

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.

CTMJ93S BAD DATE date SPECIFIED

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.

CTMJ94I USER: userId TABLE: tableName LIBRARY: lib

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.

CTMJ9CE QNAME TABLE ENTRY ERROR. FLAG=num STC=stcName STR=structName LSN=logStreamName HLQ=hiLevelQualifier

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 method used to transfer the IOADDC input trigger to Control-M Possible 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.

CTMJ9DE cbName CONTROL BLOCK NOT FOUND - DATA SET TRIGGERING REQUEST ABORTED

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.

CTMJ9EE qName QNAME TABLE ENTRY NOT FOUND - DATA SET TRIGGERING REQUEST ABORTED

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.

CTMJA1I IOADDS: dsn

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, for example, 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 that either IOADDC is activated in an APF-authorized environment, or that measures have been taken to handle this message.

CTMJA2S IOADDS FUNCTIONAL SERVER IS NOT OPERATIONAL. DATASET TRIGGERING REQUESTS MAY BE LOST

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.

CTMJA3I AJF IS BEING FORMATTED. IOADDS WILL WAIT TILL FORMAT FINISHES.

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

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

Corrective Action: No action is required.

CTMJA4S SYSPLEX TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTED

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

Possible causes are:

• the Sysplex table is not present in the PARM library
• the internal format of the table is invalid

The interface module aborts the request.

Corrective Action: Check why the Sysplex table is not in the PARM library, or why its internal format is invalid. Correct the problem and retry the request.

CTMJA5S CMMPLEX TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTED

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

Possible causes are:

• The CMMPLEX table is not present in the PARM library.
• The internal format of the table is invalid.

The interface module aborts the request.

Corrective Action: Check why the CMMPLEX table is not in the PARM library, or why its internal format is invalid. Correct the problem and retry the request.

CTMJA6S SYSTEM LOGGER REQUEST xxxxxx FAILED: R15=rc15 RETURN=rcx REASON=rsn

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)
• DISLGS, IXGCONN (disconnect from log stream)
• DELLGS, IXGINVNT (delete log stream)
• DELCFS, IXGINVNT (delete coupling facility structure)

rc15 is the return code in Register 15 that identifies the error, and is one of the following:

The return code rcx and reason code rsn are documented in the IBM manual MVS Programming: Assembler Services Reference, which contains the relevant system action. Each of the System Logger requests identified by the return code rc15 is in a separate section of that publication, which also contains the possible values for the return code rcx and the reason code rsn for that System Logger request.

Corrective Action: If you have any difficulty interpreting the IBM publication, contact your INCONTROL administrator.

CTMJA7E NAME/TOKEN SERVICES REQUEST xxxxxxxx FAILED: R15=rc

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

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

The return code rc is documented in the IBM manual MVS Programming: Assembler Services Reference, which contains the relevant system action. Each of the name/token services requests xxxxxxxx is in a separate section of the publication, which also contains the possible values for the return code rc for that request.

Corrective Action: If you have any difficulty interpreting the IBM publication, contact your INCONTROL administrator.

CTMJA8E PARAMETER (DATA SET NAME) LENGTH ERROR - DATA SET TRIGGERING REQUEST ABORTED

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

The interface module aborts the request.

Corrective Action: Specify an appropriate data set name trigger, then retry the request.

CTMJA9S IOACPRM TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTED

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

Possible causes are:

• the IOACPRM table is not present in the PARM library
• the internal format of the table is invalid

The interface module aborts the request.

Corrective Action: Check why the IOACPRM table is not in the PARM library, or why its internal format is invalid. Correct the problem and retry the request.

CTMJAAS SYSTEM LOGGER INTERFACE NOT ENABLED BY USER - DATA SET TRIGGERING REQUEST ABORTED

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

The interface module aborts the request.

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

CTMJABW SYSTEM LOGGER INTERFACE NOT OPERATIVE - DATA SET TRIGGERING REQUEST PROCESSED BY IOADDR

Explanation: The System Logger interface is not enabled (SYSTLOGR parameter value in the IOACPRM parameters 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.

CTMJACI qName QNAME TABLE ENTRY SUCCESSFULLY REGISTERED

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

Corrective Action: No action is required.

CTMJADE cbName CONTROL BLOCK CREATION ERROR - REGISTRATION ABORTED

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.

CTMJAEE NO AVAILABLE ENTRIES IN QNAME TABLE - REGISTRATION ABORTED

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.