EQQOC02 - EQQOC31

EQQOC02E

AN OUTPUT COLLECTOR WITH THIS NAME IS ALREADY ACTIVE, IT CANNOT START AGAIN.

You submitted an operator START command for an output collector that is already active.

The second attempt to invoke the output collector is terminated.

If you want to restart the output collector, stop it and submit the START command again.

EQQOC05E

THE OUTPUT COLLECTOR CLIENT 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 output collector client task initialization fails.

Try to restart the output collector. If the problem persists, search the IBM Support database for a solution at Support.

EQQOC06E

THE OUTPUT COLLECTOR CLIENT TASK ENDED BECAUSE YOU DID NOT DEFINE ANY HTTP OR HTTPS DESTINATIONS.

You did not define any HTTP or HTTPS destinations in the ROUTOPTS statement in the parameter library.

The output collector client task initialization fails.

Verify that the OUCOPTS CNTPARMS parameter is correctly set to the name of the parameter library member containing the ROUTOPTS statement definitions and that you defined at least one HTTP or HTTPS destination for a z-centric agent or a for a dynamic domain manager. Correct the parameters and restart the output collector.

EQQOC07W

THE EQQPARM MEMBER SPECIFIED BY CNTPARMS DOES NOT INCLUDE OUTPUTCOLLECTOR(YES).

The EQQPARM member specified in the CNTPARMS keyword of the OUCOPTS statement points to an HTTPOPTS statement that does not include the OUTPUTCOLLECTOR(YES) keyword.

Output collector continues processing.

Verify that you specified a correct member in CNTPARMS, or that the controller is using a different version of HTTPOPTS with the OUTPUTCOLLECTOR keyword set to YES.

EQQOC08E

OUCOPTS STATEMENT NOT FOUND IN THE EQQPARM PARAMETER LIBRARY MEMBER.

The output collector started task could not find the OUCOPTS initialization statement in the data set specified in the EQQPARM DD statement.

The output collector started task is terminated.

Check and correct the EQQPARM DD statement in the JCL and restart Output collector.

EQQOC10E

OUTPUT COLLECTOR FAILED SETTING TCP/IP IMAGE NAME TO TCPNAME.

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

The output collector 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.

EQQOC11E

THE LOG REQUEST (ADID: ADID, IA: IA, OPNO: OPNUM) IS DISCARDED BECAUSE THE DESTINATION DESTNAME DOES NOT EXIST.

The output collector cannot get the joblog for the operation OPNUM in occurrence ADID with input arrival IA because the destination DESTNAME no longer exists.

The output collector discards the request.

Correct your ROUTOPTS definition. Then run a MODIFY command to refresh the destination list or stop and restart the output collector.

EQQOC12W

THE LOG REQUEST (ADID: ADID, IA: IA, OPNO: OPNUM) IS NOW IN PENDING STATUS BECAUSE THE AGENT IS UNAVAILABLE.

Output collector cannot get the job log for operation OPNUM of occurrence ADID with input arrival IA because the dynamic agent that ran the job is unavailable.

Output collector puts the request in pending status and repeatedly tries to get the job log for this job every 30 minutes until the agent is available or the retry period specified by the OUCOPTS RETAINPEND keyword expires.

Check why the dynamic agent is unavailable and fix the problem. If the problem persists, search the IBM Support database for a solution at Support.

EQQOC13E

OUTPUT COLLECTOR IS CLOSING BECAUSE AN ERROR OCCURRED.

The output collector is closing because an error occurred.

The output collector closes.

Review the output collector message log to determine the cause of the error. If the problem persists, search the IBM Support database for a solution at Support.

EQQOC14E

KILL ERROR KILLING MAIN PROCESS (PID=PID): ERRNO=ERRNUM, ERRMSG, REASON=REASON.

An output collector thread failed to send a signal to shut down the main process. PID is the process ID of the main process. The error is ERRNUM (described by the ERRMSG) with reason code REASON.

The thread closes but the output collector remains active.

Close the output collector and review the output collector message log to determine why the thread is trying to kill the main process. If the problem persists, search the IBM Support database for a solution at Support.

EQQOC15E

ERROR OPENING SYSOUT DATA SET DDNAME: ERRNO=ERRNUM, ERRMSG, REASON=REASON.

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

The output collector ends with errors.

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

EQQOC16E

DYNAMIC ALLOCATION FAILED FOR SYSOUT DATA SET DDNAME: ERROR CODE=ERRNUM, INFORMATION CODE=REASON.

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

The output collector ends with errors.

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

EQQOC17E

DYNAMIC DEALLOCATION FAILED FOR SYSOUT DATA SET DDNAME: ERROR CODE=ERRNUM, INFORMATION CODE=REASON.

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

The output collector ends with errors.

Verify and solve the error that is preventing the output collector from closing the sysout data set, then restart the output collector.

