The normal mode manager (NMM) subtask has been requested to terminate processing. This request is propagated to all active subtasks. The NMM subtask starts its own termination when all subtasks have ended.

A current plan refresh request has been processed by the normal mode manager (NMM) subtask. The current plan data set has been closed and the checkpoint data set has been updated to indicate that no current plan is available. All HCL Workload Automation for Z functions that need access to the current plan data set are inoperative.

The normal mode manager (NMM) subtask was reading the job tracking log data set during restart from checkpoint and met an error accessing a current plan operation record while processing an automatic job recovery event.

A severe error occurred while closing a VSAM file.

A HCL Workload Automation for Z subtask or batch job encountered an I?O error when accessing a VSAM data set.

A severe error has occurred in the normal mode manager (NMM) subtask.

An invalid job tracking event record has been found in the job tracking log data set. The most likely cause is that the last four bytes of the record do not contain the HCL Workload Automation for Z identifier EQQ3. It is also possible that the first three characters of the job number field do not contain the character string JOB.

An invalid job tracking event record has been found in the job tracking log data set. The normal mode manager (NMM) subtask could not determine the origin of the event. Each event must come from one of 16 possible event data sets on each HCL Workload Automation for Z node. In the current event record, either the event number in the data set or the HCL Workload Automation for Z node number is invalid.

An abend prevented the normal mode manager (NMM) subtask from finishing its processing of a job tracking event while it read the job tracking log data set.

The controller could not open the checkpoint or backup checkpoint data set, which is a required data set for HCL Workload Automation for Z when OPCHOST(YES) is specified.

An I?O error occurred when a HCL Workload Automation for Z function tried to write a log record to the currently active job tracking log file.

An abend occurred when a HCL Workload Automation for Z function attempted to write a record to the current job tracking log data set. If the abend code is SB37 or SD37, the current job tracking log data set is too small.

The normal mode manager (NMM) subtask has switched to the next available job tracking log data set. This is done after every current plan backup. If dual logging is requested, the dual log data set is also switched to the next available data set.

The normal mode manager (NMM) subtask has started successfully and there is an available current plan.

The normal mode manager (NMM) subtask determined that the current plan data set could not be used. A new current plan has been created by starting from the old current plan and reprocessing events logged on the job tracking log data set.

A HCL Workload Automation for Z subtask has finished copying a VSAM data set to a backup data set.

In the JCL repository data set, the name in use after a copy is DDNAME.

A HCL Workload Automation for Z subtask has started to copy the JCL repository data set because either the current one has reached its maximum size or a backup has been requested using the BACKUP TSO command for the JS resource.

A VSAM LSR buffer pool has been successfully built for the file allocated to DDNAME. This message documents the size of the buffer pool and can be issued for either EQQCPxDS or EQQTBxDS.

NR is set for EQQPxDS only to store the additional text (REQUESTED nnnnnn); this is the number of buffers tuned on EQQCPxDS size. Depending on the available storage, the number of allocated buffers could be less than the buffers requested.

HCL Workload Automation for Z was unable to build a VSAM LSR buffer pool for the file identified by DDNAME. This message documents the size of the buffer pool that HCL Workload Automation for Z was trying to build and the return code from the build buffer pool service. The message can be issued for either EQQCPxDS or EQQTBxDS.

The normal mode manager (NMM) subtask could not copy the specified file because an error occurred when opening the input or output data sets.

HCL Workload Automation for Z re-creates a current plan by copying the new current plan data set, EQQNCPDS, and updates it using events from the archived job tracking log and from the current job tracking log data set.

HCL Workload Automation for Z successfully deleted the buffer pool for the file indicated in the message.

HCL Workload Automation for Z could not delete the buffer pool for the file indicated in the message.

The normal mode manager (NMM) subtask was reading the job tracking log data set during restart from checkpoint. An abend prevented it from processing the entire data set.

