EQQFA00 - EQQFV43

EQQFA00E

VSAM ERROR FUNC: FUNC RC: RC REASON: REASON

A VSAM operation failed. FUNC specifies which kind of operation, for example, OPEN, CLOSE, and so on. RC and REASON are the VSAM return and reason codes.

If the VSAM error could not be bypassed the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information. This file contains a copy of the control block.

EQQFA01E

BAD CONTROL BLOCK REASON: - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. The first field of the specified control block is invalid. It does not contain the name of the control block.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information. This file contains a copy of the control block.

EQQFA02E

BAD INSTANCE - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. The specified instance address for the called service is invalid.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA03E

BAD PARAMETER - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. One or more parameters passed to a called service are invalid.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information. This file contains a copy of the value of the invalid parameter.

EQQFA04E

BAD REQUEST - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. The specified address for the control block is invalid.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information. This file contains the value of the invalid request field.

EQQFA05E

BAD SYSOUT DATABASE - REASON: REASON

Generally there is a mismatch between the primary keys data set and data files, for example, the Data Store was started without all the previously-used data files and containing the sysout listed by the primary key file.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

Check that, when the Data Store was started, it was pointing to the correct primary key and data files. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA06E

IS EMPTY - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. An internal objects list was found to be empty.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA07E

NOT FOUND - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. An internal object was not found by a search operation.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA08E

NOT INITIALIZED - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. A data file was not found in an initialized state.

The Data Store is terminated See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA10E

DETACH ERROR - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. An error occurred when the Data Store attempted to detach a subtask.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error.

EQQFA11E

NOT ACTIVE - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. A component that should be active was found in an inactive state.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA12E

NOT READY - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. A data file or primary index was found not ready to be used, for example, not logically open.

The Data Store is terminated

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA13E

INTERNAL ERROR - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. This is a generic internal failure of the Database task. It can occur during the shutdown of the Data Store and indicates an internal mismatch. No data is lost, but its handling can be deferred to the next startup of the Data Store.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA14E

BAD DATA - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. A data file or a storage area was found in a corrupted state.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

Use the Recover utility to recover the corrupted data file or use the Export utility to make a copy of the previous backup copy. After the recovery operation, if the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA17E

COMMAND ERROR

This message describes an internal error of the Data Store and is addressed to IBM Software Support. An internal error was detected while analyzing a modify comamnd.

The modify command is ignored.

Resubmit the modify command with the correct syntax.

EQQFA18E

STOP IN PROGRESS

The Data Store has received a command while closing all the subtasks.

The stop command is ignored.

EQQFA19E

COMMAND SYNTAX ERROR

The modify command is syntactically incorrect.

The modify command is ignored.

Resubmit the modify command with the correct syntax.

EQQFA20E

NOT OPEN - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. A read or write operation was attempted on a data file or index that was not previously opened.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (with ddname EQQDUMP) for further information.

EQQFA21E

ERROR IN RPL GENERATION FOR VSAM ACCESS - REASON: REASON

During an RPL generation, the DIV macro returns an error.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If possible correct all errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that there is a DFP error in the Data Store data files or indexes.

EQQFA22E

ERROR IN POINT OPERATION ON VSAM FILE - REASON: REASON

During a Point operation, the DIV macro returns an error.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If possible correct all errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that there is a DFP error in the Data Store data files or indexes.

EQQFA24E

VSAM LOGICAL ERROR IN GET - REASON: REASON

During a Get operation, the DIV macro returns an error.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If possible correct all errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that there is a DFP error in the Data Store data files or indexes.

EQQFA25E

VSAM PHYSICAL ERROR IN GET - REASON: REASON

During a Get operation, the DIV macro returns an error.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If possible correct all errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that there is a DFP error in the Data Store data files or indexes.

EQQFA26E

NO PARAMETER PASSED - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. A calling function did not pass all the required parameters to the called function.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA27E

INCORRECT PARAMETER IN MODIFY COMMAND

The command could not be processed because one or more parameters on that command could not be recognized or are out of range.

The command is ignored.

Change the Modify command and resubmit the command.

EQQFA28E

TRANSMISSION ERROR FROM COMMUNICATION - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. There was a generic transmission error in the communication subtask.

The requested data cannot be transmitted. See Reason codes for a list of the REASON codes.

If possible correct all the errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possible reason is a communication failure in the SNA or the XCF communication task due to system resource definition or an unavailable resource.

EQQFA30E

BAD STATUS - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. An internal object was found in a corrupted state.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

Contact the Software Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA32E

BAD PAGE - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. The database component detected a data page in a corrupted state.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

Use the Recover utility to recover the corrupted data file or use the Export utility to make a copy of the previous backup copy. After the recovery operation, if the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA34E

NO SPACE AVAILABLE - REASON: REASON

There is no more space available in a data file or an index file.

The involved Database data file subtask is closed. Data Store processing continues using the other data files. If this was the last available data file, the Data Store is terminated.

Refer to the dump data set (ddname EQQDUMP) for further information. The data files or the index files, or both, should be reallocated with more space and the old data files should be copied using the IDCAMS Repro utility or the Data Store Export/Import utility.

EQQFA36E

ERROR DURING ENQUEUE - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. An enqueue operation failed.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA37E

ALREADY RESERVED - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. The Data Store attempted to reserve a message that was already reserved for processing.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA39E

ERROR IN ACB GENERATION FOR VSAM ACCESS - REASON: REASON

During an ACB generation, the macro returns an error.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If possible correct all errors and restart the Data Store. If the error persists, contact the Software Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that there is a DFP error in the Data Store data files or indexes.

EQQFA42E

NO DD FOUND - REASON: REASON

In the Data Store startup procedure, all the ddnames and the files that are necessary for Data Store life were not specified.

The Data Store is terminated See Reason codes for a list of the REASON codes.

Check the Data Store start up procedure.

Refer to the Planning and Installation Guide for correct definitions of files.

EQQFA43E

VSAM OPEN ERROR - REASON: REASON

During an Open operation, the macro returns an error.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If possible correct all errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that there is a DFP error in the Data Store data files or indexes.

EQQFA44E

GENERIC I/O ERROR - REASON: REASON

During an I/O operation, an error was detected.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If possible correct all errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that there is a DFP error in the Data Store data files or indexes.

EQQFA45E

ATTACH ERROR - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. An error occurred when the Data Store attempted to attach a subtask.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If possible correct all errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that the Data Store is being started in a region that is too small.

EQQFA46E

UNEXPECTED TASK END - REASON: REASON

A Data Store subtask ended unexpectedly.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA47E

ERROR DURING DYNALLOC (ALLOCATION) - REASON: REASON

There was an error during a Dynalloc operation.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA48E

ERROR DURING SSI REQUEST - REASON: REASON

There was an error during a Dynalloc operation.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA49E

ERROR DURING DYNALLOC (UNALLOCATION) - REASON: REASON

This message describes an internal error of the Data Store and is addressed to IBM Software Support. An error was detected when a Subsystem Interface function was invoked.

The Data Store is terminated. See Reason codes for a list of the REASON codes.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Refer to the dump data set (ddname EQQDUMP) for further information.

EQQFA70E

NO VALUE ASSIGNED TO SYSDEST PARAMETER

You must specify a valid output destination value in the SYSDEST parameter of DSTOPTS because there is no default value..

Data store does not start.

Check the command. Correct the error and resubmit the request.

EQQFA71E

SYSDEST IS MANDATORY IN DSTOPTS OPTIONS

You must specify the SYSDEST (sysout destination reserved for data store) parameter in DSTOPTS.

Data store does not start.

Check the command. Correct the error and resubmit the request.

EQQFA72W

HDRJOBNAME PARAMETER NOT SPECIFIED DEFAULTED TO "JOBNAME"

You did not specify the HDRJOBNAME parameter in DSTOPTS. It has been defaulted to "JOBNAME"

Data store continues processing.

None.

EQQFA73W

HDRSTEPNAME PARAMETER NOT SPECIFIED DEFAULTED TO "STEPNAME"

You did not specify the HDRSTEPNAME parameter in DSTOPTS. It has been defaulted to "STEPNAME".

Data store continues processing.

None.

EQQFA74W

HDRPROCNAME PARAMETER NOT SPECIFIED DEFAULTED TO "PROCSTEP"

You did not specify the HDRPROCNAME parameter in DSTOPTS. It has been defaulted to "PROCSTEP".

Data store continues processing.

None.

EQQFA75W

HDRJOBLENGTH PARAMETER NOT SPECIFIED DEFAULTED TO 21

You did not specify the HDRJOBLENGTH parameter in DSTOPTS. It has been defaulted to 21.

Data store continues processing.

None.

EQQFA76W

HDRSTEPLENGTH PARAMETER NOT SPECIFIED DEFAULTED TO 30

You did not specify the HDRSTEPLENGTH parameter in DSTOPTS. It has been defaulted to 30.

Data store continues processing.

None.

EQQFA77W

HDRPROCLENGTH PARAMETER NOT SPECIFIED DEFAULTED TO 39

You did not specify the HDRPROCLENGTH parameter in DSTOPTS. It has been defaulted to 39.

Data store continues processing.

None.

EQQFA78E

AN INVALID VALUE WAS ASSIGNED TO SYSDEST PARAMETER

You have specified an invalid value for the SYSDEST parameter of the DSTOPTS option. It must be a valid z/OS name.

Data store does not start.

Check the command. Correct the error and resubmit the request.

EQQFA7AW

MAXUNPAGES PARM NOT SPECIFIED OR OUT OF RANGE DEFAULTED TO 4096

The MAXUNPAGES parameter was not specified in DSTOPTS, or its value is out of range. It has been defaulted to 4096.

Data store continues processing.

None.

EQQFA7BW