EQQOC18E

ERROR CLOSING SYSOUT DATA SET DDNAME: ERRNO=ERRNUM, ERRMSG, REASON=REASON.

An error occurred while closing the DDNAME sysout data set. The fclose() function error is indicated by ERRNUM (described by the ERRMSG) with reason code REASON.

The output collector discards the data in the sysout data set and it ends with errors.

Verify and solve the error that is preventing the output collector from closing the sysout data set, then restart the output collector.

EQQOC19E

ERROR WRITING TO SYSOUT DATA SET DDNAME: ERRNO=ERRNUM, ERRMSG, REASON=REASON.

An error occurred while writing a joblog to a sysout data set with name DDNAME. The fwrite() function error is indicated by ERRNUM (described by the ERRMSG) with reason code REASON.

The output collector discards the data in the sysout data set and it ends with errors.

Verify and solve the error that is preventing the output collector from closing the sysout data set, then restart the output collector.

EQQOC20E

ERROR PROCESSING THE LOG REQUEST (ADID: ADID, IA: IA, OPNO: OPNUM).

The output collector cannot get the joblog for the operation OPNUM in occurrence ADID with input arrival IA because an error occurred.

The output collector discards the request.

Review the output collector message log to determine the cause of the error. If the problem persists, search the IBM Support database for a solution at Support.

EQQOC21W

DESTINATION DESTNAME IS OFFLINE.

Output collector failed to communicate with the z-centric agent or the dynamic domain >manager identified by the destination DESTNAME.

The processing continues. The output collector tries periodically to connect to the destination.

Look for the message EQQHT15 in the message log. It provides details about the cause of the problem.

EQQOC23W

THE DDNAME EVENT DATASET HAS NOT BEEN FORMATTED YET.

The event dataset specified by DDNAME and used to exchange events between the controller and Output collector 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 Output collector JCLs.

EQQOC24W

ERROR PROCESSING JOB LOG HEADER (ADID: ADID, IA: IA, OPNO: OPNUM).

Output collector cannot substitute the variables specified in the job log header for operation OPNUM in occurrence ADID with input arrival IA because an error occurred. This message is followed by message EQQHT43I, which provides the details of the error.

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

EQQOC25W

ERROR GETTING THE JOB LOG HEADER FROM DESTINATION DESTNAME.

Output collector cannot get the job log header from the agent because the current version of your agent or dynamic domain manager does not support this service.

Output collector does not add the header to the job log of jobs that run on this destination.

Upgrade the agent and/or dynamic domain manager to version 8.6.0.1 or higher. As soon as the upgraded version starts running, Output collector will automatically start adding a header to the job logs originated from this workstation.

EQQOC26W

THE REQUEST CHECKPOINT DATASET DDNAME IS FULL. SLEEPING FOR SECS SECONDS.

Output collector cannot checkpoint an incoming job log request in the DDNAME dataset.

Output collector stops reading incoming requests from the EQQOUCEV dataset for SECS seconds. After that it will retry to checkpoint the request.

Check the output collector message log for messages indicating a problem in communicating with the agents or in deleting check-pointed requests from the dataset. Verify and solve the error. If the problem persists, search the IBM Support database for a solution at Support.

EQQOC27E

ERROR DELETING MEMBER MEMBER FROM THE REQUEST CHECKPOINT DATASET DDNAME.

Output collector cannot delete a processed request from the DDNAME checkpoint dataset.

Output collector continues processing without removing the requestr.

Manually remove the member from the dataset. Verify and solve the error that is preventing Output collector from deleting the member. If the problem persists, search the IBM Support database for a solution at Support.

EQQOC28E

ERROR RESUMING INTERRUPTED JOB LOG REQUESTS. REASON: REASON.

Output collector has encountered a problem during initialization. An error occurred while resuming interrupted job log requests that were checkpointed in the EQQOUCKP dataset.

Output collector stops resuming job log requests and continues its initialization.

Investigate the REASON to solve the problem that is causing the error and restart Output collector. If the problem persists, search the IBM Support database for a solution at Support.

EQQOC30I

THE LOG REQUEST (ADID: ADID, IA: IA, OPNO: OPNUM) IS NO LONGER IN PENDING STATUS.

EQQOC31E

THE PENDING LOG REQUEST (ADID: ADID, IA: IA, OPNO: OPNUM) HAS BEEN DISCARDED BECAUSE THE RETAIN PERIOD HAS EXPIRED.

Output collector cannot get the job log for operation OPNUM of occurrence ADID with input arrival IA because the dynamic agent that ran the job has been unavailable for a longer period than the retry period specified by the OUCOPTS RETAINPEND keyword.

Output collector discards the request.

Check why the dynamic agent is unavailable and fix the problem. If the problem persists, search the IBM Support database for a solution at Support.