|
|
|
|
|
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: This information message indicates that as a result of an ADD or DELETE option, the resourceName control resource of Control-type was either deleted from the Control-M Resources file, or added to the Control-M Resources file.
Corrective Action: No action is required.
Explanation: The control resource marked for deletion (D option) was already deleted from the Control-M Resources file. While you were working on the screen, another user or one of the IOA monitors deleted the control resource from the Control-M Resources file.
Corrective Action: No action is required.
Explanation: An invalid quantity specified in the window. Quantity must be a 4-digit number.
Corrective Action: Correct the quantity field.
Explanation: The resourceName quantitative resource is in use by an active job under Control-M. Therefore, the resource cannot be deleted.
The resource is not deleted.
Corrective Action: Wait until the job finishes executing, and try again.
Explanation: Highlighted, unrollable message.
The Control-M Resources file is full.
The resourceName quantitative resource is not added to the file.
Corrective Action: Consult your system programmer about the possibility of increasing the capacity of the Control-M Resources file.
Explanation: A quantitative resource (resourceName) being added using the ADD command already exists in the file.
The addition request is ignored.
Corrective Action: No action is required.
Explanation: The resourceName quantitative resource that was marked for deletion (the D option) was already deleted from the Control-M Resources file. While you were working on the screen, another Control-M user deleted the quantitative resource from the Control-M Resources file.
Corrective Action: Check who did it and why (by entering the IOA Log screen).
Explanation: As a result of an ADD or DELETE option, the resourceName quantitative resource has been deleted from the Control-M Resources file, or added to the Control-M Resources file.
Corrective Action: No action is required.
Explanation: A change request was issued for a condition or a control resource. The change option can be specified only in order to change the quantity of a quantitative resource.
The change request is ignored.
Corrective Action: No action is required.
Explanation: Invalid sign of quantity change in the CHANGE window. The quantity sign must be "-" for subtracting the amount from the maximum available quantity, "+" for adding the amount to the maximum available quantity, or blank for setting a new quantity.
Corrective Action: Supply the correct sign.
Explanation: This message is issued when the IOACND utility fails to delete control resource res from the Control-M Resources file. The specified control exists in the Control-M Resources file but the IOACND utility cannot delete it for one of the following reasons:
Corrective Action: No action is required.
Explanation: The Control-M Active Environment screen cannot use indexing because the user region size is too small. This might cause the screen response time to slow significantly.
Corrective Action: Enlarge the user region size. If the size of the Active Jobs file and/or the History Active Jobs file have increased recently, make sure that all user region sizes are enlarged accordingly.
Explanation: The quantity resulting from the CHANGE operation is either negative, or more than 9999.
The change request is ignored.
Corrective Action: Try again with a correct value.
Explanation: Internal error. Invalid return code from the CTMURS IOA internal utility.
Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.
Explanation: As a result of a change command, the quantity of the resourceName resource changed from quant by snnnn (s is the sign).
Corrective Action: No action is required.
Explanation: IOACND was asked to delete the res resource, but the resource was not found in the RES file.
The resource is not deleted.
Corrective Action: Check if the correct resource was specified, and if it was not, specify the correct resource.
Explanation: This information message indicates that the New Day procedure started deleting archived SYSDATA sysouts.
Corrective Action: No action is required.
Explanation: An internal error was detected in the modName module.
The Application Server becomes unstable.
Corrective Action: Stop and restart IOAGATE and the Application Server CTOGATE. If the error persists, contact BMC Customer Support.
Explanation: This information message indicates that the New Day procedure finished deleting archived SYSDATA sysouts.
Corrective Action: No action is required.
Explanation: Some Archived Sysout Data Sets were not deleted by the Control-M New Day procedure or during compression of the Control-M Active Jobs file.
This message follows other messages that explain the nature of the error for each archived sysout data set.
The Control-M New Day procedure or CTMCOP utility continues processing.
Corrective Action: See the messages that precede this message for the reasons for deletion failure.
Explanation: The name of Archived Sysout Data Set does not follow the Control-M/Restart naming conventions for this type of data set. This message is issued either by the Control-M New Day procedure, or by the CTMCOP utility, during compress of the Control-M Active Jobs file.
Corrective Action: Contact BMC Customer Support for assistance.
Explanation: The number of Archived Sysout Data Sets scheduled for deletion exceeds the permitted number. This message is issued either by the Control-M New Day procedure or by the CTMCOP utility during compress of the Control-M Active Jobs file. The permitted value is one fifth of the Active Jobs file size.
Deletion of Archived Sysout Data Sets will be resumed during the next run of the Control-M New Day procedure or the CTMCOP utility.
Corrective Action: No action is required.
Explanation: An Sysplex query error was detected in the modName module.
The Application Server becomes unstable.
Corrective Action: Stop and restart IOAGATE and the Application Server CTOGATE. If the error persists, contact BMC Customer Support.
Explanation: When executing the IOANOTE utility, no message was specified in the PARM of the JCL EXEC statement or no PARM was specified on the JCL EXEC statement.
The utility terminates with a return code of 4.
Corrective Action: Add a message in the PARM of the EXEC JCL statement.
Explanation: The CTMRELRS utility (the CTMRLR program) has been activated from a started task or from a TSO session. The CTMRELRS utility may be activated only from batch jobs which are submitted by the Control-M monitor.
The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.
Corrective Action: For usage restriction of the utility, see the INCONTROL for z/OS Utilities Guide.
Explanation: The CTMRELRS utility (the CTMRLR program) was activated from a job that was not submitted by the Control-M monitor. Only a job that is submitted by the Control-M monitor can release its own quantitative resources.
The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.
Corrective Action: For more information on usage restriction of the utility, see the INCONTROL for z/OS Utilities Guide.
Explanation: This information message indicates that the quant quantity of the resourceName quantitative resource has been released for general use, or has been changed by the CTMRLRES utility.
The specified action is either RELEASED or CHANGED.
Corrective Action: No action is required.
Explanation: Invalid function supplied as a parameter to the CTMRELRS utility.
The CTMRELRS utility stops executing with a condition code of 04. The resource is not released or changed.
Corrective Action: Specify either the RELEASE or CHANGE function for the utility.
Explanation: The quantity requested to be released by the job using the CTMRELRS utility is greater than the quantity of the resource currently allocated to the job.
The utility stops executing with a condition code of 04. The resource is not released.
Corrective Action: Correct the parameters of the utility.
Explanation: The quantitative resource to be released by the CTMRELRS utility is not allocated at all to the job that activates the utility.
A job can only release resources which are allocated to it.
The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.
Corrective Action: For more information on usage restriction of the utility, see the INCONTROL for z/OS Utilities Guide.
Explanation: Open of control statements file failed (the DARELIN DD statement in the CTMRELRS utility).
Possible causes are:
Program execution stops with a condition code of 08.
Corrective Action: Correct the JCL for the job and run it again.
Explanation: The quantity requested to be changed using the CTMRELRS utility is greater than the quantity of the resource currently allocated to the job. The CTMRELRS utility can only be used to decrease the quantity of the resource allocated to a job.
The utility stops executing with a condition code of 4. The resource amount allocated to the job is not changed.
Corrective Action: Correct the parameters of the job.
Explanation: Open of control statements file failed (the DACNDIN DD statement in the IOACND utility or program).
It may be due to one of the following:
Program execution stops with a condition code of 08.
Corrective Action: Correct the JCL for the job or the CLIST, and run it again.
Explanation: The quantResource Quantitative resource does not exist. The missing resource was named as input to the CTMRLR program.
Corrective Action: Ensure that the name of the resource specified as input to the program matches the resource name in the job scheduling definition.
Explanation: Severe syntax error in the parameters to the IOACND or CTMRELRS utility.
The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.
Corrective Action: Correct the parameters and reactivate utility.
Explanation: Invalid date format in ADD COND or DELETE COND statement (the IOACND utility or program). The date format should be mmdd or ddmm, depending on the site standard.
The utility stops executing with a condition code of 12. The condition is not added or deleted.
Corrective Action: Correct the parameters and reactivate utility.
Explanation: Internal error in the IOACND and CTMRELRS utilities.
The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.
Corrective Action: Call your IOA administrator for assistance.
Explanation: Open of messages file failed in the IOACND and CTMRELRS utilities. Possible causes are:
The utility stops executing with a condition code of 12.
Corrective Action: Correct the JCL for the job or the CLIST and run it again.
Explanation: An invalid function has been passed to the IOACND utility.
Valid functions are ADD, DELETE or CHECK.
The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.
Corrective Action: Correct the parameters syntax and reactivate.
Explanation: An attempt was made to add or delete a Quantitative Resource or Control Resource using the IOACND utility. These are privileged operations for Control-M or Control-D support personnel.
The utility stops executing with a condition code of 12.
Corrective Action: Correct the parameters syntax and reactivate.
Explanation: An attempt to load the CTMRS0 program failed.
Corrective Action: Check that the name of the load library is correct. If that does not solve the problem, contact your INCONTROL Administrator.
Explanation: The IOACND utility failed in one of the initialization steps of the Control-M Resources file. Either the file accessed is not a valid Resources file, or the Resources file is being formatted.
The utility stops with a return code of 16.
Corrective Action: Ensure that the DARESF DD statement points to a valid resource file, and that the file is not corrupted.
Explanation: You are trying to save a table that does not exist.
The table is not saved.
Corrective Action: To save a new production parameters table, erase the Y in the SAVE field, enter Y in the CREATE field, and press Enter.
Explanation: The CKPSIZE parameter in CTMPARM is not the same as when the Active Jobs file (AJF) referenced by the DACKPT DD statement was formatted. A change was made in the CKPSIZE parameter in CTMPARM after the Active Jobs file was formatted.
The job step or request terminates without performing the requested function.
Corrective Action: Adjust the CKPSIZE parameter according to the real size of the AJF, or reformat the AJF.
Explanation: While looking at a certain part of the IOA Log file, an IOA component updated that part of the Log. When the IOA Log file is full, a wraparound is performed and new records are written starting at the top of the Log. If you are at the top of the Log, a wraparound might cause some messages to be lost.
The Online facility issues a warning to inform of the possible loss of messages.
Corrective Action: No action is required.
Explanation: This information message is generated by the IOACND utility when optional wish WI2232 is applied.
The IOACND utility translates a condition name from the PARM= parameter in the EXEC card of this utility to upper case.
Corrective Action: No action is required.
Explanation: Invalid value specified in the field. The cursor points to the field that contains the invalid value.
Corrective Action: Enter either Y for yes, or N for no.
Explanation: No MESSAGE TYPE field has been marked for selection (Y). At least one of the MESSAGE TYPES must be marked as Y.
Corrective Action: Enter Y for at least one MESSAGE TYPE.
Explanation: A job record with an invalid format was detected during the New Day procedure. If the User Daily is run on a different computer without proper ENQ distribution software, such as GRS or MIM, a faulty record may be created in the Active Jobs file.
The faulty record is erased from the Active Jobs file.
Corrective Action: To avoid this problem, run all User Daily procedures on the CPU in which the Control-M monitor is running.
Explanation: The field contains leading blanks or two strings separated by blanks. Leading or embedded blanks are not allowed in this field.
The cursor points to the first blank.
Corrective Action: Correct the field contents.
Explanation: No URGENCY field was marked for selection (Y). At least one of the URGENCY fields must be marked Y.
Corrective Action: Enter Y for at least one URGENCY field.
Explanation: No TASK TYPE field has been marked for selection (Y). At least one of the TASK TYPEs must be marked Y.
Corrective Action: Enter Y for at least one TASK TYPE.
Explanation: After an operator DISPLAY command to one of the Online monitors, this header message for message CTM646I is issued.
Corrective Action: No action is required.
Explanation: After an operator DISPLAY command to one of the Online monitors, this message is displayed for each active user.
The variables in this message are:
Corrective Action: No action is required.
Explanation: Load for the requested pgm module during user sign-on to the Online facility failed. The user main program as specified by Online monitor sign-on exit or by default (CTMXMAN, CTMXMAND, CTDXMAN, or CTDXMANU) cannot be found in the Online monitor STEPLIB libraries.
Sign-on to the specified IOA Online monitor is terminated.
Corrective Action: Contact your INCONTROL administrator to find out why the program is missing. If the problem is not resolved, contact BMC Customer Support for assistance.
Explanation: The maximum number of characters allowed for an RBC name is 20 characters, including the exclamation mark (!) prefix used to specify an Exclude RBC. Since the name of this RBC already consists of 20 characters, an exclamation mark (!) cannot be added as a prefix to this RBC name, in the event it is required for an Exclude RBC.
Corrective Action: Rename the RBC with 19 or less characters.
Explanation: Highlighted, unrollable message.
A severe error has occurred. The IOA Online monitor is shutting down.
Detailed information on this error is available in the messages which were previously displayed on the operator console.
The monName IOA Online monitor is shutting down.
Corrective Action: Check the system log for additional messages.
Explanation: An invalid parameter was passed to the monName IOA Online monitor by an operator modify command (F). A list of valid modify parameters will appear on the operator console following this message.
The modify command is rejected.
Corrective Action: Enter a correct modify parameter.
Explanation: Open of Control-M Active Jobs file failed (the DACKPT DD statement). Possible causes are:
Corrective Action: Check the contents of the system log for additional messages which may clarify the picture, or logon again. If the sense code appears in the message, supply it to the INCONTROL administrator when requesting assistance.
Explanation: I/O error while reading Control-M Active Jobs file. Possible causes are:
Corrective Action: Check the contents of the system log for additional messages which may clarify the picture, or logon again. If this does not solve the problem, notify the INCONTROL administrator informing him of the sense code and RBA.
Explanation: Internal error. Invalid request to the CTMUCK Control-M internal program.
The function requested is not performed.
Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support for assistance.
Explanation: Result of DELETE, CHANGE or UNDELETE commands.
For DELETE or CHANGE commands, the taskName task of the original scheduling date (odate) is not in the HELD state and therefore cannot be deleted or changed.
For an UNDELETE command, the task of the original scheduling date was not deleted, therefore cannot be undeleted.
The DELETE, CHANGE or UNDELETE request is ignored.
Corrective Action: In the case of DELETE or CHANGE commands, hold the task using the H option. Wait until the REQUESTED HELD status is changed to HELD, and then you can perform the change or delete.
Explanation: The taskName task with the odate original date already has the requested status.
The user request is ignored.
Corrective Action: No action is required.
Explanation: Another user is currently updating the file. The file is currently in use by another user or by the Control-M monitor.
The requested action is not performed.
Corrective Action: Try again later.
Explanation: Result of HOLD (H), RERUN (R), FREE (F), AESIM (%) (AutoEdit simulation), or CHANGE request for the taskName task of the odate original scheduling date whose status has already been changed. While you were looking at the screen, another user or Control-M monitor changed the status of the task, or the contents of the production parameters.
The requested action is ignored.
Corrective Action: Check the task status and act accordingly.
Explanation: Cannot do more actions on the taskName task of the odate original scheduling date. The maximum number of requests for action has been exceeded. Control-M monitor must accept the requests before another action can be performed.
The user request is ignored.
Corrective Action: If the Control-M monitor is up, try again. If it is down, it should be brought up again.
Explanation: The CTMUCK Control-M internal utility has issued an unexpected return code.
The user request is ignored.
Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.
Explanation: This information message indicates the specified action was performed by the taskName task to the grpname group on the odate date.
When this message is produced as the result of an action in screen 2, the date is the current Control-M working date in YYMMDD format.
Corrective Action: No action is required.
Explanation: This information message indicates that the action action requested by the userId user was performed by the taskName task on the odate date.
This message is issued to the log only.
Corrective Action: No action is required.
Explanation: The selected step has the same name as the step with the number num. A From, To, or Only RESTART was specified in the Control-M/Restart Step List window for a step with a name that is not unique in the job.
The cursor is placed on the line in which the non-unique step was selected.
Corrective Action: Clear the entry and choose another step.
Explanation: The command that was requested, or the function key that was pressed, is not supported in this screen or this window.
The request is ignored.
Corrective Action: No action is required.
Explanation: The Step List display requested under Screen 3.R (the Restart window) cannot be built, either because the job has no archived sysout, or because the existing archived sysout contains no steps from which a step list can be built. To build a step list, a meaningful archived sysout must exist.
The step list is not displayed.
Corrective Action: Select FROM and TO steps manually.
Explanation: The History command was entered in the Control-M Active Environment (Job Status) screen. However, the DAHIST file is not allocated to the user or could not be accessed.
This message is also generated if Control-M/Restart is not installed.
The command is ignored.
Corrective Action: Make sure the DAHIST DD statement correctly references the History Jobs file.
Explanation: Option G (Group) was requested in the Control-M Active Environment (Job Status) screen for a task that is not part of a Group scheduling table. Option G can only be specified for a Group entity (GRP) or job (JOB) that is part of a Group scheduling table.
The request is ignored.
Corrective Action: Request an option that is valid for the particular line entry in the screen.
Explanation: Invalid value specified in the field. The cursor points to the field that contains the invalid value.
Corrective Action: Select Y for yes, or N for no.
Explanation: At least one task type must be Y.
Corrective Action: Mark at least one of the task types as Y.
Explanation: At least one message type must be Y. All of the Y/N options are marked N.
Corrective Action: Mark at least one of the message types as Y.
Explanation: At least one of the first two types of job status must be Y (both are marked NO).
Corrective Action: Mark at least one of the first two types of job status Y.
Explanation: Internal error.
The function requested is not performed.
Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support for assistance.
Explanation: The taskName task of the odate original scheduling date did not finish executing, therefore it cannot be rerun.
The rerun request is ignored.
Corrective Action: No action is required.
Explanation: Internal error. Invalid return code from the CTMTWHY Control-M internal program (Why screen).
Corrective Action: Have your system programmer contact BMC Customer Support for assistance.
Explanation: The WHY ("?") option is used to determine the reason that a task is waiting to be scheduled; it cannot be used unless the task is in the WAIT SCHEDULE state.
The user request is ignored.
Corrective Action: No action is required.
Explanation: Internal error. Invalid return code from the pgm Control-M internal program.
The CTMTSVY, CTMTWHY, or IOATOLV programs can return the following return codes:
rc |
Explanation |
|---|---|
20 |
Insufficient REGION allocated to online environment |
1008 |
First CLS entry is an inserted/deleted entry |
1012 |
No CTDBOX vectors were processed |
1016 |
Insufficient memory for CTDBOX vector |
1020 |
Maximum number GETMAINS for CTDBOX vector exceeded |
1024 |
VSAM record for first CLS entry not found |
1028 |
VSAM record for first CLS entry is not a primary record |
1032 |
All compressed data sets were deleted. May also indicate that the SYSOUT file was deleted manually, by a system utility or another program. |
1036 |
Internal error in page fix environment |
1040 |
Error in GETMAIN of work areas |
1044 |
Error while reading a ruler |
2000 |
Error in CTDBOX |
2004 |
End of data sets |
2016 |
Unrecognized request |
2020 |
Allocation error |
2024 |
Open error |
2028 |
Subsystem not up |
Corrective Action: When the program identified in the message is CTMTSVY or IOATOLV, try to solve the problem according to the return code. If you are unable to solve the problem, and for all other return codes, record the program name and return code, then contact BMC Customer Support.
Explanation: Result of the ZOOM (Z) command. Error in the contents of the Active Jobs file. Possible causes are:
Corrective Action: Call your system programmer for assistance. A dump of the file will be needed to solve the problem.
Explanation: The requested command or option (cmd) is not supported in the current display mode.
The command or option is ignored.
Corrective Action: Request a command or option that is valid in the current display mode.
Explanation: Due to an internal error, an abCode abend occurred in the imod module
Execution stops following the abend.
Corrective Action: Ask your system programmer to prepare the Control-M monitor full output and contact BMC Customer Support. If requested, issue the command DUMP ON, so that a dump is generated the next time this abend occurs.
Explanation: The cmd command was entered without mandatory parameters.
The command is ignored.
Corrective Action: Supply the required parameters and re-enter the command.
Explanation: This information message indicates that the string specified in a FIND command or the prefix specified in a LOCATE command was not found.
Corrective Action: No action is required.
Explanation: When the status of a group is Held, the status of all the jobs belonging to that group changes to GRP Held. Individual jobs with the status GRP Held cannot be freed. Only the group itself can be freed.
The status of the job remains unchanged.
Corrective Action: If required, you can use the F (Free) option to free the group. This will free all the jobs belonging to the group.
Explanation: Internal Control-M error while building the Zoom screen.
Corrective Action: Have your system programmer contact BMC Customer Support for assistance.
Explanation: A user tried to FREE or DELETE a task that is still in the REQUESTED CHANGE mode.
The request is ignored.
Corrective Action: Wait until the REQUESTED CHANGE status disappears and then try again.
Explanation: Additional data were added to the job on the Zoom screen and the message appears as a result of the SAVE command. When a job order is placed on the Active Jobs file a certain amount of space is reserved for possible future addition of data by the user. This message appears whenever this space is exhausted.
The new job data are not saved.
Corrective Action: Try to delete some data in the Zoom screen. If you are trying to add ON STEP statements, try to delete other ON STEP statements, for OUT conditions, delete unnecessary OUT statements, and the like. Deleting all SHOUT WHEN messages usually releases enough space.
If all the above fail, delete the job order and reissue it manually with the new data (using the CLIST CTMJOBRQ). If the problem persists, contact BMC Customer Support.
Explanation: A request to delete a task in process or to Force OK a Group task that is not in ENDED status could not be performed. Only a task that awaits scheduling or has ended can be deleted. Force OK is valid only for a Group Task that has ended (in other words, all its jobs have ended).
The requested action is not performed.
Corrective Action: Depending on the requested action, take the necessary steps and repeat the request if desired.
Explanation: An attempt was made to delete a task in Wait Schedule state, after the task, which is of critical path priority, already reserved the resources for execution. A critical path priority task reserves Control Resources and Quantitative Resources, to obtain all the runtime resources required for its execution. You cannot delete such a task as long as the resources are still reserved.
The request is ignored.
Corrective Action: To delete the task, do the following:
Explanation: Internal error. An unexpected return code was received from the CTMTVEW Control-M program (View screen).
Corrective Action: Have your system programmer contact BMC Customer Support for assistance.
Explanation: RESTART was set to N with either FROM stepname or TO stepname. FROM stepname and TO stepname describe how the job is restarted by Control-M/Restart. Therefore, they cannot be specified when RESTART is set to N.
Corrective Action: For restart processing set RESTART to Y. When rerun is needed without restart processing, erase the FROM step and the TO step fields.
Explanation: A CONFIRM (C), or RERUN (R) was issued for a job whose status was already changed. While you were looking at the screen, another user or the Control-M monitor changed the status of the job or the contents of the production parameters.
The requested action is ignored.
Corrective Action: Press Enter again, check the job status, and act accordingly.
Explanation: The restart decision was changed from pgmStepName1.procStepName1 to pgmStepName2.procStepName2 during rerunning (R) of the task or confirmation of the restart of the task (C). Restart determines in which steps Control-M/Restart tries to start and end a restarted job. The original restart decision was manually modified, and this message indicates the new restart decision.
If and when this task is restarted, the new restart decision will be used.
Corrective Action: No action is required.
Explanation: A request to confirm (C) the restart of a task that is not waiting for confirmation failed. Confirm is valid only for tasks which are in WAIT CONFIRMATION status.
Confirm is ignored.
Corrective Action: No action is required.
Explanation: The customer issued 3.Z (ZOOM) command for the job in HELD ENDED status, but Control-M did not completely finish the processing of the job. The last step of post-processing (the handling of SHOUTs and OUTPUT CONDITIONS) was not completed. In this situation, the SAVE command (under ZOOM) may prevent Control-M from executing DO COND and DO SHOUT actions. For this reason, 3.Z is forced to BROWSE mode, where change/save is not possible.
3.Z is forced to BROWSE mode.
Corrective Action: If the job should be changed (and BROWSE mode is not acceptable), the user should FREE the job, wait several seconds (to enable Control-M to finish processing of the job), then HOLD and ZOOM again.
Explanation: Edit JCL was performed through IOA Online option 3.J. The change was saved to the specified library and member.
Corrective Action: No action is required.
Explanation: The memName member that was requested is not in the library.
Possible causes are:
The system action depends on the cause, as follows:
Corrective Action: The appropriate response depends on the cause, as follows:
Explanation: The requested DSN is not a partitioned data set.
Possible causes are:
The system action depends on the cause, as follows:
Corrective Action: The appropriate response depends on the cause, as follows:
Explanation: The memName member that you are trying to create already exists in the specified library.
The memName member is not created.
Corrective Action: Correct the member name and try again.
Explanation: A problem has occurred during the reading of a record.
Corrective Action: Make sure you chose the correct library.
Explanation: The DSN is held exclusively by another user. Possible causes are:
The system action depends on the cause, as follows:
Corrective Action: Try again.
Explanation: Internal Control-M error while trying to read a member from a library.
Possible causes are:
The system action depends on the cause, as follows:
Corrective Action: Look for additional messages on IOA Log that may clarify the picture. If you can, correct the problem, and continue according to the CTM680 message. Under the Online facility, it may be helpful to log off and log on again.
In any case, prepare the Control-M monitor full output and contact BMC Customer Support. Note the function code (func), which will help the BMC support team resolve the problem.
Explanation: The requested DSN (dsn) is not in the catalog.
Possible causes are:
The system action depends on the cause, as follows:
Corrective Action: The appropriate response depends on the cause, as follows:
Explanation: Dynamic allocation for the requested DSN (dsn) failed. Possible causes are:
This can also happen when the Control-M Online facility is activated under the Control-M Online facility (nesting) and you are trying to access the same library in two screens.
The system action depends on the cause, as follows:
Corrective Action: Exit the Online facility and retry. If this happens under batch environment or in Control-M AutoEdit facility, prepare the Control-M monitor full output and contact BMC Customer Support for assistance.
Explanation: Internal IOA error while trying to read a member from a library. Possible causes are:
The system action depends on the cause, as follows:
Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support for assistance.
Explanation: An attempt to read a large member from the library failed.
The system action and appropriate user response depend on the circumstances at the time the message is issued, as follows:
In this case, job submission fails. Increase the REGION size or LOGON size, and try again.
Corrective Action: No action is required.
Explanation: The parameter list passed to IOAMEM must include the requested member name, which is missing.
The request to IOAMEM is terminated.
Corrective Action: Notify your INCONTROL administrator.
Explanation: IOAMEM received a request to allocate a DD name (ddName) that has already been allocated.
The request to IOAMEM is terminated.
Corrective Action: Notify your INCONTROL administrator.
Explanation: The open process of the dsn data set failed.
The request to IOAMEM is terminated.
Corrective Action: Notify your INCONTROL administrator.
Explanation: IOAMEM detected that the requested data set (dsn) does not exist on the volume pointed to by the MVS catalog
The request to IOAMEM is terminated.
Corrective Action: Notify your INCONTROL administrator.
Explanation: IOAMEM received a request to access a data set (dsn) allocated to the ddName DD name, but that dsn is not, in fact, allocated to the ddName DD name.
The request to IOAMEM is terminated.
Corrective Action: Notify your INCONTROL administrator.
Explanation: The parameter list passed to IOAMEM must include a library name, which is missing.
The request to IOAMEM is terminated.
Corrective Action: Notify your INCONTROL administrator.
Explanation: IOAMEM detected that the requested data set (dsn) is migrated by a space management product such as DFSMSHSM, and it cannot be accessed
The request to IOAMEM is terminated.
Corrective Action: Notify your INCONTROL administrator.
Explanation: This messages is issued by the FORMCND procedure (program IOABCN), which formats the conditions file when it is submitted with DISP=SHR instead of DISP=NEW or DISP=OLD.
The format is not run.
Corrective Action: Stop all Control-X monitors and re-run the FORMCND procedure with DISP=OLD.
Explanation: The IOAMEM program failed to allocate memory to the specific member in the specific library.
Corrective Action: Troubleshoot your environment for memory issues.
Explanation: Internal IOA error while trying to read a member from a library. Possible causes are:
The system action depends on the cause, as follows:
Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support for assistance.
Explanation: Internal Control-M error while trying to read a directory of a library during schedule definition, calendar definition, batch utility, etc.
Online facility - Tables or calendars list is not shown.
Corrective Action: For batch utility, correct the error and rerun the job.
Explanation: Internal Control-M error while trying to process a member from a library. Possible causes are shown in the following table:
Circumstances |
System Action |
Possible Cause |
|---|---|---|
New Day procedure |
New Day procedure terminates with errors |
Failure to read a calendar from the data set described by the DACAL DD statement |
Control-M AutoEdit facility |
Job submission is stopped |
Failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement) |
Control-M Online facility |
Processing of schedule, mission, rule or calendar definition is not performed |
Internal failure to process the schedule, mission, rule or calendar definition |
Corrective Action: Examine any prior system message. If there is no such message, prepare the Control-M monitor full output and contact BMC Customer Support for assistance.
Explanation: You are trying to save a table, mission, tree, or rule that does not exist.
The table, mission, tree, or rule is not saved.
Corrective Action: To save a new table, mission, tree, or rule, erase the Y in the SAVE field, mark Y in the CREATE field, and click Enter.
Explanation: The table, mission, tree, or rule you are trying to create already exists in the specified library.
The table, mission, tree, or rule is not created or saved.
Corrective Action: Either specify Y in the SAVE field to replace the existing table, mission, tree, or rule with the changed one, or change its name to a new name.
Explanation: While rerunning or confirming the rerun of the job, the user deleted the restart decision of the job.
The job will be rerun without restart processing.
Corrective Action: No action is required.
Explanation: An error occurred in the CTMMEM module.
The CTMMEM module detected that the record format of the library to be opened differs from the requested record format.
The library or DD name is not allocated.
Corrective Action: If the CTMMEM module was invoked from a user-written program or from one of the user exits, check the parameters passed by the calling program to CTMMEM, and ensure that they match the DCB parameters of the library that the user-written program intends to access.
If the call was not made by a user exit or user-written program, prepare the Control-M monitor full output and contact BMC Customer Support for assistance.
Explanation: This information message indicates that the jobName job with the orderId order ID and odate order date was deleted, because the grp group entity with the groupId order ID, to which this job belongs, was deleted.
Corrective Action: No action is required.
Explanation: This information message indicates that the grp group entity with the odate order date and the orderId order ID was undeleted because the jobName job with the jobId order ID, to which this job belongs, was undeleted by an UNDELETE command.
Corrective Action: No action is required.
Explanation: A request to delete the grp group entity with the odate order date and the orderId order ID was issued. However, not all jobs in this group are eligible for deletion.
Jobs belonging to the specified group that can be deleted are deleted. Jobs that are not ready for deletion remain in their original queue. The group entity is not deleted.
Corrective Action: Wait until all the jobs that belong to the specified group have finished execution, then try again to delete the group.
Explanation: The library directory is full.
Corrective Action: Compress or enlarge the appropriate library.
Explanation: No matching member was found in the library or the library had no members.
Corrective Action: Correct the member-name used in the filter or ensure that the library is not empty, then try again.
Explanation: The JSORT command requires either a RBA or ORDERID subparameter. The order in which the jobs are displayed in screen 3 can be controlled by the JSORT command.
Corrective Action: Do one of the following:
Explanation: This information message indicates that there are no sysouts to be viewed. You can only view an existing sysout. Either no sysout was generated, or the existing sysout was manually deleted.
Corrective Action: No action is required.
Explanation: A Locate RBA command (RBAL) was specified with no, or more than one, RBA parameter. Only one RBA parameter, consisting of from 1 through 6 hexadecimal digits, must be specified for the Locate RBA command.
The Locate RBA command is not executed.
Corrective Action: Specify the Locate RBA command correctly.
Explanation: An invalid RBA value was specified in the Locate RBA command (RBAL). The value specified for the RBA parameter in the Locate RBA command must contain from 1 through 6 hexadecimal digits.
The Locate RBA command is not executed.
Corrective Action: Enter the Locate RBA command with a valid RBA value.
Explanation: The Locate RBA command was specified with an RBA parameter which exceeded the highest RBA in the Active Jobs file.
The Locate RBA command is not executed.
Corrective Action: Enter the Locate RBA command with a correct RBA value.
Explanation: An attempt was made to edit the JCL of a job by using line command J in the Control-M Active Environment screen or the Schedule Setup screen. The job in question had MEMLIB set to GENERAL, but the DALIB is not allocated to the user.
Corrective Action: Allocate DALIB to the user, and reenter line command J.
Explanation: An error occurred while trying to process the indexing in the Control-M Active Environment screen. The displayed reason code (rsn) indicates the reason for the error.
Possible values for rsn are:
The Active Environment screen response time may slow significantly.
Corrective Action: Press Enter to return to the Active Environment screen. Inform the INCONTROL administrator, indicating the reason code and the RBA specified in the message. The INCONTROL administrator should proceed according to the reason code, as follows:
Explanation: The Kill command cannot issued in screen 3 for a job that is executing on a remote NJE node.
Corrective Action: To clear the job, manually set the job to non-NJE (by setting the NJE field to N or blank via 3.Z).
This can be done by doing the following:
After a short time, the Job goes to ENDED status.
Explanation: The RSORT command requires either a FLOW or NAME subparameter. The order in which the Rerun Flow jobs are displayed in screen 3 can be controlled by the RSORT command.
Corrective Action: Do one of the following:
Explanation: The total number of characters in the summary exceeds 128 characters.
Corrective Action: Shorten the summary so that it contains fewer than 128 characters. Each line of the summary may contain up to 70 characters.
Explanation: The total number of characters in the description exceeds 1024 characters.
Corrective Action: Shorten the description so that it contains fewer than 1024 characters.
Explanation: The DO REMEDY parameter is only supported in INCONTROL for z/OS version 6.2.18 and later.
Corrective Action: Install version 6.2.18 or later.
Explanation: The summary and description lines have been left blank.
Corrective Action: Enter information into the summary and description lines.
Explanation: The URGENCY parameter must be set to one of the following values:
Corrective Action: Enter a valid value.
Explanation: The ADJUST CONDITIONS parameter for the SMART Table is set to B (Bridge), but a bridge could not be applied to this job. The SMART Table is ordered without applying the bridge.
This message is followed by message CTM6B2I, which contains more information about the reason for the issue.
Corrective Action: Consider adjusting job conditions, based on the information in message CTM6B2I.
Explanation: This message provides one of the following reasons for the failure to apply a bridge, as reported in message CTM6B1I:
Corrective Action: Consider adjusting job conditions, based on the information in this message.
Explanation: This message follows message CTM6B2I and provides the name of the condition that prevented the bridge from being applied. In certain cases, the name of the predecessor is provided, as well.
Corrective Action: Consider adjusting job conditions, based on the information in this message and the preceding messages.
Explanation: This information message describes a step performed during the process of applying a bridge in a SMART Table (with ADJUST CONDITIONS set to B).
This message is issued only if the level of detail is set by the ADJBCMSG parameter to Y.
Corrective Action: No action is required.
Explanation: This information message describes a step performed during the process of applying a bridge in a SMART Table (with ADJUST CONDITIONS set to B).
This message is issued only if the level of detail is set by the ADJBCMSG parameter to Y.
Corrective Action: No action is required.
Explanation: This information message describes a step performed during the process of applying a bridge in a SMART Table (with ADJUST CONDITIONS set to B).
This message is issued only if the level of detail is set by the ADJBCMSG parameter to Y.
Corrective Action: No action is required.
Explanation: This information message describes a step performed during the process of applying a bridge in a SMART Table (with ADJUST CONDITIONS set to B).
This message is issued only if the level of detail is set by the ADJBCMSG parameter to Y.
Corrective Action: No action is required.
Explanation: The process of applying a bridge in a SMART Table failed due to an internal error or insufficient memory. The SMART Table is ordered without applying the bridge.
Corrective Action: For a memory issue, try increasing the region size specified in the JOB or EXEC JCL. For an internal error, contact BMC Support.
Explanation: The process of applying a bridge in a SMART Table failed because adding a condition would cause the job or table to exceed the maximum allowed size. The SMART Table is ordered without applying the bridge.
Corrective Action: Consider adjusting your job or table.
Explanation: During the process of applying a bridge in a SMART Table, conditions were successfully adjusted in a job.
Corrective Action: No action is required.
Explanation: During the process of applying a bridge in a SMART Table, adjustments to a job’s conditions were only partially successful. More information is provided in messages CTM6B1I, CTM6B2I, and (sometimes) CTM6B3I.
Corrective Action: No action is required.
Explanation: During the process of applying a bridge in a SMART Table, adjustments to a job’s conditions were not successful. More information is provided in messages CTM6B1I, CTM6B2I, and (sometimes) CTM6B3I.
Corrective Action: No action is required.
Explanation: The SMART Table was successfully adjusted during bridge processing.
Corrective Action: No action is required.
Explanation: Adjustments to the SMART Table during bridge processing were only partially successful. More information is provided in messages CTM6B1I, CTM6B2I, and (sometimes) CTM6B3I.
Corrective Action: No action is required.
Explanation: Adjustments to the SMART Table during bridge processing were not successful. More information is provided in messages CTM6B1I, CTM6B2I, and (sometimes) CTM6B3I. The SMART Table is ordered without applying the bridge.
Corrective Action: No action is required.
Parent Topic |