SMSMODDELETE PARAM NOT SPECIFIED DEFAULTED TO NO

The SMSMODDELETE parameter was not specified in DSTOPTS. It was defaulted to NO.

Data store continues processing.

None.

EQQFA81I

THE DSTHIGHJOBID VALUE USED NEEDS MVS 64K JOBID SUPPORT

The DSTHIGHJOBID value is greater than 65534. The MVS system must support >64K Jobid values.

Data store continues processing.

EQQFA82E

CTLHOSTNAME IS MANDATORY WHEN HOSTCON(TCP) IS SPECIFIED.

If you select the TCP/IP connection type, you must specify the CTLHOSTNAME parameter.

The Data Store does not start.

Correct the DSTOPTS initialization statement and restart the Data Store.

EQQFA83W

CTLPORTNUMBER NOT SPECIFIED OR OUT OF RANGE (0:65535) DEFAULTED TO 423.

The CTLPORTNUMBER parameter is invalid or missing.

The Data Store processing continues using the default value for CTLPORTNUMBER parameter.

EQQFAR1I

WAITING FOR SUBTASK COMPLETION TASKNAME

The Data Store is waiting for a subtask completion. This message can occur during the Data Store shut down.

None.

None.

EQQFAR2E

TASKNAME TASK ABENDED - RETURN: REASON

The task specified TASKNAME has abended with reason REASON or is terminated unexpectedly.

The involved Data Store task is closed. If the involved task is either the JES Queue or the Database task, the Data Store is terminated. If the involved task is WRITER and the RETURN value is 00001000, see message EQQFJKME.

If possible correct all errors and restart the Data Store. If the error persists, contact the Software Support.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that the Data Store is being started in a region that is too small.

EQQFAR3I

ALL WRITER SUBTASKS ARE CLOSED

All active writer subtasks are now closed.

The Data Store is not able to store sysout until a minimum of one writer is restarted. To start some of them, issue the ARMDWR modify command.

EQQFAR4I

DATA STORE ENDED

All Data Store subtasks have terminated. The Data Store subsystem is starting its own termination process.

The Data Store subsystem frees all acquired resources and is terminated.

EQQFAR5W

RETRYCOUNTER PARM INVALID OR NOT SPECIFIED: DEFAULTED TO 1

The RETRYCOUNTER value is invalid or missing. A default value of 1 will be used.

Data store continues processing.

EQQFAR6E

INVALID COMBINATION OF COMMUNICATION PARAMETERS

The combination of communication parameters is invalid, for example, you have specified both HOSTCON(SNA) and CTLMEM.

The Data Store does not start.

EQQFAR7W

FAILDEST PARM NOT SPECIFIED: DEFAULTED TO FAILDEST

The FAILDEST parameter was not specified. Default value FAILDEST will be used.

Data store continues processing.

EQQFAR8I

DATA STORE STATISTICS

A modify command, /F procname,ARSTGN or /F procname,ARSTKW O=[owner],K=[keyword], has been issued and the data store shows internal statistics values. This message is followed by one or more EQQFAR9I messages.

Data store statistics are displayed

None

EQQFAR9I

DATA STORE STATISTICS NOT EVALUATED YET

A modify command, /F procname,ARSTGN or /F procname,ARSTKW O=[owner],K=[keyword], has been issued but the data store does not have any statistic value to display.

Data store continues processing.

None.

EQQFARAI

DATA STORE TASKNAME TASK ACTIVE

The task indicated by TASKNAME has been successfully started and is active.

The Data Store continues processing.

EQQFARBE

A COMMUNICATION METHOD MUST BE SPECIFIED (SNA / XCF)

You must specify one of the two methods for communication in DSTOPTS via the HOSTCON keyword.

The Data Store does not start.

EQQFARCE

DSTLUNAM / CTLLUNAM ARE MANDATORY WHEN HOSTCON(SNA) IS SPECIFIED

If HOSTCON(SNA) is required, you must specify both DSTLUNAM and CTLLUNAM.

The Data Store does not start.

EQQFARDE

DSTGROUP / DSTMEM / CTLMEM ARE MANDATORY WHEN HOSTCON(XCF) IS SPECIFIED

If HOSTCON(XCF) is required, you must specify all the three parameters.

The Data Store does not start.

EQQFAREE

SYSCLASS IS MANDATORY IN DSTOPTS OPTIONS

You must specify the SYSCLASS (sysout class reserved for Data Store) parameter in DSTOPTS.

The Data Store does not start.

EQQFARFW

NWRITER PARM NOT SPECIFIED OR OUT OF RANGE (1:16): DEFAULTED TO 1

The NWRITER (number of writer tasks) parameter was invalid or not specified. The number of writers was defaulted to 1.

The Data Store continues processing.

EQQFARGW

MAXSTOL PARM NOT SPECIFIED OR OUT OF RANGE (0:10000): DEFAULTED TO 0

The MAXSTOL (maximum number of sysout lines stored in SysDb) parameter was invalid or not specified. The maximum number of stored lines was defaulted to 0.

The Data Store continues processing.

EQQFARHW

MAXSYSL PARM NOT SPECIFIED OR OUT OF RANGE (0:10000): DEFAULTED TO 0

The MAXSYSL (maximum number of sysout lines returned to the Controller) parameter was invalid or not specified. The maximum number of sysout lines was defaulted to 0.

The Data Store continues processing.

EQQFARIW

QTIMEOUT PARM NOT SPECIFIED OR OUT OF RANGE (0:10000): DEFAULTED TO 15

The QTIMEOUT (timeout system reader) parameter was invalid or not specified. The timeout system reader was defaulted to 15.

The Data Store continues processing.

EQQFARJE

DSTHIGHJOBID PARM MUST BE GREATER THAN DSTLOWJOBID PARM.

You have specified a value for the DSTHIGHJOBID parameter that is lower than the value of the DSTLOWJOBID parameter.

The Data Store does not start.

EQQFARKI

DATA STORE STATISTICS NOT EVALUATED YET

A modify command, /F procname,ARSTGN or /F procname,ARSTKW O=[owner],K=[keyword], has been issued but the Data Store doesn't have any statistic value to display.

Data Store continues processing.

None

EQQFARKW

RETRYCOUNTER PARM INVALID OR NOT SPECIFIED: DEFAULTED TO 1

The RETRYCOUNTER value is invalid or missing. Default value 1 will be used.

Data Store continues processing.

EQQFARLW

CINTERVAL PARM NOT SPECIFIED OR OUT OF RANGE (0:1440): DEFAULTED TO 0

The CINTERVAL (interval time in minutes for cleanup) parameter was invalid or not specified. The interval time for cleanup was defaulted to 0.

The Data Store continues processing.

EQQFARMW

WINTERVAL PARM NOT SPECIFIED OR OUT OF RANGE (0:3600): DEFAULTED TO 30

The WINTERVAL (interval time in seconds for writer) parameter was invalid or not specified. The interval time for writer was defaulted to 30.

The Data Store continues processing.

EQQFARNW

DELAYTIME PARM NOT SPECIFIED OR OUT OF RANGE (0:1440): DEFAULTED TO 1

The DELAYTIME (maximum delay for job permanence in JES queue) parameter was invalid or not specified. The parameter was defaulted to 1.

The Data Store continues processing.

EQQFAROE

REQDEFCLASS MUST BE DIFFERENT FROM SYSCLASS

The REQDEFCLASS (default class for requeue) parameter must be different from the SYSCLASS (sysout class reserved for Data Store) parameter.

The Data Store does not start.

EQQFARPE

UNABLE TO START TASK BECAUSE IT IS ALREADY ACTIVE

An operator START command has been entered for a Data Store task that is already active.

The second attempt is terminated.

If you want to restart the task, first stop it, and then issue the START command.

EQQFARQE

SYSDEST SPECIFIES A DESTINATION ALREADY IN USE BY ANOTHER DATA STORE

A Data Store has been started with a destination that is assigned to another active Data Store.

The second Data Store is terminated.

If you want to restart the second Data Store, first change the SYSDEST in the initialization parameters.

EQQFARRI

SUBTASK TASKNAME DIAGNOSE HAS BEEN ACTIVATED

The diagnose trace for subtask TASKNAME has been activated

The activities of subtask TASKNAME are now traced.

EQQFARSI

SUBTASK TASKNAME DIAGNOSE HAS BEEN DE-ACTIVATED

The diagnose trace for subtask TASKNAME has been deactivated.

The activities of subtask TASKNAME are now traced.

EQQFARTW

CLNPARM PARM NOT SPECIFIED DEFAULTED TO EQQCLNPA

The CLNPARM (cleanup options member name) parameter was not specified. The cleanup options member name was defaulted to EQQCLNPA.

The Data Store continues processing.

EQQFARUW

STORESTRUCMETHOD PARM NOT SPECIFIED DEFAULTED TO IMMEDIATE.

You did not specify a value for storestrucmethod parameter. The allowed values are :

Delayed- Structured information will be archived only on demand, that is when requested by controller.

Immediate- Structured information will be archived as soon as possible, when a writer task will be available.

Value is defaulted to immediate. Processing continues.

None

EQQFARVW

DSTREQUEUEDEF PARM NOT SPECIFIED DEFAULTED TO ASIS

The DSTREQUEUEDEF parameter was not specified. The parameter was defaulted to ASIS.

The Data Store continues processing.

EQQFARWE

STORESTRUCMETHOD (DELAYED) NEEDS STOUNSD (YES)

If you specify storestrucmethod as delayed you must set STOUNSD to yes, because delayed method needs to find the JOBLOG into the UDF files in order to extract the structured data.

Processing is terminated.

Set STOUNSD to yes and check that the UDFXX files are allocated and specified into the data store start JCL.

EQQFARXE

