EQQPH00 - EQQP109

EQQPH00I

SERVER TASK HAS STARTED

The server task has started successfully. This task is started by the server started task. It is started by the HCL Workload Automation for Z subsystem if APPC(YES) is specified in the OPCOPTS initialization statement.

HCL Workload Automation for Z continues processing.

EQQPH01I

SERVER TASK ENDED

The server task has been requested to stop and is ending normally.

HCL Workload Automation for Z continues processing.

EQQPH02E

SERVER NAME IS ALREADY ACTIVE, IT CANNOT START AGAIN

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

The second attempt to invoke the server is terminated.

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

EQQPH03I

AN ELEMENT ON THE APPC/MVS QUEUE IS OF UNRECOGNIZED TYPE: ELEM

HCL Workload Automation for Z receives APPC requests, for example, allocate requests, on the APPC queue. The queue element presented in the message is not supported by the server task.

The queue element is deleted from the APPC queue. It causes no further action.

The message variable ELEM gives diagnostics, which is expecially useful if there are other indications on an error in the HCL Workload Automation for Z server APPC communication.

EQQPH05E

BUFFER CONTAINS WRONG AMOUNT OF INPUT DATA, OR WRONG VALUES

The APPC and TCP/IP communication routines of the HCL Workload Automation for Z server receive data for processing by the server. The buffer of data is validated and does not pass the validation.

The server deallocates the APPC (TCP/IP) conversation. The contact between either the HCL Workload Automation for Z dialog or the program interface application and the HCL Workload Automation for Z subsystem is thereby broken. The partner of the APPC (TCP/IP) conversation needs to reestablish the connection.

Save a slip trap on message EQQPH05E and dump the HCL Workload Automation for Z Server task. Save the HCL Workload Automation for Z server and controller message log and the SYSLOG portion that includes the message. If the problem persists, to collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures. Search the IBM Support database for a solution at Support.

Check the HCL Workload Automation for Z Server region size to verify if this value is not enough to run the workload. Describe the scenario that caused the error.

EQQPH06E

A SERVER SUBTASK ABENDED. THE SUBTASK WAS CREATED FOR PROCESSING APPC ALLOCATE DATA: FMH5 FMH52

The HCL Workload Automation for Z server has created a subtask for processing requests from a remote dialog user or a program interface application. The subtask has abended.

The server deallocates the APPC conversation. The contact between either the HCL Workload Automation for Z dialog or the program interface application and the HCL Workload Automation for Z subsystem is thereby broken.

If the problem persists save the server and controller message log and the DUMP produced. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures. Search the IBM Support database for a solution at Support.

Check the Server region size to verify if this value is not enough to run the workload. Describe the scenario that caused the error.

EQQPH07E

A SERVER OBJECT ABENDED. THE OBJECT WAS CREATED TO PROCESS TYPE REQUESTS.

A HCL Workload Automation for Z server subtask was created to process requests from a remote dialog user using a TCP/IP connection. The subtask has abended.

For the end-to-end server the problem may be that it is pointing to the wrong work directory. If this is the case, this is due to the fact that either the BINDIR or WRKDIR values in the TOPOLOGY statement may be discordant with the values created with the EQQPCS05 sample.

The server closed the TCP/IP connection, so contact between the HCL Workload Automation for Z dialog and the HCL Workload Automation for Z subsystem has been lost.

If you use end-to-end scheduling, check the BINDIR and WRKDIR values in the TOPOLOGY statement.

If the problems recurs, report the error to IBM Software Support.

EQQPH08I

TCP/IP CANNOT BE INITIALIZED. CHECK THAT TCP/IP IS AVAILABLE AND THAT SSL IS PROPERLY CONFIGURED.

A HCL Workload Automation for Z server got an error when trying to communicate with TCP/IP.

The HCL Workload Automation for Z server stops processing.

Check that TCP/IP is available.

EQQPH09I

THE SERVER IS USING THE PROT PROTOCOL

A HCL Workload Automation for Z server is using the PROT protocol for communication.

None.

EQQPH10E

COMMUNICATION WITH USER USER AT LU LU FAILED, APPC/MVS SERVICE VERB REQUESTED IN STATE STATE RETURN_CODE RC, STATUS_RECEIVED SR, DATA_RECEIVED DR

The APPC communication between a dialog user or program interface application and the HCL Workload Automation for Z server failed. An APPC service request issued by the server ended with a nonzero return code.

The server deallocates the APPC conversation. The contact between either the HCL Workload Automation for Z dialog or the program interface application and the HCL Workload Automation for Z subsystem is therby broken.

Check the meaning of the APPC return codes. If the problem recurs, report the error to IBM Software Support.

EQQPH11E

COMMUNICATION WITH USER USER AT LU LU FAILED, UNEXPECTED COMBINATION OF RETURN VALUES APPC/MVS SERVICE VERB REQUESTED IN STATE STATE RETURN_CODE RC, STATUS_RECEIVED SR, DATA_RECEIVED DR

The APPC communication between a dialog user or program interface application and the HCL Workload Automation for Z server failed. An APPC service request ended with a combination of return values that is not supported by the communication routines.

The server deallocates the APPC conversation. The contact between either the HCL Workload Automation for Z dialog or the program interface application and the HCL Workload Automation for Z subsystem is thereby broken. The partner of the APPC conversation, a dialog user, or a program interface application, is informed about the error by message EQQPH14 and an error return code. A HCL Workload Automation for Z dialog user gets message EQQPH14 displayed at the next terminal action. A program interface application gets message EQQPH14 written to the message log of the program interface job and the EQQYCOM call ends with a return code of 8.

Check the meaning of the APPC return codes. If the problem recurs, report the error to IBM Software Support.

EQQPH12E

COMMUNICATION WITH USER USER AT LU LU FAILED, INSUFFICIENT VIRTUAL STORAGE AVAILABLE, DIAGNOSTIC INFO ALT

The APPC communication between a dialog user or program interface application and the HCL Workload Automation for Z server failed because of insufficient storage for the server task.

The server deallocates the APPC conversation. The contact between either the HCL Workload Automation for Z dialog or the program interface application and the HCL Workload Automation for Z subsystem is thereby broken.

Stop the server, or the HCL Workload Automation for Z Controller if the message is in the Controller message log, and restart it in a larger region.

EQQPH13E

FAILED TO LOAD SERVICE MODULE MOD

A dialog user or a program interface application tries to invoke HCL Workload Automation for Z remotely. A HCL Workload Automation for Z server module required for the remote communication cannot be located.

The system waits for you to respond.

Check that the module can be accessed. If the problem recurs, report the error to IBM Software Support.

EQQPH14E

USER USER AT LU LU TERMINATED COMMUNICATION WITHOUT DEALLOCATE

This message is issued in the APPC server message log. The communication terminated prematurely on the user side, either because the TERM request in a program interface running through the APPC was not processed or a dialog user terminated prematurely an APPC session (for example, by pressing the Escape key). It might be also due to a program abend.

The communication is terminated on the server side.

Check the communication on the server side.

EQQPH15E

COMMUNICATION FAILED. TCPIP SOCKET_CALL VERB CALLED IN STATE STATEINVALID SOCKET CALL OR STATE SOCKET CALL RETURN_CODE RC, REASON_CODE RS

