|
|
|
|
|
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.
Explanation: ISPF generates this message when an ISPF service returns an invalid return code of 12 or higher. The message text describes the specific problem.
The ISPF service is abnormally terminated.
Corrective Action: Check the information provided in the error message. Note that many problems can be resolved by exiting and reentering ISPF.
Explanation: ISPF returned an invalid return code, usually an RC less than 12. This general message may be issued for any ISPF service, such as TBADD, TBPUT, VCOPY, and so on.
The ISPF service is abnormally terminated.
Corrective Action: Many problems can be solved by exiting and reentering ISPF.
Explanation: The LOCATE command failed to find the required parameter.
The lines on the screen remain in their original position.
Corrective Action: No action is required.
Explanation: The command entered is not a valid command.
The command is ignored.
Corrective Action: Correct the command entry. You may use the Help command (PF1) to display a list of the available commands.
Explanation: This information message indicates that a CANCEL command was entered. The user requested that all changes made to the current table or plan be ignored.
The changes are not kept in the library.
Corrective Action: No action is required.
Explanation: An invalid value was entered in the OPTION field.
The invalid option is ignored.
Corrective Action: Enter a valid option. Valid options are listed in the error message. Use the Help command (PF1) to display a list and explanation of the available options.
Explanation: The facility could not create a new Master Table or Plan. The ISPF service TBADD failed with the return code rc specified in the message.
The table or plan is not created.
Corrective Action: Check the return code of the TBADD service. Many problems are solved by exiting and reentering ISPF.
Explanation: This information message indicates that a new table or plan was added to the library.
Corrective Action: No action is required.
Explanation: The facility found an existing table or plan with the same name. Each Master Table or Plan must have a unique name in the system.
The Master Table or Plan is not created.
Corrective Action: Assign another name to the table you want to create.
Explanation: An internal error occurred during the Display Type definition syntax check.
The User Report List is not displayed.
Corrective Action: Contact BMC Customer Support.
Explanation: The facility could not find the specified Master Table or Plan. It can be created now).
Corrective Action: To create a new Master Table or Plan, fill in the required details. To exit and return to the previous menu, press PF03 or PF15.
Explanation: The facility cannot update the AutoEdit member in the library because the AutoEdit parameters library is full.
The parameters member will not be created or updated.
Corrective Action: Compress the AutoEdit library.
Explanation: The facility cannot perform dynamic allocation for the data set. The most probable cause is that the data set is held by another user or job.
The operation is terminated immediately.
Corrective Action: Check what prevented the dynamic allocation. If it was because another user held the data set, try again later.
Explanation: The facility received an invalid return code from IOACND. The facility tried to add the condition to the IOA Conditions file by using the IOACND program. The operation failed.
The condition is not added.
Corrective Action: Check the messages produced by IOACND and proceed accordingly.
Explanation: This information message indicates that the AutoEdit member was updated in the library. The facility updated the parameter in the AutoEdit member.
Corrective Action: No action is required.
Explanation: The facility cannot find the IOA Log file having the specified prefix. The facility uses the IOA Log file, and other files to add a condition to the Conditions file. Only the log file is checked, since all the files have the same prefix.
The operation stops immediately.
Corrective Action: Check the IOA files prefix in the Primary Menu.
Explanation: The facility cannot find any tables in the Master Table List. The PROMPTB Table, which contains the Master Table List, is not found. The reason may be that a user specified Option 2 of the facility before defining at least one Master Table.
The facility returns to the Primary Menu.
Corrective Action: Define at least one Master Table in Option 1.
Explanation: You tried to close the Save/Create Window without specifying whether or not to save or create the defined parameters and conditions. When exiting the Define Parameters and Conditions screen in the Parameter Prompting Facility Type 1, the Save/Create Window is opened. Option Y or N must be specified to save or create.
Corrective Action: No action is required.
Explanation: This information message confirms that the specified table will be deleted from the table list displayed by the Parameter Prompting facility (PPF) (Type 1) and from the table prompt library, as requested. The system issues this message after the user confirms the delete request.
As soon as the system finishes deleting the table, it redisplays the PPF Table Selection screen.
Corrective Action: No action is required.
Explanation: Changes to the table were not saved or cancelled. After making changes in a table, you must enter SAVE or CANCEL to leave the table. SAVE saves the changes; CANCEL leaves the table unchanged.
Corrective Action: Enter SAVE or CANCEL.
Explanation: There is no table name prefix or plan name.
Corrective Action: Enter the table name prefix or plan name.
Explanation: The facility cannot find the tableName table in the lib library.
Corrective Action: Do one of the following:
Explanation: The parameter name is missing from the Daily or Master Table, so the facility cannot update the parameter.
Corrective Action: Define the parameter using Option 1.
Explanation: The facility cannot read the existing Daily Table or create a new one. The table is probably in use by another user.
The Daily Table is not displayed.
Corrective Action: Try again later.
Explanation: The table list contains the name of a Master Table that the facility cannot find in the library.
The facility returns the Master Table List to the user.
Corrective Action: Delete the Master Table name from the Master Table list.
Explanation: The facility cannot copy the Master Table to Daily Table. When a member cannot be copied from one library to another, it may be because a member with the same name already exists in the target library.
The facility returns the Master Table List to the user.
Corrective Action: Check the Table library.
Explanation: This information message indicates that the specified parameter was successfully updated, and the specified prerequisite condition was added to the IOA Conditions file.
Corrective Action: No action is required.
Explanation: This information message indicates that the specified parameter was updated, but the specified prerequisite condition was not added to the IOA Conditions file, because the condition already existed in the file. While the requested parameter change was successful (that is, the facility updated the parameter), it was unnecessary to add the condition to the Conditions file because the parameter had already been updated that day.
Corrective Action: No action is required.
Explanation: The facility cannot get enough virtual storage to create or read an AutoEdit member because the REGION size is too small.
The member is not created or updated.
Corrective Action: Exit ISPF and try to re-enter; or increase the REGION size.
Explanation: The facility can not read the AutoEdit member from the library. There is probably a general system problem with the library file.
The member is not created or updated.
Corrective Action: Check the AutoEdit library file for general systems problems.
Explanation: Invalid TYPE specified.
Corrective Action: Correct the TYPE field.
Explanation: This type has already been defined for this parameter.
Corrective Action: Enter a correct TYPE combination.
Explanation: This type conflicts with the previous types in the TYPE definition for the parameter. The combination is invalid.
Corrective Action: Enter a correct TYPE combination.
Explanation: An invalid value was entered after MINL or MAXL, which specifies the length limit. Valid values are number between 1- 99.
Corrective Action: Enter a valid number after MINL or MAXL.
Explanation: The parameter does not match the type specified in the message.
Corrective Action: Enter a value which is appropriate to the TYPE.
Explanation: The facility cannot call the validation routine CTMTVAL. The CTMTPRP program, which is operated from CTMEXEC, failed to call the CTMTVAL validity check routine.
CTMEXEC terminates abnormally.
Corrective Action: Check the IOA Load library.
Explanation: The date format is invalid. The date field contains data, but the format of the date is not ddmmyy or mmddyy.
The panel is redisplayed with an error message.
Corrective Action: Enter date in the correct format.
Explanation: The facility cannot allocate the lib library. The facility failed to allocate an existing library, or to create a new Daily library.
The current operation is abnormally terminated.
Corrective Action: If the library already exists, try displaying it. If the library is a new library, check to see if there is sufficient free space on the disk.
Explanation: The facility cannot find the tableName Scheduling Table in the lib library.
The current operation is terminated.
Corrective Action: Add the Scheduling Table to the library.
Explanation: There is no default value for this parameter. There is a request for the default value of the parameter to be used; however, this parameter does not have a default value.
No value is set for the parameter.
Corrective Action: Enter the value for the parameter.
Explanation: This information message indicates the facility updated the AutoEdit member. The facility does not order the jobs of the Daily Plan more than once. However the AutoEdit member is updated with the current value of the parameters in the plan.
Corrective Action: No action is required.
Explanation: This information message indicates that the plan contains parameters without values. Therefore, the plan cannot be ordered by Control-M. A plan is ordered by Control-M only when all the parameters contain values.
The plan is not ordered.
Corrective Action: Enter values for the parameters.
Explanation: Another user is probably performing an EXEC using the REMAIN option.
The EXEC phase is not performed.
Corrective Action: Try again later.
Explanation: The facility cannot read the parameters from the plan.
The plan will not be ordered by Control-M, and the AutoEdit member will not be created.
Corrective Action: Exit, and then re-enter, ISPF.
Explanation: This informational message indicates that the user specified YES in the REMAIN option of CTMEXEC, and CTMEXEC finished processing all the plans in the Daily library.
Corrective Action: No action is required.
Explanation: The facility tried to create a new member in the AutoEdit library, but a member with the specified name already exists in the library.
The AutoEdit member is not created and the plan is not ordered by Control-M.
Corrective Action: Check the AutoEdit library.
Explanation: This informative message indicates that the plan was ordered by Control-M.
Corrective Action: No action is required.
Explanation: The facility cannot find the Index Table in the Daily library that is created during the FETCH phase. The Index Table, which is created during the FETCH phase, contains information on all the Daily Plans that were fetched for that day.
The EXEC is not performed.
Corrective Action: Perform the FETCH again, and then execute CTMEXEC.
Explanation: This is an internal facility error. The FETCH phase was not completed. Due to previous errors during the FETCH, the Daily libraries do not contain all the information required to perform the EXEC.
The EXECUTE phase for the plan is terminated.
Corrective Action: Execute the FETCH for the plan again.
Explanation: This information message indicates that the status of the plan was changed while the user was in the Plan Selection screen. The plan was probably executed by another user while the list of plans was displayed.
The list of plans is redisplayed.
Corrective Action: Select the plan again.
Explanation: This informative message indicates that the facility has successfully performed the FETCH phase for the plan.
Corrective Action: No action is required.
Explanation: The facility received a non-zero return code when trying to read or update the Scheduling Table. The CTMMEM program returned a non-zero return code when the facility accessed the Scheduling library. The Daily Scheduling library may need to be compressed.
The FETCH phase is not completed.
Corrective Action: Compress the Daily Scheduling library, and perform the FETCH again.
Explanation: The facility cannot find the Master Plan in the Master Plan library. During the FETCH phase, the facility copies the Master Plan to the Daily library, but the Master Plan does not exist in the Master Plan library.
The FETCH phase is not completed.
Corrective Action: Create the Master Plan, or correct the name of the Master Plan or library.
Explanation: No jobs in this Scheduling Table are scheduled to be run today, according to their scheduling definitions. Therefore, there are no parameters in this plan that require prompting.
The Daily Scheduling Table is not created.
Corrective Action: Check whether or not jobs from this plan should have been fetched today.
Explanation: This informative message indicates that the facility is allocating a new Daily library. The first time, on a given day, that a user tries to perform a FETCH, the library against which the FETCH is performed is allocated as the Daily library for that day.
Corrective Action: No action is required.
Explanation: A Daily Plan with the same name was already fetched. Each Daily Plan must have a unique name in the Daily library. If a plan with the same name already exists in the Daily library, override the existing plan, or use a suffix to create a new plan.
The FETCH is not performed.
Corrective Action: Specify YES to override the plan or use a suffix to create a new Daily Plan.
Explanation: The facility cannot find the plan in the library. The plan should have been created earlier.
Corrective Action: Check to see if there is a physical problem with the library.
Explanation: The plan is probably in use by another user. A plan can be updated by only one user at a time. A second user trying to update the same plan receives this message.
The plan is not displayed.
Corrective Action: Try again later.
Explanation: The user set PROMPT IND to Y, but the MESSAGE field is empty.
Setting PROMPT IND to Y means that the user will be prompted for a value for this parameter during the EXEC phase. In such a case, a prompting message must be displayed at the time the EXEC is performed.
The parameter is not accepted.
Corrective Action: Enter the text of the message, or set PROMPT IND to N.
Explanation: PROMPT IND was set to N, but the DEFAULT field is empty. Setting PROMPT IND to N assigns the value of this parameter in the Master Plan, and prevents it from being modified during the EXEC phase. In this case, the value must be supplied.
Corrective Action: Enter the default value, or set PROMPT IND to Y.
Explanation: Invalid format of the OCCUR NO. field. It should be two digits.
Corrective Action: Enter the value in correct format.
Explanation: In the Control-M Quick Schedule Definition screen, the name of the scheduling table to be created was not entered. It is a required entry.
A prompt asks for a valid table name.
Corrective Action: Enter the name of the scheduling table to be created.
Explanation: In the Control-M Quick Schedule Definition screen, the skeleton scheduling table tableName was not found in library lib.
A prompt requests the name of a skeleton scheduling table.
Corrective Action: Enter the name of a skeleton scheduling table that exists in library lib.
Explanation: In the Control-M Quick Schedule Definition screen, the group name was not entered.
If the format of the inter-job prerequisite conditions is GROUP-FROMJOB-SUFFIX, the group name is a required entry.
A prompt asks for a group name.
Corrective Action: Enter a group name of 1 to 20 non-blank characters.
Explanation: In the Control-M Quick Schedule Definition screen, the name of the skeleton scheduling table was not entered.
A prompt asks for the name of a skeleton scheduling table.
Corrective Action: Enter the name of the skeleton scheduling table to be used.
Explanation: In the Control-M Quick Schedule Definition screen, a prerequisite condition prefix was not entered. If the format of the inter-job prerequisite conditions is PREFIX-FROMJOB-TOJOB, the prefix is a required entry.
A prompt asks for a prefix.
Corrective Action: Enter a one or two character prefix.
Explanation: In the Control-M Quick Schedule Definition screen, a prerequisite condition suffix was not entered. If the format of the inter-job prerequisite conditions is FROMJOB-TOJOB-SUFFIX or GROUP-FROMJOB-SUFFIX, the suffix is a required entry.
A prompt requests a suffix.
Corrective Action: Enter the suffix. For FROMJOB-TOJOB-SUFFIX, the suffix is limited to one or two characters.
Explanation: In the Control-M Quick Schedule Definition screen, either none of the options for prerequisite condition format was marked Y, or more than one was marked Y. Only one format for the inter-job prerequisite conditions may be used to create a scheduling table.
A prompt requests entry of valid Y and N values for the three prerequisite condition format options.
Corrective Action: Ensure that one of the three choices is marked Y, and the other two choices are marked N.
Explanation: In the Control-M Quick Schedule Definition Jobs List screen, an entry in the DEPENDS ON field refers to a member that was not found in the table. Entries in the DEPENDS ON field must refer only to members in the table being created. One of the following was found:
A prompt requests correction of the DEPENDS ON field.
Corrective Action: Correct the invalid reference, as follows:
Explanation: In the Control-M Quick Schedule Definition Jobs List screen, more than one member has Option C or Option M selected.
Each time the Enter key is pressed, only one member may be moved or copied.
A prompt requests removal of one of the duplicate M or C options.
Corrective Action: Enter the M or C option on one line only.
Explanation: In the Control-M Quick Schedule Definition Jobs List screen, more than one member has Option A or Option B selected. The target of a move or copy line operation must be a specific line, indicated with the A or B option.
A prompt requests removal of one of the duplicate A or B options.
Corrective Action: Enter option A or B on one line only.
Explanation: In the Control-M Quick Schedule Definition Job List screen, a Move or Copy operation was requested, but no line was marked with either an A (after) or B (before).
A prompt requests entry of option A or B.
Corrective Action: Enter either the A or B option to define where the data is to be moved or copied, or remove the Move or Copy option.
Explanation: In the Control-M Quick Schedule Definition Jobs List screen, a Before or After was indicated, but no Move or Copy operation was requested.
A prompt asks for specification of an M or C option.
Corrective Action: Either enter a Move or Copy option, or remove the Before or After option.
Explanation: In the Control-M Quick Schedule Definition Jobs List screen, the Description for a member was not entered.
A prompt requests a description.
Corrective Action: Enter the member description.
Explanation: In the Control-M Quick Schedule Definition Job List screen, a member refers to itself. A reference was found that is either a job name that is identical to the member name, or a line number that is the same as the line number the member is on.
A prompt requests correction of the DEPENDS ON field.
Corrective Action: Correct the reference in error.
Explanation: The DEPENDS ON field in the Quick Schedule Definition Job List screen contains data in an invalid format, such as an embedded blank in a member name, or two commas with no data between them. The DEPENDS ON field may consist of any number of subfields separated by commas. Each subfield may be either:
If a prerequisite condition name is used, it must be the last subfield in the DEPENDS ON area. Only one condition name is allowed per line.
A prompt requests correction of the DEPENDS ON field.
Corrective Action: Correct the invalid data in the DEPENDS ON field.
Explanation: In the Control-M Quick Schedule Definition Job List screen, a member name appears more than once. A member name in a schedule produced by the Quick Schedule Definition must appear only once in the table.
A prompt requests removal of the duplicate members.
Corrective Action: Delete the duplicate entry.
Explanation: In the Control-M Quick Schedule Definition Job List screen, option D (Delete) was entered for a member that is a prerequisite to another member. This line cannot be deleted, since this would cause the member that depends on it to refer to a member that does not exist.
A prompt requests removal of the reference to the line marked for deletion.
Corrective Action: Delete the references to the member to be deleted. Then the deletion will be accepted.
Explanation: This information message indicates that scheduling table tableName has been built successfully and placed in library lib.
Corrective Action: No action is required.
Explanation: In the Control-M Quick Schedule Definition Exit Option Window, the user entered N for the Save or Create option.
The scheduling table is not updated.
Corrective Action: No action is required.
Explanation: This information message indicates that a scheduling table has been successfully built and has replaced table tableName in library lib.
Corrective Action: No action is required.
Explanation: In the Control-M Quick Schedule Definition screen, the skeleton scheduling table specified is not a valid skeleton scheduling table, or it contains definitions for more than one job. The skeleton scheduling table must be a valid Control-M scheduling table, and must contain a definition for one and only one job.
The user is prompted to enter the name of a valid scheduling table.
Corrective Action: Either modify the skeleton scheduling table using the Control-M Online Schedule Definition - screen 2, and retry the request to use this skeleton scheduling table, or enter the name of a valid skeleton scheduling table.
Explanation: In the End User Job Order Interface (CLIST CTMJBINT), a value other than S (select this job for submission) was specified in the OPTION field. Only S may be specified in the OPTION field, other than leaving the OPTION field blank.
Corrective Action: Ensure that the OPTION field for each job in the list either contains S or is blank, and then press Enter.
Explanation: An invalid date was specified in the End User Job Order Interface (CLIST CTMJBINT). The format shown in the message text depends on the standard in use at the site. The specified date was not valid according to this standard.
Corrective Action: Specify a date that is valid according to the indicated site standard, and press Enter.
Explanation: An internal error occurred while allocating the library for the End User Job Order Interface (CLIST CTMJBINT). The system was unable to allocate a required library. Possible causes are:
The CLIST is terminated without any further processing.
Corrective Action: Notify your INCONTROL administrator who, depending on the cause of the error, should perform the appropriate action, as follows:
Explanation: An internal error occurred while opening the library for the End User Job Order Interface (CLIST CTMJBINT). The system cannot open the library indicated in the USRLIB parameter in CLIST CTMJBINT.
The CLIST is terminated without any further processing.
Corrective Action: Notify your IOA administrator. The IOA administrator should determine why the system was not able to open the library. For example, ensure that the library exists, and resides on the volume to which the MVS catalog points.
Explanation: The user attempted to use the Control-M End User Job Order Interface (CLIST CTMJBINT), but the End User Job Order Interface has not been implemented at your site.
The CLIST is terminated without any further processing.
Corrective Action: Request that the INCONTROL administrator implement the End User Job Order Interface at your site. Implementation instructions are in the Control-M chapter of the INCONTROL for z/OS Administrator Guide.
Explanation: A user (usr) attempted to use the Control-M End User Job Order Interface (CLIST CTMJBINT), but no job list is defined for that user.
The CLIST is terminated without any further processing.
Corrective Action: Notify your IOA administrator that you are unable to use the End User Job Order Interface. Implementation instructions for the End User Job Order Interface are provided in the chapter that describes JCL and the AutoEdit facility in the Control-M for z/OS User Guide.
Explanation: The user requested the M6 Control-M ISPF utility or executed the CLIST CTMJOBRQ command. However, the tableName Control-M Job Scheduling table contains job names that are duplicates.
A list of the job names in the tableName Job Scheduling table is displayed, but this list contains only one entry for each set of duplicated job names.
Corrective Action: Ask your INCONTROL administrator to delete or rename the jobs in the tableName scheduling table that have names that duplicate other job names.
Parent Topic |