INVALID VALUE SPECIFIED FOR STORESTRUCMETHOD PARAMETER.

If you specify an invalid value for parameter storestrucmethod. The allowed values are:

Delayed- Stuctured information will be archived only on demand, that is when requested by controller.

Immediate- Structured information will be archived as soon as possible, when a writer task will be available.

Processing is terminated.

Set a valid value.

EQQFARYI

DSTLOWJOBID PARM NOT SPECIFIED, DEFAULTED TO 1

The DSTLOWJOBID parameter was invalid or not specified. The parameter was defaulted to 1.

The Data Store continues processing.

EQQFARZI

DSTHIGHJOBID PARM NOT SPECIFIED, OR INVALID DEFAULTED TO hjobid

The DSTHIGHJOBID parameter was not valid or not specified. The parameter was defaulted to the hjobid value, where hjobid is one of the following:
  • 65534, if the value of DSTHIGHJOBID is greater than 65534
  • 9999 otherwise

Data store continues processing

EQQFCC0E

DATA STORE COMMUNICATION TASK INITIALIZATION FAILED

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

The Communication task is not started.

Correct the errors and restart the communication task.

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

EQQFCC1I

DATA STORE COMMUNICATION TASK INITIALIZATION ENDED

The Communication task has successfully completed its initialization.

Communication processing starts.

EQQFCC2I

DATA STORE COMMUNICATION TASK ENDED

The Communication processing has been completed and control is returned to the Data Store subsystem.

The Communication task is terminated.

EQQFCC3I

STARTING FN APPLICATION

The Data Store FN task has received control from the Data Store communication subtask and is soon to start initialization processing.

Data Store FN processing continues.

EQQFCC4I

CLOSING FN APPLICATION

The Data Store FN processing has been completed and control is returned to the Data Store communication task.

Data Store FN processing is terminated.

EQQFCC5E

FN APPLICATION DOES NOT RESPOND

After a close request issued by the Data Store communication task, the Data Store FN subtask does not respond.

The system waits until the subtask is closed.

Correct the errors shown in the message and restart the std task.

Check for problems in the communication VTAM or TCP/IP settings of the system where the data store runs. C

EQQFCC6I

XCF COMMUNICATION WITH CONTROLLER MEMBER MEMBER IS OFFLINE

The member MEMBER of the XCF communication with the Controller is offline.

The Data Store cannot communicate with the Controller.

Check if the Controller is active or if there are some problems in the XCF connections. One possibility is that either CTLMEM or DSTGROUP is incorrectly specified in the DSTOPTS initialization statement.

EQQFCC7I

UNABLE TO SEND MESSAGE: CONTROLLER XCF MEMBER MEMBER IS OFFLINE

The XCF Controller member MEMBER is offline.

The Data Store cannot communicate with the Controller: sysout cannot be sent back to it.

Check if the Controller is active or if there are some problems in the XCF connections. One possibility is that CTLMEM is incorrectly specified in the DSTOPTS initialization statement.

EQQFCC9I

XCF MEMBER MEMBER HAS JOINED THE GROUP GROUP

A data store or controller FL subtask has joined the XCF group as defined in the DSTOPTS or FLOPTS statements.

None

None.

EQQFCCAI

STARTING XCF JOIN

The join process between the Data Store and XCF has been started.

Normal processing continues.

EQQFCCBI

UNABLE TO RETRIEVE JOB JOBNAME: READER TASK INACTIVE

The Controller requested the retrieval of the JOB JOBNAME to the Data Store, but the Data Store Reader subtask is not active. The retrieval cannot be performed.

The request is rejected. Data Store normal processing continues.

Start the reader task and resubmit the request.

EQQFCCCI

STARTING TCP/IP COMMUNICATION TASK FOR DATA STORE (ID TASK).

The ID task started the initialization process.

The processing continues.

EQQFCCDE

TCP/IP COMMUNICATION TASK FOR DATA STORE DOES NOT RESPOND (ID TASK).

After a close request issued by the Data Store communication task, the ID task does not respond.

The system waits until the subtask is closed.

Correct the errors shown by the earlier messages and restart the std task.

Check for problems in the TCP/IP settings of the system where the data store runs.

EQQFCCEI

CLOSING TCP/IP COMMUNICATION TASK FOR DATA STORE (ID TASK).

The TCP/IP communication processing has been completed and control is returned to the Data Store subsystem.

The TCP/IP communication task (ID task) ends.

EQQFCM1I

STOP IN PROGRESS

The Data Store command task is terminating after a stop request.

The Data Store waits until the command task is closed.

EQQFCM2I

DATA STORE COMMAND TASK IS BEING STARTED

The command task has been successfully attached.

The Data Store continues processing. If the startup process is successful, the Command task issues its own start message.

EQQFCM3I

DATA STORE COMMAND TASK ENDED

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

The command task is terminated and all other active tasks are closed.

EQQFCMAI

NUMBER OF ACTIVE WRITERS: VALUE

This message indicates (by VALUE) the number of writers that are currently running.

The Data Store continues processing.

EQQFCMBI

WINTERVAL TIME FOR SYSDB WRITERS : VALUE

This message indicates (by VALUE) the current value of the WINTERVAL (interval time in minutes for writer) parameter.

The Data Store continues processing.

EQQFCMCI

MAXSYSL RETURNED SYSOUT LINES: VALUE

This message indicates (by VALUE) the current value of the MAXSYSL (maximum number of sysout lines returned to the Controller) parameter.

The Data Store continues processing.

EQQFCMDI

MAXSTOL STORED SYSOUT LINES: VALUE

This message indicates (by VALUE) the current value of the MAXSTOL (maximum number of sysout lines stored in SysDb) parameter.

The Data Store continues processing.

EQQFCMFI

CLEAN UP INTERVAL TIME: VALUE

This message indicates (by VALUE) the current value of the CINTERVAL (interval time in minutes for cleanup) parameter.

The Data Store continues processing.

EQQFCMGE

AN INCORRECT MODIFY COMMAND HAS BEEN IGNORED

The Data Store has detected an invalid modify command.

The modify command is not processed.

Enter a valid command.

EQQFCMHE

MODIFY COMMAND SYNTAX ERROR

The modify command is syntactically incorrect.

The modify command is not processed.

Enter a valid command.

EQQFCMIE

INVALID MODIFY COMMAND PARAMETER VALUE

The parameter value specified for the modify command is incorrect or out of range.

This command is not processed. The Data Store continues processing.

Enter a valid command.

EQQFCU1I

CLEAN UP TASK STARTED

The cleanup data store task has been successfully started. This does not always mean that a cleanup policy is running (see message EQQFCU3I).

The Data Store continues processing.

EQQFCU2I

CLEAN UP TASK ENDED

The cleanup data store task has been requested to stop and is terminating normally.

The cleanup task is terminated. Data Store normal processing continues.

EQQFCU3I

CLEAN UP TASK RUNNING

The cleanup data store task is running. A value other than 0 (zero) was specified for CINTERVAL. The cleanup policy specified in the CLNPARM member is active.

The Data Store and cleanup task continue processing.

EQQFCU4I

CLEAN UP TASK IN QUIESCE STATUS

The cleanup task is in a quiescent status and is waiting until the cleanup interval time has elapsed.

At the end of the cleanup interval time, the cleanup task is reactivated.

EQQFCU5E

PARAMETER NOT ALLOWED IN DATA STORE CLEAN UP TASK

A statement (or statements) in CLNPARM is invalid because it is applicable only to batch cleanup.

The cleanup task is terminated. Data store normal processing continues.

Check the CLNPARM statement (or statements). Correct the error and restart the cleanup task.

EQQFCU6I

BATCH UTILITY PROCESSING STARTED

The batch program that executes the batch utilities has been successfully started.

None

EQQFCU7E

PARAMETER PARM NOT ALLOWED IN BATCH CLEAN UP

A statement (or statements) in CLNPARM is invalid because it is applicable only to the data store cleanup task.

Batch utility processing is terminated.

Check the CLNPARM statement (or statements). Correct the error and resubmit the utility.

EQQFCU8I

BATCH UTILITY PROCESSING ENDED

The program that executes the batch utilities is terminating normally.

The batch utility processing is terminated. Data Store normal processing continues.

EQQFCU9E

STRUCTURED DATA NOT AVAILABLE

One of the following events has happenned:
  • A batch utility is processing one of the following commands:
    • DELBOTH
    • DELSTRUC
    • EXPBOTH
    • EXPSTRUC
    but the structured data files are not available (perhaps because they were not specified in the JCL procedure).
  • A batch utility is processing an IMPORT command by using an export file that contains structured data but the structured data files are not available (perhaps because they were not specified in the JCL procedure).

The current command is ignored and the following command is processed.

Check the command and the batch utility start JCL. Correct the error and resubmit the request.

Refer to the diagnostics file (ddname EQQDUMP) for further information

EQQFCUAE

CMDPAR: PARM-MEMBER IS EMPTY

No operand is specified in the CMDPAR member.

The batch utility is not started.

Check the member. Correct the error and resubmit the request.

EQQFCUBE

IMPORT / EXPORT COMMAND WITHOUT DDNAME PARAMETER

The DDNAME parameter was not specified in an Import or Export statement.

The request is rejected.

Check the DDNAME parameter. Correct the error and resubmit the utility.

EQQFCUCE

PARAMETER CMDPAR NOT ALLOWED

The CMDPAR parameter is not allowed for this statement.

The request is rejected.

Check the parameter. Correct the error and resubmit the utility.

EQQFCUEE

ERROR ON PARAMETER LIBRARY MEMBER CMDPAR

An error was found in the CMDPAR initial parameter member.

The batch utility is terminated. Previous error messages help you to understand the problem.

Check the statement. Correct the error and resubmit the utility.

EQQFCUFE