HCL Workload Automation for Z has detected that a new current plan (NCP) has been created by a daily planning batch job, but because HCL Workload Automation for Z failed to create a valid backup of the current plan (CP) to be used as input for the batch job, the NCP is considered invalid and is not used. This message is also issued when the checkpoint data set (EQQCKPT) has not been initialized.

The normal mode manager (NMM) subtask has been requested to copy the specified file, but was unable to do so because the maximum size of records in the output data set is smaller than the maximum size of records in the input data set.

The normal mode manager (NMM) subtask has been requested to copy the specified file, but is unable to do so because of insufficient virtual storage.

The normal mode manager (NMM) subtask has been requested to copy the VSAM data set DDNAME, but is unable to do so because a logical VSAM error occurred.

The normal mode manager (NMM) subtask has been requested to copy the VSAM data set DDNAME, but cannot do so because a VSAM I?O error occurred.

The HCL Workload Automation for Z subsystem or a HCL Workload Automation for Z batch job could not open a VSAM data set.

After opening a VSAM data set (FILE), the VSAM I?O subtask determined that the data set’s attributes did not agree with the I?O subtask’s expectations for this ddname. For example, an incorrect size of the VSAM key could cause this message.

When building a VSAM LSR pool for the file DDNAME, the return code RCODE from BLDVRP macro indicated that the pool had not been built.

The TSO user TSOUSER issued a long-term plan (LTP) refresh request.

This message shows the number of entries contained in the EDP table when it is initialized from the checkpoint data set when the controller starts.

The refresh of the checkpoint data set completed successfully.

HCL Workload Automation for Z tried to allocate storage to build the specified table, but was not able to obtain sufficient storage.

An error occurred while adding the EQQTWSIN entry in the EDP table. The controller detected that the EDP table has reached the number of 1000 entries, which is the maximum allowed.

A HCL Workload Automation for Z subtask encountered an unexpected error when accessing a VSAM data set. The return code, or RC, is always RC = 08 on return to HCL Workload Automation for Z from VSAM. The reason code, or RSN, is the RPL feedback code for logical errors and the ACBERFLG for OPEN/CLOSE.

This message is issued for all successful VSAM requests in the HCL Workload Automation for Z address space when VSAM I?O tracing is active.

A HCL Workload Automation for Z subtask or batch job requested VSAM I?O services incorrectly.

This message is issued for all logical VSAM requests in the HCL Workload Automation for Z address space when VSAM I?O tracing is active.

This message is issued by the VSAM I?O subtask during HCL Workload Automation for Z termination when a HCL Workload Automation for Z subtask ends without closing all of the logical VSAM files that it opened.

An error occurred while creating, extending, or replanning a current plan. The JRUNHISTORY parameter of the BATCHOPT statement is set to (YES,STOP), therefore the batch job tries to create a backup copy of the old current plan to be used later by the archiving process. The copy is not created because of the IDCAMS utility failure.

This message contains additional information for a preceding EQQN043E message. It identifies the HCL Workload Automation for Z subtask that has exclusive control of a VSAM control interval that the current HCL Workload Automation for Z subtask needs.

The normal mode manager (NMM) subtask could not open the job-tracking or extended-auditing log data set DDNAME, which it requires.

A modify current plan (MCP) multiple add request did not complete normally. HCL Workload Automation for Z has canceled the wait for the completing modify request. Operations within such added occurrences may be in held status and must be released manually.

A modify current plan (MCP) multiple add request did not complete normally. HCL Workload Automation for Z has canceled the wait for the completing modify request. Operations within the reported occurrence may be in held status and must be released manually.

The normal mode manager (NMM) subtask has started to copy a current plan data set because either a new current plan has become available or a current plan image copy backup is to be created.

The normal mode manager (NMM) subtask has finished copying a current plan data set.

HCL Workload Automation for Z determined that a CP recovery is required. While this CP recovery is in progress, the scheduler is in a partially initialized state. Users cannot enter the dialogs and no jobs are submitted.