The TCP/IP connection between a dialog user and a HCL Workload Automation for Z server failed. Either the TCP/IP socket service or the connection subtask state is invalid.

The server closes the TCP/IP connection. Contact between the HCL Workload Automation for Z dialog and the HCL Workload Automation for Z subsystem is lost. The partner of the TCP/IP connection is informed about the error.

Verify that the value specified in the message (case sensitive) is the same reported in the RACF profile for TMEADMIN. Search the IBM Support database for a solution at Support.

EQQPH16E

COMMUNICATION FAILED. TCPIP SOCKET_CALL VERB FAILED IN STATE STATE RETURN_CODE RC, REASON_CODE(ERRNO) RS

The TCP/IP connection between a dialog user and a HCL Workload Automation for Z server failed. A TCP/IP socket service call failed.

The server closes the TCP/IP connection. Contact between the HCL Workload Automation for Z dialog and the HCL Workload Automation for Z subsystem is lost. The partner of the TCP/IP connection is informed about the error.

Look at the TCP/IP return codes to discover the reason. If the problem recurs, report the error to IBM Software Support.

EQQPH17E

COMMUNICATION FAILED, INSUFFICIENT VIRTUAL STORAGE AVAILABLE, DIAGNOSTIC INFO ALT

The TCP/IP connection between a dialog user and a HCL Workload Automation for Z server failed due to insufficient storage for the server task.

The server deallocates the TCP/IP connection. Contact between the HCL Workload Automation for Z dialog and the HCL Workload Automation for Z subsystem is lost. The partner of the TCP/IP connection is informed about the error.

Stop the server and restart it in a larger region.

EQQPH18E

COMMUNICATION FAILED, THE FUNCTION SOCKET CALL FAILED WITH ERROR CODE ERRNO

The TCP/IP connection between a dialog user and a HCL Workload Automation for Z server failed. A TCP/IP socket service call failed.

If the TCP/IP connection is active, the connection is closed and contact between the HCL Workload Automation for Z dialog and the HCL Workload Automation for Z subsystem is lost.

Look at the TCP/IP return codes to discover the reason. If the problem recurs, report the error to IBM Software Support. Typical examples are ERRNO=1011 (the DD card SYSTCP might be missing in the TCP/IP started task), ERRNO=156 (the OMVS segments for the server STC could not be defined), and ERRNO=13 (the server is related to a different port number in the TCP/IP profile data set).

EQQPH19E

COMMUNICATION FAILED, THE COMMUNICATION WAS TIMED OUT. COMMUNICATION CLOSED

The TCP/IP connection between a dialog user and a HCL Workload Automation for Z server was timed out. The connection was inactive for too long.

The server closes the TCP/IP connection. Contact between the HCL Workload Automation for Z dialog and the HCL Workload Automation for Z subsystem is lost. The partner of the TCP/IP connection is informed about the error. The HCL Workload Automation for Z server continues processing.

Try to locate the previous error messages in the message log, and contact your system programmer.

EQQPH20E

COMMUNICATION FAILED, A PROTOCOL ERROR WAS DETECTED BY THE SERVER. COMMUNICATION CLOSED

The TCP/IP connection between a remote interface (dialog or batch interface) and a HCL Workload Automation for Z server failed due to a protocol error. Possibly, an incorrect connection parameter was provided.

The server closes the TCP/IP connection. Contact between the remote interface and subsystem is lost. The partner of the TCP/IP connection is informed about the error.

Check the connection parameters. It is very likely that there is a firewall misalignment between the server and the client (for example, the server is set with the SSLFORCE option to YES, but the client does not use SSL).

EQQPH21E

TYPE IS NOT CORRECT. TYPE MUST BE IN THE RANGE FROM 0 TO 65535, DEFAULT TYPEDEFAULT IS CURRENTLY USED.

An incorrect TYPE parameter value has been specified.

The TYPE parameter value is set to DEFAULT.

If you do not want to use the default value, check the TYPE value in the SERVOPTS statement. It must be within the range 0 to 65535.

EQQPH22E

COMMUNICATION FAILED, TCPIP SOCKET CALL VERB CALLED IN STATE STATE. UNEXPECTED COMBINATION SOCKET CALL RETURN _CODE RC, REASON_CODE RS

The TCP/IP connection between a dialog user and a HCL Workload Automation for Z server failed.

The server closes the TCP/IP connection. Contact between the HCL Workload Automation for Z dialog and the HCL Workload Automation for Z subsystem is lost. The partner of the TCP/IP connection is informed about the error.

Search the IBM Support database for a solution at Support.

EQQPH23E

NO DEFAULT CALENDAR IS SPECIFIED, IT IS REQUIRED WHEN PROTOCOL IS JSC

The default calendar name is required by the protocol.

The server initialization is terminated.

Make sure that the INIT statement is present in the server parameter library and that the CALENDAR keyword is specified.

EQQPH24E

REQUIRED PARAMETER PAR MISSING IN STMT STATEMENT

The required parameter is missing in the related statement of the server parameter file.

None.

Check the statement and correct the errors.

EQQPH25E

TME USER ID MISSING IN RACF CLASS TMEADMIN: USER

The server rejected the request for either of the following reasons:
  • The server table for the mapping of the Tivoli administrator and the RACF user ID does not exist.
  • The Tivoli administrator is not defined in the TMEADMIN mapping table.

None.

Check that the mapping table exists or that the Tivoli administrator is defined in the table. For detailed information about implementing security, see Customization and Tuning.

EQQPH26E

TME USER ID MISSING IN TME USER TO RACF USER ID MAPPING TABLE: USER

The user ID is not defined in the server table containing the mappings from TME® users to RACF users.

The server rejected the request.

Check the USERMAP parameter that identifies the mapping table in the SERVOPTS statement. Check the table entries and the user ID that are provided.

EQQPH27I

TYPE IS NOT SPECIFIED, DEFAULT TYPEDEFAULT IS CURRENTLY USED.

The TYPE parameter is missing. The default DEFAULT value is currently used.

The parameter TYPE is set to the DEFAULT value.

If you do not want to use the default value, enter a valid value for the parameter.

EQQPH28I

THE TCP/IP STACK IS AVAILABLE.

A HCL Workload Automation for Z server can communicate with TCP/IP.

The HCL Workload Automation for Z is continuing the process.

If you do not want to use the default value, enter a valid value for the parameter.

EQQPH29I

INVALID TYPE SPECIFIED, DEFAULT TYPE DEFAULT IS CURRENTLY USED.

An invalid value has been specified for the Type parameter. The Default value is currently used.

The parameter type is set to the default value.

If you do not want to use the default value, enter a valid value for the parameter.

EQQPH30E

COMMUNICATION TO FT WORKSTATIONS FAILED, THE SCHEDULER REQUIRES SERV AS END-TO-END SERVER. THE COMMUNICATION WITH FTWs CANNOT BE STARTED

The server cannot start the communication with fault-tolerant workstations, because the end-to-end server defined in the controller is another one.

The server does not start communication with fault-tolerant workstations and continues processing.

Change the end-to-end server parameter and restart the controller and the server

The end-to-end server parameters could be wrong.

