EQQHT01 - EQQHT83

EQQHT01I

THE HTTP CLIENT COMMUNICATION TASK HAS STARTED.

The HTTP client communication task has successfully completed initialization.

The HTTP client communication task processing continues.

None.

EQQHT02I

THE HTTP CLIENT COMMUNICATION TASK HAS ENDED.

The HTTP client communication task 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.

EQQHT03E

THE HTTP CLIENT COMMUNICATION TASK 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.

The HTTP client task initialization fails.

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

EQQHT04E

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

No HTTP or HTTPS destinations were defined in the ROUTOPTS statement.

The HTTP client task initialization fails.

None.

EQQHT05E

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

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

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

Save the HCL Workload Automation for Z message log and contact IBM Software Support.

Contact your system programmer.

EQQHT06E

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

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

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

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

Review the HCL Workload Automation for Z message log data set and the SYSMDUMP data set, to determine the cause of the problem.

EQQHT07E

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

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

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

Contact your system programmer.

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

Review the HCL Workload Automation for Z message log data set and the SYSMDUMP data set, to determine the cause of the problem.

EQQHT08I

THE MODIFY COMMAND CMD CANNOT BE PROCESSED BECAUSE THE HTTP COMMUNICATION TASK IS NOT RUNNING.

See message text.

None.

Enter the command again when the HTTP communication task is running.

EQQHT09E

ERROR PARSING JOB JOB_NAME. THE KEYWORDS IN THE JOBREC STATEMENTS ARE NOT SUPPORTED BY THE AGENT LEVEL OF WORKSTATION WORKSTATION_NAME.

See message.

The job ends in error.

To run job job_name, update the agent to the latest fix pack level.

EQQHT11I

THE HTTP SERVER COMMUNICATION TASK HAS STARTED.

The HTTP server communication task has successfully completed initialization.

The HTTP server communication task processing continues.

None.

EQQHT12I

THE HTTP SERVER COMMUNICATION TASK HAS ENDED.

The HTTP server communication task 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.

EQQHT13E

THE HTTP SERVER COMMUNICATION TASK 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.

The HTTP server task initialization fails.

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

EQQHT14E

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

No HTTP or HTTPS destinations were defined in the ROUTOPTS statement.

The HTTP server task initialization fails.

None.

EQQHT15E

THE HTTP CLIENT FAILED TO PROCESS A REQUEST FOR DESTINATION DEST.

An error occurred while communicating through HTTP with the DEST destination. This message is followed by message EQQHT43I, which indicates the details of the error.

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

Look at the error detail and try to fix the problem.

EQQHT16W

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

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

The HTTP client task uses the default name TCPIP.

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

EQQHT17W

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

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

The HTTP server task uses the default name TCPIP.

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

EQQHT18I

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

See message text.

None.

EQQHT19I

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

See message text.

None.

EQQHT20E

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

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

The HTTP server issues message EQQHT11E and is terminated.

If necessary, restart the HTTP server.

Ensure that the ddname EQQHTTP0 is correctly specified and that the HCL Workload Automation for Z started task is authorized to open the data set for update.

EQQHT21E

THE HTTP SERVER OUTPUT DATA SET IS TOO SMALL.

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 EQQHTTP0 does not fulfill this requirement.

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

Allocate a larger event data set. If necessary, restart HCL Workload Automation for Z to pick up the new event data set.

EQQHT22I

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

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.

The HTTP server continues normal processing.

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

EQQHT23E

UNABLE TO KILL JOB JOBNAME ON WORKSTATION WSNAME.

The HTTP client task cannot send the KILL command for the job JOBNAME. For details about the reason why the operation has failed, see messages EQQHT15E and EQQHT43I. The most common reason is that the workstation is offline.

The HTTP client continues normal processing.

Verify the reasons why the operation has failed, and retry to issue the command after the error has been resolved.

EQQHT24E

JOB JOBNAME ON WORKSTATION WSNAME WAS NOT KILLED. THE REASON IS: RSNCODE ON

An error occurred while an agent was running a KILL command for the job JOBNAME on workstation WSNAME. The reason code is RSNCODE.

None.

Check the reason code to verify why the command failed.

EQQHT25E

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

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.

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.

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.

EQQHT26E

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

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.

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.

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.

EQQHT27E

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

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

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

Correct the problem, basing on the ERRNO.

EQQHT28E

THE AGENT FAILED TO SUBMIT THE JOB WITH OPERATION NUMBER: OPNUM OCCURRENCE TOKEN: OCCTOKEN.

The agent failed to submit a job on a z/OS remote engine. Message EQQHT43I follows this message and provides the details of the error.

Processing continues.

See the information provided by message EQQHT43I.

EQQHT29E

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

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.

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