While the CP recovery is in progress, a lot of events are processed from the JT files to update the CP data set.

Keyword WLRSTMT on the JTOPTS statement contains a valid value KEYW, but in an incorrect position.

Keyword WLRSTMT on the JTOPTS statement contains too many values.

Keyword WLRSTMT on the JTOPTS statement contains a value KEYW, which is not recognized by HCL Workload Automation for Z.

There was an error while the NMM subtask was copying the current plan VSAM file to the EQQSCPDS VSAM file during the Symphony file creation process.

The NMM subtask failed to send the event shown in the message text to the end-to-end task for an unknown reason.

The user submitted a Symphony Renew batch job but the NMM subtask found that there is no active current plan.

You issued a modify command with the LSTNOERR option, to list the NOERROR table content. The NOERRROW variable shows a currently active NOERROR definition; the NOERRMEM variable shows the name of the EQQPARM member containing that definition.

While defining a new NOERROR entry TABROW1, the scheduler detected that it overlaps the already defined entry TABROW2.

While defining a new NOERROR entry TABROW1, the scheduler detected that it is not consistent with the already defined entry TABROW2.

An invalid keyword value has been defined.

A modify command was entered requesting the NOERROR table to be updated. One or more errors were found while processing input NOERROR statements.

A modify command has caused HCL Workload Automation for Z to rebuild the NOERROR table from NOERROR statements in the parameter library.

You issued a modify command to modify the list of protected data sets but the OPCOPTS RCLEANUP option is not set toYES.

You issued a modify command to modify the list of protected data set but the RCLOPTS option was not specified or built with defaults.

You issued a modify command to modify the list of protected data set via DDNAME providing a blank value for DDNAME member. For example, /F subsys,DDPROT(). An empty member name removes the current list of protected data sets.

You issued a modify command to modify the list of protected data set via DSNAME providing a blank value for DSNAME member. For example, /F subsys,DSNPROT(). An empty member name removes the current list of protected data sets.

You issued a modify command to modify the list of protected data set via DDNAME providing a new value for DDNAME member. For example, /F subsys,DDPROT(newmem). The newmem member is read and used to substitute the current list of protected data set via DDNAME.

You issued a modify command to modify the list of protected data sets via DSNAME providing a new value for DSNAME member. For example, /F subsys,DSNPROT(newmem) The newmem member is read and used to substitute the current list of protected data set via DSNAME.

At least one of the two parameters of the ALEACTION keyword is either out of range or was specified not using 3 digits. The default value is used.

The job-tracking log archiver task has completed initialization and is ready to perform additional work.

The job-tracking log archiver task is ending normally after having been posted to stop processing.

HCL Workload Automation for Z was unable to use the next job-tracking or extended-auditing log data set in a situation where the current log can no longer be used.

The value specified for the JTLOGS keyword is not supported.

A DD statement needed to support currently specified (or defaulted) values of the JTLOGS and DUAL keywords of the JTOPTS initialization statement is not defined.

The value specified for the JTLOGS keyword of the JTOPTS initialization statement is smaller than the number of the current job-tracking log. This is not supported.

The value specified for the JTLOGS keyword of the JTOPTS initialization statement is smaller than the number of the first nonarchived job-tracking log. This is not supported.

During HCL Workload Automation for Z restart it was determined that the dual job-tracking log contains more events that the primary log. This could indicate that the primary log data set is invalid.

HCL Workload Automation for Z was unable to use the next job-tracking or extended-auditing log data set in a situation where current log can no longer be used.

The scheduler did not find any NOERROR definition while processing a modify command, /F subsys,LSTNOERR.

The job-tracking log archiver task has successfully copied a data set to the archive data set.

An error prevented the job-tracking log archiver task from copying a job-tracking log data set to the archive data set.

An I/O error occurred when the job-tracking log archiver task tried to write a log record to the job-tracking archive log data set.

