The statements for creating an application description (AD) have been received. Syntax checking has revealed no error.

The statements for creating an operator instruction (OI) have been received. Syntax checking has revealed no error.

Before the PQ83269 APAR there was a limitation in the design of the batch loader for which it was allowed to have only one options statement in the sysin file and this should have been the first not commented card. This design limitation was not reflected in a consistent way in the code. With the PQ83269 APAR it is now allowed to have more options statements in the sysin file, with the rule that the following not commented card must be another options card or an ADSTART or an OISTART. If the sysin file does not comply with this rule, the new EQQV003E message is issued.

No more statements remain to be processed. The highest return code set when processing the statements is RC.

A file required for validation of the created records cannot be opened. For validation of application descriptions, a file with workstation descriptions and calendar descriptions is required (ddname EQQWSDS). For validation of operator instructions, a file with application descriptions is required (ddname EQQADDS). These files are required only if the output is directed to a VSAM file.

The ADSTART and OISTART statements start up the creation of a record. After ADSTART is entered, only an application description (AD) details statement or another ADSTART or OISTART statement is allowed. After an OISTART statement, only an OIT statement or another ADSTART or OISTART statement is allowed. MSTM is an ADSTART or OISTART statement; STM is a details statement.

The statement parser has detected an error in statement STM.

This statement is for the same record as an earlier statement in which an error was detected.

The program interface request to INSERT application ADID into the current plan failed.

The validation of the output data cannot be suppressed when the output data from the batch loader goes to a HCL Workload Automation for Z subsystem.

No validation of output data is performed when ACTION(SCAN) is specified. By ACTION(SCAN), a check is done (on the batch loader statements) to verify that keywords are correctly specified and that the required values are set. No output data is produced and no consistency checking is done.

The character format for the application ID and owner ID used in the HCL Workload Automation for Z subsystem is used by the batch loader when the output is directed to a subsystem.

Two different subsystem names are specified.

You can specify the ADRULE control statement only for run cycles with type R (Regular rule) or E (Exception rule).

You can specify only one ADRULE control statement for each run cycle.

The ADRUN control statement specifies type R (Regular rule) or E (Exception rule), but there is no ADRULE statement.

The ADRULE control statement for run cycle VADRN contains an error. Messages that precede this message give more details about the error.

The length specified in the ADRIRDLEN field is not the same as the length in the ADRULEL field of the rule.

The RGRUN control statement is missing an ADRULE statement.

The ADRULE control statement for run cycle VADRN contains an error. Messages that precede this message give more details about the error.

The length specified in the RGRIRDLEN field is not the same as the length in the RGRULEL field of the rule.

The control block BLOCK contains an error at offset POS.

The value for the SHSIGN keyword is incorrect. Enter B (for a negative shift) or F (for a positive shift).

In the OPTIONS statement, ADVALFROMCHG(Y) cannot be specified if the ACTION is ADD. ADVALFROMCHG(Y) is allowed only with ACTION(REPLACE) and ACTION(SCAN).

In the OPTIONS statement, ADVALFROMCHG(Y) cannot be specified if the STATUSCHANGE is Y. ADVALFROMCHG(Y) is allowed only with ACTION(REPLACE) and ACTION(SCAN).

The keyword KEY has no significance in the current environment.

When ACTION(SETDEF) is specified, KEY cannot be specified.

You did not specify the required keyword. The keyword KEY is a required keyword and cannot be omitted.

You specified an invalid value for the keyword. The keyword KEY can have only a certain set of values or abbreviations of these values.

The value of the keyword KEY is abbreviated so that it matches more than one of the valid values.

If you specify REMPORTNUMBER in the INIT statement, you must specify also REMHOSTNAME in the same statement. Or, if you specify REMPORT directly in the PIF program initialization, you must specify also REMHOST in the same program.

The character field that is specified as a keyword value is too long.

The integer value that is specified as a keyword value is too large.

You specified an incorrect value VAL for keyword KEY in statement STMT.

Keyword KEY is missing in statement STMT.

KEY and LUNAME are mutually exclusive keywords.

LUNAME parameter cannot be specified together REMHOST parameter, because they correspond to different communication protocols.

You specified REMHOST and REMPORT values in both EQQYPARM and EQQYRPRM.