Correct the problem, basing on the SSL_ERR description.

EQQHT30E

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

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.

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

Correct the problem, basing on the ERRNO description.

EQQHT31E

THE HTTP SERVER FAILED TO MANAGE A REQUEST.

The HTTP server failed to manage an HTTP request. The request can be either a status change notification or a bind request.

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

None.

EQQHT32E

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

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

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

None.

EQQHT33E

THE HTTP SERVER RECEIVED THE UNSUPPORTED REQUEST REQUEST.

The HTTP server received from an external client an unsupported request.

The unsupported request is discarded. The HTTP server continues processing.

None.

EQQHT34E

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

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

The action requesting the storage fails.

Collect the appropriate documentation and contact the Customer Support. A minimum set of documentation is a console dump of the controller address space, the message log, and, if present, the trace log. A possible recovery action is to restart the controller.

EQQHT35E

ERROR PARSING JOB JOBNAME. PASSWORD NOT FOUND FOR USER USER ON WORK STATION WSNAME.

In job JOBNAME the JOBPWD keyword is set to YES, meaning that the password of user USER on workstation WSNAME is specified in the USRREC statement. The parse has failed because the password is not present.

Parsing fails and the job is set in Error status.

Correct the problem by editing the JCL for the job and setting JOBPWD to NO, or add the USRREC statement for the user USER on workstation WSNAME. Then rerun the job.

EQQHT36E

ERROR PARSING JOB JOBNAME. LINE LINE.

The HTTP client is parsing job JOBNAME before submitting it, and an error has occurred while parsing line LINE.

Parsing fails and the job is set in Error status.

Correct the problem by editing the JCL for the job. Run the job again.

EQQHT37E

ERROR PARSING JOB JOBNAME. INCORRECT VALUE FOR KEYWORD KEYW.

The HTTP client is parsing job JOBNAME before submitting it, and an error has occurred during parsing. The value specified for the keyword KEYW is incorrect.

Parsing fails and the job is set in Error status.

Correct the problem by editing the JCL for the job. Run the job again.

EQQHT38E

ERROR PARSING JOB JOBNAME. UNBALANCED JOBREC STATEMENT.

The HTTP client is parsing job JOBNAME before submitting it and an error has occurred during parsing. Typical errors that can cause this message to be issued are:

//JOBREC line is present but //END JOBREC line is missing
//END JOBREC line is present but //JOBREC line is missing
//JOBREC line is duplicated

Parsing fails and the job is set in Error status.

Correct the problem by editing the JCL for the job. Run the job again.

EQQHT39E

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

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.

The request for the conversion fails.

Contact the Customer Support.

EQQHT40E

EVENT DATASET ERROR: HTTP SERVER COMMUNICATION TASK HAS ENDED.

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

The HTTP server task initialization fails.

None.

EQQHT43I

MSG_TEXT

This message contains additional details for other messages (EQQHT15E, EQQHT28E, EQQHT44E, EQQHT70W and EQQOC24W).

Processing continues.

Integrate this information with the related message information.

EQQHT44E

THE AGENT FAILED TO SUBMIT THE JOB JOBNAME ON WORKSTATION WSNAME. OPERATION NUMBER: OPNUM OCCURRENCE TOKEN: TOKEN.

The agent failed to submit the job. Message EQQHT43I follows this message and indicates the details of the error.

Processing continues.

Integrate this information with the related EQQHT43I message information.

EQQHT45E

THE HTTP SERVER RECEIVED A REQUEST WITH AN INCORRECT VALUE FOR THE PARM PARAMETER.

The HTTP server received an incorrect HTTP request. The request can be either a status change notification or a bind request. The error concerns the internal parameter PARM, which has an incorrect value.

The request is rejected.

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.

EQQHT46E

THE HTTP SERVER RECEIVED A REQUEST WITH NO VALUE SPECIFIED FOR THE PARM PARAMETER.

The HTTP server received an incorrect HTTP request. The request can be either a status change notification or a bind request. The error concerns the internal parameter PARM, which is missing.

The request is rejected.

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.

EQQHT47E

NOR THE SCRIPT NEITHER THE COMMAND WAS SET FOR THE JOB JOBNAME .

The HTTP server has tried to submit the job JOBNAME, which had nor a script neither a command set.

No job is submitted.

Ensure that the definition of the job is correct.

EQQHT48E

ERROR PARSING JOB JOBNAME. KEYWORD KEYW NOT FOUND.

The HTTP client is parsing job JOBNAME before submitting it, and an error has occurred during parsing. The required keyword KEYW is not specified.

Parsing fails and the job is set in Error status.

Correct the problem by editing the JCL for the job. Run the job again.

EQQHT49I

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

See message text.

None.

EQQHT50W

