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.

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

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

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

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.

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

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

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

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.

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 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 TCP/IP connection between a dialog user and a HCL Workload Automation for Z server failed. A TCP/IP socket service call failed.

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 TCP/IP connection between a dialog user and a HCL Workload Automation for Z server failed. A TCP/IP socket service call failed.

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

An incorrect TYPE parameter value has been specified.

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

The default calendar name is required by the protocol.

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

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

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

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

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

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 cannot start communication with fault-tolerant workstations, because the specified controller is not found in the system.

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 has successfully started the UNIX® processes required to communicate with fault-tolerant workstations.

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

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 cannot start the communication with Fault Tolerant Workstations, because the topology parameters aren't defined in Controller.

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

See message text.

The APPC started task is inactive or not ready.

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

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

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.

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.

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

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.

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.

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

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

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

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

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

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

The TCP/IP communication subtask has successfully completed initialization.

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.

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.

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 maximum number of possible concurrent connections was reached.

Details provided by message.

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

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

The Pre Submitter task has successfully completed its initialization.

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

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

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

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

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

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

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

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

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 could not open the JCL library.

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

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

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 starter process has started all the required processes and is now inactive until a stop command is received.

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

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 signal sig has been successfully sent to the process PROC.

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

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.

The PROC process with process id PID has ended abnormally.

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

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

The process ended successfully.

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

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

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

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.

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

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

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.

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

The synchronization process completed.

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 has installed the new symphony file produced by a Daily Planning or Renew Symphony batch job.

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

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

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

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

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

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

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 Output Translator process is stopping OBJECTS. The server is running the synchronization process with the controller during a daily planning activity.

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

The translator has processed an event received from system.

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

The translator has been started without the required parameters.

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

An error has been returned during function activity. The error is described by 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 scheduler event queue indicates by DDNAME has a corrupted header.

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

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

The FILE Symphony file is not present.

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

The THD thread has finished executing.

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

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

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

The process PROCESS is no longer running.

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.

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

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

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

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.

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

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.

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

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 output translator is stopping the fault-tolerant workstation CPU. This message is not shown for an extended agent workstation.

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

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 controller started the synchronization process with the server during a daily planning activity.

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.

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 controller ended the synchronization process with the server during a daily planning activity.

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.

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

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.

An error occurred at the server.

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.

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