Messages DDRJ00 through DDRJxx

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

DDRJ81I UTILITY IOADDR STARTED

Explanation: This information messages indicates that IOADDR utility started.

Corrective Action: No action is required.

DDRJ82I UTILITY IOADDR ENDED

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

Corrective Action: No action is required.

DDRJ83S 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.

DDRJ84S 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.

DDRJ85S 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.

DDRJ86S 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.

DDRJ87S 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.

DDRJ88S 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.

DDRJ89S 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.

DDRJ8AW NO TRIGGERED EVENTS MATCHED TRIGGER dsn

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

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

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:

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 PROCESS

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

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 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.

DDRJ94I 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.

DDRJ9CE 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 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 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.

DDRJ9EE 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.

DDRJA1I 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, 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.

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.

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 ABORTED

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 ABORTED

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

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

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 ABORTED

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 ABORTED

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 ABORTED

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 IOADDR

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 REGISTERED

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

Corrective Action: No action is required.

DDRJADE 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.

DDRJAEE 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.