THE HTTP DESTINATION LIST IS BEING REFRESHED. WAIT FOR IT TO COMPLETE AND ENTER THE COMMAND AGAIN.

The command to refresh the destinations or display the list of destinations in use cannot be run, because another command to refresh the destinations is being processed.

The latest command you entered to refresh the destinations or display the list of destinations in use is not processed.

Wait for the refresh command to complete, then enter the command again.

EQQHT51I

THE HTTP DESTINATION LIST HAS CHANGED.

See message text.

None.

EQQHT52I

THE DESTINATION DEST WAS ADDED.

See message text.

None.

EQQHT53W

TOO MANY DESTINATIONS WERE ADDED. SOME DESTINATIONS WILL BE IGNORED.

The destinations that were totally added are more than 100, which is the maximum allowed. Some destinations are not added.

Some destinations are not added, because they exceed the maximum allowed.

Stop and restart the controller, to have the MODIFY command manage other 100 new destinations.

EQQHT54I

THE DESTINATION DEST WAS DELETED.

See message text.

None.

EQQHT55I

NO CHANGE WAS MADE TO THE DESTINATION LIST. THE REFRESH COMMAND HAS NO EFFECT.

See message text.

None.

EQQHT56I

THE DESTINATION DEST WAS CHANGED.

See message text.

None.

EQQHT57I

START OF HTTP DESTINATION LIST.

See message text.

None.

EQQHT58I

END OF HTTP DESTINATION LIST.

See message text.

None.

EQQHT59I

PROTOC DESTINATION DEST, HOST:PORT[/REMENGTYPE], PROXY: PRXYHOST:PRXYPORT.

This message shows the current HTTP or HTTPS destinations in use, identified by:

PROTOC: The type of communication protocol used, either HTTP or HTTPS.
DEST: The destination name, as defined in the ROUTOPTS statement.
HOST: The fully qualified host name or IP address used to communicate with the agent.
PORT: The port number used to communicate with the agent.
REMENGTYPE: The type of remote engine, either D for a distributed remote engine, or Z for a z/OS remote engine. This value is shown only if the destination is used to communicate with a remote engine workstation.
PRXYHOST: The fully qualified host name or IP address of the proxy used to communicate with the agent.
PRXYPORT: The port number of the proxy used to communicate with the agent.

None.

EQQHT60I

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

See message text.

None.

EQQHT62E

A BIND REQUEST WITHOUT ANY KNOWN NOTIFICATION ADDRESS WAS RECEIVED. THE REQUEST WAS DISCARDED.

The controller has received a bind request, but the notification addresses are not defined as HTTP destinations in the EQQPARM library. See previous EQQHT66 messages for details about the unknown notification addresses.

The bind request is discarded.

If you want the request to be received, add the destination to the ROUTOPTS statement.

EQQHT63W

A REFRESH COMMAND FOR DESTINATION DEST CHANGED THE DESTINATION TYPE.

See message text.

None.

EQQHT64W

A REQUEST WITH A NOT SUPPORTED APPLICATION NAME WAS RECEIVED. THE REQUEST IS DISCARDED.

The request received has a not supported value in the application name field. The correct value to specify for a z/OS shadow job is zShadowJob.

The request is ignored.

Inform the remote engine Tivoli Workload Scheduler administrator.

EQQHT65E

DESTINATION DESTNAME REJECTED A BIND REQUEST BECAUSE THE PROTOC NOTIFICATION ADDRESS LHOSTN:SPORT IS UNKNOWN.

The controller has sent a bind request to a remote engine with destination DESTNAME, but in the EQQPARM library of the remote engine there is not any PROTOC destination that defines the controller notification address LHOSTN:SPORT. For this reason, the remote controller rejected the bind request.

The shadow job is put in error with SHPF error code.

Contact the remote engine administrator to add to the ROUTOPTS statement a z/OS remote engine PROTOC destination with the specified address.

EQQHT66W

THE PROTOC NOTIFICATION ADDRESS HOSTN:PORT IS UNKNOWN.

The controller has received a bind request, but the notification address is not defined as an HTTP destination in the EQQPARM library.

If all the notification addresses are unknown, the request is discarded and message EQQHT62 is logged. The message is issued for all the unknown notification addresses of the request.

If only some of the notification addresses are unknown, the system processes the request by using the notification addresses that are defined as HTTP destinations in the EQQPARM library. The message EQQHT66W is issued only once; so, if the controller receives another request with the same unknown notification addresses, the message is not issued again. This condition is reset with the refresh destination command.

If you do not want the notification address to be ignored, add the destination to the ROUTOPTS statement.

EQQHT67E

ERROR OPENING DDNAME DATASET: ERRNO =ERRNUM, ERRMSG, REASON=REASON.

