EQQN000 - EQQN254

EQQN000I

THE NORMAL MODE MANAGER TASK HAS BEEN REQUESTED TO TERMINATE

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.

The NMM subtask waits for all subtasks to end. When there are no more active subtasks, the NMM backs up the current plan data set and terminates.

None.

If the NMM subtask has not ended within a few minutes, there may be a problem in one of the subtasks that prevents it from ending normally. If the problem cannot be resolved, cancel the subsystem started subtask and request a dump.

EQQN001I

REFRESH IS COMPLETE. CURRENT PLAN IS NO LONGER AVAILABLE

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.

All HCL Workload Automation for Z functions that do not need access to the current plan continue processing.

Schedule a batch job to create a new current plan using only long-term plan information as input.

EQQN002E

THE NMM SUBTASK WAS UNABLE TO READ OR UPDATE CURRENT PLAN OPERATION RECORD WITH KEY (HEXADECIMAL): F0F3OPRINDEX

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.

The current job tracking event record is not processed. The NMM subtask continues reading the job tracking log data set.

Save the message log data set containing this error message and the job tracking log data set containing the incorrect record. Contact the Customer Support.

Review the preceding messages in the HCL Workload Automation for Z message log and SYSLOG data sets to determine the cause of the error.

EQQN003E

VSAM ABENDED WHILE ATTEMPTING TO CLOSE DDNAME FILE. FOR ADDITIONAL INFORMATION SEE SYSLOG MESSAGES AND DUMP DATA SET

A severe error occurred while closing a VSAM file.

A dump is generated. The I/O subtask attempts to continue normal termination processing.

Save the HCL Workload Automation for Z message log and dump data sets. To collect appropriate documentation for problem determination, see the problem analysis procedures described in theDiagnosis Guide and Reference manual. Search the IBM Support database for a solution at Support.

Describe the scenario that caused the error.

Review earlier messages in the HCL Workload Automation for Z message log, SYSLOG, and dump data sets to determine what caused the close abend.

EQQN004E

VSAM PHYSICAL I/O ERROR. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK. LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME VSAM RETURN CODE IS 12, REASON CODE IS RSN, KEY IS KEY VSAM MESSAGE: SYNAD

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

The action taken by the HCL Workload Automation for Z subtask or batch job is given by additional messages that follow this message in the HCL Workload Automation for Z message log. The VSAM message supplies information such as jobname, stepname, unit address, device type, ddname, RBA, error description and so on.

Correct the errors and, if necessary, rerun the batch job or restart the HCL Workload Automation for Z subsystem.

The MSGAREA and MSGGEN parameters of the RPL macro are used to extract the relevant information presented in the VSAM message. Use the VSAM return code, reason code, and message to determine the cause of the error. For more information, refer to the appropriate documentation for the MVS/DFP product installed on this z/OS system.

EQQN005E

THE NORMAL MODE MANAGER SUBTASK HAS ABENDED. FOR ADDITIONAL INFORMATION SEE SYSLOG MESSAGES AND DUMP DATA SET

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

NMM processing is terminated. A dump is created if a dump data set is defined. Message EQQZ045W is issued.

Save the message log data set containing this error message, the dump data set, and the SYSLOG data set. To collect appropriate documentation for problem determination, see the problem analysis procedures described in the Diagnosis Guide and Reference manual. Search the IBM Support database for a solution at Support.

Describe the scenario that caused the error.

Review the preceding messages in the HCL Workload Automation for Z message log, SYSLOG, and dump data sets to determine what caused the NMM subtask to abend.

EQQN006E

THE NORMAL MODE MANAGER HAS IGNORED THE FOLLOWING INVALID EVENT RECORD WHILE PROCESSING THE JOB TRACKING LOG DATA SET DURING RESTART FROM CHECKPOINT: EXITREC

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.

The incorrect job tracking event record is not processed. The normal mode manager (NMM) subtask continues reading the job tracking log data set.

Save the HCL Workload Automation for Z message log data set containing this error message and the job tracking log data set containing the incorrect record. Contact the Customer Support.

Note the job name and job number in the exit record. If necessary, set the correct status for this job manually.

EQQN007E

THE FOLLOWING INVALID RECORD WAS ENCOUNTERED WHEN THE NORMAL MODE MANAGER WAS PROCESSING THE JOB TRACKING LOG DATA SET DURING RESTART FROM CHECKPOINT: EVENT HEADER: EVNTHDR EVENT RECORD: EXITREC

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.

The incorrect job tracking event record is not processed. The NMM subtask continues reading the job tracking log data set.

Save the HCL Workload Automation for Z message log data set containing this error message and the job tracking log data set containing the incorrect record. Contact the Customer Support.

Note the job name and the job number in the exit record. If necessary, set the correct status for this job manually.

EQQN008E

AN ABEND OCCURRED WHILE PROCESSING THE JOB TRACKING LOG DATA SET DURING RESTART FROM CHECKPOINT. THE TRACKLOG RECORD HAS BEEN SKIPPED

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.

z/OS recovery/ termination is requested to generate a dump. The NMM subtask attempts to continue normal operation with the next queued event.

Save the HCL Workload Automation for Z message log data set containing this error message and the job tracking log data set containing the incorrect record. Contact the Customer Support.

Note the job name and the job number in the exit record. If necessary, set the correct status for this job manually.

Review the HCL Workload Automation for Z message log, SYSLOG, and dump data sets to determine the cause of the error.

EQQN009E

THE CHECKPOINT DATA SET, DDNAME DDNAME, COULD NOT BE OPENED.

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.

The controller stops.

Check that ddname is correctly specified and that it is correctly allocated.

Contact your system programmer.

EQQN010E

AN I/O ERROR OCCURRED WHILE ATTEMPTING TO UPDATE THE CURRENT JOB TRACKING LOG DATA SET. SYNAD MESSAGE FOLLOWS: SYNMSG FIRST 90 BYTES OF LOG RECORD FOLLOWS: LOGREC

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.

HCL Workload Automation for Z attempts to switch to the next job tracking log file. If this process is successful, the log record is written to the next log instead. The normal mode manager (NMM) subtask is posted to take a backup of the current plan.

Scrap and reallocate the job tracking log data set at a suitable time when HCL Workload Automation for Z is stopped.

Contact your system programmer.

The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product installed on this system.

EQQN011E

A SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE CURRENT JOB TRACKING LOG DATA SET

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.

HCL Workload Automation for Z attempts to switch to the next job tracking log file. If this process is successful, the log record is written to the next log instead. The normal mode manager (NMM) subtask is posted to take a backup of the current plan.

If the current job tracking log data set is too small, scrap the current data set and allocate a larger one at a suitable time when HCL Workload Automation for Z is stopped. Refer to Customization and Tuning for instructions.

Contact your system programmer.

EQQN012I

JOB TRACKING EVENTS ARE NOW BEING LOGGED ON FILE DDNAME

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.

Normal HCL Workload Automation for Z processing continues.

None.

EQQN013I

JOB TRACKING IS NOW ACTIVE AND CURRENT PLAN DD-NAME IS DDNAME

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

Normal HCL Workload Automation for Z processing continues.

None.

EQQN014I

THE JOB TRACKING LOG DATA SET, DDNAME JTFILE, HAS BEEN USED TO UPDATE THE CURRENT PLAN. NUMBER EVENTS HAVE BEEN APPLIED TO DD-NAME DDNAME

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.

Normal HCL Workload Automation for Z processing continues.

None.

EQQN015I

A VSAM DATA SET WAS SUCCESSFULLY COPIED: FROMDD=FROMDD, TODD=TODD

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

Normal HCL Workload Automation for Z processing continues.

None.

EQQN016I

DDNAME OF CURRENT JCL REPOSITORY DATA SET IS DDNAME

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

HCL Workload Automation for Z processing continues.

None.

EQQN017I

THE JCL REPOSITORY DATA SET WILL BE COPIED

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.

HCL Workload Automation for Z processing continues.

None.

EQQN018I

VSAM LSR BUFFERS HAVE BEEN SUCCESSFULLY ALLOCATED FOR VSAM FILE DDNAME NUMBER OF INDEX BUFFERS ARE NINDEX WITH SIZE SINDEX NUMBER OF DATA BUFFERS ARE NDATA WITH SIZE SDATA NR

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 continues and uses the new buffer pool for I/O to the file.

None.

If necessary, verify that the size of the buffer pool is adequate.

EQQN019E

VSAM LSR BUFFER ALLOCATION FAILED FOR VSAM FILE DDNAME RETURN CODE FROM BLDVRP WAS VRPRC REQUESTED NUMBER OF INDEX BUFFERS WAS NINDEX WITH SIZE SINDEX REQUESTED NUMBER OF DATA BUFFERS WAS NDATAWITH SIZE SDATA

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.

HCL Workload Automation for Z continues and uses normal VSAM buffering techniques for the file. The message EQQN019E is captured by the alerts OPCERROR() function and is issued to the system console and / or captured by NetView, if so specifed.

Correct the error and restart HCL Workload Automation for Z.

Use the VSAM return code to determine the cause of the error. For more information, refer to the appropriate documentation for the MVS/DFP product installed on this z/OS system.

EQQN021E

VSAM FILE FILE COULD NOT BE COPIED BECAUSE INPUT OR OUTPUT DATA SET COULD NOT BE OPENED

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

The NMM subtask is terminated.

Correct the errors and, if necessary, restart the NMM subtask.

Review earlier messages in the HCL Workload Automation for Z message log to determine the exact reason for this message.

EQQN022I

A CURRPLAN(NEW) RESTART REQUEST IS BEING PROCESSED. THE SCHEDULER WILL START FROM THE NEW CURRENT PLAN DATA SET, DDNAME=EQQNCPDS, AND APPLY EVENTS FROM THE ARCHIVED JT LOG DATA SET, DDNAME=EQQJTARC

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.