EQQPH31E

COMMUNICATION TO FT WORKSTATIONS FAILED, SERVER CANNOT FIND THE CONTROLLER SSNM THE COMMUNICATION WITH FTWs CANNOT BE STARTED

The server cannot start communication with fault-tolerant workstations, because the specified controller is not found in the system.

The server does not start communication with fault-tolerant workstations and continues the processing.

Check the controller specified in the server parameters and restart the controller before starting the server.

The controller specified in the server parameters could be wrong or the controller is not active.

EQQPH32E

COMMUNICATION TO FT WORKSTATIONS FAILED, THE SERVER SHOULD ACT AS END-TO-END WITH THE SSNM CONTROLLER BUT THE TOPOLOGY PARAMETER IS MISING IN SERVOPTS STATEMENT

The server is not defined as an end-to-end server but is defined as the end-to-end server in the controller parameter.

The server does not start communication with fault-tolerant workstations and continues the processing.

If the server must be the end-to-end server, introduce the topology parameters in the server parameters, then restart the server.

The topology parameters are not defined in the server parameters.

EQQPH33I

THE END-TO-END PROCESSES HAVE BEEN STARTED

The server has successfully started the UNIX® processes required to communicate with fault-tolerant workstations.

The server continues processing.

None.

EQQPH34I

THE END-TO-END PROCESSES HAVE ENDED

The server has detected that the UNIX processes required to communicate with fault-tolerant workstations have ended as required.

The server continues to shut down.

None.

EQQPH35E

CANNOT START STARTER PROCESS: BPX1ATX FAILED WITH RC=RC, RSN=RSNC

The server has detected an error starting UNIX processes required to communicate with fault-tolerant workstations. The USS Assembler Callable Service BPX1ATX has failed with the specified return code RC and reason code RSNC.

The server does not start the UNIX processes and continues processing other server functions.

Check the return code (RC) and reason code (RSNC) in the UNIX System Services Messages and Codes manual to determine which error has caused the BPX1ATX to fail. In the scheduler parameters, check the value of the BINDIR keyword in the TOPOLOGY statement. This controls the access mode and extended attributes of the starter executable file on the HFS or ZFS file system.

EQQPH36E

COMMUNICATION TO FAULT TOLERANT WORKSTATIONS FAILED, NO TOPOLOGY PARAMETERS DEFINED TO CONTROLLER. THE COMMUNICATION WITH FAULT TOLERANT WORKSTATIONS CANNOT BE STARTED.

The server cannot start the communication with Fault Tolerant Workstations, because the topology parameters aren't defined in Controller.

The Server doesn’t start the communication with Fault Tolerant Workstations and continue the processing.

Add the topology parameters on Controller and restart Cntroller and Server.

The topology parameters couldn't be provided in the controller parameters member.

EQQPH37I

SERVER CAN RECEIVE REQUESTS

The server has acknowledged that the z/OS connector is up and running and that the TCP/IP communication is now open.

The server is now ready to process input.

None.

EQQPH40I

JSC HOSTNAME NOT SPECIFIED, THE IP ADDRESS VALUE IS TAKEN FROM TCP/IP CONFIGURATION.

See message text.

Processing continues.

Verify that your configuration is correctly set up.

EQQPH41E

APPC IS EITHER INACTIVE OR NOT READY.

The APPC started task is inactive or not ready.

The server task waits for the APPC started task to be reactivated; APPC connections toward the controller are impossible.

Make the APPC started task working properly.

EQQPH42E

NO TPLGYPRM IS SPECIFIED, IT IS REQUIRED WHEN PROTOCOL IS E2E

The TPLGYPRM parameter is required by end-to-end distributed environment.

The server initialization is terminated.

Make sure that the TPLGYPRM parameter is present in the server parameter library.

Enter a valid value for the parameter. TPLGYPRM is a member of parameter library.

EQQPH43E

COMMUNICATION REJECTED: THE CONNECTOR LEVEL IS TOO LOW. LEVEL REQUIRED IS VERSION.

There was an attempt to establish a communication between the Z connector and controller, but the Z connector version does not allow it. The minimum required version for the Z connector is 9.5.
The connection is not established.
Upgrade the Z connector to version 9.5 by upgrading the Dynamic Workload Console to version 9.5.

EQQPH44W

BOTH SERVOPTS AND TCPOPTS STATEMENTS ARE SPECIFIED FOR THE SERVER. JSCHOSTNAME AND PORTNUMBER VALUES IN SERVOPTS HAVE BEEN REPLACED.

You specified both the SERVOPTS and TCPOPTS server initialization statements. Both of them contain host name and connection timeout parameters.

HOSTNAME and SRVPORTNUMBER values in the TCPOPTS statement override JSCHOSTNAME and PORTNUMBER values in the SERVOPTS statement.

If the HOSTNAME and SRVPORTNUMBER values in the TCPOPTS statement are the ones that you expect, no action is required; anyway you can remove the unneeded SERVOPTS keywords. Otherwise, remove or correct the HOSTNAME and SRVPORTNUMBER parameter in the TCPOPTS statement.

EQQPH45E

AN ERROR OCCURRED IN TCP/IP CALL FUNC. RETURN CODE: RC ERRNO: ERRNO. DIAGNOSE TCP/IP MESSAGE FOLLOWS.

The server detected the error indicated by the message variables. When a connection attempt is going to be retried, this message is followed by EQQPH47W, to inform about the connection retry interval.

The server gets TCP/IP information and processes it to set EQQPH46I message variable.

To obtain additional information, look for EQQPH46I in the message log (EQQMLOG).

EQQPH46I

TCPIPMSG

This message contains additional information for a previous EQQPH45E message. If TCPIPMSG is TIMEOUT EXPIRED MONITORING A CONNECTION, the problem is due to a lack of network resources causing the network to slow down.

Processing continues.

Integrate this information with the previous EQQPH45E message information. In case of SSL error, the most common causes are listed in SSL errors.

EQQPH47W

THE SERVER COULD NOT INITIALIZE THE COMMUNICATION WITH TCP/IP. A NEW ATTEMPT WILL OCCUR EVERY 60 SECONDS.

This message is issued after EQQPH45E when the connection attempt is going to be retried.

The system waits approximately for 1 minute before attempting an automatic restart.

None.

EQQPH48E

THE CONNECTION TIMEOUT EXPIRED. THE CONNECTION WAS NOT ESTABLISHED WITHIN THE TIME SPECIFIED WITH THE CONNTIMEOUT PARAMETER.

This message is issued on the client when the connection cannot be established within the time specified in the CONNTIMEOUT parameter. This condition might occur because of one of the following reasons:the server has temporarily reached the maximum number of concurrent connection requests it can manage. Message EQQPH49W is also issued in the server MLOG.

The connection is rejected.

On the client, increase the value set for the CONNTIMEOUT parameter.

EQQPH49W

MAXIMUM NUMBER OF CONNECTIONS REACHED IN THE SERVER STARTED TASK.

This message is issued when the server cannot temporarily manage further TCP/IP connections from clients, because there is not enough storage available below the 16 MB line.