An error has occurred while opening the DDNAME data set. The fopen() function error is indicated by ERRNUM (described by ERRMSG) with reason code REASON .

If the error cannot be bypassed, the output collector or the controller ends with errors.

Verify and solve the error that is preventing the output collector or the controller from opening the data set, then restart it.

EQQHT68E

ERROR READING DDNAME DATASET: ERRNO =ERRNUM, ERRMSG, REASON=REASON.

An error has occurred while reading the DDNAME data set. The fread() function error is indicated by ERRNUM (described by ERRMSG) with reason code REASON .

If the error cannot be bypassed, the output collector or the controller ends with errors.

Verify and solve the error that is preventing the output collector or the controller from reading the data set, then restart it.

EQQHT69E

ERROR ALLOCATING DDNAME DATASET: ERROR CODE=ERRNUM, INFORMATION CODE=REASON.

An error has occurred while allocating the DDNAME data set dynamically. ERRNUM and REASON are the error code and information code returned by the dynalloc() dynamic allocation function.

If the error cannot be bypassed, the output collector or the controller ends with errors.

Verify and solve the error that is preventing the output collector or the controller from allocating the data set, then restart it.

EQQHT70W

ERROR PROCESSING JOB LOG HEADER (OCCURRENCE TOKEN: OCCTOKEN, OPNO: OPNUM).

The controller cannot substitute the variables specified in the job log header for the job with occurrence token OCCTOKEN and operation number OPNUM. This message is followed by message EQQHT43I, which provide details for this error.

The controller does not add the header to the job log.

Review the output collector message log to determine the cause of the problem. Check that the level of the agent and, if appropriate, of the dynamic domain manager associated to the job log request is 8.6.0.1 or higher. If the problem persists, search the IBM Support database for a solution at Support.

EQQHT71E

UNABLE TO USE THE JOB LOG HEADER.

The controller cannot use the job log header in the parameter library that you specified in the HTTPOPTS JLOGHDRTEMPL parameter.

The controller continues processing but it does not add the header to the job log when requested from one of the product interfaces.

Review the message log of the controller to determine the cause of the problem. After you solve the problem, restart the controller. If the problem persists, contact the IBM Support.

EQQHT72I

THE HTTP DESTINATIONS LIST IS EMPTY.

ROUTOPTS does not contain any HTTP destinations at this moment.

Processing continues.

None.

EQQHT74E

ERROR: FAILED TO OPEN TICKET FOR JOB JOBNAME(JOBNUM)

The Controller failed to open an incident report for job JOBNAME JOBNUM.

Processing continues.

Verify if the URI specified in the TKTURI keyword of the OSLCOPTS statement is available.

EQQHT75E

ERROR: FAILED TO OPEN TICKET FOR JOB JOBNAME(JOBNUM) BECAUSE THE AUTHENTICATION HAS FAILED.

The Controller failed to open an incident report for job JOBNAME JOBNUM because the authentication data provided were not correct.

Processing continues.

Enter a valid user ID and password.

EQQHT76E

PROXY DESTINATION PROXY_NAME IS SPECIFIED IN THE HTTP OR HTTPS PARAMETER OF ROUTOPTS BUT PROXY_NAME IS NOT SET IN THE PROXY PARAMETER OF ROUTOPTS.

In the ROUTOPTS statement, the PROXY_NAME is set in the HTTP or HTTPS parameter but not in the PROXY parameter.

The HTTP client is stopped.

Set the PROXY_NAME in the PROXY parameter of ROUTOPTS, then stop and restart the controller.

EQQHT77E

THE SAME NAME DEST IS SET IN MORE THAN ONE KEYWORD PROXY IN THE ROUTOPTS STATEMENT.

A proxy name must be unique within the HCL Workload Automation for Z configuration.

HCL Workload Automation for Z initialization is terminated.

Correct the proxy name in the ROUTOPTS statement.

EQQHT78E

BOTH PROXY KEYWORDS DEST AND DEST2 IN THE ROUTOPTS STATEMENT CONTAIN THE PORT PORT AND IP ADDRESS IP_ADDR.

The list of PROXY destinations contain more than one destination with the same IP address and port number. This definition is unnecessary.

HCL Workload Automation for Z initialization is terminated.

Correct the ROUTOPTS statement by deleting the superfluous PROXY destination.

EQQHT79W

TOO MANY PROXY DESTINATIONS WERE DEFINED. SOME DESTINATIONS WILL BE IGNORED.

The PROXY destinations that were totally defined are more than 100, which is the maximum allowed. Some destinations are ignored.

Some proxy destinations are ignored, because they exceed the maximum allowed.

Modify the PROXY parameter in ROUTOPTS so that the total number of proxy destinations defined does not exceed 100, then stop and restart the controller.