Previous Topic

Next Topic

Book Contents

Book Index

Messages DFL0 through DFL0xx

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=SCAN

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

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 FAILED

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

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"

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

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 FAILED

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 FILE

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

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

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 STARTED

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

Corrective Action: No action is required.

DFL039I TAPE PULL LIST UTILITY ENDED

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 SUBMISSION

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

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

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.

Parent Topic

DFL messages