After this message is issued, the connection requested by the client can either remain queued until the server is able to establish it, or can be rejected because the time specified in the CONNTIMEOUT parameter is exceeded (in this case, message EQQX619E THE CONNECTION TIMEOUT EXPIRED, THE CONNECTION WAS NOT ESTABLISHED is issued).

This message is issued in the server MLOG the first time the maximum number of connections is reached. It will be reissued only when it again reaches the maximum number.

None.

EQQPH50I

THE SERVER IS WAITING FOR REQUESTS ON PROTOCOL NETWORK.

The server is ready to process network requests with the PROTOCOL protocol.

The processing continues.

None.

EQQPH51E

THE COMMUNICATION WAS UNEXPECTEDLY RESET BY THE PEER.

A problem occurred at the server side. Most common causes of this problem are:
  • The server was stopped.
  • The partner connection parameters are inconsistent.

The server closes the TCP/IP connection. Contact between the remote interface and subsystem is lost. The partner of the TCP/IP connection is informed about the error.

Check the status of the server and the connection parameters. Look for additional information in the peer EQQMLOG. If the problem persists, report the error to IBM Software Support.

EQQPH52I

A CONNECTION HAS BEEN ESTABLISHED TO THE SERVER AT NETWORK ADDRESS AND PORT HOST PORT.

A session was established between the remote partner and the server.

The processing continues.

EQQPH53E

THE COMMUNICATION TASK ENDED UNEXPECTEDLY.

The task used to establish connection between the interface and the server ended.

The task abnormally ends without a stop request.

Contact your system programmer. Search the IBM Support database for a solution at Support.

EQQPH55I

PARENT TASK STOPPED BEFORE THE CHILD COMMUNICATION TASK.

The task used to establish connection between the interface and the server ended after the parent task ended.

The task abnormally ends without a stop request.

Verify the shutdown process for the parent task. If you run a programming interface, verify that a TERM request is performed before closing the user program.

EQQPH56W

RAN MOMENTARILY OUT OF STORAGE. WAITING FOR RESOURCES TO BECOME AVAILABLE.

The server cannot at this moment manage further TCP/IP connections from clients, because sufficient storage is momentarily unavailable.

All the available memory resources are currently being used by the already established connections. As soon as enough memory is released, the requested connection will be established (unless in the meantime the time specified in the CONNTIMEOUT parameter is exceeded, then the connection is rejected and message EQQX619E THE CONNECTION TIMEOUT EXPIRED, THE CONNECTION WAS NOT ESTABLISHED will be issued).

None.

EQQPH57I

THE TCPIP COMMUNICATION SUBTASK BUILD DATE IS:YYYYMMDD.

Shows the build date of the TCPIP COMMUNICATION SUBTASK used to communicate with the remote user interfaces.

EQQPH59E

CHARACTER CURCHAR NOT VALID FOR STMT STATEMENT.

This error message is issued while a row of the USERMAP member in the parameter library is being parsed.
CURCHAR
Is the offending character.
STMT
Can be one of the following parameters: USER or USERMAP.

The server closes the TCP/IP connection.

Correct the offending USERMAP entry.

EQQPH60I

THE TCP/IP COMMUNICATION SUBTASK HAS STARTED.

The TCP/IP communication subtask has successfully completed initialization.

Processing of the TCP/IP communication subtask continues.

None.

EQQPH61I

THE TCP/IP COMMUNICATION SUBTASK HAS ENDED.

The TCP/IP communication subtask has ended either because the controller is in the process of shutting down or as a result of an operator MODIFY command to terminate this task or a related task.

HCL Workload Automation for Z processing continues.

None.

EQQPH62E

THE TCP/IP COMMUNICATION SUBTASK FAILED TO INITIALIZE THE C PROCESS.

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

Initialization of the TCP/IP communication subtask fails.

Try to restart the TCP/IP communication subtask with the MODIFY command. If the problem persists, contact IBM Software Support.

EQQPH63E

TOO MANY WILD CARDS USED IN STMT STATEMENT.

This error message is issued while a row of the USERMAP member in the parameter library is being parsed. STMT can be one of the following parameters: USER or USERMAP.

The server closes the TCP/IP connection.

Correct the offending USERMAP entry.

EQQPH64I

USER USER WAS MAPPED TO THE RACF RACUSR USER ID AND RACGRP RACF GROUP.

EQQPH65I

NO RACF USER ID MATCHES USER USER.

EQQPH66I

USER USER WAS MAPPED TO THE RACF RACUSR USER ID.

EQQPH67I

SERVER IS ACTIVATING SECURE SOCKETS LAYER (SSL) PROTOCOL FOR COMMUNICATAION.

Only SSL-type requests are accepted.

Use clients with SSL ON only.

EQQPH68E

TOO MANY CONNECTIONS OPEN IN THE SYSTEM.

The maximum number of possible concurrent connections was reached.

The involved user interface session is closed.

Increase the value of the MAXTHREADS system parameter in the BPXPRMxx system parameters member or wait for another connection to close.

EQQPH69E

INSUFFICIENT RESOURCES AVAILABLE, DIAGNOSTIC INFORMATION: message.

Details provided by message.

If the connection was up, it is closed.

Wait for resources to become available.

EQQPH70W

USER USER IS ASSOCIATED TO THE RACF PATTERN: PATTERN IN THE USER MAP. THE RESULTING VALUE IS TOO LONG. IT WILL BE TRUNCATED TO SHORTRAC.

The value for RACFUSER or RACFGROUP exceeds the 8-character limit after being matched with the wildcarded USER.

The value of is truncated to the 8-character limit.

None.

EQQPH74E

TME USER IS MISSING IN RACF CLASS EQQADMIN: USER.

The server failed to find the specified user in the RACF class EQQADMIN.
Processing continues.
Make sure that the definition of the resource class EQQADMIN is correct, in particular about the AUTOMAPPING setting. If needed, add USER to the class. For detailed information about implementing security, see Customization and Tuning.

EQQPS00E

PRE SUBMITTER TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE

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

The Pre Submitter task does not process the invalid element, but continues normal processing.

Save the scheduler Pre Submitter task message log and contact IBM Software Support.

Contact your system programmer.

EQQPS01I

PRE SUBMITTER TASK INITIALIZATION COMPLETE

The Pre Submitter task has successfully completed its initialization.

Pre Submitter task processing starts.

None.

EQQPS02E

PRE SUBMITTER TASK INITIALIZATION FAILED

The Pre Submitter task could not acquire all the resources needed for normal operation.

The Pre Submitter task does not start and all other active tasks close.

Correct the errors and restart the submit task.

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

EQQPS03E

PRE SUBMITTER TASK DQE SUBTYPE UNEXPECTED

The Pre Submitter task kept a DQE containing an invalid subtype.

The Pre Submitter task does not process the invalid element, but continues normal processing.

Save the scheduler Pre Submitter task message log. Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQPS04E

PRE SUBMITTER ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT DQE

An ABEND prevented the Pre Submitter task from processing a queue element.

Recovery/termination is requested to generate a dump. The Pre Submitter task attempts to continue normal processing.

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

Contact your system programmer.

Review the data store message log data set, the EQQDUMP data set, and the SYSMDUMP data set to determine the cause of the problem.

EQQPS05E

PRE SUBMITTER QUEUE POINTER IS DESTROYED. ARCQ IS LOST

