EELE210I - EELZ412I

EELE210I

THE AGENT FOR z/OS® HAS UPDATED ITS GMT OFFSET ON SYSTEM SYSID.

Explanation

The system time was changed and the agent for z/OS generated an event to change its GMT offset.

System action

The agent for z/OS generates an event to modify its GMT offset and records the change in the message log.

User response

None.

EELF000E

DATA ROUTER TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE.

Explanation

A queue element did not contain the correct eye catcher or version number.

System action

The data router task does not process the invalid element, but continues normal processing.

System programmer response

Save the message log of the agent for z/OS and contact IBM® Software Support.

User response

Contact your system programmer.

EELF001I

DATA ROUTER TASK INITIALIZATION IS COMPLETE.

Explanation

The data router task has successfully completed initialization.

System action

Data router task processing starts.

User response

None.

EELF002E

DATA ROUTER TASK INITIALIZATION FAILED.

Explanation

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

System action

Data router task processing is terminated.

System programmer response

Correct all errors and restart the data router task.

User response

Contact your system programmer.

Problem determination

Review previous messages in the message log of the agent for z/OS.

EELF004E

DATA ROUTER TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT DQE.

Explanation

An abend prevented the data router task from processing a queue element.

System action

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

System programmer response

Save the message log and dump data sets and contact IBM Software Support.

User response

Contact your system programmer.

Problem determination

Review the agent for z/OS message log data set, the EELDUMP data set, and the SYSMDUMP data set to determine the cause of the problem.

EELF005E

DATA ROUTER TASK QUEUE POINTERS ARE DESTROYED, RTRQ IS LOST.

Explanation

The data router task abended while processing elements on RTRQ because the queue chaining is invalid.

System action

z/OS recovery?termination is requested to generate a dump. All elements on RTRQ are skipped, but the data router task attempts to continue normal processing.

Programmer response

Save the message log and dump data sets and contact IBM Software Support.

Problem determination

Review the agent for z/OS message log data set, the EELDUMP data set, and the SYSMDUMP data set to determine the cause of the problem.

EELF009I

ADAPTIVE PACING ON EVENT INFLOW MODE.

Explanation

The MODE can be ACTIVATED or DEACTIVATED.
ACTIVATED
The data router has detected that the maximum number of queue elements on the event manager queue (MGRQ) were already in use when the data router task attempted to add incoming events to the MGRQ. The data router task has posted each locally attached event reader task and event writer task (when EWSEQNO(n)), to stop reading from the event data sets or adding to the DRTQ.
DEACTIVATED
The data router task has detected that the event manager has processed all events on the event manager queue (MGRQ), so the data router task has posted each locally attached event reader task and event writer task (when EWSEQNO(n)), to start reading from the event data sets or adding to the DRTQ.

System action

Processing continues.

User response

None. This message is for information only.

EELF017E

THE HTTP CLIENT TASK QUEUE IS FULL. NO EVENTS WILL BE SENT TO SERVER.

Explanation

The HTTP client task queue is full.

System action

The agent for z/OS is no longer able to send events to IBM Workload Scheduler.

System programmer response

Try to find out why the HTTP client task is not processing.

EELF018E

DATA ROUTER TASK HAS IGNORED THE FOLLOWING DQE ELEMENT BECAUSE IT CONTAINS INVALID DATA: DQE.

Explanation

The queue element shown in the message contains invalid data.

System action

The data router task does not process the invalid element, but continues normal processing.

System programmer response

Save the agent for z/OS message log and contact IBM Customer Support.

EELH003E

SEND GENERIC ALERT TO NETVIEW FAILED WITH RC=RC

Explanation

Request type 12 sent to the NetView* PPI failed.

System action

A WTO is issued instead of the generic alert.

System programmer response

Check NetView® documentation for further information.

EELHM21E

APPLICATION NAME NOT VALID.

Explanation

The agent for z/OS received a submission request for a type of object that the agent is not designed to manage, such as a bind request for a cross dependency.

System action

The request is ignored.

System programmer response

Check the definition of the object (cross dependency, workstation, and so on) in question in IBM Workload Scheduler.

EELHM22E

MISSING PARAMETER.

Explanation

The agent for z/OS received an incomplete request from the HTTP server; for example, the name of the JCL that it is to submit is not specified.

System action

The request is ignored.

System programmer response

Check the definition of the object in question in IBM Workload Scheduler.

EELHM23E

INCORRECT PARAMETER.

Explanation

The agent for z/OS received a request that includes an incorrect parameter from the HTTP server.

System action

The request is ignored.

System programmer response

Check the definition of the object in question in IBM Workload Scheduler.

EELHM24E

GENERIC ERROR.

Explanation

The agent for z/OS received an incorrect request from the HTTP server.

System action

The request is ignored.

System programmer response

Check the definition of the object(s) in question in IBM Workload Scheduler.

EELHM25E

JOB LOG NOT AVAILABLE.

Explanation

The requested job log is not available. It was either not created or it was purged by JES.

System action

The job log is not shown.

System programmer response

No action.

EELHM27E

INCORRECT JCL MEMBER NAME OR DATA SET NAME.

Explanation

The agent for z/OS received from the HTTP server a request for a JCL that does not exist.

System action

The JCL is not shown.

System programmer response

Check that the definition of the object is correct in IBM Z Workload Scheduler.

EELHM28E

JCL TOO LONG.

Explanation

The agent for z/OS received from the HTTP server a request for a JCL that is too long to retrieve.

System action

The JCL is not shown.

System programmer response

Check that the definition of the object is correct in IBM Z Workload Scheduler.

EELHT01I

THE HTTP CLIENT COMMUNICATION TASK HAS STARTED.

Explanation

The HTTP client communication task has successfully completed initialization.

System action

The HTTP client communication task processing continues.

User response

None.

EELHT02I

THE HTTP CLIENT COMMUNICATION TASK HAS STARTED.

Explanation

The HTTP client communication task has ended either because the IBM Workload Scheduler master or domain manager is in the process of shutting down or as a result of an operator modify command to terminate this task or a related task.

System action

Processing continues.

User response

None.

EELHT03E

THE HTTP CLIENT COMMUNICATION TASK FAILED TO INITIALIZE THE C PROCESS.

Explanation

An error occurred while attaching a task to run the C code as a z/OS executable program: an invocation to the BPX1ATM callable service failed.

System action

The HTTP client task initialization fails.

User response

Try to restart the HTTP client task with the modify command. If the problem persists, contact IBM Software Support.

EELHT04E

THE HTTP CLIENT COMMUNICATION TASK HAS ENDED BECAUSE NO HTTP OR HTTPS DESTINATIONS ARE DEFINED.

Explanation

No HTTP or HTTPS destinations were defined for the agent for z/OS.

System action

The HTTP client task initialization fails.

User response

None.

EELHT05E

THE HTTP CLIENT COMMUNICATION TASK HAS IGNORED THE FOLLOWING QUEUE ELEMENT: DQE.

Explanation

The HTTP Client task received an invalid queue element. A queue element did not contain the correct eye catcher or version number.

System action

The HTTP client task does not process the invalid element, but continues normal processing.

System programmer response

Save the message log of the agent for z/OS and contact IBM Software Support.

User response

Contact your system programmer.

EELHT06E

A SEVERE ERROR IN THE HTTP CLIENT COMMUNICATION TASK HAS CAUSED ONE OR MORE REQUESTS TO BE LOST.

Explanation

The HTTP client task abended while processing elements on HTTQ because the queue chaining is invalid.

System action

z/OS recovery/termination is requested to generate a dump. All elements on HTTQ are lost and the HTTP Client task terminates.

Programmer response

Save the message log and dump data set, and contact IBM Software Support.

Problem determination

Review the agent for z/OS message log data set and the SYSMDUMP data set, to determine the cause of the problem.

EELHT07E

THE HTTP CLIENT COMMUNICATION TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: DQE.

Explanation

An abend prevented the HTTP client task from processing a queue element.

System action

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

User response

Contact your system programmer.

Programmer response

Save the message log and dump data set, and contact IBM Software Support.

Problem determination

Review the agent for z/OS message log data set and the SYSMDUMP data set, to determine the cause of the problem.

EELHT11I

THE HTTP SERVER COMMUNICATION TASK HAS STARTED AND IS WAITING FOR THE HTTP CLIENT COMMUNICATION TASK INITIALIZATION.

Explanation

The HTTP server communication task has successfully completed initialization and is waiting for the HTTP client.

System action

The HTTP server communication task processing continues.

User response

None.

EELHT12I

THE HTTP SERVER COMMUNICATION TASK HAS STARTED.

Explanation

The HTTP server communication task has ended either because the IBM Workload Scheduler master or domain manager is in the process of shutting down or as a result of an operator modify command to terminate this task or a related task.

System action

Processing continues.

User response

None.

EELHT13E

THE HTTP SERVER COMMUNICATION TASK FAILED TO INITIALIZE THE C PROCESS.

Explanation

An error occurred while attaching a task to run the C code as a z/OS executable program: an invocation to the BPX1ATM callable service failed.

System action

The HTTP server task initialization fails.

User response

Try to restart the HTTP server task with the modify command. If the problem persists, contact IBM Software Support.

EELHT14E

THE HTTP SERVER COMMUNICATION TASK HAS ENDED BECAUSE NO HTTP OR HTTPS DESTINATIONS ARE DEFINED.

Explanation

No HTTP or HTTPS destinations were defined for the agent for z/OS.

System action

The HTTP server task initialization fails.

User response

None.

EELHT15E

THE HTTP CLIENT FAILED TO PROCESS A REQUEST FOR DESTNAME.