SYNTAX ERROR IN SEARCH CRITERIA CMDPAR

The search condition specified for the CMDPAR statement contains a syntax error (or errors).

The batch utility is terminated.

Check the statement. Correct the error and resubmit the utility.

EQQFCUGW

NAME EXCEEDS 8 CHARACTERS

In the search criteria, you specified a Job name or Job ID that is greater than eight characters. This is not allowed.

The name or ID is truncated to eight characters.

To use the correct criteria, change the statement and resubmit the utility.

None.

EQQFCUHW

THE IMPORT FILE IS EMPTY

The import batch utility found an empty import file.

The batch utility is terminated.

Check the import file and, if necessary, resubmit the utility.

EQQFCUJI

NUMBER OF SYSOUTS/RECORDS EXPORTED: nnn/mmm NUMBER OF SYSOUTS IGNORED: xxx

This message is issued by the data store batch utility to indicate:
  • The total number of SYSOUTS that were selected from the SYSOUT database and stored in the export file (nnn)
  • The total number of records that were selected from the SYSOUT database and stored in the export file (mmm)
  • The total number of SYSOUTS that were not selected from the SYSOUT database according to the specified filter criteria (xxx)

The system informs you that the export utility has terminated processing of a single export command. Normal batch utilities processing continues.

EQQFCUKI

NUMBER OF SYSOUTS IMPORTED: nnn NUMBER OF SYSOUTS IGNORED: mmm

This message is issued by the Data store batch utility to indicate:
  • The total number of SYSOUTS that were selected from the import file and stored in the SYSOUT database (nnn)
  • The total number of SYSOUTS that were not selected from the import file according to the specified filter criteria (mmm)

None.

EQQFCUMW

BAD SYSOUT: SYSOUT KEY IMPORTED

During a batch import utility, a mismatch was detected between the number of records written in the import file, for a specific sysout, and the total number of pages stored in the page prefix. The incorrect SYSOUT KEY is shown.

The batch utility does not import the incorrect sysout and continues its normal processing.

EQQFCUNI

NUMBER OF KEYS EXTRACTED: nnn

This message indicates the total number of keys selected from the sysout database and written into an output file by a single batch recover primary index utility.

The system informs you that the recover utility has terminated Normal batch utilities processing continues.

EQQFCUOW

THE HEADER RECORD DOESN'T CONTAIN A VALID IDENTIFIER

The first record of an input file found by the import batch utility is not an header record.

The import utility is terminated.

Check the import file and, if necessary, resubmit the utility.

EQQFCUPI

CLEAN UP ISSUED DELETE REQUEST FOR NNN SYSOUTS STRUCTURED: STR UNSTRUCTURED: UNS

The cleanup task has completed the deletion of the specified sysouts (NNN) in accordance with the current cleanup policy. STR identifies the number of deleted structured sysout (joblogs structured info) and UNS identifies the number of deleted unstructured sysout (joblogs).

None

EQQFCUQI

EQQCLNPA MEMBER NOT FOUND

This message is issued when the CLNPARM option is not specified in the DSTOPTS statement. Default member EQQCLNPA is used, but is not found in the parameter library.

The cleanup task is started, but there is no active policy.

Specify the CLNPARM option or add the member EQQCLNPA into the parameter library and restart the cleanup task with the appropriate command.

EQQFCUSE

UNSTRUCTURED DATA NOT AVAILABLE

One of the following events has happenned:
  • An online cleanup was processing a DELUNSTR or DELBOTH command, but STOUNSD(N) was codified in Data Store (Data Store does not manage unstructured data).
  • A batch utility was processing the DELBOTH, DELUNSTR, EXPBOTH, or EXPUNSTR command but the unstructured data files are not available (perhaps they were not specified in the JCL procedure).
  • A batch utility was processing an IMPORT command by using an export file that contains unstructured data, but the unstructured data files are not available (perhaps they were not specified in the JCL procedure).

If the message is issued during the online cleanup, the execution of the command is terminated. The cleanup task waits for another request and Data Store normal processing continues. If the message is issued while the batch utility program is running, the current command is discarded and the next command is processed.

Check the command and the batch utility start JCL. Correct the error and resubmit the request.

Refer to the diagnostics file (with ddname EQQDUMP) for further information.

EQQFCUTE

A SINGLE COMMAND MUST BE SPECIFIED IN ON LINE DATA STORE CLEAN UP

During the online cleanup, more than one command DSTUTIL has been specified, but this isn’t supported in on line mode.

No command DSTUTIL is performed and the data store is terminated with return code 8.

Correct the error specifying only one DSTUTIL command in the cleanup parameters member. Then restart data store.

Contact your system programmer.

No further information is needed to identify this problem.

EQQFJK1I

UNABLE TO WRITE ALL DSID IN SYSDB FOR JOB: JOBNMID

After several retries, a writer task was unable to store all the sysouts in the database for the specified job.

The sysouts are not requeued to their original class. They are kept in the Data Store reserved class for a next retry until they are correctly processed or removed manually from the reserved class.

If the error persists, remove the job manually from the reserved class and contact the Software Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error.

EQQFJK2E

DATA STORE JESQUEUE TASK INITIALIZATION FAILED

The JES queue task could not acquire all the resources needed for normal operation.

The JES queue task is not started and all other active tasks are closed. Data Store is terminated.

Correct the errors and restart the data store.

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

EQQFJK3I

DATA STORE JESQUEUE TASK INITIALIZATION COMPLETED

The JES queue task has successfully completed its initialization.

JES queue processing starts.

EQQFJK4I

DATA STORE JESQUEUE TASK ENDED

The JES queue task has been requested to stop and is terminating normally.

The JES queue task is terminated.

EQQFJK5E

DATA STORE JESQUEUE TASK ENDED DUE TO AN ERROR

The JES queue task has been abnormally stopped.

The JES queue task is terminated and all other active tasks are closed. The data store is terminated.

Correct the errors shown by the earlier messages and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Correct the errors shown by the data store message log and restart the data store. If the problem occur again refer to the Diagnosis Guide and Reference.

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

EQQFJK6I

DATA STORE JESQUEUE TASK WAITING FOR DATABASE TASK END.

The JES queue has received a stop command, but it has some jobs in its queue and the database task has to complete the pending requests.

The JES queue task waits until the database task is terminated.

EQQFJK7I

DATA STORE JESQUEUE TASK CLOSE IN PROGRESS : ANALYSING QUEUE

Before closing, the JES queue task examines its internal queue for the last time to close all pending situations.

None.

EQQFJK9I

JOBNMID CANNOT BE REQUEUED TO ORIGINAL CLASS: DEFAULT CLASS IS USED.

The original class specified for the requeue operation is reserved. The requeue operation for the JOBNMID job is forced in the default class.

JES queue processing continues.

EQQFJKAI

ORIGINAL CLASS NOT FOUND: JOBNMID REQUEUED TO DEFAULT CLASS

The original class specified for the requeue operation was not found. The requeue operation for the JOBNMID job is forced in the default class.

JES queue processing continues.

EQQFJKBE

SSI CALL ENDED IN ERROR:FUNCTION: SAPIFUNCRETURN CODE: SRCSSOBRETN: SRETNSSS2REAS: SREASJOBNAME: SAPIJOBNJOBID: SAPIJBID

Data Store invoked the SSI interface to execute a SAPI function for handling the sysout from its reserved destination queue, but this call failed. The message displays the following detailed information:
SAPIFUNC
The SAPI function that failed. Possible values are:
SAPI 79 — PUT/GET
Used to put/get sysouts from spool.
SAPI 79 — PUT/GET LAST CALL
Used to close a put/get function.
SAPI 79 — COUNT
Used to count sysout elements.
SAPI 79 — COUNT LAST CALL
Used to close a count function.
SAPI 79 — BULK MODIFY
Used to requeue or purge sysouts.
SAPI 79 — BULK MODIFY LAST CALL
Used to close a Bulk modify function.
SRC
The return code from the SSI call. To learn its meaning, refer to the MVS publication that describes the specified SAPI function (OS/390 MVS Using the Subsystem Interface — Return Code Information).
SRETN
The value returned by SAPI in the ssobretn field of the SSOB control block. To learn its meaning, refer to the MVS publication that describes the specified SAPI function.(OS/390 MVS Using the Subsystem Interface — Output Parameters — SSOBRETN Contents).
SREAS
The value retuned by SAPI in the sss2reas field of the SSS2 control block To learn its meaning, refer to the MVS publication that describes the specified SAPI function (OS/390 MVS Using the Subsystem Interface — Output Parameters — SSS2 Contents).
SAPIJOBN
The jobname filter criteria used to execute the specified SAPI function. It can be blank or it can contain a jobname value. The jobname value indicates which is the job that causes problems to the SAPI function. A blank indicates that Data Store issued a SAPI function to get all the jobs on its reserved queue: in this case, it is not easy to identify the job that causes problems (if it is a job and not another kind of error). One of the possible reasons is a job that lacks the JCT; this can be verified by looking for the $HASP364 message on the data store log.
SAPIJBID
The jobid range used as filter criteria for the specified SAPI function. It has the form lowjobid/highjobid. If lowjobid and highjobid are equal, they identify the single job that causes trouble. If lowjobid and highjobid are different, this means that Data Store issued a SAPI function to get all the jobs on its reserved queue. The SAPIJBID is the used range.

Data store stops processing the problem job. If the error occurred in the JES queue task, data store stops processing completely. If the error occurred in the Writer task, Writer stops processing and the job is retried later.

See the MVS publication for the explanation of the SAPI function,the return code, the SSOB reason code, and the SSS2 reason code. If a specific jobname jobid is shown in the message, remove it from the reserved class queue. If no specific jobname appears, look into the reserved class queue which contains the jobs currently handled by data store: a generic SAPI get function was issued with only reserved class as the filter criteria. One of the possible reasons is that a job has no JCT and this can be verifyed by looking for the $HASP364 message in the data store log.