The HCL Workload Automation for Z restart process continues.

None.

EQQN023I

VSAM LSR BUFFERS HAVE BEEN SUCCESSFULLY DELETED FOR VSAM FILE DDNAME

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

None.

None.

EQQN024W

VSAM LSR BUFFER DELETE FAILED FOR VSAM FILE DDNAME RETURN CODE FROM DLVRP WAS VRPRC

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

None.

Use the return code to determine the cause of the error and take appropriate action.

Use the VSAM return code to determine the cause of the error. For more information, refer to the appropriate documentation for the MVS/DFP product installed on this z/OS system.

EQQN025E

AN ERROR OCCURRED WHILE READING THE JOB TRACKING LOG DATA SET DURING RESTART FROM CHECKPOINT. THE DATA SET HAS BEEN TRUNCATED

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.

z/OS recovery/termination is requested to generate a dump. The NMM subtask tries to complete the restart by treating the error as an end-of-file on the log data set.

Save the message log data set containing this error message and the job tracking log data set causing the error. Contact Customer Support.

Review the status of all operations in the current plan. If necessary, set the correct statuses manually.

Review the HCL Workload Automation for Z message log., SYSLOG, and dump data sets to determine the cause of the error.

EQQN026W

A NEW CURRENT PLAN (NCP) HAS BEEN REJECTED

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.

HCL Workload Automation for Z starts up with the CP that was in use before HCL Workload Automation for Z was terminated. If the EQQCKPT data set has been reallocated, HCL Workload Automation for Z does not permit current plan actions as the old CP cannot accurately be identified.

Ensure that both the CP1 and CP2 data sets are online and available for HCL Workload Automation for Z. Rerun the daily plan batch job, to create a new NCP. If the EQQCKPT data set has been reallocated specify the JTOPTS keyword CURRPLAN(NEW) option and restart the HCL Workload Automation for Z subsystem.

Review the message log from the previous HCL Workload Automation for Z startup and look for error messages that could explain why the backup process failed. If the HCL Workload Automation for Z backup process failed due to an open error, the reason could be that another job was using the file.

EQQN027E

THE NORMAL MODE MANAGER IS TERMINATING UNEXPECTEDLY. NMMSTAT IS NMMSTAT

The normal mode manager (NMM) subtask is in the processing of terminating unexpectedly. The reason for the termination is documented by NMMSTAT, which can have the following values:
E
An I/O error has occurred
A
Virtual storage is exhausted
S
Termination is requested by another HCL Workload Automation for Z function.

NMM terminates all related subtasks. HCL Workload Automation for Z continues to execute, but when the NMM subtask has terminated current plan functions are not available.

Analyze the preceding messages and take appropriate action to prevent the NMM subtask from terminating. To reactivate NMM, issue the command F ssnm,S=NMM.

Contact your system programmer.

Review the HCL Workload Automation for Z message log (EQQMLOG) for preceding error messages that describe the problem.

EQQN028E

CANNOT COPY VSAM FILE INFILE TO FILE FILE MAXIMUM OUTPUT RECORD SIZE IS SMALLER THAN MAXIMUM INPUT RECORD SIZE

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 NMM subtask is terminated. Message EQQZ045W is issued.

Reallocate the output data set so that it has the same maximum record length as the input data set and retry.

EQQN029E

CANNOT COPY VSAM FILE FILE. BUFFER GETMAIN FAILED

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 NMM subtask is terminated. Message EQQZ045W is issued.

Stop HCL Workload Automation for Z and restart it in a larger region.

EQQN030E

ERROR COPYING VSAM FILE. DDNAME = DDNAME, VSAM RC = RC, REASON = RSN

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 VSAM copy process is stopped.

Correct the errors and, if necessary, restart the NMM subtask.

Use the VSAM return code and reason code to determine the cause of the error. For more information, refer to the appropriate documentation for the MVS/DFP product installed on this z/OS system.

EQQN031E

I/O ERROR COPYING VSAM FILE. DDNAME = DDNAME, VSAM MSG FOLLOWS ERRMSG

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 VSAM copy process is stopped.

Correct the errors and, if necessary, restart the NMM subtask.

Use the VSAM error message to determine the cause of the error. For more information, refer to the appropriate documentation for the MVS/DFP product installed on this z/OS system.

EQQN032E

UNABLE TO OPEN VSAM FILE FILE, VSAM RC = RC, REASON = RSN

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

The messages that follow this message in the message log identify the action taken by the subsystem or the batch job.

Correct the error and restart the HCL Workload Automation for Z subsystem or batch job.

Use the VSAM return code and reason code to determine the cause of the error. For more information, refer to the appropriate documentation for the MVS/DFP product installed on this z/OS system.

EQQN033E

VSAM FILE FILE IS INVALIDLY DEFINED

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.

The VSAM file is not opened.

Correct the errors and restart HCL Workload Automation for Z.

Check that the file is correctly specified in the HCL Workload Automation for Z started task procedure. Use the IDCAMS LISTCAT function to determine the attributes of the file. Check that the relative key position is zero and that the key size is the same as that defined in the Planning and Installation

EQQN034E

DAILY PLAN ENDS AFTER FAILURE TO BUILD VSAM LSR POOL, MACRO BLDVRP FAILED WITH RC=RCODE FOR DDNAME=DDNAME

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 daily planning job is ended without creating a new current plan.

For return code = 0008, make sure that enough virtual storage is available. Review the REGION parameter in conjunction with the limits in the IEALIMIT/IEFUSI exit. Rerun the daily planning job.

For other return codes, save the message log containing the error and contact Customer Support.

For return code = 0008, the request could not complete due to lack of virtual storage. The daily planning job allocates 100 times 32 KB VSAM LSR buffers, for the new current plan VSAM file, above 16 MB. For other return codes this is probably a system error.

EQQN035I

REFRESH REQUEST ISSUED BY TSOUSER

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

HCL Workload Automation for Z processing continues.

None.

EQQN036I

THE EDP TABLE WAS INITIALIZED WITH NODES ENTRIES

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.

HCL Workload Automation for Z PROCESSING CONTINUES.

If the number is close to the maximum allowed, 1000 entries, and it is much greater than the number of remote destinations defined in the ROUTOPTS, refresh the checkpoint data set from the old entries at next CP extend or replan. To do this, specify the CKPTREFRESH keyword with value YES in the BATCHOPT.

EQQN037I

THE EDP TABLE AND THE CKPT DATASET WERE REFRESHED

The refresh of the checkpoint data set completed successfully.

HCL Workload Automation for Z processing continues.

None.

EQQN038E

INSUFFICIENT STORAGE TO BUILD THE TABLE TABLE

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

HCL Workload Automation for Z initialization is terminated.

Check the region size defined in the HCL Workload Automation for Z JCL procedure. Increase the region size and restart HCL Workload Automation for Z.

EQQN039E

UNABLE TO ADD EQQTWSIN DATASET ENTRY IN EDP TABLE

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.

The controller initialization fails and a user abend is generated.

Remove the TPLGYPRM keyword in the BATCHOPT statement and the TPLGYSRV in the OPCOPTS; then refresh the checkpoint data set, running a daily plan extend or replan batch job after specifying the CKPTREFRESH keyword with value YES. When the batch job completes, restore the keywords previously removed.

EQQN040I

SKIPINCL LIST HAS BEEN ACTION

The modify command:
/F subsys,SKIPINC(member name)
was successfully processed. This command acts on the list of INCLUDE statements that are to be skipped in the JCL tailoring process (see the RCLOPTS SKIPINCL parameter section in the Customization and Tuning manual for details). The type of action performed by the command is specified by the value of ACTION and can be one of the following:
  • Removed
  • Updated

The list of INCLUDE statements to be skipped is removed or updated. HCL Workload Automation for Z processing continues.

None.

EQQN041E

SKIPINCL LIST CAN BE UPDATED ONLY IF RCLEANUP=YES

The modify command:
/F subsys,SKIPINC(member name)
could not be processed because it has significance only when the Restart and Clean Up fuction is active.

HCL Workload Automation for Z processing continues.

Check if RCLEANUP=NO is the intended setting. If it is not, set RCLEANUP=YES and check that all Restart and Clean Up customization is valid.

EQQN043E

UNSUCCESSFUL VSAM I/O REQUEST. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK. LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME VSAM RETURN CODE IS 8, REASON CODE IS RSN, KEY IS KEY HEXADECIMAL ZONES HEXKEYZ HEXADECIMAL DIGITS HEXKEYD

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.

The messages that follow this message in the HCL Workload Automation for Z message log indicate the action taken by the HCL Workload Automation for Z subtask.

Correct the error and, if necessary, restart the subtask that encountered the error.

Attention:
  1. Specific corrective action must be taken for the following reason codes:
    RSN=28
    DATASET CANNOT BE EXTENDED

    Make additional space available and then stop and restart the controller to force the affected data set to be closed and reopened.

    RSN=40
    INSUFFICIENT VIRTUAL STORAGE

    Increase the region available to the HCL Workload Automation for Z controller started task.

  2. This message can also be caused by a concurrent DELETE action on the CP that was run by a user at the same time of the query. If this is the case, the I/O Error is only a normal consequence of this.

Look up the reason code for the requested function in the documentation for the MVS/DFP product installed on the system (the VSAM Instruction Reference books contain a good description of the return and reason codes). If this error condition cannot be reproduced, consider activating a VSAM I/O trace to check preceding VSAM requests that led up to the error.

Note: Activating an I/O trace causes a large amount of output on the message data set.

EQQN044I

A VSAM I/O REQUEST COMPLETED SUCCESSFULLY. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK. LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME KEY OF VSAM RECORD IS KEY HEXADECIMAL ZONES HEXKEYZ HEXADECIMAL DIGITS HEXKEYD

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.