Explanation

An error occurred while communicating through HTTP with Dynamic Workload Console. The problem can be that the destination Dynamic Workload Console instance is unavailable. This message is followed by message EELHT43I, which indicates the details of the error.

System action

The request fails. If the error is related to the TCP/IP connection, the destination is set to OFFLINE.

User response

Check the state of the Dynamic Workload Console instance.

If the problem is due to Dynamic Workload Console being unavailable, resolve by running:
  • startAppServer if WebSphere Application Server Liberty Base is running
on the master or domain manager.

EELHT16W

THE HTTP CLIENT FAILED TO SET THE TCP/IP JOB NAME TO TCPNAME. THE DEFAULT TCPIP HAS BEEN USED.

Explanation

An error occurred while trying to communicate with a TCP/IP stack with TCPIPJOBNAME TCPNAME.

System action

The HTTP client task uses the default name TCPIP.

User response

Verify your TCP/IP stack configuration and make sure that the TCPIPJOBNAME parameter in the HTTPOPTS statement is correct.

EELHT17W

THE HTTP SERVER FAILED TO SET THE TCP/IP JOB NAME TO TCPNAME. THE DEFAULT TCPIP HAS BEEN USED.

Explanation

An error occurred while trying to communicate with a TCP/IP stack with TCPIPJOBNAME TCPNAME.

System action

The HTTP server task uses the default name TCPIP.

User response

Verify your TCP/IP stack configuration and make sure that the TCPIPJOBNAME parameter in the HTTPOPTS statement is correct.

EELHT18I

THE HTTP SERVER IS LISTENING FOR HTTPS REQUESTS ON LOCAL HOST NAME HOSTNAME WITH PORT NUMBER SSL_PORT.

Explanation

See message text.

System action

None.

User response

None.

EELHT19I

THE HTTP SERVER IS LISTENING FOR HTTP REQUESTS ON LOCAL HOST NAME HOSTNAME WITH PORT NUMBER PORT.

Explanation

See message text.

System action

None.

User response

None.

EELHT20E

THE HTTP SERVER WAS UNABLE TO OPEN THE EVENT DATA SET WITH DDNAME EELHTDS.

Explanation

The HTTP server could not open its output event data set, ddname EELHTDS.

System action

The HTTP server issues message EELHT11E and is terminated.

User response

If necessary, restart the HTTP server.

Problem determination

Ensure that the ddname EELHTDS is correctly specified and that the agent for z/OS started task is authorized to open the data set for update.

EELHT21E

THE HTTP SERVER OUTPUT DATA SET IS TOO SMALL.

Explanation

The HTTP server requires that the event data set is large enough to contain a minimum of 100 events. The data set defined by the ddname EELHTDS does not fulfill this requirement.

System action

The HTTP server processing is terminated. Message EELHT40E is issued.

System programmer response

Allocate a larger event data set. If necessary, restart the agent for z/OS to pick up the new event data set.

EELHT22I

THE HTTP SERVER CANNOT REPOSITION AT RESTART POSITION: CYC REC.

Explanation

The HTTP server cannot position on the event data set with the event data set position that it has received. The restart position was probably overwritten when the event data set wrapped around.

System action

The HTTP server continues normal processing.

Programmer response

The event data set might be too small. Reallocate the data set with a larger size.

EELHT25E

THE HTTP SERVER FAILED TO BIND ON PORT PORT. ERROR: ERRNO.

Explanation

An error was encountered when the HTTP server attempted a bind request. ERRNO shows the TCP/IP error number. The most common decimal values for ERRNO are:
121
The socket is already bound to an address or the socket was shut down.
139
The user is not authorized to bind to the port specified.

System action

The system tries to bind on port PORT every minute, until it is successful. If you specified a port for the SSL communication and a port for non-SSL communication, the HTTP server tries to bind also to the other port and, if successful, remains active and listens on that port while it continues to try to bind port PORT.

User response

Correct the problem, basing on the ERRNO description. If you change the initialization statement parameters, restart the subsystem, otherwise wait for the next attempt to establish the connection.

EELHT26E

THE HTTP SERVER IS NOT LISTENING ON SSL PORT PORT BECAUSE IT FAILED TO INITIALIZE THE SSL CONTEXT. ERROR: SSL_ERR.

Explanation

An error was encountered when the HTTP server attempted to initialize the SSL context. SSL_ERR shows the numeric error returned by the SSL API or a text explaining the error.

System action

The HTTP server cannot receive SSL requests. The system tries to bind on port PORT every minute, until it is successful. If you specified a port for the SSL communication and a port for non-SSL communication, the HTTP server tries to bind also to the other port and, if successful, remains active and listens on that port while it continues to try to bind to port PORT.

User response

Correct the problem, basing on the SSL_ERR description. If you change the initialization statement parameters, restart the subsystem, otherwise wait for the next attempt to establish the connection.

EELHT27E

THE HTTP SERVER FAILED TO ACCEPT A NEW CONNECTION. ERROR: ERRNO.

Explanation

An error was encountered when the HTTP server attempted to accept a new connection request. ERRNO shows the TCP/IP error.

System action

The HTTP server closes the connection and retries to listen on the specified ports.

User response

Correct the problem, basing on the ERRNO.

EELHT29E

THE HTTP SERVER FAILED TO INITIALIZE THE SSL CONTEXT FOR A NEW CONNECTION. ERROR: SSL_ERR.

Explanation

An error was encountered when the HTTP server attempted to initialize the SSL context for a new connection request. SSL_ERR shows the numeric error returned by the SSL API or a text explaining the error.

System action

The new connection request is rejected. The HTTP server continues its processing.

User response

Correct the problem, basing on the SSL_ERR description.

EELHT30E

THE HTTP SERVER FAILED TO RECEIVE DATA ON A SOCKET. ERROR: ERRNO.

Explanation

An error was encountered when the HTTP server attempted to receive data on a socket. ERRNO shows the numeric error returned by the SSL API or a text explaining the error.

System action

The connection is closed and the HTTP server continues its processing.

User response

Correct the problem, basing on the ERRNO description.

EELHT31E

THE HTTP SERVER FAILED TO MANAGE A STATUS CHANGE REQUEST.

Explanation

The HTTP server failed to manage a status change notification.

System action

A bad HTTP response is sent to the agent and the connection is closed. The HTTP server continues its processing.

User response

None.

EELHT32E

THE HTTP SERVER FAILED TO SEND DATA ON A SOCKET. ERROR: ERRNO.

Explanation

The HTTP server failed to send the HTTP response for a status change notification.

System action

The HTTP server continues its processing. This could cause the event manager to discard some events.

User response

None.

EELHT34E

ERROR RESERVING A BLOCK OF STORAGE OF N BYTES. MODULE: MODULE - LINE: LINE.

Explanation

The HTTP client or server received an error while reserving a block of storage of n bytes length.

System action

The action requesting the storage fails.

User response

Collect the appropriate documentation and contact the Customer Support. A minimum set of documentation is a console dump of the agent for z/OS, the message log, and, if present, the trace log. A possible recovery action is to restart the agent for z/OS.

EELHT39E

ERROR CONVERTING CHARACTERS. MODULE MODULE - LINE: LINE. ERR_STRING

Explanation

The HTTP client received an error while converting a series of characters from an encoded character set. ERR_STR shows the reason of the failure.

System action

The request for the conversion fails.

User response

Contact IBM Customer Support.

EELHT40E

EVENT DATASET ERROR: HTTP SERVER COMMUNICATION TASK HAS ENDED.

Explanation

The HTTP server subtask closes because an error occurred while reading an event from EELHTDS.

System action

The HTTP server task initialization fails.

User response

None.

EELHT41I

THE HTTP SERVER STARTED THE SYNCHRONIZATION WITH THE SUBMIT TASK.

Explanation

The HTTP server started the synchronization with the submit task.

System action

Processing continues.

User response

None.

EELHT42I

THE HTTP SERVER FINISHED THE SYNCHRONIZATION WITH THE SUBMIT TASK. NUM SUBMISSION EVENTS HAVE BEEN REPROCESSED.

Explanation

The HTTP server completed the synchronization with the submit task. During the operation the reported number of events were reprocessed.

System action

Processing continues.

User response

None.

EELHT43I

MSG_TEXT

Explanation

This message contains additional details for a related EELHT15E or EELHT44E message.

System action

Processing continues.

User response

Integrate this information with the related EELHT15E or EELHT44E message information.

EELHT46E

THE HTTP SERVER RECEIVED A JOB NOTIFICATION MESSAGE WITH NO VALUE SPECIFIED FOR THE PARM PARAMETER

Explanation

The HTTP server received an incorrect notification. The error concerns the internal parameter PARM, which is missing.

System action

The status of the notified job is not updated.

User response

Check if the HTTP server is incorrectly contacted by an extraneous client. If this is not the case, this is an internal error. Contact IBM Software Support for assistance.

EELHT50I

THE EELEVDS EVENT DATASET DOES NOT INDICATE SUBMISSIONS IN PROGRESS. SUBMISSION EVENTS MUST NOT BE RECOVERED.

Explanation

See message text.

System action

None.

User response

None.

EELHT51I

THE AGENT IS CONNECTED TO: SERVER HOSTNAME: hostname/IPSERVER PORT NUMBER: port number

Explanation

After a previous failed connection attempt, the agent for z/OS linked successfully to port port number of the hostname/IP Dynamic Workload Console.

System action

None.

User response

None.

EELHT60I

THE HTTP SERVER HAS COMPLETED THE REFRESH OF THE HTTP DESTINATION LIST.