Contact your system programmer to analyze where the problem originated.

EQQFJKDI

ARCHIVING IN PROGRESS FOR: JOBNMID (REASON=RETRY)

The archiving process is not completed yet, but there is no real error: data is still being sent and a retry will be performed.

The data store continues the archiving process.

None.

EQQFJKEI

ARCHIVING IN PROGRESS FOR: JOBNMID (REASON=DELAY)

The archiving process is not completed yet, but there is no real error: delay time has been reached (data retry will be performed).

The data store continues the archiving process.

None.

EQQFJKFI

ARCHIVING COMPLETED FOR: JOBNMID

The archiving process, delayed for ’retry’ or ’delay’ reason, is finally completed.

None.

None.

EQQFJKGW

ARCHIVING FAILED FOR: JOBNMID. JOB REQUEUED TO FAILD

The job identified by JOBNMID exceeded the maximum number of archiving attempts specified by the RETRYCOUNTER keyword. For this reason, the job is requeued to the destination FAILD.

Data store removes the job from the reserved destination queue and requeues it to the failure destination: the one specified in FAILDEST keyword.

Check the data stores EQQMLOG and EQQDUMP for messages about the problem job. Check if the delay value specified in the initial parameters is too low for the data store to complete the archiving.

Contact your system programmer to analyze the origin of the problem.

EQQFJKHI

EQQFJKHI PARSER ONLY IN PROGRESS FOR: JOBNMID

This message occurs immediately after message EQQFJKLI or EQQFJKEI. Refer to these two messages for details. This message indicates that data store handled the operinfo retrieval request associated with the specified JOBNMID (job name - job ID) by starting only the parser processing. This can occur only if STORESTRUCMETHOD(DELAYED) is set on.

Data store continues its processing. The parser process of JOBNMID is stopped and not started again until a new operinfo retrieval request is received from controller.

None.

EQQFJKIW

STOP COMMAND IN PROGRESS: VSAM FILE CHECK NOT POSSIBLE

This message occurs during the data store shutdown when the database and the JESQUEUE tasks end.

Data store continues processing. The JESQUEUE task ends with no error.

None.

EQQFJKLW

JOB: JOBNMID TOO LARGE - R&C IS ALLOWED BUT JOBLOG IS NOT STORED. JOBLOG WILL BE REQUEUED TO FAILD.

The job identified by JOBNMID is not archived because too large. For this reason, the job is requeued to the destination indicated by the FAILD variable.

Data store removes the job from the reserved destination queue and requeues it to the failure destination specified in the FAILDEST keyword.

None.

EQQFJKME

ARCHIVING FAILED FOR: JOBNMID. JOBLOG DELETED.

A writer task was unable to store the joblog for the specified job.

The joblog was deleted from the Data Store destination because unusable.

If this message is preceded by message EQQFAR2E and the REASON value is 00001000, a S001 abend has been recovered and no other action is needed. However it is not possible to restart the job mentioned in the EQQFAR2E message. Contact your system programmer to determine the QSAM abend cause. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. The cause of the problem might be a QSAM abend.

EQQFJKNE

JOB: JOBNMID MVS JOB LOG TOO LARGE. JOB LOG IS NOT STORED, NOT PARSED AND REQUEUED TO FAILD.

The job identified by JOBNMID was not archived because too large. It is the MVS part of the job log to be too large, therefore parsing is not possible. The job is queued again to the destination FAILD.

Data store removes the job from the reserved destination queue and queues it again to the failure destination specified by the FAILDEST keyword.

None. Restart and clean up cannot be performed on this job. To prevent this problem from occurring again, consider setting the MAXMVSPAGES keyword in the DSTOPTS statement.

EQQFJKWW

ARCHIVING FAILED FOR: JOBNMID. JOB REQUEUED TO FAILD.

The job identified by JOBNMID exceeded the maximum number of archiving attempts (as specified by the RETRYCOUNTER keyword). For this reason, the job is requeued to the FAILD destination.

Data store removes the job from the reserved destination queue and requeues it to the failure destination specified in the FAILDEST keyword..

EQQFL00E

JOB LOG FETCH TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE

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

The job log fetch task does not process the invalid element, but continues normal processing.

Save the Data Store job log task message log. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQFL01I

JOB LOG FETCH TASK INITIALIZATION COMPLETE

The job log fetch task has successfully completed its initialization.

Job log fetch processing is available.

EQQFL02E

JOB LOG FETCH TASK INITIALIZATION FAILED

The job log fetch task could not acquire all the resources needed for normal operation.

The job log fetch task is not started and all other active tasks are closed.

Correct the errors and restart the submit task.

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

EQQFL04E

JOB LOG FETCH ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT DQE

An abend prevented the job log fetch task from processing a queue element.

z/OS recovery/termination is requested to generate a dump. The job log fetch task attempts to continue normal processing.

Save the message log and dump data sets. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review the Data Store message log data set, the EQQDUMP data set, and the SYSDUMP data set to determine the cause of the error.

EQQFL05E

JOB LOG FETCH QUEUE POINTER IS DESTROYED. ARCQ IS LOST

The job log fetch task abended while processing elements on the DSCQ because queue chaining is invalid.

z/OS recovery/termination is requested to generate a dump. The job log fetch task attempts to continue normal processing.

Save the message log, BEX and dump data sets. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". 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.

EQQFL10E

IN XCF ENVIRONMENT BOTH DSTGROUP AND CTLMEM ARE MANDATORY

DSTGROUP and CTLMEM are not specified in the FLOPTS statement of the controller initial parameter statement. If you specify the XCFDEST parameter, they are both mandatory.

The Data Store does not start.

Correct the error and restart the Data Store.

EQQFL11E

CTLLUNAM AND DSTGROUP/CTLMEM ARE MUTUALLY EXCLUSIVE

CTLLUNAM and DSTGROUP or CTLMEM parameters are specified together in the FLOPTS statement of the controller initial parameter statement. They are mutually exclusive.

The FL task does not start.

Correct the error and restart the FL task

EQQFL12E

SPECIFY AT LEAST ONE DESTINATION.

Specify at least one of the following parameters: SNADEST, XCFDEST, or TCPDEST.

The FL task does not start.

Correct the error and restart the FL task

EQQFL13E

CONFLICT DETECTED BETWEEN CTLLUNAM AND SNADEST VALUES

The same name is specified in the FLOPTS statement for the CTLLUNAM and SNADEST parameters or for the CTLMEM and XCFDEST parameters. Home and destination must have different names.

The FL task does not start.

Correct the error and restart the FL task

EQQFL14E

SNADEST SPECIFIED IN XCF ENVIRONMENT

SNADEST and DSTGROUP or CTLEM are specified together in the FLOPTS statement of the controller initial parameter statement. They are mutually exclusive.

The FL task does not start.

Correct the error and restart the FL task

EQQFL15E

XCFDEST SPECIFIED IN SNA ENVIRONMENT

XCFDEST and CTLLUNAM are specified together in the FLOPTS statement of the controller initial parameter statement. They are mutually exclusive.

The FL task does not start.

Correct the error and restart the FL task

EQQFL16E

MORE THAN ONE DOT FOUND IN DESTINATION PARM

The value of the XCFDEST, SNADEST, or TCPDEST parameter in the FLOPTS statement is not valid because it contains more than one dot (period) The period divides the Tracker by Data Store destination names and there must be only one.

The FL task does not start.

Correct the error and restart the FL task

EQQFL17E

AT LEAST ONE DOT MUST BE SPECIFIED IN DESTINATION PARM

The value of the XCFDEST, SNADEST, or TCPDEST parameter in the FLOPTS statement is not valid because it does not contain a dot (period). The period divides the Tracker by Data Store destination names and there must be a minimum of one.

The FL task does not start.

Correct the error and restart the FL task

EQQFL18E

NO DESTINATION NAME FOUND FOR TRACKER TRACKER

The Controller has requested a job log from the Data Store, but the Tracker destination name is not specified in the XCFDEST, SNADEST, or TCPDEST parameter of the FLOPTS statement.

The request fails.

Correct the XCFDEST or SNADEST parameter and restart the Data Store.

If you changed the data store destination name, specify both the old and new destination names in the FLOPTS statement. For further information, refer to the tracker and data store considerations in the Migrating section of the Installation Guide.

EQQFL19I

DATA STORE DST IS INACTIVE

The Controller has requested a job log, but the Data Store destination specified in the XCFDEST, SNADEST, or TCPDEST parameter of the FLOPTS statement is currently inactive.

The request fails.

Start the appropriate Data Store and resubmit the request.

EQQFL21E

ERROR CREATING DB END WRITE QUEUE

An internal Joblog Fetch task error occurred when constructing an internal queue.

The Joblog Fetch task ends abnormally.

Save the scheduler Pre Submitter task message log. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQFL22E

ERROR CREATING DB DELETE EVENTS QUEUE

An internal Joblog Fetch task error occurred when constructing an internal queue.

The Joblog Fetch task ends abnormally.

Save the scheduler Pre Submitter task message log. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQFL23E

UNEXPECTED LOCAL DATASTORE SUBTASK END

The Joblog Fetch task detected a failure in the local data store.

The Joblog Fetch task ends abnormally.

If the problem persists, save the message log and dump data sets.If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

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

EQQFL24E

ERROR CREATING CP16 QUEUE FOR FL SUBTASK

An internal Joblog Fetch task error occurred during construction of an internal queue.

The Joblog Fetch task ends abnormally.

Save the scheduler Pre Submitter task message log. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQFL25E

ERROR ADDING OPERATION TOKEN TO BE DELETED