Processing continues.

None.

EQQN045E

INCORRECT VSAM I/O REQUEST. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK. LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME ERROR CAUSE IS: CAUSE

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

The messages that follow this message in the HCL Workload Automation for Z message log indicate the action taken by the HCL Workload Automation for Z subtask or batch job.

Save the message log containing this error message and the SYSLOG data set. To collect appropriate documentation for problem determination, see the problem analysis procedures described in the Diagnosis Guide and Reference. Search the IBM Support database for a solution at Support.

Describe the scenario that caused the error.

Review earlier messages in the HCL Workload Automation for Z message log and SYSLOG data set.

EQQN046I

A LOGICAL VSAM FILE OPERATION WAS COMPLETED. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK. LOAD MODULE IS MODULE REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME

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.

Processing continues.

None.

EQQN047W

SUBTASK TASK HAS TERMINATED WITHOUT CLOSING LOGICAL FILE FILE, DDNAME DDNAME. VSAM MAY BE UNABLE TO CLOSE THIS FILE

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.

The I/O subtask attempts to close the VSAM file.

Contact Customer Support.

This message usually indicates that the subtask has terminated abnormally.

EQQN048E

IDCAMS REPRO UTILITY FAILED TO COPY FROM FROMDD TO TODD.

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.

The daily planning batch job fails.

If the problem persists save the HCL Workload Automation for Z message log and the DP Extend message log. To collect appropriate documentation for problem determination, see the problem analysis procedures described in theDiagnosis Guide and Reference manual. Search the IBM Support database for a solution at Support.

Review the message log data set for further error messages. Remove the cause of each error and submit the daily planning batch job again.

EQQN049I

EXCLUSIVE CONTROL VSAM ERROR, RETCODE 8, REASON CODE 0020, WAS CAUSED BY A RESOURCE CONFLICT WITH SUBTASK TASK

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.

Processing continues.

Save the HCL Workload Automation for Z message log data set containing this message and contact the Customer Support.

EQQN050E

A DSTYPE LOG DATA SET, DDNAME DDNAME, COULD NOT BE OPENED

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

The NMM is terminated. Message EQQN107I is issued.

Correct the errors and restart HCL Workload Automation for Z.

Check that ddname DDNAME is correctly specified and that the HCL Workload Automation for Z started task is authorized to open the data set for output.

EQQN051I

A CURRENT PLAN BACKUP PROCESS HAS STARTED. TRIGGER WAS: REASON

The normal mode manager (NMM) subtask has started updating a current plan data set in preparation for the creation of a current plan image copy backup. The reason why HCL Workload Automation for Z has initiated the backup is identified by the REASON defined in the message text. The possible values for REASON are:
BACKUP LIM
The number of events specified in the JTOPTS BACKUP keyword has been reached
BACKUP CMD
The backup was initiated as a result of the HCL Workload Automation for Z BACKUP command
BULKDISC CMD
The HCL Workload Automation for Z BULKDISC command initiated a bulk discovery request
CATCH UP
HCL Workload Automation for Z has successfully recovered the current plan using job-tracking data
JT ERROR
An error on a job-tracking log has caused HCL Workload Automation for Z to switch to the next available JT log
NMM ENDING
The controller has been requested to shutdown or the NMM subtask has been requested to stop
DP START
Daily plan turnover phase 1, a daily plan batch extend, replan, trial, or print current period results process has been started
DP END
Daily plan turnover phase 2, a daily plan extend or replan has created a new current plan that is being taken over by HCL Workload Automation for Z
UNKNOWN
Please take a copy of the EQQJTARC and the EQQMLOG data sets and report to IBM Software Support.

Backup processing continues. Current plan activity is suspended until the backup is complete.

None.

EQQN052W

AN OUTSTANDING MCP MODIFY REQUEST HAS BEEN CANCELLED FOR USER USER REASON IS: REASON. LIST OF AFFECTED OCCURRENCES FOLLOW:

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.

The wait for the modify request has been canceled.

EQQN053W

OCCURRENCE OCCID WITH IA IADATE IATIME MAY CONTAIN HELD OPERATIONS

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 wait for the modify request has been canceled.

EQQN056I

A CURRENT PLAN COPY PROCESS HAS STARTED

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.

Processing continues.

None.

EQQN057I

A CURRENT PLAN DATA SET WAS SUCCESSFULLY COPIED: FROMDD=FROMDD, TODD=TODD

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

Processing continues.

None.

EQQN058I

THE SCHEDULER WILL RECOVER THE CP DATA SET FROM THE JTLOGS. PLEASE BE PATIENT. THIS WILL TAKE A WHILE.

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.

Processing continues.

None.

EQQN059I

JT APPLY IS IN PROGRESS. NUMBER RECORDS HAVE BEEN PROCESSED

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

Processing continues.

None.

EQQN060E

INVALID KEYW KEYWORD VALUE POSITION IN THE WLRSTMT KEYWORD

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

The normal mode manager (NMM) subtask is terminated.

Correct the error and restart the NMM subtask or the HCL Workload Automation for Z subsystem. Refer to Customization and Tuning for a description of the keyword.

EQQN061E

TOO MANY KEYWORD VALUES IN THE WLRSTMT KEYWORD

Keyword WLRSTMT on the JTOPTS statement contains too many values.

The normal mode manager (NMM) subtask is terminated.

Correct the error and restart the NMM subtask or the HCL Workload Automation for Z subsystem. Refer to Customization and Tuning for a description of the keyword.

EQQN062E

The WLRSTMT KEYWORD CONTAINS UNKNOWN KEYWORD VALUE KEYW

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

The normal mode manager (NMM) subtask is terminated.

Correct the error and restart the NMM subtask or the HCL Workload Automation for Z subsystem. Refer to Customization and Tuning for a description of the keyword.

EQQN063W

A FAILURE OCCURRED DURING THE CREATION OF THE VSAM FILE EQQSCPDS

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 creation of the Symphony fails either during the Daily plan batch job or during the Symphony Renew batch job execution. If the Daily plan is running, it ends with return code 4, allowing the creation of the current plan. The Symphony Renew ends with return code 8.

Analyze the preceding messages to determine the cause of the error. Correct the problem, then run a Symphony Renew to create the Symphony file asynchronously.

EQQN064E

CONTROLLER FAILED TO SYNCHRONIZE WITH END-TO-END SERVER

The NMM subtask was unable to synchronize with the end-to-end server. Possible causes are:
  • An end-to-end queue is full.
  • There is a communication problem between the controller and the server.
  • The server is down.

The NMM subtask continues its processing and the Symphony creation fails.

Check for previous EQQW088W or EQQW089W messages. Verify that the Enabler tasks and the Server are active. If necessary, restart either the Enabler or the Server, then try to recreate the Symphony file running a Daily Plan or a Symphony Renew batch job. If the Enabler and the Server are active, save the message log data set containing this error message and contact the Customer Support.

In the case where the NCP was created successfully by the DP batch run, do not stop and restart with CURRPLAN(NEW), but perform the following actions:
  • Solve the problem that caused the missing synchronization if possible (for example, start the server).
  • Run a DP extend (TPLGYPRM commented out in BATCHOPTS).
  • Run a Symphony renew (TPLGYPRM uncommented in BATCHOPTS).
Refer to APAR PK40651 for more details.

EQQN065E

THE NORMAL MODE MANAGER WAS NOT ABLE TO SEND THE EVENT EVENT TO THE ENABLER TASK: THE EVENT IS LOST

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

The NMM subtask continues its normal processing while the event is lost. The creation of the Symphony file fails.

Review earlier messages in the message log and, if it is possible to fix the problem, recreate the Symphony file running the Daily Plan or the Symphony Renew batch jobs. In any case, save the message log data set containing this error message, then contact the Customer Support.

EQQN066W

A CURRENT PLAN MUST BE PRESENT TO RUN A SYMPHONY RENEW

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

The Symphony Renew batch job fails. No new Symphony can be created if there is no active current plan.

Run a Daily Plan batch job to generate the current plan. A new Symphony file is also created.

EQQN067I

NOERRROW !NOERRMEM

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.

The scheduler lists the NOERROR table content in the controller message log.

None.

EQQN068I

THE NEW NOERROR STATEMENT VALUE: TABROW1 OVERLAPS THE ALREADY DEFINED VALUE: TABROW2.

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

The new entry is added to the NOERROR table.

Consider removing any redundant criteria. You can list the currently active NOERROR table by using the modify command, /F subsys,LSTNOERR.

EQQN069W

THE NEW NOERROR STATEMENT VALUE: TABROW1 IS NOT CONSISTENT WITH THE ALREADY DEFINED VALUE: TABROW2. IT CANNOT BE ADDED TO THE NOERROR TABLE.

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

The scheduler does not update the NOERROR table. Processing continues.

Check the currently active NOERROR table by using the modify command, /F subsys,LSTNOERR and remove the inconsistency.

EQQN070E

KEYVALUE IS NOT A VALID KEYWORD VALUE

An invalid keyword value has been defined.

HCL Workload Automation for Z uses the default keyword value.

Correct the value for the keyword containing the error and restart HCL Workload Automation for Z.

Contact your HCL Workload Automation for Z administrator.

EQQN071E

AN ATTEMPT TO UPDATE THE NOERROR TABLE HAS FAILED

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

The NOERROR table is not changed. HCL Workload Automation for Z continues normal processing.

Review earlier error messages in the message log that describe initialization statement processing errors. Correct all identified errors and reenter the modify command.

EQQN072I

THE NOERROR TABLE HAS BEEN SUCCESSFULLY UPDATED

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

HCL Workload Automation for Z continues normal processing and is using the updated NOERROR table.

None.

EQQN073E

PROTECTED LIST CAN BE UPDATED ONLY IF RCLEANUP=YES

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

