EQQZ000 - EQQZ908

EQQZ000I

A STOP COMMAND HAS BEEN RECEIVED

The HCL Workload Automation for Z started task has received an operator stop command.

HCL Workload Automation for Z posts all active subtasks for termination and terminates when all subtasks have terminated.

EQQZ001E

JES IS NOT ACTIVE. THE SCHEDULER CANNOT START

The HCL Workload Automation for Z subsystem could not start because no primary JES subsystem is active.

The subsystem task module, EQQMAJOR, is terminated.

Wait for JES to start and reissue the start command.

EQQZ002E

THE PRODUCT SUBSYSTEM IS ALREADY ACTIVE. IT CANNOT START AGAIN

An operator START command has been entered for a HCL Workload Automation for Z subsystem that is already active.

The second attempt to invoke HCL Workload Automation for Z is terminated.

If you want to restart the HCL Workload Automation for Z subsystem, stop it and issue the START command.

EQQZ003E

INVALID JOBNAME JOBNAME. NAME MUST BE 4 CHARACTERS OR LESS

The HCL Workload Automation for Z subsystem task module, EQQMAJOR, has been incorrectly invoked.

The EQQMAJOR module is terminated.

Change the name of the HCL Workload Automation for Z subsystem started task to one of the subsystem names defined in SYS1.PARMLIB and reissue the start command.

EQQZ004E

UNABLE TO ATTACH SUBTASK SUBTASK

An error occurred when the HCL Workload Automation for Z subsystem attempted to attach the subtask SUBTASK.

HCL Workload Automation for Z continues processing.

Correct all errors and restart HCL Workload Automation for Z.

Review earlier messages in the HCL Workload Automation for Z message log and SYSLOG data sets to determine the exact reason for this message. One possibility is that HCL Workload Automation for Z is being started in a region that is too small.

EQQZ005I

SUBTASK SUBTASK IS BEING STARTED

The HCL Workload Automation for Z subsystem has successfully attached the subtask SUBTASK.

HCL Workload Automation for Z continues processing. If the startup process is successful, the subtask issues its own start message.

EQQZ006I

NO ACTIVE PRODUCT SUBTASKS. THE SCHEDULER IS ENDING

All HCL Workload Automation for Z subtasks have terminated. The HCL Workload Automation for Z subsystem is about to enter its own termination process.

The HCL Workload Automation for Z subsystem frees all acquired resources and is terminated.

EQQZ007E

JOBNAME JOBNAME IS NOT A VALID SUBSYSTEM NAME

The HCL Workload Automation for Z subsystem task module, EQQMAJOR, has been incorrectly invoked.

The EQQMAJOR module is terminated.

Change the name of the HCL Workload Automation for Z subsystem started task to one of the subsystem names defined in SYS1.PARMLIB and reissue the start command.

EQQZ008E

THE INITIALIZATION PROGRAM, EQQINIT2, HAS NOT BEEN SUCCESSFULLY EXECUTED. THE PRODUCT SUBSYSTEM IS UNABLE TO START.

The HCL Workload Automation for Z subsystem could not start, because the required CSA resident control blocks could not be located or were invalid. These control blocks are built during IPL by the EQQINIT2 program.

Processing continues.

Correct all errors and restart HCL Workload Automation for Z after an IPL of the z/OS system.

Check that the currently active IEFSSNxx member of SYS1.PARMLIB defines the HCL Workload Automation for Z subsystem correctly. Check also that EQQINIT2 is present in SYS1.LINKLIB or in a library in the LNKLSTxx concatenation of libraries. Review the master console messages issued during IPL.

EQQZ010E

MEMBER MEMBER CANNOT BE FOUND IN PARAMETER LIBRARY

The parameter library member MEMBER could not be found in the library defined by the EQQPARM DD statement.

The HCL Workload Automation for Z subtask that issues this message is terminated.

Correct all errors and restart the failing subtask.

Check that the EQQPARM DD statement is correctly defined. Check also that the OPCOPTS initialization statement is correctly defined.

EQQZ011E

PARAMETER LIBRARY MEMBER MEMBER IS EMPTY

There are two possibilities:
  • The parameter library member MEMBER exists in the library defined by the EQQPARM DD statement, but there are no records in the member.
  • The data set referenced by the SYSIN DD statement is empty.

The HCL Workload Automation for Z subtask that issues this message is terminated.

Correct all errors and restart the failing subtask.

Check that the EQQPARM DD statement is correctly defined, or that the SYSIN DD statement uses the correct data set name. Check also that the OPCOPTS initialization statement is correctly defined.

EQQZ012E

I/O ERROR READING PARAMETER LIBRARY MEMBER MEMBER

The parameter library member MEMBER could not be read from the library defined by the EQQPARM DD statement.

The HCL Workload Automation for Z subtask that issues this message is terminated.

Correct all errors and restart the failing subtask.

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

EQQZ013I

NOW PROCESSING PARAMETER LIBRARY MEMBER MEMBER

A HCL Workload Automation for Z subtask has started processing the parameter library member MEMBER.

HCL Workload Automation for Z processing continues.

None.

EQQZ014I

MAXIMUM RETURN CODE FOR PARAMETER MEMBER MEMBER IS: MAXCC

A HCL Workload Automation for Z subtask has finished processing the parameter library member MEMBER. MAXCC is the maximum return code encountered for HCL Workload Automation for Z initialization statements in the member.

If the maximum return code is not zero, the HCL Workload Automation for Z subtask that issues this message is terminated.

Correct any initialization errors and, if necessary, restart any failing subtask.

EQQZ015I

INIT STATEMENT: CARD

A HCL Workload Automation for Z subtask that is processing a parameter library member prints the entire member using this message.

HCL Workload Automation for Z processing continues.

None.

EQQZ016I

RETURN CODE FOR THIS STATEMENT IS: MAXCC

A HCL Workload Automation for Z subtask has finished processing an initialization statement. MAXCC is the return code sent by the subtask. It indicates if the statement was successfully processed.

The HCL Workload Automation for Z subtask continues processing initialization statements.

If the return code is not zero, correct all initialization statement errors. If necessary, restart the subtask.

EQQZ017E

RESOURCE NAME SPECIFIED, RESNAME, IS NOT RECOGNIZED

An error has been found while processing the SUBRESOURCES keyword in the AUTHDEF statement.

HCL Workload Automation for Z initialization fails.

Change the list of resource names in the SUBRESOURCES keyword to include only valid resource names.

EQQZ018E

INITIALIZATION STATEMENT SPECIFICATION IS LONGER THAN 455 RECORDS

An initialization statement cannot exceed 455 input records.

HCL Workload Automation for Z initialization fails.

Reduce the total number of records in the statement by entering as many keywords and keyword values per record as possible. You can abbreviate any keyword and can use up to 72 characters of each 80-character record for your specification. For more information, refer to Customization and Tuning

EQQZ019E

DB2 MODULE DB2MOD LOAD FAILED

The DB2 module DB2MOD failed to load during HCL Workload Automation for Z startup.

HCL Workload Automation for Z is stopped.

Check the reason for the failure and correct the problem.

EQQZ020E

COMMAND SPECIFIED, COMMAND, IS NOT RECOGNIZED.

An error has been found while processing the COMMAND keyword in the AUTHDEF statement.

HCL Workload Automation for Z initialization fails.

Modify the list of commands in the COMMAND keyword to include only valid commands.

EQQZ022W

THE SSCM LOAD MODULE SPECIFIED, SSCM, COULD NOT BE LOADED

The module name specified in the SSCMNAME parameter of the OPCOPTS initialization statement could not be found.

Initialization continues, using the EQQSSCMx module defined by IEFSSNxx for HCL Workload Automation for Z event generation.

Check that the module name specified in SSCMNAME is correct and that the module is contained in an APF-authorized library, accessible to HCL Workload Automation for Z either by the STEPLIB DD statement or by the LNKLSTxx concatenation.

EQQZ023W

THE SSCMNAME LOAD MODULE SPECIFIED, SSCM, IS NOT VALID

A module name specified in an SSCMNAME keyword on an OPCOPTS initialization statement is not valid.

The HCL Workload Automation for Z subsystem continues to create event records using the EQQSSCMx module that was loaded during IPL.

Specify a valid HCL Workload Automation for Z event creation routine.

EQQZ024I

BEXTXT

This message contains output from the HCL Workload Automation for Z internal diagnostic routines.

HCL Workload Automation for Z continues normal processing.

None.

EQQZ025E

THE SUBSYSTEM SSNAME IS USING AN INVALID EQQSSCM MODULE

The event creation module, EQQSSCM2, used by the subsystem named in the message is not valid for HCL Workload Automation for Z. This error was discovered during system IPL.

The IPL continues. The subsystem named in the message is active, but the tracking event that it creates is not reliable.

Verify that the correct EQQSSCMx module is accessible to the operating system during the IPL. Check that the SYS1.PARMLIB member IEFSSNxx is correctly updated.

For more information, see HCL Workload Scheduler for Z: Planning and Installation.

EQQZ028E

THE ACTION CHARACTER OF ONE OR MORE OF THE CATMDISP VALUES IS INCORRECT

You have specified an invalid action for a message class in the CATMDISP keyword. The only valid value is Q.

HCL Workload Automation for Z is terminated.

Correct the CATMDISP values and restart HCL Workload Automation for Z.

EQQZ029E

INVALID COMBINATION OF ACTION AND NEW CLASS IN THE CATMDISP KEYWORD

You have specified an invalid combination for the action character and the new class section of the CATMDISP keyword value. A new class must be specified when the action character is Q, meaning that the output is to be requeued to a different class.

HCL Workload Automation for Z is terminated.

Correct the CATMDISP value and restart HCL Workload Automation for Z.

EQQZ030E

THE SCHEDULER WAS UNABLE TO OPEN THE MESSAGE LOG DATA SET

HCL Workload Automation for Z cannot open its message log data set.

The subsystem task module, EQQMAJOR, is terminated.

Correct the errors and reissue the start command.

Check that the EQQMLOG DD statement exists and is correctly coded. Verify that the subsystem started task is authorized to update the message log data set.

EQQZ031E

THE SCHEDULER WAS UNABLE TO OPEN THE MESSAGE LIBRARY FILE

HCL Workload Automation for Z cannot open its message library data set.

The subsystem task module, EQQMAJOR, is terminated.

Correct the errors and reissue the start command.

Check that the EQQMLIB DD statement exists and is correctly coded. Verify that the subsystem started task is authorized to read the message library data set.

EQQZ032E

SIZE OF MESSAGE LIBRARY RECORDS MUST BE 80 BYTES

HCL Workload Automation for Z cannot use its message library data set because the data set does not contain message records of 80 bytes.

The subsystem task module, EQQMAJOR, is terminated.

Correct the errors and reissue the start command.

Check that the EQQMLIB DD statement is correctly coded.

EQQZ033E

THE SCHEDULER IS ENDING. MESSAGE ROUTINE COULD NOT BE INITIALIZED

HCL Workload Automation for Z cannot initialize its message services.

The subsystem task module, EQQMAJOR, is terminated.

Correct the errors and reissue the start command.

Check the previous WTO messages from this subsystem.

EQQZ034I

SUBTASK SUBTASK HAS ENDED. SUBTASK WAS ACTIVE ACTIVE SECONDS AND USED CPUT CPU SECONDS

A HCL Workload Automation for Z subtask has ended after being requested to stop processing. A possible cause might be the lack of a current plan. This message documents how long the subtask was active and how much CPU time it used.

HCL Workload Automation for Z continues normal processing.

None.

EQQZ035E

MAXIMUM QUEUE SIZE (MAXNUM) WAS REACHED ON THE QNAME QUEUE. NUMLOST EVENTS HAVE BEEN LOST

An HCL Workload Automation for Z queue has reached its maximum size and a number of events could not be added. The most likely reason is that HCL Workload Automation for Z has been inactive (not started) for some time and more job tracking events have occurred than could fit into the ECSA buffers available to this HCL Workload Automation for Z subsystem.

QNAME can be one of the following:
WTRQ
The event writer queue
JCCQ
The job completion checker queue
MGRQ
The event manager queue
GENQ
The general service task queue
MSGQ
The HCL Workload Automation for Z message queue
RTRQ
The data router queue
NCFQ
The NCF queue
SUBQ
The submit queue
TWSQ
The end-to-end queue

HCL Workload Automation for Z continues processing.

If the message is issued for the WTRQ of a production HCL Workload Automation for Z subsystem that is being started during IPL, increase the maximum ECSA space for event buffering by changing the definition of the subsystem in SYS1.PARMLIB. If the message is issued for a queue other than WTRQ, contact the Software Support.

This message is sometimes issued for the WTRQ of a test HCL Workload Automation for Z system that is started only infrequently. If the message is issued for a production system, the error may be caused by an unusually long delay in starting HCL Workload Automation for Z or by insufficient ECSA storage for HCL Workload Automation for Z event buffering.

EQQZ036E

ERROR RETRIEVING INFORMATION FOR DDNAME = DDNAME DYNALLOC RETCODE = RC, INFO CODE = INFO, REASON CODE = RSN

HCL Workload Automation for Z tried to retrieve information from the definition of a HCL Workload Automation for Z ddname, but failed.

The task issuing this message is terminated.

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

Use the DYNALLOC return code and reason code to determine the cause of the error. For more information, refer to the appropriate DYNALLOC documentation for the currently active system.

EQQZ037E

A REQUIRED DD-CARD IS MISSING. DDNAME = DDNAME

An EQQMLOG, EQQCKPT, EQQCP1DS, or EQQJT1DS DD statement is needed, to start HCL Workload Automation for Z in the manner defined by the current input parameter statements.

If the EQQMLOG DD statement is missing, the subsystem task module, EQQMAJOR, is terminated. If one of the other DD statements is missing, the normal mode manager subtask is terminated.

Add the missing DD statement to the started task procedure and restart the HCL Workload Automation for Z subsystem.

EQQZ038E

TWO PRODUCT SYSTEMS CANNOT USE THE SAME MESSAGE LOG DATA SET

You tried to start a HCL Workload Automation for Z subsystem or batch job that does not have an EQQMLOG DD statement or the message log data set is being used by another HCL Workload Automation for Z subsystem or batch job.

The subsystem or batch job is terminated.

Change the definition of the EQQMLOG DD statement and restart the HCL Workload Automation for Z subsystem or batch job. If the message is issued for a program interface job, give the failing INIT request a unique message log ddname. Use the MLOGDDN argument.

EQQZ039E

DATA SET CONFLICT. THE DATA SET DEFINED BY DDNAME DDNAME IS USED BY ANOTHER PRODUCT SYSTEM. DSNAME IS DSNAME

You tried to start a HCL Workload Automation for Z subsystem using an output data set that is being used by another HCL Workload Automation for Z subsystem.

The subsystem is terminated.

Change the definition of the DD statement and restart the HCL Workload Automation for Z subsystem.

EQQZ040E

NCF APPLICATION NAME IS REQUIRED WHEN NCFTASK(YES) IS SPECIFIED

The NCFAPPL keyword is required, because you specified NCFTASK(YES) in the OPCOPTS initialization statement.

The subsystem is terminated.

Add the NCFAPPL keyword to the OPCOPTS statement and restart the HCL Workload Automation for Z subsystem.

EQQZ041E

THE ERDRTASK KEYWORD SPECIFIES A VALUE THAT IS NOT IN THE RANGE 0 - 16

The ERDRTASK keyword on the OPCOPTS initialization statement specifies an invalid value.

HCL Workload Automation for Z initialization fails.

Change the ERDRTASK value to a number within the range 0–16 and restart HCL Workload Automation for Z.

EQQZ042E

ONE OR MORE EVENT READER MEMBER NAMES ARE NOT DEFINED

The ERDRPARM keyword on the OPCOPTS initialization statement does not define enough member names. The number of member names must be equal to the number of reader tasks to be started. This number is defined by the ERDRTASK keyword.

HCL Workload Automation for Z initialization fails.

Change the ERDRTASK value or the number of names in the ERDRPARM list and restart HCL Workload Automation for Z.

EQQZ043E

DUPLICATE NAMES IN THE EVENT READER MEMBER NAME LIST

The ERDRPARM keyword on the OPCOPTS initialization statement specifies the same member name more than once.

HCL Workload Automation for Z initialization fails.

Change the ERDRPARM member name list so that all names are specified only once and restart HCL Workload Automation for Z.

EQQZ044E

TOO MANY NAMES IN THE EVENT READER MEMBER NAME LIST

The ERDRPARM keyword on the OPCOPTS initialization statement defines too many member names. The number of member names must be equal to the number of reader tasks to be started. This number is defined by the ERDRTASK keyword.

HCL Workload Automation for Z initialization fails.

Change the ERDRTASK value or the number of names in the ERDRPARM list and restart HCL Workload Automation for Z.

EQQZ045E

SUBTASK SUBTASK ENDED UNEXPECTEDLY

An HCL Workload Automation for Z subtask ended without having been requested to terminate.

HCL Workload Automation for Z processing continues.

If possible, use an HCL Workload Automation for Z Modify command to restart the failing subtask. Ensure that before restarting the subtask, you review earlier messages to correct the error.

Review earlier messages in the HCL Workload Automation for Z message log to determine the exact reason for this message. Check if a dump has been created on any dump data set allocated to the HCL Workload Automation for Z started task.

EQQZ046E

EQQMLOG DD CARD MISSING OR MESSAGE LOG NOT AVAILABLE

The EQQMLOG DD CARD is not valid or the message log data set is being used by another HCL Workload Automation for Z subsystem or batch job.

The subsystem or batch job is terminated.

Change the definition of the EQQMLOG DD statement and restart the HCL Workload Automation for Z subsystem or batch job. If the message is issued for a program interface job, assign a unique message log ddname to the failing INIT request by using the MLOGDDN.

EQQZ047E

THE GSTASK KEYWORD SPECIFIES A VALUE THAT IS NOT IN THE RANGE 1 - 5

The GSTASK keyword in the OPCOPTS initialization statement specifies an invalid value.

HCL Workload Automation for Z initialization fails.

Change the GSTASK value to a number within the range 1-5 and restart HCL Workload Automation for Z.

EQQZ048I

A MODIFY COMMAND HAS BEEN PROCESSED. MODIFY SSNAME,FPARAM

An HCL Workload Automation for Z modify command has been processed successfully.

HCL Workload Automation for Z processing continues.

None.

EQQZ049W

AN INCORRECT MODIFY COMMAND HAS BEEN IGNORED. MODIFY SSNAME,FPARAM

A HCL Workload Automation for Z Modify command could not be processed because parameters on the modify command could not be recognized or they are inappropriate.

The incorrect command is ignored. HCL Workload Automation for Z processing continues.

Change the Modify command and issue it again.

Check that the syntax of the Modify command is correct. If it is correct, you probably have attempted to start a function that is already active or to stop a function that is not active.

EQQZ050W

THE PRODUCT SUBSYSTEM HAS BEEN CANCELLED

An operator cancel command has been received.

HCL Workload Automation for Z terminates without waiting for subtasks to end.

None.

EQQZ051E

THE PRODUCT SUBSYSTEM MOTHER TASK HAS ABENDED

A severe error has occurred in the HCL Workload Automation for Z subsystem task.

HCL Workload Automation for Z terminates without waiting for subtasks to end. If a dump data set is allocated, a dump is created.

Save the message log data set containing this error message, the dump data set, and the SYSLOG data set. Contact the Software Support.

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

EQQZ052E

THE PARAMETER LIBRARY FILE, DDNAME = EQQPARM OR DDNAME = EQQYPARM, COULD NOT BE OPENED.

HCL Workload Automation for Z could not open the parameter library file, ddname EQQPARM or EQQYPARM, which is a required input data set for HCL Workload Automation for Z.

HCL Workload Automation for Z is terminated. Message EQQZ054E is issued.

Check that ddname EQQPARM or EQQYPARM is correctly specified and that the HCL Workload Automation for Z started task is authorized to open the data set for input. Correct all errors and restart HCL Workload Automation for Z.

EQQZ053E

LOGICAL RECORD SIZE FOR THE PARAMETER LIBRARY, DDNAME EQQPARM, IS NOT VALID