An internal Joblog Fetch task error occurred during an operation on an internal queue.

The Joblog Fetch task ends abnormally.

Save the scheduler Pre Submitter task message log. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQFL26E

ERROR DURING OPERINFO CHECK FOR OP TOKEN:OPTOK

The Joblog Fetch task detected a failure while trying to delete a sysout in the local data store. The sysout belongs to the occurence identified by the token OPTOK. The RC return code indicates the kind of error:
  • * = 4 → the sysout was not found
  • * > 4 → an internal error occurred
The cleanup of a local data store is the consequence of a current plan extend or a current plan replan and its start and end is identified by the messages EQQFL28 and EQQFL29. The sysout to be deleted are the ones associated to the occurrences removed by the current plan batch run.

The Joblog Fetch task continues processing.

If RC > 4 are detected, save EQQDUMP and EQQMLOG. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer if RC > 4 are detected .

If RC > 4 are detected, check EQQMLOG and EQQDUMP to find further error messages.

EQQFL27E

ERROR DURING OPERINFO CHECK FOR OP TOKEN OPTOK

An internal Joblog Fetch task error occurred while an internal queue was being processed.

The Joblog Fetch task ends abnormally.

Save the scheduler message log. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQFL28I

LOCAL DATA STORE CLEANUP STARTED

The Joblog Fetch task started the local data store cleanup process. The cleanup of local data store is the consequence of a current plan extend or current plan replan and its start and end is identified by the messages EQQFL28 and EQQFL29. The sysout to be deleted are the ones associated to the occurrences removed by the current plan batch run (the completed ones).

The Joblog Fetch task continues the processing.

None.

None.

EQQFL29I

LOCAL DATA STORE CLEANUP ENDED. NUMBER OF OCCURENCE SUCCESSFULLY PROCESSED: SYS

The Joblog Fetch task ended the local data store cleanup process. The number of occurence whose sysout were successfully deleted is indicated by the SYS value. The cleanup of local data store is the consequence of a current plan extend or current plan replan and its start and end is identified by the messages EQQFL28 and EQQFL29. The sysout to be deleted are the ones associated to the occurrences removed by the current plan batch run (the completed ones).

The Joblog Fetch task continues the processing.

None.

None.

EQQFL30E

UNEXPECTED ID SUBTASK END.

The ID task detected a failure in the local data store.

The ID task ends abnormally.

If the problem persists, save the message log and dump data sets. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

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

EQQFL31E

AT LEAST ONE TCPDEST KEYWORD VALUE IS INCORRECT.

The TCPDEST keyword of the FLOPTS statement contains one or more incorrectly defined TCP/IP destinations.

The processing of the current FLOPTS statement terminates with a nonzero return code. This causes the controller initialization to fail.

Review the syntax of the TCP/IP destinations specified. Remove or correct the incorrect destination, and then restart the controller.

EQQFL32E

A TRACKER DESTINATION ENTRY IS TOO LONG IN STATEMENT FLOPTS.

The tracker destination name must be not greater than 8 characters.

Processing of the TCPDEST keyword continues. Message EQQFL31E is issued when all destinations have been processed.

Either remove or correct the invalid destination and restart the subsystem.

EQQFL1AE

UNEXPECTED FN SUBTASK END

The FL task has detected an unexpected end of FN subtask.

The FL task ends in error.

If the error persists, save the message log and dump data sets and contact the 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

EQQFSD0E

SYSOUT DATABASE INITIALIZATION FAILED

The initialization of the sysout data base task failed.

If the task is started by data store, data store ends. If the task is started by the controller, FL task is ended.

Check the previous messages in the EQQMLOG to get more information (for example the message EQQFSF0E).

EQQFSD1I

SYSOUT DATABASE ERROR HANDLER TASK STARTED

The sysout database error handler task is being started.

The Data Store initialization process continues.

EQQFSD2I

SYSOUT DATABASE ERROR HANDLER TASK ENDED

The sysout database error handler task has been requested to stop and it has terminated normally.

The sysout database error handler task is terminated.

EQQFSD3E

DATABASE ERROR HANDLER DETECTED SUBTASK FAILURE

The error handler task that coordinates data file activities has detected a subtask failure.

If possible correct all errors and restart the Data Store. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems, sub-section "Information to collect for data store problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error.

EQQFSD4I

SYSOUT DATABASE STARTING

The sysout database is being started.

The Data Store initialization process continues.

EQQFSD5I

SYSOUT DATABASE INITIALIZATION COMPLETE

The sysout database has successfully completed its initialization.

The sysout database is now active.

EQQFSD6I

SYSOUT DATABASE TERMINATING

A stop request was issued to close the sysout database.

The sysout database is shut down.

EQQFSD7I

SYSOUT DATABASE STOPPED

A stop request was accepted and completed by the sysout database.

The sysout database is now stopped.

EQQFSD8W

WARNING MESSAGES WERE ISSUED DURING OPERATION ON DATA FILE DATAFILE

This message is displayed during the close process of the Data Store and indicates that an error was found during an operation on the DATAFILE data file.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine which operation failed or the cause of the error.

EQQFSD9E

DATAFILE NUMBER MISMATCH: DATFILE NUM:DNUMDATAFILE MAX NUM:MNUM

Data store detected a datafile number mismatch during initialization phase. The primary key information(MNUM) does not match with the number of data files (DNUM)

Data Store stops the processing and terminates.

Check if the JCL used to start data store has the correct number of data file specified: if it doesn’t, change the JCL and restart.

Contact system programmer to find the origin of mismatch.

EQQFSDAE

UNSTRUCTURED DATA REQUIRED BUT NO UDFxx VSAM FILE HAS BEEN SPECIFIED

Data store initialization failed because STOUNSD(Y) was specified (for joblog retrieval) but the started task JCL did not include any unstructured vsam file (identified by ddname UDFxxx).

Data store stops processing.

Allocate and add the UDFxx VSAM files, then restart data store.

EQQFSDBE

STRUCTURED DATA REQUIRED BUT NO SDFxx VSAM FILE HAS BEEN SPECIFIED

Data store initialization failed because no structured VSAM file was specified in the started task JCL. Structured VSAM files (identified by ddname SDFxx) are always required.

Data store stops processing.

Allocate and add the SDFxx VSAM files, then restart data store.

EQQFSF0E

OPEN FAILED FOR DDN FUNCTION: FUNC REASON: SS

A Data store SYSOUT database task tried to open the data file identified by the ddname DDN but detected an error: the specific macro used is explained by FUNC while the reason code returned by the macro is specified in SS.

If the task is started by data store, data store ends. If the task is started by the controller, the FL task is ended.

Check the meaning of the macro reason code. For example, the specified data file could be already used by another data store or the started task JCL could contain a duplicate ddname.

EQQFSF1I

DATA FILE DATAFILE INITIALIZATION COMPLETED

The initialization process of the DATAFILE data file task was completed successfully.

The DATAFILE data file can be used to store sysout data.

EQQFSF2I

DATA FILE DATAFILE TERMINATION COMPLETED

The DATAFILE data file task termination process has been completed.

The DATAFILE data file is closed.

EQQFSF3E

UNABLE TO ALLOCATE AND FORMAT SPACE MAP

An error occurred when allocating storage to build and format the space map.

Data Store initialization is stopped.

The allocation in the data file is too small (a minimum of two tracks is needed). Correct the values in the allocation JCL, reallocate the data file and restart the Data Store.

EQQFSF4W

INVALID PAGE - FILENUMRBN

During cleanup an invalid page was detected for one of the following reasons:
  • the RBN is out of range
  • the page status is deleted, but the corresponding bit of the space map is on.

The message shows the data file number FILENUM and the RBN stored in the page prefix.

The cleanup resets the corresponding bit of the space map.

EQQFSF5W

UNABLE TO EXTEND DATA FILE DATAFILE- DATA FILE DISABLED

An error occurred when trying to extend the data file number DATAFILE.

The data file was flagged as disabled and cannot be used to store sysout data. The store operations continue on the next available data file. If no more data files are available, no more sysout could be stored.

Perform one of the following actions:
  • To make more space available, shorten the cleanup task interval (CINTERVAL)
  • Stop the data store, increase the size of the current data store files, and restart the data store.
  • Allocate additional data files and restart the data store.

EQQFSF6I

UNABLE TO COMPLETE SAVE OPERATION - DATA FILE DISABLED SAVE WILL BE RETRIED

This message is issued by the sysout DB task, which is a data store task started also by the controller when the restart and cleanup function is activated. It occurs when the storing in the data file of the JOBLOG or structured info failed due to problems occurred during the I/O phase (for example when the data file is full).

The archiving will be retried later.

Check the EQQMLOG to find messages that may explain the origin of the problem.

EQQFSF7W

NO MORE DATAFILE AVAILABLE TO STORE JOBLOG

An error occurred when trying to extend the data file. This message is sent when the datafile is the last one.

No more datafile available.

Allocate additional datafile and restart the Data Store.

EQQFSF8E

DATA FILE DDNAME HEADER PAGE FILE NUMBER FILNUM MISMATCH

This message is issued when, at start time, the data store database subtask finds incongruent information in the header page of the data file identified by the ddname specified by DDNAME. The incorrect information is the data file identifier number FILNUM.

Data store stops processing and terminates.

Check the data store started procedure JCL to see which is the data file associated with the specified DDNAME. Check which are the data files that have the same FILENUM printing the header page of all used data files. Check if among these data files there are data files used by another data store: This cannot be done.

EQQFSF9W

UNABLE TO STORE DATATYPE DATA, FILES ARE FULL

Sysout data was to be stored on the data store data files but there was not enough free space. DAYTATYPE is SDF for structured, UDF for unstructured data.

Data store continues its processing.

