Messages SPY200 through SPY2xx

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.

SPY250I CONTROL-M IS TERMINATING. TERMINATION SHOULD BE COMPLETED IN LESS THAN TWO MINUTES

Explanation: Highlighted, unrollable message.

This information message indicates that the Control-M monitor is about to shut down because of an internal problem. Due to a unique situation, the termination process may take longer than usual.

Control-M monitor will shut down after approximately one minute.

Corrective Action: Do not cancel the Control-M monitor. If it does not shut down after 5 minutes, cancel it with DUMP, prepare the Control-M monitor full output, and notify BMC Customer Support. Find out why the Control-M monitor shut down and start it again as soon as possible.

SPY251I SPY STARTED

Explanation: This information message is generated when the Control-M monitor internal SPY task is started.

Corrective Action: No action is required.

SPY252S taskType memName jobName /jobId OID=orderId SEVERE INTERNAL ERROR

Explanation: Severe Control-M monitor internal error while processing the above mentioned job order.

Control-M monitor will abend with user code 0006. The internal task CTMSPY will abend with user code 0040.

Corrective Action: Control-M Log should contain additional messages describing the type of error.

SPY253E taskType memName jobName /jobId OID=orderId NOT FOUND IN QUEUE num TIMES

Explanation: Control-M monitor searched number times but did not find the job in the JES queue.

Possible causes are:

Someone has purged the job (before, during or after execution).
The user tried to activate a started task that does not exist in the Procedures library.
The user activated a started task, but the JES parameter STCMCLAS is directed to a non-print output class. See the section on Started Tasks in the Control-M Installation Considerations section in the INCONTROL for z/OS Installation Guide.
The job/STC has been sent to another NJE node while the Control-M NJE option has not been installed.
The jobs output has been read by an external writer before the Control-M monitor has managed to read it. See the section on the Control-M Operational Parameter - HLDCLAS, in the INCONTROL for z/OS Installation Guide.

The job will finish with status Disappeared. The event code is JLOST.

Corrective Action: Check the reason for the disappearance of the job/STC and correct it. Make sure that no-one purges the output of Control-M jobs. (Only cancel commands should be allowed.)

SPY254I taskType memName jobName /jobId OID=orderId SCANNED

Explanation: This information message is generated when the Control-M monitor finishes processing the job’s output.

Corrective Action: No action is required.

SPY255S taskType memName jobName /jobId OID=orderId CONTROL-M SHUTTING DOWN - SEVERE ERROR WHILE PROCESSING JOB SYSOUT

Explanation: Highlighted, unrollable message.

Control-M monitor had a severe error while reading the output of the job and is shutting down.

Control-M monitor will shut down.

Corrective Action: Check the contents of the IOA Log for prior messages that will clarify the picture. If you cannot correct the reason, and whenever you start the Control-M monitor, the monitor shuts down again for the same reason, then enter screen 3 of the Online Facility and hold the job order. Prepare the Control-M monitor full output and contact BMC Customer Support.

SPY256S taskType memName jobName /jobId OID=orderId CONTROL-M SHUTTING DOWN - COMMUNICATION TO "JES" NOT AVAILABLE

Explanation: Highlighted, unrollable message.

The Control-M monitor detected some problem in communication to JES, and shuts down as a precaution. The Control-M monitor is usually one of the first components of the computer environment to detect problems in JES operation. Usually this is because JES was brought down, or is about to get stuck because of an internal JES problem.

The Control-M monitor will shut down.

Corrective Action: Correct the JES problem and restart the Control-M monitor.

SPY257E taskType memName jobName /jobId OID=orderId DISAPPEARED BECAUSE OF CONTROL-M SHUT DOWN

Explanation: A started task had been started by the Control-M monitor, but had not yet been assigned a job number by the JES, when the Control-M monitor was forced to shut down. When the Control-M monitor was brought up, it considered the output as lost.

The status of the started task will be Disappeared.

Corrective Action: Check very carefully. Maybe the started task did run while the Control-M monitor was down. If so, you have to notify Control-M manually of the results.

SPY258S taskType memName jobName/blank OID=orderId INSUFFICIENT MEMORY FOR CONTROL-M MONITOR

Explanation: Highlighted, unrollable message.