The Pre Submitter task abended while processing elements on the ARCQ because queue chaining is invalid.

Recovery/termination is requested to generate a dump. The Pre Submitter task attempts to continue normal processing.

Save the MLOG, dump and BEX data sets. Search the IBM Support database for a solution at Support.

Contact your systems programmer.

Review the data store message log data set, the BEX diagnostic data set, and the dump data set to determine the cause of the problem.

EQQPS06E

PRE SUBMITTER JCL TAILORING FAILURE: MODULE MNAME RETURN CODE: RC - REASON CODE: RSC

An internal error occured during Pre Submitter task jcl tailoring in module MNAME.

The Pre Submitter task does not process the current JCL, but continues normal processing.

Save the scheduler Pre Submitter task message log. Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQPS07E

NO PRE SUBMITTER JCL TAILORING: JCL MEMBER IS IN USE FOR ADID: ADID IA: IA OPNUM: OPNUM

Pre Submitter task is unable to perform JCL tailoring action because jcl is currently in use by another task or user.

The Pre Submitter task does not process the current JCL, but continues normal processing.

Free the JCL resource and restart the process.

EQQPS08W

NO PRE SUBMITTER JCL TAILORING: JS VSAM JCL NOT FOUND FOR ADID: ADID IA: IA OPNUM: OPNUM

Pre Submitter task is unable to perform JCL tailoring action because the requested JCL is not present in JS VSAM data set.

If there are no other EQQPSxx error messages, the JCL is processed normally by using the JCL located in the PDS JOBLIB.

A user probably manually deleted JCL from JS VSAM data set using an online scheduler function.

EQQPS09E

NO PRE SUBMITTER JCL TAILORING: INSUFFICIENT STORAGE FOR ADID: ADID IA: IA OPNUM: OPNUM

Pre Submitter task is unable to perform JCL tailoring action because there is insufficient storage to perform operation.

The Pre Submitter task does not process the current JCL, but continues normal processing.

If the problem occurs often, try to solve it by enlarging the size of the scheduler main storage. Search the IBM Support database for a solution at Support.

Contact your System Programmer.

EQQPS10E

NO PRE SUBMITTER JCL TAILORING: JCL MEMBER NOT FOUND FOR: ADID: ADID IA: IA OPNUM: OPNUM

Pre Submitter task is unable to perform JCL tailoring action because the requested JCL is not present neither in JS VSAM data set and nor in PDS job library.

The Pre Submitter task does not process the current JCL, but continues normal processing.

A user probably manually deleted JCL from JS VSAM data set using an online scheduler function and from PDS JCL library.

EQQPS11E

THE JCL LIBRARY, DDNAME EQQJBLIB, COULD NOT BE OPENED

The Pre Submitter task could not open the JCL library.

The Pre Submitter task does not start and all other active tasks close.

Correct the errors and restart the submit task. If the problem persists save message log. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures. If the problem persists, search the IBM Support database for a solution at Support.

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

EQQPS12E

LOGICAL RECORD SIZE FOR THE JCL LIBRARY, DDNAME EQQJBLIB, IS INVALID

The Pre Submitter task could not open the JCL library because its record size is invalid. It must be 80.

The Pre Submitter task does not start and all other active tasks close.

Correct the errors and restart the submit task. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures. Search the IBM Support database for a solution at Support.

EQQPS13E

NO PRE SUBMITTER JCL TAILORING: SYSIN MERGE PROBLEMS FOR ADID: ADID IA: IA OPNUM: OPNUM RSNTXT

The operation identified by ADID, IA and OPNUM was not rerun because the needed expanded JCL could not be correctly restored merging the missing SYSIN DD * statement from JS JCL. The RSNTXT explains in detail the kind of problem occurred:
  • EXPANDED JCL MISSING
  • JS JCL SYSIN INFO MISSING
  • EXPANDED JCL SYSIN INFO MISSING
  • EXPANDED JCL AND JS JCL SYSIN MISMATCH
  • ERROR DURING MERGED JCL CREATION
  • ERROR DURING MERGE SYSIN PROCESS

HCL Workload Automation for Z set the operation in error with error code CLNA (error during apply logic processing).

Try to identify the origin of the problem from EQQMLOG and EQQDUMP messages. If the problem persists save message log. Search the IBM Support database for a solution at Support.

Except for number 2 and 4, the reasons indicate internal errors. Reason 4 indicates that a mismatch was found between the expanded JCL and the JCL got from JS VASM: a SYSIN DD found empty in the expanded JCL was not found at all in the JS JCL. One possible reason is that SYSIN were in external procedures. If possible, restart the operation from the dialog, setting the SYSIN manually.

Reason 2 indicates that the JS JCL was not found (maybe it has been deleted from JS). Try to restore it with edit command. For all other reasons contact system administrator.

EQQPT01I

PROGRAM PROG HAS BEEN STARTED, PID IS PID

The starter process has started the process PROG, the process ID is PID.

None.

None.

EQQPT02E

SPAWN ERROR STARTING PROG: ERRNO=ERR_NUM: ERR_MSG, REASON=RSN

An error has occurred during the spawn of the PROG process. The error is indicated by ERR_NUM (described by the ERR_MSG) with reason code RSN.

The system will retry later to start the PROG.

Verify and solve the error that is preventing the starter from spawning the process, then stop and restart the server.

EQQPT03I

STARTER PROCESS WAITING FOR STOP COMMAND

The starter process has started all the required processes and is now inactive until a stop command is received.

None.

None.

EQQPT04I

STARTER HAS DETECTED A STOP COMMAND

The starter process has detected a stop command issued to the server by the user.

The starter process now shuts down all its child processes.

None.

EQQPT05E

KILL ERROR KILLING TRANSLATOR PROCESS (PID=PID): ERRNO=ERR_NUM: ERR_MSG, REASON=RSN

An error occurred while the starter sent a signal to shutdown the translator process. pid is the process ID of the translator process. The error is ERR_NUM (described by the ERR_MSG) with reason code RSN.

The starter waits for the end of the translator process.

If the server does not shut down, cancel the server started task

EQQPT06I

THE SIG SIGNAL HAS BEEN SENT TO PROC PROCESS

The signal sig has been successfully sent to the process PROC.

None.

None.

EQQPT07I

STARTER IS WAITING FOR NUM SONS TO END

Starter is waiting for the end of NUM child processes before it exits

None.

None.

EQQPT08W

WAIT ERROR: ERRNO=ERR_NUM: ERR_MSG, REASON=RSN

An error as occurred while the starter waited for the end of a child process. The error is ERR_NUM (described by the ERR_MSG) with reason code RSN.

None.

None.

EQQPT09E

THE PROC PROCESS (pid=PID) ENDED ABNORMALLY

The PROC process with process id PID has ended abnormally.

None.

Check the TWS logs in WRKDIR/stdlist/logs directory. If a TWS process running in Unix System Services has ended abnormally, an error message should be printed to the log in this directory. See this message for additional information about the error. (WRKDIR is the HFS or ZFS directory specified in the TOPOLOGY WRKDIR parameter)

EQQPT10I

ALL STARTER'S SONS ENDED

The starter process stopped waiting for the end of its child processes.

