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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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 Data Store has received a command while closing all the subtasks.

The modify command is syntactically incorrect.

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.

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

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

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

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

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 command could not be processed because one or more parameters on that command could not be recognized or are out of range.

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.

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.

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.

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

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

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.

During an ACB generation, the macro returns an error.

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

During an Open operation, the macro returns an error.

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

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.

A Data Store subtask ended unexpectedly.

There was an error during a Dynalloc operation.

There was an error during a Dynalloc operation.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

The CTLPORTNUMBER parameter is invalid or missing.

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

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

All active writer subtasks are now closed.

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

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

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

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

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.

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.

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

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

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

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

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

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

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 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 QTIMEOUT (timeout system reader) parameter was invalid or not specified. The timeout system reader was defaulted to 15.

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

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.

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

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

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

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

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

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

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

The diagnose trace for subtask TASKNAME has been activated

The diagnose trace for subtask TASKNAME has been deactivated.

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

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.

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

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.

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.

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

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

The Communication task has successfully completed its initialization.

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

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

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

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

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

The XCF Controller member MEMBER is offline.

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

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

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 ID task started the initialization process.

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

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

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

The command task has been successfully attached.

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

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

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

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

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

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

The Data Store has detected an invalid modify command.

The modify command is syntactically incorrect.

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

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

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

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 cleanup task is in a quiescent status and is waiting until the cleanup interval time has elapsed.

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

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

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

The program that executes the batch utilities is terminating normally.

No operand is specified in the CMDPAR member.

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

The CMDPAR parameter is not allowed for this statement.

An error was found in the CMDPAR initial parameter member.

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

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

The import batch utility found an empty import file.

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.

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 first record of an input file found by the import batch utility is not an header record.

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

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.

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

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

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

The JES queue task has successfully completed its initialization.

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

The JES queue task has been abnormally stopped.

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.

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

The original class specified for the requeue operation is reserved. The requeue operation for the JOBNMID job is forced in the 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.

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 archiving process is not completed yet, but there is no real error: delay time has been reached (data retry will be performed).

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

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.

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.

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

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.

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

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.

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.

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

The job log fetch task has successfully completed its initialization.

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

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

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

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.

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

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

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.

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

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

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

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

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

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

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

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

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

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 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 ID task detected a failure in the local data store.

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

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

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

The initialization of the sysout data base task failed.

The sysout database error handler task is being started.

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

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

The sysout database is being started.

The sysout database has successfully completed its initialization.

A stop request was issued to close the sysout database.

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

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.

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 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 initialization failed because no structured VSAM file was specified in the started task JCL. Structured VSAM files (identified by ddname SDFxx) are always required.

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.

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

The DATAFILE data file task termination process has been completed.

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

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

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

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

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

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.

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.

The initialization process of secondary key file task completed successfully.

The secondary key file task termination process has completed.

The macro returns an error during an OPEN operation.

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

The primary key file task termination process has been completed.

A VSAM Open operation failed.

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

The reader task has successfully completed its initialization.

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

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.

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

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

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.

Data store reader task is unable to retrieve requested joblog.

The writer task has successfully completed its initialization.

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

The writer task has been abnormally stopped.

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.

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.

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.

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.

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

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 initialization processing failed. Messages that are issued preceding this message define the cause of the error.

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

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

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 initialization processing failed because the CTLLUNAM keyword was not specified or was invalid.

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

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

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

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

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

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

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 has been successfully disconnected from VTAM.

The FN is unable to successfully disconnect from VTAM.

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.

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

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

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 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 was unable to establish contact with VTAM because of an OPEN ACB failure. RC is the ACB error flag value in hexadecimal.

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.

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

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

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

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

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

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

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 did not recognize the type of data received from the application. This message is issued once for every invalid receive operation.

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