Insufficient memory for Control-M monitor to trace a started task.

The started task has just been initiated by the Control-M monitor, and the Control-M monitor requires a small work area in order to try to locate the job ID assigned by JES to the started task. Unfortunately, there is insufficient memory for the required work area.

The Control-M monitor will try again after a few seconds (it is possible that memory will be released by other components of the Control-M monitor). Meanwhile, the started task will remain with a STARTED status and the job ID is “blank.” Under severe circumstances of this event, the Control-M monitor may shut down.

Corrective Action: Increase the Control-M monitor region size and start it again. You are working on the limits.

SPY259I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message announces the shut down of the Control-M monitor.

Shut down of Control-M internal spy task by a request of Control-M main task.

Control-M monitor will shut down.

Corrective Action: No action is required.

SPY270E taskType memName jobName/jobId OID=orderId SYSOUT action FAILED [FROM=class][DSN=dsn] [SECURITY VIOLATION]

Explanation: A sysout operation on the job’s output has failed. SECURITY VIOLATION is displayed if, during an ARCHIVE attempt, the IOASE32 security module does not allow the allocation of the archive data set specified by DSN=dsn.

The failing action can be:

Action	Description
RELEASE	Release the sysout.
DELETE	Delete (purge) the sysout.
NEWCLASS==>class	Change sysout class (to the specified class).
NEWDEST==>destination	Change sysout destination to the specified destination.
ARCHIV	Copy the sysout to a data set.

The FROM= class appears when the sysout operation will be limited to a specified class (not on all the held sysouts).
The DSN= dsn designates the data set name used for the archiving action.

The sysout operation will not be executed, but it will not affect the finishing status of the job (OK or NOTOK).

Corrective Action: Look for a previous message that will clarify the reason for the failure. You will have to execute the sysout operation manually (until next time).

If the action is ARCHIV, and Spool Encryption is in use, make sure that the Control-M monitor is authorized to read all encrypted spool output datasets of jobs submitted by Control-M.

SPY271E taskType memName jobName/jobId OID=orderId OPEN OF DDNAME "OUT180" FAILED

Explanation: Highlighted, unrollable message.

Open of Control-M work data set described by the OUT180 DD statement failed.

This may be due to the following:

The OUT180 DD statement is missing.
The OUT180 DD statement cannot be opened for sequential processing.

The Control-M monitor will shut down with an error message.

Corrective Action: Correct the JCL for the Control-M monitor and start it again.

SPY272E taskType memName jobName/jobId OID=orderId INTERNAL STACK CAPACITY OVERFLOW. SEE MESSAGES AND CODES FOR REQUIRED ACTION

Explanation: Control-M monitor internal job events stack capacity exceeded.

When Control-M monitor analyzes the job’s output, all the execution events such as condition codes, abend codes, user defined codes, and so on, are accumulated in a stack (in memory). For some reason the stack became full, and Control-M monitor cannot finish analyzing the job’s results. This can happen because of:

A loop in user exit CTMX003 (which is capable of adding events to the stack).
An internal error in the Control-M monitor.

Message SPY278E will be issued. The job will finish with ENDED NOT OK - REASON UNKNOWN status.

Corrective Action: Ask your system programmer to check Control-M exit CTMX003. If this does not solve the problem, call BMC Customer Support. Keep the sysout of the job causing the problem in hold status so further testing can be carried out.

SPY273E taskType memName jobName/jobId INTERNAL ERROR. RBA=rba INVALID "CODES"- SEE MESSAGES AND CODES FOR REQUIRED ACTION

Explanation: Internal error in the operation of Control-M monitor.

Invalid data discovered in the job order which resides in the rba in the Active Jobs file. It can be due to the following:

A Control-M user exit incorrectly modified the job order.
Someone incorrectly modified the Active Jobs file.
A chain of unexpected processing errors occurred prior to this event.
Internal Control-M monitor error.

SPY278E message will follow, and the job will finish with ENDED NOT OK - REASON UNKNOWN status.

Corrective Action: Check the IOA Log. If there are previous severe errors regarding this job, they are probably the cause of the problem. Correct them and the problem should be resolved. Otherwise, have your system programmer call BMC Customer Support for assistance. The IOA representative will need a copy of the Active Jobs file.