The starter process exits.

None.

EQQPT11I

THE PROCESS WITH PID=PID HAS BEEN KILLED BY SIGNAL SIG

The process with PID PID has been killed by a signal SIG. Ignore this message if you are stopping the server.

The functions related to the killed process are disabled.

Stop and restart the server to reactivate the functions.

EQQPT12I

THE PROCESSNAME PROCESS ENDED SUCCESSFULLY

The process ended successfully.

Processing continues.

None.

EQQPT13E

TCPIP STACK (JOBNAME = JOBNAME) NOT FOUND. THE DEFAULT = TCPIP HAS BEEN TAKEN.

The TCP/IP stack with job JOBNAME has not been found.

The Server used as TCP/IP name the default (TCPIP), because it did not find the job name specified.

Check why the job JOBNAME started task was not available.

EQQPT14W

TCPIP STACK IS DOWN. A CONNECTION RETRY WILL BE ATTEMPTED IN 60 SECONDS.

The connection to TCP/IP failed because TCP/IP is not active.

The server end-to-end initialization is suspended. Attempting to connect to TCP/IP is repeated every 60 seconds. When the connection is established, the end-to-end initialization is automatically resumed and completed.

Start the TCP/IP stack.

EQQPT15I

The USS BINDIR BINDIR MAINTENANCE LEVEL IS APAR.

The PTF related to apar APAR is the latest maintenance applied on the HCL Workload Automation for Z USS bindir BINDIR.

HCL Workload Automation for Z continues its processing.

None.

EQQPT16E

THE PROC PROCESS ENDED ABNORMALLY TWICE. STARTER AND CHILD PROCESSES BEGINNING TO SHUT DOWN.

The netman or translator process running in Unix System Services (USS) ended abnormally twice within two hours. No more restarts will be attempted. All end-to-end server activities will be terminated.

To determine the cause of the problem, review the HCL Workload Automation for Z server message log, EQQDUMP diagnostic, and dump data sets.

Save the message log, diagnostic, and dump data sets, then search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQPT20I

INPUT TRANSLATOR HAS STARTED; WAITING FOR BATCHMAN AND MAILMAN TO START

The input translator thread has started; it waits until it reads an event indicating that mailman and batchman have started.

The input translator waits until it reads an event indicating that batchman has started.

If the message EQQPT21I is not displayed within a few minutes of EQQPT20I, check the HCL Workload Automation logs in WRKDIR/stdlist/logs directory to see what is preventing mailman and/or batchman from starting. (WRKDIR is the HFS or ZFS directory specified in the TOPOLOGY WRKDIR parameter).

EQQPT21I

INPUT TRANSLATOR HAS CONFIRMED THAT MAILMAN AND BATCHMAN HAVE STARTED

batchman has notified the input translator that batchman and mailman have started.

The input translator thread starts again and starts processing input events.

None.

EQQPT22I

INPUT TRANSLATOR THREAD STOPPED UNTIL NEW SYMPHONY WILL BE AVAILABLE

The input translator thread has stopped while it waits for a new Symphony to be produced from a Daily Planning or Renew Symphony batch job.

The input translator thread stops until the new Symphony is available.

If the Daily Planning or Refresh Symphony batch job is finished and the message EQQPT23I is not displayed in few minutes, check the MLOG job to see what is preventing the Daily Planning or Refresh Symphony from creating the Symphony.

EQQPT23I

INPUT TRANSLATOR THREAD IS RUNNING

A new Symphony has been installed and the input translator thread has started again.

The input translator thread starts again and starts processing input events.

None.

EQQPT24I

SYNCHRONIZATION BETWEEN SERVER AND CONTROLLER ENDED

The synchronization process completed.

The input translator thread communicates to the controller that the synchronization process is over. The thread stops until the new Symphony is available.

None.

EQQPT30I

STARTING SWITCHING SYMPHONY

The translator has received an event from the scheduler to stop the fault-tolerant workstations because of the creation of a new Symphony.

The translator starts the procedure to switch the Symphony file.

None.

EQQPT31I

SYMPHONY SUCCESSFULLY SWITCHED

The translator has installed the new symphony file produced by a Daily Planning or Renew Symphony batch job.

The translator restarts the processing of distributing the new Symphony file to the fault-tolerant workstations.

None.

EQQPT32E

AN INVALID STATUS TRANSITION REQUEST HAS BEEN RECEIVED

The translator has received an incorrect event containing an unsupported status transition for a job.

The event is discarded.

See the translator trace for more details about the invalid event.

EQQPT33E

MAILMAN OR BATCHMAN ENDED ABNORMALLY. TRANSLATOR BEGINNING TO SHUT DOWN.

An error occurred while running the mailman or batchman. The translator is stopped and the starter process tries to restart translator, mailman, and batchman.

Save the message log, diagnostic, and dump data sets, then search the IBM Support database for a solution at Support.

If the problems persists at the next restart, contact your system programmer.

Review the HCL Workload Automation for Z message log, EQQDUMP diagnostic, and dump data sets to determine the cause of the problem.

EQQPT34I

ACTION ACTION ON OBJECT OBJECT HAS BEEN CORRECTLY PERFORMED

The end-to-end server performed action ACTION on object OBJECT correctly.

Processing continues.

None.

EQQPT35E

UNABLE TO OPER OBJECT, REASON: RSN

An error has occurred performing the oper operation on the object. Rsn provides a description of the error cause.

The event is discarded. A misalignment between the scheduler Current Plan and the Symphony file is possible.

Run Renew Symphony batch job to re-establish the alignment between the scheduler Current plan and the symphony file.

EQQPT36W

UNABLE TO OPER OBJECT, REASON: RSN

An error has occurred performing the oper operation on the object. Rsn provides a description of the error cause.

The event is discarded. The Translator continues its processing without waiting for the change of the Symphony.

Correct the problem reported by reason RSN and do the operation again.

EQQPT37W

PROBLEMS TO OPEN/READ SYMPHONY AND/OR EVENTS FILES.

Translator cannot access the Symphony file or the event files and read network information to perform a progressive shutdown.

All the workstations attached to OPCMASTER will be stopped simultaneously.

None.

EQQPT38W

UNABLE TO GET THE SCRIPT FOR OPERATION OPNUM IN OCCURRENCE OCCNAME. REASON: RSN

Operation OPNUM in occurrence OCCNAME uses a centralized script. The Translator thread cannot get the script from the EQQTWSCS data set: Find the cause of the error in the RSN field.

The sender task tries again to send the script to the agent for a maximum of 10 attempts; then, the operation fails.

Fix the cause of the error.

EQQPT39I

STOPPING OBJECTS

The Output Translator process is stopping OBJECTS. The server is running the synchronization process with the controller during a daily planning activity.

OBJECTS are one of the following:
  • Mailman and batchman processes
  • Input Translator thread activities
  • All fault-tolerant workstations
  • All fault-tolerant workstations in the master domain

The end-to-end server continues processing.

None.

EQQPT40I

THD THREAD IS SHUTTING DOWN

The translator thread THD has detected a stop command and is exiting.

The thread closes all opened files and exits.

None.

EQQPT41I

AN EVENT FROM "SYSTEM" HAS BEEN PROCESSED