The modify command is ignored.

Check why RCLEANUP option is not set.

EQQN074E

PROTECTED LIST CAN BE UPDATED ONLY IF RCLOPTS SPECIFIED

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

The modify command is ignored.

Check why RCLOPTS was not specified.

EQQN075I

PROTECTED DDNAME LIST HAS BEEN REMOVED

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.

The DDPROT list is removed.

None.

EQQN076I

PROTECTED DSNAME LIST HAS BEEN REMOVED

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.

The DSNPROT list is removed.

None.

EQQN077I

PROTECTED DDNAME LIST HAS BEEN UPDATED

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.

The DDPROT list is updated.

None.

EQQN078I

PROTECTED DSNAME LIST HAS BEEN UPDATED

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.

The DSNPROT list is updated.

None.

EQQN079W

INCORRECT VALUE SPECIFIED FOR KEYWORD KEYWORD. DEFAULT VALUE IS USED.

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.

None.

Specify a correct value and restart the controller.

EQQN080I

THE LOG ARCHIVER TASK HAS STARTED

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

Normal processing continues.

None.

EQQN081I

THE LOG ARCHIVER TASK HAS ENDED

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

Normal processing continues.

None.

EQQN082E

NEXT DSTYPE DATA SET, DDNAME DDNAME, IS NOT OPEN

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 normal mode manager (NMM) subtask is stopped and the current plan is no longer available.

Stop HCL Workload Automation for Z. Ensure that HCL Workload Automation for Z is authorized to update all job-tracking or extended-auditing data sets defined by currently specified (or defaulted) values of the JTLOGS and DUAL keywords of the JTOPTS initialization statement. Reallocate any log data sets that had output errors. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

Review earlier messages in the message log data set to determine why the next job-tracking or extended-auditing log is not open.

EQQN083E

THE JTLOGS KEYWORD MUST SPECIFY A VALUE IN THE RANGE 2 TO 99

The value specified for the JTLOGS keyword is not supported.

The normal mode manager subtask is terminated.

Correct the JTLOGS specification and restart HCL Workload Automation for Z.

Contact your system programmer.

EQQN084E

DD STATEMENT IS MISSING FOR A JOB TRACKING LOG DATASET, DDNAME DDNAME

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 normal mode manager subtask is terminated.

Either change the value defined by the JTLOGS or DUAL keyword or add the ddname defined by this message to the HCL Workload Automation for Z started task procedure. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

EQQN085E

UNSUPPORTED ATTEMPT TO REDUCE THE NUMBER OF JOB TRACKING LOGS. JTLOGS VALUE IS MAXJT, CURRENT JOB TRACKING LOG IS CURJT

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 normal mode manager subtask is terminated.

Change the JTLOGS specification to a larger value. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

EQQN086E

UNSUPPORTED ATTEMPT TO REDUCE THE NUMBER OF JOB TRACKING LOGS. JTLOGS VALUE IS MAXJT, LAST ARCHIVED LOG IS ARCJT

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.

The normal mode manager subtask is terminated.

Change the JTLOGS specification to a larger value. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

EQQN087E

DUAL JOB TRACKING LOG CONTAINS MORE EVENTS THAN PRIMARY JOB TRACKING LOG. CURRENT JOB TRACKING LOG, DDNAME DDNAME MAY BE INVALID

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.

The normal mode manager (NMM) subtask is terminated.

If the primary log data set is invalid, copy the dual log to the primary log. Otherwise, if the dual log data set is invalid, copy the primary log to the dual log. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

EQQN088E

NMM WAS UNABLE TO SWITCH TO NEXT DSTYPE DATA SET, DDNAME DDNAME, BECAUSE IT HAS NOT YET BEEN ARCHIVED.

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 normal mode manager subtask is stopped and the current plan is no longer available.

Stop HCL Workload Automation for Z. Ensure that HCL Workload Automation for Z is authorized to update all job-tracking or extended-auditing data sets defined by currently specified (or defaulted) values of the JTLOGS and DUAL keywords of the JTOPTS initialization statement. Reallocate any log data sets that had output errors. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

Review earlier messages in the message log data set to determine why the next job-tracking or extended-auditing log has not been archived.

EQQN089E

AN ATTEMPT TO LIST THE NOERROR TABLE CONTENT HAS FAILED. THE NOERROR TABLE IS EITHER EMPTY OR NOT DEFINED.

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

The modify command ends in error. Processing continues.

Verify that the EQQPARM library contains NOERROR definitions. Check for previous parsing error messages in the controller message log. After the controller initialization statements have been successfully processed, submit the modify command again.

EQQN090I

THE JOB TRACKING LOG DATA SET DEFINED BY DDNAME DDNAME HAS BEEN COPIED TO THE JOB TRACKING LOG ARCHIVE DATA SET

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

Normal processing continues.

None.

EQQN091I

THE LOG ARCHIVER TASK WAS UNABLE TO COPY THE DATA SET DEFINED BY DDNAME DDNAME TO THE JOB TRACKING LOG 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.

The job-tracking log archiver task is terminated. The current plan updating tasks continue, but if the log archiver task problem is not corrected, HCL Workload Automation for Z eventually runs out of available job hypheng log data sets.

Stop HCL Workload Automation for Z. Make sure that HCL Workload Automation for Z is authorized to read all job-tracking log data sets defined by currently specified (or defaulted) values of the JTLOGS and DUAL keywords of the JTOPTS initialization statement. Reallocate any job-tracking log data sets that had output errors. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

Review earlier messages in the message log data set to determine what prevented the log archiver task from copying the current log data set.

EQQN092E

AN I/O ERROR OCCURRED WHILE ATTEMPTING TO UPDATE THE JOB TRACKING LOG ARCHIVE DATA SET. THE ARCHIVER TASK IS ENDING. SYNAD MESSAGE FOLLOWS: SYNMSG

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.

The job-tracking log archiver task ends. The current plan updating tasks continue, but if the job-tracking log archiver task problem is not corrected, HCL Workload Automation for Z eventually runs out of available job-tracking log data sets.

Stop HCL Workload Automation for Z. If necessary, allocate a new job-tracking log archive data set and copy the old data set to the new data set. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout refer to the appropriate decoumentation for the MVS/DFP product installed on this system.

EQQN093E

A SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE THE JOB TRACKING LOG ARCHIVE DATA SET. THE ARCHIVER TASK IS ENDING.

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.

The job-tracking log archiver task ends. The current plan updating tasks continue, but if the job-tracking log archiver task problem is not corrected, HCL Workload Automation for Z eventually runs out of available job-tracking log data sets.

Stop HCL Workload Automation for Z. If necessary, allocate a new larger job-tracking log archive data set and copy the old data set to the new data set. After making the necessary corrections, restart HCL Workload Automation for Z.

Contact your system programmer.

Use the abend code to determine what is wrong with the archive data set.

EQQN094E

AN I/O ERROR OCCURRED WHILE ATTEMPTING TO UPDATE A DUAL JOB TRACKING LOG DATA SET. SYNAD MESSAGE FOLLOWS: SYNMSG

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.

HCL Workload Automation for Z stops logging events to the dual job-tracking log data sets. Logging on the primary job-tracking log data sets continues normally.

Scrap and reallocate the failing data set at a suitable time when HCL Workload Automation for Z is stopped.

Contact your system programmer.

The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product installed on this system.

EQQN095E

A SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE CURRENT DUAL JOB TRACKING LOG DATA SET

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.

HCL Workload Automation for Z stops logging events to the dual job-tracking log data sets. Logging on the primary job-tracking log data sets continues normally.

If the current job-tracking log data set is too small scrapthe current dual log data set and allocate a larger one at a suitable time when HCL Workload Automation for Z is stopped.

Contact your system programmer.

EQQN096I

THE NEW NOERROR STATEMENT VALUE: TABROW1 IS ALREADY PRESENT IN THE NOERROR TABLE: IT IS NOT STORED AGAIN.

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

The new NOERROR entry is ignored. Processing continues.

Check the currently active NOERROR table by using the modify command, /F subsys,LSTNOERR and consider removing the duplication.

EQQN097E

EQQUX014 EXIT RETURNED RC RETURN CODE. EXIT HAS BEEN DEACTIVATED

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

The scheduler cannot use the exit and deactivates it.

Check if the controller JCL procedure specifies the UX14IN DD statement.

EQQN098I

THE NOERROR TABLE HAS BEEN UPDATED ANYWAY DUE TO NOERRCONCHECK PARAMETER SETTING.

The NOERROR consistency check detected some inconsistent statements.

Based on the NOERRCONCHECK parameter setting MSG, the NOERROR table update has been forced.

If you specified NOERRCONCHECK(MSG), review the previous EQQN069W messages issued as result of the NOERROR table update. Based on your environment settings (for example naming conventions and standards), make sure that the indicated entries are not actually inconsistent.

Before attempting to update the NOERROR table, consider running the trial modify command /F subsys,TRYNOERR(mem_name), to simulate the insertion of new statements, and check the sequence of EQQN069W messages.

The NOERROR statements might be inconsistent and might produce unexpected results.

EQQN099I

THE NOERROR STATEMENTS TRIAL COMMAND HAS ENDED

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

The scheduler did not update the NOERROR table. Normal processing continues.

Check for previous EQQN069W messages issued after the modify command. Consider removing any inconsistency or changing the NOERRCONCHECK parameter value in the OPCOPTS statement.

EQQN101E

THE MODIFY CURRENT PLAN MODULE, EQQMCTOP, COULD NOT BE LOADED

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

The normal mode manager (NMM) subtask initialization fails.

Make sure that the EQQMCTOP load module is present in a library that can be reached by HCL Workload Automation for Z, and restart the NMM subtask

EQQN102W