SPY275E OID=orderId NOT CATLGD x ON DSNAME dsn

Explanation: A NOT CATLGD 2 (or NOT RECTLGD 2) event has occurred during job execution on data set dsn.

The default of this event is NOTOK for the entire job. The user may specify an ON STEP ANYSTEP CODES *NCT2 DO OK to signify that the event NCT2 (NOT CATLGD 2) is considered OK for this job.

The status of the job will be according to user definition.

Corrective Action: No action is required.

SPY276E taskType memName jobName/jobId OID=orderId READING SYSOUT FAILED

Explanation: Reading of job’s sysout failed.

Control-M failed to read the job’s output.

The job will finish with status FAILED - REASON UNKNOWN (the event *UKNW).

Corrective Action: Check the IOA Log for additional messages which will clarify the reason for the problem.

SPY277E taskType memName jobName/jobId OID=orderId INTERNAL ERROR INVALID SYSOUT OPTION_opt. SEE MESSAGES AND CODES FOR REQUIRED ACTION

Explanation: Internal error in the operation of Control-M monitor.

Invalid data discovered in the job order. It can be due to the following:

Control-M user exit incorrectly modified the job order.
Someone incorrectly modified the Active Jobs file.
A chain of unexpected processing errors occurred prior to this event.
Internal Control-M monitor error.

SPY278E message will follow, and the job will finish with ENDED NOT OK - REASON UNKNOWN status.

SPY278E taskType memName jobName/jobId OID=orderId OUTPUT PROCESSING FAILED

Explanation: General message when the processing of the output of the job fails.

The Control-M should contain additional messages concerning the reasons.

Determined by the problem which has caused the failure.

Corrective Action: Check the IOA Log for additional messages.

SPY279I taskType memName jobName/jobId OID=orderId SYSOUT action [FROM=class] [DSN=dsn]

Explanation: This information message is the result of a successful sysout operation on the job’s sysout.

The sysout operation can be:

Operation	Description
RELEASED	Release the sysout.
DELETED	Delete (purge) the sysout.
NEWCLASS==>class	Change sysout class (to the specified class).
NEWDEST==>destination	Change sysout destination (to the specified destination).
ARCHIVED	Copy the sysout to a data set

The FROM= class will appear when the sysout operation will be limited to a specified class (not on all the held sysouts).
The DSN= dsn will designate the data set name used for the archiving action.

Corrective Action: No action is required.

SPY27AI OID=orderId CYCLING STOPPED BY "DO STOPCYCL" STATEMENT

Explanation: A DO STOPCYCL statement in a job scheduling definition caused Control-M to stop cycling a job.

Control-M stops initiating the job at regular intervals when it encounters a DO STOPCYCL statement.

Control-M stops cycling the job and reports the status of the job as OK or NOTOK, depending on the last run of the job.

Corrective Action: To resume cycling of the job, issue a RERUN or RESTART statement for the job from the Active Environment screen.

SPY27CW step/range stepName.procstepName / stepsRangeNname REFERENCED BY "ON PGMST" DOESN'T MATCH ANY STEP IN JCL OF JOB

Explanation: The installation parameter DEFSTEP=Y is specified in the CTMPARM member and the step/range referenced by the ON PGMST statement in the job definition does not match any step in the job’s JCL.

The ' Post-Processing Failed' characteristic is added to the job's status in Control-M.

Corrective Action: Check the JCL of job and its corresponding job definition. If one of them was changed, the other one should be corrected accordingly.

SPY27DI SYSOUT ACTION REQUESTED TYPE= [CLASS=] [DEST=] [FROMCLASS=]

Explanation: This information message indicates that the processing of a sysout operation has begun. TYPE= values are: SYSREL (release), SYSPURG (delete), SYSCLAS (change class) and SYSNDST (change destination). CLASS= is the new output class, DEST= is the new destination, FROMCLASS= is the original output class specified in the request.

Corrective Action: No action is required.

SPY27EI SYSOUT ACTION REQUEST QUEUE INITIALIZED SUCCESSFULLY

Explanation: This information message indicates that the sysout action request queue has been initialized successfully.

Corrective Action: No action is required.