The value of the field FLD in a program interface control block is required to be in a certain range. A value outside this range is detected when a database record is created from the control block.

The value of the field FLD of a program interface control block is required to have one of the values shown in the message. Another value is detected when a database record is created from the control block.

The specified REMHOST exceeds the allow length.

The value specified for keyword KEYWD is incorrect.

The application description or operator instruction already exists.

When applications with the same application ID, but different valid-from dates are specified, only four different dates can be specified.

When you specify the input day for an application, you must also specify the input arrival time. When you specify the deadline day for an application, you must also specify the deadline time. KEY indicates which of these times is missing.

An ADDEP statement that does not identify any predecessor operation is received from the input file.

An application has been written with temporary information in the external predecessor section. It is now to be updated by the correct predecessor information, predecessor operation number or the workstation name, or both. The update fails because the predecessor section cannot be identified. The application might have been modified since it was written by the batch loader.

An application that references a group definition for run cycle information cannot itself contain run cycles.

A group definition cannot contain operations.

A group definition cannot contain predecessor operations.

The application can only be selected NUM times for one run cycle.

The PIF called the EQQUXPIF checks to validate the operation type about the resourceresource. type can assume the value REPLACE or INSERT. resource can only be AD. The exit rejected the request and the reason for this is specified into the string reason. This string is filled up by the exit with any value customer decides to put in it (limit is of 80 characters).

You cannot specify system automation information to a group definition.

The possible inconsistencies met during the process could have been removed during the second scan, which was run because the OPTIONS parameter is set to MSGLEVEL(3).

No operation in the predecessor application matches the specification given in the message text. A blank means that no value is specified. A predecessor operation can be specified by workstation name, operation number, or job name, or by any combination of the three items. If the predecessor is required by another application or another occurrence of the same application, an application ID is also required.

More than one operation in the predecessor application matches the specification given in the message text. A blank means that no value is specified. A predecessor operation can be specified by workstation name, operation number, or job name, or by any combination of the three items. If the predecessor is required by another application or another occurrence of the same application, an application ID is also required.

An application has been written to the database with temporary predecessor information. The update of the predecessor section, to add the correct information, has failed.

A new application description overlaps the validity period of an existing application description. You tried to adjust the validity of the existing version to the day before the new version becomes valid, but this update failed.

The deletion of an application description failed.

Status Change was requested by OPTIONS parameter STATUSCHANGE(Y). Batch loader statements are processed for changing the application description identified in the message from active to pending or from pending to active.

The version of the application description to be changed must be uniquely identified. Both an active and pending version exist already.

An owning operation can be specified by workstation name, operation number, or job name, or by any combination of the three items, together with the application ID.

No operation in the application matches the specification given in the message text. A blank means that no value is specified.

An owning operation can be specified by workstation name, operation number, or job name, or by any combination of the three items, together with the application ID.

More than one operation in the application matches the specification given in the message text. A blank means that no value is specified.

A SELECT JCLPREP was done without completion of the listed operation.

An operator instruction has been written to the database with temporary information. The update of it, together with the correct information about the operation to which it belongs, has failed.

The deletion of an operator instruction failed.

An OISTART statement, which does not identify the owning operation, is received from the input file.

You tried to issue an INSERT request for resource JCLPREP without first issuing a successful SELECT JCLPREP request.

You tried to perform an INSERT of JCLPREP. At least one of the required prompt variables has not been set.

A group definition cannot contain special resources.

A program interface (PIF) program has requested simulated substitution (resource JCLPREPA). A SIMTIME value that is not in CCYYMMDDHHMM format or that contains an invalid value has been requested.

A program interface (PIF) program has requested simulated substitution (resource JCLPREPA). A SIMTIME value that is not 'FULL' or 'PARTIAL' has been requested.

In the request argument name ARG is specified. The corresponding argument value pointer locates the value VAL. Argument ARG cannot have this value.

The ARGN parameter can contain only one argument controlling the selection on resource name and operation status and only one argument controlling selection by owner ID.

This message is issued for a SELECT request. The SELECT request reads elements from a list. Argument NEXT is specified. When the list was created, argument SEQN was specified in the LIST request. When processing a list in this way the only arguments accepted in the SELECT request are NEXT and SEQN, not the argument given in the message.