Explanation

See message text.

System action

None.

User response

None.

EELHT64W

A REQUEST WITH AN UNSUPPORTED JOB STREAM NAME WAS RECEIVED. THE REQUEST WAS DISCARDED.

Explanation

See message text.

System action

The request was discarded.

User response

Review the name of the job stream and modify it in accordance with the documented nomenclature rules.

EELIT00I

THE AGENT IS OPEN FOR E-BUSINESS.AGENT HOSTNAME IS: LHOSTNAGENT PORT NUMBER: LPORT SERVER HOSTNAME IS: RHOSTN SERVER PORT NUMBER: RPORT

Explanation

The agent did connect with the Dynamic Workload Console component of IBM Workload Scheduler using the shown host names and ports.

System action

The agent can now receive and send events from/to IBM Workload Scheduler.

EELIT01E

THE TDWBHOSTNAME PARAMETER FOR THE Dynamic Workload Console HOSTNAME IS MISSING. THE PARAMETER IS MANDATORY.

Explanation

The agent cannot start because the hostname of the Dynamic Workload Console was not provided.

System action

The agent cannot be initialized.

User response

Provide the TDWBHOSTNAME initialization parameter and restart the agent.

EELIT02E

SSLKEYRING SSL key ring parameter is missing. The SSL key ring parameter is mandatory when SSL is activated.

Explanation

The agent cannot start because the SSL key ring parameter was not provided and SSL is activated (SSL parameter set to YES).

System action

The agent cannot be initialized.

System programmer response

Correct the agent initialization statements to avoid the error messages at the next restart.

User response

Provide the SSLKEYRING initialization parameter or set SSL to NO and restart the agent.

EELIT03E

SSLKEYRINGPSW SSL key ring psw parameter is missing. The SSL key ring psw parameter is mandatory when SSL is activated and the key ring file is a key database USS file.

Explanation

The agent cannot start because the SSL key ring psw parameter was not provided, SSL is activated (SSL parameter set to YES), and the key ring file is a key database USS file.

System action

The agent cannot be initialized.

System programmer response

Correct the agent initialization statements to avoid the error messages at the next restart.

User response

Provide the SSLKEYRINGPSW initialization parameter or set SSL to NO and restart the agent.

EELMH13E

THE MONITORING TASK WAS UNABLE TO OPEN DATASET WITH DDNAME DDNAME

Explanation

The monitoring task is unable to open the data set referenced by the DDNAME.

System action

The monitoring task terminates.

User response

Check that the data set referenced by the DDNAME is correctly defined and recycle the controller.

EELSU01I

THE SUBMIT TASK HAS STARTED

Explanation

The submit task has successfully completed initialization.

System action

The submit task processing starts.

User response

None.

EELSU02I

THE SUBMIT TASK HAS ENDED

Explanation

The submit task has terminated processing normally. An operator has stopped the submit task or the agent for z/OS has stopped.

System action

The submit task processing is terminated.

User response

None.

EELSU03E

THE SUBMIT TASK HAS ENDED DUE TO PROCESSING ERRORS

Explanation

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

System action

The submit task processing is terminated.

System programmer response

Correct the errors and restart the submit task.

Problem determination

Review previous messages in the agent for z/OS message log.

EELSU04E

THE SUBMIT TASK INITIALIZATION FAILED, THE TASK IS TERMINATED

Explanation

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

System action

The submit task processing is terminated.

System programmer response

Correct the errors and restart the submit task.

Problem determination

Review previous messages in the agent for z/OS message log.

EELSU05E

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

Explanation

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

System action

If the error occurs while the submit task is being initialized, processing of the submit task is terminated and message EELSU04 is issued.

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

System programmer response

Correct the errors and restart either the submit task or the agent for z/OS.

Problem determination

Check that DDNAME EELBRDS is correctly specified in the startup procedure.

EELSU06E

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

Explanation

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

System action

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.

System programmer response

Save the message log and dump data sets, and contact IBM Software Support.

Problem determination

Review the agent for z/OS message log and dump data sets to determine the cause of the problem.

EELSU07E

THE SUBMIT TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: REQUEST

Explanation

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

System action

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

System programmer response

Save the message log and dump data sets, and contact IBM Software Support.

Problem determination

Review the agent for z/OS message log and dump data sets to determine the cause of the problem.

EELSU09W

JOB JOBNAME(JOBNUM) COULD NOT BE RELEASED. REPEATED RETRIES HAVE FAILED. JOB NAME IS: JOBALIAS

Explanation

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.

System action

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

Operator response

Determine the current status of the job. If necessary, release the job manually.

Problem determination

Review the system log and look for previous JES messages that indicate unusual conditions.

EELSU10E

JOB JOBNAME COULD NOT BE SUBMITTED BECAUSE THE SUBMIT EXIT RETURNED A SUBMITTING USER ID, USER, WHOSE AUTHORITY COULD NOT BE DETERMINED. JOB NAME IS: JOBALIAS

Explanation

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

System action

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

User response

If necessary, submit the job manually.

Problem determination

Check that the job submit exit, EELUX001, returns only valid TSO user IDs.

EELSU11W

DDNAME EELEVDS IS MISSING OR SPECIFIES DD DUMMY

Explanation

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 might be lost or duplicated.

System action

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

System programmer response

Allocate a unique event data set to the EELEVDS DD statement. If this agent for z/OS address space does not start an event writer subtask, allocate the event data set with two tracks of space.

Problem determination

Verify the JCL procedure for this agent for z/OS address space.

EELSU13E

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

Explanation

The submit task was unable to open the started task temporary proclib data set. This file is defined by the EELSTC DD statement in the JCL procedure used to start the agent for z/OS.

System action

If the error is discovered during the start of the agent for z/OS, the submit task issues message EELSU04 and is terminated. If the error is discovered during submit of a started task, this message is followed by message EELW759W and the submit task stops submitting started tasks.

System programmer response

Make sure that the agent for z/OS is properly authorized to use the temporary proclib data set, that the EELSTC DD statement is correctly defined, and restart either the submit task or the agent for z/OS.

Problem determination

Check that the EELSTC DD statement is correctly specified in the startup procedure. Verify that the agent for z/OS 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.

EELSU14W

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

Explanation

The submit task received a STOP command and the job could not be released from hold.

System action

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

System programmer response

Determine the current status of the job. If required, release the job manually when the agent for z/OS is restarted.

Problem determination

This message is only for information purposes.

EELSU20E

UNABLE TO READ EELEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE.

Explanation

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.

System action

The submit task continues normal processing.

System programmer response

If necessary, stop the agent for z/OS, take corrective action, and then restart it.

Problem determination

Review earlier messages in the message log to determine the cause of the error.

EELSU21E

UNABLE TO UPDATE EELEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE.

Explanation

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.

System action

The submit task continues normal processing.

System programmer response

If necessary, stop the agent for z/OS, take corrective action, and then restart it.

Problem determination

Review earlier messages in the message log to determine the cause of the error.

EELSU22E

UNABLE TO ACCESS THE EELEVDS FILE FOR REQUEST TYPE DQETYPE.

Explanation

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

System action

The submit task continues normal processing.

System programmer response

If necessary, stop the agent for z/OS, take corrective action, and then restart it.

Problem determination

Review earlier messages in the message log to determine the cause of the error.

EELSU23E

NO FREE SPACE IN EELEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE.

Explanation

The submit task was unable to execute a submit checkpoint request because an error was found in the dataset header record.

System action

The submit task continues normal processing.

System programmer response

Take the following steps:
  1. Stop the agent for z/OS
  2. Save a copy of the dataset and contact IBM Support
  3. Scrap and reallocate the dataset
  4. Restart the agent for z/OS

EELSU24W

WORKSTATION IS NOT PRESENT IN THE EELEVDS HEADER RECORD

Explanation

The submit task could not remove the name of the agent for z/OS from the header record in the event data set because the name is not present.

System action

The submit task continues normal processing.

System programmer response

None.

EELSU25E

SUBMISSION CANNOT BE EXECUTED BECAUSE THE SUBMISSION SEQUENCE NUMBER SSEQ IS NOT A SUCCESSOR OF THE EVTSSEQ SEQUENCE NUMBER. THE JOB NAME IS JOBALIAS.

Explanation

The submission of job JOBALIAS failed due an OUT OF SEQUENCE event.

System action

The submit task stops.

System programmer response

Stop and start the agent again.

If the problem persists, copy the contents of the message log and of the events dataset before you stop the agent, and call IBM Support.

EELSU30W

JOB CARD NOT FOUND OR INVALID. SPIN PREVENTION NOT POSSIBLE FOR: TYPJOB NAME. JOB NAME IS: JOBALIAS

Explanation

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

System action

The job or started task is submitted as it is.

User response

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 that SPIN prevention is applied only if the JCC function is active. If you are using JCC, 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.

EELSU31I

TYPJOB NAME HAD JESLOG KEYWORD SET TO JKEY. IT HAS BEEN REPLACED BY JESLOG=NOSPIN. JOB NAME IS: JOBALIAS

Explanation

The job identified by:
  • Input Arrival Time IA
  • Job name NAME
has the JESLOG set to JKEY and not to NOSPIN.

System action

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

User response

None.

EELSU32W

GETMAIN FAILED. SPIN PREVENTION NOT POSSIBLE FOR TYPJOB NAME. JOB NAME IS: JOBALIAS

Explanation

The job identified by:
  • 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.

System action

The job is submitted as it is.

User response

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 the agent for z/OS address space, if possible.

EELSU33W

