|
|
|
|
|
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: A syntax error was found on the previously displayed line.
The CTMJOB program ends with errors.
Corrective Action: Correct the erroneous keyword or data in the order request.
Explanation: This information message is a standard message when a request order is being processed.
Corrective Action: No action is required.
Explanation: A keyword was given twice in the same order request. The order request which was listed prior to this message contains the same keyword twice, regardless of whether or not the values are identical.
The CTMJOB program ends with errors.
Corrective Action: Delete the duplicate keyword in the order request.
Explanation: The table member either exceeds the maximum allowed size, or contains invalid data.
The CTMJOB program ends with errors.
Corrective Action: Check that the table member contains less than 32,000 records of valid scheduling definitions.
Explanation: Reading the specified table member failed.
The order request could not be done either because the library did not exist, or could not be allocated, or the table member was not found.
The CTMJOB program ends with errors.
Corrective Action: Check that the order request is given to an existing 80-bytes record length library, and the member can be accessed. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.
Explanation: The date specified in the order request is not a valid date.
The CTMJOB program ends with errors.
Corrective Action: Check that the specified date is specified correctly according to your installation standards.
Explanation: None of the jobs in the table satisfy both selection criteria of “JOB” and “GROUP”, specified in the ORDER request.
Corrective Action: Specify other values to order the jobs.
Explanation: The specified parameter was not given in the order request.
Some parameters are obligatory in each order request. Failing to specify one of them results in this message being issued.
The CTMJOB program ends with errors.
Corrective Action: Supply the missing parameter.
Explanation: Two keywords which are mutually exclusive where given in the same order request.
Certain keywords, such as DSNAME and DDNAME, cannot appear together on the same order request.
The CTMJOB program ends with errors.
Corrective Action: Specify one of the keywords.
Explanation: The DASTAT DD statement is missing from the file allocation of the job step.
This warning message is issued by the CTMJOB program.
The Automatic Tape Adjustment facility is skipped. Jobs are ordered, but required resource quantities are not computed for these jobs.
Corrective Action: Add a DASTAT DD statement for future runs.
Explanation: This warning message indicates that the Automatic Tape facility cannot adjust resources for jobs currently being processed.
This is a summary message. It is preceded by a message that describes the reason for the error.
The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the quantity of required resources.
Corrective Action: View the error message that precedes this message and correct the problem described there.
Explanation: An invalid definition was found in the UNITDEF parameter member.
The UNITDEF parameter member associates logical names to physical resources.
In this message, lineNum is the number of the line in the UNITDEF parameter member where the error occurred.
Resource definition example in the UNITDEF file:
CARTRIDGE=(0480-0483,0440-0445,0300-031F,0552-0553,0556-0557),DESC=3490 RANGE
The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the required amount of resources.
Corrective Action: Correct the error at the specified line. View the description in the UNITDEF file supplied during the installation.
Explanation: The UNITDEF DD statement is missing.
This warning message is issued by the CTMJOB program.
The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the required amount of resources.
Corrective Action: Add a UNITDEF DD statement to the JCL stream.
Explanation: The Control-M Daily Subsystem stopped due to insufficient memory.
The Daily job stops execution.
Corrective Action: Increase the region size defined in the Daily job and rerun the job.
Explanation: The requirement that a prerequisite condition exist (for a job which is part of a group) was not deleted.
The “adjust conditions in a group” feature failed to delete the requirement that a prerequisite condition exist for one of the jobs of a group.
The job is ordered with the prerequisite condition requirement intact.
Corrective Action: Determine if the condition prevents the job from running. If so, add the required condition manually in screen 4 or erase the requirement for the condition from the job in zoom screen 3.Z.
Explanation: The requirement for prerequisite conditions for a job which is part of a group were not deleted.
This message accompanies message JOBL48W.
The job is ordered prerequisite condition requirement intact.
Corrective Action: Determine if the condition prevents the job from running. If so, add the required condition manually in screen 4 or erase the requirement for the condition from the job in zoom screen 3.Z.
Explanation: The scheduling library in which the table mentioned in JOBL40E resides.
This message accompanies message JOBL40E.
Corrective Action: Specify the correct values to order the jobs.
Explanation: A request to dynamically insert a job into a Group Entity that is already on the Active Jobs file has failed. The reason for the failure is detailed in an accompanying message.
Dynamic ordering of the job was not performed.
Corrective Action: Check the accompanying message to determine the cause of the failure, and respond accordingly.
Explanation: A request to dynamically insert a job into a group failed because the rba, which points to the Group Entity in the Active Jobs file, was not pointing to a Group Entity.
Dynamic ordering of the job is not performed.
Corrective Action: Find the correct Group Entity rba, and change the order request accordingly.
Explanation: A request to dynamically insert a job as part of a group failed, because the job is not a member of the group. Users can dynamically insert jobs only if the jobs are members of the group definition.
The job is not ordered.
Corrective Action: Correct the order request appropriately.
Explanation: A request to dynamically insert a job into a group in the AJF failed, because the group already contains the maximum number of jobs allowable in a group.
The job is not ordered.
Corrective Action: No action is required.
Explanation: A request to dynamically insert a job into a group in the Active Jobs file failed because a job with same name already exists in the group, and the order request did not specify the DUP (duplicate) parameter.
The job is not ordered.
Check if the job should still be inserted in the group. If so, dynamically insert a duplicate job into the group using the DUP parameter in the ORDER statement.
Corrective Action: No action is required.
Explanation: The table specified is not a SMART table.
Corrective Action: No action is required.
Explanation: NEWDAY processing occurred during the ordering of a Smart Table. Some of the jobs in the Smart Table were ordered before NEWDAY started, but after NEWDAY started the ordering process was suspended. The NEWDAY process then deleted the jobs that were already ordered, as indicated in the NEWDAY SYSOUT.
After NEWDAY has ended, CTMJOB/CTMAPI resumes the job ordering process for this Smart Table. It detects that the previously ordered jobs are no longer in the Active Jobs File (AJF). These jobs are now Held (as they are ‘orphans’ that are no longer attached to their Smart Table) and the JOBL56I message is issued. The complete Smart Table is now (correctly) ordered again.
Corrective Action: Delete the ‘orphan’ jobs from the Actives Jobs File.
Explanation: There is a syntax error in the SELECT or IGNORE RBC statement. The ORDER statement (to which this SELECT or IGNORE RBC command refers) is ignored. The daily job resumes processing with the next ORDER statement.
Corrective Action: Use one of the following syntaxes:
Explanation: Job has been ordered successfully.
Corrective Action: No action is required.
Explanation: Job has not been ordered.
Corrective Action:Check for additional messages that explain why the job was not ordered successfully.
Explanation: SMART Entity has been ordered successfully.
Corrective Action: No action is required.
Explanation: SMART Entity has not been ordered.
Corrective Action:Check for additional messages that explain why the SMART Entity was not ordered successfully.
Explanation: Ordering of job has been bypassed because the SMART Table has not been ordered.
Corrective Action: Refer to previous message(s) that describe why SMART Table has not been ordered.
Explanation: Performing ORDER request, but no JOB was eligible to be ordered because the scheduling criteria were not satisfied.
Corrective Action: No action is required.
Explanation: Performing ORDER request of a SMART Table. The order request failed because of an error in the SMART Table.
Corrective Action: Refer to previous message(s) that describes the error.
Explanation: Performing ORDER request of a SMART Table. The order request failed because of an error return code from either the Control-M user exit CTMX001 or the security module CTMSE01.
Corrective Action: Refer to previous message(s) that describes the error.
Explanation: This information message indicates that the CTMJOB program has started a UNIQUE FLOW (UFLOW) order request.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTMJOB program has successfully ordered a UNIQUE FLOW (UFLOW) request.
The uid is the three characters that the CTMJOB adds to all IN and OUT conditions that are part of the UNIQUE FLOW.
Corrective Action: No action is required.
Explanation: This warning message indicates that the CTMJOB program did not find any valid conditions that satisfy the UNIQUE FLOW (UFLOW) rule.
For a description of UNIQUE FLOW, refer to the Control-M for z/OS User Guide.
The CTMJOB program will perform the ORDER request as a regular order.
Corrective Action: No action is required.
Explanation: This error message indicates that the CTMJOB program succeeded in backing out jobs that were ordered as part of the UNIQUE FLOW (UFLOW).
Message JOB511I was issued for the JOBs that were ordered.
The jobs will not be placed in the AJF.
If order_number equals “000” it means that the error occurred before any jobs were ordered as part of the UNIQUE FLOW (UFLOW).
Corrective Action: Correct the error as described in the previous message and reorder the table.
Explanation: This error message indicates that the CTMJOB program succeeded in backing out jobs that were ordered as part of the UNIQUE FLOW (UFLOW).
Message JOB511I was issued for the JOBs that were ordered.
The jobs will not be placed in the AJF.
If order_number equals “000” it means that the error occurred before any jobs were ordered as part of the UNIQUE FLOW (UFLOW).
Corrective Action: Correct the error as described in the previous message and reorder the table.
Explanation: This error message indicates that the CTMJOB program found an IN or OUT condition name whose length is greater than 36 characters. When the UNIQUE FLOW process adds a prefix of three characters to the condition name, the name will become invalid.
The UNIQUE FLOW process will fail and all jobs will be backed out.
Corrective Action: Shorten the condition name and reorder the table.
Explanation: This error message indicates that the CTMJOB program failed to add the JOB to the AJF because the UNIQUE FLOW process increased the size of the IN or OUT condition name.
The UNIQUE FLOW process will fail and all jobs will be backed out.
Corrective Action: Compress the AJF or increase the AJF file size. Refer to the INCONTROL for z/OS Administrator Guide.
Explanation: This error message indicates that the CTMJOB program identified that the UNIQUE FLOW is filtered by "JOB=". UNIQUE FLOW is only for jobs in the table whose scheduling criteria are satisfied.
The UNIQUE FLOW process will not continue.
Corrective Action: Remove the JOB or the UFLOW from the ORDER request and reorder the table.
Explanation: CTMJOB was performing an ORDER request with a Unique Flow ID (UFLOW), but the process failed with an internal error, indicated by RC=return_code.
Corrective Action: Perform the ORDER request again. If the problem persists, do the following:
//DATRACE DD SYSOUT=*
//DATRCIN DD *
TRACE=128
Parent Topic |