HCL Workload Automation for Z cannot use the parameter library data set, ddname EQQPARM, because its logical record length is not 80 bytes.

HCL Workload Automation for Z is terminated. Message EQQZ054E is issued.

Check that EQQPARM is correctly defined. Correct all errors and restart HCL Workload Automation for Z.

EQQZ054E

ERRORS DETECTED PROCESSING PRODUCT PARAMETERS. THE SCHEDULER IS ENDING

HCL Workload Automation for Z found one or more errors while processing its initialization member.

HCL Workload Automation for Z initialization fails.

Correct all errors and restart HCL Workload Automation for Z.

EQQZ055E

THE INTERNAL READER FILE, DDNAME = EQQBRDS, COULD NOT BE OPENED

HCL Workload Automation for Z could not open the internal reader data set.

HCL Workload Automation for Z is terminated. Message EQQZ054E is issued.

Check that ddname EQQBRDS is correctly specified. Correct all errors and restart HCL Workload Automation for Z.

EQQZ056E

THE LOOP LOG DATA SET EQQLOOP COULD NOT BE OPENED

HCL Workload Automation for Z cannot open the EQQLOOP data set.

EQQBATCH module terminates.

Correct the errors and run the daily plan batch process again.

Check that the EQQLOOP DD statement exists and it is correct. Verify that the daily plan batch process is authorized to update the loop log data set.

EQQZ057E

EQQLOOP DD CARD MISSING OR LOOP MESSAGE LOG NOT AVAILABLE

The EQQLOOP DD CARD is not valid or the loop message log data set is being used by another batch job.

The batch job is terminated.

Change the definition of the EQQLOOP DD statement and restart the batch job.

EQQZ058E

THE BEX INTERFACE MODULE, EQQBEX, COULD NOT BE LOADED

HCL Workload Automation for Z could not locate the HCL Workload Automation for Z service routine interface load module EQQBEX.

Normal mode manager (NMM) initialization fails.

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

EQQZ059E

DD-CARD EQQJTABL MISSING OR LOG DATA SET NOT AVAILABLE.

The current plan contains at least one critical job, but you did not specify the EQQJTABL data set in the controller start procedure JCL.

The NMM task initialization fails.

Specify the EQQJTABL data set in the controller start procedure JCL, then stop and restart the NMM task using the MODIFY command or restart the controller.

EQQZ060E

THE SYSOUTDISP VALUE, DISP, IS NOT RECOGNIZED

The first character of the SYSOUTDISP value is not one of the four valid characters: blank, H, R, or D.

The job-completion checker initialization fails.

Change the SYSOUTDISP value and restart the job-completion checker.

EQQZ061E

THE INCDSN VALUE MUST NOT CONTAIN A MEMBER NAME. THE FILE MUST BE SEQUENTIAL

The INCDSN keyword on the JCCOPTS initialization statement must specify the name of a sequential, cataloged, disk resident data set.

The job-completion checker initialization fails.

Change the INCDSN value and restart the job-completion checker.

EQQZ062W

THE START/STOP USER EXIT MODULE COULD NOT BE LOADED

HCL Workload Automation for Z could not locate the subsystem start/stop exit load module EQQUX000.

The subsystem start/stop exit is not used by HCL Workload Automation for Z.

If the subsystem start/stop exit is meant to be used, make sure that the EQQUX000 load module is present in a library that can be reached by HCL Workload Automation for Z. Restart the HCL Workload Automation for Z started task.

EQQZ063E

JCCTASK(YES) AND JCCTASK(DST) NEED EWTRTASK(YES)

The job-completion checker can only be started when the event writer is also started.

HCL Workload Automation for Z initialization fails.

Correct all errors and restart HCL Workload Automation for Z.

EQQZ064I

THE SCHEDULER WILL USE THE NJE NODE NAME NJENODE FOR JOBS HELD ON THIS NODE

During initialization of the event writer, HOLDJOB(YES) or HOLDJOB(USER) was encountered. This message displays the name of the network job entry (NJE) node that HCL Workload Automation for Z uses for reader events created on this node.

HCL Workload Automation for Z processing continues.

Check that the NJE node name is correct. If the NJE node name is not correct, check the installation of the JES2 EXIT7 or the JES3 IATUX29, as appropriate. If the shipped EQQEXIT macro has been user-modified, make sure that it does not prevent or filter the tracking of HCL Workload Automation for Z itself.

EQQZ065I

THE SCHEDULER RELEASES HELD JOBS USING THE JES2 COMMAND CHARACTER CMDCHAR

During initialization of the event writer, HOLDJOB(JES) or HOLDJOB(USER) was encountered. This message displays the JES command character that HCL Workload Automation for Z uses to release JES2 jobs from hold.

HCL Workload Automation for Z processing continues.

Check that the correct command character is displayed. If the command character is not correct, check the installation of the JES2 EXIT7. If the shipped EQQEXIT macro has been user-modified, make sure that it does not prevent or filter the tracking of HCL Workload Automation for Z itself.

EQQZ066W

THE SCHEDULER HAS NOT BEEN ABLE TO DETERMINE THE JES TYPE. JES3 IS ASSUMED.

HCL Workload Automation for Z could not determine whether it is running on a JES2 or a JES3 system. NJENODE is the name of this network job entry (NJE) node.

Processing continues. A JES3 system is assumed.

Check the installation of the JES2 EXIT7 or JES3 IATUX29, as appropriate. If the shipped EQQEXIT macro has been user-modified, make sure that it does not prevent or filter the tracking of HCL Workload Automation for Z itself.

EQQZ067E

COMMAND SYNTAX ERROR: CARD FURTHER STATEMENT PROCESSING STOPPED

The statement contains a syntactically incorrect command.