An abend occurred when the job-tracking log archiver task tried to write a log record to the job tracking archive log data set. If the abend code is SB37 or SD37, the archive data set is too small.

An I/O error occurred when a HCL Workload Automation for Z function tried to write a log record to the currently active dual job-tracking log file.

An abend occurred when a HCL Workload Automation for Z function attempted to write a record to a dual job-tracking log data set. If the abend code is SB37 or SD37, the current dual job-tracking log data set is too small.

While defining a new NOERROR entry TABROW1, the scheduler detected that it duplicates already defined criteria.

The scheduler tried to access the UX14IN data set but failed.

The NOERROR consistency check detected some inconsistent statements.

The scheduler normally processed a modify command /F subsys,TRYNOERR(mem_name .

HCL Workload Automation for Z could not locate the modify current plan load module, EQQMCTOP.

HCL Workload Automation for Z could not locate an exit load module.

HCL Workload Automation for Z could not locate the event handler load module, EQQEMEVH.

HCL Workload Automation for Z has passed job tracking log information to Exit011, but unusual conditions (including errors) have been encountered.

The HCL Workload Automation for Z checkpoint data set indicates that no valid current plan exists. All HCL Workload Automation for Z functions that need access to the current plan data set are inoperative.

While processing initialization statements, the normal mode manager (NMM) subtask found one or more errors.

The normal mode manager (NMM) subtask is ending normally after having initialized successfully. Usually, this message is due to an operator command requesting the HCL Workload Automation for Z subsystem to stop.

The normal mode manager (NMM) subtask found that a new current plan (NCP) in the NCP data set did not contain any header record.

HCL Workload Automation for Z has passed job tracking log information to Exit011, but an abnormal condition has been encountered. This condition has caused an abnormal termination for Exit011.

A turnover process was just completed and a request was built to remove the completed occurrence related information from the Restart and Cleanup data store. However, the FL task that should process the request is not active.

The batch job has successfully created the symnew file. This file is a new version of the symphony file and is created by daily planning. It becomes active when translator renames the existing symphony file to symold and the symnew file to symphony.

The batch job was unable to renew the Symphony file.

Your TWS subsystem runs without the end- to- end features defined, the keyword TPLGYSRV on OPCOPTS parameter not specified, but exists a workstation on CP defined as a Fault-tolerant workstation.

The TWSJOBNAME parameter in the JTOPTS statement is set to EXTNAME, EXTNOCC or JOBNAME, but the record length of the EQQTWSOU data set is 120 bytes. This behaviour is not supported: in order to select a value different from the default OCCNAME for the TWSJOBNAME parameter, you have to migrate the EQQTWSOU data set using sample EQQMTWSO; this sample increase the data set record length to 160 bytes.

The daily planning job is creating a new current plan (NCP). The normal mode manager (NMM) controller subtask is waiting for the process to complete.

The daily planning job finished to create a new current plan (NCP).

The controller started synchronizing with the server during a daily planning activity.

The current plan backup created the SCP file, which is a copy of the current CP.

HCL Workload Automation for Z could not locate the load module EQQZVGSU for the variable substitution function in the system automation command.

The batch job completed the NCP creation phase. The NCP might have been created if the batch ended successfully. If so, the message EQQN118I follows.

The current plan backup for the creation of the Symphony file was created.

A Symphony renew activity was started by a batch job.

The controller received a request to start a new bulk discovery when a bulk discovery is already in progress.

The controller was restarted with JTOPTS CURRPLAN(NEW) specified. This means that during recovery to restore the current plan, the NCP VSAM file is used, with the job-tracking logs archived in the JTARC file. However, the controller detected that this NCP file had not been copied to the CP1 and CP2 VSAM files during the previous controller run. The checkpoint data set indicates that this NCP file was not taken by the controller: OPCTUNCP field is set to H. To prevent reapplying of old events, ensure that you have taken the manual actions described in the User response.

An error occurred during the submission synchronization processing for the HCL Workload Automation Agent workstations.

An error occurred while adding the EQQHTTP0 entry in the EDP table. The controller detected that the EDP table has reached the number of 1000 entries, which is the maximum allowed.

An error occurred that caused the late tie adding routine to fail.

An error occurred that caused the late tie deletion routine to fail.

With the support of extended VSAM files for the JS files, the unit of measure for the MAXJSFILE parameter has been modified from kilobytes to megabytes.

An error occurred while the bind requests coming from a remote engine and in pending status were being processed. The bind requests are put in pending state when they need to wait for a current plan extension, a long-term plan extension, or a lock on long-term plan to be available. These pending requests are processed each time a new plan is put in production, that is when you replan or extend the current plan.

The backup controller received a synchronization answer from the primary controller, but there was no synchronization process in progress. The answer is ignored.

An I/O error trying to read the backup checkpoint data set occurred while the controller was processing a JT event.

The primary controller tried to transfer the data set identified by FILE to the backup controller but the transfer failed. The job used to run the transfer is identified by JOBNAME JOBID.

The backup controller received a message that a restore for the file identified by FILE was started and completed. The job used to run the restore is identified by JOBNAME JOBID. Because there is no synchronization process in progress, the information is ignored.

The primary controller tried to transfer the data set identified by FILE to the backup controller but the restore failed. The job used to run the restore is identified by JOBNAME JOBID.

Because the BKPTOPTS statement is set, the SSX must be consistent with it.

The CP on the primary controller is older than the CP on the backup controller (either the run number or the last processed JT seqno is lower). This is not allowed and the backup controller stops.

The primary controller tried to transfer the data set FILE by running the job PROCN but the connection with the backup controller is down.

The primary controller detected a JT seqno disalignment with the backup controller, but JT could not be sent again because it was not found in the current JT.

The modify command /F subsys,BKTAKEOVER was issued when the primary and backup controllers were still connected. This is not allowed.

The backup controller detected a JT seqno disalignment with the primary controller. The last JT event received by the backup controller is identified by TYP1 and seqno SEQN1, while the last JT event written by the primary controller is identified by TYP2 and seqno SEQN2.

At startup, the checkpoint data set reported that the latest archived JT and current JT are the same: this is not allowed.

While checking the content of the JT and CP, the Z controller started a plan backup before reapplying the JT. This message is usually preceded by message EQQN183I or EQQN184I.

While checking the content of the JT and CP, the Z controller evaluated necessary to start a current plan backup and JT reapply: the last record in the JT data set was not related to a CP backup. This message is usually issued together with message EQQN182I.

While checking the content of the JT and CP, the Z controller evaluated necessary to start a JT reapply: an event in the JT data set was dated later that the latest CP backup performed. This message is usually issued together with message EQQN183I.

At startup, the backup controller detected that the JT events were to be reapplied to the plan. Reapplying JT events at startup is not allowed for a backup controller.

The controller tried to open the current JT data set but an error occurred. The JT ddname is JTDD.

The primary controller updated the logical file LOGDB on VSAM data set SBDDB, but these changes were not received by the backup controller.

The modify command /F subsys,BKTAKEOVER was issued when a synchronization process was in progress. The type of synchronization is indicated by the value SYNCTYP. The status of the affected data sets is shown by NCPS, CP1S, CP2S, and LTPS.

The modify command /F subsys,BKTAKEOVER was issued when a JT synchronization process was in progress. This means that some JT events might be lost.

The modify command /F subsys,BKTAKEOVER was issued when a plan synchronization process was in progress. The backup controller requested the CP and LTP data sets, but only LTP was received and restored. This means that the plans are disaligned, therefore the BKTAKEOVER command cannot be run and the backup controller waits for you to perform the manual actions indicated by the EQQN212I message that follows.

The modify command /F subsys,BKTAKEOVER was issued when a plan synchronization process was in progress. The backup controller requested the CP and LTP data sets, but only CP was received and restored. This means that the plans are disaligned, therefore the BKTAKEOVER command cannot be run and the backup controller waits for you to perform the manual actions indicated by the EQQN212I message that follows.

The modify command /F subsys,BKTAKEOVER was issued when the long-term plan is not available. This message is followed by message EQQN213W BKTAKEOVER COULD NOT BE EXECUTED: BACKUP CONTROLLER IS STOPPED.

This message is issued when you entered the modify command /F subsys,BKTAKEOVER or when a synchronization process completed. The LTP data set shows a TOD value earlier than the TOD for the CP data set, meaning that the LTP has been produced before the latest DP batch run.

A possible reason is that after a DP batch run on the primary controller, the backup controller received only the CP data set. Therefore the LTP is older than the CP.

This message is issued when you entered the modify command /F subsys,BKTAKEOVER or when a synchronization process completed. The LTP data set shows a plan end that is not compatible with the current plan.

A possible reason is that after a DP batch run on the primary controller, the backup controller received only the CP data set. Therefore the LTP is older than the CP.

The job submission is deactivated. This message is usually shown after you issued the modify command /F subsys,BKTAKEOVER while the synchronization process was in progress.

When the synchronization process completed, the system detected that the current plan previously used had a backup date and time more recent than the latest restored current plan.

When you issued the modify command /F subsys,BKTAKEOVER the current plan was not available. This message is followed by message EQQN213W BKTAKEOVER COULD NOT BE EXECUTED: BACKUP CONTROLLER IS STOPPED.

The modify command /F subsys,BKTAKEOVER cannot be completed because some manual actions are required, as described in the EQQN212I messages that are shown (see also User response).

You issued the modify command /F subsys,BKTAKEOVER when a plan synchronization process was in progress. The backup controller did not receive any answer from the primary controller.

You issued the modify command /F subsys,BKTAKEOVER when a DP batch plan extend synchronization process was in progress. The backup controller did not receive any NCP data set.

The NMM task could not open the internal reader data set identified by the DD statement EQQBR2DS. NMM needs to open the internal reader to start a transfer or restore procedure. PROB identifies the specific problem occurred.

The value specified for RISKCONFIDENCE is not allowed. Valid values are 1-99.

The extended auditing feature has been deactivated, because the extended-auditing-archive data set has accumulated too much data.

See message text.

JTEVENTS

Number of JT events that accumulated from the start of turnover (including MCP events).

MCPEVENTS

Number of MCP events accumulated from the start of turnover.

MCPTIME

Time spent in executing the accumulated MCP events, expressed in hundredths of seconds.

01

WSSYSAFF is not set to any value, for example WSSYSAFF().

02

A value is set for system.destination but not for the corresponding wsname. The correct syntax isWSSYSAFF(wsname:sysname.destination).

03

There is not enough storage to allocate buffer for the system.destination information related to the wsname.

04

The value set for wsname is not correct, either because length is 0 or exceeding the maximum size (4 characters).

05

There is not enough storage to allocate buffer for the system.destination information related to the wsname. The affected workstation is the last in the list.

06

There is not enough storage to allocate buffer for the list of workstations specified.

07

The definition for the workstation identified by wsname is duplicated. This is not allowed.

08

A value set for the sysname.destination information related to wsname has incorrect length.

10

The workstation name specified starts with a number: this is not allowed.

• WSNAME=wsname
• WSSYSNAME=system DESTINATION=destination

For example, if you set JTOPTS WSSYSAFF(VIRT:SYSA.D1,SYSB.D2,SYSC.D3) and workstation VIRT is a virtual workstation with destinations D1 and D2, at job submission the SYSAFF parameter of the job card will always include system SYSC because destination D3 cannot be checked for any workstation-open interval. Systems SYSA and SYSB, instead, are subject to the shutdown policy check and will be included depending on the check result.