EQQSU01 - EQQSU44

EQQSU01I

THE SUBMIT TASK HAS STARTED

The submit task has successfully completed initialization.

The submit task processing starts.

None.

EQQSU02I

THE SUBMIT TASK HAS ENDED

The submit task has terminated processing normally. An operator has stopped the submit task or the HCL Workload Automation for Z subsystem has stopped.

The submit task processing is terminated.

None.

EQQSU03E

THE SUBMIT TASK HAS ENDED DUE TO PROCESSING ERRORS

The submit task cannot continue processing due to a severe error.

The submit task processing is terminated.

Correct the errors and restart the submit task.

Review previous messages in the HCL Workload Automation for Z message log. Correct them e restart the task.

EQQSU04E

THE SUBMIT TASK INITIALIZATION FAILED, THE TASK IS TERMINATED

The submit task could not acquire the resources required for normal operation.

The submit task processing is terminated.

Correct the errors and restart the submit task.

Review previous messages in the HCL Workload Automation for Z message log. Correct them e restart the task.

EQQSU05E

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

The submit task could not open the internal reader data set.

If the error occurs when the submit task is being initialized, the submit task processing is terminated and message EQQSU04 is issued.

If the error occurs when the submit task tries to reopen the internal reader to perform a submit for a user, the submit task processing continues, but the current job is not submitted.

Correct the errors and restart either the submit task or the HCL Workload Automation for Z subsystem.

Check that DDNAME EQQBRDS is correctly specified in the startup procedure. Also review previous messages in the HCL Workload Automation for Z message log and in the system message log (for example analyze the messages issued by the DFSMS) referencing the EQQBRDS DD dataset name, that indicates an unusual condition.

EQQSU06E

A SEVERE ERROR IN THE SUBMIT TASK HAS CAUSED ONE OR MORE REQUESTS TO BE LOST

The submit task abended while processing elements on SUBQ. The chaining of elements on SUBQ has been corrupted.

z/OS recovery termination is requested to generate a dump. All elements currently on SUBQ are skipped. The submit task attempts to continue normal processing.

Correct the errors and restart either the submit task or the HCL Workload Automation for Z subsystem. If the problem persists, save the message log and dump data sets. Search the IBM Support database for a solution at http://www.ibm.com/software/sysmgmt/products/support.

Review the HCL Workload Automation for Z message log data set and the dump data set to determine the cause of the problem. Provide the info to your System Programmer.

EQQSU07E

THE SUBMIT TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: REQUEST

An abend prevented the submit task from processing a queue element.

z/OS recovery termination is requested to generate a dump. The submit task attempts to continue normal processing.

Analyze the errors, correct them, and restart either the submit task or the HCL Workload Automation for Z subsystem. Retry the operation. If the problem persists, save the message log and dump data sets. Search the IBM Support database for a solution at http://www.ibm.com/software/sysmgmt/products/support.

Review the HCL Workload Automation for Z message log data set and the dump data set to determine the cause of the problem. Provide the info to your System Programmer.

EQQSU09W

JOB JOBNAME(JOBNUM) COULD NOT BE RELEASED. REPEATED RETRIES HAVE FAILED

The submit task received a release request for a job, but could not communicate successfully with JES while trying to release the job from hold.

No more attempts to release the job are made. The submit task continues processing.

Review system and JES load for any unusual peek causing response degradation in the 5 minutes retry window. Try to better balance the system workload.

Review the system log and look for previous JES messages that indicate unusual conditions. Determine the current status of the job. If necessary, release the job manually.

EQQSU10E

JOB JOBNAME IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE THE SUBMIT EXIT OR THE USER FIELD WITH FIELD NAME SUBJOBUSER RETURNED A SUBMITTING USER ID, USER, WHOSE AUTHORITY COULD NOT BE DETERMINED

The job submit exit or the indicated user field returned a TSO user ID. A job submit environment could not be built for this user ID, because of an authority error.

The current job is not submitted. The submit task continues processing.

If necessary, submit the job manually.

Check that the job submit exit EQQUX001 or the user field SUBJOBUSER returns only valid TSO user IDs.

EQQSU11W

DDNAME EQQEVDS IS MISSING OR SPECIFIES DD DUMMY

The submit task is starting and does not have access to an event data set. The header record (record 0) in the event data set is used for submit checkpointing, and with no event data set available for submit checkpointing, submit requests may be lost or duplicated.

The submit task continues processing, but does not checkpoint submit requests. The first submit request received after start up causes message EQQSU22E to be issued.