A possible cause for this error is when the start (/*) and end (*\) comment delimiters are not used on the same record line.

No more statements are processed. The program is terminated with a return code of 8.

Correct the error.

For problems related to the start and end comment delimiters, ensure they are specified for each record line.

EQQZ068E

CMD IS AN UNKNOWN COMMAND AND WILL NOT BE PROCESSED FURTHER STATEMENT PROCESSING IS STOPPED

HCL Workload Automation for Z has detected an unknown command in this statement.

No more statements are processed. The program is terminated with a return code of 8.

Correct the error.

EQQZ069W

EQQSDUMP DDNAME IS MISSING

The subsystem job-step task could not find the ddname EQQSDUMP in the JCL.

The subsystem job-step task sends any dump triggered on a message number to the SYS1.DUMP data sets.

None

If necessary, include the DD name EQQSDUMP in the HCL Workload Automation for Z started-task procedure, and restart HCL Workload Automation for Z.

None

None

Check if your customization of HCL Workload Automation for Z involves sending message triggered dumps to SYS1.DUMP data sets.

EQQZ070E

THE SSCMNAME KEYWORD SPECIFIES AN OPTION THAT IS NOT RECOGNIZED

The SSCMNAME keyword on the OPCOPTS initialization statement specifies a load option that is not supported.

HCL Workload Automation for Z initialization fails.

Change the SSCMNAME option to one of the supported values, TEMPORARY or PERMANENT, or remove the currently specified value to let the option default, and restart HCL Workload Automation for Z.

EQQZ071E

OPTION PERMANENT FOR THE SSCMNAME KEYWORD REQUIRES THE BUILDSSX KEYWORD

The SSCMNAME keyword on the OPCOPTS initialization statement specifies the PERMANENT load option. This is supported only when the BUILDSSX keyword has been specified.

HCL Workload Automation for Z initialization fails.

Add the BUILDSSX keyword to the OPCOPTS initialization statement and restart HCL Workload Automation for Z.

EQQZ072W

OPTION PERMANENT FOR THE SSCMNAME KEYWORD REQUIRES STEPLIB DD-STATEMENT

The SSCMNAME keyword on the OPCOPTS initialization statement specifies the PERMANENT load option. This is supported only when a STEPLIB DD statement has been defined.

HCL Workload Automation for Z starts without loading the SSCM module permanently.

Add a STEPLIB DD statement to the JCL used to start the subsystem and restart HCL Workload Automation for Z.

EQQZ073I

THE SCHEDULER HAS RECOGNIZED THAT THIS IS A JESTYPE SYSTEM WITH COMMAND CHARACTER CMDCHAR AND THAT THE NJE NODE NAME IS NJENODE

JESTYPE is JES2 or JES3. CMDCHAR is the command character that HCL Workload Automation for Z uses when issuing JESx commands. NJENODE is the name of this network job entry (NJE) node.

Processing continues.

If JESTYPE, CMDCHAR, or NJENODE is not correct, check the installation of the JES2 EXIT7 or JES3 IATUX29, as appropriate. If the shipped EQQEXIT macro has been user-modified, make sure that it does not prevent or filter the tracking of HCL Workload Automation for Z itself.

EQQZ074W

THE SCHEDULER HAS NOT BEEN ABLE TO DETERMINE NJE NODE NAME FOR THIS SYSTEM

The NJENODE parameter was not specified. During initialization of the event writer, HCL Workload Automation for Z was unable to determine the name of the network job entry (NJE) node for this system.

Processing continues.

Check the installation of the JES2 EXIT7 or JES3 IATUX29, as appropriate. If the shipped EQQEXIT macro has been user-modified, make sure that it does not prevent or filter the tracking of HCL Workload Automation for Z itself.

EQQZ075W

THE JES2 COMMAND CHARACTER MAY BE INCORRECT

The JES2 command character that HCL Workload Automation for Z uses (stated in message EQQZ073I) may be incorrect.

Processing continues.

If the JES2 command character is incorrect, check the installation of the JES2 EXIT7 or JES3 IATUX29, as appropriate. If the shipped EQQEXIT macro has been user-modified, make sure that it does not prevent or filter the tracking of HCL Workload Automation for Z itself.

EQQZ076E

THE EVENT DATA SET IS ALREADY IN USE. IT CANNOT BE SHARED.

The event data set identified by the EQQEVDS card in the HCL Workload Automation for Z subsystem, is being used by another subsystem.

HCL Workload Automation for Z stops processing.

Use a different data set as the event data set, and restart HCL Workload Automation for Z.

EQQZ077W

MISSING KEYWORD KEYWORD: THE DEFAULT DEFAULT IS USED

The parameter keyword in a statement is missing: the default value is used.

Processing continues.

None.

EQQZ078W

INVALID KEYWORD VALUE: THE DEFAULT DEFAULT IS USED

The value specified for the keyword is not valid: the default value is used.

Processing continues.

None.

EQQZ079W

KEYWORD VALUE IS TOO LONG: THE DEFAULT DEFAULT IS USED

The value specified for the keyword is too long: the default value is used.

Processing continues.

None.

EQQZ080I

A STOP COMMAND HAS BEEN RECEIVED

The HCL Workload Automation for Z address space has received an operator stop command.

HCL Workload Automation for Z posts all active subtasks for termination and terminates when all subtasks have terminated.

None.

EQQZ081E

VARFAIL VALUE INVALID. AT MAXIMUM ONLY 3 CHARACTERS &, %, ? ARE ALLOWED. CHARACTERS CANNOT BE REPEATED

The VARFAIL keyword contains a value different from the three characters that are allowed.

HCL Workload Automation for Z initialization fails.

Correct the value (or values) in the VARFAIL keyword and restart HCL Workload Automation for Z.

EQQZ082W

DATABASE CONNECTION OBJ LOAD MODULE COULD NOT BE LOADED.

The scheduler could not locate the load module OBJ needed by the parser process for the DBOPT statement.

The initialization of the server started task fails.

Ensure that the server references a library that contains the OBJ load module, then restart the server.

EQQZ083E

INVALID JOBNAME JOBNAME. NAME MUST BE 4 CHARACTERS OR LESS

The HCL Workload Automation for Z subsystem task module, EQQMAJOR, has been incorrectly invoked.

The EQQMAJOR module is terminated.

Change the name of the HCL Workload Automation for Z subsystem started task to one of the subsystem names defined in SYS1.PARMLIB and reissue the start command.

EQQZ084E

UNABLE TO ATTACH SUBTASK SUBTASK

An error occurred when the HCL Workload Automation for Z subsystem attempted to attach the subtask SUBTASK.

HCL Workload Automation for Z continues processing.

Correct all errors and restart HCL Workload Automation for Z.

Review earlier messages in the HCL Workload Automation for Z message log and SYSLOG data sets to determine the exact reason for this message. One possibility is that HCL Workload Automation for Z is being started in a region that is too small.

EQQZ085I

SUBTASK SUBTASK IS BEING STARTED

The HCL Workload Automation for Z subsystem has successfully attached the subtask SUBTASK.

HCL Workload Automation for Z continues processing. If the startup process is successful, the subtask issues its own start message.

None.

EQQZ086I

NO ACTIVE SUBTASKS. THE SCHEDULER IS ENDING

All HCL Workload Automation for Z subtasks have terminated. The HCL Workload Automation for Z address space is about to enter its own termination process.

The HCL Workload Automation for Z address space frees all acquired resources and is terminated.

None.

EQQZ087E

JOBNAME JOBNAME IS NOT A VALID SUBSYSTEM NAME

The HCL Workload Automation for Z subsystem task module, EQQMAJOR, has been incorrectly invoked.

The EQQMAJOR module is terminated.

Change the name of the HCL Workload Automation for Z subsystem started task to one of the subsystem names defined in SYS1.PARMLIB and reissue the start command.

EQQZ088E

THE INITIALIZATION PROGRAM, EQQINIT, HAS NOT BEEN SUCCESSFULLY EXECUTED. THE PRODUCT SUBSYSTEM IS UNABLE TO START

The HCL Workload Automation for Z subsystem could not start because the required CSA resident control could not be located or was invalid. These control blocks are built during IPL by the EQQINIT program.

The subsystem task module, EQQMAJOR, is terminated.

Correct all errors and restart HCL Workload Automation for Z after an IPL of the z/OS system.

Check that the currently active IEFSSNxx member of SYS1.PARMLIB defines the HCL Workload Automation for Z subsystem correctly. Check also that EQQINIT is present in SYS1.LINKLIB or in a library in the LNKLSTxx concatenation of libraries. Review the master console messages issued during IPL.

EQQZ090W

THE NOERROR VALUE, VALUE, IS INCORRECTLY SPECIFIED

A NOERROR statement or the NOERROR keyword of the JTOPTS contains an error. Entry VALUE is not valid.

Depending on how you specified the NOERROR value, the normal mode manager (NMM) processing continues or terminates:
  • If you specified the NOERROR value in the EQQPARM library, the NMM subtask terminates.
  • If you specified the NOERROR value by using a MODIFY command, the NMM processing continues.

Correct the entry. If the NMM subtask terminated, restart the subtask or the scheduler address space, otherwise reenter the MODIFY command.

EQQZ091W

WRONG NUMBER OF PERIODS IN THE NOERROR VALUE, VALUE

A NOERROR statement or the NOERROR keyword of JTOPTS contains an error. Entry VALUE is not valid. The number of periods in each entry must be either zero or three.

The normal mode manager (NMM) is terminated.

Correct the entry and restart the NMM subtask or the HCL Workload Automation for Z address space.

EQQZ092W

PERIODS ARE NOT PLACED CORRECTLY IN THE NOERROR VALUE, VALUE

A NOERROR statement or the NOERROR keyword of JTOPTS contains an error. Entry VALUE is not valid. The periods in an entry must be separated by not less than one and not greater than eight nonblank characters.

The normal mode manager (NMM) is terminated.

Correct the entry and restart the NMM subtask or the HCL Workload Automation for Z address space.

EQQZ093E

FILE KEYWORD IS MISSING

The current AUDIT statement does not contain the FILE keyword.

The normal mode manager (NMM) is terminated.

Add the FILE keyword to the current AUDIT statement and restart the HCL Workload Automation for Z subsystem.

EQQZ094E

A PARAMETER IS REQUIRED FOR THE FILE KEYWORD

The FILE keyword in the current AUDIT statement does not specify a value.

The normal mode manager (NMM) is terminated.

Add the FILE keyword to the current AUDIT statement and restart the HCL Workload Automation for Z subsystem.

EQQZ095I

GENSERV: STG CPLOCK: STC EVENTS: STE WSATASK: STW EVELIM VALUE: EVE STATIM VALUE: STA

This message is issued after the /F subsys,DSPSTA command has been given. It indicates whether the keywords GENSERV, CPLOCKS, EVENTS, and WSATASK have been activated. (These are activated either by the STATIM initial parameter statement or by the appropriate modify command.) The message also displays the current value of the EVELIM and STATIM keywords. These values can be used to specify how often statistics messages are issued.

The values of the message variables are:
STG
Active if GENSERV statistic messaging is currently active. Otherwise, Inactive.
STC
Active if CPLOCK statistic messaging is currently active. Otherwise, Inactive.
STE
Active if EVENTS statistic messaging is currently active. Otherwise, Inactive.
STW
Active if WSATASK statistic messaging is currently active. Otherwise, Inactive.
EVE
The current value of the EVELIM parameter, which can be in the range 0-9999.
STA
The current value of the STATIM parameter, which can be in the range 0-99.

Processing continues.

None.

None.

EQQZ096W

OBSOLETE PARAMETER SPECIFIED:keyword. THE PARAMETER IS IGNORED

The keyword shown in the message text is obsolete and is no longer supported.

The initialization of the scheduler or data store continues and the obsolete keyword is ignored.

Correct the scheduler or data store initialization statements to avoid the warning messages at the next restart.

EQQZ097W

END-TO-END OBJ LOAD MODULE COULD NOT BE LOADED

The scheduler could not locate the load module shown in the message text for the end-to-end function.

The initialization of the scheduler main task continues but it is not be possible to the use the end-to-end function.

Ensure that the Topology load module shown in the message text is present in a library that can be reached by the scheduler, then restart the controller.

EQQZ098W

JESLOG SPIN PREVENTION NEEDED BUT NOT APPLIED FOR JES: JESFMID. IT WAS NOT APPLIED BECAUSE OF PARAMETER SETTING.

The SPIN keyword has been set to YES in the OPCOPTS statement to enable to JESLOG SPIN usage while Restart and Clean up or Job Completion Checker tasks are running. An error can occur if you do not disable the usage of the JESLOG SPIN.

Processing continues.

None.

EQQZ099E

SAVARFAIL VALUE NOT VALID. AT MAXIMUM & , % CAN BE SPECIFIED TOGETHER. CHARACTERS CANNOT BE REPEATED.

The SAVARFAIL parameter contains a value different from the only two variable characters allowed: & and %. The variable characters cannot be specified more than once.

HCL Workload Automation for Z initialization fails.

Correct the value for the SAVARFAIL parameter and restart HCL Workload Automation for Z.

EQQZ100E

THE GMTOFFSET VALUE IS REQUIRED AND MUST BE AN INTEGER

The GMTOFFSET keyword specifies an incorrect value. The value is required and it must be a positive or negative integer.

HCL Workload Automation for Z considers the current initialization statement to be incorrectly coded. This causes HCL Workload Automation for Z initialization to fail.

Correct the GMTOFFSET value and restart HCL Workload Automation for Z.

EQQZ101E

THE GMTOFFSET VALUE MUST BE IN THE RANGE -1439 TO +1439

The GMTOFFSET keyword specifies a value that is outside the range of valid values.

HCL Workload Automation for Z considers the current initialization statement to be incorrectly coded. This causes HCL Workload Automation for Z initialization to fail.

Correct the GMTOFFSET value and restart HCL Workload Automation for Z.

EQQZ102E

THE SAME SYSTEM ID OCCURS MORE THAN ONCE IN THE SYSID KEYWORD

The same system ID occurs more than once in the SYSID keyword of the ROUTOPTS initialization statement. HCL Workload Automation for Z cannot determine to which system ID the DESTID should be connected.

HCL Workload Automation for Z initialization fails and the subsystem is terminated.

Correct the SYSID keyword values and restart HCL Workload Automation for Z.

EQQZ103W

THE SAME DESTINATION ID OCCURS MORE THAN ONCE IN THE DESTID KEYWORD

The same destination ID occurs more than once in the DESTID keyword of the ROUTOPTS initialization statement.

HCL Workload Automation for Z processing continues.

Verify the SYSID and DESTID keywords and, if necessary, change them.

EQQZ104E

UNPAIRED NUMBER OF SYSTEM IDS AND DESTINATIONS

The number of values in the SYSID keyword of the ROUTOPTS initialization statement does not match the number of values in the DESTID keyword.

HCL Workload Automation for Z initialization fails and the subsystem is terminated.

Change the SYSID and DESTID keywords so that they contain the same number of values and restart HCL Workload Automation for Z.

EQQZ105W

THE DST VALUE IS NO LONGER SUPPORTED FOR THE JCCTASK PARAMETER

You have specified JCCTASK (DST) but this value is no longer supported. This is because the Data Store does no longer uses the class re-queuing mechanism to retrieve joblogs.

HCL Workload Automation for Z continues processing. JCC is not started.

Specify one of the supported values. For information about the supported values, see the Customization and Tuning manual, Chapter 1. Defining initialization statements, section, "JCCOPTS".

EQQZ106W

PERCENT % OF QUEUE QNAME IN USE

The utilization of a queue has exceeded a threshold value.

None.

Ensure that all subtasks are active. Check system contention.

EQQZ107E

TOO MANY DASD CONNECTIONS DEFINED

You defined more than 16 destinations in the DASD keyword of the ROUTOPTS initialization statement. A maximum of 16 submit/release data sets can be used at the same time.

HCL Workload Automation for Z initialization fails and the subsystem is terminated.

Change the DASD keyword to specify fewer destinations and restart the subsystem.

EQQZ109I

THE RELATIONAL OPERATOR IN THE NOERROR STATEMENT, VALUE, IS NOT EQ: EQ VALUE IS FORCED.

The scheduler was parsing a NOERROR statement including as error code an HCL Workload Automation for Z -defined code. The statement does not contain EQ as its relational operator. In this case EQ is the only allowed value.

The scheduler overrides the statement in the NOERROR table and the EQ value is forced.

Review your NOERROR statement definitions. Change the VALUE statement to specify the EQ relational operator. You can issue the modify command: /F subsys,LSTNOERR to verify the NOERROR table content.

EQQZ110E

AN XCF CONNECTION HAS BEEN SPECIFIED IN THE OPT STATEMENT, BUT THE XCFOPTS INITIALIZATION STATEMENT IS MISSING

A XCF connection cannot be established between the controller and a tracker because the parameter member being processed does not contain an XCFOPTS initialization statement.

The XCF connection is defined by the XCF keywords in the controller ROUTOPTS statement and the HOSTCON keyword of the tracker TRROPTS statement.

HCL Workload Automation for Z initialization is terminated.

Add the XCFOPTS statement or change the SNA or HOSTCON keyword.

EQQZ111E

AN SNA CONNECTION HAS BEEN SPECIFIED IN THE OPT STATEMENT, BUT NCFTASK(YES) IS NOT SPECIFIED IN OPCOPTS

An SNA connection cannot be established between the controller and a tracker because the OPCOPTS init statement does not contain NCFTASK(YES).

The SNA connection is defined by the SNA keywords in the controller ROUTOPTS statement and the HOSTCON keyword of the tracker TRROPTS statement.

HCL Workload Automation for Z initialization is terminated.

Add the NCFTASK(YES) and NCFAPPL(applid) keywords or change the SNA or HOSTCON keywords.

EQQZ112E

A DESTINATION HAS BEEN SPECIFIED IN THE OPCAV1R2 KEYWORD IN THE ROUTOPTS STATEMENT. THIS DESTINATION IS NOT FOUND IN THE SNA OR THE DASD KEYWORD

A destination specified in the OPCAV1R2 keyword must also be defined in the SNA or DASD keyword.

HCL Workload Automation for Z initialization is terminated.

If the destination represents an OPC/A Version 1 Release 2 NEC system, specify it in the SNA keyword.

If the destination represents an OPC/A Version 1 Release 2 EMS system connected to the controller through shared DASD, specify it in the DASD keyword.

EQQZ113E

THE HOSTCON KEYWORD IN TRROPTS DEFINES AN SNA CONTROLLER CONNECTION, BUT THE SNAHOST KEYWORD IS MISSING

An SNA connection cannot be established between the controller and a tracker because the SNAHOST keyword does not contain the controller VTAM application ID.

The VTAM application ID of the controller is defined in the OPCOPTS initialization statement for the controller, keyword NCFAPPL.

HCL Workload Automation for Z initialization is terminated.

Update the SNAHOST with this ID.

EQQZ114E

THE SNAHOST KEYWORD IN TRROPTS IS SPECIFIED, BUT THE CONTROLLER CONNECTION DEFINED IN THE HOSTCON KEYWORD IS NOT SNA

The initialization statement is inconsistent.

HCL Workload Automation for Z initialization is terminated.

Delete the SNAHOST keyword or update the HOSTCON keyword to specify SNA.

EQQZ115E

THE SAME DESTINATION APPEARS IN MORE THAN ONE OF THE SNA, XCF, USER, TCP, HTTP, AND DASD KEYWORDS IN THE ROUTOPTS STATEMENT

A destination name must be unique within the HCL Workload Automation for Z configuration. A destination can be reached by only one of the supported methods.

HCL Workload Automation for Z initialization is terminated.

Correct the ROUTOPTS statement.

EQQZ116E

AN XCF OR APPC CONNECTION HAS BEEN REQUESTED BUT THE LEVEL OF THE MVS SYSTEM DOES NOT SUPPORT IT

If the XCF keyword of a ROUTOPTS initialization statement or the HOSTCON keyword of a TRROPTS initialization statement requests an XCF destination, your system must be MVS SP 4.1 or later. If the APPC keyword of a ROUTOPTS initialization statement requests an APPC destination, your system must be MVS SP 4.2.2 or later.

HCL Workload Automation for Z initialization is terminated.

Change the ROUTOPTS or TRROPTS initialization statement so that no unsupported destinations are requested.

EQQZ117E

THE TRROPTS STATEMENT IS NOT APPLICABLE FOR A CONTROLLER OR STANDBY SYSTEM

This HCL Workload Automation for Z subsystem is defined as a controller or standby system. The TRROPTS statement is not allowed.

HCL Workload Automation for Z initialization is terminated.

Remove the TRROPTS statement. Use the ROUTOPTS statement to define routing information for a controller or standby system.

EQQZ118E

THE ROUTOPTS STATEMENT IS NOT APPLICABLE AT A TRACKER SYSTEM

This HCL Workload Automation for Z subsystem is defined as a tracker system. The ROUTOPTS statement is not allowed.

HCL Workload Automation for Z initialization is terminated.

Remove the ROUTOPTS statement. Use the TRROPTS statement to define routing information for a tracker system.

EQQZ119E

MORE THAN 1000 DESTINATIONS DEFINED FOR CONNECTION

More than 1000 tracker destinations are defined on the ROUTOPTS statement for connection to the controller.

HCL Workload Automation for Z initialization is terminated.

Connect fewer trackers by redefining the ROUTOPTS statement. If you have more than 1000 trackers, you can create clusters of trackers that use only one connection to the controller. For example, if you have five systems in one data center currently NCF-connected to the controller and the systems share DASD, you can start four event reader subtasks on one of the trackers and have a single VTAM link to the controller.

EQQZ120E

CF FUNCTION FUNCTION FAILED WITH RETURN CODE=RETCODE AND REASON CODE RESCODE

This message lists the service requested, the failed function, the return code, and the reason code.

Depending on what kind of service failed, HCL Workload Automation for Z either continues processing without the requested service or is terminated.

Correct the error and restart the HCL Workload Automation for Z address space.

Review the message log (EQQMLOG) and look for preceding error messages relating to the problem. Use the FUNCTION, RETCODE, and RESCODE to determine the cause of the error:
  • When CF indicates XCF, or APPC and FUNCTION indicates JOINX, refer to the appropriate z/OS SP Authorized Assembler Reference manual (see IXCJOIN macro) for the currently active z/OS system.
  • When CF indicates APPC, function IDEN and code=2C, make sure that the APPC address space is started.
  • For other errors, refer to the appropriate z/OS SP Authorized Callable Services manual for the currently active z/OS system.

EQQZ121E

XCF CONNECTIONS ARE NOT SUPPORTED ON A LOCAL-SYSPLEX

The sysplex mode is LOCAL-SYSPLEX. This configuration is not supported by HCL Workload Automation for Z. Only MULTISYSTEM or MONOPLEX sysplex configurations are supported.

HCL Workload Automation for Z initialization is terminated.

Change the communication method and restart HCL Workload Automation for Z.

EQQZ122E

KEYWORD KEYWORD IN CURRENT INITIALIZATION STATEMENT IS MISSING

The specified keyword in the current initialization statement is required.

HCL Workload Automation for Z initialization is terminated.

Add the missing keyword to the initialization statement and restart HCL Workload Automation for Z.

EQQZ123E

KEYWORD KEYWORD IN TRROPTS INITIALIZATION STATEMENT IS MISSING

The HOSTCON keyword in the TRROPTS initialization statement is missing.

HCL Workload Automation for Z initialization is terminated.

Correct the invalid TRROPTS initialization statement and restart HCL Workload Automation for Z.

EQQZ124E

OWN KW APPEARS AS A DESTINATION IN STMT

The same name appears in one of these keywords:
  • XCFOPTS MEMBER
  • OPCOPTS NCFAPPL
and also one of these keywords:
  • ROUTOPTS SNA
  • ROUTOPTS XCF
  • TRROPTS SNAHOST

This duplication is not allowed.

HCL Workload Automation for Z initialization is terminated.

Correct the invalid initialization statement and restart HCL Workload Automation for Z.

EQQZ125E

CANNOT CONTINUE PROCESSING DUE TO FULL QUEUE: QNAME THE SUBSYSTEM IS TERMINATING

One of the HCL Workload Automation for Z internal queues is full. The subsystem was canceled by the task that added the last element.

The HCL Workload Automation for Z subsystem is terminated.

Restart the HCL Workload Automation for Z subsystem and verify that all subtasks start normally.

Check the HCL Workload Automation for Z message log for EQQZ106W messages indicating which queue is full. Check for other previous messages about the subtask that is processing the queue:
MGRQ
Event manager
MONQ
Tivoli Enterprise Portal (TEP) task
NCFQ
NCF task
SUBQ
Submit task
RTRQ
Data router task

EQQZ126W

THE SYSTEM WHERE THE SCHEDULER HOST IN THE XCF GROUP XCFG WAS RUNNING HAS FAILED. A TAKEOVER BY THE STANDBY HOST XCFSTB MUST BE INITIATED BY THE OPERATOR.

The HCL Workload Automation for Z standby subsystem has detected that the z/OS image on which the HCL Workload Automation for Z host is located is down. If you set the XCFOPTS statement to automatic takeover, the first takeover and subsequent attempt (after 20 seconds) have both failed.

None.

Restart z/OS and the HCL Workload Automation for Z host or use the Modify command to order the HCL Workload Automation for Z standby subsystem to perform a takeover of the controller functions.

EQQZ127W

THE SCHEDULER HOST IN XCF GROUP XCFG HAS FAILED. A TAKEOVER BY THE STANDBY HOST XCFSTB MUST BE INITIATED BY THE OPERATOR.

This HCL Workload Automation for Z standby subsystem has detected that the HCL Workload Automation for Z host is not running.

None.

Restart the HCL Workload Automation for Z host or use the Modify command to order the HCL Workload Automation for Z standby subsystem to perform a takeover.

EQQZ128I

SCHEDULER ACTIVE IN STANDBY MODE

This system has been fully initialized in standby mode.

None.

None.

EQQZ129I

TAKEOVER IN PROGRESS

This system has started takeover processing.

The system continues initialization as the new host.

None.

EQQZ130W

XCF FUNCTION MSGO HAS FAILED DUE TO SIGNALLING FACILITY BUSY

An XCF transmission was not successfully sent.

The system tries to resend it. If the data queue element has not been successfully transmitted within five minutes, it is discarded.

None.

No action is needed unless message EQQZ131W also occurs.

EQQZ131W

THE FOLLOWING OUTBOUND QUEUE ELEMENT HAS BEEN DISCARDED DUE TO REPEATED TRANSMISSION ERRORS: DQE

The system tried for five minutes to send the data queue element, but did not succeed. The data queue element is discarded.

Processing continues.

This message could indicate that insufficient space in the message buffer has been allocated in the transport class. For an explanation of how to use RMF to tune the value of the MAXMSG parameter, refer to z/OS® MVS Setting up a Sysplex.

EQQZ132W

THE FOLLOWING INBOUND QUEUE ELEMENT HAS BEEN DISCARDED DUE TO MISSING EXTENSION BUFFER SEGMENTS: DQE

The system waited five minutes for a minimum of one missing buffer segment, then discarded the data queue element and the incomplete extension buffer.

Processing continues.

None.

EQQZ133W

THE FOLLOWING INBOUND QUEUE ELEMENT WITH MISSING EXTENSION BUFFER SEGMENTS HAS BEEN DISCARDED DUE TO DATA ROUTER TERMINATION: DQE

A data queue element with an incomplete buffer was present when the data router task terminated.

Data router termination continues.

None.

EQQZ134I

A CONTROLLER IS ALREADY ACTIVE WITHIN THE SAME XCF GROUP AS THIS SYSTEM

This system has been started as a host within a HCL Workload Automation for Z XCF group including an active host.

The system is terminated.

Check XCFOPTS for the group keyword value. Check OPCOPTS for the OPCHOST keyword value.

EQQZ135E

THE TRROPTS INITIALIZATION STATEMENT IS REQUIRED FOR A TRACKER SYSTEM

A tracker system was started with no TRROPTS initialization statement.

If OPCHOST(NO) is specified, HCL Workload Automation for Z needs to know how the tracker is connected to the controller. This is defined in the HOSTCON keyword in TRROPTS. The possible connections are:
Shared DASD
The controller and tracker communicate via an event data set and optionally a submit/release data set.
XCF
The controller and tracker communicate via XCF communication links.
SNA
The controller and tracker communicate via VTAM communication links.

HCL Workload Automation for Z initialization fails and the subsystem is terminated.

Add a TRROPTS initialization statement specifying the controller connection type.

EQQZ136E

EMPTY OR UNSPECIFIED EQQPARM PARAMETER LIBRARY MEMBER.

This error is issued for one of the following reasons:
  • A member for the EQQPARM DD statement was not specified
  • The member of the dataset specified by the EQQPARM DD statement is empty

The task that issues this message is terminated.

Check that the EQQPARM DD statement is defined correctly and restart the failing task.

EQQZ138E

THE WAITREL KEYWORD SPECIFIES A VALUE THAT IS NOT IN THE RANGE 0 - 99.

An invalid value has been set for the WAITREL keyword.

HCL Workload Automation for Z uses the WAITREL default value.

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

EQQZ139W

FOR XCF GROUP XCFG HAS BEEN DETECTED A TFAIL. THE SCHEDULER LOCK IS STILL IN USE: A MANUAL TAKEOVER COULD BE NEEDED.

The standby controller belonging to the XCF group XCFG detected that a controller failure or a failure of the system where the primary controller is running occurred. The standby controller failed to get the required lock, even retrying after 20 seconds. For this reason, it is required that a manual /F procname, TAKEOVER command is issued.

The standby controller waits for a manual /F procname, TAKEOVER command.

Check if the primary scheduler is down; in this case, on the standby controller issue the command /F procname, TAKEOVER.

EQQZ140E

YEAR, MONTH, AND DAY MUST ALL BE TWO-DIGIT NUMBERS

A nonnumeric date value has been specified.

Processing continues.

Reenter a numeric date value.

EQQZ141E

YEAR MUST BE IN THE RANGE 00 TO 99

The year value is not valid. Year must be specified as 72 to 99 for years 1972 to 1999 or 00 to 71 for years 2000 to 2071.

Processing continues.

Reenter the date value and specify a year number in the range 00 through 99.

EQQZ142E

MONTH MUST BE IN THE RANGE 1 TO 12

A date value has been specified where the month number is not valid.

Processing continues.

Reenter the date value and specify a month number in the range 1 through 12.

EQQZ143E

DAY MUST BE IN THE RANGE 1 TO 31

A date value has been specified where the day number is not valid.

Processing continues.

Reenter the date value and specify a day number in the range 1 through 31.

EQQZ144E

DAY DD IS NOT VALID IN FEBRUARY

A date value has been specified where the month number is 2 and the day number is greater than 29.

Processing continues.

Reenter the date value and specify a valid day number for February.

EQQZ145E

MONTH MM DOES NOT HAVE 31 DAYS

A date value has been specified with a day value of 31 for a month that only has 30 days.

Processing continues.

Reenter the date value and specify a valid day and month combination.

EQQZ146E

YEAR YY DOES NOT HAVE 29 DAYS IN FEBRUARY

A date value has been specified where the month number is 2 and the day number is 29 but the year is not a leap year.

Processing continues.

Reenter the date value and specify a valid day number for February.

EQQZ147E

HOUR AND MINUTE MUST BOTH BE TWO-DIGIT NUMBERS

A nonnumeric time value has been specified.

Processing continues.

Reenter a numeric time value.

EQQZ148E

HOUR MUST BE IN THE RANGE 0 TO 23

A time value has been specified where the hour number is not valid.

Processing continues.

Reenter the time value and specify an hour number in the range 0 through 23.

EQQZ149E

MINUTE MUST BE IN THE RANGE 0 TO 59

A time value has been specified where the minute number is not valid.

Processing continues.

Reenter the time value and specify a minute number in the range 0 through 59.

EQQZ150I

OLD MESSAGE TRIGGERED DUMP MESSAGE NUMBER(S)

The message (or messages) that triggers a dump has been changed by a Modify command. Message EQQZ152I follows this message, showing the old message number (or numbers).

HCL Workload Automation for Z processing continues.

None.

None.

None.

None.

None.

EQQZ151I

NEW MESSAGE TRIGGERED DUMP MESSAGE NUMBER(S)

The message (or messages) that triggers a dump has been changed by a Modify command. Message EQQZ152I follows this message, showing the new message number (or numbers).

HCL Workload Automation for Z processing continues.

None.

None.

None.

None.

None.

EQQZ152I

MSGNO

The subsystem job-step task uses this message to print the message number (or numbers) that triggers a dump, when this number (or numbers) is changed by a Modify command.

HCL Workload Automation for Z processing continues.

None.

None.

None.

None.

None.

EQQZ153E

TOO MANY USER DESTINATIONS DEFINED

You defined more than 64 destinations in the USER keyword of the ROUTOPTS initialization statement. A maximum of 64 user defined destinations can be used at the same time.

HCL Workload Automation for Z initialization fails and the subsystem is terminated.

Change the USER keyword to specify fewer destinations and restart the subsystem.

EQQZ154E

THE PIFHD KEYWORD IS MISSING OR INVALID

The PIFHD keyword on the INTFOPTS initialization statement is required. You have not defined the keyword or the keyword has an invalid value.

HCL Workload Automation for Z initialization fails and the subsystem is terminated.

Change or add the keyword to the INTFOPTS initialization statement and restart the subsystem.

EQQZ155E

THE CONTENTIONTIME KEYWORD IS INVALID

The value of 0 is invalid.

HCL Workload Automation for Z NMM initialization fails and the NMM task is terminated.

Change or add the CONTENTIONTIME keyword and restart the subsystem.

EQQZ156W

THE CONTENTION TIME VALUE WILL BE IGNORED BECAUSE RESCONT IS MISSING

If RESCONT is not specified, any value specified for CONTENTIONTIME is not taken into consideration.

HCL Workload Automation for Z NMM initialization ends with RC=4, but the NMM continues processing.

Add the missing RESCONT or remove the CONTENTIONTIME keyword.

EQQZ159E

JOBSUBMIT CANNOT BE SPECIFIED IN COMBINATION WITH EITHER ZCENJSUB OR HOSTJSUB, OR BOTH.

In the JTOPTS statement, the JOBSUBMIT parameter was specified in combination with either ZCENJSUB or HOSTJSUB, or both. The JOBSUBMIT parameter is mutually exclusive with ZCENJSUB and HOSTJSUB.

Controller stops processing.

Specify the correct parameters. For example, to activate the job submission on host workstations and deactivate the job sumission on z-centric workstations, specify HOSTJSUB(Y) and ZCENJSUB(N).

JOBSUBMIT is used for backward compatibility and apply to the situation when job submission is activated or deactivated on both host and z-centric workstations.

EQQZ160E

LIBRARY WITH DDNAME EQQJCLIB COULD NOT BE OPENED

HCL Workload Automation for Z could not open a required input data set, ddname EQQJCLIB. This message can be issued:
  • During initialization of the event writer task.
  • When processing a Modify command with the DEPLOYCF or NEWDSLST option.

If the message was issued when processing a Modify command, the configuration file that was previously built remains in effect. If the error occurs during initialization, data set triggering functions are not available.

If the data set triggering function should be active, check that EQQJCLIB is correctly defined and that the HCL Workload Automation for Z started task is authorized to open the data set. Restart the tracker or issue the Modify command when the problem has been corrected.

EQQZ161E

UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF EQQJCLIB

An error occurred when allocating storage to build a data set selection table. This message can be issued:
  • During initialization of the event writer task.
  • When processing a Modify command with the DEPLOYCF or NEWDSLST option.

If the message was issued when processing a Modify command, the data set selection table that was previously built remains in effect. If the error occurs during initialization, data set triggering functions are not available.

Verify that the EQQEVLST or EQQDSLST member in the EQQJCLIB library is not too large. If it is not, determine which product or program, or both, is exhausting ECSA storage. Restart the tracker or issue the Modify command when the problem has been corrected.

EQQZ162W

UNABLE TO FIND MEMBER MEMBER IN EQQJCLIB

HCL Workload Automation for Z could not find the member EQQEVLST or EQQDSLST in the data set referenced by the EQQJCLIB ddname. This message can be issued:
  • During initialization of the event writer task.
  • When processing a Modify command with the DEPLOYCF or NEWDSLST option.

If the message was issued when processing a Modify command, the data set selection table that was previously built remains in effect. If the error occurs during initialization, data set triggering functions are not available.

If the data set triggering function should be active, check that EQQJCLIB contains the data set selection table. Restart the tracker or issue the Modify command when the data set selection table has been created.

EQQZ163W

MEMBER MEMBER IN EQQJCLIB IS EMPTY

A data set selection table exists in library EQQJCLIB, but there are no records in the member. This message can be issued:
  • During initialization of the event writer task.
  • When processing a Modify command with the DEPLOYCF or NEWDSLST option.

If the message was issued when processing a Modify command, the data set selection table that was previously built remains in effect. If the error occurs during initialization, data set triggering functions are not available.

If the data set triggering function should be active, check that EQQJCLIB contains a valid data set selection table. If EQQJCLIB contains an EQQDSLST member, consider that it must contain at least an end-of-table indicator. Restart the tracker or issue the Modify command when the problem has been corrected.

EQQZ164E

MEMBER MEMBER CONTAINS INVALID DATA

The data set triggering selection table contains invalid data or is missing an end-of-table marker. This message can be issued:
  • During initialization of the event writer task.
  • When processing a Modify command with the DEPLOYCF or NEWDSLST option.

If the message was issued when processing a Modify command, the data set selection table that was previously built remains in effect. If the error occurs during initialization, data set triggering functions are not available.

Check the output of the data set selection table builder job (EQQRXTRG or EQQLSENT assembly). If you used EQQLSENT, consider that the data set selection table must contain at least an end-of-table indicator created with STRING=LASTENTRY as input to the EQQLSENT macro. If you cannot correct the problem, contact the Software Support. Restart the tracker or issue the Modify command when the problem has been corrected.

EQQZ165I

MEMBER MEMBER OF LIBRARY EQQJCLIB IS SUCCESSFULLY LOADED

HCL Workload Automation for Z has successfully created a data set selection table from the current contents of member EQQEVLST or EQQDSLST in the library defined by the EQQJCLIB DD statement. This message is issued when an event writer first creates the table after an IPL or when the table is rebuilt during the processing of a Modify command with Modify option DEPLOYCF or NEWDSLST.

HCL Workload Automation for Z continues normal processing.

None.

EQQZ166E

ERROR WRITING MEMBER MEMBER OF EQQJCLIB LIBRARY.

The scheduler encountered an I/O error writing to the data set triggering selection table.

If the message was issued when processing a Modify command, the data set selection table that was previously built remains in effect. If the error occurs while building the selection table or during initialization, data set triggering functions are not available.

Check that EQQJCLIB is correctly defined. After correcting the error, restart the tracker or issue a Modify command with option DEPLOYCF.

EQQZ167E

ERROR IN MACRO STOW: RC = RETCODE, RSN = RSNCODE WRITING MEMBER MEMBER OF EQQJCLIB LIBRARY.

The scheduler received an error while stowing member MEMBER in the tracker EQQJCLIB.

If the message was issued when processing a Modify command, the data set selection table that was previously built remains in effect. If the error occurs while building the selection table or during initialization, data set triggering functions are not available.

Check that EQQJCLIB is correctly defined. After correcting the error, restart the tracker or issue a Modify command with option DEPLOYCF.

EQQZ168I

MEMBER MEMBER OF EQQJCLIB LIBRARY HAS BEEN UPDATED.

The scheduler successfully updated the data set triggering selection table.

HCL Workload Automation for Z continues normal processing.

None.

EQQZ169I

CONFIGURATION FILE MEMBER OF EQQJCLIB LIBRARY IS LOADED TO INTERCEPT EVENTS.

The scheduler successfully refreshed the data set triggering selection table from the current contents of member MEMBER in the tracker EQQJCLIB.

HCL Workload Automation for Z continues normal processing.

None.

EQQZ170E

CODE LEVEL VERIFICATION FAILED CODE LEVEL OF THE SSX CONTROL BLOCK IS SSXLEV CODE LEVEL OF THE EQQMAJOR MODULE IS MCALEV CODE LEVEL OF THE SSCM MODULE IS SSCMLEV

HCL Workload Automation for Z initialization has determined that the SSX control block, the EQQMAJOR module and the EQQSSCMx load module are on different service levels. This difference is not supported.

HCL Workload Automation for Z initialization fails.

Verify that HCL Workload Automation for Z is using the correct load library. If the SSX control block and the EQQMAJOR module are on different code levels, modify the OPCOPTS statement, specifying the BUILDSSX keyword. If the EQQSSCMx and the EQQMAJOR modules are on different code levels, modify the OPCOPTS statement, adding or changing the SSCMNAME keyword.

After making the appropriate changes, restart the HCL Workload Automation for Z subsystem.

EQQZ171E

MERGE PARAMETER IS NOT SUPPORTED. OLD SSX AND NEW SSX ARE NOT FOR THE SAME FMID CODE LEVEL OF THE NEW SSX CONTROL BLOCK IS SSXLEV CODE LEVEL OF THE OLD SSX CONTROL BLOCK IS OLDLEV

The MERGE parameter of the BUILDSSX keyword is supported only when the old SSX control block was built for the same FMID as the current EQQMAJOR module.

HCL Workload Automation for Z initialization fails.

Change the BUILDSSX keyword to specify BUILDSSX(REBUILD).

EQQZ172I

SSX BLOCK OF VERSION SSXLEV SUCCESSFULLY BUILT

The BUILDSSX keyword was specified in the OPCOPTS control statement and HCL Workload Automation for Z has successfully verified that the EQQSSCMx load module is of the correct version. A new SSX control block has been built and is used by this HCL Workload Automation for Z address space.

The HCL Workload Automation for Z address space initialization continues.

EQQZ173I

SSX BLOCK OF VERSION SSXLEV SUCCESSFULLY RESTORED

The BUILDSSX keyword was specified in the OPCOPTS control statement and HCL Workload Automation for Z has successfully restored the previous version of the SSX block as the operative version.

This message is issued only when the SSX block was rebuilt by theHCL Workload Automation for Z address space using the BUILDSSX keyword and when the address space is about to terminate.

The SSXLEV variable indicates the code level of the SSX that is restored. The restored SSX is used by all HCL Workload Automation for Z functions while the HCL Workload Automation for Z subsystem is inactive.

The HCL Workload Automation for Z address space termination continues.

EQQZ174W

OLD AND NEW SSX CONTROL BLOCK ARE ON THE SAME LEVEL, SSXLEV

The BUILDSSX keyword was specified in the OPCOPTS control statement and a new SSX block has been successfully built. However, the new and the old SSX control block are at the same code level.

HCL Workload Automation for Z initialization continues.

If this message is expected, modify the OPCOPTS statement, removing the BUILDSSX keyword.

If this message is not expected, verify that the load modules used byHCL Workload Automation for Z are coming from the correct load libraries. After making the appropriate changes, restart the HCL Workload Automation for Z subsystem.

EQQZ175E

INCONSISTENT DEFINITION OF JOBLOGRETRIEVAL KEYWORD

You have made an inconsistent definition of JOBLOGRETRIEVAL in JOBOPTS. Check the following conditions:
  • OPCHOST(NO) must be specified on OPCOPTS
  • CATMGT(YES) must be specified on OPCOPTS
  • If you have specified JOBLOGRETRIEVAL(DELAYED) or (DELAYEDEXIT), you must have a EXITS statement with CALL010(YES) or LOAD010(nnnnnnnn).

HCL Workload Automation for Z is terminated.

Correct the inconsistent definition and restart HCL Workload Automation for Z.

EQQZ176E

INCONSISTENT DEFINITION OF CATMDISP KEYWORD

You have made an inconsistent definition of CATMDISP in JOBOPTS. Check the following conditions:
  • OPCHOST(NO) must be specified on OPCOPTS
  • CATMGT(YES) must be specified on OPCOPTS
  • A JOBLOGRETRIEVAL other than NONE is specified.

HCL Workload Automation for Z is terminated

Correct the inconsistent definition and restart HCL Workload Automation for Z.

EQQZ177E

INCONSISTENT DEFINITION OF MAXNUMUSYS KEYWORD

You have made an inconsistent definition of MAXNUMUSYS in JOBOPTS. Check the following conditions:
  • OPCHOST(NO) must be specified on OPCOPTS
  • CATMGT(YES) must be specified on OPCOPTS
  • A JOBLOGRETRIEVAL value other than NONE is specified.

HCL Workload Automation for Z is terminated.

Correct the inconsistent definition and restart HCL Workload Automation for Z.

EQQZ178E

INCONSISTENT DEFINITION OF JOBLOGDEST KEYWORD

You have made an inconsistent definition of JOBLOGDEST in OPCOPTS. Check the following conditions:
  • OPCHOST(YES) must be specified
  • CATMGT(YES) must be specified.
Also check that the destination pairs specified are in alignment with those defined in the ROUTOPTS statement.

HCL Workload Automation for Z is terminated.

Correct the inconsistent definition and restart HCL Workload Automation for Z.

EQQZ179E

UNBALANCED PAIR OF DESTINATIONS IN JOBLOGDEST KEYWORD

You have specified a JOBLOGDEST that contains an unbalanced definition of destinations. Either the execution destination is specified, but no retrieval destination, or a retrieval destination is specified, but no execution destination.

HCL Workload Automation for Z is terminated.

None.

Correct the inconsistent definition and restart HCL Workload Automation for Z.

EQQZ180E

INCONSISTENT DEFINITION OF EXIT STATEMENT AND JOBLOGRETRIEVAL KEYWORD

You have specified the JOBLOGRETRIEVAL keyword with value DELAYED or DELAYEDEXIT. The value implies the use of a user exit, UX010, that has not been defined to HCL Workload Automation for Z.

HCL Workload Automation for Z is terminated.

Correct the inconsistent definitions and restart HCL Workload Automation for Z.

EQQZ181E

UNPAIRED DESTINATION:IPADDR SPECIFIED IN THE TCP KEYWORD

In the TCP keyword of the ROUTOPTS statement each destination must be paired with the IP address of the corresponding tracker.

HCL Workload Automation for Z is terminated.

Correct the inconsistent definitions and restart HCL Workload Automation for Z.

EQQZ182E

SUBSTRING EXCEEDS BOUNDS OR LENGTH ZERO WAS FOUND IN PARMREC

During symbol substitution of PARMLIB, a substringed symbol was encountered. It exceeds either the bounds of the substitution text or a substring, in which the length specified was 0. The incorrect record follows in message EQQZ182I.

The task is terminated.

Correct the wrong system symbol definitions. Restrictions in usage of the system symbols are found in the Assembler Services Reference.

EQQZ183E

UNEXPECTED ERROR DURING SYMBOL SUBSTITUTION

During symbol substitution processing, an unexpected error occurred.

The task is terminated.

Contact the Software Support. Provide a copy of the message log as documentation. A possible solution is to remove the system symbols from the PARMLIB member being processed.

EQQZ184E

XCF STATEMENT NEEDED WHEN OPCOPT OPCHOST(PLEX) SPECIFIED

During the processing of the XCF statement, either the MEMBER or the GROUP keyword is missing. These keywords are required when OPCOPT OPCHOST(PLEX) is specified.

HCL Workload Automation for Z stops processing.

Correct the statement definitions, either by adding the correct XCF MEMBER and GROUP definitions or by changing the OPCHOST(PLEX) keyword.

EQQZ185I

THE SCHEDULER WILL START AS AN ACTIVE CONTROLLER

The HCL Workload Automation for Z subsystem starts as an active controller, with job submission and tracking functions as defined in the initialization parameters.

HCL Workload Automation for Z startup continues.

None.

EQQZ186I

THE SCHEDULER WILL START AS A STANDBY CONTROLLER

The HCL Workload Automation for Z subsystem starts as an standby controller, ready to take over job submission and tracking functions from the active controller, as defined in the initialization parameters.

HCL Workload Automation for Z startup continues.

None.

EQQZ187E

CHECKPOINT DATASET WAS NOT INITIALIZED

During the startup with OPCOPTS OPCHOST(PLEX), the checkpoint data set is not initialized. This is not supported.

HCL Workload Automation for Z stops processing.

Start one HCL Workload Automation for Z controller with OPCOPTS OPCHOST(YES) to initialize the checkpoint data set with the correct FMID and service level for a Sysplex Controller configuration.

EQQZ188E

UNEXPECTED RETURN CODE DURING SYMBOL SUBSTITUTION

During symbol substitution an unexpected return code was issued by the z/OS symbol substitution services. Diagnosis messages are shown.

HCL Workload Automation for Z stops processing.

Save the parameter data set definitions, the message log and the current values of z/OS static symbols. Contact the Software Support. A possible solution is to remove the system symbols from the PARMLIB member being processed.

EQQZ189W

OPCOPT OPCHOST(PLEX) WAS SPECIFIED BUT NO TAKEOVER KEYWORD FOR THE XCFOPTS STATEMENT WAS FOUND

The initialization statement OPCOPT OPCHOST(PLEX) was specified, but no TAKEOVER keyword for the XCFOPTS statement was coded. This is necessary to avoid operator intervention in a takeover situation.

HCL Workload Automation for Z startup continues.

Code either TAKEOVER SYSFAIL or HOSTFAIL, as appropriate.

EQQZ190E

THE FMID FILEFMID OF DATASET FILENAME DOES NOT MATCH CODE FMID OPCFMID

The FMID FILEVER of the data set FILENAME does not match the FMID OPCVER of the code trying to access the file.

Either the program or HCL Workload Automation for Z initialization is terminated.

Check that the level of HCL Workload Automation for Z matches the level of the file indicated in the message. Possible explanations include running on backlevel code or a backlevel data set. Correct the errors and restart either HCL Workload Automation for Z or the program.

Contact your system programmer.

EQQZ191E

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

The subsystem task module, EQQMAJOR, could not open the checkpoint data set, which is a required data set for HCL Workload Automation for Z.

HCL Workload Automation for Z initialization is terminated.

Check that ddname EQQCKPT is correctly specified and the HCL Workload Automation for Z started task is authorized to open the data set for updating. Correct the errors and restart HCL Workload Automation for Z.

Contact your system programmer.

EQQZ192E

THE VERSION FILEVER OF DATASET FILENAME DOESN'T MATCH CODE VERSION OPCVER

The version FILEVER of the data set FILENAME does not match the version OPCVER of the code trying to access the file.

Either the program or HCL Workload Automation for Z initialization is terminated.

Check that the level of HCL Workload Automation for Z matches the level of the file indicated in the message. Possible explanations include running on backlevel code or a backlevel data set. Correct the errors and restart either HCL Workload Automation for Z or the program.

Contact your system programmer.

EQQZ193I

END-TO-END TRANSLATOR SERVER PROCESS IS NOW AVAILABLE

The Receiver task periodically checks for the End-to-end Translator server process availability. This message is issued in the controller MLOG when the translator process is available. If the Event Manager task is not active, the Receiver starts waiting for it to become active again, and the EQQW099I message with action = 'STARTED' is issued in the controller MLOG and the Receiver stops checking for the server availability. When the Event manager is active again, EQQW099I message with action = 'STOPPED' is issued in the controller MLOG, and the Receiver restarts checking for the server availability.

None.

None.

EQQZ194W

RCLEANUP (YES) FORCES OUTPUTNODE (FINAL)

Outputnode (JTOPTS) was set to any but RCLEANUP (YES) requires it to be set to final.

OUTPUTNODE value is defaulted to final, initialization continue.

None.

EQQZ195I

SYNCRONIZATION BETWEEN CONTROLLER AND SERVER ENDED

The server ended the synchronization process with the controller during a daily planning activity.

The planning activity continues.

None.

EQQZ196E

THE SAME IP ADDRESS AND PORT APPEAR IN MORE THAN ONE TCPIP KEYWORD OF THE ROUTOPTS STATEMENT.

The pair address-port number must be unique within the TCP/IP destination list.

The product initialization terminates.

Correct the ROUTOPTS statement.

EQQZ197E

AN ERROR OCCURRED WHILE LOGGING CRITICAL JOB TABLE DATA SPACE IN DATA SET EQQJTABL.

The scheduler tried to log the critical job table data space before closing the critical path handler, but the logging failed.

The critical path handler processing ends without saving the current critical job table content.

Check the system log and EQQMLOG for messages that explain why the logging failed. In particular, verify that EQQJTABL is correctly defined.

EQQZ198E

AN ERROR OCCURRED WHILE LOADING CRITICAL JOB TABLE ENTRIES FROM DATA SET EQQJTABL TO UPDATE DATA SPACE.

The scheduler tried to log the critical job table data space before closing the critical path handler, but the logging failed.

The scheduler cannot update the critical job table. Dynamic updates might be lost.

Save the message log (EQQMLOG), the job table log file (EQQJTABL) and the current plan (EQQCPxDS), and contact the Software Support.

Contact your system programmer.

EQQZ199E

AN ERROR OCCURRED WHILE RESETTING CRITICAL JOB TABLE LOG DATA SET.

The scheduler failed to reset the critical job table when extending, recreating, or deleting the current plan.

The scheduler cannot update the critical job table. Dynamic updates might be lost.

Save the message log (EQQMLOG), the job table log file (EQQJTABL) and the current plan (EQQCPxDS), and contact the Software Support.

Contact your system programmer.

EQQZ200I

OPCTYP SSNAME HEARTBEAT

This message is sent by the scheduler at startup or as result of a "heartbeat" command, to state that the scheduler is active and running.
OPCTYP
One of the following values:
CONTROLLER
If the subsystem is a controller.
STAND-BY
If the subsystem is a standby controller.
TRACKER
If the subsystem is a tracker.
SSNAME
The name of the scheduler subsystem.

If the scheduler instrumentation for GEM is active, this message is translated by NetView into a Heartbeat event and is sent to GEM. When GEM receives this message, it adds an icon for this component in the Job Scheduling view on the GEM console.

None.

EQQZ201I

OPCTYP SSNAME: STATUS

Displays the status of a subsystemof the scheduler.
OPCTYP
One of the following values:
CONTROLLER
If the subsystem is a controller of HCL Workload Automation for Z.
STAND-BY
If the subsystem is a standby controller.
TRACKER
If the subsystem is a tracker of z/OS.
SSNAME
The name of the scheduler subsystem.
STATUS
One of the following values:
FULLY_OPERATIONAL
The subsystem is working correctly.
PARTIALLY_OPERATIONAL
The subsystem has limited functionality, for example, ER is not active. Therefore a controller can still schedule jobs, but cannot receive their status.
NOT_OPERATIONAL
Some core functionality of the scheduler is not active, for example, a controller is not able to execute a plan or to submit a job.

If the scheduler instrumentation for GEM is active, this message is translated into a Monitor Threshold event and sent to GEM, which updates the Job Scheduling view correctly on the APM console.

If the scheduler STATUS is not FULLY_OPERATIONAL, one or more of the scheduler subtasks is inactive or is not working properly. Depending on the inactive tasks, the status can assume the values PARTIALLY_OPERATIONAL or NOT_OPERATIONAL. Message EQQZ202I lists the inactive subtasks, which you should restart.

EQQZ202I

FOLLOWING SUBTASKS ARE INACTIVE: TASKLST

Lists the names of the scheduler subtasks that are inactive. If the scheduler status is not FULLY_OPERATIONAL, this message is always issued in conjunction with message EQQZ201I.

Normal processing continues.

Restart the correct scheduler subtask.

EQQZ203I

TRKTYPE TRACKER TRKNAME : TRKADDR TRKSTAT

Provides information about the status of a tracker connected to a controller.
TRKTYPE
The type of tracker. It can be one of the following values:
  • SNA
  • XCF
  • DASD
  • TCP
  • USER
  • APPC
  • HOME
TRKNAME
The name of the scheduler destination associated with that tracker.
TRKADDR
The TCP/IP or SNA address associated with that tracker.
TRKSTAT
The status of the tracker. It can be one of the following values:
  • ONLINE
  • OFFLINE

If the scheduler instrumentation for GEM is active, this message is translated into a Monitor Threshold event and sent to GEM, which updates the Job Scheduling view correctly on the APM console.

If the status of a connected tracker is offline, either the tracker is not running or the connection is down. Restart the tracker or wait for the tracker to reestablish the connection.

EQQZ204I

SSNAME TRKTYPE TRACKER TRKNAME: TRKADDRHEARTBEAT

This message is sent by the scheduler at startup or as a result of a STATUS,TRK scheduler command, to state that a tracker defined to this controller is active and running.
SSNAME
The name of the scheduler subsystem.
TRKTYPE
The type of tracker. It can be one of the following values:
  • SNA
  • XCF
  • DASD
  • TCP
  • USER
  • APPC
TRKNAME
The name of the scheduler destination associated with that tracker.
TRKADDR
The TCP/IP or SNA address associated with that tracker.

If the scheduler instrumentation for GEM is active, this message is translated by NetView into a Heartbeat event for the Tracker and is sent to GEM. When GEM receives this message, it updates the Job Scheduling view in the APM server with a new component for this tracker and a new link with the related controller.

None.

EQQZ205I

TRKTYPE TRACKER TRKNAME : TRKADDR NOT FOUND

This message is sent by the scheduler as result of a STATUS,TRK command of the scheduler, when the tracker name (or tracker address) is not defined to the controller in the ROUTOPTS initialization statements.
TRKTYPE
The type of tracker. It can be one of the following values:
  • SNA
  • XCF
  • DASD
  • TCP
  • USER
  • APPC
TRKNAME
The name of the scheduler destination associated with that tracker.
TRKADDR
The TCP/IP or SNA address associated with that tracker.

Normal processing continues.

Specify the correct tracker name (or address) in the STATUS,TRK command of the scheduler.

EQQZ206I

SSNAME TRKTYPE TRACKER TRKNAME: TRKADDR TRKSTAT

Provides information about the status of a tracker connected to this controller.
SSNAME
The name of the scheduler subsystem.
TRKTYPE
The type of tracker. It can be one of the following values:
  • SNA
  • XCF
  • DASD
  • TCP
  • USER
  • APPC
TRKNAME
The name of the scheduler destination associated with that tracker.
TRKADDR
The TCP/IP or SNA address associated with that tracker.
TRKSTAT
The status of the tracker. It can be one of the following values:
  • ONLINE
  • OFFLINE

If the scheduler instrumentation for GEM is active, this message is translated by NetView into a Connection Change event for the tracker and is sent to GEM. When GEM receives this message, it updates the Job Scheduling view in the APM Server by removing or creating the link between the tracker and the related controller.

If the status of a connected tracker is offline, either the tracker is not running or the connection is down. Restart the tracker or wait for the tracker to reestablish the connection.

EQQZ207I

TASKNAM IS STATUS

Displays the status of the specified scheduler subtask.
TASKNAM
The name of the scheduler subtask.
STATUS
The status of the scheduler subtask:
ACTIVE
The scheduler subtask is running.
INACTIVE
The scheduler subtask is not running.

Normal processing continues.

None.

EQQZ208I

DDNAMELAST-RC= LASTRC

Provides the return code of the last I/O operation on the specified DDNAME.
DDNAME
The ddname of the scheduler data set.
LASTRC
The return code of the last I/O operation. It can be one of the following values:
  • NORMAL
  • WARNING
  • SEVERE
  • CRITICAL
  • UNKNOWN

Depending on the return code value and on the specified DDNAME, the scheduler could stop some of its subtasks.

If the LASTRC value is other than NORMAL or WARNING, and depending on the DDNAME value, some of the scheduler functions could not work correctly. In this case, check the status of the physical sequential or VSAM data set associated with DDNAME.

EQQZ209I

OPNUM OPDESC FOR TRACKER TRKNAM

Displays the number of operations that have been completed or ended in error for the specified tracker.
OPNUM
The number of operations that completed or ended in error.
OPDESC
The description of the operations. It can be one of the following values:
COMPLETED_OPERATIONS
The number of operations that completed successfully on that destination.
IN_ERROR_OPERATIONS
The number of operations that ended in error on the specified tracker.
TRKNAM
The name of the tracker.

If the scheduler instrumentation for GEM is active, this message is translated into a Monitor Threshold event and sent to GEM, which updates the Job Scheduling view correctly on the APM console.

None.

EQQZ210I

ERRCODE ERROR ACCESSING SSNAME DATASET: ERRMSG

An error occurred accessing a data set, where:
SSNAME
The name of the scheduler subsystem
ERRCODE
The code of the error. It can be either SEVERE or FATAL.
ERRMSG
The cause of the error. It can be either an I/O error or unable to open the file.

Depending on the ERRCODE value, some of the scheduler functions could not work correctly.

Check the status of data set.

EQQZ211E

THE EDP TABLE HAS REACHED THE LIMIT OF 1000 DESTINATIONS

The controller detected that the EDP table has reached the maximum number of entries for the remote destinations while trying to add a new one.

All the controller communication tasks and event readers are stopped until a refresh of the checkpoint data set is performed.

Refresh the checkpoint data set by running a daily plan extend or replan batch job after specifying the CKPTREFRESH keyword the value YES in the BATCHOPT options.

EQQZ212E

ARM OPERATION (RET CODE: RTC, RSN CODE: RSC)

The automatic restart management (ARM) OPERATION has ended in error.

The ARM operation is not completed.

Verify the correct configuration of the ARM function. If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQZ212I

ARM OPERATION (RET CODE: RTC, RSN CODE: RSC)

The automatic restart management (ARM) OPERATION has completed.

The ARM operation has completed.

If RTC is 04, contact your system administrator.

EQQZ213W

THE THRESHOLD MUST BE IN THE RANGE FROM 0 TO 100

The threshold value is used with the conditional policy (specified in the WLM statement as SMART). If a job has not yet reached its deadline, the job considers the time remaining before the deadline. If the remaining time is long enough compared with the interval between the latest start time and the start time, no WLM request for promotion is issued. If you want to try and apply the Deadline and Latest Start Time policies in a row, you should specify a threshold value equal to 0.

None

Check that the threshold value you specified in the WLM statement of OPCOPTS is in the range 0-100. If not specify a correct value and rerun the task. For information about the supported values, see the Customization and Tuning manual, Chapter 1. Defining initialization statements, section, "OPCOPTS".

EQQZ214E

THE PROCESSING CANNOT PROCEED: TCP/IP COMMUNICATION FEATURE IS NOT INSTALLED

The server could not locate a required load module.

The server terminates.

If the TCP/IP communication is not installed, install it. Otherwise, ensure you are using the correct libraries.

EQQZ215E

WLM SCHEDULING ENVIRONMENT DEFINITIONS COULD NOT BE DETERMINED. RETURN CODE: RETC REASON CODE: RSNC

The tracker could not check the scheduling environment status, because the WLM macro used for this purpose (IWMSEQRY) failed. The WLM macro return code RETC and the reason code RSNC explain why.

If the tracker was to check all the currently available scheduling environments (this is performed when the Submit task starts up), the related VM event is not generated.

If the tracker was to check a specific scheduling environment, the related job is not submitted and the following EQQSU37E message specifies the name of the job.

See the WLM IWMSEQRY return code and reason code on the WLM guide book, and fix the problem. (See MVS Programming: Workload Management Services ).

EQQZ216I

ENF EXIT EXNAME WAS DELETED FROM CSA ADDRESS: ADDR SIZE: SIZ

At startup, the tracker or controller detected that the level of the associated EXNAME exit in CSA differs from the level of the EQQZNF57 exit loaded from the tracker STEPLIB (if) or LNKLIST library.

EXNAME can be one of the following:
  • EQQZNF41
  • EQQZNF57
This message reports that the pre-existing exit was deleted from CSA and specifies the new CSA address and the size of the just loaded exit.

The tracker removes existing exit from CSA and loads the new exit.

None.

EQQZ217W

THE SAME PORT PORT AND IP ADDRESS IPADDR APPEAR IN MORE THAN ONE HTTP KEYWORD OF THE ROUTOPTS STATEMENT.

The HTTP or HTTPS destinations list contains more destinations of the same type with the same IP address-port number. This definition is unnecessary.

The product initialization terminates.

Correct the ROUTOPTS statement by deleting the superfluous destination.

EQQZ218W

THE POTENTIAL PREDECESSOR RECORD FOR APPLICATION APPL COULD NOT BE UPDATED: THE APPLICATION WAS NOT FOUND IN AD VSAM DATA SET.

This message is issued in the controller MLOG file when, while adding the occurrence identified by the application appl, the related AD VSAM is not found.

The occurrence is added but the related potential predecessor record is not updated.

This situation might occur during the JT reapply processing of events, if the application was deleted after being added to the current plan.

EQQZ220W

CLNJOBPX PARM NOT SPECIFIED OR INVALID: DEFAULTED TO "EQQCL"

You specified OPCOPTS RCLEANUP(YES) but either did not specify RCLOPTS CLNJOBPX, or specified a cleanup job prefix with less then five characters: the cleanup job prefix parameter has been defaulted to "EQQCL".

Processing continues.

Specify the CLNJOBPX parameter for the RCLOPTS option or specify a cleanup job prefix with more five or more characters. For information about the supported values, see the Customization and Tuning manual, Chapter 1. Defining initialization statements, section, "RCLOPTS".

EQQZ222W

DSTDEST PARM NOT SPECIFIED DEFAULTED TO "OPC"

You did not specify the DSTDEST parameter in RCOPTS option. It has been defaulted to "HCL Workload Automation for Z".

The scheduler continues processing.

Specify the DSTDEST parameter in the RCLOPTS option and rerun the task. For information about the supported values, see the Customization and Tuning manual, Chapter 1. Defining initialization statements, section, "RCLOPTS".

EQQZ223E

DSTRMM VALUE INVALID. MUST BE "Y" OR "N"

You specified an invalid value for the DSTRMM parameter in RCOPTS option. Valid values are "Y" or "N".

The scheduler continues processing.

Check the command. Correct the error and resubmit the request.

EQQZ224W

DDPRMEM NOT ALLOWED WHEN DDPROT IS SPECIFIED

You have specified both DDPRMEM and DDPROT parameters in RCOPTS option. DDPRMEM is invalid when DDPROT is specified and it has been ignored.

The scheduler continues processing.

Remove the DDPRMEM parameter and rerun the task. For information about the supported values, see the Customization and Tuning manual, Chapter 1. Defining initialization statements, section, "RCLOPTS".

EQQZ225W

DSNPRMEM NOT ALLOWED WHEN DSNPROT IS SPECIFIED

You have specified both DSNPRMEM and DSNPROT parameters in RCOPTS option. DSNPRMEM is invalid when DSNPROT is specified and it has been ignored.

The scheduler continues processing.

Remove the DDPRMEM parameter and rerun the task. For information about the supported values, see the Customization and Tuning manual, Chapter 1. Defining initialization statements, section, "RCLOPTS".

EQQZ226E

DSTDEST VALUE INVALID

You specified an invalid value for the DSTDEST parameter in RCOPTS option. It must be a valid z/OS name.

The scheduler does not start.

Check the command. Correct the error and resubmit the request.

EQQZ227E

UNBALANCED PAIR OF DESTINATION AND JES CLASS IN DSTCLASS KEYWORD

The KEYWORD DSTCLASS has been specified with an invalid syntax in the RCLOPTS statement. The values must be pairs of destination and class,such as:
DSTCLASS ( Dest1:A , Dest2:B, Dest3:C )
See HCL Workload Automation for Z Customization and Tuning for details.

The controller stops processing and terminates.

Correct the syntax errors and restart the controller.

EQQZ228E

DSTCLASS VALUE INVALID

The values specified for the tracker destination or the JES class in the keyword DSTCLASS of the RCLOPTS statement contain syntax errors. See HCL Workload Automation for Z Customization and Tuning for details.

The Controller stops processing and terminates.

Correct the syntax errors and restart the controller.

EQQZ229E

A SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE EQQJTABL LOG DATA SET

While processing a stop or cancel command, the controller abnormally ended when attempted to write a record to the EQQJTABL data set. If the abend code is SB37 or SD37, the EQQJTABL data set is too small.

The scheduler stops logging records in the EQQJTABL data set. Remaining records will not be logged. As a consequence, at controller restart, events related to critical job table entries might be only partially processed.

If the abend code is SB37 or SD37, scrap the EQQJTABL data set and allocate a larger one at a suitable time when the controller is stopped. The next DP batch extend or replan process will rebuild the critical job table by reading current plan data.

EQQZ230E

THE SCHEDULER DID NOT GET ENOUGH STORAGE TO SEND AN EVENT TO TBSM

In the OPCOPTS statement, the EXTMON parameter is set to YES. The scheduler tried to allocate storage for a build of the event to send to TBSM, but the request for storage failed.

The event is not sent to TBSM.

Ensure that the product is running in a sufficiently large region, then restart it.

EQQZ231E

AN ERROR OCCURRED DURING COMMUNICATION WITH TBSM. THE EXTMON PARAMETER IS SET TO N

In the OPCOPTS statement, the EXTMON parameter is set to YES. The scheduler tried to communicate with TBSM but an ABEND occurred.

The EXTMON parameter is set to NO. Communication with TBSM is interrupted.

Verify the communication with TBSM and restart the controller/tracker.

EQQZ232E

AN ERROR OCCURRED LOADING AOPEDI MODULE. THE EXTMON PARAMETER IS SET TO N

In the OPCOPTS statement, the EXTMON parameter is set to YES. The scheduler tried to load the AOPEDI module to communicate with TBSM, but the load failed.

The EXTMON parameter is set to NO. Communication with TBSM is interrupted.

Concatenate a library containing the AOPEDI module in the controller/tracker steplib and restart the controller/tracker.

EQQZ233E

AN ERROR OCCURRED LOADING THE EQQZJBNF ROUTINE

The scheduler could not locate the EQQZJBNF subsystem routine. This routine is used to create the job name in the symphony file depending on the value of the TWSJOBNAME parameter of the JTOPTS statement.

The scheduler abends.

Ensure that the EQQZJBNF load module is present in the scheduler library.

The scheduler could not be installed correctly.

EQQZ234E

AN ERROR OCCURRED BUILDING AN EVENT FOR THE FTW FOR OPERATION(OPERNUM) IN APPLICATION APPL, IA = IA. THE JOBNAME USED TO ADD THE OPERATION TO THE SYMPHONY IS INCOMPATIBLE WITH THE EQQTWSOU DATASET RECORD LENGTH. EVENT COULD BE NOT APPLICABLE

When adding this operation to the current plan, the criterion specified by the TWSJOBNAME parameter of the JTOPTS statement was set to EXTNAME, EXTNOCC or JOBNAME; it implies that the EQQTWSOU data set record length was 160 bytes. Now the scheduler is building an event for this operation to be sent to the distributed network, but the EQQTWSOU record length is 120, so the information necessary to address the event to the correct job in the symphony file cannot be sent to the server. The event could be non-applicable.

The event is built using the occurrence name and the old format for the job name in the symphony file (OCCNAME value for the TWSJOBNAME parameter).

Again migrate the EQQTWSOU data set to a record length of 160 bytes by using sample EQQMTWSO

EQQZ235E

LOGICAL ERROR IN MODULE MODULE AT POINT POINT

A logical error has occurred in module MODULE at point POINT.

Other traces can be issued in the message log to explain the error condition

Save the HCL Workload Automation for Z message log data set containing this message, then search the IBM Support database for a solution at http://www.ibm.com/software/sysmgmt/products/support.

EQQZ236E

AN ERROR OCCURRED WHILE SENDING A DQE TO CPHQ QUEUE.

This is an internal error during the communication between the critical path handler and another task.

The scheduler cannot update the critical job table. Dynamic updates might be lost.

Save the message log (EQQMLOG), the job table log file (EQQJTABL) and the current plan (EQQCPxDS). To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section, "Information needed for all problems", sub-section, "Information to collect for critical path problems". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQZ238E

THE MANDATORY KEYWORD KEYWD IN STATEMENT STMT IS MISSING.

The keyword KEYWD of the STMT statement was not specified, but it is required.

HCL Workload Automation for Z continues and the STMT statement is ignored.

Specify a value for the KEYWD keyword and restart HCL Workload Automation for Z.

EQQZ239E

THE OSLCOPTS PRIORITY VALUE MUST BE BETWEEN 1 AND 5.

The value specified for the PRIORITY keyword of the OSLCOPTS statement is not valid.

HCL Workload Automation for Z continues and the OSLCOPTS statement is ignored.

Specify a value between 1 and 5 for the PRIORITY keyword and restart HCL Workload Automation for Z.

EQQZ240E

MONHOSTNAME NOT SPECIFIED. IT IS MANDATORY FOR MONOPTS STATEMENT

The MONHOSTNAME parameter of the MONOPTS statement was not specified, but is required. This parameter defines the host name or IP address of the remote Tivoli Monitoring agent

HCL Workload Automation for Z terminates. Message EQQZ054E is also issued.

Provide a valid value for the MONHOSTNAME field and restart HCL Workload Automation for Z.

EQQZ241I

PORT VALUE IS INCORRECT. VALUE MUST RANGE FROM 0 TO 65535. DEFAULT VALUE IS CURRENTLY USED

The value specified for the MONPORT or LOCPORT parameter in the MONOPTS statement, is outside the valid range. Valid values are from 0 to 65535.

The default value 7500 is used for MONPORT or the default value 0 is used for LOCPORT.

None.

EQQZ242I

PORT PARAMETER NOT SPECIFIED. DEFAULT VALUE IS CURRENTLY USED.

The value specified for the MONPORT or LOCPORT parameter in the MONOPTS statement was not specified or recognized.

The default value 7500 is used for MONPORT or the default value 0 is used for LOCPORT.

None.

EQQZ243I

A VALUE OF MANUAL FOR MONPOL EXCLUDES ALL OTHER OPTIONS.

If MANUAL is specified for the MONPOL statement with other values, all other values will be ignored.

Only the value MANUAL is considered for the MONPOL statement.

None.

EQQZ244I

CONNTIMEOUT PARM NOT SPECIFIED OR OUT OF RANGE (0:10000). DEFAULTED TO 15.

The CONNTIMEOUT parameter was omitted or a value outside the valid range of 0 to 10000 seconds.

The default value of 15 seconds will be used for the CONNTIMEOUT parameter.

None.

EQQZ245I

CODEPAGE KEYWORD IS NOT PRESENT IN OPCOPTS STATEMENT THE DEFAULT VALUE IS USED

The CODEPAGE parameter in the OPCOPTS statement was not specified.

The default codepage IBM-037 is used.

None.

EQQZ246W

OBSOLETE PARAMETER SPECIFIED: CRITPATH. CRITICAL PARAMETER IS SET AUTOMATICALLY WHEN CRITPATH IS SPECIFIED

The MONPOL statement contains the CRITPATH obsolete parameter.

The scheduler activates the same processing as when CRITICAL is specified.

Consider changing CRITPATH to CRITICAL in the MONPOL statement.

EQQZ249E

THE TKTURI PARAMETER IN THE OSLCOPTS STATEMENTS HAS AN INVALID VALUE.

The value specified for the TKTURI keyword of the OSLCOPTS statement is not valid.

HCL Workload Automation for Z continues and the OSLCOPTS statement is ignored.

Specify a correct URI for the TKTURI keyword and restart HCL Workload Automation for Z.

EQQZ250W

KEYWORD KEYWD IN STATEMENT STMT IS NOT VALID. THE VALUE IS OUTSIDE THE VALID RANGE. WILL USE DEFAULT DEFAULT.

The value specified for keyword KEYWD is incorrect.

The processing continues by using the default value for keyword KEYWD.

Specify a valid value for keyword KEYWD. If you do not want the processing to use the default, restart the started task.

EQQZ251I

KEYWORD KEYWD IS MISSING IN STATEMENT STMT. WILL USE DEFAULT DEFAULT.

Keyword KEYWD was not specified in statement STMT.

The processing continues using the default value for keyword KEYWD.

If you do not want the processing to use the default, specify a value for keyword KEYWD in statement STMT, then restart the started task.

EQQZ252E

KEYWORD KEYWD IS MISSING BUT SSLLEVEL IS SET TO FORCE IN STATEMENT STMT.

If the statement STMT is set with SSLLEVEL(FORCE), the keyword KEYWD is required.

The started task initialization terminates.

Correct the statement STMT by either modifying the SSLLEVEL(FORCE) parameter or setting the keyword KEYWD to a valid value. Then restart the started task.

EQQZ253E

THE TRROPTS STATEMENT CONTAINS HOSTCON(TCP) BUT THE TCPHOSTNAME KEYWORD IS MISSING.

A TCP/IP connection cannot be established between the controller and a tracker because the TCPHOSTNAME keyword does not contain the controller IP address or host name.

The started task initialization terminates.

Specify a valid value for TCPHOSTNAME keyword.

EQQZ254E

EITHER THE TCPHOSTNAME OR THE TCPPORTNUMBER KEYWORD IS SPECIFIED, BUT THE TRROPTS STATEMENT DOES NOT CONTAIN HOSTCON(TCP).

The initialization statement is inconsistent.

The started task initialization terminates.

Correct the TRROPTS statement either specifying the TCP value for HOSTCON keyword or deleting the TCPHOSTNAME or the TCPPORTNUMBER keyword.

EQQZ255E

TCPIP KEYWORD VALUE VAL1 IS TOO LONG OR MISSING.

A workstation destination name specified as a value of the TCPIP keyword of the ROUTOPTS statement is incorrect. The destination name is required and cannot exceed eight characters.

Processing of the current ROUTOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.

Specify a correct value for the TCPIP keyword, then restart the started task.

EQQZ256E

THE REAPPLY KEYWORD SPECIFIES A VALUE THAT IS NOT IN THE RANGE 1-32000.

In the OPCOPTS statement, the REAPPLY parameter is set to a value that is not in the valid range (1-32000).

Processing of the current OPCOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.

Specify a correct value for the REAPPLYCOUNT keyword, then restart the started task.

EQQZ257I

DEFAULT VALUE DEFAULT IS USED FOR KEYWORD KEYWD IN STATEMENT STMT.

Keyword KEYWD was not specified in statement STMT.

The processing continues using the default value for keyword KEYWD. For the TCPOPTS statement, the possible cases are:
  • TRKPORTNUMBER keyword. The default value can be one of the following:
    424
    It applies to the controller only.
    0
    It applies to the tracker, meaning that the process returns the actual value.
  • DSTPORTNUMBER keyword. The default value can be one of the following:
    423
    It applies to the controller only.
    0
    It applies to the data store, meaning that the process returns the actual value.
  • SRVPORTNUMBER keyword. The default value can be one of the following:
    425
    It applies to the server only.
    0
    Default value for an ISPF dialog or PIF program, meaning that the process returns the actual value.

If you do not want the processing to use the default, specify a value for keyword KEYWD in statement STMT, then restart the started task.

EQQZ258I

KEYWORD KEYWD IN STATEMENT STMT WILL BE IGNORED.

The parsing process for the statement STMT ignored the keyword KEYWD. It is a valid keyword of the TCPOPTS statement but it does not affect the selected function.

The keyword is not used.

You can remove the unneeded keyword from the TCPOPTS statement.

EQQZ259E

DSTPORTNUMBER AND TRKPORTNUMBER MUST BE DIFFERENT.

The TCPOPTS controller statement defines connection parameters for z/OS communication partners. The DSTPORTNUMBER and the TRKPORTNUMBER specify the same port number for both of the connections.

The controller terminates with an error.

Ensure different values are assigned to each of the port number parameters.

EQQZ260E

LIBRARY WITH DDNAME EQQEVLIB COULD NOT BE OPENED.

The controller could not open the required EQQEVLIB data set.

The tracker does not find any configuration file to correlate system activities and triggered actions.

Check that EQQEVLIB is correctly defined and that the scheduler is authorized to open the data set. Restart the controller when the error has been corrected.

EQQZ261E

UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF EQQEVLIB.

An error occurred when allocating storage to process the member indicated in the message variable.

The scheduler stops processing the indicated EQQEVLIB member.

Verify that the member indicated in the message variable is not too large. If it is not, determine which product or program, or both, is exhausting ECSA storage.

EQQZ262E

LIBRARY WITH DDNAME EQQEVLIB COULD BE USED BY ANOTHER TASK.

Another task or user is accessing the EQQEVLIB data set.

The scheduler stops processing EQQEVLIB.

When the EQQEVLIB data set is free, restart the process.

EQQZ263W

COMMAND IS VALID JUST ON CONTROLLER SIDE.

When issuing a command with the DEPLOYCF option, you specified a procedure name different from the controller started task name.

The request is rejected.

Specify the controller started task name as procedure name.

EQQZ264W

NO DESTINATION MEMBERS FOUND IN LIBRARY WITH DDNAME EQQEVLIB.

The data set referenced by the EQQEVLIB does not contain any member name corresponding to a destination currently defined in the ROUTOPTS statement.

There is no data correlating event conditions and actions. No action is triggered.

Check the destinations specified in the event rule definitions as input data for the job that builds and deploys the event configuration file. Rerun the job.

EQQZ265E

THE DESTINATION $$$$$$$$ IS NOT PERMITTED.

The $$$$$$$$ string is reserved for identifying the local destination in the event rule definition.

The controller initialization fails.

Remove $$$$$$$$ from any destination list in the ROUTOPTS statement.

EQQZ266E

ERROR WRITING MEMBER MEMBER OF EQQEVLIB LIBRARY

The process encountered an I/O error writing to the configuration file repository.

The process stops creating or updating MEMBER configuration file.

Check that EQQEVLIB is correctly defined. Refer to DFSMS Macro Instructions for Data Sets to find the cause of the error and correct it.

EQQZ267E

ERROR IN MACRO STOW: RC = RETCODE, RSN = RSNCODE WRITING MEMBER MEMBER OF EQQEVLIB LIBRARY

The process received an error while stowing MEMBER configuration file in the controller EQQEVLIB.

The process stops creating or updating MEMBER configuration file.

Check that EQQEVLIB is correctly defined. Refer to DFSMS Macro Instructions for Data Sets to find the cause of the error and correct it.

EQQZ268E

ERROR READING DIRECTORY BLOCKS OF EQQEVLIB LIBRARY

An I/O error prevented the process from accessing the configuration file repository.

The scheduler cannot access the selection table for data for data set triggering.

Check that EQQEVLIB is correctly defined and contains valid data.

EQQZ269W

THE PULSEIVL VALUE SPECIFIED FOR DESTINATION DEST IS OUTSIDE THE VALID RANGE. WILL USE THE HTTPOPTS PULSEIVL VALUE.

The value specified for the pulseivl parameter of the HTTP/HTTPS DEST destination name in the ROUTOPTS initialization statement is not in the valid range (0 to 1440 minutes).

The scheduler reverts to the global value specified for PULSEIVL in the HTTPOPTS initialization statement. If the keyword is not defined in HTTPOPTS, then 0 (the default value, no heartbeat checking) is assumed.

Correct the value of pulseivl in the ROUTOPTS statement.

EQQZ270E

HTTP KEYWORD VALUE VAL1 IS TOO LONG OR MISSING.

A workstation destination name specified as a value of the HTTP keyword of the ROUTOPTS statement is incorrect. The destination name is required and cannot exceed eight characters.

Processing of the current ROUTOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.

Specify a correct value for the HTTP keyword, then restart the started task.

EQQZ271E

AT LEAST ONE HTTP KEYWORD VALUE IS INCORRECT.

The HTTP keyword of the ROUTOPTS statement contains one or more incorrectly defined HTTP destinations.

Processing of the current ROUTOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.

Review the syntax of the HTTP destinations specified. Remove or correct the incorrect destination, then restart the controller.

EQQZ272I

THE VALUE FOR JCCREQUD EXCEEDS THE MAX VALUE (500). IT IS SET TO 500.

Because the JCCREQUD keyword of the JCCOPTS statement is set to a value that exceeds the maximum allowed (500), the keyword is automatically set to 500.

JCCREQUD is set to 500, and processing continues. Consider that this high value can delay operations' tracking.

None.

EQQZ273E

HTTPS KEYWORD VALUE VAL1 IS TOO LONG OR MISSING.

A workstation destination name specified as a value of the HTTPS keyword of the ROUTOPTS statement is incorrect. The destination name is required and cannot exceed eight characters.

Processing of the current ROUTOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.

Specify a correct value for the HTTPS keyword, then restart the started task.

EQQZ274E

AT LEAST ONE HTTPS KEYWORD VALUE IS INCORRECT.

The HTTPS keyword of the ROUTOPTS statement contains one or more incorrectly defined HTTPS destinations.

Processing of the current ROUTOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.

Review the syntax of the HTTPS destinations specified. Remove or correct the incorrect destination, then restart the controller.

EQQZ275E

USRNAM KEYWORD IS MISSING.

The USRREC statement requires the USRNAM keyword.

The task ends.

Find all the USRREC statements without the USRNAM keyword in the users information member of EQQPARM. Add valid users names in these definitions.

EQQZ276W

USER DEFINITION RECORD USER DOES NOT SPECIFY CPU, OR CPU NAME IS NOT CORRECT: THE USER IS NOT AVAILABLE FOR Z-CENTRIC JOB SUBMISSION.

In a USRREC statement, the USRCPU keyword is not specified or the CPU name specified in the keyword is not an existing CPU.

The task continues its processing, ignoring this record. This may impact the execution of Windows® jobs that need the specified user.

Add or correct the CPU name specified for the user USER.

Check the USRREC statements in the scheduler parameters to make sure that the CPU specified for the Windows users is correct.

EQQZ277W

THE NUMBER OF TABLES SPECIFIED FOR THE VARTABLES KEYWORD HAS EXCEEDED THE MAXIMUM LIMIT (16). THE EXCESS TABLES ARE IGNORED

A maximum of 16 tables can be specified in the VARTABLES keyword of the HTTPOPTS statement. This number has been exceeded and, as a consequence, the excess tables are ignored.

Processing continues, ignoring the tables in excess.

Correct the HTTPOPTS statement by specifying 16 tables or less for the VARTABLES keyword.

EQQZ278E

THE SSLKEYRING KEYWORD IS NOT SPECIFIED IN STATEMENT STMT. IF SSL IS ACTIVATED, THIS KEYWORD IS REQUIRED.

If you specified an SSL port greater than zero in the HTTPOPTS statement, the SSL connections are enabled. You must also specify the name of the key ring containing the security certificates. If the key ring is a key database USS file, specify the name of the file containing the key password.

Processing terminates.

Correct the HTTPOPTS statement by specifying the required keyword.

EQQZ279E

THE SSLKEYRINGPSW KEYWORD IS NOT SPECIFIED IN STATEMENT STMT. IF SSL IS ACTIVATED, AND THE KEY RING FILE IS A KEY DATABASE USS, THEN THIS KEYWORD IS REQUIRED.

If you have specified an SSL port greater than zero in HTTPOPTS, then SSL connections are enabled. If the key ring is a key database USS file, then you must also specify the name of the file containing the key password.

Processing terminates.

Correct the HTTPOPTS statement by specifying the required keyword.

EQQZ280E

PROXY KEYWORD VALUE VALUE IS TOO LONG OR MISSING.

A destination name specified as a value of the PROXY keyword in the ROUTOPTS statement is incorrect. The destination name is required and cannot exceed 8 characters.

Processing of the current ROUTOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.

Specify a correct value for the PROXY keyword, then restart the started task.

EQQZ281E

AT LEAST ONE VALUE IN THE PROXY KEYWORD IS INCORRECT.

The PROXY keyword in the ROUTOPTS statement specifies one or more incorrect PROXY destinations.
Processing of the current ROUTOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Specify a correct value for the PROXY keyword.

EQQZ283E

CHGDATE VALUE IS INCORRECT, VALID FORMAT IS YYMMDD.

An incorrect value has been specified for the CHGDATE parameter of OPCOPTS. The valid format is YYMMDD.
Processing stops.
Specify correct values for YY, MM, and DD, then restart the controller.

EQQZ284W

CHGOFF VALID VALUES ARE M, O, P. AN INCORRECT VALUE WAS SET, THE DEFAULT VALUE O IS USED.

Because an incorrect value was specified for the CHGOFF parameter of OPCOPTS, the default value is used instead. Valid values are:
M
Minus. The time change is intended 1 hour backward.
O
Off. The CHGDATE parameter is to be ignored. This is the default value.
P
Plus. The time change is intended 1 hour forward.
Processing continues.
If you do not want to use the default, set the value you want and restart the controller.

EQQZ285I

REBUILD PARAMETER WILL MERGE THE OLD SSX EVENT WRITER QUEUE BECAUSE OLD SSX AND NEW SSX ARE FOR THE SAME SSXLEV.

In OPCOPTS you set BUILDSSX(REBUILD), which requires the drop of the current SSX event queue. However, the drop is performed only when the old SSX control block is related to an FMID different from the current EQQMAJOR module FMID. This message is issued when you performed a migration requesting the drop of the SSX event queue, and the FMIDs for the old and new SSX were different. Then, you did not delete BUILDSSX(REBUILD) from the OPCOPTS parameter.
The event writer queue is not dropped. Processing continues.
Delete BUILDSSX(REBUILD) from the OPCOPTS parameter if no longer required.

EQQZ286I

RUNNING WITH MAXIMUM USER LEV USERLEV.

This message is issued every time that the Z controller and server are started. It shows the maximum user level supported.
Processing continues.
Ensure that the user level you are using is not higher than the maximum allowed.

EQQZ287E

KEYWORD KEYWD IN STATEMENT TCPOPTS IS MISSING, BUT SSLLEVEL IS SET TO FORCE AND SSLKEYSTORETYPE IS SET TO USS.

Because the statement TCPOPTS is set with SSLLEVEL(FORCE) and SSLKEYSTORETYPE(USS), the keyword KEYWD is required.

The started task initialization terminates.

Correct the statement TCPOPTS by either modifying the setting of SSLLEVEL and SSLKEYSTORETYPE or setting the keyword KEYWD to a valid value. Then restart the started task.

EQQZ290W

CDP PARAMETER IN OPCOPTS IS SET TO NO BUT THERE ARE SOME OTHER PARAMETERS SPECIFIED. THEY WIL BE IGNORED.

In OPCOPTS, parameters related to the CDP logging feature are specified, but the CDP parameter that activates the CDP logging is set to NO. The CDP logging feature is not activated.

The parameters related to CDP logging are ignored. Processing continues.

To activate the CDP logging, set CDP(YES) in the OPCOPTS statement.

EQQZ291W

CDP PARAMETER IN OPCOPTS IS SET TO YES, BUT CDPSWITCHLOGLIM PARAMETER IS NOT SET. CDPSWITCHLOGLIM IS SET TO ITS DEFAULT VALUE, 1000.

In OPCOPTS, the CDP parameter is set to YES but no value is specified for the CDPSWITCHLOGLIM parameter to set the number of records to be written before switching log. CDPSWITCHLOGLIM is automatically set to its default value (1000).
Processing continues.
To set a different value for the number of records to be written in the CDP logs before switching them, set CDPSWITCHLOGLIM to the value you want.

EQQZ292W

CDPPATH PARAMETER IS SET TO BLANK. CDP LOGGING IS DEACTIVATED.

In OPCOPTS, the CDPPATH parameter does not contain any value. The CDP logging is therefore deactivated.

The CDP logging is deactivated. Processing continues.

Specify a valid value for CDPPATH in OPCOPTS.

EQQZ293W

CDP PARAMETER IN OPCOPTS IS SET TO YES BUT CDPPATH PARAMETER IS NOT SET. CDP LOGGING IS DEACTIVATED.

In OPCOPTS, the CDPPATH parameter is not set. The CDP logging is therefore deactivated.
The parameter CDP(YES) is ignored. Processing continues.
To activate the CDP logging, specify a valid value for CDPPATH.

EQQZ294W

THE VALUE FOR CDPPATH PARAMETER IN OPCOPTS EXCEEDS MAX LENGTH OF 40 CHARS. CDP LOGGING IS DEACTIVATED.

In OPCOPTS, the CDPPATH parameter is set to a value longer than the maximum length allowed (40 characters). The CDP logging is therefore deactivated.
The parameter CDP(YES) is ignored. Processing continues.
To activate the CDP logging, specify a valid value for CDPPATH (an existing path in the HFS file system, up to 40 alphanumerical characters).

EQQZ295W

THE PATH SET FOR THE CDPPATH PARAMETER IN OPCOPTS DOES NOT EXIST. CDP LOGGING IS DEACTIVATED.

In OPCOPTS, the CDPPATH parameter is set to a path that does not exist. The CDP logging is therefore deactivated.
The CDP logging is deactivated. Processing continues.
Make sure that the value set for CDPPATH exists in the HFS file system. If exists, check that the RACF user ID used to run the controller is granted the OMVS rights required to access and modify that path.

EQQZ296W

CDP LOG FILE CANNOT BE CREATED. CDP LOGGING IS DEACTIVATED.

The CDP log file cannot be created, therefore the CDP logging is deactivated.
The CDP logging is deactivated. Processing continues.
Make sure that the RACF user ID used to run the controller is granted the OMVS rights required to create files in the path set in OPCOPTS(CDPPATH).

EQQZ297W

CDPSWITCHLOGLIM IS SET TO 0, BUT THIS IS NOT A VALID VALUE. CDPSWITCHLOGLIM WILL BE SET TO ITS DEFAULT VALUE, 1000.

The CDPSWITCHLOGLIM parameter is set to 0, which is not a valid value. The CDP logging is set to its default (1000).
Processing continues.
Specify a valid value for CDPSWITCHLOGLIM (from 1 to 999 999 999) or accept the default value.

EQQZ300W

RCLEANUP, FLOPTS, RCLOPTS VALID ONLY FOR CONTROLLER: THEY WILL BE IGNORED

You have specified one of the above mentioned options for a tracker, but they are meaningful only for a Controller.

The options are ignored. The scheduler continues processing.

Remove the RCLEANUP, FLOPTS, RCLOPTS options for the tracker configuration and run the task again.

EQQZ301W

RCLEANUP (NO): RCLOPTS WILL BE IGNORED

You have set the RCLEANUP option to NO, that is, the restart and cleanup function is not activated. The RCLOPTS statement specifies details about the restart and cleanup function: for this reason it is ignored.

The RCLOPTS statement is ignored. The scheduler continues processing.

None.

EQQZ302I

RCLEANUP(NO) : THERE ARE NO PROTECTED DATA SETS

Currently there is no data set protected via the DD statement name or directly via the data set name. You did not specify RCLEANUP(YES) so this function is not active and data set protection is redundant.

None.

EQQZ303W

RCLEANUP(NO): FLOPTS WILL BE IGNORED

You have specified the FLOPTS option that describes how the Controller communicates with data store. However, the OPCOPTS RCLEANUP option is not set to YES. Therefore, the FL task (the one responsible for Controller/Data Store communication) was not started

The scheduler continues processing. The restart and cleanup function is not activated. The FL task is not started.

Set RCLEANUP (YES) in the OPCOPTS statement.

EQQZ304E

FL TASK NEEDS FLOPTS

You have specified the OPCOPTS RCLEANUP (YES) statement but did not specify the FLOPTS option. FLOPTS is needed to allow communication between Controller and Data Store and, therefore, to support the restart and cleanup function.

The scheduler stops the process.

Add the FLOPTS option in the OPCOPTS statement.

EQQZ305I

THERE ARE NO DATA SETS PROTECTED BY DD STATEMENT NAME

Currently there is no data set protected via the DD statement name. You did not specify any initial parameter statement for this (for example, RCLOPTS DDPROT or DDPRMEM), nor did you issue a modify command to activate a member containing such a list.

None.

EQQZ306I

THERE ARE NO DATA SETS PROTECTED BY DATA SET NAME

Currently there is no data set protected by data set name. You did not specify any initial parameter statement for this (for example, RCLOPTS DDPROT or DDPRMEM), nor did you issue a modify command to activate a member containing such a list.

None.

EQQZ307I

THE DATA SETS PROTECTED BY TYPE ARE THE FOLLOWING:

This messages occurs after the issuing of one of the following modify commands:
/F subsystem,DSPPROTDD
- OR -
/F subsystem,DSPPROTDSN
TYPE identifies the kind of protection and can be DDNAME or DSNAME. It is followed by one or more EQQZ308I messages, one for each protected DD name or DS name.

None.

EQQZ308I

DSNAME

This messages occurs after the EQQZ307I message and identifies a protected data set name or DD name.

None.

EQQZ314W

CDP LOGGING IS ALREADY ENABLED

You issued a command to enable the CDP logging, which was already activated.
Processing continues.
None.

EQQZ315W

CDP LOGGING IS ALREADY DISABLED

You issued a command to disable the CDP logging, which was already inactivated.
Processing continues.
None.

EQQZ316W

THE CDPPATH PARAMETER IN OPCOPTS IS NOT SET, CDP LOGGING IS NOT ACTIVATED

A command to activate the CDP logging was issued, but the CDPPATH parameter in OPCOPTS is not set or was not set at controller startup. CDP logging is not activated.
Processing continues.
Set a valid value for the CDPPATH parameter, then restart the controller.

EQQZ317E

THE KEYWORD PARAMETER IN MAILOPTS STATEMENT HAS AN INVALID VALUE

In the MAILOPTS statement, the parameter indicated in the message is set to a value that is not valid.
Processing of the MAILOPTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Set a valid value for the parameter, then restart the controller. In particular, ensure that the value for the MAILFROM parameter contains the at character (@), and that the value for the MAILDOMAIN parameter does not contain the at character (@).

EQQZ319E

VALUE VAL FOR THE MAIL PARAMETER OF THE ALERTS STATEMENT IS INVALID

The value VAL of the MAIL parameter of the ALERTS statement is not correct.
Processing of the current ALERTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Set a valid value for the MAIL parameter, then restart the controller.

EQQZ320E

AT LEAST ONE VALUE IN THE MAIL PARAMETER OF THE ALERTS STATEMENT IS NOT CORRECT

At least one value of the MAIL parameter in the ALERTS statement is not valid.
Processing of the current ALERTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Set valid values for the MAIL parameter, then restart the controller.

EQQZ321E

THE VALUE VAL FOR THE MAIL PARAMETER OF THE ALERTS STATEMENT IS INCOMPLETE

The value set for the MAIL parameter is not complete. The valid syntax is alert condition:member name.

The supported alert conditions are DURATION, ERROROPER, HIGHRISK, LATEOPER, OPCERROR, POTENTRISK, SPECRES, and WLMOPER.

Processing of the current ALERTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Set valid values for the MAIL parameter, then restart the controller.

EQQZ323E

THE FILE WITH DDNAME=EQQSMTP COULD NOT BE OPENED.

The scheduler main task could not open the internal reader data set.
This error occurs when the scheduler main task tries to open the JES internal reader to send an email to an address. The main task processing ends.
Correct the errors in the controller startup procedure and restart the HCL Workload Automation for Z subsystem.
Check that the information contained in the EQQSMTP DD statement is correctly specified in the controller startup procedure. Also, review previous messages in the HCL Workload Automation for Z message log and system message log (for example, analyze the messages issued by the DFSMS) that refer to the EQQSMTP DD data set name by indicating an unusual condition.

EQQZ324E

UNEXPECTED ERROR SENDING AN EMAIL TO THE JES.

This error occurs when the scheduler main task tries to open the JES internal reader to send an email to an address.
The main task processing continues, but the email is not sent.
Correct the errors and either restart the submitted task or the HCL Workload Automation for Z subsystem.
Check that the information contained in the EQQSMTP DD statement is correctly specified in the controller startup procedure. Also, review previous messages in the HCL Workload Automation for Z message log and system message log (for example, analyze the messages issued by the DFSMS) that refer to the EQQSMTP DD data set name by indicating an unusual condition.

EQQZ325E

ERROR WRITING THE EMAIL TO THE FILE WITH DDNAME=EQQSMTP.

The scheduler main task could not write data into the internal reader data set.
This error occurs when the scheduler main task tries to write data into the internal reader to send an email to an address. The main task processing continues, but the email is not sent.
Correct the errors and either restart the submitted task or the HCL Workload Automation for Z subsystem.
Check that the information contained in the EQQSMTP DD statement is correctly specified in the controller startup procedure. Also, review previous messages in the HCL Workload Automation for Z message log and system message log (for example, analyze the messages issued by the DFSMS) that refer to the EQQSMTP DD data set name by indicating an unusual condition.

EQQZ326E

THE MAIL LIBRARY, DDNAME=EQQEMAIL, COULD NOT BE OPENED.

The scheduler main task could not open the email data set.
This error occurs when the scheduler main task tries to open the email data set in order to read the emails. The main task processing ends.
Correct the errors and restart the HCL Workload Automation for Z subsystem.
Check that the information contained in the EQQEMAIL DD statement is correctly specified in the controller startup procedure. Also, review previous messages in the HCL Workload Automation for Z message log and system message log (for example, analyze the messages issued by the DFSMS) that refer to the EQQEMAIL DD data set name by indicating an unusual condition.

EQQZ327E

LIBRARY WITH DDNAME EQQEMAIL COULD BE USED BY ANOTHER TASK.

Another user is accessing the data set with DD name EQQEMAIL.
The scheduler stops processing EQQEMAIL data set and the email is not sent.
Wait until the EQQEMAIL data set is released.

EQQZ328E

MEMBER MEMBER IS EMPTY IN LIBRARY WITH DDNAME EQQEMAIL.

The scheduler is accessing the member indicated in the message, but the member does not contain any information.
The scheduler stops sending the email to the addresses.
Populate the member with the required data.

EQQZ329E

MEMBER MEMBER NOT FOUND IN LIBRARY WITH DDNAME EQQEMAIL.

The scheduler is accessing the member indicated in the message, but the member is not found.
The scheduler stops sending the email to the addresses.
Populate the member with the required data.

EQQZ330E

UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF EQQEMAIL.

An error occurred when allocating storage to process the member indicated in the message.
The scheduler stops processing the indicated member.
Verify that the member indicated in the message is not too large. If it is not, determine which product or program, or both, is exhausting storage.

EQQZ331E

LOGICAL RECORD SIZE FOR THE LIBRARY WITH DDNAME EQQEMAIL IS NOT VALID.

HCL Workload Automation for Z cannot use the indicated library because its logical record length is not 80 bytes.
HCL Workload Automation for Z is terminated.
Check that EQQEMAIL is correctly defined. Eventually, correct the errors and restart HCL Workload Automation for Z

EQQZ332E

THE MAILDOMAIN PARAMETER OF THE MAILOPTS STATEMENT IS REQUIRED IF YOU DID NOT SET A VALUE FOR DOMAIN IN THE EMAIL ADDRESSES

The scheduler main task found an email header without the domain specified, and no default is provided in the MAILOPTS MAILDOMAIN statement.
The main task processing continues, but the email is not sent.
Set a domain in the email address within the member RULES of EQQEMAIL, or set a default domain in the MAILDOMAIN parameter of the MAILOPTS statement.

EQQZ333E

THE MAILFROM PARAMETER OF THE MAILOPTS STATEMENT IS REQUIRED IF YOU DID NOT SET A VALUE FOR THE FROM FIELD IN THE EMAIL ADDRESSES

The scheduler main task found an email header without the FROM keyword specified, and no default is provided in the MAILOPTS MAILFROM statement.
The main task processing continues, but the email is not sent.
Set a value for the FROM field within the member RULES in EQQEMAIL, or set a default address in the MAILFROM parameter of the MAILOPTS statement.

EQQZ334E

AN EMAIL DOES NOT CONTAIN ANY RECIPIENT FIELD. THIS IS NOT ALLOWED.

The scheduler main task found an email header without any value specified for the TO, CC, and BCC fields.
The main task processing continues, but the email is not sent.
Ensure that in the member RULES of EQQEMAIL, at least an address is set in one of the recipient fields.

EQQZ335E

PARAMETER PARM IS TOO LONG.

The parameter PARM specified in member RULES of the EQQEMAIL data set is too long.
Processing continues.
Set a valid value for the parameter.

EQQZ336E

PARAMETER PARM MUST START WITH ( CHARACTER.

The parameter PARM specified in member RULES of the EQQEMAIL must begin with the left parenthesis character.
Processing continues.
Set a valid value for the parameter.

EQQZ337E

PARAMETER PARM MUST END WITH THE ) CHARACTER.

The parameter PARM specified in member RULES of the EQQEMAIL data set must end with the right parenthesis character.
Processing continues.
Set a valid value for the parameter.

EQQZ338E

AT LEAST ONE FILTER PARAMETER MUST BE SET IN MEMBER MEMBER OF EQQEMAIL DATA SET. EMAILS CANNOT BE SENT .

At least one FILTER parameter must be specified in the member MEMBER of the EQQEMAIL data set.
Processing of the member MEMBER terminates with a non-zero return code. This causes that no emails can be sent.
Set a valid FILTER parameter.

EQQZ339E

THE VALUE FOR PARAMETER PARM FOUND IN MEMBER RULES OF EQQEMAIL DATA SET HAS A SYNTAX ERROR. EMAIL FOR THIS RULE CANNOT BE SENT.

The syntax of parameter PARM specified in member RULES of the EQQEMAIL data set has an error.
Processing continues but the email associated with the rule is not sent.
Set a correct value for the parameter PARM.

EQQZ340E

ONE PARM VALUE MUST BE SET IN EVERY RULE OF MEMBER RULES OF EQQEMAIL DATA SET. EMAIL FOR THAT RULE CANNOT BE SENT.

One parameter PARM must be specified for each rule in member RULES of the EQQEMAIL data set.
Processing continues, but the email associated with the rule is not sent.
Set a correct value for the parameter PARM.

EQQZ342E

CHARACTER = IS REQUIRED FOR EVERY EXPRESSION IN A FILTER PARAMETER VALUE.

An expression set in the parameter FILTER of a rule located in member RULES of EQQEMAIL data set is not valid, because the equals sign is missing.
Processing continues, but the email associated with the rule is not sent.
Set a valid value for the expression set in the parameter FILTER located in member RULES.

EQQZ344E

SYNTAX ERROR FOUND IN A RULE OF MEMBER RULES OF EQQEMAIL DATA SET. EMAIL FOR THAT RUE CANNOT BE SENT.

A syntax error was found in member RULES of the EQQEMAIL data set.
Processing continues, but the email associated with the rule is not sent.
Set valid values for the parameters in member RULES of the EQQEMAIL data set.

EQQZ345E

VARIABLE VARIABLE FOUND IN PARAMETER PARM CANNOT BE RESOLVED.

The parameter PARM within a rule in the member RULES of the EQQEMAIL data contains the variable VARIABLE, which cannot be resolved because it is unknown.
Processing continues, but the email associated with the rule is not sent.
Set a valid variable for the parameter PARM.

EQQZ346E

THE TRKPLS KEYWORD SPECIFIES A VALUE THAT IS NOT IN THE RANGE 1-10.

The parameter TRKPLS in the OPCOPTS initialization statement is set to a value outside of the valid range 1-10.
HCL Workload Automation for Z initialization fails.
Set the TRKPLS parameter to a value in the range 1-10 and restart HCL Workload Automation for Z.

EQQZ347E

THE KEYWD PARAMETER IN INCOPTS STATEMENT HAS AN INVALID VALUE.

In the INCOPTS initialization statement, the parameter indicated in the message is set to a value that is not valid.
Processing of the INCOPTS statement terminates with a non-zero return code.
Set a valid value for the parameter, then restart the controller.

EQQZ348I

KEYWORD KEYWD IS NOT SET IN THE STATEMENT INCOPTS. THE DEFAULT VALUE VALUE IS USED.

The specified keyword was not specified in the INCOPTS initialization statement.
The processing continues by using the default value for keyword KEYWD.
If you do not want the processing use the default, specify a value for keyword KEYWD in statement INCOPTS, then restart the started task.

EQQZ351E

LIBRARY WITH DDNAME EQQINCID COULD BE USED BY ANOTHER TASK.

Another user is accessing the data set with DD name EQQINCID.
The scheduler stops processing EQQINCID data set and the incident is not notified.
Wait until the EQQINCID data set is released.

EQQZ352E

MEMBER MEMBER IS EMPTY IN LIBRARY WITH DDNAME EQQINCID.

The scheduler is accessing the member indicated in the message, but the member does not contain any information.
The scheduler stops notifying the incidents.
Populate the member with the required data.

EQQZ353E

MEMBER MEMBER NOT FOUND IN LIBRARY WITH DDNAME EQQINCID.

The scheduler is accessing the member indicated in the message, but the member is not found.
The scheduler stops notifying the incidents.
Populate the member with the required data.

EQQZ354E

A VALUE FOR PARAMETER PARM IS REQUIRED.

The indicated parameter, which is required, was not specified in the INCOPTS statement.
Processing of the INCOPTS statement terminates with a non-zero return code.
Ensure that all the required parameters in INCOPTS are specified.

EQQZ355E

THE INCIDENT LIBRARY, DDNAME=EQQINCID, COULD NOT BE OPENED.

The scheduler main task could not open the incident data set.
This error occurs when the scheduler main task tries to open the EQQINCID data set in order to read the incidents. The main task processing ends.
Correct the errors and restart the HCL Workload Automation for Z subsystem.
Check that the information contained in the EQQINCID DD statement is correctly specified in the controller startup procedure. Also, review previous messages in the HCL Workload Automation for Z message log and system message log (for example, analyze the messages issued by the DFSMS) that refer to the EQQINCID DD data set name by indicating an unusual condition.

EQQZ356E

AT LEAST ONE VALUE IN THE INCIDENT PARAMETER OF THE ALERTS STATEMENT IS NOT VALID.

At least one value of the INCIDENT parameter in the ALERTS statement is not correct.
Processing of the current ALERTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Set a valid value for the INCIDENT parameter, then restart the controller.

EQQZ357E

THE VALUE VAL FOR THE INCIDENT PARAMETER OF THE ALERTS STATEMENT IS INCOMPLETE.

The value set for the INCIDENT parameter is not complete. The valid syntax is alert condition:member_name. The supported alert conditions are: DURATION, ERROROPER, HIGHRISK, LATEOPER, OPCERROR, POTENTRISK, SPECRES, and WLMOPER.
Processing of the current ALERTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Set a valid value for the INCIDENT parameter, then restart the controller.

EQQZ358E

VALUE VAL FOR THE INCIDENT PARAMETER OF THE ALERTS STATEMENT IS TOO LONG.

The indicated value in the INCIDENT parameter is too long. The valid syntax is alert condition:member_name, where the member_name can be up to 8 characters. The supported alert conditions are: DURATION, ERROROPER, HIGHRISK, LATEOPER, OPCERROR, POTENTRISK, SPECRES, and WLMOPER.
Processing of the current ALERTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Set a valid value for the INCIDENT parameter, then restart the controller.

EQQZ359E

VALUE VAL FOR THE INCIDENT PARAMETER OF THE ALERTS STATEMENT IS NOT VALID.

The value VAL of the INCIDENT parameter in the ALERTS statement is not correct.
Processing of the current ALERTS statement terminates with a non-zero return code. This causes the controller initialization to fail.
Set a valid value for the INCIDENT parameter, then restart the controller.

EQQZ360E

UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF EQQINCID.

An error occurred when allocating storage to process the member indicated in the message.
The scheduler stops processing the indicated member.
Verify that the member indicated in the message is not too large. If it is not, determine which product or program, or both, is exhausting storage.

EQQZ361E

CHARACTER = IS REQUIRED FOR EVERY EXPRESSION IN A FILTER PARAMETER VALUE.

An expression set in the parameter FILTER of a rule located in member RULES of EQQINCID data set is not valid, because the equals sign is missing.
Processing continues, but the incident associated with the rule is not notified.
Set a valid value for the expression set in the parameter FILTER located in member RULES.

EQQZ362E

VARIABLE VARIABLE FOUND IN PARAMETER PARM CANNOT BE RESOLVED.

The parameter PARM within a rule in the member RULES of the EQQINCID data contains the variable VARIABLE, which cannot be resolved because it is unknown.
Processing continues, but the incident associated with the rule is not notified.
Set a valid variable for the parameter PARM.

EQQZ363E

PARAMETER PARM IS TOO LONG.

The parameter PARM specified in member RULES of the EQQINCID data set is too long.
Processing continues, but the incident associated with the rule is not notified.
Set a valid value for the parameter.

EQQZ364E

PARAMETER PARM MUST END WITH THE ) CHARACTER.

The parameter PARM specified in member RULES of the EQQINCID data set must end with the right parenthesis character.
Processing continues, but the incident associated with the rule is not notified.
Set a valid value for the parameter.

EQQZ365E

PARAMETER PARM MUST START WITH ( CHARACTER.

The parameter PARM specified in member RULES of the EQQINCID must begin with the left parenthesis character.
Processing continues, but the incident associated with the rule is not notified.
Set a valid value for the parameter.

EQQZ366E

AT LEAST ONE FILTER PARAMETER MUST BE SET IN MEMBER MEMBER OF EQQINCID DATA SET. INCIDENTS CANNOT BE NOTIFIED .

At least one FILTER parameter must be specified in the member MEMBER of the EQQINCID data set.
Processing of the member MEMBER terminates with a non-zero return code. This causes that no incidents can be notified.
Set a valid FILTER parameter.

EQQZ367E

THE VALUE FOR PARAMETER PARM FOUND IN MEMBER RULES OF EQQINCID DATA SET HAS A SYNTAX ERROR. INCIDENT FOR THIS RULE CANNOT BE NOTIFIED.

The syntax of parameter PARM specified in member RULES of the EQQINCID data set has an error.
Processing continues but the incident associated with the rule is not notified.
Set a correct value for the parameter PARM.

EQQZ368E

AN INCIDENT DOES NOT CONTAIN A FIELD FIELD. THIS IS NOT ALLOWED.

The scheduler main task found an incident header without any value set for the field indicated in the message.
The main task processing continues, but the incident is not notified.
Ensure that in the member RULES of the EQQINCID data set, every rule header contains all the required fields.

EQQZ369E

SYNTAX ERROR FOUND IN A RULE OF MEMBER RULES OF EQQINCID DATA SET. INCIDENT FOR THAT RULE CANNOT BE NOTIFIED.

A syntax error was found in member RULES of the EQQINCID data set.
Processing continues, but the incident associated with the rule is not notified.
Set valid values for the parameters in member RULES of the EQQINCID data set.

EQQZ370E

ONE PARM VALUE MUST BE SET IN EVERY RULE OF MEMBER RULES OF EQQINCID DATA SET. INCIDENT FOR THAT RULE CANNOT BE NOTIFIED.

One parameter PARM must be specified for each rule in member RULES of the EQQINCID data set.
Processing continues, but the incident associated with the rule is not notified.
Set a correct value for the parameter PARM.

EQQZ371W

KEYWORD KEYWD IN STATEMENT INCOPTS IS NOT VALID. THE VALUE IS OUTSIDE THE VALID RANGE. WILL USE DEFAULT DEFAULT.

The value specified for keyword KEYWD is incorrect.

The processing continues by using the default value for keyword KEYWD.

Specify a valid value for keyword KEYWD. If you do not want the processing to use the default, restart the started task.

EQQZ372I

OPCTYP SSNAME IS READY TO WORK.

This message is issued when all the subtasks of the subsystem OPCTYP have started:
For the Z controller
General Service, Normal Mode Manager, Workstation Analyzer, Event Manager, Submit Task, Event Writer
For the tracker
Submit Task, Event Writer
The subsystem OPCTYP can be a Z controller or a z/OS tracker.

SSNAME indicates the scheduler subsystem.

Normal processing continues. The subsystem starts working, the indicated subtasks are active.

None.

EQQZ373W

OPCTYP SSNAME HAS TERMINATED TO WORK.

This message is issued when one of the following subtasks of the subsystem OPCTYP has ended:
For the Z controller
General Service, Normal Mode Manager, Workstation Analyzer, Event Manager, Submit Task, Event Writer
For the tracker
Submit Task, Event Writer
The subsystem OPCTYP can be a Z controller or a z/OS tracker.

SSNAME indicates the scheduler subsystem.

Normal processing continues. Because at least one subtask has ended, the subsystem might not work properly. At least one important subtask is not active.

To explore the problem, check for other messages related to the affected subtask in the EQQMLOG file.

EQQZ374E

KEYWORD KEYWD IN STATEMENT INCOPTS IS NOT VALID. THE VALUE EXCEEDS THE MAXIMUM ALLOWED.

The value specified for keyword KEYWD is too long.

Processing of the INCOPTS statement terminates with a non-zero value.

Specify a valid value for keyword KEYWD, then restart the controller.

EQQZ375E

LOGICAL RECORD SIZE FOR THE LIBRARY WITH DDNAME EQQINCID IS NOT VALID.

HCL Workload Automation for Z cannot use the indicated library because its logical record length is not 80 bytes.

HCL Workload Automation for Z is terminated.

Ensure that EQQINCID is correctly defined. Eventually, correct the errors and restart HCL Workload Automation for Z.

EQQZ376W

HEADER INFO VALUE IN MEMBER RULES OF EQQINCID IS NOT VALID. THE VALUE IS NOT ALLOWED. THE DEFAULT DEFAULT IS USED.

In the EQQINCID data set, the value specified for INFO in the HEADER of member RULES is not correct.

Processing continues by using the default value for INFO.

If you do not want to use the default for INFO, specify a valid value.

EQQZ377W

THE SUBTASK SUBNAME OF OPCTYP SSNAME HAS BEEN ENDED.

This message is issued when one of the following subtasks of the subsystem OPCTYP has ended:
For the Z controller
General Service, Normal Mode Manager, Workstation Analyzer, Event Manager, Submit Task, Event Writer
For the tracker
Submit Task, Event Writer
The subsystem OPCTYP can be a Z controller or a z/OS tracker.

SSNAME indicates the scheduler subsystem.

Normal processing continues. Because a subtask has ended, the subsystem might not work properly. The subtask SUBNAME is not active.

To explore the problem, check for other messages related to the affected subtask in the EQQMLOG file.

EQQZ378I

THE SUBTASK SUBNAME OF OPCTYP SSNAME HAS BEEN STARTED.

This message is issued only when one of the following subtasks of the subsystem OPCTYP has been ended and restarted:
For the Z controller
General Service, Normal Mode Manager, Workstation Analyzer, Event Manager, Submit Task, Event Writer
For the tracker
Submit Task, Event Writer
The subsystem OPCTYP can be a Z controller or a z/OS tracker.

SSNAME indicates the scheduler subsystem.

Normal processing continues.

None.

EQQZ403I

RUNNING PRODUCT NAME VERSION

This message is issued to identify the current product version.

Processing continues.

None.

EQQZ404I

THE PENF53 COMMAND HAS BEEN IGNORED BECAUSE THE ENF EXIT EQQZNF53 IS NOT ACTIVE

The ENF exit EQQZNF53 is not active, therefore your stop request is ignored.

The stop request is ignored.

EQQZ405I

THE PENF53 COMMAND HAS BEEN IGNORED BECAUSE THE ENF EXIT EQQZNF53 IS ALREADY ACTIVE

The ENF exit EQQZNF53 is already active, therefore your start request is ignored.

The start request is ignored.

EQQZ406I

ENF EXIT EXNAME WAS ACTIVATED. TOKEN TOKEN ADDRESS ADDRESS SIZE SIZ

At startup, the tracker or controller activated exit EXNAME. This message reports that the exit is loaded in CSA at Address ADDR with size SIZ.

Note that the value of SIZ exceeds by 8 bytes the real exit size (the value you see if you browse the partitioned data set containing the exit), because the exit module appends some extra information when it is loaded in the CSA.

The ENF deactivation request used token TOKEN to identify the exit.

EXNAME can be one of the following:
  • EQQZNF41
  • EQQZNF57

Exit EXNAME is now active and can generate VS events about scheduling environment availability.

None.

EQQZ407I

ENF EXIT EXNAME WAS DEACTIVATED. TOKEN TOKEN ADDRESS ADDRESS SIZE SIZ

When closing, the tracker or controller deactivated exit EXNAME. This message reports that the exit is loaded in CSA at Address ADDR with size SIZ.

The ENF deactivation request used token TOKEN to identify the exit.

EXNAME can be one of the following:
  • EQQZNF41
  • EQQZNF57

Exit EXNAME is now inactive, but is still in CSA.

None.

EQQZ408W

SWITCHMLOGLIM PARAMETER IS SPECIFIED BUT EQQMLOG2 DATA SET IS NOT AVAILABLE. MLOG SWITCH FUNCTION IS NOT ACTIVATED.

The EQQMLOG2 data set is unavailable for one of the following reasons:
  • The EQQMLOG2 data definition statement is missing
  • The data set is already in use by another task
  • The characteristics of the data set do not fit the MLOG specifications.
The MLOG switching function is not activated.

Add a DD statement for EQQMLOG2 in the JCL of the controller started task (EQQJOBS provides customized samples EQQCONO and EQQCON if you specified YES for the MLOG switching function in the EQQJOBSC panel). If the statement already exists, check that the associated data set is available or that EQQMLOG2 is not already used by another process.

EQQZ409E

EXIT EXNAME CANNOT BE LOADED

At startup, the tracker or controller detected that the associated exit EXNAME should be loaded in CSA and for this reason tried to load, but failed.

EXNAME can be one of the following:
  • EQQZNF41
  • EQQZNF57

Exit EXNAME is not loaded and the startup fails.

Check if the startup procedure can access the library where the exit resides.

Note that the exit is loaded by means of the macro LOAD.

EQQZ500E

UNABLE TO ALLOCATE GCAM CACHE

The scheduler was not able to allocate the GCAM cache required to handle the JOBLOG and OPERINFO pending requests correctly.

The scheduler terminates.

Check EQQMLOG to understand the reason for the failure. Increase the region size if storage was not sufficient.

Contact your system programmer.

EQQZ501E

AN ERROR OCCURRED WHILE UNLOADING GCAM CACHE INTO EQQLOGRC DATA SET

The scheduler was not able to unload the GCAM cache content into the log data set EQQLOGRC.

The EQQLOGRC does not contain all the JOBLOG and OPERINFO pending requests existing at Scheduler stop time.

Check EQQMLOG to understand the reason for the failure. JOBLOG and OPERINFO pending requests must be restarted manually.

Contact your system programmer.

EQQZ502I

JOBLOG RETRIEVAL PENDING REQUEST RESUMED FOR JOBN (JID) APPL: APPL, IA, OPER

At startup, the scheduler detected that a JOBLOG retrieval process is pending for the job identified by Job Name JOBN, Job ID JID, Application Name APPL, Input arrival time IA, operation number OPER. As soon as FL task and HTTP task are started, the pending request will be resumed to be restarted.

The JOBLOG retrieval process is resumed.

EQQZ503I

OPERINFO RETRIEVAL PENDING REQUEST RESUMED FOR JOBN (JID) APPL: APPL, IA, OPER

At startup, the scheduler detected that an OPERINFO retrieval process is pending for the job identified by Job Name JOBN, Job ID JID, Application Name APPL, Input arrival time IA, operation number OPER. As soon as FL task is started, the pending request will be resumed to be restarted.

The OPERINFO retrieval process is resumed.

EQQZ504W

UNABLE TO RESUME JOBLOG RETRIEVAL PENDING REQUEST FOR JOBN (JID) APPL: APPL, IA, OPER

At startup, the scheduler detected that a JOBLOG retrieval process is pending for the job identified by Job Name JOBN, Job ID JID, Application Name APPL, Input arrival time IA, operation number OPER. The pending request should have been resumed to be restarted after FL task and HTTP task were started, but an error occurred.

The JOBLOG retrieval process is not resumed.

Check EQQMLOG to understand the reason for the failure.

Contact your system programmer.

EQQZ505W

UNABLE TO RESUME OPERINFO RETRIEVAL PENDING REQUEST FOR JOBN (JID) APPL: APPL, IA, OPER

At startup, the scheduler detected that an OPERINFO retrieval process is pending for the job identified by Job Name JOBN, Job ID JID, Application Name APPL, Input arrival time IA, operation number OPER. The pending request should have been resumed to be restarted after FL task and HTTP task were started, but an error occurred.

The OPERINFO retrieval process is not resumed.

Check EQQMLOG to understand the reason for the failure.

Contact your system programmer.

EQQZ506E

UNABLE TO PERFORM THE CHECK ROLE PROCESSING

An error occurred in the controller initialization or TCP/IP communication, so that the controller cannot perform the check role processing.

The controller initialization fails.

Correct the error that prevents the controller from being initialized, or set OPCOPTS CHECKROLE to NO; in this way, the controller will start with the role based on the value set in OPCOPTS OPCHOST.

EQQZ507W

THE CHECK ROLE PROCESSING DETECTED THAT THE BACKUP CONTROLLER IS RUNNING AS PRIMARY CONTROLLER. THIS CONTROLLER IS STARTED AS BACKUP CONTROLLER.

The check role process detected that the controller with OPCOPTS OPCHOST set to BACKUP is running as the primary controller. This controller is therefore started as backup controller.

The controller is started as backup controller.

None.

EQQZ600E

THE SSL ENVIRONMENT IS NOT CONFIGURED IN HTTPOPTS. IF FTPROXYHOST IS SPECIFIED, THE SSL PARAMETERS ARE REQUIRED.

You specified the FTPROXYHOST parameter in the HTTPOPTS statement, but the SSL environment is not configured. To communicate with the Z controller, the File Transfer proxy requires an SSL connection.

Processing terminates.

Correct the HTTPOPTS statement by specifying the parameters required for enabling an SSL connection.

EQQZ601E

TLS V1.2 IS THE MINIMUM VERSION SUPPORTED. ANY EARLIER VERSION IS AUTOMATICALLY DISABLED.

See the message text.

Processing continues.

None.

EQQZ810I

THE NUMBER OF COMPLETED JOBS THAT WERE RUN ON DYNAMIC AND Z-CENTRIC AGENTS FROM FROMDATE UNTIL NOW IS NUM

The DP batch job calculated that the number of jobs that were successfully run on z-centric and dynamic agents, from the date indicated in the message until now, is NUM.
Processing continues.
None.

EQQZ811E

THE DATA SET WITH DDNAME EQQFLEX COULD NOT BE OPENED

The scheduler main task, the DP batch job, or the job connecting to the license sever cannot open the license data set to read the data.
The scheduler main task, the DP batch job, or the job connecting to the data set stop processing. Scheduling on z-centric and dynamic agents cannot start.
Check that the information contained in the EQQFLEX DD statement is correctly specified in the controller startup or jobs procedure. Also, review previous messages in the message log of process in error and system message log (for example, analyze the messages issued by the DFSMS) that refer to the EQQFLEX DD data set by indicating an unusual condition.

After correcting the error, restart the program that stopped processing.

EQQZ812E

THE DATA SET WITH DDNAME EQQFLEX MUST BE INITIALIZED BY THE CONTROLLER

The DP batch job or the job connecting to the license sever found that the data set with DD name EQQFLEX has not been initialized by the controller.
The job stops processing.
Check that the information contained in the EQQFLEX DD statement is correctly specified in the controller startup or jobs procedure. Also, review previous messages in the message log and system message log (for example, analyze the messages issued by the DFSMS) that refer to the EQQFLEX DD data set by indicating an unusual condition.

After correcting the error that prevents the scheduler main task from initializing the data set indicated by the message, restart the HCL Workload Automation for Z subsystem.

EQQZ813I

THE DATA SET WITH DDNAME EQQFLEX HAS BEEN INITIALIZED

The scheduler main task has initialized the license data set.
Processing continues.
None.

EQQZ814W

THE KEYWORD KEY IN STATEMENT STMT IS MISSING

The keyword KEY is not set in the indicated statement, but it is required for scheduling on z-centric agents.
Processing continues and the statement STMT is ignored.
Specify a value for the keyword KEY and restart HCL Workload Automation for Z to work in an environment with z-centric capabilities.

EQQZ815E

LICENSE INFORMATION IS NOT READABLE. TO RESOLVE THE PROBLEM CONTACT SUPPORT.

No valid information is found in the license data set with DD name EQQFLEX. The file seems corrupted.
Processing continues, but no more jobs can be scheduled on z-centric agents.
Contact the Support to repair the license data set.

EQQZ816E

LICENSE INFORMATION IS NOT READABLE. TO RESOLVE THE PROBLEM CONTACT SUPPORT.

No valid license information is found in the AD data set. The information seems corrupted.
Processing continues, but no more jobs can be scheduled on z-centric agents.
Contact the Support to repair the license data set.

EQQZ817I

LICENSE INFORMATION HAS BEEN CORRECTED.

The license information has been corrected.
Processing continues, and jobs can be scheduled on z-centric and dynamic agents.
None.

EQQZ818I

LICENSE INFORMATION JOB STARTED (PROCN JOBID).

The NMM task started the license connection job that is identified by job PROCN and job ID JOBID.
The job is submitted. Processing continues.
None.

EQQZ819E

LICENSE CONNECTION JOB FAILED (PROCN): REASON.

The NMM task could not start the license connection job that is identified by 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 license connection job is not submitted. Processing continues.
Correct the error, and manually submit the license connection job or re-run a daily planning process.

The error JCL NOT FOUND means that the job to be submitted is not found. In this case, copy the EQQFLEX member of the sample job JCL to the controller JOBLIB.

EQQZ820W

LICENSE INFORMATION PROBLEM FOUND. SUBMISSION FOR ZCENTRIC AND DYNAMIC WORKSTATIONS IS DISABLED.

No valid license information is found.
Processing continues, but no more jobs can be scheduled on z-centric and dynamic agents.
To understand the cause of the problem, analyze further messages in EQQMLOG.

EQQZ822E

THE DATA SET NAME PROVIDED IN EQQFLEX DD STATEMENT IS NOT EQUAL TO FLEXERA DATA SET NAME USED BY CONTROLLER.

The data set name provided with the EQQFLEX DD statement in the job is different from the data set name used by the controller for the same DD statement. The controller and jobs using the EQQFLEX DD statement must use the same data set name related to that DD statement.
The job is terminated.
Change the data set name provided in the EQQFLEX DD statement in the job, so that it is coincident with the data set name used by the controller.

EQQZ823I

THE NUMBER OF COMPLETED JOBS THAT WERE RUN ON Z-CENTRIC AND DYNAMIC AGENTS FROM FROMDATE THAT MUST BE STILL COMMUNICATED TO LICENSE SERVER IS JOBSNUM

The DP batch job calculated that the number of jobs that were successfully run on z-centric and dynamic agents from the date indicated in the message and that must be communicated to the license server is JOBSNUM.
Processing continues.
None.

EQQZ824I

JOBS SUBMISSION FOR Z-CENTRIC AND DYNAMIC AGENTS HAS BEEN ACTIVATED

Jobs submission on z-centric and dynamic agents has been activated again.
Processing continues.
None.

EQQZ825E

AN ERROR WAS FOUND WHILE RUNNING THE EQQFLEX JOB USED TO CONNECT TO THE LICENSE SERVER. THE ERROR IS ERRMSG.

While checking the licenses for submitting jobs on z-centric and dynamic agents, one of the following error messages was found:
'CANNOT_LOAD_KEY'
The key to connect to the license server was not found.
'DATASET_CORRUPTED'
The EQQFLEX data set is corrupted.
'DSNAME_NOT_EQUAL'
The EQQFLEX data set that is used by the EQQFLEX job to connect to the license server is different from the EQQFLEX data set used by the Z controller.
'COMMUNICATION_ERROR'
Cannot communicate with the license server. For details, see the Flexera.log, which by default is located in the work directory.
'UNKNOWN_ERROR_CODE'
The EQQFLEX job that is used to connect to the license server has detected an unknown error.
Processing continues, but no more jobs can be submitted on z-centric and dynamic agents.
Correct the error and run the EQQFLEX job again.

EQQZ826E

AN ERROR WAS FOUND DURING THE LICENSE CHECKING. THE ERROR MESSAGE IS ERRMSG.

While trying to communicate with the license server, one of the following errors was found:
'NULL_PAYLOAD'
The license is empty.
'FEATURE_NOT_AVAILABLE'
The provided license is not available.
'FEATURE_NOT_STARTED'
The provided license has not been activated.
'FEATURE_EXPIRED'
The license has expired.
'FEATURE_COUNT_INSUFFICIENT'
The license computation is not sufficient to submit additional jobs.
Processing continues, but no more jobs can be submitted on z-centric and dynamic agents.
Contact the Support to resolve the license problem.

EQQZ850E

NO LICENSED TO RUN ON CPU.

The license check failed. The CPU check failed.

The controller stops, and cannot be restarted until the license problem is resolved.

The license must be updated to be congruent with the system where the controller runs. For details about the license certificate implementation, see the Program Directory.

EQQZ851E

CPU MSU RATING TOO HIGH.

The license check failed. The MSU rate check failed.

The controller stops, and cannot be restarted until the license problem is resolved.

The license must be updated to be congruent with the system where the controller runs. For details about the license certificate implementation, see the Program Directory.

EQQZ852E

BEFORE LICENSE START DATE.

The license check failed, because the starting date of validity is later than the current date.

The controller stops, and cannot be restarted until the license problem is resolved.

The license must be updated to be congruent with the system where the controller runs. For details about the license certificate implementation, see the Program Directory.

EQQZ853E

LICENSE EXPIRED.

The license check failed, because the ending date of validity is earlier than the current date.

The controller stops, and cannot be restarted until the license problem is resolved.

The license must be updated to be congruent with the system where the controller runs. For details about the license certificate implementation, see the Program Directory.

EQQZ858I

RUNNING PRODUCTNAME VERSION VERSION PRODUCT FMID AT SERVICE LEVEL LEVEL

This message is issued every time the Z controller is started. LEVEL is in the format YY/MM/DD HH.MM.SS YYXXXXX where:
YY/MM/DD
Date of the build.
HH.MM.SS
Time of the build.
YYXXXXX
Maintenance level of the product.

None.

None.

EQQZ859W

DAYS MISSING TO LICENSE EXPIRING: DAYS

The license is going to expire within the number of days specified in DAYS.

The controller continues to run.

The license check is done at controller startup and at every daily planning EXTEND. This means that this message is issued until the license is renewed or expires. When the license expires, the controller is stopped and cannot be restarted until the license problem is resolved.

This message starts to be issued two weeks before expiration. For details about the license certificate implementation,, see the Program Directory.

EQQZ908W

MLOG SWITCH PROCEDURE MLOGPROC JOBID FAILED

The MLOG switch procedure failed because a problem was found with procedure MLOGPROC defined in the MLOGPROCNAME keyword of the OPCOPTS initialization statement.

No MLOG switching takes place and the component messages are sent to the system log.

Check that MLOGPROC was copied into your proclib or see if there is any other problem with it and correct it.