SPY27FW SYSOUT ACTION REQUEST QUEUE NOT INITIALIZED - MEMORY ALLOCATION FAILED

Explanation: Sysout action request queue not initialized due to lack of available storage. The enhanced spy feature will not be used.

Corrective Action: To use the enhanced spy feature, increase the REGION size of the Control-M monitor.

SPY27GW SYSOUT ACTION REQUEST QUEUE NOT INITIALIZED - RC FROM IOAREQ IS #

Explanation: Internal error during the initialization of the sysout action request queue. The enhanced spy feature will not be used.

Corrective Action: Report the message ID and return code to BMC Software Customer Support.

SPY27HW SYSOUT ACTION REQUEST QUEUE READ FAILED - RC FROM IOAREQ IS #

Explanation: Internal error during the processing of a sysout request.

Corrective Action: Report the message ID and return code to BMC Software Customer Support.

SPY27JW SYSOUT ACTION REQUEST PUT FREE ENTRY FAILED - RC FROM IOAREQ IS #

Explanation: Internal error during the processing of a sysout request.

Corrective Action: Report the message ID and return code to BMC Software Customer Support.

SPY27KW MULTI-SPY NOT ENABLED - DOES NOT SUPPORT SDSB=F OR SAPI=N

Explanation: The multi-spy feature was not enabled because either SDSB=F or SAPI=N (or both) were specified in CTMPARM.

Corrective Action: To use the enhanced spy feature, specify SDSB=Y and SAPI=Y in CTMPARM.

SPY280W taskType memName jobName/jobId OID=orderIduser message

Explanation: A user message to the Control-M Log.

The message is created by user exit CTMX003.

The exit is activated during the Control-M sysout scan. If you do not understand the meaning of the message, consult your INCONTROL administrator.

Corrective Action: No action is required.

SPY281I taskType memName jobName/jobId OID=orderId START start_daytime STOP end_daytime CPU nnnn MIN ss SEC SRB nnnn MIN ss SEC elapsed_time initiator_num class systemId userData

Explanation: This information message displays a statistical record containing job and group execution statistics.

Item	Description
start_daytime	Start time of the job as Julian date + hour + minutes.
end_daytime	Termination time of the job as Julian date + hour + minutes.
CPU	CPU time in minutes and seconds.
SRB	SRB time in minutes and seconds.

The information described above is taken from the job’s output statistical messages (IEF375I, IEF376I).

Item	Description
elapsed-time	Elapsed time in minutes and hundredths of a minute.
initiator-num	1-character initiator number.
class	1-character identifier of the Job class in which the job executed. If the Job class is longer than 1 character, this byte is filled by the "." Character.
systemId	4-character system identifier (where the job executed).
userData	Statistical information optionally added by user exit CTMX003.

If taskType is GRP, this message represents group execution statistics. However:

the CPU and SRB times will be zero,
the elapsed_time is the time between the start of the first job in the group entity until the end of the last job in the group entity, and
the class, initiator_num, systemId and user-data fields will be blank.

Corrective Action: No action is required.

SPY283I taskType memName jobName/jobId OID=orderId RE-QUEUED FOR EXECUTION ON STEP step ($EJ COMMAND)

Explanation: This information message indicates that the job has been requeued for execution by operator command $EJ (JES2) or has been restarted (JES3 message IAT2006).

This message is recorded for each “requeue” (restart) event during the lifetime of the job. It is an informative message.

Corrective Action: No action is required.

SPY287I OID=orderId JOB SYSOUT WAS PURGED SUCCESSFULLY

Explanation: This information message indicates that Control-M cancelled a job submission and purged the job sysout.

During AutoEdit resolution an in-use data set was encountered, such as a %%INCLUDE statement specified for a data set that is in use. Control-M purged the job sysout because an attempt will be made to resubmit the job.

Control-M will attempt to resubmit the job.

Corrective Action: No action is required.

SPY288W OID=orderId SUBSYSTEM REQUEST TO PURGE JOB SYSOUT FAILED

Explanation: Control-M cancelled a job submission, but did not manage to purge the job sysout.

During AutoEdit resolution an in use data set was encountered, such as a %%INCLUDE statement specified for a data set that is in use. Control-M tried to purge the job sysout because an attempt will be made to resubmit the job.