The translator has processed an event received from system.

The translator waits for the next event.

None.

EQQPT42I

A EVENTTYPE EVENT FROM "SYSTEM" HAS BEEN RECEIVED

The translator has received from system an event of type EVENTTYPE.

The translator processes the event.

None.

EQQPT43E

TRANSLATOR STARTED WITHOUT ENOUGH PARAMETERS SPECIFIED, EXITING ...

The translator has been started without the required parameters.

The translator process is terminated.

Check that the starter and translator programs have been installed correctly. The programs are probably misaligned.

EQQPT44I

NO EVENT AVAILABLE

The translator has not yet received any event from the scheduler.

The translator process waits for another event.

None.

EQQPT46E

ERROR CALLING FUNCTION : ERR_MSG

An error has been returned during function activity. The error is described by ERR_MSG.

The translator aborts the current operation.

Try to locate the previous error messages in the message log, and contact your system programmer.

EQQPT47E

Error ACTION "FILE" : ERR_MSG

An error has occurred while performing an action on a file. The ERR_MSG describes the cause of the error; the ERR_MSG information is not available when the action is COPYING.

The translator aborts the current operation.

Check the server logs on the USS for further messages explaining the error and contact your system programmer.

EQQPT48E

INVALID HEADER IN EVENT QUEUE DDNAME

The scheduler event queue indicates by DDNAME has a corrupted header.

The translator stops the operations until the scheduler queue is restored.

Restart the end-to-end task to rebuild the scheduler queue.

EQQPT49E

AN ERROR HAS OCCURRED READING HEADER RECORD

The translator was unable to read the header record of a scheduler queue. A previous error specifies which error has been encountered.

This message is embedded as a reason for another error.

Try to locate the previous error messages in the message log, and contact your system programmer.

EQQPT50I

WRITER OF MAILBOX FILE FILE HAS GONE

The process that was writing on message file FILE has stopped running and no events in FILE are processed.

The translator stops processing events from the file.

None.

EQQPT51E

CANNOT FIND THE FILE SYMPHONY FILE

The FILE Symphony file is not present.

The Symphony can not be switched.

Check why the file disappeared. You might need to run a Refresh Symphony batch job to re-create the Symphony file.

EQQPT52E

CANNOT SWITCH TO THE NEW SYMPHONY FILE: RUN NUMBERS OF SYMPHONY (SYMRN) AND CP (CPRN) AREN'T MATCHING

The new Symphony file that the translator has found does not have the same run number as the scheduler Current Plan.

The translator does not switch the Symphony file.

If the Symphony is not switched with the next event, run a Refresh Symphony batch job to re-create the Symphony file.

EQQPT53I

THD THREAD HAS TERMINATED

The THD thread has finished executing.

None.

None.

EQQPT54W

THE DDNAME QUEUE IS PERCENTAGE% FULL

The queue specified by DDNAME and used to exchange between controller and translator is full to the degree specified by PERCENTAGE.

None.

Allocate a bigger data set for the specified DDNAME and restart the controller and server.

EQQPT55E

THE DDNAME QUEUE IS 100% FULL

The queue specified by DDNAME and used to exchange between the controller and the translator is completely full.

The task or process that is writing in the specified data set is held until the data set is partially free.

Allocate a bigger data set for the specified DDNAME and restart the controller and the server.

EQQPT56W

THE DDNAME QUEUE HAS NOT BEEN FORMATTED YET

The queue specified by ddname and used to exchange events between the controller and the translator is not formatted yet.

The task or process that is writing in the specified data set is held until the data set is formatted.

Check that the controller is started and that it has completed its initialization without error. Verify that the DDNAME specified in the message refers to the same data set in both the controller and server JCL.

EQQPT59I

PROCESS PROCESS HAS GONE

The process PROCESS is no longer running.

The translator process is no longer receiving the events from the PROCESS process.

None.

EQQPT60E

AN END-TO-END PROCESS COULD END ABNORMALLY

This message is issued if the batchman process is not active. Batchman is started by mailman while mailman is started by netman. Generally it can indicate that one of these processes ended abnormally.

Anyway a slow initialization of mailman can cause the EQQPT60E to be issued even if no process has ended abnormally. Mailman is initialized at server start and when switching a new symphony file; possible causes of the slowness can be unreachable workstations or, when switching the new symphony file, lots of unprocessed events present in the message files.

None.

Check if mailman is initializing correctly in the TWSMERGE log in WRKDIR/stdlist/logs directory and in this case wait for mailman to complete its initialization; note that the initialization starts with message AWSBCV086I and ends with message "AWSBCV108I Started Batchman, pin xxx". Otherwise check the logs in WRKDIR/stdlist/logs directory for additional error messages; verify if a dump is available, otherwise take a console dump of the server address space; collect the entire workdir and contact the IBM Software Support. Try to recover from the error by shutting down and restarting the E2E server.

EQQPT61E

INVALID DATE AND TIME FOUND IN A TWS EVENT (OPERATION NUMBER: OPNUM - OCCURRENCE TOKEN: TOKEN). CURRENT DATE AND TIME ARE USED.

The date and time contained in an event coming from an FT workstation were invalid.

The date and time in the event are ignored; the current date and time are used instead. For example, if the event was tracking the start of an operation, the current date and time will be used for the job start date and time, instead of the invalid values in the event.

Search the IBM Support database for a solution at Support.

EQQPT62W

THE BATCHMAN AND MAILMAN PROCESSES ARE STILL ACTIVE. STARTING WAITING FOR THEIR STOP.

Before switching the symphony file, the batchman and mailman processes required to be stopped.

During the switch of the Symphony file, if the batchman and mailman processes are not stopped yet, the Output Translator tries to stop it for 10 minutes. If within this time the processes are still active, the error message EQQPT63E is displayed in the Server MLOG. If the processes instead, will be stopped within 10 minutes, the Output Translator continues its normal process and the Symphony file is correctly switched. In this case, the message EQQPT31I is shown in the Server MLOG.

Check for further messages.

EQQPT63E

AN ERROR OCCURRED WHILE STOPPING THE BATCHMAN AND MAILMAN PROCESSES. THE SYMPHONY FILE CANNOT BE SWITCHED.

During the switch of the symphony file, the batchman and mailman processes have not been stopped.

During the switch of the Symphony file, the Output Translator unsuccessfully tried to stop the batchman and mailman processes for 10 minutes. As a consequence, the symphony file is not switched.

Search the IBM Support database for a solution at Support.

EQQPT64I

STOP COMMAND SENT TO FAULT TOLERANT WORKSTATION CPU

The output translator sent a STOP command to the fault-tolerant workstation CPU. The workstation is stopped only if it can be reached in the network. The message is not shown for an extended agent workstation.

Processing continues.

None.

EQQPT65I

STOP COMMAND SENT TO OPCMASTER

The output translator sent a STOP command to the OPCMASTER. Mailman and batchman are stopped in the server.

Processing continues.

None.

EQQPT66I

VALUE CONTAINED IN THE SERVER CHECKPOINT FILE: KEYWORD = VALUE

This message is issued at Translator startup and every time the KEYWORD value is modified. It shows the current value of the KEYWORD contained in the server checkpoint file. The data contained in the server checkpoint file Translator.chk represents the actual server status.

