|
|
|
|
|
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: There was an attempt to view statistics of a job for which no statistics are available. The Statistics file is updated only by the CTMJSA JCL procedure. If a job is run for the first time in this system, job statistics may not yet exist. If the job was previously run on this system, CTMJSA is probably not run regularly at your site.
Corrective Action: Check whether or not CTMJSA is runs regularly at your site. To get job statistics, run CTMJSA regularly.
Explanation: An error occurred in the CTMTSYV or CTRTSTP Control-M internal module. There was an attempt to perform a view (V) function or a step list display on the Active Jobs file. However, a problem indicated by the return code occurred in the module, and the SYSDATA could not be retrieved:
Valid values for rc are:
rc |
Explanation |
|---|---|
12 |
The name of Archived Sysout Data set does not follow the Control-M/Restart naming convention for this type of data set. |
16 |
The Archived Sysout data sets (which are accessed to retrieve SYSDATA for viewing) belong to another job. |
20 |
The loading of an internal module failed. Message CTM046S which preceded this message specifies the module in question. |
24 |
The CTRTSTP module encountered an internal CDAM error. |
28 |
ATTACH for the CTRTSTP module failed, probably because of insufficient memory. |
32 |
The CTRTSTP module abended. A symptom dump probably exists in the JOBLOG or the SYSLOG. |
Archived SYSDATA is not displayed.
Corrective Action: Record the return code, prepare the Control-M monitor full output, and contact BMC Customer Support.
Explanation: The CTMTSYV or CTRSTP internal module failed to perform the view or step list display function on the Active Jobs file due to insufficient storage allocated to the Control-M online environment.
The archived SYSDATA is not displayed.
Corrective Action: Notify your INCONTROL administrator. The storage allocated to the online environment by the REGION parameter must be enough for all Control-M processing.
Explanation: The user issued a JOBSTAT command without specifying a member name. The JOBSTAT command, which displays job statistics, needs the name of the member whose statistics are to be displayed.
Corrective Action: Try again. Specify the member name with the JOBSTAT command.
Explanation: A parameter (JOBNAME or GROUPNAME) specified in the JOBSTAT command exceeded the maximum allowable length. The maximum length for the JOBNAME parameter is eight characters. This parameter is required for the JOBSTAT command. The maximum length for the GROUPNAME optional parameter is 20 characters. If this parameter is omitted, the group name is assumed to be blank.
Corrective Action: Correct the command and try again.
Explanation: The Statistics file could not be opened. When you use option 3.S to view job statistics, Control-M attempts to open the Statistics file pointed to by the DASTAT DD statement. This message is displayed when the attempt fails.
Corrective Action: Check that the data set described by the DASTAT DD statement is allocated to the Statistics file. See the Control-M installation procedure for details.
Explanation: Option A (Reactivate) was specified for a job that did not have a status of DISAPPEARED or FAILED REASON UNKNOWN. The Reactivate option can only be specified for jobs having a status of DISAPPEARED or FAILED REASON UNKNOWN. This option allows the search for the sysout to continue.
Corrective Action: No action is required.
Explanation: An invalid AutoRefresh interval was specified. The number of seconds specified for the interval in the AUTO command must be between 1 and 99.
AutoRefresh mode is not activated.
Corrective Action: Re-enter the AUTO command followed by a number between 1 and 99.
Explanation: This information message displays the current AutoRefresh interval and counter value. It is displayed whenever the screen is in AutoRefresh mode to indicate that the screen display is being updated automatically every num seconds. The counter value indicates the number of times the screen was refreshed.
Corrective Action: No action is required.
Explanation: This information message indicates that AutoRefresh mode was terminated. AutoRefresh mode is cancelled by a user request, or if an attempt is made to activate AutoRefresh mode in an environment that does not support it.
For more information, see the description of AutoRefresh mode in the Online Facilities chapter in the Control-M for z/OS User Guide.
Corrective Action: No action is required.
Explanation: The action requested in the Active Environment screen cannot be performed due to storage shortage.
The requested action is not performed.
Corrective Action: Increase the REGION size and try again.
Explanation: This information message indicates that a TSO command entered from the command line of an IOA screen was performed successfully.
Corrective Action: No action is required.
Explanation: The Control-M Statistics file (DD name DASTAT) failed to open. The return and error codes are VSAM codes.
Control-M will not accumulate statistics, and as a result deadline scheduling calculations may be inaccurate.
Corrective Action: Check the return and error codes in the IBM manual for DFP macro instructions for data sets under VSAM macro return and reason codes, and correct accordingly.
Explanation: An unsuccessful attempt was made to perform a TSO command entered from the command line of an IOA screen. A TSO command can only be activated from an IOA screen when running the IOA Online facility under ISPF or TSO. The variables displayed in the message are returned by TSO.
Corrective Action: Verify that you entered the command when running the IOA Online facility under ISPF or TSO. If the command was activated under one of these environments then the problem lies in TSO. Have the INCONTROL administrator correct the problem using the TSO codes appearing in the message and try the command again.
Explanation: This information message indicates that the N line command in the Active Environment screen was used to display the net of dependencies for a specific job, but the job had neither predecessors nor successors.
Corrective Action: No action is required.
Explanation: Jobs have been added to the Active Jobs file (AJF). The Net file might have to be refreshed to display all the dependent jobs.
Corrective Action: Refresh the Net file by issuing command REFRESH NET using Screen 3.
Explanation: The request to display net dependencies of a job cannot be performed because the Net file has not been updated.
Only the root job is displayed.
Corrective Action: Refresh the Net file by issuing command REFRESH NET using Screen 3.
Explanation: When defining a SCHEDULE RBC parameter in a Smart Table Entity, either TBL (a SCHEDULE RBC defined in a Smart Table Entity and used by jobs in this Smart Table) or CTM (a SCHEDULE RBC defined by IOA Calendars Facility and can be used by any job) must be specified in the LEVEL field.
Corrective Action: In the LEVEL field, specify either TBL or CTM.
Explanation: Displayed under IOA Calendars Screen for RBC calendars when either a SAVE RBC or COPY RBC request is issued without specifying an RBC name. The SAVE or COPY request does not proceed.
Corrective Action: Either enter the RBC name to proceed or cancel the request.
Explanation: The asterisk ("*") wild card character, which indicates all the RBCs of the Smart Table entity, can only be used to specify the SCHEDULE RBC scheduling parameter for a job that belongs to a Smart Table.
Corrective Action: Use * only for Schedule RBCs defined in Smart Tables.
Explanation: A schedule cannot be defined with only Exclude RBCs. At least one Include RBC must be part of the schedule definition, besides the Exclude RBCs.
Corrective Action: Define or make reference to at least one include RBC, besides the Exclude RBC.
Explanation: The request to display net dependencies of a job cannot be performed because the Net file is being refreshed.
Only the root job is displayed.
Corrective Action: Wait a short while, then press Enter again. Repeat this until the refresh process is completed and the dependent jobs are displayed.
Explanation: The request to display net dependencies of a job cannot be performed because the Net file is busy.
Only the root job is displayed. No dependent jobs are displayed.
Corrective Action: Wait a short while and then press Enter again. Repeat this until the Net file is released and the dependent jobs are displayed.
Explanation: An error occurred during display of the net dependencies of a job. If rc is 28, the QNAME in the GRF file in the first record, just after the constant JD0, differs from the QNAME specified in IOAPARM.
The variables in this message are:
The Net screen is not displayed.
Corrective Action: Notify your INCONTROL administrator or system programmer, who should take required actions based on the information in the message. For example, depending on the type of error, the requested load module can be made accessible, or the region size can be enlarged.
If rc is 28, reformat the GRF file with the QNAME specified in IOAPARM.
Explanation: The user specified the REFRESH command in the Net screen (screen 3.N) with an invalid parameter.
The REFRESH process is not performed.
Corrective Action: Re-issue the REFRESH command with a valid parameter.
Explanation: The REFRESH NET command was issued but the Control-M monitor was down, so some jobs may not have been displayed in the Net Display screen.
Corrective Action: Wait until Control-M comes up again, then continue work as usual.
Explanation: This information message indicates that the REFRESH command was successfully submitted in the Net screen (screen 3.N).
The Refresh process starts.
Corrective Action: Wait until the refresh is complete, then continue working.
Explanation: The function requested is not authorized for the user. The message is issued by the IOA security mechanism.
Corrective Action: Check with your system security administrator.
Explanation: This information message is a response to the use of the SET command to set a language. It indicates that the newly-set language will begin to be used when you next log on to IOA.
Corrective Action: No action is required.
Explanation: Either the value or the setting of the specified trace is not valid. The trace level may be any value from 1 through 256. The trace level setting must be ON or OFF.
The system ignores the command and continues processing.
Corrective Action: Enter a valid value and/or a valid setting for the trace level, and try again.
Explanation: This information message indicates that a trace level was turned ON or OFF, where nnn is the TRACE level number.
Corrective Action: No action is required.
Explanation: A user issued the SET TRACE command in order to turn on the trace, and the tracing is not allowed.
The trace is not turned on.
Corrective Action: Contact your IOA administrator in order to enable the online tracing.
Explanation: The AJF conversion utility issues this information message to show the number of jobs on the old Active Jobs file, and the number of old Active Jobs file records that were needed to store these jobs.
Corrective Action: No action is required.
Explanation: The AJF conversion utility issues this information message to show the number of jobs on the new Active Jobs file, and the number of new Active Jobs file records that are now needed to store these jobs.
The variables in this message are:
Corrective Action: No action is required.
Explanation: The AJF conversion utility issues this information message to show the percentage of unused records in the new Active Jobs file (AJF).
In this message, nn% is the percentage of unused records in the new AJF.
Corrective Action: No action is required.
Explanation: The AJF conversion utility issues this information message to show the average number of records used to store one job on the new Active Jobs file.
Corrective Action: No action is required.
Explanation: The AJF conversion utility issues this information message to show the average number of unused bytes in the records used to store one job on the new Active Jobs file.
Corrective Action: No action is required.
Explanation: The CTMCAF utility cannot convert the file from one version to another because only one Load library was indicated. The STEPOLD DD statement should point to the Load library of the previous version, but it points to the Load library of the new version.
The CTMCAF utility terminates with a return code of 08.
Corrective Action: Correct the STEPOLD DD statement so that it points to the Load library of the previous version, and rerun the job.
Explanation: The CTMCAF utility cannot convert the file from one version to another because the AJF or HST file sizes are not identical. The conversion requires the same size files for the new version and the old version. The file size should match the size specified in CTMPARM.
The CTMCAF utility terminates with a return code of 08.
Corrective Action: Correct the file sizes so that they are identical for both versions, and rerun the job.
Explanation: An internal error occurred during the load of the CTMLOGR module.
The CTMCAF utility terminates with a return code of 08.
Corrective Action: Have your INCONTROL administrator record the return code, prepare the Control-M monitor full output, and contact BMC Customer Support.
Explanation: An internal error occurred during deletion of the CTMLOGR module.
The CTMCAF utility terminates with a return code of 08.
Corrective Action: Have your INCONTROL administrator notify your INCONTROL administrator.
Explanation: Internal error in the Control-M Monitor logic of keeping Jobs in the memory. Control-M Monitor terminates abnormally.
Corrective Action: Keep the Control-M Monitor output and IOA LOG and contact IOA technical support.
Explanation: This information message notifies you that the memory image for the Active Jobs File (AJF) was allocated above the 2G bar.
Corrective Action: No action is required.
Explanation: This message is issued when AJFABAR=Y is used for explicit loading of the AJF into 64-bit storage (above the 2GB BAR). Such an AJF is capable of supporting up to 10,000,000 records. As a result, the AJF Space Reuse facility, which allows reuse of space in smaller-sized AJFs that are loaded to 31-bit storage (below the 2GB BAR), is not required and is therefore disabled by enforcing the REUSTIME=0 setting in CTMPARM.
Corrective Action: You can choose the following alternative settings:
Note: The Space Reuse Facility can only be enabled when the AJF is loaded to 31-bit storage (below the 2GB BAR). Support for this facility will be discontinued in a future release of Control-M, and BMC advises that you disable it. Disabling the Space Reuse Facility allows the AJF to be loaded to 64-bit storage (above the 2GB BAR) and enables you to manage high volumes of jobs in the AJF.
Explanation: This message is issued when AJFABAR=A is used for automatic selection of the storage type to which the AJF is loaded (that is, either 31-bit “below the 2GB BAR” or 64-bit “above the 2GB BAR”). The message indicates that 31-bit storage (below the 2GB BAR) is selected, because the Space Reuse Facility is enabled (REUSTIME is set to a non-zero value in CTMPARM).
Corrective Action: If you want to allow the AJF to be loaded to 64-bit storage (above the 2GB BAR), disable the Space Reuse Facility by setting REUSTIME=0 in CTMPARM.
Note: The AJF can be loaded to 64-bit storage (above the 2GB BAR) only if the Space Reuse Facility is disabled. Support for this facility will be discontinued in a future release of Control-M, and BMC advises that you disable it. Disabling the Space Reuse Facility allows the AJF to be loaded to 64-bit storage (above the 2GB BAR) and enables you to manage high volumes of jobs in the AJF.
Explanation: A started task (STC) requiring APF authorization was not APF authorized. Certain STCs (for example, CTMVMON) must be run from APF authorized libraries.
The task stops after issuing the error message.
Corrective Action: Change the JCL or authorize the library so that the STC will be run from an authorized library.
Explanation: While processing a Control-M DO FORCEJOB, CMEM or Control-O request, the Control-M monitor encountered an error while reading table memName in data set dsn.
This message is followed by additional messages which identify the failed action.
No additional action will be taken for the failed job/table order.
Corrective Action: For information about the return code rc, see the DOCIMEM member in the IOA DOC library.
Explanation: While processing CMEM or Control-O request, the Control-M monitor encountered an empty table memName in data set dsn.
This message is followed by message WKJA59E which identifies the failed action.
No additional action will be taken for the failed job/table order.
Corrective Action: Make sure that table memName contains valid scheduling information.
Explanation: While processing a CMEM or Control-O request for data set dsn, the Control-M monitor encountered an abend condition abCode.
This message is followed by message WKJA59E which identifies the failed action.
No additional action will be taken for the failed job/table order.
Corrective Action: Record the abend code, prepare the Control-M monitor full output, and contact BMC Customer Support.
Explanation: An error occurred while processing a FORCEJOB request for job jobName, or, in the case where jobName is blank, for the complete scheduling table tableName.
The source of the request may be:
This message is preceded by another message, which gives more details of the cause of the error.
Control-M may try again to execute the job or table, depending on the values set for the FORCE#RT and FORCE#WI installation parameters. For more information, see the customization chapter of the INCONTROL for z/OS Installation Guide.
Corrective Action: Correct the error as detailed in the preceding message. If scheduling is still required for the job or table for which the error occurred, then the job or table should be ordered manually. If the specification in the original request was incorrect, correct it and reload, if necessary. Reload the CMEM table or reorder the Control-O rule.
Explanation: This error message is issued when an attempt is made to read an MVS System Logger log stream which is currently being read by another Control-M monitor.
To avoid a loop of FORCEJOB jobs, the same MVS System Logger log stream should not be read simultaneously by more than one Control-M monitor . Should a second Control-M monitor attempt to read the same log stream, this error message is issued.
The CMEM facility is deactivated for this Control-M monitor.
Corrective Action: Make sure only one Control-M monitor is reading the same MVS System Logger log stream simultaneously.
Explanation: A Control-M component attempted to free a block of working storage, but failed to do so.
The variables in this message are:
No additional action is performed.
Corrective Action: If this is a recurring problem, prepare the Control-M monitor full output and contact BMC Customer Support. If ignored, this may cause severe insufficient storage problems.
Explanation: Control-M failed to execute a DO FORCEJOB request because a scheduling table was in use.
The source of the DO FORCEJOB request may be any of the following:
Control-M queues the DO FORCEJOB request, and may try again to execute it, depending on the values set for the FORCE#RT and FORCE#WI installation parameters.
For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.
Corrective Action: No action is required.
Explanation: After failing to execute a DO FORCEJOB request because a scheduling table was in use, Control-M retried the request and succeeded in executing it, in accordance with the values set for the FORCE#RT and FORCE#WI installation parameters.
The source of the DO FORCEJOB request was one of the following:
No additional action is taken.
Corrective Action: No action is required.
Explanation: During the processing of a CONNECT DIRECT request, no successfully triggered events were processed, and a data set-in-use condition occurred.
The probable source of the CONNECT DIRECT request is the IOADCC utility.
Control-M queues the DO FORCEJOB request, and will try again to execute it, in accordance with the values set for the FORCE#RT and FORCE#WI installation parameters.
For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.
Corrective Action: No action is required.
Explanation: A DO FORCEJOB command was issued for a table in the schedLib scheduling library, which has been migrated. An attempt was made to RECALL the library. An additional message follows describing whether the RECALL action was successful or not.
Corrective Action: Look for the following messages, which inform about the success of the RECALL action.
Explanation: When a schedule table is not available because the data set is in use by another address space, Control-M retries the request several times based on the FORCE#RT parameter in CTMPARM. When this number of retries is exhausted and Control-M no longer retries the request, this message is displayed.
Control-M no longer retries the request.
Corrective Action: Determine why the data set is in use and retry the request manually. Messages CTMC53E and CTMA59E give details about the job name, table name, and schedule library name.
Explanation: This information message indicates that an exceptional VTAM condition was encountered during the execution of a KOA communication command.
This informational message is issued by the KOA Facility. Return code, error and feedback information are detailed in an appendix to the Control-O User Guide.
The KOA script continues processing. If an ON SCREENERROR statement was specified, the processing resumes at the label specified in the ON statement.
Corrective Action: Analyze the specific VTAM error, and take the corresponding corrective actions. Make sure that the error is handled correctly by the KOA script.
Explanation: An internal abend was intercepted by the KeyStroke utility.
The KSL/KOA script is terminated.
Corrective Action: Check the associated error messages. Correct the KOA script accordingly, and resubmit.
Explanation: The SMFID of the CPU to which the KSL job was submitted does not appear in the IOAKPRM member in the IOA PARM library.
The KSL stops running.
Corrective Action: Add the SMFID by making the appropriate entry in the IOAKPRM member. The best way of doing this is by means of the INCONTROL Installation and Customization Engine (ICE). For more information on ICE, see the INCONTROL for z/OS Installation Guide.
Explanation: This informational message indicates that the initial program invoked by the CTMEMUDL procedure has begun processing.
Corrective Action: No action is required.
Explanation: This information message indicates the normal termination of the initial program invoked by the CTMEMUDL procedure.
Corrective Action: No action is required.
Explanation: This information message indicates the start of Control-M AutoEdit cache initialization. The message is issued on starting the Control-M monitor if the AECACHL parameter is defined, or when the command F CONTROLM,AECACHE=RELOAD... is processed.
In this message, memName identifies the member that contains the list of members that should be loaded into AutoEdit cache.
Corrective Action: No action is required.
Explanation: This information message displays a non-comment line from the member indicated in message CTMAE1I, as follows:
Corrective Action: No action is required.
Explanation: An error occurred during the reading of the member referenced by the DD statement identified in message CTMAE2I. The return code (rc) and reason code (rsn) are returned by the IOAMEM utility.
Loading of Auto-Edit cache is terminated.
Corrective Action: Correct the error. Recycling of the Control-M monitor is not necessary; refresh the Auto-Edit cache by entering the operator command F CONTROLM,AECACHE=RELOAD[(memName)].
Explanation: An internal error occurred during the loading of AutoEdit cache. The cause may have been a shortage of storage.
Loading of Auto-Edit cache is terminated.
Corrective Action: Correct the error. Recycling of the Control-M monitor is not necessary; refresh the Auto-Edit cache by entering the operator command F CONTROLM,AECACHE=RELOAD[(memName)].
Explanation: An AutoEdit syntax error was detected either in the line identified in message CTMAE2I, or in the member referenced by that line.
Loading of Auto-Edit cache is terminated.
Corrective Action: Correct the syntax error. Recycling of the Control-M monitor is not necessary; refresh the Auto-Edit cache by entering the operator command F CONTROLM,AECACHE=RELOAD[(memName)].
Explanation: An error occurred when trying to access the IOA AutoEdit database.
If the problem occurred during JCL processing during submission, and %%RESOLVE NO was not previously set , job submission is cancelled. Otherwise, the variable remains as is, that is, unresolved.
Corrective Action: The following actions are recommended:
Parent Topic |