Check the MAXSTOL parameter of the DSTOPTS data store initialization statement giving the number of user SYSOUT files that can be stored. If correctly specified, allocate more space to the EQQUDFnn files or the EQQSDFnn files, or specify a cleanup policy that prevents the files from filling up.

Messages EQQFJK1I or EQQFJKGW following message EQQFSF9 in the data store message log give the jobname and jobid of the job for which sysout data failed to be stored.

EQQFSI1I

SECONDARY KEY FILE INITIALIZATION COMPLETED

The initialization process of secondary key file task completed successfully.

The secondary key file can now be used to store sysout data.

None.

EQQFSI2I

SECONDARY KEY FILE TERMINATION COMPLETED

The secondary key file task termination process has completed.

The secondary key file is now closed.

None.

EQQFSI3I

GENERIC I/O ERROR DURING OPEN VSAM FILE

The macro returns an error during an OPEN operation.

The data store closes.

If possible, correct all errors, then restart data store. If the error persists, contact the Software Support.

Contact your system programmer.

Review earlier messages in the data store message log and the SYSLOG data sets to determine the exact reason for this message. One possibility is that the user has an insufficient authorization to the VSAM file.

EQQFSK1I

PRIMARY KEY FILE INITIALIZATION COMPLETED

The initialization process of the primary key file task was completed successfully.

The primary key file can be used to store sysout data.

EQQFSK2I

PRIMARY KEY FILE TERMINATION COMPLETED

The primary key file task termination process has been completed.

The primary key file is closed.

EQQFSK3I

GENERIC I/O ERROR DURING OPEN VSAM FILE

A VSAM Open operation failed.

The Data Store is terminated.

If possible correct all errors and restart the Data Store. If the error persists, contact the Software Support.

Contact your system programmer.

Review earlier messages in the Data Store message log and SYSLOG data sets to determine the cause of the error. One possibility is that you have insufficient authorization on that VSAM file.

EQQFSR0E

DATA STORE READER TASK INITIALIZATION FAILED

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

The reader task is not started.

Correct the errors and restart the submit task.

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

EQQFSR1I

DATA STORE READER TASK INITIALIZATION COMPLETED

The reader task has successfully completed its initialization.

Reader processing starts.

None.

EQQFSR2I

DATA STORE READER TASK ENDED

The reader task has been requested to stop and is terminating normally.

The reader task is terminated.

None.

EQQFSR3I

DATA STORE IS ATTEMPTING TO COMMUNICATE WITH CONTROLLER

During a retrieval request processing, communication was lost between the Controller and the Data Store. The Data Store retries three times, at 5-second intervals, to retransmit the joblog.

None

If the error persist, check the reason for the communication failure.

EQQFSR4I

JOB JOBNMID NOT FOUND NEITHER IN DATA STORE NOR IN JES QUEUE

The Reader Task has received a request for a job that is not stored either on Data Store or on the JES queue. It may happen if the job log has not been copied into the scheduler destination (see value specified both in DSTDEST parameter of RCLOPTS controller initialization statement and SYSDEST parameter of DSTOPTS data store initialization statement). Possible reasons of the failure:
  • a JCL error produces a log which cannot be copied in the scheduler destination (e.g. incomplete job log)
  • a job is tracked by scheduler but submitted outside, for example Event-Triggered Tracking (ETT with "job-name replace" option set to Y). In any case the Reader Task is unable to return the requested job.

The job log retrieval request fails.

Correct the JCL to avoid the error. In case of ETT, you can manually route the job log from the local to the scheduler destination.

EQQFSR5I

TIMEOUT REACHED DURING SEARCH OF JOB: JOBNMID

The job log retrieval request reached the maximum allowed time (see QTIMEOUT statement). The reader is unable to return the requested job.

The job log retrieval request fails.

EQQFSR6I

SOME PROBLEMS OCURRED IN WRITE PHASE FOR JOB: JOBNMID, RETRY LATER

An internal error was detected during database write phase. Data store was unable to return the job log identified by JOGNMID.

The job log retrieval request fails.

Check the writer failure reason.

EQQFSR7I

UNSTR DATA FOR JOB JOBNMID REQUEST BUT NOT ON DB DUE TO INIT PARAM

The data store reader task is unable to retrieve requested unstructured data because it can not be stored in the data store database. This because the DSTOPST STOUNSTR(N) option is not specified.

The reader task is unable to retrieve JOBLOG but continues processing.

If you want to retrieve JOBLOG, you must specify the DSTOPTS STOUNSTR(Y) option in your data store initialization parameters

EQQFSR8I

UNABLE TO RETRIEVE JOB JOBNMID

Data store reader task is unable to retrieve requested joblog.

The reader task is unable to retrieve JOBLOG but continues processing.

If the problem persists, save the message log and dump data sets, then contact the Software Support.

Contact your system programmer.

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

EQQFSW1I

DATA STORE WRITER TASK INITIALIZATION COMPLETED

The writer task has successfully completed its initialization.

Writer processing starts.

None.

EQQFSW2I

DATA STORE WRITER TASK ENDED

The writer task has been requested to stop and is terminating normally.

The writer task is terminated.

None.

EQQFSW3I

DATA STORE WRITER TASK ENDED DUE TO AN ERROR

The writer task has been abnormally stopped.

The writer task is terminated.

Correct the errors shown by the earlier messages and restart the indicated task.

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

EQQFSW4I

JOB: JOBNAME- JOBNAME(DDN) INVALID SYSOUT

The writer has received an empty data set (dynamically allocated). DDN is returned to JES, but is always equal to JESMSGLG for the three DSIDs of the job log. This message is displayed once for each DSID found for the job.

The writer task skips to another job log that is to be stored.

None.

EQQFSW5W

JOB: JOBNMID INCOMPLETE JOBLOG: OPERINFO NOT GENERATED

Data store handled an incomplete MVS joblog: not all of the 3 MVS sysouts (JESMSGLG, JESJCL and JESYSMSG) were received. Data store needs all the 3 MVS sysouts to build the structured information (operinfo): it will not be built.

Only unstructured information is stored.

None.

EQQFSW6W

JOB: JOBNMID JOBLOG PARSING ERROR: OPERINFO NOT GENERATED. REASON: STRURSN

This message is issued by the Writer task of Data store when the joblog parsing fails and structured info cannot be built. The related job is identified by JOBNMID and the reason for failing is explained by STRURSN.

The structured information is not produced. If requested to do so, the unstructured joblog is archived. The job is deleted from the destination queue.

Check STRURSN to understand the cause of the error.

EQQFV00E

DUPLICATE NAMES IN THE DSTOPTS SNA DESTINATIONS

A minimum of one name in the SNA keyword destination list of the DSTOPTS initialization statement is a duplicate of a previously-specified name. These names are the application names of potential session partners and must be unique.

FN processing is terminated.

Correct the name (or names) in error and restart the subsystem.

EQQFV01I

FN APPLICATION STARTED

The FN task has received control from the Data Store subsystem and is soon to start initialization processing.

FN processing continues.

None.

EQQFV02E

FN APPLICATION TERMINATED - SETLOGON EXECUTION FAILURE

A VTAM® SETLOGON macro used for enabling FN logon processing has failed. The reason for this error is defined in detail by message EQQFV15E that precedes this message in the message log.

FN processing is terminated.

Correct the error (or errors) and restart the subsystem.

Review message EQQFV15E to determine the cause of the error.

EQQFV05E

FN APPLICATION TERMINATED - INITIALIZATION PROCESSING FAILURE

FN initialization processing failed. Messages that are issued preceding this message define the cause of the error.

FN processing is terminated.

Correct all errors and restart the subsystem.

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

EQQFV06I

FN APPLICATION ENDED

FN processing has completed and control is returned to the HCL Workload Automation for Z subsystem.

FN processing is terminated.

None.

EQQFV07E

INITIALIZATION FAILED - SNA DESTINATION NOT SPECIFIED IN FLOPTS

In a Controller system, FN initialization processing failed because no partner application IDs were specified in the SNA keyword of the FLOPTS statement.

FN processing is terminated.

Add the missing information and restart the subsystem.

EQQFV08I

INITIALIZATION FAILED - SUBSYSTEM STOP REQUESTED

FN received a subsystem stop request while in the initialization phase. FN was most likely waiting for some other HCL Workload Automation for Z resource to become active.

FN processing is terminated.

None.

EQQFV09E

INITIALIZATION FAILED - CTLLNAM KEYWORD NOT SPECIFIED OR INVALID

FN initialization processing failed because the CTLLUNAM keyword was not specified or was invalid.

FN initialization processing is terminated.

Add the missing information and restart the subsystem.

EQQFV10E

NIB BUILD PROCESSING FAILED - R15 = R15 R00 = R00

The GENCB macro request that was issued to generate a NIB block did not complete normally.

FN processing is terminated.

If insufficient main storage was the cause of the error, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the error, contact the Software Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM® product installed on this system.

EQQFV11E

RPL BUILD PROCESSING FAILED - R15 = R15 R00 = R00

The GENCB macro request that was issued to generate an RPL block did not complete normally.

FN processing is terminated.

If insufficient main storage was the cause of the error, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the error, contact the Software Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this system.

EQQFV12E

NIB EXSLT BUILD PROCESSING FAILED - R15 = R15 R00 = R00

The GENCB macro request that was issued to generate a NIB EXLST block did not complete normally.

FN processing is terminated.

If insufficient main storage was the cause of the error, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the error, contact the Software Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this system.

EQQFV13E

ACB EXSLT BUILD PROCESSING FAILED - R15 = R15 R00 = R00

The GENCB macro request that was issued to generate an ACB EXLST block did not complete normally.

FN processing is terminated.

If insufficient main storage was the cause of the error, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the error, contact the Software Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this system.

EQQFV14E