When the argument NEXT is specified, the argument value address must be binary zero or point to a binary zero fullword field.

The WSNAME keyword was used as an argument for the OI/OICOM resource in a delete, list, or select request. As from Tivoli OPC Version 2.2.0, WSNAME was no longer significant as argument. The workstation name (WSNAME) was therefore removed from the OI (operator instruction) record and, consequently, it was also removed as an argument of OI/OICOM resource code in PIF programming.

The program interface was called to do the request REQ for the resource RES. It is possible to use only one argument ARG.

All the joblog lines have been already returned.

The file given by ddname DDN is required for processing, but could not be opened. The file can be either SYSIN or EQQOIPDS.

The EQQOIPDS data set must have a logical record length of 80.

The batch loader statement OISTART specifies a PDS member name that does not exist in the data set allocated to ddname EQQOIPDS.

The PDS member could not be read.

You entered an operator instruction (OI) text row that is longer than 72 characters. It is truncated to 72 characters.

You must specify at least the condition identifier and how many condition dependencies are to be included in this condition.

The validation of the parameters in a program interface call found that the communication block address is not locating a valid communication block.

The PAR parameter (could be either REQUEST or RESOURCE) has an unsupported value REQ.

The ARG argument is not supported for the specified request type and resource.

The ARGN parameter can contain only one of the codes mentioned in the message text.

The ARGN parameter indicates that there is a parameter with an associated value, but the corresponding ARGP entry does not contain a valid data address.

The ARGN parameter indicates list select (one of the values FIRST, NEXT, PREV, and LAST is specified), but there has been no preceding LIST request made for the resource RES.

A SELECT request requires at least one selection parameter, but the ARGN parameter indicates that there is none.

More than one record matches the selection criteria set up by the ARGN parameter or the ARGV parameter, or both parameters.

A serious error caused the program interface function to end in error.

The combination of RES and REQ is not supported. REQ is a program interface request type. RES is either a resource in the program interface call or the resource in a record header.

The RES resource is not supported in a SELECT request to the program interface function.

The program interface request requires that a specific argument be present in the ARGN parameter or the ARGV parameter, or both parameters, for the specified resource.

The REQ request requires that the data address parameter (DATAP) contains a valid address.

When adding an application to the long-term plan, You cannot use the data address parameter (DATAP) to supply an application description.

The record header contains an unsupported header resource.

The REQ request requires that the record header contains a resource for the common section of a record.

The HRES resource can exist only once in the buffer header.

The REQ request requires that the data address parameter (DATAP) is set to zero.

The record with key KEY has been updated by another function since it was read by the program interface function.

The record with key KEY is being updated by another function.

The record with key KEY has been updated by another function since it was read by the program interface function.

The record cannot be inserted as it already exists.

A REPLACE request is issued, but the record to be replaced does not exist.

The request could not be handled as the record was already being updated by another dialog or program interface user.

The ENQ macro is issued via the program interface. The ENQ fails with a return code indicating an error: previous request for control of the same resource has been made for the same task.

The DEQ macro is issued either due to a direct request via the program interface or a record read, update or delete request. The DEQ fails with a return code indicating an error. A return code of 8 means that the DEQ is made without a preceeding ENQ for the record by the same program interface user.

The record with key KEY is being updated by another user.

A JCL record is identified by its application ID, input arrival time (date and time), and operation number. You cannot omit any of these fields in a SELECT JS or SELECT JSCOM request.

The program interface is called to update the details of an occurrence. No occurrence is identified.

The program interface is called to update the details of an operation. No operation is identified.

The data address in a program interface call to insert an occurrence is not zero. The data address should therefore locate an application description. A header defining the rest of the data area must come first in the data area. The header to be located at the beginning of the data area does not start with a header entry for the common part of an application description.

The program interface was called to insert a new version of an application description record among the existing versions, but four active versions were already existing in the application description data set. No more active versions of the application are allowed.

The program interface was called to insert a new version of an application description record among the existing versions, but four pending versions were already existing in the application description data set. No more pending versions of the application are allowed.

The program interface was called to modify duration. It is possible to change CPOPEDU using the arguments EDUR and CPOPEDUI using DURATION. But only one of these arguments can be used in a request.