AN USER EXIT LOAD MODULE, MODULE, COULD NOT BE LOADED

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

This exit is not used by HCL Workload Automation for Z.

Correct the error and restart the HCL Workload Automation for Z subsystem.

Check if the module named in this message should be used by HCL Workload Automation for Z. Also check that the module exists in a library that the subsystem started task can reach.

EQQN103E

THE EVENT HANDLER MODULE, EQQEMEVH, COULD NOT BE LOADED

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

HCL Workload Automation for Z initialization fails.

Make sure that the EQQEMEVH load module exists in a library that can be reached by HCL Workload Automation for Z and restart the HCL Workload Automation for Z started task.

EQQN104W

PROCESSING RETURN CODE RETC from EQQUX011. THE EXIT HAS BEEN MARKED AS NOT EXECUTABLE BUT THE PROCESS CONTINUES

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

The system writes a job tracking log record, but Exit011 is set as inactive.

Refer to the meaning of the RETC return code in the Exit011. The code depends on Exit011 customization.

EQQN105W

NO VALID CURRENT PLAN EXISTS. CURRENT PLAN VSAM I/O IS NOT POSSIBLE

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.

The normal mode manager (NMM) subtask, which has been initialized, takes a new current plan if one is created by a daily plan create batch job executing on behalf of this subsystem.

Correct the errors and, if necessary, restart the NMM subtask.

If this message was not expected, check that the started task procedure (ddname EQQCKPT) is correctly specified. Also check that this subsystem is the only HCL Workload Automation for Z subsystem that references this checkpoint data set.

EQQN106E

ERRORS ENCOUNTERED PROCESSING NMM INITIALIZATION STATEMENTS. THE NORMAL MODE MANAGER TASK WILL TERMINATE

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

The NMM subtask initialization fails.

Correct the error and restart the HCL Workload Automation for Z subsystem.

Review the previous messages in the message log data set to determine the cause of the problem.

EQQN107I

THE NORMAL MODE MANAGER TASK HAS ENDED

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.

Normal processing continues.

None.

EQQN108E

THE NEW CURRENT PLAN DATA SET IS INVALID. A NEW NCP DATA SET MUST BE CREATED.

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

The NMM subtask does not use the contents of the NCP data set.

If necessary, correct errors in the daily planning input data sets and rerun the daily planning batch job or correct the NCP file definition problems and restart HCL Workload Automation for Z.

Contact your system programmer.

If a daily planing batch job has just ended, check ending conditions for the job. If the error occurs when HCL Workload Automation for Z is starting, verify that the DD statement, EQQNCPDS, defining the NCP file, is correct.

EQQN109W

EXIT11 TERMINATES ABNORMALLY. THE EXIT HAS BEEN MARKED AS NOT EXECUTABLE BUT THE PROCESS CONTINUES

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.

The system writes a job tracking log record, but Exit011 is set as inactive.

None.

EQQN110W

FL TASK IS NOT STARTED: R&C DATA STORE CLEAN UP COULD BE IGNORED

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 remove request is not processed.

Check why the FL task is down and restart it.

EQQN111I

A NEW SYMPHONY FILE HAS BEEN CREATED

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 task sends to the Translator the command to complete the switch of the new Symphony file.

None.

EQQN112E

THE NEW SYMPHONY FILE HAS NOT BEEN CREATED

The batch job was unable to renew the Symphony file.

The task continues its own processing. The plan is not distributed to fault-tolerant workstations.

If the problem persists save the DP Extend message log. To collect appropriate documentation for problem determination, see the problem analysis procedures described in theDiagnosis Guide and Reference manual. Search the IBM Support database for a solution at Support.

Review the message log data set for further error messages. Remove the cause of each error and submit the daily planning batch job again.

EQQN113E

FT WORKSTATION WSID PRESENT ON CP, BUT E2E FEATURES NOT ACTIVE

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 inconsistency is showed on subsystem MLOG for every Fault-tolerant workstation.

Change workstation from Fault-tolerant to None-Fault-tolerant workstation, or the keyword TPLGYSRV on OPCOPTS parameter.

EQQN114E

ONLY OCCNAME VALUE ALLOWED FOR TWSJOBNAME PARAMETER WHEN EQQTWSOU RECORD LENGTH IS LESS THAN 160

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 controller initialization fails.

Migrate the EQQTWSOU data set by using the EQQMTWSO sample or set the TWSJOBNAME parameter in the JTOPTS statement to OCCNAME.

EQQN115I

WAITING FOR NCP

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 NMM subtask is waiting for the NCP to complete.

None.

EQQN116I

A NEW NCP WAS CREATED

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

Processing continues.

None.

EQQN117I

SYNCHRONIZATION BETWEEN CONTROLLER AND SERVER STARTED

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

The normal mode manager (NMM) subtask is waiting for synchronization to complete.

None.

EQQN118I

NEW SCP WAS CREATED

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

Processing continues.

None.

EQQN119W

THE SA COMMAND VARSUB MODULE EQQZVGSU COULD NOT BE LOADED

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

The initialization of the scheduler main task continues, but it is not possible to use the variable substitution function for system automation commands. If the SAVARFAIL parameter is not set, no variable substitution is done. If the SAVARFAIL parameter is set, the system automation operation fails with OJCV code.

Make sure that the EQQZVGSU load module exists in a library that can be accessed by HCL Workload Automation for Z. Stop and restart the HCL Workload Automation for Z started task.

EQQN120I

DP BATCH NCP CREATION PHASE ENDED

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.

None.

None.

EQQN121I

NEW SCP WAS CREATED

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

Processing continues.

None.

EQQN122I

A SYMPHONY RENEW ACTIVITY WAS STARTED

A Symphony renew activity was started by a batch job.

Processing continues.

None.

EQQN123W

A NEW BULK DISCOVERY CANNOT BE STARTED. BULK DISCOVERY IS CURRENTLY IN PROGRESS.

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

The new bulk discovery request is interrupted.

None.

EQQN124W

JTOPTS CURRPLAN(NEW) HAS BEEN SPECIFIED, BUT THE NCP DATA SET WAS NOT COPIED BY THE CONTROLLER

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.

Processing continues.

Ensure that you performed the following steps; if not, stop the controller, take them, and restart the controller:
  1. You must have replaced JTARC with the current JT log, that is the JT log indicated in the checkpoint data set. For details, see the DCLOPC record in the Diagnosis Guide and Reference.
  2. The current JT log must have been emptied.

Note that this message is issued only the first time the controller is restarted after an incomplete NCP creation process.

EQQN125W

FAILED TO SYNCHRONIZE SUBMISSION ON Z-CENTRIC WORKSTATIONS

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

The normal mode manager (NMM) subtask continues its processing.

Find and correct any error occurred on operations on HCL Workload Automation Agent workstations with status Started and extended status Waiting for submission.

EQQN126E

UNABLE TO ADD EQQHTTP0 DATASET ENTRY IN EDP TABLE

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.

The controller initialization fails and a user abend is generated.

Remove the TPLGYPRM keyword in the BATCHOPT statement and the TPLGYSRV in the OPCOPTS; then refresh the checkpoint data set, running a daily plan extend or replan batch job after specifying the CKPTREFRESH keyword with value YES. When the batch job completes, restore the keywords previously removed.

EQQN127E

A SEVERE ERROR OCCURRED WHILE RUNNING TIE BLOCK ADD ROUTINE

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

HCL Workload Automation for Z processing continues and additional debugging traces are generated in message log.

If the problem persists save message log. Search the IBM Support database for a solution at Support.

Describe the scenario that caused the error. To collect appropriate documentation for problem determination, see the problem analysis procedures described in theDiagnosis Guide and Reference manual.

EQQN128E

A SEVERE ERROR OCCURRED WHILE RUNNING TIE BLOCK DELETE ROUTINE

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

HCL Workload Automation for Z processing continues and additional debugging traces are generated in message log.

If the problem persists save message log. Search the IBM Support database for a solution at Support.

Describe the scenario that caused the error. To collect appropriate documentation for problem determination, see the problem analysis procedures described in theDiagnosis Guide and Reference manual.

EQQN130E

AN ERROR OCCURRED WHILE SYNCHRONIZING BIND REQUESTS

An error occurred while synchronizing the bind requests at controller startup. The scope of the synchronization is to prevent events from being lost while cross-dependencies are processed. The synchronization consists of:
  1. Sending again to remote engines the bind request for shadow jobs that are in Ready status with Sending bind request extended status.
  2. Notifying again the current status for the jobs associated with an active bind request.

The normal mode manager (NMM) subtask processing continues.

If the problem persists save message log. Search the IBM Support database for a solution at Support.

Check for other messages indicating the cause of the error. After the problem is solved, restart the controller to force a new synchronization. If the problem persists, describe the scenario that caused the error. To collect appropriate documentation for problem determination, see the problem analysis procedures described in theDiagnosis Guide and Reference manual.

EQQN131W

THE UNIT OF MEASURE FOR THE MAXJSFILE PARAMETER HAS CHANGED FROM KILOBYTES TO MEGABYTES

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.

Recalculate and assign the value of the parameter in megabytes.

EQQN132E

AN ERROR OCCURRED WHILE PROCESSING THE BIND REQUESTS IN PENDING STATUS

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 normal mode manager (NMM) subtask processing continues.

If the problem persists save message log. Search the IBM Support database for a solution at Support.

Check for other messages indicating the cause of the error. After the problem is solved, run a replan to process the pending bind requests again. If the problem persists, describe the scenario that caused the error. To collect appropriate documentation for problem determination, see the problem analysis procedures described in the Diagnosis Guide and Reference manual.

EQQN138W

SYNCHRONIZATION IS NOT IN PROGRESS, THE MESSAGE IS IGNORED.

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

The normal mode manager (NMM) subtask processing continues.

Check that the DD name is correct and that was correctly allocated.