Allocate a unique event data set to the EQQEVDS DD statement. If this HCL Workload Automation for Z address space does not start an event writer subtask, that is, EWTRTASK(NO) in OPCOPTS, allocate the event data set with two tracks of space.

Verify the JCL procedure for this HCL Workload Automation for Z address space. Verify the dataset name specified in the DDNAME EQQEVDS.

EQQSU12I

MAX NUMBER OF WORKSTATIONS CHECKPOINTED BY THIS SUBMIT TASK: #WS

Using the EQQEVDS data set LRECL, the submit task has calculated the maximum number (#WS) of workstations that can be checkpointed by this submit task.

Normal processing continues.

None.

None.

This message is for information only.

EQQSU13E

THE STARTED TASK FILE, DDNAME = EQQSTC, COULD NOT BE OPENED FOR OUTPUT

The submit task was unable to open the started task temporary proclib data set. This file is defined by the EQQSTC DD statement in the JCL procedure used to start the HCL Workload Automation for Z subsystem.

If the error is discovered during the start of HCL Workload Automation for Z, the submit task issues message EQQSU04 and is terminated. If the error is discovered during submit of a started task, this message is followed by message EQQW759W and the submit task stops submitting started tasks.

Make sure that the HCL Workload Automation for Z subsystem is properly authorized to use the temporary proclib data set, that the EQQSTC DD statement is correctly defined, and restart either the submit task or the HCL Workload Automation for Z subsystem.

Check that the EQQSTC DD statement is correctly specified in the startup procedure. Verify that the HCL Workload Automation for Z subsystem is authorized to open the temporary proclib data set for output. If RACF is installed, determine if the SYSLOG file contains an ICH408 access violation message for the temporary proclib data set.

EQQSU14W

THE SUBMIT TASK IS IN TERMINATION PHASE, JOB JOBNAME (JOBNUM) COULD NOT BE RELEASED

The submit task received a STOP command and HCL Workload Automation for Z could not release the job from hold.

No more attempts to release the job are made, because the submit task is stopped.

Make sure that the submit task termination is an expected situation and is not caused by a preceding error condition.

Determine the current status of the job. If required, release the job manually when HCL Workload Automation for Z is restarted.

EQQSU20E

UNABLE TO READ EQQEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE ON WORKSTATION WSNAME

The submit task was unable to execute a submit checkpoint request for the stated reason. Valid requests for the request type are:
J0
Request for submit checkpoint sequence number
J1
Job submit checkpoint request
J2
STC start checkpoint request
WTO
Message checkpoint request.

The submit task continues normal processing.

If necessary, stop HCL Workload Automation for Z, take corrective action, and restart HCL Workload Automation for Z.

Review earlier messages in the HCL Workload Automation for Z message log and system message log (I/O or dasd related errors) to determine the cause of the error during Header retrieval.

EQQSU21E

UNABLE TO UPDATE EQQEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE ON WORKSTATION WSNAME

The submit task was unable to execute a submit checkpoint request for the stated reason. Valid requests for the request type are:
J0
Request for submit checkpoint sequence number
J1
Job submit checkpoint request
J2
STC start checkpoint request
WTO
Message checkpoint request.

The submit task continues normal processing.

If necessary, stop HCL Workload Automation for Z, take corrective action, and restart HCL Workload Automation for Z.

Review earlier messages in the HCL Workload Automation for Z message log and system message log (I/O or dasd related errors) to determine the cause of the error during Header replacement.

EQQSU22E

UNABLE TO ACCESS THE EQQEVDS FILE FOR REQUEST TYPE DQETYPE ON WORKSTATION WSNAME

The submit task was unable to execute a submit checkpoint request for the stated reason. Valid requests for the request type are:
J0
Request for submit checkpoint sequence number
J1
Job submit checkpoint request
J2
STC start checkpoint request
WTO
Message checkpoint request

The submit task continues normal processing.

If necessary, stop HCL Workload Automation for Z, take corrective action, and restart HCL Workload Automation for Z.

Review earlier messages in the HCL Workload Automation for Z message log related to disabled checkpointing to determine the cause of the error.

EQQSU23E

NO FREE SPACE IN EQQEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE ON WORKSTATION WSNAME

The submit task was unable to run a submit checkpoint request because all workstation entries in the header record of the event data set are used. Valid requests for the request type are:
J0
Request for submit checkpoint sequence number
J1
Job submit checkpoint request
J2
STC start checkpoint request
WTO
Message checkpoint request

The submit task continues normal processing.

If necessary, stop HCL Workload Automation for Z, scrap and reallocate the EQQEVDS with a larger LRECL, and restart HCL Workload Automation for Z.

The maximum number of workstations that this EQQEVDS can checkpoint yis indicated in message EQQSU12I. If you have more workstations defined for this destination to checkpoint, you should reallocate the EQQEVDS with a larger logical record length. Refer to the Planning and Installation for more details.

EQQSU24W

WORKSTATION WSNAME IS NOT PRESENT IN THE EQQEVDS HEADER RECORD

The submit task could not remove a workstation name from the header record in the event data set because the name is not present.

The submit task continues normal processing.

If necessary, stop HCL Workload Automation for Z, take corrective actions, and restart HCL Workload Automation for Z.

Verify if the EQQEVDS DD data set name is the correct one to use. Verify if the used EQQEVDS was reallocated from scrap.

EQQSU30W

JOB CARD NOT FOUND OR INVALID. SPIN PREVENTION NOT POSSIBLE FOR: TYPJOB NAME in Application APPL IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Job name NAME
  • Application name APPL
  • Input Arrival Time IA
required tailoring for SPIN prevention, but no job card was found in the JCL.

The job or started task is submitted as it is.

Misplacement of the job card could also be due to a JCL coding error. If the problem is a JCL error, correct it.

If the job card is missing, consider the following:

  • SPIN prevention is applied only if Restart and Clean Up or the JCC functions are active.

  • The Restart and Clean Up functions automatically add the job card when it is missing.

If you are using JCC but no Restart and Clean Up, you need to transform your started task in JOB to have SPIN prevention applied. If SPIN prevention is not required for the started task, ignore this message.

EQQSU31I

TYPJOB NAME IN APPLICATION APPL IA IA HAD JESLOG KEYWORD SET TO JKEY. IT HAS BEEN REPLACED BY JESLOG=NOSPIN.

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Application name APPL
  • Input Arrival Time IA
  • Job name NAME
has the JESLOG set to JKEY and not to NOSPIN.

The job or started task is submitted after having replaced the JESLOG=JKEY with JESLOG=NOSPIN.

None.

EQQSU32W

GETMAIN FAILED. SPIN PREVENTION NOT POSSIBLE FOR TYPJOB NAME IN APPLICATION APPLN IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Application name APPL
  • Input Arrival Time IA
  • Job name NAME
could not be tailored by inserting or replacing the JESLOG=NOSPIN keyword because of storage problems.

Tailoring is needed to apply SPIN prevention.

The job or started task is submitted as it is.

Check the JCL to see if it is possible to split the job card into more lines so that tailoring for SPIN prevention does not require additional storage allocation.

Increase the region of tracker address space, if possible.

EQQSU33W

TAILORING FAILURE. SPIN PREVENTION NOT POSSIBLE FOR: TYPJOB NAME IN APPLICATION APPL IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Job name NAME
  • Application name APPL
  • Input Arrival Time IA
could not be tailored by inserting or replacing the JESLOG=NOSPIN keyword.
Tailoring is needed to apply SPIN prevention and consists of the insertion of the JESLOG=NOSPIN keyword. This was not possible for one of the following reasons:
  • The job card does not allow a new keyword to be added
  • The job card was not found
  • Not enough storage is available
  • There are JCL coding problems

The job or started task is submitted as it is.

Check if the JCL can be changed to add the JESLOG=NOSPIN keyword.

EQQSU34E

JOB CARD NOT FOUND OR INVALID. SCHEDULING ENVIRONMENT TAILORING NOT POSSIBLE FOR: TYPJOB NAME IN APPLICATION APPL IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Application name APPL
  • Input Arrival Time IA
  • Job name NAME
could not be tailored by inserting or replacing the SCHENV=Scheduling Environment Name keyword.

Misplacement of the job card could also be due to a JCL coding error.

The job or started task is set to error with code OSUB.

If the problem is a JCL error, correct it. See if you can change it to add the SCHENV keyword. If the job card is missing, add one.

EQQSU35W

SCHEDULING ENVIRONMENT SCHE NOT AVAILABLE FOR JOB: NAME IN APPLICATION APPL IA IA JPLEX

The job identified by:
  • Application name APPL
  • Input Arrival Time IA
  • Job name NAME
could not be submitted because the associated scheduling environment SCHE is not available. The JPLEX parameter specifies if the scheduling environment is unavailable at the JESplex level only or throughout the entire sysplex.

The job is set to ready status with extended status Waiting for SE. It will be submitted again when the Scheduling Environment becomes available.

Check why the specified scheduling environment is unavailable and make it available, if possible.

EQQSU36W

SCHEDULING ENVIRONMENT SCHE NOT DEFINED FOR JOB: NAME IN APPLICATION APPL IA IA

The job identified by:
  • Application name APPL
  • Input Arrival Time IA
  • Job name NAME
could not be submitted because an associated scheduling environment was not defined to WLM.

The job is set to error with code SEUN.

Check whether the scheduling environment is defined incorrectly in the JCL or in the CP operation record, or if the WLM definition is missing. Fix the error so that the job can be submitted.

EQQSU37E

SCHEDULING ENVIRONMENT SCHE CHECK FAILED FOR JOB: NAME IN APPLICATION APPL IA IA

The job identified by:
  • Application name APPL
  • Input Arrival Time IA
  • Job name NAME
could not be submitted because the check on the associated scheduling environment SCHE failed. The check is performed using the IWMSEQRY WLM macro.

The job is set to error with code OSUB.

For details, see message EQQZ215E in the log.

EQQSU38E

GETMAIN FAILED: TAILORING OF SCHEDULING ENVIRONMENT SCHE CHECK NOT POSSIBLE FOR JOB: NAME IN APPLICATION APPL IA IA

The job identified by:
  • Application name APPL
  • Input Arrival Time IA
  • Job name NAME
could not be submitted because the associated scheduling environment SCHE could not be tailored due to storage problems.

The job is set to error with code OSUB.

See if the tracker region can be increased.

EQQSU39E

TAILORING OF SCHEDULING ENVIRONMENT SCHE FAILED FOR JOB: NAME IN APPLICATION APPL IA IA

The job identified by:
  • Job name NAME
  • Application name APPL
  • Input Arrival Time IA
was not submitted because the associated scheduling environment SCHE could not be tailored.

The job is set to error with code OSUB.

See if the JCL has enough room to insert the SCHENV= statement.

EQQSU40W

JOB CARD NOT FOUND OR INVALID. SYSAFF TAILORING NOT POSSIBLE FOR TYPJOB NAME IN APPLICATION APPL IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Job name NAME
  • Application name APPL
  • Input Arrival Time IA
required SYSAFF tailoring, but no JOB card was found in the JCL.

The job or started task is submitted as it is.

Misplacement of the job card could also be due to a JCL coding error. If the problem is a JCL error, correct it.

EQQSU41W

GETMAIN FAILED. SYSAFF TAILORING NOT POSSIBLE FOR TYPJOB NAME IN APPLICATION APPL IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Job name NAME
  • Application name APPL
  • Input Arrival Time IA
could not be tailored by inserting the SYSAFF keyword.

The job or started task is submitted as it is.

Check the JCL to see if it is possible to split the job card into more lines so that tailoring for SYSAFF does not require additional storage allocation.

Increase the region of tracker address space, if possible.

EQQSU42W

PARM TAILORING FAILURE FOR: TYPJOB NAME IN APPLICATION APPL IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Job name NAME
  • Application name APPL
  • Input Arrival Time IA
could not be tailored by inserting the SYSAFF or CLASS keyword.
Tailoring is needed to insert the SYSAFF or CLASS keyword in the JCL. This was not possible for one of the following reasons:
  • The job card does not allow a new keyword to be added
  • The job card was not found
  • Not enough storage is available
  • There are JCL coding problems

The job or started task is submitted as it is.

Check if the JCL can be changed to add the SYSAFF or CLASS keyword.

EQQSU43W

JOB CARD NOT FOUND OR INVALID. CLASS TAILORING NOT POSSIBLE FOR TYPJOB NAME IN APPLICATION APPL IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Job name NAME
  • Application name APPL
  • Input Arrival Time IA
required CLASS tailoring, but no job card was found in the JCL.

The job or started task is submitted as it is.

Misplacement of the job card could also be due to a JCL coding error. If the problem is a JCL error, correct it.

EQQSU44W

GETMAIN FAILED. CLASS TAILORING NOT POSSIBLE FOR TYPJOB NAME IN APPLICATION APPL IA IA

The job or started task (the value of TYPJOB shows you whether it is a job or started task) identified by:
  • Job name NAME
  • Application name APPL
  • Input Arrival Time IA
could not be tailored by inserting the CLASS keyword.

The job or started task is submitted as it is.

Check the JCL to see if it is possible to split the job card into more lines so that tailoring for CLASS does not require additional storage allocation.

Increase the region of tracker address space, if possible.