Messages DVL300 through DVL3xx

This group includes messages for the Control-O product.

DVL341S AUTOMATION LOG FILE LEVEL INCONSISTENT WITH LEVEL OF CONTROL-O

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 FILE

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

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 ERROR

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 RDJFCB

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 LOG

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 INSTALLATION

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 FILE

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 ACCESSED

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.