EQQN150W

I/O ERROR READING BACKUP CHECKPOINT DATA SET: SKIP JTX EVENT.

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

The JT event is ignored.

Check the reason for the I/O error.

EQQN156E

FILE TRANSFER END WAS RECEIVED BUT TRANSFER FAILED (JOBNAME JOBID).

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 data set transfer is not performed.

Check the job log for JOBNAME JOBID to understand the reason of the failure.

EQQN157W

FILE RESTORE END WAS RECEIVED BUT PLAN RESYNCHRONIZATION IS NOT IN PROGRESS: RESTORE IS IGNORED (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.

Processing continues.

Check the log for the job JOBNAME JOBID, and check the system log to see if the restore procedure was started manually.

EQQN158E

FILE RESTORE END WAS RECEIVED BUT RESTORE FAILED (JOBNAME JOBID).

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.

The data set restore is not performed.

Check the job log for JOBNAME JOBID to understand the reason of the failure.

EQQN159E

INVALID SSX: REBUILD SSX IS REQUIRED TO ALLOW BACKUP AND PRIMARY CONTROLLER COMMUNICATION.

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

The controller stops.

Set the OPCOPTS BUILDSSX(REBUILD) SSCMNAME(EQQSSCMx, PERMANENT) statement to the controller and restart it.

EQQN171E

PRIMARY CONTROLLER PLAN OR JT SEQNO IS OLDER THAN THE BACKUP CONTROLLER PLAN OR JT SEQNO: BACKUP CONTROLLER IS STOPPED.

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 backup controller stops.

Check the reason why the backup controller has a more recent version of the current plan. One reason could be that after issuing the modify command /F subsys,BKTAKEOVER, the backup controller became the primary controller, then it was stopped and restarted as backup controller. Perform a cleanup action on the current plan and on the checkpoint data sets, then restart the backup controller.

EQQN172E

FILE TRANSFER COULD NOT BE STARTED (PROCN): CONNECTION IS DOWN.

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 transfer is not performed.

Check and re-establish the connection between the controllers.

EQQN175W

PRIMARY CONTROLLER COULD NOT RESEND JT: PLAN RESEND IS REQUIRED.

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 JT is not sent and the backup controller is notified.

None.

EQQN176W

COMMAND BKTAKEOVER CANNOT BE RUN: PRIMARY CONTROLLER IS STILL CONNECTED.

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

The command is ignored.

Stop the primary controller and wait for the connection closure, then issue the modify command /F subsys,BKTAKEOVER again.

EQQN177W

SOME EVENTS WERE NOT RECEIVED: EVENT CURRENTLY RECEIVED HAS TYPE TYP1 AND SEQNO CSEQN1 BUT EVENT PREVIOUSLY RECEIVED HAD TYPE TYP2 AND SEQNO CSEQN2. JT MUST BE SENT AGAIN.

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.

The JT resynchronization is requested.

None.

EQQN180W

LATEST ARCHIVED JT NUMBER AND CURRENT JT NUMBER ARE THE SAME: JT RECOVER IS ATTEMPTED.

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

The current JT is moved to the next.

None.

EQQN182I

EXECUTE A PLAN BACKUP BEFORE TO START JT REAPPLY.

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.

The Normal Mode Manager (NMM) subtask is waiting for the backup and reapply to complete.

None.

EQQN183I

LAST RECORD IN CURRENT JT IS NOT A BACKUP EVENT: JT REAPPLY IS REQUIRED.

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.

The Normal Mode Manager (NMM) subtask is waiting for the backup and reapply to complete.

None.

EQQN184I

CP EVENTS AFTER LAST BACKUP TIME HAVE BEEN FOUND IN THE CURRENT JT: JT REAPPLY IS REQUIRED.

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.

The Normal Mode Manager (NMM) subtask is waiting for the reapply to complete.

None.

EQQN187W

JT REAPPLY IS REQUIRED BUT THIS IS A BACKUP CONTROLLER: A REQUEST WILL BE SENT TO RECEIVE THE PLANS AGAIN

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 backup controller sends a request to the primary controller to receive the plans.

None.

EQQN188W

UNABLE TO OPEN CURRENT JT JTDD

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

The controller stops.

Check the JT data set to understand the reason of the failure.

EQQN193W

SOME CHANGES ON LOGDB WERE NOT RECEIVED BY THE BACKUP CONTROLLER: THE WHOLE DATA SET SNDDB NEEDS TO BE MANUALLY SENT.

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

Processing continues.

Transfer the impacted VSAM data set to the backup controller by starting the appropriate customized procedure. Before you transfer the EQQSIDS data set, run a current plan backup (for details about the current-plan backup process, see Managing the Workload).

EQQN199W

A SYNCHRONIZATION PROCESS WAS IN PROGRESS WHEN BKTAKEOVER WAS ISSUED. SYNCHRONIZATION INFO: SYNC TYPE: SYNCTYP, NCP STATUS: NCPS, CP1 STATUS: CP1S, CP2 STATUS: CP2S, LTP STATUS: LTPS

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.

Following this message, other messages are logged to show the specific action taken by the system. In all cases, job submission is stopped to allow a plan check.

For example, if a restore process was in progress, the command /F subsys,BKTAKEOVER is postponed after the restore process is completed. No manual actions are required, the following messages are shown:
EQQN207W JOB SUBMISSION IS DEACTIVATED TO ALLOW
         A PLAN CHECK
EQQN200I A RESTORE PROCESS IS IN PROGRESS: 
         BKTAKEOVER EXECUTION IS POSTPONED
         AFTER RESTORE PROCESS END.

To decide if any action is required, check the details about the synchronization process and the messages that follow.

EQQN201W

A JT SYNCHRONIZATION PROCESS WAS IN PROGRESS: SOME EVENTS COULD HAVE BEEN LOST.

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.

Processing continues.

Because some JT events might be lost, check the status of the jobs in plan. If needed, check also the list of step events (for detailed information about browsing the list of job steps, see Managing the Workload).

EQQN202W

BOTH CP AND LTP PLANS HAVE BEEN REQUESTED BY BACKUP CONTROLLER BUT ONLY LTP HAS BEEN RESTORED.

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 BKTAKEOVER command is not run, the job submission is stopped and following messages are issued:
EQQN207W JOB SUBMISSION IS DEACTIVATED TO ALLOW A
         PLAN CHECK
EQQN211I BKTAKEOVER COULD NOT BE EXECUTED:   
         MANUAL ACTIONS ARE REQUIRED         
EQQN212I RECOVER LTP FROM VERSION AVAILABLE BEFORE
         LATEST RESTORE. 
         ONCE COMPLETED RE-ISSUE BKTAKEOVER MODIFY
         COMMAND.
The backup controller waits for you to perform the manual actions indicated by the EQQN212I messages that follow.

Recover the long-term plan available before the latest restore process, by following the instructions shown in the customized LTP restore procedure. After completing the recovery, issue the modify command /F subsys,BKTAKEOVER again.

EQQN203W

BOTH CP AND LTP PLANS HAVE BEEN REQUESTED BY BACKUP CONTROLLER BUT ONLY CP HAS BEEN RESTORED.

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 BKTAKEOVER command is not run, the job submission is stopped and following messages are issued:
EQQN207W JOB SUBMISSION IS DEACTIVATED TO ALLOW
         A PLAN CHECK
EQQN211I BKTAKEOVER COULD NOT BE EXECUTED:   
         MANUAL ACTIONS ARE REQUIRED         
EQQN212I RECOVER CP FROM VERSION AVAILABLE BEFORE
         LATEST RESTORE: 
         USE BKSTATUS MODIFY COMMAND CP PLAN  
         DDNAME VALUE TO IDENTIFY CP TO BE 
         RECOVERED.
         ONCE COMPLETED RE-ISSUE BKTAKEOVER
         COMMAND.
The backup controller waits for you to perform the manual actions indicated by the EQQN212I messages that follow.
Complete the following steps:
  1. Issue the modify command /F subsys,BKTAKEOVER to verify which is the current CP (CP1 or CP2).
  2. Restore the CP available before the latest restore (CP1 or CP2, as indicated by the BKSTATUS command), by following the instructions shown in the customized CP restore procedure
  3. After completing the recovery, issue the modify command /F subsys,BKTAKEOVER again.

EQQN204W

LONG-TERM PLAN IS NOT AVAILABLE.

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.

The controller is stopped.

Restore the previous copy of LTP and CP that were saved in the GDG data set, then restart the backup controller.

EQQN205W

LTP IS OLDER THAN CP: THEY ARE NOT ALIGNED.

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.

If this message was issued when you entered the BKTAKEOVER command, the command has not completed. The backup controller shows the following messages and waits for you to perform the manual actions indicated:
EQQN211I  BKTAKEOVER COULD NOT BE EXECUTED:      
          MANUAL ACTIONS ARE REQUIRED 
EQQN212I  RECOVER LTP FROM LATEST AVAILABLE VERSION
          ONCE COMPLETED RE-ISSUE BKTAKEOVER MODIFY
          COMMAND.

If this message was issued during backup controller processing, at the end of a synchronization process another synchronization process is started to request both plans. If this process fails, there are no other retries.

Check the reasons for the plan disalignment (for example, a TCP/IP communication problem or an error occurred during the send or restore procedure) and fix them. If the primary controller is still connected, produce a long-term plan modify all, to send an earlier version of LTP.

TODs are created at LTP batch and CP batch run time, by applying the current time. If between the CP batch run and LTP batch run the system time is changed (for example, when Daylight Saving Time occurs and the clock is moved back 1 hour) the LTP might seem older than CP, but this is not true.

EQQN206W

LTP PLAN END IS OLDER THAN CP PLAN END OR THEY HAVE THE SAME END BUT THE NUMBER OF REPLAN IS DIFFERENT: THEY ARE NOT ALIGNED.

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.

If this message was issued when you entered the BKTAKEOVER command, the command has not completed. The backup controller shows the following messages and waits for you to perform the manual actions indicated:
EQQN211I  BKTAKEOVER COULD NOT BE EXECUTED:                    
          MANUAL ACTIONS ARE REQUIRED                          
EQQN212I  RECOVER LTP FROM LATEST AVAILABLE VERSION
          ONCE COMPLETED RE-ISSUE BKTAKEOVER MODIFY
          COMMAND.                              

If this message was issued during backup controller processing, at the end of a synchronization process another synchronization process is started to request both plans. If this process fails, there are no other retries.

Check the reasons for the plan disalignment (for example, a TCP/IP communication problem or an error occurred during the send or restore procedure) and fix them. If the primary controller is still connected, produce a long-term plan modify all, to send an earlier version of LTP.

EQQN207W

JOB SUBMISSION IS DEACTIVATED TO ALLOW A PLAN CHECK.

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.

Processing continues.

Check the status of the plan to verify if manual actions are required.

EQQN208W

LATEST RESTORED CP IS OLDER THAN PREVIOUSLY USED CP.

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.

If this message was issued when a synchronization process completed, another synchronization process is started to request both plans. If this process fails, there are no other retries.

None.

EQQN209W

CURRENT PLAN IS NOT AVAILABLE.

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 controller is stopped.

Restore the CP and LTP from previous copies that were saved in the GDG data set, then restart the backup controller.

EQQN212E

BKTAKEOVER COULD NOT BE EXECUTED: MANUAL ACTIONS ARE REQUIRED.

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).

