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

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

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

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

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

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

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 task module, EQQMAJOR, has been incorrectly invoked.

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 EQQINIT0 program.

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

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

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

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.

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

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.

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

An initialization statement cannot exceed 455 input records.

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

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

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

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

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

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

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

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 cannot open its message log data set.

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

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

HCL Workload Automation for Z cannot initialize its message services.

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.

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.

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

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.

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.

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 NCFAPPL keyword is required, because you specified NCFTASK(YES) in the OPCOPTS initialization statement.

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

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.

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

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.

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

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 GSTASK keyword in the OPCOPTS initialization statement specifies an invalid value.

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

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.

An operator cancel command has been received.

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

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 cannot use the parameter library data set, ddname EQQPARM, because its logical record length is not 80 bytes.

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

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

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

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

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

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 first character of the SYSOUTDISP value is not one of the four valid characters: blank, H, R, or D.

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

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

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

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.

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

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.

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

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

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

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

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.

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.

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.

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

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

The DB2 system specified in the DB2SYSTEM keyword of the OPCOPTS initialization statement is not active.

The DB2 system specified in the DB2SYSTEM keyword of the OPCOPTS statement has been started. The HCL Workload Automation for Z history function is now available.

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

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

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

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

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

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

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 subsystem task module, EQQMAJOR, has been incorrectly invoked.

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.

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

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.

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 current AUDIT statement does not contain the FILE keyword.

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

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 keyword shown in the message text is obsolete and is no longer supported.

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

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.

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

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

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

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.

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

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

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.

The utilization of a queue has exceeded a threshold value.

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.

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.

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.

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.

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

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.

The initialization statement is inconsistent.

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.

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.

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

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

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

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

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.

The specified keyword in the current initialization statement is required.

The HOSTCON keyword in the TRROPTS initialization statement is missing.

This duplication is not allowed.

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

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

This system has been fully initialized in standby mode.

This system has started takeover processing.

An XCF transmission was not successfully sent.

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

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

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

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

A tracker system was started with no TRROPTS initialization statement.

An invalid value has been set for the WAITREL keyword.

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.

A nonnumeric date value has been specified.

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.

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

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

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

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

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.

A nonnumeric time value has been specified.

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

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

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

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

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.

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.

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

The value of 0 is invalid.

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

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.

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.

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

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

The scheduler successfully updated the data set triggering selection table.

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

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.

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

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.

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.

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

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.

During symbol substitution processing, an unexpected error occurred.

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.

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

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.

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

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

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.

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

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

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

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.

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

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

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

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

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

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

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.

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.

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

The automatic restart management (ARM) OPERATION has completed.

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.

The server could not locate a required load module.

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.

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.

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

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.

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

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

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

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

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

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

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.

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.

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.

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

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

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.

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

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

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

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

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

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 value specified for the MONPORT or LOCPORT parameter in the MONOPTS statement was not specified or recognized.

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

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

The CODEPAGE parameter in the OPCOPTS statement was not specified.

The MONPOL statement contains the CRITPATH obsolete parameter.

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

The value specified for keyword KEYWD is incorrect.

Keyword KEYWD was not specified in statement STMT.

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

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 initialization statement is inconsistent.

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.

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

Keyword KEYWD was not specified in statement STMT.

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 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 could not open the required EQQEVLIB data set.

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

Another task or user is accessing the EQQEVLIB data set.

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

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

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

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

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

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

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

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.

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

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.

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.

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

The USRREC statement requires the USRNAM keyword.

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

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.

If you have specified an SSL port greater than zero in HTTPOPTS, then 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, then specify the name of the file containing the key password.

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.

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.

The CHGTIME parameter of the OPCOPTS statement is set to an invalid value. Verify that the format HHM was used and that the values specified for HH and MM are valid.

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

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.

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.

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

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.

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.

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.

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

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

This message is issued to identify the current product version.

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

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

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.

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.

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.

The scheduler was not able to allocate the GCAM cache required to handle the JOBLOG and OPERINFO pending requests correctly.

The scheduler was not able to unload the GCAM cache content into the log data set EQQLOGRC.

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.

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.

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.

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.

An error occurred in the controller initialization or TCP/IP communication, so that the controller cannot perform the check role processing.

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.

• JOBLIB NOT OPENED
• JCL RETRIEVAL FAILURE
• INSUFFICIENT STORAGE
• EMPTY JCL
• JCL NOT FOUND
• LOGICAL RECORD SIZE NOT VALID

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

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

The license check failed. The CPU check failed.

The license check failed. The MSU rate check failed.

The license check failed, because the starting date of validity is later than the current date.

The license check failed, because the ending date of validity is earlier than the current date.

The license is going to expire within the number of days specified in DAYS.

The MLOG switch procedure failed because a problem was found with procedure MLOGPROC defined in the MLOGPROCNAME keyword of the OPCOPTS initialization statement.