|
|
|
|
|
This group includes messages for the Control-M/Analyzer product.
Explanation: This information message signals the normal start of the CTBBAO program. 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.
Explanation: Open of Control-M/Analyzer BALMIS library failed.
Failure is due to one of the following:
The CTBBAO program ends with errors.
Corrective Action: Consult your INCONTROL administrator.
Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement). This message is issued by the CTMJOB program, which is usually activated by the New Day procedure.
Possible causes are:
The CTMJOB program ends with errors.
Corrective Action: Correct the JCL for the job/CLIST.
Explanation: The data set described by the DACHK DD statement is empty.
The CTMJOB program ends with errors.
Corrective Action: Correct the JCL for the job/CLIST.
Explanation: An invalid value was specified for the GEN TYPE (generation type) field. Valid values for the GEN TYPE field are
Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.
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 CTBBAO program ends with errors.
Corrective Action: Set date-3 (or date-5), positions 25-30 (or 50-55) in the Date Control Record (the DACHK 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 day before.
Note:
Do not order the same mission twice on the same day when rerunning the New Day procedure. First delete previously ordered missions from the Active Balancing file, and then rerun the New Day procedure.
Explanation: Scheduling failed for the memName member. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.
The IOA Log or the output of the job should contain an additional message concerning the reason for failure.
The job order of member is not placed in the Active Jobs file. Depending on the severity of the problem, the New Day procedure will continue to the next job order or terminate with a condition code of 08.
Corrective Action: Check the IOA Log or the job’s output for the reason.
Explanation: Invalid last monthly Scheduling Date.
The last monthly Scheduling Date (positions 18-23) in the User Date Control Record is greater than the current original Scheduling Date (positions 1-6). Possible causes are:
For more details refer to the INCONTROL for z/OS Administrator Guide.
The CTMJOB program ends with errors.
Corrective Action: Correct the User Date Control Record (the DACHK DD statement).
Explanation: The last monthly scheduling date is more than 28 days ago.
Possible causes are:
For more details refer to the INCONTROL for z/OS Administrator Guide.
Program execution stops with a condition code of 08.
Corrective Action: Correct the dates in the User Date Control Record (the DACHK DD statement).
Explanation: A severe error was detected in the scheduling data. This message is issued by the New Day procedure. This message is produced when a scheduling mission (pointed to by the DABAL DD statement) contains erroneous data.
Possible causes are:
The New Day procedure terminates with a condition code of 08.
Corrective Action: Try to restore the mission to its original state. If you cannot, have your IOA administrator call BMC Customer Support for assistance. 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.
Explanation: The name specified in the field contains leading or embedded blanks. Only trailing blanks are valid in this field. The cursor points to the invalid value.
Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.
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.
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.
Explanation: The value specified in the field does not start with an alphabetic character. The first character in the value must be alphabetic. The cursor points to the invalid value.
Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.
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.
Explanation: The value specified in the field contains non-alphanumeric characters. Only alphanumeric characters are valid in this field. The cursor points to the invalid value.
Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.
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 CTBBAO program ends with errors.
Corrective Action: Check that the DABAL DD statement refers to a valid Balancing Mission definition.
Explanation: An invalid number of generations was specified. Values for the MAXIMUM ACTIVE GENERATIONS field must be from 1 through 1000.
Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.
Explanation: The DD statement pointing to the job scheduling tables is empty or missing.
The program ends with errors.
Corrective Action: Correct the JCL for the job or CLIST.
Explanation: Invalid year in the User Date Control record used by the New Day procedure.
This year is not supported by the release of Control-M you are using.
The CTMJOB program ends with errors.
Corrective Action: Correct the YEAR field (the DACHK DD statement).
Explanation: Invalid previous weekly Scheduling Date in the User Date Control record (positions 43-48). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.
This date (date-4 of User Date Control record) might not be equal to date-5 (positions 50-55) or in invalid format. Valid format is ddmmyy or mmddyy. Possible causes are:
For more details refer to the INCONTROL for z/OS Administrator Guide.
The New Day procedure will end with errors.
Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.
Explanation: No name was specified for the variable. The NAME field is mandatory in the Variable Definition screen.
Corrective Action: Specify a valid name, or use the CANCEL command to exit without saving the database variable definition.
Explanation: An error occurred while attempting to update a variable in the database Variable Definition screen. The database variable definition is not updated.
Corrective Action: Ask your INCONTROL administrator to call BMC Customer Support.
Explanation: An error occurred while attempting to update or create a variable in the database Variable Definition screen.
The database variable definition is not updated.
Corrective Action: Ask your INCONTROL administrator to call BMC Customer Support.
Explanation: Invalid original scheduling date in the User Date Control Record (positions 1-6). This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.
Valid format is ddmmyy or mmddyy. The message may be due to one of the following:
For more details, refer to the INCONTROL for z/OS Administrator Guide.
The New Day procedure will end with errors.
Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.
Explanation: A database variable name was specified in the database Entry Panel, but a specific group name was not specified.
There are four possible system actions:
Corrective Action: Specify a group name or delete the database variable name.
Explanation: Invalid previous monthly scheduling date in the User Date Control Record (positions 18-23). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.
This date (date-2 of User Date Control Record) should be equal to date-3 (positions 24-29) or in valid format. The valid format is ddmmyy or mmddyy.
Possible causes are:
For more details refer to the INCONTROL for z/OS Administrator Guide.
The CTMJOB program ends with errors.
Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.
Explanation: An error occurred during an attempt to open or read the Control-M/Analyzer database. The error occurred during online processing from a screen under Main Menu option BV (database Variables).
No information is retrieved. The screen is exited.
Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support of the error message, return code and function.
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.
Explanation: An attempt was made to create a variable, but a variable with the same name already exists in the group. The variable cannot be created because it already exists. It cannot be saved because it was specified using the Insert command.
The Exit Option Window is closed. The database Variable Definition screen remains displayed.
Corrective Action: Either specify a database variable name that does not currently exist in the group, or use the CANCEL command to exit without saving the database variable definition.
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.
Explanation: A request was made to save a database variable which was not yet created in the group. After inserting a variable in a group and exiting, the Exit Option Window is displayed. The SAVE option in the window is valid only for existing database variables. The CREATE option must be used to create new database variables.
Corrective Action: Either specify option CREATE to create the database variable, or press the RESET key (PF04) to close the window without saving the database variable.
Explanation: More than one option was specified in the Exit Option Window. When exiting the database Variable Definition screen, the Exit Option Window is opened. It contains two options: SAVE and CREATE. A value can be specified for only one of the exit options. Valid values are Y (Yes) or N (No).
Corrective Action: Specify Y or N for either SAVE or CREATE (but not both), or press the RESET key (PF04) to close the window without saving the database variable.
Explanation: An invalid value was specified in the CREATE or UPDATE field in the Group Window.
Valid values for CREATE or UPDATE in the Group Window are
Corrective Action: Specify Y or N in the CREATE or UPDATE field.
Explanation: An invalid value was specified in the GROUP field in the New Group Window. When inserting a new group in the Group List, the GROUP field in the New Group Window must contain an alphanumeric value with no leading blanks.
Corrective Action: Specify a valid name in the GROUP field.
Explanation: The last weekly scheduling date in the Date Control Record is greater than the current original scheduling date.
This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure. Date-4 (positions 43-48) should not be greater than date-1 (positions 1-6) in the Date Control Record. The message may be due to one of the following:
For more details, refer to the INCONTROL for z/OS Administrator Guide.
Program execution stops with a condition code of 08.
Corrective Action: Correct the User Date Control Record (the DACHK DD statement) and rerun the New Day procedure.
Explanation: A group with the name specified in the New Group Window already exists. Group names must be unique. When inserting a new group, the name of an existing group cannot be specified in the GROUP field of the New Group Window.
Corrective Action: Specify a unique group name, or cancel the create request by specifying N (No) in the CREATE field of the window.
Explanation: The last weekly scheduling date is more than 28 days ago.
Possible causes are:
For more details, refer to the INCONTROL for z/OS Administrator Guide.
Program execution stops with a condition code of 08.
Corrective Action: Correct the dates in the Date Control Record (the DACHK DD statement) and rerun.
Explanation: An invalid value was specified in the GROUP MODE field in the Group Window.
Valid values for the GROUP MODE field in the Group Window are:
Corrective Action: Specify a valid GROUP MODE value.
Explanation: This information message indicates that a group was successfully updated or added to the database Group List.
Corrective Action: No action is required.
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:
Program execution stops with a condition code of 08.
Corrective Action: Correct the JCL for the mission/ CLIST and rerun it.
Explanation: An option other than Insert was requested in an empty Group. If the Variables List for a group contains no variables, Insert is the only operation permitted. Insert is the first operation which should be performed in a new group, in order to insert the first variable and to add it to the list of variables.
Corrective Action: Either request option Insert, or exit the database Variable List screen.
Explanation: The DESCRIPTION field in the New Group Window is empty. The DESCRIPTION field is mandatory when creating a new group.
Corrective Action: Fill in the DESCRIPTION field.
Explanation: Severe error on 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:
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.
Explanation: This information message is issued when the database Variable Definition screen is exited without saving changes (for example, by specifying CANCEL, or by specifying N (No) in the SAVE or CREATE field in the Exit Option Window).
Corrective Action: No action is required.
Explanation: The name of the group specified in the database Entry Panel does not exist. Only names of existing groups can be specified in the Entry Panel. To define a new group, use the Insert option in the Group List.
Corrective Action: Either specify an existing group name, or clear the GROUP field and define the new group in the Group List.
Explanation: Severe error was found in the scheduling data statements. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.
Scheduling fails for the job order. The CTMJOB program terminates with a condition code of 08.
Corrective Action: Look for additional messages concerning the error, correct the error and rerun.
Explanation: This information message indicates that a prefix was specified in the VARIABLE field in the database Entry Panel, but no matches were found in the specified group. A prefix specified in the VARIABLE field must match at least one existing database variable.
The database Variable Definition screen can be accessed directly from the database Entry Panel by specifying an existing group and an existing variable prefix. If only a group name is specified, the database Variable List for the group is displayed.
Corrective Action: Specify the prefix of an existing variable to display the database Variable Definition screen, or clear the VARIABLE field to display the database Variable List for the group.
Explanation: Internal work areas of the New Day procedure have been exhausted.
The job order contains more data than can be handled by the current release of Control-M.
The New Day procedure terminates with a condition code of 08.
Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.
Explanation: This information message indicates that a prefix was specified in the GROUP field in the database Entry Panel but no matches were found in the database. A prefix specified in the GROUP field must match at least one existing group. The matching Group List is then displayed.
If the GROUP and VARIABLE fields are both blank in the Entry Panel, the entire Group List is displayed.
Corrective Action: Specify the prefix of an existing group to display an abbreviated Group List, or clear the GROUP field to display the entire Group List.
Explanation: Loading of Control-M/Analyzer Installation Parameters, which are in the CTBPARM member in the IOA PARM library, failed.
Possible causes are:
The requested function is terminated.
Corrective Action: Look in the system log for additional related messages. Try one of the following:
Explanation: Invalid DATETYP Control-M/Analyzer Installation Parameter. The DATETYP parameter specifies the date format used at installation.
Valid values are:
For more details, see the section on operational parameters 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.
Explanation: An attempt to view generations of database variables failed. Option V (View) was specified in the Variables List Panel to display all active generations of the selected specific database variable.
The View operation is not performed.
Corrective Action: Ask your INCONTROL administrator to call BMC Customer Support.
Explanation: Highlighted, unrollable message.
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 it size. Compress the Active Balancing files.
Explanation: Loading of the specified IOA security module failed. Possible causes are:
As a result, no security checking is performed. For more details, refer to the sections on Security Interface Modules in the appropriate security guides.
Corrective Action: Notify the INCONTROL administrator. This is a potentially serious situation. Someone may be attempting to violate security.
Explanation: An operation other than Insert was attempted although there are no groups in the database.
When the database is empty and there are no existing groups, the only operation permitted is Insert. Insert is the first operation that must be performed in the Group List. After the first group is created, Select and Update operations are also permitted.
Corrective Action: Specify an Insert operation, or exit the Group List screen.
Explanation: An attempt was made to Insert a new variable, but there is not enough space in the database. No new variables can be defined until sufficient space is provided.
The new variable is not created.
Corrective Action: It may be possible to create the variable by requesting fewer generations. In any case, more free file space should be provided. Use the CTBDBVCP utility to copy the file to a new enlarged file, or use the CTBDBVDL utility to compress the file. For more information, see the INCONTROL for z/OS Utilities Guide.
Explanation: An attempt was made to Insert a new variable, but there is insufficient space in the database Variable Basic file. The file is full or nearly full. No new variables can be defined until sufficient space is provided.
The new variable is not created.
Corrective Action: You must provide more file space. Use the CTBDBVCP utility to copy the file to a new enlarged file, or use the CTBDBVDL utility to compress the file. For more information, see the INCONTROL for z/OS Utilities Guide.
Explanation: An attempt was made to Insert a new variable, but there is insufficient space in the database Variable Basic Index file. The file is full or nearly full. No new variables can be defined until sufficient space is provided.
The new variable is not created.
Corrective Action: Use the CTBDBVCP utility to copy the file to a new enlarged file, or use the CTBDBVDL utility to compress the file. For more information, see the INCONTROL for z/OS Utilities Guide.
Explanation: The user is unauthorized to perform the requested Insert or Update on the variable.
The new variable is not created or updated.
Corrective Action: If you think you should be authorized to perform the attempted operation, contact your INCONTROL administrator.
Explanation: The user attempted to view a graph of a specific variable, but the variable was empty, and as a result, the graph option failed. A variable must have a value to be viewed as a graph.
Corrective Action: Verify that the variable specified has a value.
Parent Topic |