The program interface was called to modify the open time interval data for a current plan workstation or workstation instance. No current plan workstation or instance was identified.

The program interface tried to modify an application version validity period, making sure that all existing versions would be back-to-back. When the valid-from date is changed to an earlier date and the application version has an earlier version, the valid-from date must be greater than the valid-from date of the earliest version. Otherwise, this version would be deleted by the back-to-back mechanism.

You requested to insert or delete a condition dependency without identifying the corresponding condition.

The condition that is to be modified does not exist in the current plan.

The condition that is to be modified already exists in the current plan.

A write record failed.

A read record failed.

A list request was done to the HCL Workload Automation for Z subsystem, but no items were returned. This is either because the selection argument in the request was too narrow or because you are not authorized to read the requested data.

During a consistency check between the application description (AD) and the operator instruction (OI) databases, you have attempted to read the OI database, but you are not authorized.

During a consistency check between the application description (AD) and the operator instruction (OI) databases, you have attempted to update the OI database, but you are not authorized.

An invalid input arrival date was specified while adding an application to the current plan.

The program interface failed to read the record during a restart and cleanup action requested from the Dynamic Workload Console.

The program interface detected an invalid sequence of restart and cleanup actions requested from the Dynamic Workload Console.

The program interface detected an invalid sequence of restart and cleanup actions requested from the Dynamic Workload Console.

The current plan workstation WS to be modified does not exist or the specified instance of a workstation cannot be found.

The current plan occurrence that is to be modified does not exist.

The current plan operation OP that is to be modified does not exist in the specified occurrence.

The current plan operation OP that is to be added already exists.

Changing the status of an occurrence in the current plan to STAT is invalid.

The program interface does not let you modify or delete a current plan occurrence that you have already modified or deleted since the last Execute request.

It is recommended that you issue the Execute request every time you modify or delete a current plan occurrence.

The program interface does not let you modify a workstation or virtual workstation instance that you have already modified since the last Execute request.

A predecessor could not be resolved because the predecessor application does not have an occurrence with an earlier start time or same start time, or the predecessor application is not defined in the Application Description.

The occurrence could not be deleted because of a storage allocation problem.

The occurrence could not be added because of an I/O error.

The occurrence could not be deleted because of an I/O error.

The connector encountered an error while retrieving the information needed to connect to the historical database used by the Dynamic Workload Console reporting feature. The DBOPT statement is not available.

More than one record matches the selection criteria set up by the ARGN or ARGV parameter, or by both parameters, for the DELETE operation.

A field in a table has an invalid format.

A field in a variable in a table has an invalid format.

You tried to define more than 360 dependencies.

The INTFOPTS initialization statement keyword PIFHD is required. It has not been defined.

You are trying to insert or replace a JS record that contains no text rows. The value of JSLINES must be greater than 0.

The Extended Name cannot be composed by all blank characters or by all underscore characters or by combination of blank and underscore characters.

For the specified resource res, the Program Interface Request requires that at least one argument be present in the ARGN or ARGV parameter, or in both.

The scheduling environment name cannot be made up entirely of blank or underscore characters.

The variable varname cannot be blank, because the field field is set to Y.

See message text.

An operation that runs on an Automation workstation cannot be added without specifying the related CPSAI segment.

The CPSAI segment cannot be used to insert system automation info for not automation workstations.

The Deadline Action cannot be set without specifying the Deadline Day offset and Time.

For the application AD, operation OP, you specified the keywords ALL_KEYWDS for the Not Started Action. The keywords ALL_KEYWDS must be all specified, or none specified.

The time value set for the keyword KEYWD is not valid. Allowed values are in the format HHMM, from 0001 to 1259.

For the run cycle RUNCYCLE of the application AD, operation OP, you specified the keywords KEYWDS for the Not Started Action. The keywords ALL_KEYWDS must be all specified, or none specified.

For the application AD, operation OP, you specified the keywords KEYWDS for Not Started Alert. The keywords ALL_KEYWDS must be all specified, or none specified.

For the run cycle RUNCYCLE of the application AD, operation OP, you specified the keyword keyword for Not Started Alert. The keywords ALL_KEYWDS must be all specified, or none specified.

For the Not Started Action, both day and time must be specified or none specified.