TAILORING FAILURE. SPIN PREVENTION NOT POSSIBLE FOR: TYPJOB NAME. JOB NAME IS: JOBALIAS

Explanation

The job identified by:
  • Input Arrival Time IA
  • Job name NAME
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

System action

The job is submitted as it is.

User response

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

EELSU34E

JOB CARD NOT FOUND OR INVALID. SCHEDULING ENVIRONMENT TAILORING NOT POSSIBLE FOR: TYPJOB NAME. JOB NAME IS: JOBALIAS

Explanation

The job identified by:
  • 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.

System action

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

User response

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.

EELSU35W

SCHEDULING ENVIRONMENT SCHE NOT AVAILABLE FOR JOB: NAME IN JPLEX. JOB NAME IS: JOBALIAS

Explanation

The job identified by:
  • 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.

System action

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

User response

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

EELSU36W

SCHEDULING ENVIRONMENT SCHE NOT DEFINED FOR JOB: NAME. JOB NAME IS: JOBALIAS

Explanation

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

System action

The job is set to error with code SEUN.

User response

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.

EELSU37E

SCHEDULING ENVIRONMENT SCHE CHECK FAILED FOR JOB: NAME. JOB NAME IS: JOBALIAS

Explanation

The job identified by:
  • 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.

System action

The job is set to error with code OSUB.

User response

For details, see message EELZ215E in the log.

EELSU38E

GETMAIN FAILED: TAILORING OF SCHEDULING ENVIRONMENT SCHE CHECK NOT POSSIBLE FOR JOB: NAME. JOB NAME IS: JOBALIAS

Explanation

The job identified by:
  • 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.

System action

The job is set to error with code OSUB.

User response

See if the size of the agent for z/OS region can be increased.

EELSU39E

TAILORING OF SCHEDULING ENVIRONMENT SCHE FAILED FOR JOB: NAME. JOB NAME IS: JOBALIAS

Explanation

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

System action

The job is set to error with code OSUB.

User response

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

EELW011I

THE EVENT WRITER ENDED NORMALLY

Explanation

The initialization of the event writer has completed and the event writer has been requested to stop execution.

System action

Processing continues.

User response

None.

EELW012E

THE EVENT WRITER TERMINATED BECAUSE OF UNRECOVERABLE ERRORS

Explanation

The initialization of the event writer has completed, but a severe error caused the event writer to stop execution.

System action

The event writer terminates execution. Message EELZ045W is issued.

System programmer response

Correct all errors and restart the event writer.

Problem determination

Review earlier messages in the message log of the agent for z/OS to determine the exact reason for this message.

EELW016E

AN UNRECOVERABLE I/O ERROR OCCURRED. SYNAD MESSAGE FOLLOWS: SYNMSG

Explanation

An I/O error occurred when the event writer was updating the event data set.

System action

The event writer attempts to continue processing.

System programmer response

Correct all errors and, if necessary, restart the event writer.

Problem determination

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

EELW017E

THE EVENT WRITER WAS UNABLE TO OPEN THE EVENT DATA SET

Explanation

The event writer could not open its output data set, ddname EELEVDS.

System action

The event writer issues message EELW062E and is terminated.

System programmer response

If necessary, restart the event writer.

Problem determination

Check that ddname EELEVDS is correctly specified and that the agent for z/OS started task is authorized to open the data set for update.

EELW021E

THE EVENT WRITER OUTPUT DATA SET IS TOO SMALL

Explanation

The event writer requires that the event data set is large enough to contain a minimum of 100 events. The data set defined by the ddname EELEVDS does not fulfill this requirement.

System action

The event writer processing is terminated. Message EELW062E is issued.

System programmer response

Allocate a larger event data set. If necessary, restart the agent for z/OS to pick up the new event data set.

EELW024E

THE EVENT WRITER ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC

Explanation

An abend prevented the event writer from writing an event record to the event data set.

System action

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

Operator response

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

Problem determination

Review the SYSLOG data set, the message log of the agent for z/OS, and the dump data set to determine the cause of the error.

EELW025W

THE EVENT WRITER HAS IGNORED THE FOLLOWING INVALID EXIT RECORD: EXITREC

Explanation

An invalid event record EXITREC has been found by the event writer. The most likely reason is that the last four bytes of the record do not contain the EEL3 character string. It is also possible that the first three characters of the job ID field do not contain the character string JOB.

If the last four bytes of the record contain the character string ERA2, an abend has occurred during the event creation, and the event contains the following information:
EXRJOBN
Name of the abending CSECT
EXRJOBID
Compile date of the abending CSECT
EXRCREAT
Compile time of the abending CSECT
EXRRDATE+1
Abend code (from SDWACMPC)
EXRRTIME
Offset in CSECT at which the abend occurred
If the last four bytes of the record contain the character string ERU2, the event creation has been called by an unsupported exit, and the event contains the following information:
EXRJOBN
Name of the unsupported exit.

System action

The event writer terminates processing of the event, but continues normal processing. If the invalid event was of the ERA2 or ERU2 type (see previous explanations), the events are created only if a minimum of five minutes have passed since the last creation of the same type.

System programmer response

Save the agent for z/OS message log data set (EELMLOG) containing this error message and contact IBM Software Support.

Problem determination

If the message is issued for all events (in which case the event data set is empty), check that the EELSSCMJ module and the event writer are at the same release level.

EELW030I

A DISK DATA SET WILL BE FORMATTED, DDNAME = DDNAME

Explanation

The agent for z/OS has started to format an event data set or a submit?release data set for the ddname DDNAME.

System action

The agent for z/OS continues processing.

User response

None.

EELW038I

A DISK DATA SET HAS BEEN FORMATTED, DDNAME = DDNAME

Explanation

The agent for z/OS has finished formatting an event data set or a submit?release data set for the ddname DDNAME.

System action

The agent for z/OS continues processing.

User response

None.

EELW044E

UNEXPECTED ERROR SUBMITTING JOB JOBNAME TO THE JES INTERNAL READER

Explanation

An error occurred when submitting the job JOBNAME to JES.

System action

Processing continues.

Operator response

If necessary, submit the job manually.

EELW046E

SEQUENCE NUMBER SEQNO IS ALREADY IN USE BY AN EVENT READER SUBTASK

Explanation

At initialization of the event writer, an event reader was already started with the sequence number specified in the EWSEQNO keyword of EWTROPTS.

The number specified in the EWSEQNO keyword of EWTROPTS must be unique within the IBM Z Workload Scheduler subsystem.

System action

The initialization of the event writer fails. The event writer task is terminated.

Programmer response

Review the ERSEQNO keyword of the ERDROPTS initialization statements to get a sequence number that is unused. Update the EWSEQNO keyword with a unique sequence number and use the IBM Z Workload Scheduler Modify command to restart the event writer task.

EELW048E

THE EVENT FILTERING EXIT, EELUX004, ABENDED AND HAS BEEN DISABLED

Explanation

An abend in the event filtering exit prevented the event writer from writing an event record to the event data set.

System action

z/OS recovery?termination is requested to generate a dump. The event writer attempts to continue normal operation with the next queued event, but the event filtering exit is not called again.

Operator response

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

System programmer response

Correct all errors and restart the event writer.

Problem determination

Review the SYSLOG data set, the agent for z/OS message log, and the dump data set to determine the cause of the error.

EELW049E

UNABLE TO FORMAT DATA SET WITH DDNAME DDNAME BECAUSE THE DATA SET IS NOT A SINGLE EXTENT, DISK RESIDENT, DATA SET

Explanation

The agent for z/OS was unable to format an event data set or a submit?release data set for the ddname DDNAME. A data set to be formatted must be a disk resident, single extent data set.

System action

The agent for z/OS fails to initialize correctly.

Operator response

None.

System programmer response

Correct the agent for z/OS started task procedure and restart it.

EELW052E

THE EVENT DATASET, DDNAME DDNAME, LRECL BLKSZ IS INVALIDLY DEFINED. DATASET IS NOT USABLE

Explanation

The event data set referenced by ddname DDNAME has been allocated with an invalid logical record length.

System action

The initialization of the event writer fails.

System programmer response

Stop the agent for z/OS, reallocate the data set, and restart the agent for z/OS.

Problem determination

An event data set must have a logical record length (LRECL) not less than 100 and not greater than 32000. Check that the LRECL is within the supported range.

EELW061W

THE EVENT FILTERING EXIT LOAD MODULE, MODULE, COULD NOT BE LOADED

Explanation

The event writer could not locate the event filtering exit load module, EELUX004.

System action

The event filtering exit is not used by the event writer.

System programmer response

If the event filtering exit is meant to be used, make sure that the EELUX004 load module is present in a library that can be reached by the agent for z/OS. Correct all errors and, if necessary, restart the event writer.

Problem determination

None.

EELW062E

EVENT WRITER INITIALIZATION FAILED

Explanation

The event writer could not acquire all resources required for normal operation. The most likely reason is that the event data set or a submit?release data set could not be opened.

System action

The event writer processing is terminated. Message EELZ045W is issued.

System programmer response

Correct all errors and restart the event writer.

Problem determination

Review earlier messages in the message log of the agent for z/OS to determine the exact reason for this message.

EELW065I

EVENT WRITER STARTED

Explanation

The initialization of the event writer has completed and the event writer is now about to start processing.

System action

The agent for z/OS continues processing.

User response

None.

EELW067E

A SEVERE ERROR IN THE EVENT WRITER HAS CAUSED LOSS OF CSA EVENT BUFFERS

Explanation

An abend in the queue processing routine of the event writer prevented the event writer from returning all event buffers to the free chain.

System action