None.

Perform the manual actions requested and issue the /F subsys,BKTAKEOVER command again, unless otherwise stated.

The possible manual actions suggested by EQQN212I messages are:
RECOVER LTP FROM LATEST AVAILABLE VERSION. ONCE COMPLETED RE-ISSUE BKTAKEOVER MODIFY COMMAND.
This action is requested when the processing detects that the long-term plan is older than the current plan. You must align the long-term plan to the current plan by restoring the latest version of LTP using the existing restore samples. If the latest LTP is not available, align the plans by restoring the previous version of the current plan using the existing restore samples (consider that each time a plan is restored, the previous version is saved by a restore sample).
RECOVER LTP FROM VERSION AVAILABLE BEFORE LATEST RESTORE. ONCE COMPLETED RE-ISSUE BKTAKEOVER MODIFY COMMAND.
This action is requested when a synchronization was in progress and only the long-term plan was received. You must align the long-term plan to the current plan by restoring the previous version of LTP, using the existing restore samples (consider that each time a plan is restored, the previous version is saved by a restore sample).
RECOVER CP FROM VERSION AVAILABLE BEFORE LATEST RESTORE: USE BKSTATUS MODIFY COMMAND CP PLAN DDNAME VALUE TO IDENTIFY CP TO BE RECOVERED. ONCE COMPLETED RE-ISSUE BKTAKEOVER MODIFY COMMAND
This action is requested when a synchronization was in progress and only the current plan was received. You must align the long-term plan to the current plan by restoring the previous version of CP, using the existing restore samples (consider that each time a plan is restored, the previous version is saved by restore sample)
RESTORE COHERENT CP AND LTP VERSION: SYNC PLAN REQUEST IS FORCED.
This action is requested when a synchronization was in progress and no plan was received, thus making the available plans not aligned. You must restore the latest available couple of aligned CP and LTP. Then issue the BKTAKEOVER command again.
RESTORE NCP FROM LATEST AVAILABLE VERSION ONCE COMPLETED RE-ISSUE BKTAKEOVER MODIFY COMMAND.
This action is requested when the connection broke while the new current plan (NCP) was requested, but not restored. You must restore NCP, then issue the BKTAKEOVER command again.

EQQN214W

BOTH CP AND LTP PLANS HAVE BEEN REQUESTED TO PRIMARY CONTROLLER BUT NONE OF THEM HAS BEEN RESTORED.

You issued the modify command /F subsys,BKTAKEOVER when a plan synchronization process was in progress. The backup controller requested the CP and LTP data sets, but none of them was received and restored. If CP and LTP plans are available, the BKTAKEOVER command is run and the synchronization process is performed by using the available plans. The following messages are shown:
EQQN207W JOB SUBMISSION IS DEACTIVATED TO ALLOW
         A PLAN CHECK
EQQN212I CURRENT SYNCHRONIZATION IS COMPLETED WITH
         AVAILABLE LTP AND CP.                    
If plans are not available, the controller does not complete the BKTAKEOVER command, but waits for you to perform the manual actions indicated by the following messages:
EQQN211I BKTAKEOVER COULD NOT BE EXECUTED:   
         MANUAL ACTIONS ARE REQUIRE    
EQQN212I 	RESTORE COHERENT CP AND LTP VERSION: SYNC
         PLAN REQUEST IS FORCED. 

Depending on plan availability, the BKTAKEOVER command completes or not. If not, the controller waits for you to perform the manual actions indicated by EQQN212I messages.

If needed, restore the CP and LTP from previous copies that were saved in the GDG data set.

EQQN215W

CP PLAN HAS BEEN REQUESTED TO PRIMARY CONTROLLER BUT IT MUST STILL BE RESTORED.

You issued the modify command /F subsys,BKTAKEOVER when a plan synchronization process was in progress. The backup controller requested the CP data set, but it was not received nor restored. The BKTAKEOVER command is run and the synchronization process is performed by using the available plans. The following messages are shown:
EQQN207W JOB SUBMISSION IS DEACTIVATED TO ALLOW
         A PLAN CHECK
EQQN212I CURRENT SYNCHRONIZATION IS COMPLETED WITH
         AVAILABLE LTP AND CP.                    

The BKTAKEOVER command completes with the available plans.

Check any operations in the current plan that where in Started status when the controller were switched. If required, browse also the list of job steps. According to the job information available, verify if you need to manually complete or rerun any operations.

EQQN216W

LTP PLAN HAS BEEN REQUESTED TO PRIMARY CONTROLLER BUT IT MUST STILL BE RESTORED.

You issued the modify command /F subsys,BKTAKEOVER when a plan synchronization process was in progress. The backup controller requested the LTP data set, but it was not received nor restored. The BKTAKEOVER command is run and the synchronization process is performed by using the available plans. The following messages are shown:
EQQN207W JOB SUBMISSION IS DEACTIVATED TO ALLOW
         A PLAN CHECK
EQQN212I CURRENT SYNCHRONIZATION IS COMPLETED WITH
         AVAILABLE LTP AND CP.                    

The BKTAKEOVER command completes with the available plans.

Check any operations in the current plan that where in Started status when the controller were switched. If required, browse also the list of job steps. According to the job information available, verify if you need to manually complete or rerun any operations.

EQQN217W

A SYNCHRONIZATION CHECK REQUEST WAS SENT TO PRIMARY CONTROLLER BUT NO ANSWER HAS BEEN RECEIVED.

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.

Job submission is stopped to allow plan check. The BKTAKEOVER command is run with available plans. The following messages are shown:
EQQN207W JOB SUBMISSION IS DEACTIVATED TO ALLOW
         A PLAN CHECK.
EQQN212I CURRENT SYNCHRONIZATION IS COMPLETED WITH
         AVAILABLE LTP AND CP.

Check any operations in the current plan that where in Started status when the controller were switched. If required, browse also the list of job steps. According to the job information available, verify if you need to manually complete or rerun any operations.

EQQN218W

A DP BATCH SYNCHRONIZATION IS IN PROGRESS: ONLY NCP IS STILL TO BE RESTORED.

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.

Job submission is stopped to allow plan check. The BKTAKEOVER command is not run. The controller waits for you to perform the manual actions indicated by the following messages:
EQQN207W JOB SUBMISSION IS DEACTIVATED TO ALLOW
         A PLAN CHECK
EQQN211I BKTAKEOVER COULD NOT BE EXECUTED:              
         MANUAL ACTIONS ARE REQUIRED                          
EQQN212I RESTORE NCP FROM LATEST AVAILABLE VERSION. 
         ONCE COMPLETED RE-ISSUE BKTAKEOVER MODIFY
					COMMAND.

Perform the manual actions indicated by the EQQN212I messages.

EQQN219E

INTERNAL READER FILE, DDNAME = EQQBR2DS, PROBLEMS: PROB.

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 transfer or restore procedure is not started. Processing continue.

Correct the errors and restart the HCL Workload Automation for Z subsystem.

Check that the DD name EQQBR2DS is correctly specified in the startup procedure. Also, review the previous messages in the HCL Workload Automation for Z message log and system message log (for example, the messages issued by DFSMS) that refer to EQQBR2D by indicating an unusual condition.

EQQN220E

TRANSFER START FAILED (PROCN): REASON.

The NMM task could not start the transfer procedure identified by the job PROCN. REASON identifies that one of the following problems occurred:
  • JOBLIB NOT OPENED
  • JCL RETRIEVAL FAILURE
  • INSUFFICIENT STORAGE
  • EMPTY JCL
  • JCL NOT FOUND
  • LOGICAL RECORD SIZE NOT VALID

The transfer procedure is not submitted. Processing continue.

Correct the errors and manually submit the transfer procedure.

EQQN221E

RESTORE START FAILED (PROCN): REASON.

The NMM task could not start the restore procedure identified by the job PROCN. REASON identifies that one of the following problems occurred:
  • JOBLIB NOT OPENED
  • JCL RETRIEVAL FAILURE
  • INSUFFICIENT STORAGE
  • EMPTY JCL
  • JCL NOT FOUND
  • LOGICAL RECORD SIZE NOT VALID

The restore procedure is not submitted. Processing continue.

Correct the errors and manually submit the restore procedure.

