Messages BAO500 through BAO5xx

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

BAO501I CTBBAO STARTED

Explanation: This information message signals the normal start of program CTBBAO. The Control-M/Analyzer Online Facility produces this message when it orders or forces a balancing mission to the Active Balancing file.

Corrective Action: No action is required.

BAO502S OPEN OF SCHEDULE DATA FAILED. DDNAME "DABAL"

Explanation: Open of Control-M/Analyzer BALMIS library failed.

Possible causes are:

• The DABAL DD statement is missing.
• Either the data set referenced by the DAJOB DD statement cannot be opened for sequential read, or its record length is not 80.

The CTBBAO program ends with errors.

Corrective Action: Consult your INCONTROL administrator.

BAO505S PREVIOUS RUN OF CTBBAO DID NOT FINISH OK

Explanation: A previous run of the CTBBAO program did not finish OK. This program is usually activated as part of the New Day procedure.

date_2 and date_3 (or date_4 and date_5) of the Date Control Record are not equal. Possible causes are:

• The previous run of the CTBBAO program did not finish OK.
• The contents of the User Date Control Record (the DACHK DD statement) have been manually modified.

The CTBBAO program ends with errors.

Corrective Action: Set date_3 (or date_5), positions 25 through 30 (or 50 through 55) in the Date Control Record (the DACHKK DD statement), to the values of date_2 (or date_4). To rerun the same New Day procedure, change all the dates to the value of the previous day.

Note:

When rerunning the New Day procedure, do not order the same mission twice on the same day. First delete previously ordered missions from the Active Balancing file, and then rerun the New Day procedure.

BAO510S SEVERE ERROR IN THE BALANCING DATA. PLEASE NOTIFY THE IOA ADMINISTRATOR

Explanation: A severe error was detected in the scheduling data. This message is issued by the New Day procedure. This message is produced when any scheduling mission (pointed to by the DABAL DD statement) contains erroneous data.

Possible causes are:

• The contents of the mission were incorrectly modified, using an editor or program, and the format of the mission is invalid.
• There was an internal error in Control-M/Analyzer.

The New Day procedure terminates with a condition of code 08.

Corrective Action: Do the following:

• Try to restore the mission to its original state. If you cannot, have your IOA administrator call BMC Customer Support.
• If the mission is a batch New Day procedure using a permanent Date Control Record, correct the contents of the Date Control record before running the New Day procedure again.
• For more information, see the BAO505S message.

BAO511I ID= orderId TASK= taskName PLACED ON THE ACTIVE BALANCING FILE - desc

Explanation: This information message indicates that a mission order was placed on the Active Balancing file. The task is now on the Active Balancing file in Wait Schedule state.

Corrective Action: No action is required.

BAO513I SCHEDULE FAILED FOR num CONTROL-M/ANALYZER CATEGORIES

Explanation: This information message displays the number of Control-M/Analyzer balancing missions categories that were not found in the library allocated to the DABAL DD statement.

In this message, num is the number of balancing missions categories that were not found.

The Control-M/Analyzer New Day procedure continues processing.

Corrective Action: Examine the IOA Log file for the failed categories and associated reasons for failure.

BAO514S INSUFFICIENT STORAGE FOR THE BALANCING MISSION

Explanation: There is insufficient storage for processing the mission order.

The CTBBAO program of the New Day procedure terminates with a condition code of 08.

Corrective Action: Increase the REGION size of the New Day procedure.

BAO515S ERROR IN SCHEDULING DATA - TOO MANY STATEMENTS FOR ONE MISSION

Explanation: The scheduling mission contains too many statements. Scheduling data describing the mission order is too large to be processed by Control-M/Analyzer.

The mission order is not placed on the Active Balancing file. The New Day procedure terminates with a condition code of 08.

Corrective Action: Check the contents of the mission order using the Online Scheduling Facility and omit unnecessary scheduling data. Report this to your INCONTROL administrator.

BAO516S ERROR IN SCHEDULING DATA - FIRST STATEMENT SHOULD START WITH "B"

Explanation: Invalid scheduling data was detected in the first data set pointed to by the DABAL DD statement. The first statement of a valid balancing mission should start with B.

The error could be due to one of the following:

• The data set pointed to by the DABAL DD statement is not a Balancing Mission.
• The Balancing Mission has been manually modified incorrectly.

The CTBBAO program ends with errors.

Corrective Action: Check that the DABAL DD statement refers to a valid Balancing Mission definition.

BAO524S CTBBAO ENDED WITH ERRORS

Explanation: The CTBBAO program ended with errors. It is activated as part of the New Day procedure.

The New Day procedure finishes executing with a condition code of 08. The IOA Log File contains one or more prior messages concerning the errors.

Corrective Action: Examine the IOA Log File for the errors. If necessary, correct the Date Control Record date-3 and date-5 manually for the next run of the New Day procedure.