Control-M will attempt to resubmit the job.

Corrective Action: Manually purge the job sysout for the failed job.

SPY289E CONTROL-M EXTENDED MCS TRACKING STOPPED. RC=rc

Explanation: Highlighted, unrollable message.

A system error occurred when Control-M monitor attempted an extended MCS console operation.

Control-M stops using the extended MCS console.

Corrective Action: Check for a preceding system or IOA message related to this message, and proceed accordingly.

SPY28AE OID=orderId CTMCJI INTERNAL ERROR. RC=rc, REASON=rsn, JOBID=jobId

Explanation: An internal error occurred when an NJE job with a changed job ID was being processed.

The process of the job is aborted.

Corrective Action: Call BMC Customer Support with the following data: Job SYSDATA files (the first 3 files of the job created by the system), the IOA Log file for that job, and the message text showing the exact RC, REASON and JOBID.

SPY28GI OID=orderId TAPE DRIVE UNITS USED=nn nn nn nn nn nn nn nn nn nn nn nn

Explanation: This information message provides statistical information on the tape drive usage of a job.

At the end of each job execution, the job log is checked to evaluate tape drive usage. The UNITDEF member of the Control-M PARM library is used to associate logical names to physical resources (meaning tape drive units). UNITDEF sorts tape drive unit addresses into twelve groups or less.

The variables in this message are:

orderId - the order ID of the job
nn - The number of tape drives in each group used by the tape drive. In the message, each tape drive group is identified by its order after USED (for example, the first group corresponds to the first nn).

Corrective Action: No action is required.

SPY28HW OID=orderId AUTO TAPE DRIVE RESOURCE ADJUSTMENT IS BYPASSED DUE TO PREVIOUS MESSAGE

Explanation: Resource adjustment for the Automatic Tape Adjustment facility was bypassed for current job end processing.

An error occurred during resource adjustment for the Automatic Tape Adjustment facility. The reason is described in the preceding message.

Job end processing continues without tape drive adjustment.

Corrective Action: Check the reason described in the preceding message.

SPY28JE OID=orderId ERROR ANALYZING PARM MEMBER "UNITDEF" AT LINE lineNum

Explanation: An error was detected in the specified line of UNITDEF.

There is probably a syntax error.

The Automatic Tape Adjustment facility is turned OFF for the job, and processing continues.

Corrective Action: To implement automatic tape adjustment, correct the error in the specified line and restart Control-M.

SPY28KW OID=orderId DAUNITDF DD CARD MISSING

Explanation: There is no valid DD statement that points to UNITDEF.

Either the statement is missing or it contains a syntax error.

The Automatic Tape Adjustment facility is turned OFF for the current job, and processing continues.

Corrective Action: To implement automatic tape adjustment, correct the DD statement that points to UNITDEF and restart Control-M.

SPY28LS OID=orderId GETMAIN FAILED IN CTMATD AUTO TAPE PROCESSING

Explanation: There is not enough memory to perform Automatic Tape adjustment.

The region may be too small.

The Automatic Tape Adjustment facility is turned OFF for the current job, and processing continues.

Corrective Action: To implement automatic tape adjustment, increase the size of the region and restart Control-M. If there still is not enough memory, contact your local systems analyst.

SPY28ME OID=orderId TAPE UNIT unitId IS NOT DEFINED IN "UNITDEF" MEMBER

Explanation: During Automatic Tape Adjustment facility processing, a Tape Unit address was specified in the job log. However, this unit address was not defined in the UNITDEF member.

Resource adjustment for the Automatic Tape Adjustment facility of Control-M was unable to assign Tape Unit address unitId to a defined tape drive type.

The unknown tape drive is ignored for the job and processing continues.

Corrective Action: Check the UNITDEF member of the Control-M PARM library. Verify that the unit address is properly defined.

SPY28NI NEW TAPE DRIVE DEFINITION IS LOADED PER OPERATOR REQUEST

Explanation: This information message indicates that a fresh copy of the UNITDEF member is now in use.

A new copy of the UNITDEF member was loaded in response to modify command F.

Corrective Action: No action is required.

Parent Topic

SPY messages