ACB BUILD PROCESSING FAILED - R15 = R15 R00 = R00

The GENCB macro request that was issued to generate the FN ACB did not complete normally.

FN processing is terminated.

If insufficient main storage was the cause of the error, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the error, contact the Software Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this system.

EQQFV15E

VTAM MACRO REQUEST FAILURE - DIAGNOSTIC INFORMATION: NODE= NODE, REQUEST= X'REQ' (NAMEREQ), RTNCD= X'RC' (DECRC) FDBK2= X'FDBK2' (DFDBK2), SSENSMI= SMI, USENSEI= USEI, SSENSEI=SSEI R00= X'R00', R15= X'R15'

An error occurred when a VTAM request was executed or scheduled. The variable items in the message provide diagnostic information and have the following meanings:
NODE
FN application LU-name
REQ
VTAM request code in hexadecimal
NAMEREQ
VTAM request name
RC
RTNCD feedback field value from RPL in hexadecimal
DECRC
RTNCD feedback field value from RPL in decimal
FDBK2
FDBK2 feedback field value from RPL in hexadecimal
DFDBK2
FDBK2 feedback field value from RPL in decimal
SMI
System sense modifier information from RPL
USEI
User sense information from RPL
SSEI
System sense information from RPL
R00
Register 0 return code after a VTAM macro request
R15
Register 15 return code after a VTAM macro request.

The action taken depends on the severity of the error situation. If at all possible, FN tries to continue processing. For the most serious errors, for example, undefined feedback code, FN abends with a dump and user code.

Analyze the diagnostic information and the dump (if produced) to determine the cause of the error. If this was not a user error, contact the Software Support.

Use the diagnostic information in the message to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on the system.

EQQFV16E

NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE NOT FOUND

The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE could not be found. The most likely reasons for the failure is:
  • A LU-name is specified incorrectly in the CTLLUNAME keyword of the DSTOPTS initialization statement
  • the name NODE has not been properly defined to VTAM.

The FN processing is terminated.

Review the name specified in the CTLLUNAME keyword. Make sure that it is correct and that a counterpart exists in the VTAM definition statements. Correct the items in error and restart FN.

EQQFV17E

NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE NOT ACTIVE

The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE was not active.

The FN processing is terminated.

Investigate why NODE is inactive. Restart FN when NODE is active again.

EQQFV18E

NAMEREQ REQUEST FAILURE - VTAM ERROR, OR NCP/VTAM INCOMPATIBILITY

The VTAM NAMEREQ request failed to complete successfully because there was an error in VTAM or an NCP/VTAM incompatibility. This message is preceded by message EQQFV15E in the HCL Workload Automation for Z message log.

The FN processing is terminated.

Restart FN when the VTAM errors have been corrected.

Refer to message EQQFV15E to determine the cause of the failure.

EQQFV19E

SESSION SETUP FAILED - PLU=LU NOT AVAILABLE

The FN has not been able to establish a session for one of the following reasons:
  • The controller is not started.
  • The FN task in the controller is not available.
  • The LU specified in the CTLLUNAME keyword of the DSTOPTS initialization is not active or is not defined.
The FN retries every 10 seconds until it is successful, until the subsystem is stopped, or until the FN is deactivated.

The FN continues to attempt to establish the LU-LU session.

Review the name specified in the CTLLUNAME keyword of the DSTOPTS initialization statement and make sure that it is the correct one. If it is correct, ask the system operator at the controller system to activate the required resource.

EQQFV20I

ACB SUCCESSFULLY CLOSED

The FN has been successfully disconnected from VTAM.

The FN termination processing continues.

None.

EQQFV21W

UNABLE TO CLOSE ACB

The FN is unable to successfully disconnect from VTAM.

The FN termination processing continues even though the ACB could not be closed.

Contact your VTAM administrator.

It is most likely that a VTAM error has caused this error. Check the system log for VTAM error messages that can be related to this failure.

EQQFV22E

LOGON ATTEMPTED BY UNDEFINED LU/APPLICATION LU- CLSDST ISSUED

A session establishment attempt was made by a remote FN application unknown to this host HCL Workload Automation for Z subsystem. This message is issued only for a FN application at a HCL Workload Automation for Z host.

The FN task turns down the request for the session by issuing a CLSDST macro. Processing continues for the HCL Workload Automation for Z host FN application.

Stop the FN task for which erroneous specifications have been given. Correct the specifications in the DSTOPTS statement and restart the FN.

It is most likely that a name in the DSTOPTS SNA keyword list of names has been misspelled or left out entirely.

EQQFV23E

LOGON REQUEST FOR LU/APPLICATION LU THAT IS ACTIVE - CLSDST ISSUED

Data store/FN task connection was attempted, but the session is already active.

The request for a session is turned down and FN task process continues.

Stop the controller, data stores, and trackers that have incorrect definitions. Correct them, specifying a different LU-name and restart them.

The most likely reason for this error is that more the same LU-name was used to define more data stores or SNA connected trackers. Check both the controller FLOPTS definitions (CTLLUNAM, SNADEST), the data store DSTOPTS definitions (DSTLUNAM, CTLLUNAM) and the tracker OPCOPTS definitions (NCFAPPL).

EQQFV24I

ACB SUCCESSFULLY OPENED

The FN has successfully established contact with VTAM and is ready for further VTAM processing.

The FN processing continues.

None.

EQQFV25I

ACB OPEN FAILURE (RC=X'RC') - VTAM SHUTTING DOWN

The FN was unable to establish contact with VTAM because of an OPEN ACB failure. RC is the ACB error flag value in hexadecimal.

The FN continues processing.

None.

EQQFV26E

ACB OPEN FAILURE (RC=X'RC') - FN IMPROPERLY DEFINED

The FN task was unable to establish contact with VTAM because of an OPEN ACB failure. RC is the ACB error flag value in hexadecimal.

The FN processing is terminated.

Correct the problem and restart HCL Workload Automation for Z.

Use the return code to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQFV27E

ACB OPEN FAILURE (RC=X'RC') - ABEND 1104 DUE TO SERIOUS ERROR

The FN was unable to establish contact with VTAM because of an OPEN ACB failure. RC is the ACB error flag value in hexadecimal.

The FN processing is abnormally terminated with a dump (abend code 1104).

Analyze the 1104 abend dump. If this was not a user error, contact the Software Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQFV28W

ACB OPEN FAILED FOR THE LAST 2 MINUTES - VTAM NOT ACTIVE

The FN failed to establish contact with VTAM during the last two minutes because VTAM was not active. This message is issued every two minutes until contact is made.

The FN continues to attempt to establish contact with VTAM until contact is made or until the HCL Workload Automation for Z subsystem is stopped.

Ask your network operator to activate VTAM.

EQQFV29I

VTAM TERMINATION, OR FN DEACTIVATION, STOPPED SESSION SETUP ATTEMPTS

Session initiation attempts were stopped because VTAM is terminating or the FN task was deactivated.

The FN termination processing continues.

None.

EQQFV31I

SUBSYSTEM STOP REQUEST TERMINATED SESSION SETUP ATTEMPTS

A remote FN application was in the process of initiating a session when the subsystem was stopped.

The FN termination processing continues.

None.

EQQFV32I

SUBSYSTEM STOP REQUEST TERMINATED ACB OPEN ATTEMPTS

The FN was in the process of establishing contact with VTAM when the subsystem was stopped.

The FN termination processing continues.

None.

EQQFV33E

ACB OPEN FAILED FOR THE LAST 2 MINUTES - FN APPLICATION NOT ACTIVE

The FN failed to establish contact with VTAM during the last two minutes because the FN application was not activated. The FN attempts to establish contact every 10 seconds until contact is made. This message is issued every two minutes until contact is established.

The FN continues to attempt to establish contact with VTAM until contact is made or until the scheduler subsystem is stopped.

Ask the network operator to activate the VTAM LUs.

EQQFV34E

NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE INHIBITED

The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE was inhibited. The most likely reason for the failure is that either the cross-domain FN partner NODE has been deactivated or the partner VTAM system has been taken down.

If NAMEREQ is the REQSESS request, the FN continues processing with session establishment attempts every 10 seconds. For other VTAM requests, FN processing is terminated.

Ask the network operator to activate the VTAM or FN application, or both applications, on the cross-domain partner system.

EQQFV36I

SESSION HOME-DEST ESTABLISHED

A session has been established between the home application HOME and the destination application DEST.

The FN continues processing.

None.

EQQFV37I

SESSION HOME-DEST ENDED

The session between the home application HOME and the destination application DEST has ended.

The FN continues processing.

None.

EQQFV41E

THE FN TASK IGNORED THE FOLLOWING ELEMENT ON THE FN QUEUE DQE

An invalid element has been found by the FN task. Possibly, the first four bytes of the element do not match the HCL Workload Automation for Z character string 'DQE'. (The fourth byte is a blank space.)

The FN task no longer processes the element, but continues normal processing.

Save the HCL Workload Automation for Z message log data set containing this error message and contact the Software Support.

EQQFV42E

THE FN TASK IGNORED THE FOLLOWING DATA, RECEIVED FROM 'NODE' DQE

The FN task did not recognize the type of data received from the application. This message is issued once for every invalid receive operation.

The FN task continues processing

Verify that the session parameters specified in the VTAM LOGMODE table are valid. Especially check that the ru-sizes are not zero.

If this message occurs during normal execution and the VTAM LOGMODE definitions are correctly specified, contact the Software Support.

EQQFV43E

INVALID RU-SIZE SPECIFIED IN 'LU' SESSION PARAMETERS

The ru-sizes specified in the session parameters are not valid.

The FN continues processing, but the specified session is not established.

Verify that the ru-sizes specified are valid. If necessary, specify different ru-sizes, and stop and restart the FN task.