z/OS recovery?termination is requested to generate a dump. The event writer attempts to continue processing.

System programmer response

None.

Problem determination

Review the SYSLOG data set, the agent for z/OS message log data set, and the dump data set to determine the cause of the error.

EELW070I

THE EW CANNOT REPOSITION AT RESTART POSITION: CYCREC

Explanation

An event writer is started in event reader mode (with an EWSEQNO). The event writer cannot position on the event data set with the event data set position that it has received. The restart position was probably overwritten when the event data set wrapped around.

System action

The event writer continues normal processing.

Programmer response

The event data set might be too small. Make sure that it is large enough to hold all the generated events when the connection between the controller and the tracker with the started event writer is down.

EELW071I

UNKNOWN RECORD TYPE SKIPPED BECAUSE IT IS TOO OLD

Explanation

The event writer encountered an unknown record type when skipping records of the submit?release data set that are too old.

System action

The record is skipped.

User response

None.

EELW075W

THE HEADER RECORD IN FILE DDNAME IS INCOMPATIBLE WITH THE DEVICE TYPE

Explanation

The information in the header record does not match the calculated records per tracks value. Normally this is caused by moving the data set to a different device type.

Note: This message might be issued if you have reallocated the data set using a method that does not put an end of file at the beginning of the data set. It can then be ignored.

System action

The data set is reformatted.

User response

None.

EELW076W

NO SERVER PULSE. EVENT WRITER WILL STOP PULSE DETECTION

Explanation

The agent for z/OS uses a handshake method when communicating with Dynamic Workload Console. When handshake processing is in use, the agent for z/OS sends an identification (ID) event to the Dynamic Workload Console at a specified interval and the broker responds to the agent. This message is issued if the agent detects that the broker has not responded to two consecutive ID events.

System action

The event writer task stops sending handshake events.

System programmer response

Check that the Dynamic Workload Console is running. Restart it if necessary.

EELW520E

JOB COULD NOT BE SUBMITTED BECAUSE THE JOB CARD IS NOT TERMINATED CORRECTLY. THE JOB NAME IS: JOBALIAS

Explanation

The agent for z/OS has been requested to submit a job that has an incorrect job card.

System action

The job is not submitted.

User response

Correct the JCL for this job and use either the IBM Workload Scheduler conman command line or the Dynamic Workload Console to submit the job again.

EELW521E

JOB COULD NOT BE SUBMITTED BECAUSE THE JOB CARD ACCOUNT PARAMETER IS NOT TERMINATED CORRECTLY. THE JOB NAME IS: JOBALIAS

Explanation

The agent for z/OS has been requested to submit a job that has an incorrect job card.

System action

The job is not submitted.

User response

Correct the JCL for this job and use either the IBM Workload Scheduler conman command line or the Dynamic Workload Console to submit the job again.

EELW522E

JOB COULD NOT BE SUBMITTED BECAUSE THE JOB CARD PROGRAMMER NAME IS TOO LONG (MAX 19 CHARS). THE JOB NAME IS: JOBALIAS

Explanation

The agent for z/OS has been requested to submit a job that has an incorrect job card.

System action

The job is not submitted.

User response

Correct the JCL for this job and use either the IBM Workload Scheduler conman command line or the Dynamic Workload Console to submit the job again.

EELW523E

JOB COULD NOT BE SUBMITTED BECAUSE THE JOB CARD PROGRAMMER NAME IS NOT TERMINATED CORRECTLY. THE JOB NAME IS: JOBALIAS

Explanation

The agent for z/OS has been requested to submit a job that has an incorrect job card.

System action

The job is not submitted.

User response

Correct the JCL for this job and use either the IBM Workload Scheduler conman command line or the Dynamic Workload Console to submit the job again.

EELW524E

JOB NAME COULD NOT BE SUBMITTED BECAUSE THE JOB CARD JOB NAME PARAMETER CONTAINS INVALID CHARACTERS. THE JOB NAME IS: JOBALIAS

Explanation