BAO525I CTBBAO ENDED

Explanation: This information message indicates that the CTBBAO terminating program, which is activated as part of the New Day procedure, has terminated.

Corrective Action: No action is required.

BAO528I MEMBER memName ID= orderId ODATE odate PLACED ON ACTIVE BALANCING FILE - description

Explanation: This information message indicates that a mission order was placed on the Active Balancing file in WAIT SCHEDULE state.

Corrective Action: No action is required.

BAO532S OPEN OF CONTROL-M/ANALYZER ACTIVE BALANCING FILE FAILED. DDNAME “DAABF”

Explanation: Open of Control-M/Analyzer Active Balancing file failed. This error message is issued by the CTBBAO program, which is usually activated as part of the New Day procedure.

Possible causes are:

• The DAABF DD statement is missing.
• The data set pointed to by the DAABF DD statement is not the Control-M/Analyzer Active Balancing file.
• The data set pointed to by the DAABF DD statement is a Control-M/Analyzer Active Balancing file from a different version of Control-M/Analyzer.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the mission or CLIST and rerun it.

BAO534S SEVERE ERROR ON CONTROL-M/ANALYZER ACTIVE BALANCING FILE. NOTIFY THE IOA ADMINISTRATOR

Explanation: Severe error on the Control-M/Analyzer Active Balancing file. This error message is issued by the CTBBAO program, which is usually activated as part of the New Day procedure.

Possible causes are:

• An I/O error.
• The file allocated to the DAABF DD statement is not the Control-M/Analyzer Active Balancing file.
• The Active Balancing file has been corrupted.

The CTBBAO Control-M/Analyzer program ends with errors.

Corrective Action: Ask your IOA administrator to check whether the Active Balancing File has been updated from two computers without global ENQ control, or by an unauthorized program.

BAO535S CONTROL-M/ANALYZER ACTIVE BALANCING FILE IS BEING FORMATTED. TRY AGAIN LATER

Explanation: The New Day procedure is currently formatting the Control-M/Analyzer Active Balancing file. This message is issued by the CTBBAO program which is usually activated as part of the New Day procedure.

Corrective Action: Try again later.

BAO536W THE CONTROL-M/ANALYZER ACTIVE BALANCING FILE IS NEARLY FULL

Explanation: The Control-M/Analyzer Active Balancing file is over 90% full. It contains all the missions to be executed during the night. If it becomes full, it will be impossible to add new missions to Control-M/Analyzer for execution.

Corrective Action: Contact your INCONTROL administrator immediately. It may be necessary to compress the Active Balancing file, or to increase its size.

BAO537S INTERNAL ERROR IN ROUTINE CTBRSV

Explanation: Internal error in the CTBRSV routine. The CTBBAO program ends with errors.

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

BAO538S LOADING OF CONTROL-M/ANALYZER INSTALLATION PARAMETERS FAILED

Explanation: Loading of Control-M/Analyzer Installation Parameters, which are in the CTBPARM member in the IOA PARM library, failed.

Possible causes are:

• There is insufficient memory to load the IOA Installation Parameters.
• The CTBPARM member does not exist in the IOA PARM library.
• The IOA PARM library was updated while you were working and the position of the CTBPARM member has changed.

The requested function is terminated.

Corrective Action: Look in the system log for additional related messages. Try one of the following:

• If loading failed because of lack of memory: increase the REGION size for batch missions; for TSO, try to log on again using a larger SIZE parameter.
• If you are using many IOA screens concurrently, try to exit a few using the END command. This releases memory used by the screens.
• If the PARM library has been modified and you are working under TSO, try to log on again. If you are working under ROSCOE, you may have to shut down ROSCOE and bring it up again.

BAO539S ERROR IN CONTROL-M/ANALYZER INSTALLATION PARAMETERS - INVALID DATETYP

Explanation: Invalid DATETYP Control-M/Analyzer installation parameter. The DATETYP parameter specifies date format used at installation.

Valid values are:

• A (mmddyy)
• W (ddmmyy)
• J (yymmdd)

For more information, see the operational parameters section in the IOA installation chapter in the INCONTROL for z/OS Installation Guide.

The requested function is terminated.

Corrective Action: Contact your INCONTROL administrator. Set the DATETYP parameter in the IOAPARM member to a valid value.

BAO540S CONTROL-M/ANALYZER ACTIVE BALANCING FILE IS FULL. NOTIFY THE IOA ADMINISTRATOR

Explanation: Highlighted, unrollable message.

The Control-M/Analyzer Active Balancing file is full. There is no more space in the Active Balancing file for new missions.

The mission order is not placed in the Active Balancing file.

Corrective Action: Contact your IOA administrator immediately. It may be necessary to increase its size. Compress the Active Balancing files.