EQQN222E

WRONG VALUE FOR RISKCONFIDENCE: ONLY VALUES 1-99 ARE ACCEPTED.

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

The processing of JTOPTS parameters is not successful.

Specify a valid value for RISKCONFIDENCE and restart the controller.

EQQN224E

EXTENDED AUDITING FEATURE HAS BEEN DEACTIVATED.

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

Processing continues.

To activate the extended auditing feature again, stop the controller, allocate an EQQDBARC with a greater amount of space, copy the files from the old EQQDBARC, and restart the controller.

EQQN226I

SMOOTHSUBMISSION FUNCTION IS ACTION. SMOOTHSUBDELAY VALUE IS MAXDELAY. SMOOTHSUBCONFLEVEL VALUE IS CONFLEV.

See message text.

Processing continues.

None.

EQQN228I

TURNOVER IN PROGRESS: CURRENT ACCUMULATED EVENTS JTEVENTS CURRENT ACCUMULATED MCP EVENTS: MCPEVENTS CURRENT ACCUMULATED MCP TIME MCPTIME.

This message is issued to track the number of events that accumulated during turnover.
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.
The frequency of this message is determined by the JTAPPLCNT parameter in JTOPTS.
Processing continues.
None.

EQQN230W

WSSYSAFF OR WSCLASS WSNAME IS NOT IN CURRENT PLAN: IGNORED.

At current plan rebuilding (after a turnover or restart), HCL Workload Automation for Z detected that the workstation name set in JTOPTS(WSSYSAFF) or JTOPTS(WSCLASS) is not existent in the current plan.
Processing continues. The workstation WSNAME that was set in JTOPTS WSSYSAFF is ignored.
Ensure that the workstation name that was set in the WSSYSAFF or WSCLASS parameter of JTOPTS was not mistyped; if this is the case, correct the name and restart the controller or modify the value by deleting the incorrect workstation name, then adding the correct workstation name with the MODIFY commands (respectively, /F procname,RWSSYSAFF(wsname) and /F procname,AWSSYSAFF(wsname).

EQQN231E

WSSYSAFF DEFINITION FOR WSNAME IS INCORRECT. RC=RC.

The controller detected that the workstation name set in JTOPTS WSSYSAFF is not correct. The return code RC provides you with an explanation of the error:
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.
The controller initialization is terminated.
Correct the syntax of the WSSYSAFF parameter in JTOPTS and restart the controller.

EQQN232I

THE FOLLOWING WORKSTATIONS SUPPORT JOB EXECUTION FORCING BECAUSE JTOPTS WSSYSAFF IS SET:

You issued the MODIFY command /F procname,DWSSYSAFF to display the workstations supporting the forcing of job execution because you set JTOPTS WSSYSAFF. This message is the response; it is followed by a list of EQQN233I messages that shows the workstation names and related systems.destinations.
Processing continues.
None.

EQQN233I

TEXT

This message is issued after message EQQN232I or EQQN245I to display the list of workstations that support the forcing of job execution or class. TEXT can have either of the following syntax:
  • WSNAME=wsname
  • WSSYSNAME=system DESTINATION=destination
Processing continues.
None.

EQQN234W

WSSYSAFF WSNAME SPECIFIES DESTINATION DEST THAT IS NOT INCLUDED IN WORKSTATION DEFINITION. SHUTDOWN POLICY CANNOT BE APPLIED TO IT.

This message is issued if JTOPTS SHUTDOWNPOLICY is set to value greater than zero. It occurs when JTOPTS WSSYSAFF specifies a destination DEST that is not included in the definition of the workstation WSNAME, to indicate that the SHUTDOWNPOLICY checks are not performed for this 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.

Processing continues.
None.

EQQN235E

WSSYSAFF OR WSCLASS REMOVE OR ADD COMMAND ALREADY IN PROGRESS. COMMAND REJECTED.

A MODIFY command was issued to remove or add an entry from the WSSYSAFF or WSCLASS parameter of JTOPTS, but another command to modify WSSYSAFF or WSCLASS is already in progress.
The command is ignored.
Wait until the command in progress is completed, then issue the MODIFY command again.

EQQN236E

WSSYSAFF AND WSCLASS REMOVE OR ADD COMMANDS NEED NMM ACTIVE. COMMAND REJECTED.

A MODIFY command was issued to remove or add a value in the WSSYSAFF or WSCLASS parameter of JTOPTS, but the normal-mode-manager (NMM) task is not active.
The command is ignored.
Check the reason why the NMM task is not active. Start the NMM task or, if needed, restart the controller then issue the MODIFY command again.

EQQN237W

WORKSTATION WS ALREADY REMOVED FROM PARAMETER. NO ACTION DONE.

A MODIFY command was issued to delete the workstation WS from the WSSYSAFF or WSCLASS parameter of JTOPTS (see message text), but that workstation is not set in the parameter.
The command is ignored.
None.

EQQN238I

WORKSTATION WS REMOVED FROM PARAMETER.

A MODIFY command was issued to delete the workstation identified by WS in the WSSYSAFF or WSCLASS parameter (see message text) of JTOPTS. The command was successful.
The command was run.
None.

EQQN239W

SYSTEM SYSNAME FOR WORKSTATION WS ALREADY REMOVED FROM WSSYSAFF. NO ACTION DONE.

A MODIFY command was issued to delete system SYSNAME set for workstation WS from the WSSYSAFF parameter of JTOPTS, but that system is not set in the parameter.
The command is ignored.
None.

EQQN240I

SYSTEM SYSNAME FOR WORKSTATION WS REMOVED FROM WSSYSAFF.

A MODIFY command was issued to delete system SYSNAME set for workstation WS in the WSSYSAFF parameter of JTOPTS. The command was successful.
The command was run.
None.

EQQN241W

SYSTEM SYSNAME IS ALREADY DEFINED FOR WORKSTATION WS IN WSSYSAFF. NO ACTION DONE.

A MODIFY command was issued to add the system SYSNAME for workstation WS in the WSSYSAFF parameter of JTOPTS, but that system is already set in the parameter.
The command is ignored.
None.

EQQN242I

SYSTEM SYSNAME WITH DESTINATION DEST ADDED FOR WORKSTATION WS IN WSSYSAFF PARAMETER.

A MODIFY command was run to add system SYSNAME with destination DEST for workstation WS in the WSSYSAFF parameter of JTOPTS.
None.
None.

EQQN243E

WSCLASS DEFINITION FOR WS IS INCORRECT. RC=RC.

The controller detected a setting for JTOPTS WSCLASS that is not valid. The setting is related to workstation WS.
The return value can be one of the following:
06
Not enough storage to allocate buffer for the list of workstations set in the WSCLASS parameter.
07
Duplicate definition for the same workstation, identified by WS. This not allowed.
10
The workstation name specified starts with a number: this is not allowed.
The controller initialization is terminated.
Correct the values set for JTOPTS WSCLASS, and restart the controller.

EQQN244E

WSSYSAFF SYSNAME DEFINITION FOR WS IS DUPLICATED.

The controller detected a duplicated value for the system SYSNAME associated with workstation WS in JTOPTS WSYSAFF. This is not allowed.
The controller initialization is terminated.
Correct the values set for JTOPTS WSSYSAFF and restart the controller.

EQQN245I

THE FOLLOWING WORKSTATIONS SUPPORT JOB CLASS FORCING BECAUSE JTOPTS WSCLASS IS SET:

The MODIFY command DWSCLASS was issued to display the workstations for which you set the class forcing with JTOPTS WSCLASS. This message is the response. It is followed by message EQQN233I showing the list of workstations.
Processing continues.
None.

EQQN246W

WORKSTATION WS IS ALREADY DEFINED IN WSCLASS. NO ACTION DONE.

A MODIFY command was issued to add the workstation WS to the WSCLASS parameter of JTOPTS, but that workstation name is already set in the parameter.
The command is ignored.
None.

EQQN247I

WORKSTATION WS ADDED IN WSCLASS.

A MODIFY command was issued to add the workstation WS to the WSCLASS parameter of JTOPTS. The command was run successfully.
Processing continues.
None.

EQQN251I

CURRENT VALUE FOR JTOPTS SAVEJSUB IS YES. THE FOLLOWING JOB SUBMISSION OPTION VALUES ARE USED: HOSTJSUB HOSTJSUB, ZCENJSUB ZCENJSUB

This message is issued at controller startup. It shows the current values set for HOSTJSUB, and ZCENJSUB parameters.
Processing continues.
None.

EQQN252E

A JOB TRACKING RECORD IS NOT COHERENT FOR APAR: APARNAME

The subsystem cannot reapply the job-tracking (JT) record to the current plan. The JT record event is logged in the JT or JTARC file. This error might be caused by an incorrect maintenance level of the subsystem.
The Z controller abends with abend code U3999.
Stop the Z controller and restore the PTFs related to the APAR indicated in the message. Start the Z controller by setting CURRPLAN(NEW) in the JTOPTS statement. Re-apply the PTFs as described in the PTFs text.

EQQN253W

A USER INTERFACE TRYING TO MODIFY THE CURRENT PLAN IS NOT AT THE CORRECT LEVEL OF APAR: APARNAME

An application program or user interface with a level of code different from the subsystem, has tried to connect to the subsystem.
The request is rejected. Processing continues.
Ensure that the application program or user interface is at the same maintenance level of the subsytem to which you want to connect.

EQQN254W

A JOB TRACKING RECORD IS NOT COHERENT WITH SUBSYSTEM LEVEL

The subsystem cannot reapply the job-tracking (JT) record to the current plan. This error might be caused by an inadequate maintenance level of the subsystem. The JT record event is logged in the JT or JTARC file.
The JT record is not applied. Processing continues.
Ensure that the objects in the current plan that are affected by the discarded record have the status that you expect.