The agent for z/OS has been requested to submit a job that has an incorrect job name. Job names must use the following syntax rules:
  • Start from column 3.
  • Have length from 1 to 8 alphanumeric (capital A to Z, numbers 0 to 9) or national ($, #, @) characters.
    Note: The system recognizes the following hexadecimal representations of the U.S. National characters:
    • $ (dollar) as X'5B'
    • # (number) as X'7B'
    • @ (at) as X'7C'.

    In countries other than the U.S., the U.S. National characters represented on terminal keyboards might generate a different hexadecimal representation and cause an error. For example, in some countries the $ character might generate X'4A'. This implies that, depending on the codepage specified with the CODEPAGE parameter of the TWSOPTS initialization statement for the agent, you must use whatever characters correspond to hex X'7C', X'5B', and X'7B'. For example, if IBM_280 is specified as the system codepage in TWSOPTS, then within the job name you can use the £ (pound) character, which is coded as hex X'7B'.

  • Cannot start with a number.
  • Must be followed by at least one blank.

System action

The job is not submitted.

User response

Correct the JCL for this job and use either the IBM Workload Scheduler conman command line or the Dynamic Workload Console to submit the job again.

EELW525E

JOB COULD NOT BE SUBMITTED BECAUSE OF AN ERROR IN THE JOB CARD. THE JOB NAME IS: JOBALIAS

Explanation

The agent for z/OS has been requested to submit a job that has an incorrect job card.

System action

The job is not submitted.

User response

Correct the JCL for this job and use either the IBM Workload Scheduler conman command line or the Dynamic Workload Console to submit the job again.

EELW526E

JOB COULD NOT BE SUBMITTED BECAUSE NO JOB CARD COULD BE FOUND. THE JOB NAME IS: JOBALIAS

Explanation

The agent for z/OS has been requested to submit a job that does not have a job card.

System action

The job is not submitted.

User response

Correct the JCL for this job and use either the IBM Workload Scheduler conman command line or the Dynamic Workload Console to submit the job again.

EELW527E

JOB NAME COULD NOT BE SUBMITTED BECAUSE THE JOB CARD ACCOUNT INFORMATION PARAMETER HAS THE LAST CHARACTER IN COLUMN 71. THE JOB NAME IS: JOBALIAS

Explanation

The last character of the account information parameter in the job card cannot occupy column 71.

System action

The job is not submitted.

User response

Correct the JCL for this job by placing the last character of the account information parameter in a column before column 71 and submit the job again.

EELW528E

JOB NAME COULD NOT BE SUBMITTED BECAUSE THE JOB CARD ACCOUNT INFORMATION HAS A CHARACTER IN COLUMN 72. THE JOB NAME IS: JOBALIAS

Explanation

Account information characters are not allowed in column 72 of the job card.

System action

The job is not submitted.

User response

Correct the JCL for this job by replacing with blanks any characters belonging to the account parameter found in column 72 of the job card. Then submit the job again.

EELW766W

THE EVENT CREATION ROUTINE DETECTED THAT THE JES2 EXIT7 (EELEXIT) IS ON A LOWER RDMID LEVEL THAN THE SCHEDULER SUBSYSTEM MODULE EELZEV2X

Explanation

The level of the EELEXIT macro in JES2 EXIT7 (TWSEXIT7) is at a lower maintenance level than the agent for z/OS subsystem.

System action

The event creation routine continues to create event records. The event records might contain invalid tracking information, causing the corresponding operation status to be inaccurate.

Operator response

If necessary, set the correct operation status manually.

System programmer response

Reapply EXIT7, and make sure that the appropriate maclibs are used in the SYSLIB concatenation. If you are assembling TWSEXIT7 outside the JES2 SMP environment, make sure that you have the SMPMTS data set concatenated first in the SYSLIB concatenation.

EELW773W

THE EVENT CREATION ROUTINE DETECTED THAT JES2 EXIT51 (EELEXIT) IS ON A LOWER RMID LEVEL EXITL THAN THE SCHEDULER SUBSYSTEM MODULE EELZEV2Y WHOSE LEVEL IS J2LVL

Explanation

The level of the EELEXIT macro in JES2 EXIT51 (TWSXIT51) is at a lower maintenance level than the agent for z/OS subsystem.

System action

The event creation routine continues to create event records. The event records might contain invalid tracking information, causing the corresponding operation status to be inaccurate.

Operator response

If necessary, set the correct operation status manually.

System programmer response

Reapply EXIT51, and make sure that the appropriate maclibs are used in the SYSLIB concatenation. If you are assembling TWSXIT51 outside of the JES2 SMP environment, make sure that the SMPMTS data set is placed first in the SYSLIB concatenation.

EELW774W

THE EVENT CREATION ROUTINE DETECTED THAT JES2 EXIT51 (EELEXIT) IS ON A HIGHER RMID LEVEL EXITL THAN THE SCHEDULER SUBSYSTEM MODULE EELZEV2Y WHOSE LEVEL IS J2LVL

Explanation

The EELEXIT macro used to generate the currently active JES2 EXIT51 is on a higher maintenance level than the EELZEV2Y subsystem module of the agent for z/OS.

System action

The event creation routine continues to create event records. The event records might contain invalid tracking information, causing the corresponding operation status to be inaccurate.

Operator response

If necessary, set the correct operation status manually.

System programmer response

EELZEV2Y is part of the EELSSCMJ load module, which is normally loaded during IPL. To activate a new EELSSCMJ, until a planned IPL can be performed, specify SSCMNAME(EELSSCMJ) in the TWSOPTS initialization statement and restart the agent for z/OS address space.

EELW777W

THE EVENT CREATION ROUTINE DETECTED THAT THE JES2 EXIT7 (EELEXIT) IS ON A HIGHER RMID LEVEL (EXITL) THAN THE SCHEDULER SUBSYSTEM MODULE EELZEV2X WHOSE LEVEL IS J2LVL

Explanation

The EELEXIT macro used to generate the currently active JES2 EXIT7 is on a higher maintenance level than the subsystem module EELZEV2X.

System action

The event creation routine continues to create event records. The event records might contain invalid tracking information, causing the corresponding operation status to be inaccurate.

Operator response

If necessary, set the correct operation status manually.

System programmer response

The EELZEV2X is part of the EELSSCMJ load module, which is normally loaded during IPL. To activate a new EELSSCMJ, until a planned IPL can be performed, specify SSCMNAME(EELSSCMJ) in the TWSOPTS initialization statement and restart the agent for z/OS address space.

EELZ000I

A STOP COMMAND HAS BEEN RECEIVED

Explanation

The agent for z/OS started task has received an operator stop command.

System action

The agent for z/OS posts all active subtasks for termination and terminates when all subtasks have terminated.

EELZ001E

JES IS NOT ACTIVE. THE SCHEDULER CANNOT START

Explanation

The agent for z/OS subsystem could not start because no primary JES subsystem is active.

System action

The subsystem task module, EELMAJOR, is terminated.

System programmer response

Wait for JES to start and reissue the start command.

EELZ002E

THE EELSSCMJ TIVOLI WORKLOAD SCHEDULER SUBSYSTEM IS ALREADY ACTIVE. IT CANNOT START AGAIN.

Explanation

The subsystem is already running and cannot be started again.

System action

None

System programmer response

None.

EELZ003E

INVALID JOBNAME JOBNAME. NAME MUST BE 4 CHARACTERS OR LESS

Explanation

The agent for z/OS subsystem task module, EELMAJOR, has been incorrectly invoked.

System action

The EELMAJOR module is terminated.

System programmer response

Change the name of the agent for z/OS subsystem started task to one of the subsystem names defined in SYS1.PARMLIB and reissue the start command.

EELZ004E

UNABLE TO ATTACH SUBTASK SUBTASK

Explanation

An error occurred when the agent for z/OS subsystem attempted to attach the subtask SUBTASK.

System action

The agent continues processing.

System programmer response

Correct all errors and restart the agent.

Problem determination

Review earlier messages in the agent for z/OS message log and SYSLOG data sets to determine the exact reason for this message. One possibility is that the agent is being started in a region that is too small.

EELZ005I

SUBTASK SUBTASK IS BEING STARTED

Explanation

The agent for z/OS subsystem has successfully attached the subtask SUBTASK.

System action

The agent continues processing. If the startup process is successful, the subtask issues its own start message.

EELZ006I

NO ACTIVE PRODUCT SUBTASKS. THE SCHEDULER IS ENDING

Explanation

All agent for z/OS subtasks have terminated. The agent for z/OS subsystem is about to enter its own termination process.

System action

The agent for z/OS subsystem frees all acquired resources and is terminated.

EELZ007E

JOBNAME JOBNAME IS NOT A VALID SUBSYSTEM NAME

Explanation

The agent for z/OS subsystem task module, EELMAJOR, has been incorrectly invoked.

System action

The EELMAJOR module is terminated.

System programmer response

Change the name of the agent for z/OS subsystem started task to one of the subsystem names defined in SYS1.PARMLIB and reissue the start command.

EELZ008E

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

Explanation

The agent for z/OS 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 EELINITJ program.

System action

Processing continues.

System programmer response

Correct all errors and restart the agent after an IPL of the z/OS system.

Problem determination

Check that the currently active IEFSSNxx member of SYS1.PARMLIB defines the agent for z/OS subsystem correctly. Check also that EELINITJ is present in SYS1.LINKLIB or in a library in the LNKLSTxx concatenation of libraries. Review the master console messages issued during IPL.

EELZ010E

MEMBER MEMBER CANNOT BE FOUND IN PARAMETER LIBRARY

Explanation

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

System action

The agent for z/OS subtask that issues this message is terminated.

System programmer response

Correct all errors and restart the failing subtask.

Problem determination

Check that the EELPARM DD statement is correctly defined. Check also that the TWSOPTS initialization statement is correctly defined.

EELZ011E

PARAMETER LIBRARY MEMBER MEMBER IS EMPTY

Explanation

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

System action

The agent for z/OS subtask that issues this message is terminated.

System programmer response

Correct all errors and restart the failing subtask.

Problem determination

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

EELZ012E

I/O ERROR READING PARAMETER LIBRARY MEMBER MEMBER

Explanation

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

System action

The agent for z/OS subtask that issues this message is terminated.

System programmer response

Correct all errors and restart the failing subtask.

Problem determination

Review earlier messages in the agent for z/OS message log to determine the exact reason for this message.

EELZ013I

NOW PROCESSING PARAMETER LIBRARY MEMBER MEMBER

Explanation

An agent for z/OS subtask has started processing the parameter library member MEMBER.

System action

processing continues.

System programmer response

None.

EELZ014I

MAXIMUM RETURN CODE FOR PARAMETER MEMBER MEMBER IS: MAXCC

Explanation

An agent for z/OS subtask has finished processing the parameter library member MEMBER. MAXCC is the maximum return code encountered for agent for z/OS initialization statements in the member.

System action

If the maximum return code is not zero, the agent for z/OS subtask that issues this message is terminated.

System programmer response

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

EELZ015I

INIT STATEMENT: CARD

Explanation

An agent for z/OS subtask that is processing a parameter library member prints the entire member using this message.

System action

Processing continues.

System programmer response

None.

EELZ016I

RETURN CODE FOR THIS STATEMENT IS: MAXCC

Explanation

An agent for z/OS subtask has finished processing an initialization statement. MAXCC is the return code sent by the subtask. It indicates if the statement was successfully processed.

System action

The agent for z/OS subtask continues processing initialization statements.

System programmer response

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

EELZ018E

INITIALIZATION STATEMENT SPECIFICATION IS LONGER THAN 455 RECORDS

Explanation

An initialization statement cannot exceed 455 input records.

System action

Initialization of the agent for z/OS fails.

System programmer response

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.

EELZ022W

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

Explanation

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

System action

Initialization continues, using the EELSSCMJ module defined by IEFSSNxx for agent for z/OS event generation.

System programmer response

Check that the module name specified in SSCMNAME is correct and that the module is contained in an APF-authorized library, accessible to the agent for z/OS either by the STEPLIB DD statement or by the LNKLSTxx concatenation.

EELZ023W

THE SSCMNAME LOAD MODULE SPECIFIED, SSCM, IS NOT VALID

Explanation

The module name specified in the SSCMNAME keyword of the TWSOPTS initialization statement is not valid.

System action

The agent for z/OS subsystem continues to create event records using the EELSSCMJ module that was loaded during IPL.

System programmer response

Specify a valid agent for z/OS event creation routine.

EELZ024I

BEXTXT

Explanation

This message contains output from the agent for z/OS internal diagnostic routines.

System action

The agent for z/OS continues normal processing.

System programmer response

None.

EELZ030E

THE AGENT WAS UNABLE TO OPEN THE MESSAGE LOG DATA SET.

Explanation

The agent for z/OS cannot open its message log data set.

System action

The subsystem task module is terminated.

System programmer response

Correct the errors and reissue the start command.

Problem determination

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

EELZ031E

THE AGENT WAS UNABLE TO OPEN THE MESSAGE LIBRARY FILE.

Explanation

The agent for z/OS cannot open its message library data set.

System action

The subsystem task module is terminated.

System programmer response

Correct the errors and reissue the start command.

Problem determination

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

EELZ032E

SIZE OF AGENT MESSAGE LIBRARY RECORDS MUST BE 80 BYTES

Explanation

The agent for z/OS cannot use its message library data set because the data set does not contain message records of 80 bytes.

System action

The subsystem task module is terminated.

System programmer response

Correct the errors and reissue the start command.

Problem determination

Check that the EELMLIB DD statement is correctly coded.

EELZ033E

THE AGENT IS ENDING. MESSAGE ROUTINE COULD NOT BE INITIALIZED

Explanation

The agent for z/OS cannot initialize its message services.

System action

The subsystem task module is terminated.

System programmer response

Correct the errors and reissue the start command.

Problem determination

Check the previous WTO messages from this subsystem.

EELZ034I

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

Explanation

An agent for z/OS subtask has ended after being requested to stop processing. This message documents how long the subtask was active and how much CPU time it used.

System action

The agent for z/OS continues normal processing.

System programmer response

None.

EELZ035E

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

Explanation

An agent for z/OS queue has reached its maximum size and a number of events could not be added. The most likely reason is that the agent for z/OS 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 agent for z/OS subsystem.

QNAME can be one of the following:
HTTQ
The HTTP client task queue
MSGQ
The agent for z/OS message queue
RTRQ
The data router queue
SUBQ
The submit queue
WTRQ
The event writer queue

System action

The agent for z/OS continues processing.

System programmer response

If the message is issued for the WTRQ of a production agent for z/OS 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 IBM Software Support.

Problem determination

This message is sometimes issued for the WTRQ of a test agent for z/OS subsystem that is started only infrequently. If the message is issued for a production system, the error might be caused by an unusually long delay in starting the agent for z/OS or by insufficient ECSA storage for agent for z/OS event buffering.

EELZ036E

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

Explanation

The agent for z/OS tried to retrieve information from the definition of an agent for z/OS ddname, but failed.

System action

The task issuing this message is terminated.

System programmer response

Correct the error and restart the agent for z/OS subsystem.

Problem determination

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.

EELZ037E

A REQUIRED DD-CARD IS MISSING. DDNAME = DDNAME

Explanation

An EELMLOG DD statement is needed, to start the agent for z/OS in the manner defined by the current input parameter statements.

System action

If the EELMLOG DD statement is missing, the subsystem task module, EELMAJOR, is terminated.

System programmer response

Add the missing DD statement to the started task procedure and restart the agent for z/OS subsystem.

EELZ039E

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

Explanation

You tried to start an agent for z/OS subsystem using an output data set that is being used by another agent for z/OS subsystem.

System action

The subsystem is terminated.

System programmer response

Change the definition of the DD statement and restart the agent for z/OS subsystem.

EELZ045E

SUBTASK SUBTASK ENDED UNEXPECTEDLY

Explanation

An agent for z/OS subtask ended without having been requested to terminate.

System action

The agent for z/OS continues processing.

Operator response

If necessary, use the system MODIFY command to restart the failing task.

Problem determination

Review earlier messages in the agent for z/OS 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 agent for z/OS started task.

EELZ048I

A MODIFY COMMAND HAS BEEN PROCESSED. MODIFY SSNAME,FPARAM

Explanation

A MODIFYcommand has been processed successfully.

System action

The agent for z/OS continues processing.

System programmer response

None.

EELZ049W

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

Explanation

A MODIFY command could not be processed because parameters on the MODIFY command could not be recognized or because they are out of context.

System action

The incorrect command is ignored. The agent for z/OS continues processing.

Operator response

Correct the MODIFY command and issue it again.

Problem determination

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.

EELZ050W

THE PRODUCT SUBSYSTEM HAS BEEN CANCELLED

Explanation

An operator CANCEL command has been received.

System action

The agent for z/OS terminates without waiting for subtasks to end.

System programmer response

None.

EELZ051E

THE PRODUCT SUBSYSTEM MOTHER TASK HAS ABENDED

Explanation

A severe error has occurred in the agent for z/OS subsystem task.

System action

The agent for z/OS terminates without waiting for subtasks to end. If a dump data set is allocated, a dump is created.

System programmer response

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

Problem determination

Review earlier messages in the agent for z/OS message log data set, SYSLOG data set, and the dump data set to determine what caused the subsystem to abend.

EELZ052E

THE PARAMETER LIBRARY FILE, DDNAME = EELPARM OR DDNAME = EELYPARM, COULD NOT BE OPENED.

Explanation

The agent for z/OS could not open the parameter library file, ddname EELPARM or EELYPARM, which is a required input data set for the agent.

System action

The agent for z/OS is terminated. Message EELZ054E is issued.

System programmer response

Check that ddname EELPARM or EELYPARM is correctly specified and that the agent for z/OS started task is authorized to open the data set for input. Correct all errors and restart the agent.

EELZ053E

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

Explanation

The agent for z/OS cannot use the parameter library data set, ddname EELPARM, because its logical record length is not 80 bytes.

System action

The agent for z/OS is terminated. Message EELZ054E is issued.

System programmer response

Check that EELPARM is correctly defined. Correct all errors and restart the agent.

EELZ054E

ERRORS DETECTED PROCESSING PRODUCT PARAMETERS. THE SCHEDULER IS ENDING

Explanation

The agent for z/OS found one or more errors while processing its initialization member.

System action

Initialization of the agent for z/OS fails.

System programmer response

Correct all errors and restart the agent.

EELZ058E

THE BEX INTERFACE MODULE, EELBEX, COULD NOT BE LOADED

Explanation

The agent for z/OS could not locate the agent for z/OS service routine interface load module EELBEX.

System action

Normal mode manager (NMM) initialization fails.

System programmer response

Make sure that the EELBEX load module is present in a library that can be reached by the agent for z/OS and restart the NMM.

EELZ062W

THE START/STOP USER EXIT MODULE COULD NOT BE LOADED

Explanation

The agent for z/OS could not locate the subsystem start?stop exit load module EELUX000.

System action

The subsystem start?stop exit is not used by the agent.

System programmer response

If the subsystem start?stop exit is meant to be used, make sure that the EELUX000 load module is present in a library that can be reached by the agent for z/OS. Restart the agent for z/OS started task.

EELZ066W

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

Explanation

The agent for z/OS 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.

System action

Processing continues. A JES2 system is assumed.

System programmer response

Check the installation of the JES2 EXIT7 exit. If the shipped EELEXIT macro has been modified, make sure that it does not prevent or filter the tracking tasks of the agent.

EELZ067E

COMMAND SYNTAX ERROR: CARD FURTHER STATEMENT PROCESSING STOPPED

Explanation

The statement contains a syntactically incorrect command.

System action

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

User response

Correct the error.

EELZ068E

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

Explanation

The agent for z/OS has detected an unknown command in this statement.

System action

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

User response

Correct the error.

EELZ070E

THE SSCMNAME KEYWORD SPECIFIES AN OPTION THAT IS NOT RECOGNIZED

Explanation

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

System action

Initialization of the agent for z/OS fails.

System programmer response

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 the agent for z/OS.

EELZ071E

OPTION PERMANENT FOR THE SSCMNAME KEYWORD REQUIRES THE BUILDSSX KEYWORD

Explanation

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

System action

Initialization of the agent for z/OS fails.

System programmer response

Add the BUILDSSX keyword to the TWSOPTS initialization statement and restart the agent for z/OS.

EELZ072W

OPTION PERMANENT FOR THE SSCMNAME KEYWORD REQUIRES STEPLIB DD-STATEMENT

Explanation

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

System action

The agent for z/OS starts without loading the SSCM module permanently.

System programmer response

Add a STEPLIB DD statement to the JCL used to start the subsystem and restart the agent for z/OS.

EELZ073I

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

Explanation

JESTYPE is JES2. CMDCHAR is the command character that the agent for z/OS uses when issuing JES2 commands. NJENODE is the name of this network job entry (NJE) node.

System action

Normal processing continues.

System programmer response

If JESTYPE, CMDCHAR, or NJENODE is not correct, check the installation of the JES2 EXIT7 exit. If the shipped EELEXIT macro has been modified, make sure that it does not prevent or filter the tracking tasks of the agent.

EELZ074W

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

Explanation

The NJENODE parameter was not specified. During initialization of the event writer, the agent for z/OS was unable to determine the name of the network job entry (NJE) node for this system.

System action

Processing continues.

System programmer response

Check the installation of the JES2 EXIT7 exit. If the shipped EELEXIT macro has been modified, make sure that it does not prevent or filter the tracking tasks of the agent.

EELZ075W

THE JES2 COMMAND CHARACTER MAY BE INCORRECT

Explanation

The JES2 command character that the agent for z/OS uses (stated in message EELZ073I) might be incorrect.

System action

Processing continues.

System programmer response

If the JES2 command character is incorrect, check the installation of the JES2 EXIT7 exit. If the shipped EELEXIT macro has been modified, make sure that it does not prevent or filter the tracking tasks of the agent.

EELZ096W

OBSOLETE PARAMETER SPECIFIED:keyword. THE PARAMETER IS IGNORED

Explanation

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

System action

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

System programmer response

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

EELZ097W

OBJ LOAD MODULE COULD NOT BE LOADED

Explanation

The agent for z/OS could not locate the load module shown in the message text.

System action

Initialization of the agent for z/OS main task continues.

System programmer response

None.

EELZ106W

PERCENT % OF QUEUE QNAME IN USE

Explanation

The utilization of a queue has exceeded a threshold value.

System action

None.

System programmer response

Ensure that all subtasks are active. Check system contention.

EELZ125E

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

Explanation

One of the agent for z/OS internal queues is full. The subsystem was canceled by the task that added the last element.

System action

The agent for z/OS subsystem is terminated.

Programmer response

Restart the agent for z/OS subsystem and verify that all subtasks start normally.

Problem determination

Check the agent for z/OS message log for EELZ106W messages indicating which queue is full. Check for other previous messages about the subtask that is processing the queue:
MGRQ
Event manager
SUBQ
Submit task
RTRQ
Data router task

EELZ129I

TAKEOVER IN PROGRESS

Explanation

This system has started takeover processing.

System action

The system continues initialization as the new host.

System programmer response

None.

EELZ132W

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

Explanation

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

System action

Processing continues.

System programmer response

None.

EELZ133W

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

Explanation

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

System action

Data router termination continues.

System programmer response

None.

EELZ140E

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

Explanation

A nonnumeric date value has been specified.

System action

Processing continues.

System programmer response

Reenter a numeric date value.

EELZ141E

YEAR MUST BE IN THE RANGE 00 TO 99

Explanation

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.

System action

Processing continues.

System programmer response

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

EELZ142E

MONTH MUST BE IN THE RANGE 1 TO 12

Explanation

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

System action

Processing continues.

System programmer response

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

EELZ143E

DAY MUST BE IN THE RANGE 1 TO 31

Explanation

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

System action

Processing continues.

System programmer response

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

EELZ144E

DAY DD IS NOT VALID IN FEBRUARY

Explanation

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

System action

Processing continues.

System programmer response

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

EELZ145E

MONTH MM DOES NOT HAVE 31 DAYS

Explanation

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

System action

Processing continues.

System programmer response

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

EELZ146E

YEAR YY DOES NOT HAVE 29 DAYS IN FEBRUARY

Explanation

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.

System action

Processing continues.

System programmer response

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

EELZ147E

HOUR AND MINUTE MUST BOTH BE TWO-DIGIT NUMBERS

Explanation

A nonnumeric time value has been specified.

System action

Processing continues.

System programmer response

Reenter a numeric time value.

EELZ148E

HOUR MUST BE IN THE RANGE 0 TO 23

Explanation

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

System action

Processing continues.

System programmer response

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

EELZ149E

MINUTE MUST BE IN THE RANGE 0 TO 59

Explanation

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

System action

Processing continues.

System programmer response

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

EELZ170E

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

Explanation

Initialization of the agent for z/OS has determined that the SSX control block, the EELMAJOR module and the EELSSCMJ load module are on different service levels. This difference is not supported.

System action

Initialization of the agent for z/OS fails.

System programmer response

Verify that the agent for z/OS is using the correct load library. If the SSX control block and the EELMAJOR module are on different code levels, modify the TWSOPTS statement, specifying the BUILDSSX keyword. If the EELSSCMJ and the EELMAJOR modules are on different code levels, modify the TWSOPTS statement, adding or changing the SSCMNAME keyword.

After making the appropriate changes, restart the agent for z/OS subsystem.

EELZ171E

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

Explanation

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

System action

Initialization of the agent for z/OS fails.

System programmer response

Change the BUILDSSX keyword to specify BUILDSSX(REBUILD).

EELZ172I

SSX BLOCK OF VERSION SSXLEV SUCCESSFULLY BUILT

Explanation

The BUILDSSX keyword was specified in the TWSOPTS control statement and the agent for z/OS has successfully verified that the EELSSCMJ load module is of the correct version. A new SSX control block has been built and is used by this agent for z/OS address space.

System action

Initialization of the agent for z/OS address space continues.

EELZ173I

SSX BLOCK OF VERSION SSXLEV SUCCESSFULLY RESTORED

Explanation

The BUILDSSX keyword was specified in the TWSOPTS control statement and the agent for z/OS 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 the agent for z/OS 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 the agent for z/OS functions while the agent for z/OS subsystem is inactive.

System action

Termination of the agent for z/OS address space continues.

EELZ174W

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

Explanation

The BUILDSSX keyword was specified in the TWSOPTS 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.

System action

Initialization of the agent for z/OS continues.

System programmer response

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

If this message is not expected, verify that the load modules used by the agent for z/OS are coming from the correct load libraries. After making the appropriate changes, restart the agent for z/OS subsystem.

EELZ182E

SUBSTRING EXCEEDS BOUNDS OR LENGTH ZERO WAS FOUND IN PARMREC

Explanation

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.

System action

The task is terminated.

System programmer response

Correct the wrong symbol definitions. Restrictions in the usage of symbols are documented in the Assembler Services Reference guide.

EELZ183E

UNEXPECTED ERROR DURING SYMBOL SUBSTITUTION

Explanation

During symbol substitution processing, an unexpected error occurred.

System action

The task is terminated.

System programmer response

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

EELZ188E

UNEXPECTED RETURN CODE DURING SYMBOL SUBSTITUTION

Explanation

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

System action

The agent for z/OS stops processing.

System programmer response

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

EELZ190E

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

Explanation

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

System action

The initialization process is terminated.

System programmer response

Check that the level of the agent for z/OS 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 the agent.

Programmer response

Contact your system programmer.

EELZ192E

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

Explanation

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

System action

The initialization process is terminated.

System programmer response

Check that the level of the agent for z/OS 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 the agent.

EELZ200I

TWSTYP SSNAME HEARTBEAT

Explanation

This message is sent by the agent for z/OS at startup or as result of a heartbeat command, to state that the agent is active and running. SSNAME is the name of the agent for z/OS subsystem.

System action

If the agent 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.

System programmer response

None.

EELZ201I

TWSTYPE SSNAME STATUS: STATUS

Explanation

Displays the status of the agent for z/OS subsystem, where:
SSNAME
The name of the subsystem.
STATUS
One of the following values:
FULLY_OPERATIONAL
The subsystem is working correctly.
PARTIALLY_OPERATIONAL
The subsystem has limited functionality.
NOT_OPERATIONAL
The agent is not working.

System action

If the agent 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.

Programmer response

If the STATUS is not FULLY_OPERATIONAL, one or more of the agent for z/OS 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 EELZ202I lists the inactive subtasks, which you should restart.

EELZ202I

FOLLOWING SUBTASKS ARE INACTIVE: TASKLST

Explanation

Lists the names of the agent for z/OS subtasks that are inactive. If the agent for z/OS status is not FULLY_OPERATIONAL, this message is always issued in conjunction with message EELZ201I.

System action

Normal processing continues.

Programmer response

Restart the agent or the indicated subtask.

EELZ203I

TWSTYPE SSNAME INFORMATION: TRKADDR TRKSTAT

Explanation

Provides information about the status of an agent for z/OS subsystem.
TWSTYPE
Is AGENT
SSNNAME
The name of the agent for z/OS subsystem.
TRKADDR
The TCP/IP address associated with this agent.
TRKSTAT
The status of the agent. It can be one of the following values:
  • ONLINE
  • OFFLINE

System action

None.

Programmer response

If the status of the agent is OFFLINE, either the agent is not running or the connection is down. Restart the agent or check if there are connectivity problems between the agent and Dynamic Workload Console.

EELZ204I

TWSTYPE SSNAME INFORMATION: TRKADDR HEARTBEAT

Explanation

This message is sent by the agent for z/OS at startup to state that the agent is active and running.
TWSTYPE
Is AGENT
SSNNAME
The name of the agent for z/OS subsystem.
TRKADDR
The TCP/IP address associated with this agent.

System action

None.

System programmer response

None.

EELZ207I

TWSTYPE SSNAME IS STATUS

Explanation

Displays the status of the specified agent for z/OS subsystem.
TWSTYPE
Is AGENT
SSNNAME
The name of the agent for z/OS subsystem.
STATUS
The status of the agent for z/OS subsystem. Can be:
ACTIVE
The agent is running.
INACTIVE
The agent is not running.

EELZ208I

DDNAME LAST-RC= LASTRC

Explanation

Provides the return code of the last I/O operation on the specified DDNAME.
DDNAME
The ddname of the agent 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

System action

Depending on the return code value and on the specified DDNAME, the agent for z/OS could stop some of its subtasks.

Programmer response

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

EELZ210I

ERRCODE ERROR ACCESSING SSNAME DATASET: ERRMSG

Explanation

An error occurred accessing a data set, where:
SSNAME
The name of the agent for z/OS 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.

System action

Depending on the ERRCODE value, some of the agent for z/OS functions could not work correctly.

System programmer response

Check the status of data set.

EELZ213W

THE THRESHOLD MUST BE IN THE RANGE FROM 0 TO 100

Explanation

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.

System action

None.

User response

None.

EELZ215E

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

Explanation

The agent for z/OS 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.

System action

If the agent 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 agent was to check a specific scheduling environment, the related job is not submitted and the following EELSU37E message specifies the name of the job.

User response

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

EELZ245I

CODEPAGE VALUE IS NOT PRESENT IN TWSOPTS STATEMENT. THIS VALUE IS MANDATORY.

Explanation

A value for the CODEPAGE parameter of the TWSOPTS statement was not specified.

System action

The agent for z/OS does not start.

User response

This parameter is required for the agent to start properly. Enter the codepage value used in your z/OS system and start the agent again.

EELZ246E

CODEPAGE KEYWORD IS NOT PRESENT IN TWSOPTS STATEMENT. THIS KEYWORD IS MANDATORY.

Explanation

The CODEPAGE parameter was not specified in the TWSOPTS statement.

System action

The agent for z/OS does not start.

User response

This parameter is required for the agent to start properly. Add the keyword to the TWSOPTS initialization statement in the PARMLIB, enter the codepage value used in your z/OS system, and start the agent again.

EELZ247E

CODEPAGE KEYWORD DOES NOT HAVE A VALID VALUE.

Explanation

The value provided for the CODEPAGE is not supported.

System action

The agent for z/OS does not start.

User response

Enter the codepage value used in your z/OS system, and start the agent again.

EELZ250W

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

Explanation

The value specified for keyword KEYWD is incorrect.

System action

The processing continues using the default value for keyword KEYWD.

User response

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

EELZ251I

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

Explanation

Keyword KEYWD was not specified in statement STMT.

System action

The processing continues using the default value for keyword KEYWD.

User response

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

EELZ263W

COMMAND IS NOT VALID ON AGENT.

Explanation

This command is not supported on the agent for z/OS.

System action

The request is rejected.

System programmer response

None.

EELZ400I

TIVOLI WORKLOAD SCHEDULER AGENT FOR Z/OS VERSION VERSION. THE AGENT IS RUNNING AT SERVICE LEVEL: LEVEL - FMID

Explanation

This message is logged every time the agent for z/OS is started. Level is: 
YY/MM/DD HH.MM.SS YYXXXXX
where:
YY/MM/DD HH.MM.SS
Is the build date and time.
YYXXXXX
Is the APAR level.

User response

None.

EELZ410W

PARAMETER KEYWORD IGNORED. NOT USABLE FOR THIS AGENT TYPE.

Explanation

The keyword shown in the message text is not valid for this agent type or is no longer supported.

System action

The initialization of the agent continues and the keyword is ignored.

EELZ411I

PRODUCT ACTION SUCCESSFUL. TOKEN PTOKEN.

The product has been registered or unregistered to the IBM system with the indicated token.

Processing continues.

None.

EELZ412I

AN ERROR OCCURRED WHILE ACTION PRODUCT. SERVICE MACRO. RC RETCODE

An error occurred while the product was being registered or unregistered to the IBM system. The action is not completed..

Processing continues.

None.