KEYWORD can be one of the following:
FirstValidSymRun
The first valid symphony run number used by the server
CPAvailable
The copy of the active current plan (SCP) available or not available
SymAvailable
A new Symphony available to the server
SymRunNumber
The current Symphony run number
CPRunNumber
The Symphony run number related to the active current plan
SpecialSynchStart
A special synchronization in progress
StopCpusPostponed
Stopping the CPUs must be postponed after symphony creation

Processing continues.

None.

EQQPT67E

A DUMP WAS TAKEN FOR PROBLEM DETERMINATION PURPOSES

An I/O error occurred while accessing a file. The system performed a dump to assist in determining the problem.

Processing continues.

If the problem persists, search the IBM Support database for a solution at Support.

EQQPT68E

PUTENV() ENVVAR FAILED ERRNO=ERRNO: ERRMSG, REASON=RSC

While running the call PUTENV, an error occurred when a new environment variable was being added or the value of an existing one was being changed. ENVVAR contains the string used in the PUTENV call. The error is indicated by ERRNO (described by ERRMSG), with reason code RSC.

The program runs without this environment setting.

Check the error code explanation in the HCL Workload Automation for Z publications to determine the cause of the problem and resolve it accordingly. If the error persists, save the message log EQQMLOG and contact IBM Software Support for assistance.

EQQPT69I

SENDING STOP COMMAND TO FAULT-TOLERANT WORKSTATION CPU

The output translator is stopping the fault-tolerant workstation CPU. This message is not shown for an extended agent workstation.

Processing continues.

None.

EQQPT70I

THE STOP COMMAND WAS SENT TO ALL THE OBJECTS

The output translator sent a STOP command to all the OBJECTS, which can be one of the following:
  • Fault-tolerant workstations
  • Fault-tolerant workstations in the master domain
The fault-tolerant workstations are stopped only if they can be reached in the network.

Processing continues.

None.

EQQPT71I

WAITING OBJECT

The server is waiting for OBJECT during a daily planning activity. OBJECT can be either one of the following strings:
  • for a new Symphony file
  • until the current plan starts executing again

The end-to-end server waits for OBJECT.

None.

EQQPT72I

THE CURRENT PLAN IS RUNNING AGAIN

During a DP extend, DP replan, or Symphony renew the CP VSAM data set is available and execution is active again. If an SCP was also created, it is available to the planning batch job. (SCP is a copy of the CP created by the planning batch job, which uses it to add information to the Symphony file).

Processing continues.

None.

EQQPT73I

THE SYMNEW FILE WAS CREATED (RUN NUMBER IS RUNNO)

A planning batch job (DP extend, DP replan, or Symphony renew) created a new Symphony file (Sinfonia) which is ready to be processed by the server.

The output translator copies Symnew into Symphony and Sinfonia. Sinfonia is distributed to the network, while Symphony is available on z/OS for production.

None.

EQQPT74I

STARTING ACTIVITY

When the new Symphony file (Synfonia) is ready to be processed, the server (output translator) starts some activities to switch the Symphony file. ACTIVITY can be either one of the following strings:
  • Mailman and batchman processes
  • Input translator activities

The server proceeds to switch the Symphony file.

None.

EQQPT75I

SYNCHRONIZATION BETWEEN SERVER AND CONTROLLER STARTED

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

The translator starts all the actions required for synchronization.

None.

EQQPT76W

CANNOT ACTION OBJECT BECAUSE SYMPHONY IS NOT YET UPDATED; WAITING AND RETRYING.

The end-to-end server is trying to release or to delete dependency OBJECT but it cannot perform the action because the job or the dependency has not been added to the Symphony file yet. This message appears if the Symphony file has not been updated after one minute.

The server will try to release or delete the dependency again for a maximum of 5 minutes. If after this period the Symphony file is not updated with the object to be released or deleted, the action fails and message EQQPT35E is issued. Otherwise, message EQQPT34I is issued indicating that the action was performed successfully.

Check the TWSMERGE file in the stdlist/logs directory of the USS work directory to verify if the mailman and batchman processes are working correctly.

EQQPT77E

THE STAT() FAILED ACCESSING FILENAME. ERRNO=ERRNO: ERRMSG.

An error occurred during the running of the stat call accessing the information about the file or directory specified. Filename is the file accessed by the stat call. The error is indicated by the errno and described by the errmsg.

The request is rejected.

Check the error code to determine the cause of the problem and resolve it accordingly. If the error persists, contact IBM Software Support:
EACCESS
The process does not have permission to access some components of the path containing the files specified.
ENOTDIR
A component of the path containing the file specified is not a directory.

EQQPT95I

SYNCHRONIZATION BETWEEN SERVER AND CONTROLLER ENDED

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

Processing continues.

None.

EQQP010E

VERB in state STATE failed with RC RC, SR SR, DR DR

An APPC service request issued for server communication failed. The verb VERB was issued when the conversation was in state STATE. APPC returned: Return_Code RC, Status_Received SR and Data_Received DR.

The request is rejected.

Check the meaning of the APPC return codes. Check the message log of the server for a message explaining the communication loss. If the problem recurs, report the error to IBM Software Support.

Check that the correct LU name is specified. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z Primary Option panel or rerun the program interface application.

EQQP011E

INSUFFICIENT VIRTUAL STORAGE, DIAGNOSTIC INFO ALT

A routine for communication with the server failed because it could not obtain sufficient amount of virtual storage.

The request is rejected.

Logon to TSO with a larger SIZE parameter value or rerun the program interface application with a larger specified region

EQQP012E

APPC/MVS VERB VERB FAILED WITH RC RC, SR SR, DR DR

An APPC service request issued for server communication failed. The verb VERB was issued when the conversation was in state STATE. APPC returned: Return_Code RC, Status_Received SR and Data_Received DR.

The request is rejected.

Check the meaning of the APPC return codes. Check the message log of the server for a message explaining the communication loss. If the problem recurs, report the error to IBM Software Support.

Check that the correct LU name is specified. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z Primary Option panel or rerun the program interface application.

EQQP014E

REQUEST FAILED, SEVERE ERROR AT THE SERVER, LU

An error occurred at the server.

The dialog or program interface application cannot continue.

Check the message log of the server for a message explaining the error at the server.

Check the message log of the server for a message explaining the communication problem. If the problem recurs, report the error to IBM Software Support.

Check that the correct LU name is specified. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z Primary Option panel or rerun the program interface application.

EQQP015E

FAILED TO SET UP COMMUNICATION WITH SERVER LU, RC RC

An APPC allocate request issued for server communication failed. LU shows the LU name of the server. RC shows the return code of the allocate request.

The user cannot start the HCL Workload Automation for Z dialog. The INIT request of program interface application gets a return code of 8.

Check that the correct LU name is specified and that LU is active. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z Primary Option panel or rerun the program interface application.

EQQP109E

FREEING A TIE THAT IS ALREADY FREE

During the scheduling activity or because of a manual action on an operation, a tie block is being freed for the second time.

Processing goes on until the double freed tie block is used for the second time by means of a cpool GET. Then an abend S0C4 can occur.

Run a Dp batch re-plan or extend and contact IBM customer support.