EQQY001 - EQQY920

EQQY001I

STATEMENTS FOR AD AD PROCESSED SUCCESSFULLY

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

Processing continues.

None.

EQQY002I

STATEMENTS FOR OI TO AD PROCESSED SUCCESSFULLY

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

Processing continues.

None.

EQQY003E

OPTIONS STATEMENT MISPLACED IN INPUT FILE. PROCESSING IS DONE IN SCAN MODE

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.

The statements are processed in SCAN mode.

Correct the input file and resubmit the job.

EQQY004I

END OF PROCESSING. HIGHEST RETURN CODE RC

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

Processing is ended.

If RC is not zero, review the message log to determine the cause of the nonzero return code.

EQQY005W

OPEN OF FILE FILE FAILED, VALIDATION OF THE RECS WILL BE INCOMPLETE

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 rest of the input statements are scanned for data type errors.

Check that the correct names of data sets are specified in the JCL and resubmit the job.

EQQY007W

THIS STM STATEMENT IS NOT PRECEDED BY A VALID MSTM STATEMENT THE STATEMENT IS PROCESSED IN SCAN MODE.

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 is scanned only for data type errors.

Correct the input file, grouping all statements for the creation of one record together, and resubmit the job.

EQQY008W

STATEMENT STM IS BYPASSED DUE TO PARSER DETECTED ERROR

The statement parser has detected an error in statement STM.

Processing continues. The creation of the current record is abandoned and the remaining statements for the same record are bypassed.

Correct the error described by the previous message and rerun.

The parser-detected error is given by the preceding message.

EQQY009W

STATEMENT STM IS PROCESSED IN SCAN MODE DUE TO ERROR IN PREVIOUS STATEMENT

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

Processing continues.

Correct the erroneous statement and rerun.

EQQY011E

INSERT OF APPLICATION ADID FAILED

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

Processing continues.

Correct the error described by the previous message and rerun.

The preceding message gives the reason why the insert could not be done.

EQQY014W

SUBSYS(NAME) AND CHECK(N) SPECIFICATIONS ARE MUTUALLY EXCLUSIVE. THE CHECK REQUEST IS IGNORED

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.

Processing continues. The normal data validation is applied.

Remove the CHECK keyword.

EQQY015W

ACTION(SCAN) AND CHECK(Y) SPECIFICATIONS ARE MUTUALLY EXCLUSIVE. THE CHECK REQUEST IS IGNORED

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.

Processing continues. No data validation is done.

Remove the CHECK keyword.

EQQY020W

CONFLICTING FORMAT SPECIFICATION BETWEEN SUBS AND THE KW KEYWORD FORMAT FORM IS USED

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.

Processing continues using the DBCS option FORM for the KW data.

Remove the KW keyword.

EQQY021E

SUBSYS SUBS IS SPECIFIED IN OPTIONS STATEMENT, IT IS SET TO YSUBS IN THE INIT STATEMENT OF THE EQQYPARM FILE

Two different subsystem names are specified.

The record being created is considered in error and is not created. The following statements are scanned and validated.

Remove or change the SUBSYS parameter of the SYSIN file OPTIONS statement or change the SUBSYS parameter of the EQQYPARM file INIT statement.

EQQY031E

ADRULE VALID ONLY FOR RUN CYCLES WITH TYPE R OR E

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

The application is not saved in the application description database because the run cycle is invalid.

Change the run cycle type or remove the rule definition, and rerun the job.

EQQY032E

DUPLICATE ADRULE CONTROL STATEMENT. ONLY 1 ADRULE IS ALLOWED FOR EACH ADRUN

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

The application is not saved in the application description database because the run cycle is invalid.

Remove the extra ADRULE control statement or add an ADRUN statement before the second ADRULE.

EQQY033E

NO ADRULE SPECIFIED FOR A RUN CYCLE WITH TYPE R OR E

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

The application is not saved in the application description database because the run cycle is invalid.

Add the ADRULE control statement to define a rule or change the TYPE on the ADRUN statement.

Review the dump data set (ddname EQQDUMP) for more information. The run cycle part of the current application description is printed in the data set and the position of the invalid value in the record is given.

EQQY034E

ERROR IN ADRULE CONTROL STATEMENT FOR RUN CYCLE VADRN IN APPLICATION VADID

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

The application is not saved in the application description database because the run cycle is invalid.

Correct the error and rerun the job.

Review the dump data set (ddname EQQDUMP) for more information. The run cycle part of the current application description is printed in the data set and the position of the invalid value in the record is given.

EQQY035E

INCORRECT LENGTH FIELD FOR ADRULE IN RUN CYCLE VADRN

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

The application is not saved in the application description database because the run cycle is invalid.

Specify the correct length in both fields and rerun the job.

Review the dump data set (ddname EQQDUMP) for more information. The run cycle part of the current application description is printed in the data set and the position of the invalid value in the record is given.

EQQY036E

NO ADRULE SPECIFIED FOR A RUN CYCLE GROUP

The RGRUN control statement is missing an ADRULE statement.

The run cycle group is not saved in the database because the run cycle is invalid.

Add the ADRULE control statement to define a rule.

Review the dump data set (ddname EQQDUMP) for more information. The run cycle part of the run cycle group is printed in the data set and the position of the invalid value in the record is given.

EQQY037E

ERROR IN ADRULE CONTROL STATEMENT FOR RUN CYCLE VADRN IN RUN CYCLE GROUP VRGID

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

The run cycle group is not saved in the database because the run cycle is invalid.

Correct the error and rerun the job.

Review the dump data set (ddname EQQDUMP) for more information. The run cycle part of the run cycle group is printed in the data set and the position of the invalid value in the record is given.

EQQY038E

INCORRECT LENGTH FIELD FOR ADRULE FOR RUN CYCLE VADRN IN RUN CYCLE GROUP VRGID

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

The run cycle group is not saved in the database because the run cycle is invalid.

Specify the correct length in both fields and rerun the job.

Review the dump data set (ddname EQQDUMP) for more information. The run cycle part of the run cycle group is printed in the data set and the position of the invalid value in the record is given.

EQQY050E

VALIDATION FAILED FOR: BLOCK, REASON: REASON, OFFSET: POS

The control block BLOCK contains an error at offset POS.

If this is a request to the program interface function, the request is rejected and control is returned with the return code set to error.

If you cannot find a valid reason for the error, save the dump data set and the message log, and contact IBM Software Support.

Correct the request according to the specified reason codes. If you cannot find a valid reason for the error, contact your system programmer.

The dump data set (ddname EQQDUMP) contains a dump of the failing control block.

The reason code REASON indicates the reason for the failure. See Reason codes for a list of the reason codes and their meanings.

EQQY102E

THE RUN CYCLE SHIFT SIGN IS INVALID, ENTER EITHER B (BACK) OR F (FORTH).

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

The keyword value is rejected.

Enter B (for a negative shift) or F (for a positive shift).

EQQY103E

KEYWORD KEY WITH VALUE VALUE NOT ALLOWED WHEN ACTION(ADD)

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

The keyword value is rejected.

In the OPTIONS statement, change the value either for the ADVALFROMCHG or ACTION keyword, and submit the job again.

EQQY104E

KEYWORD KEY WITH VALUE VALUE NOT ALLOWED WHEN STATUSCHANGE(Y)

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 value is rejected.

In the OPTIONS statement, change the value either for the ADVALFROMCHG or STATUSCHANGE keyword, and submit the job again.

EQQY105I

KEYWORD KEY IN STATEMENT STMT IS IGNORED

The keyword KEY has no significance in the current environment.

Processing continues.

Remove the keyword KEY from the statement STMT.

EQQY106E

KEYWORD KEY CANNOT BE GIVEN A DEFAULT

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

The record being created is considered in error and is not created. The statements following this record that add details to the record are scanned for valid data types.

Correct the input file and resubmit the job.

For more information about the keyword, refer to Managing the Workload.

EQQY107E

KEYWORD KEY IS REQUIRED

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

The record being created is considered in error and is not created. The statements following this record that add details to the record are scanned for valid data types.

Correct the input file and resubmit the job.

For more information about the keyword, refer to Managing the Workload

EQQY108E

KEYWORD KEY HAS AN UNSUPPORTED VALUE VAL

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 record being created is considered in error and is not created. The statements following this record that add details to the record are scanned for valid data types.

Correct the input file and resubmit the job.

For more information about the keyword, refer to Managing the Workload.

EQQY109E

KEYWORD KEY HAS AN UNAMBIGUOUS VALUE VAL

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

The record being created is considered in error and is not created. The statements following this record that add details to the record are scanned for valid data types.

Correct the input file and resubmit the job.

For more information about the keyword, refer to Managing the Workload.

EQQY120E

REMOTE PORT NUMBER MUST BE USED IN CONJUNCTION WITH REMOTE HOST NAME.

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

You can either remove the remote port number from the initialization or add also the remote host name.

EQQY121E

LENGTH OF KEY VALUE IS L, MAXIMUM LENGTH IS MAXL

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

The following statements for the same record are bypassed. No record is produced.

Modify the keyword and rerun.

EQQY122I

KEY VALUE V EXCEEDS THE MAXIMUM MAXV, THE MAXIMUM VALUE IS USED

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

The maximum value is used.

Correct the keyword value.

EQQY123W

THE VALUE VAL IS NOT VALID FOR KEYWORD KEY IN STATEMENT STMT. THE DEFAULT VALUE IS USED.

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

The processing continues using the default value for keyword KEY.

If you do not want the processing to use the default, specify a valid value and rerun.

EQQY124W

KEYWORD KEY IN STATEMENT STMT IS NOT SPECIFIED, THE DEFAULT DEFAULT IS USED.

No value was specified for the keyword KEY in statement STMT.
The processing continues using the default value for keyword KEY.
If you do not want to use the default, specify a value for keyword KEY in statement STMT, then submit the request again.

EQQY125I

OPTIONAL KEYWORD KEY IN STATEMENT STMT IS NOT SPECIFIED.

Keyword KEY is missing in statement STMT.

No default value applies for keyword KEY.

If you need to specify keyword KEY, add it to statement STMT and rerun.

EQQY126W

KEYWORD KEY IN STATEMENT STMT IS IGNORED.

The keyword KEY was set in statement STMT, but that keyword does not apply to the current action.
That keyword value is ignored. Processing continues.
You can remove the keyword from the statement and rerun.

EQQY127E

KEYWORD KEY IN STATEMENT STMT CANNOT BE SPECIFIED WITH LUNAME KEYWORD.

KEY and LUNAME are mutually exclusive keywords.

The request is rejected.

Remove either the LUNAME keyword or the KEY keyword and rerun.

EQQY128E

LU NAME AND REMOTE HOST NAME VALUES ARE MUTUALLY EXCLUSIVE.

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

The processing stops.

Correct the instruction and rerun.

EQQY129I

REMHOST AND REMPORT VALUES SPECIFIED IN EQQYPARM WILL BE USED,

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

EQQYPARM values replaced EQQYRPRM values.

If you want to use EQQYRPRM values, remove REMHOST and REMPORT from EQQYPARM, and rerun.

EQQY132E

FLD VALUE INT IS OUTSIDE SUPPORTED RANGE MINV- MAXV

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.

Processing continues.

Check the input data.

If this message is issued in a batch loader run, use the MSGLEVEL keyword of the OPTION statement to get more information and to find the batch loader statement specifying a keyword value that is outside its valid range.

EQQY133E

FLD VALUE IND IS NOT ONE OF THE SUPPORTED VALUES: ABC

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.

Processing continues.

Check the input data.

If this message is issued in a batch loader run, use the MSGLEVEL keyword of the OPTION statement to get more information and to find the batch loader statement specifying a keyword value that is not one of the accepted values.

EQQY134E

LENGTH OF REMHOST VALUE IS NOT VALID, MAXIMUM LENGTH IS 52.

The specified REMHOST exceeds the allow length.

The processing ends.

Correct the parameter value and resubmit the job.

EQQY135W

KEYWORD KEYWD IN STATEMENT STMT IS NOT VALID. THE VALUE IS OUTSIDE THE VALID RANGE. WILL USE DEFAULT DEFAULT.

The value specified for keyword KEYWD is incorrect.

The processing continues using the default value for keyword KEYWD.

Consider resubmitting the request with a valid KEYWD value.

EQQY136W

VALUE OF KEYWORD KEYWD IN STATEMENT STMT IS EARLIER THAN THE CURRENT RELEASE VALUE VALUE.

The value specified for keyword KEYWD is earlier than the value VALUE, which should be used for the current release.
The processing continues using the provided value.
Consider resubmitting the request with keyword KEYWD set to value VALUE. If you are using your user-written program calling the programming interface, you need to recompile to see the changed layouts.

EQQY201E

AN REC RECORD TO BE ADDED WOULD REPLACE AN EXISTING ONE, NO UPDATE IS DONE KEY OF THE RECORD IS: KEY. THE REPLACE OPTION IS NOT SPECIFIED

The application description or operator instruction already exists.

The present value is kept and the new value is rejected.

Update the record by specifying the REPLACE option and rerunning the statements to create the record.

EQQY202E

TOO MANY VERSIONS, AD WITH KEY KEY IS NOT ADDED

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

The new application description is rejected.

Choose the versions you want and update accordingly.

EQQY204E

WHEN KEY IS SPECIFIED, ALSO THE TIME MUST 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.

The new application description is rejected.

Check the statements for a missing time when the day has been set and update accordingly.

EQQY205E

NO PREDECESSOR OPERATION SPECIFIED, SPECIFY PREWSID, PREOPNO AND/OR PREJOBN

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

The application description is rejected.

Correct the input file and resubmit the job.

EQQY206E

FAILED TO UPDATE AD KEY OPERATION OP WITH PREDECESSOR INFORMATION THE PREDECESSOR IS AD PID OPERATION POP

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.

The application description is deleted.

Repeat the batch loader execution with only this application description in the input. If the problem recurs, report the error to IBM Software Support.

EQQY207E

AN APPLICATION BELONGING TO AN APPLICATION GROUP CANNOT HAVE RUN CYCLES KEY OF THE RECORD IS: KEY

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

The application description is rejected.

Correct the input file and resubmit the job.

EQQY208E

A GROUP DEFINITION CANNOT HAVE OPERATIONS KEY OF THE RECORD IS: KEY

A group definition cannot contain operations.

The application description is rejected.

Correct the input file and resubmit the job.

EQQY209E

A GROUP DEFINITION CANNOT HAVE PREDECESSOR OPERATIONS KEY OF THE RECORD IS: KEY

A group definition cannot contain predecessor operations.

The application description is rejected.

Correct the input file and resubmit the job.

EQQY211E

TOO MANY SIGN START DAYS ENTERED, AT MOST NUM ARE ACCEPTED

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

The application description is rejected.

Correct the input file and resubmit the job. If you need to select more days, repeat the run cycle the necessary number of times.

EQQY212E

EQQUXPIF EXIT REJECTED TYPE RESOURCE REQUEST. REASON IS: REASON.

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

RC=8 is returned by PIF. PIF request fails.

Check the messages issued by the exit to understand why the action has been rejected.

EQQY213E

A GROUP DEFINITION CANNOT HAVE SA INFO. KEY OF THE RECORD IS: KEY

You cannot specify system automation information to a group definition.

The application description is rejected.

Correct the input file and resubmit the job.

EQQY214W

THE INCONSISTENCIES SIGNALED BY MESSAGE EQQY221E COULD HAVE BEEN REMOVED. VERIFY THAT THE RELATED APPLICATIONS HAVE BEEN LOADED OR RERUN THE JOB.

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

The job ends with RC=8.

Verify that all applications signaled by message EQQY221E were correctly inserted into the Application Description database, or run the job again and ensure it ends with RC=0.

EQQY221E

NO OPERATION IN PID MATCHES THE PREDECESSOR SPECIFICATION SUCCESSOR KEY: KEY, SUCCESSOR OPERATION: OP PREDECESSOR SPECIFICATION JOBNAME: JOB, WORK STATION: WS

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.

The application description is rejected.

Correct the input file and resubmit the job. Review previous messages in the Batch Loader message log.

EQQY222E

MORE THAN ONE OPERATION IN PID MATCHES THE PREDECESSOR SPECIFICATION SUCCESSOR KEY: KEY, SUCCESSOR OPERATION: OP PREDECESSOR SPECIFICATION: JOBNAME: JOB, WORK STATION: WS

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.

The application description is rejected.

Correct the input file and resubmit the job.

EQQY223E

FAILED TO UPDATE KEY, OPERATION OP WITH PREDECESSOR INFORMATION PREDECESSOR: PID, OPERATION: POP. REASON CODE RS

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.

Possible reasons as given by RS are:
  • The read failed for the application to be updated.
  • The update write failed.
  • The update failed because the predecessor could not be identified. The application description might have been updated previously.

The application description is rejected.

Resubmit the job with only this application description. If the problem recurs, report the error to IBM Software Support.

The message log of the subsystem contains a detailed description of the error.

EQQY224E

FAILED TO UPDATE KEY TO BE VALID UP TO VTO. REASON CODE RS

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.

Possible reasons as given by RS are:
  • The read failed for the application description to be updated.
  • The update write failed.

The application description is rejected.

Resubmit the job with only this application description. If the problem recurs, report the error to IBM Software Support.

The message log of the subsystem contains a detailed description of the error.

EQQY225E

FAILED TO DELETE KEY. REASON CODE RS

The deletion of an application description failed.

The application description to delete can be one of the following as given by RS:
  1. The new application description was output to a VSAM file.
  2. An existing application description whose valid-to date has been adjusted to create two versions. The update of the new version failed.
  3. The new application description could not be updated correctly.

None.

If the output is to a subsystem, use the Application Description dialog to delete the application description. If the problem recurs, report the error to IBM Software Support.

For reasons 2 and 3, the message log should also contain a message explaining why the new application could not be updated and a detailed description of the error.

EQQY226E

FAILED TO UPDATE APPLICATION ADID WITH VALIDFROM EQUALS TO VFROM. STATUS CHANGE IS REQUESTED AND THERE IS BOTH AN ACTIVE AND A PENDING VERSION WITH THE SAME VALDIFROM DATE.

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.

The change request is rejected.

If the output is to a subsystem, use the dialog to change the application description, if required.

EQQY227E

NO OPERATION IN PID MATCHES THE SPECIFICATION OPERATOR INSTRUCTION KEY: KEY. OWNING OPERATION SPECIFIED BY JOBNAME: JOB, WORK STATION: WS

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.

The operator instruction is rejected.

Correct the input file and resubmit the job.

EQQY228E

MORE THAN ONE OPERATION IN PID MATCHES THE SPECIFICATION OPERATOR INSTRUCTION KEY: KEY. OWNING OPERATION SPECIFIED BY JOBNAME: JOB, WORK STATION: WS

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.

The application description is rejected.

Correct the input file and resubmit the job.

EQQY229E

SETUP FOR OPERATION: POP IN APPLICATION: PID NOT COMPLETE

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

None.

Correct the error and resubmit the job. The operation in the application matches the specification given in the message text. A blank means that no value is specified.

EQQY233E

FAILED TO ADD OPERATOR INSTRUCTION FOR AD: AD, OPERATION: OP REASON CODE RS

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.

Possible reasons as given by RS are:
  • The read of the temporary instruction failed.
  • The update failed.

The operator instruction is rejected.

Resubmit the job with only this operator instruction. If the problem recurs, report the error to IBM Software Support.

The message log contains a detailed description of the error. If the output is to a HCL Workload Automation for Z subsystem, these descriptions are found in the message log of the subsystem.

EQQY234E

FAILED TO DELETE OPERATOR INSTRUCTION: KEY. REASON CODE: RS

The deletion of an operator instruction failed.

Possible reasons as given by RS are:
  • A read of the operator instructions failed.
  • The delete operation failed.

None.

Check if the operator instruction still exists there, by allocating the output file to a HCL Workload Automation for Z subsystem. If it does, use the Operator Instruction dialog to delete it. If the problem recurs, report the error to IBM Software Support.

The message log contains a detailed description of the error.

EQQY235E

NO OPERATION SPECIFIED, SPECIFY WSID, OPNO AND/OR JOBN

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

The operator instruction is rejected.

Correct the input file and resubmit the job.

EQQY236E

NO SETUP SESSION HAS YET BEEN ESTABLISHED FOR THE CURRENT OPERATION

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

The update of JCL variable values is rejected.

Correct the program interface (PIF) user program and retry.

EQQY237E

PROMPT VARIABLES HAVE NOT BEEN SET

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

The update of JCL variable values is rejected.

Check your program to see if it processes correctly.

EQQY238E

A GROUP DEFINITION CANNOT HAVE SPECIAL RESOURCES KEY OF THE RECORD IS: KEY

A group definition cannot contain special resources.

The application description is rejected.

Correct the input file and resubmit the job.

EQQY239E

INVALID ARGUMENT VALUE VAL FOR SIMTIME ARGUMENT

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.

The simulated substitution of the JCL for this operation is not performed.

Correct the PIF program and retry.

EQQY240E

INVALID ARGUMENT VALUE VAL FOR SIMTYPE ARGUMENT

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

The simulated substitution of the JCL for this operation is not performed.

Correct the PIF program and retry.

EQQY241E

INVALID ARGUMENT VALUE VAL FOR ARGUMENT ARG. THE REQUEST IS REQRES

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

The request is rejected.

Correct the request and resubmit the job.

EQQY242E

MULTIPLE MATCHTYP ARGUMENTS IN A REQ REQUEST FOR RES

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.

The request is rejected.

Check that there is a blank entry indicating the end of the ARGN parameter. Correct the request and resubmit the job.

EQQY243E

INVALID ARGUMENT ARG IN SELECT REQUEST AFTER LIST REQUEST FOR SEQUENTIAL RETRIEVAL

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.

The request is rejected.

Correct the program interface application.

EQQY244E

THE VALUE OF ARG IS VAL, MUST BE ZERO. THE REQUEST IS REQ RES

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

The request to write the record is rejected.

Correct the program interface application.

EQQY245E

THE DEFAULT CALENDAR NAME IS REQUIRED BUT IS NOT AVAILABLE. THE REQUEST IS REQRES

The request to write the record is rejected.

Make sure that a default calendar is specified for the program interface. If necessary, use either the program interface OPTIONS request or the program interface INIT statement in the EQQYPARM file to set the default calendar name. In the program interface application, if the CALENDAR argument is unintentionally left out in a SELECT statement for the CL resource, correct the program.

EQQY246E

KEYWORD WSNAME USED AS OI OR OICOM ARGUMENT NOT ALLOWED. PROCESSING IS ENDED.

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.

Processing is ended.

Set the OIWSNAME parameter of the INIT statement to the ignore value and run the PIF user program again. INIT is defined in the parameter file identified by the EQQYPARM DD statement in the JCL of the PIF application. For more information, refer to Customization and Tuning.

EQQY247E

MULTIPLE ARG ARGUMENTS IN A REQ REQUEST FOR RES

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

The request is rejected.

Check that only one argument ARG is used.

EQQY248E

NO MORE JOBLOG LINES

All the joblog lines have been already returned.

The request is rejected.

EQQY301E

FAILED TO OPEN DATA SET WITH DDNAME DDN

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

If SYSIN fails to open, the batch loader processing is terminated. If EQQOIPDS fails to open, no operator instructions are created for OISTART statements with MEMBER specified as the keyword.

Determine why the file is not available. Correct the input and resubmit the job.

EQQY302E

LOGICAL RECORD SIZE OF OI MEMBER DATA SET, DDNAME EQQOIPDS, IS NOT VALID

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

No operator instructions are created for OISTART statements with the MEMBER specified as the keyword.

Convert the EQQOIPDS data set to a record length of 80 and resubmit the job.

EQQY303E

MEMBER MEM DOES NOT EXIST IN THE EQQOIPDS DATA SET

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

Processing continues. The creation of the current record is abandoned and the remaining statements for the same record are bypassed.

Correct the member name or check that the correct data set is allocated to ddname EQQOIPDS.

EQQY304E

ERROR OCCURRED WHILE READING MEMBER MEM FROM THE EQQOIPDS DATA SET

The PDS member could not be read.

Processing continues. The creation of the current record is abandoned and the remaining statements for the same record are bypassed.

Follow the instructions for the preceding message.

The preceding message gives detailed information about the read error.

EQQY306W

TOO LONG OI ROW ENTERED, STARTS BY ST. IT IS TRUNCATED

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

The OI is created.

Correct the input file and resubmit the job.

EQQY307E

REQUIRED PARAMETER FOR ADCNC ARE CONDID, CONDDEPNO

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

The request is rejected.

Correct the input file and resubmit the job.

EQQY308E

REQUIRED PARAMETER FOR ADCNS ARE CONDID, PREWSID, PREOPNO, DEPTYPE, TYPE, LOG

The required parameters are missing.
Note:
The message text omits the CONDDEP prefix. You must actually specify CONDDEPCONDID, CONDDEPPREWSID, CONDDEPPREOPNO, CONDDEPDEPTYPE, CONDDEPTYPE, and CONDDEPLOG.

The request is rejected.

Correct the input file and resubmit the job.

EQQY700E

THE COMMUNICATION BLOCK PARAMETER DOES NOT POINT TO A COMMUNICATION BLOCK

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

Processing continues.

Make sure that the communication block address returned at the INIT request is used in the following program interface requests. Also make sure that the area located by the communication block address is not overlayed and that there was no error at the INIT request.

EQQY701E

INVALID PARAMETER VALUE IN CALL TO EQQYCOM, PARAMETER: PAR, VALUE: REQ

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

The request is rejected.

Correct the request and resubmit the job.

EQQY702E

UNSUPPORTED ARGUMENT NAME: ARG IN REQ STATEMENT, RESOURCE IS RES

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

The request is rejected.

Correct the request and resubmit the job.

EQQY703E

ONLY ONE OF THE ARGUMENTS FIRST, NEXT, PREV AND LAST IS ACCEPTED

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

The request is rejected.

Check that there is a blank entry indicating the end of the ARGN parameter. Correct the request and resubmit the job.

EQQY704E

ARGV ENTRY IS ZERO FOR ARGN VALUE ARG IN REQ REQUEST FOR RESOURCE RES

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 request is rejected.

Check that the ARGN and ARGP parameters have the corresponding entries assigned to them. Correct the request and resubmit the job.

EQQY705E

A LIST SELECT REQUEST WITHOUT A PRECEDING LIST REQUEST, RESOURCE IS RES

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.

The request is rejected.

Check that the proper RESOURCE is specified. If it is, precede SELECT by a LIST request. Correct the request and resubmit the job.

EQQY706E

A SELECT REQUEST WITH NO ARGN/ARGV SPECIFICATION, RESOURCE IS RES

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

The request is rejected.

Check the ARGN and ARGP parameters. Correct the request and resubmit the job.

EQQY707E

A SELECT REQUEST WITH INCONSISTENT ARGN/ARGV SPECIFICATION, RESOURCE IS RES

HCL Workload Automation for Z encountered one of the following problems:
  • A record area has been specified by the ARGN parameter in a SELECT request to hold the data for selection of a record. The ARGN parameter also specifies additional selection items. This is not supported. A record area must be the only selection item.
  • The STATUS argument or the TYPE argument has been specified twice in the ARGN parameter. This is not supported. These arguments can be specified only once.

The request is rejected.

Check the ARGN and ARGP parameters. Correct the request and resubmit the job.

EQQY708E

A SELECT REQUEST WITH MORE THAN ONE RECORD SELECTED, RESOURCE IS RES

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

The request is rejected.

Check the ARGN and ARGP parameters. Correct the request and resubmit the job.

EQQY709E

AN ABEND OCCURRED IN THE PROGRAM INTERFACE FUNCTION, IT IS RESTARTED

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

The program interface function resumes normal processing.

See message EQQG004E.

Review the dump data set (ddname EQQDUMP) to determine the cause of the problem.

EQQY711E

THE RESOURCE RES IS NOT SUPPORTED FOR REQUEST REQ

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 request is rejected.

Check the REQ and RES parameters and the record header. Correct the request and resubmit the job.

EQQY712E

THE RESOURCE RES IS NOT SUPPORTED WHEN SELECTION FROM LIST

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

The request is rejected.

Check the REQ and RES parameters. Correct the request and resubmit the job.

EQQY713E

REQUIRED ARGUMENT ARG MISSING IN REQ REQUEST FOR RESOURCE RES

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.

Processing continues.

Correct the program interface request.

EQQY714E

THE DATA ADDRESS PARAMETER DATAP IS ZERO IN REQ REQUEST

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

The request is rejected.

Check the DATAP parameter. Correct the request and resubmit the job.

EQQY715E

THE DATA ADDRESS PARAMETER DATAP MUST BE ZERO IN AN INSERT LTOC REQUEST

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

The request is rejected.

Do either of the following:
  • Add the application description to the model database before the INSERT LTOC request.
  • Use an existing application description and modify it after it is added by the INSERT LTOC request.

EQQY716E

UNSUPPORTED HEADER RESOURCE HRES IN REQ STATEMENT, RESOURCE IS RES

The record header contains an unsupported header resource.

The request is rejected.

Check the record header. Correct the request and resubmit the job.

EQQY717E

NO COMMON SECTION HEADER RESOURCE HRES IN REQ STATEMENT

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

The request is rejected.

Check the record header. Correct the request and resubmit the job.

EQQY718E

COMMON SECTION HEADER RESOURCE HRES TWICE IN REQ STATEMENT

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

The request is rejected.

Check the record header. Correct the request and resubmit the job.

EQQY719E

THE DATA ADDRESS PARAMETER DATAP IS NOT ZERO IN REQ REQUEST

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

The request is rejected.

Check the DATAP parameter. Correct the request and resubmit the job.

EQQY721W

CONCURRENT UPDATE (REQ) OF RECORD WITH KEY KEY, UPDATE PERFORMED

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

The update is performed.

Check that this update did not cancel any additional update to be done to the record.

EQQY722W

DELETE RECORD WITH KEY KEY NOT DONE, IS BEING UPDATED. RESOURCE IS RES

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

The delete is not performed.

Check if the record should be deleted.

EQQY723W

DANGER OF CONCURRENT UPDATE TO RECORD WITH KEY KEY, UPDATE PERFORMED THE DATA BASE RECORD WAS UPDATED AT UPDT BY USER

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

The update is performed.

Check that this update did not cancel any additional update to be done to the record.

EQQY724E

INSERT OF RECORD WITH KEY KEY NOT DONE, EXISTS. RESOURCE IS RES

The record cannot be inserted as it already exists.

The insert is not performed.

Check if the record needs to be updated. If replace is intended, use REPLACE instead of INSERT.

EQQY725E

REPLACE OF RECORD WITH KEY KEY NOT DONE, RECORD NOT FOUND. RESOURCES IS RES

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

The replacement is not supported.

Check if the record needs to be updated. If insert is intended, use INSERT instead of REPLACE.

EQQY726E

REQUEST REQ TO RESOURCE RES WITH KEY KEY FAILED. THE RECORD IS HELD FOR UPDATE BY USER.

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

Processing continues.

Either use the HCL Workload Automation for Z dialog to perform the update or rerun the program interface program.

Check the data defined in the message using the HCL Workload Automation for Z dialog.

EQQY727E

REQUEST REQ TO RESOURCE RES WITH KEY KEY FAILED. AN ENQ ON THE KEY VALUE FAILED WITH RETURN CODE RC

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 request is not performed.

Update the program interface application and rerun.

Check the meaning of the return code in the ENQ macro description.

EQQY728E

REQUEST REQ TO RESOURCE RES WITH KEY KEY FAILED. A DEQ ON THE KEY VALUE FAILED WITH RETURN CODE RC

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.

Processing continues.

Update the program interface application and rerun.

Check the meaning of the return code in the DEQ macro description.

EQQY729E

CONCURRENT UPDATE (REQ) OF RECORD WITH KEY KEY, REQUEST REJECTED

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

The request is rejected.

Submit one program interface (PIF) program at a time to serialize update requests.

EQQY730E

SELECT RES REQUIRES THE FULL KEY, FIELDS ADID, IA AND OPNO

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 request is rejected.

If you do not know the values for all of the identifier fields, issue a SELECT CPOPCOM request before the SELECT request. If you want to get JCL from only the HCL Workload Automation for Z JCL repository, issue a LIST JSCOM request before the SELECT request.

EQQY731E

A REQRES REQUEST IS RECEIVED, NO OCCURRENCE IS IDENTIFIED

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

Processing continues.

The occurrence details request must be preceded by a request identifying the occurrence, that is, a request to MODIFY the resource CPOC with the occurrence identified by the argument names ADID and IA.

EQQY732E

A REQRES REQUEST IS RECEIVED, NO OPERATION IS IDENTIFIED

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

Processing continues.

The operation details request must be preceded by a request identifying the operation, that is, a request to MODIFY the resource CPOP with the operation identified by the argument name OPNO.

EQQY733E

INPUT DATA WHEN ADDING OCCURRENCE MUST BE AN AD, ARG IS NOT SUPPORTED

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.

Processing continues.

Check that the area located by the data address starts with a correct header. If an existing application description should be used, the ARGN parameter or the ARGP parameter, or both parameters, should be used to identify the application description, and the data address must be zero.

EQQY734E

THE MAXIMUM 4 ACTIVE VERSIONS ALREADY EXIST

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 request is rejected.

Correct the program interface request to insert the application with a different Application ID or, if possible, with the status of the application set to pending.

EQQY735E

THE MAXIMUM 4 PENDING VERSIONS ALREADY EXIST

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 request is rejected.

Correct the program interface request to insert the application with a different Application ID or, if possible, with the status of the application set to active.

EQQY736E

ONLY ONE OF THE ARGUMENTS EDUR AND DURATION CAN BE USED

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.

Request rejected.

Decide which argument you want to use.

EQQY738E

A REQRES REQUEST IS RECEIVED, NO WORK STATION IS IDENTIFIED.

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 request is rejected.

Identify the workstation or instance by a MODIFY CPWS or MODIFY CPWSV request before requesting to modify the open time interval data.

EQQY739E

THIS VERSIONS VALID-FROM DATE CANNOT PRECEDE VALF

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.

The request is rejected.

Check the valid-from date of the earlier version of the application, correct the program interface request and rerun.

EQQY740E

A REQ RES REQUEST IS RECEIVED, NO CONDITION IS IDENTIFIED

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

The request is rejected.

Correct your request by identifying occurrence, operation, and condition in the request sequence.

EQQY741E

CURRENT PLAN CONDITION CID TO BE MODIFIED DOES NOT EXIST. APPLICATION ID: ID, INPUT ARRIVAL TIME: IA, OPERATION: OP

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

Processing continues.

Use the product dialog to check the occurrence defined in the message. Correct the program interface request and rerun it.

EQQY742E

CURRENT PLAN CONDITION CIDTO BE ADDED DOES ALREADY EXIST. APPLICATION ID: ID, INPUT ARRIVAL TIME: IA, OPERATION: OP

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

Processing continues.

Use the product dialog to check the occurrence defined in the message. Correct the program interface request and rerun it.

EQQY801E

FAILED TO WRITE REC RECORD WITH KEY: KEY

A write record failed.

The request is rejected.

Check the message log for messages giving detailed information about the write error.

EQQY802E

FAILED TO READ RECORD WITH KEY: KEY

A read record failed.

The request is rejected, unless the message is issued during the EQQPIFJX delete JCL process. In this case, the process continues.

Check the message log for messages giving detailed information about the read error.

EQQY803E

AN EMPTY LIST WAS RETURNED AS THE RESULT OF A LIST REQUEST SELECTION VALUES USED: KEY

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.

Note:
  1. The key value is returned in the HCL Workload Automation for Z internal format, therefore you might need to read the value in hexadecimal format to obtain the data actually used by the product as selection criteria.
  2. Any dates that appear in the key value are displayed in internal format, which is 72 years before the actual date.

Processing continues.

Check the key value or obtain the correct authorization.

EQQY804W

YOU ARE NOT AUTHORIZED TO READ THE OI DATA BASE AD AND OI WERE NOT CHECKED FOR CONSISTENCY

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.

Processing continues.

Obtain the correct authorization.

EQQY805W

YOU ARE NOT AUTHORIZED TO UPDATE THE OI DATA BASE AD AND OI WERE NOT CHECKED FOR CONSISTENCY

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.

Processing continues.

Obtain the correct authorization.

EQQY807E

IAD CANNOT BE EARLIER THAN 1984/01/01

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

The requests are rejected.

Define a new date starting from 1984/01/01.

EQQY808W

A SELECT CPOP REQUEST DID NOT RETURN ANY OPERATION. VALUES USED: KEY

A list request was made to the HCL Workload Automation for Z subsystem, but some item, that matched the filter criteria when the listing process started, changed during the process.
Note:
  1. The key value is returned in the HCL Workload Automation for Z internal format, therefore you might need to read the value in hexadecimal format to obtain the data actually used by the product as selection criteria.
  2. Any dates that appear in the key value are displayed in internal format, which is 72 years before the actual date.

Processing continues.

Specify an existing operation and run the task again.

EQQY809W

THE REQUESTED RECORD WAS NOT FOUND. KEY VALUE USED: KEY.

A list request was made to the HCL Workload Automation for Z subsystem, but no items were returned.
Processing continues.
Specify a correct value for the key.

EQQY811E

FAILED TO READ RECORD: TYPE

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

The request is rejected.

Retry the failing scenario. If it still fails contact your system programmer.

EQQY812E

INVALID SEQUENCE OF RESTART AND CLEANUP REQUESTS: REQ2 RES2 CANNOT FOLLOW A SUCCESSFUL REQ1 RES1

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

The requests are rejected.

To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section, "Information needed for all problems" sub-section, "Information to collect for restart and cleanup problems". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

EQQY813E

INVALID SEQUENCE OF RESTART AND CLEANUP REQUESTS: REQ2 RES2 MUST BE PRECEDED BY A SUCCESFUL REQ1 RES1

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

The requests are rejected.

Contact your system programmer.

EQQY821E

CURRENT PLAN WORK STATION WS TO BE MODIFIED DOES NOT EXIST

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

Processing continues.

Check the program interface call identifying the workstation that is to be modified. Modify the ARGN or ARGP parameter, or both, by adding the name of the correct current plan workstation, or workstation and destination combination.

EQQY822E

CURRENT PLAN OCCURRENCE TO BE MODIFIED DOES NOT EXIST APPLICATION ID: ID, INPUT ARRIVAL TIME: IA

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

Processing continues.

Check the program interface call identifying the occurrence that is to be modified. Modify the ARGN parameter or the ARGP parameter, or both parameters, by adding the application ID and input arrival date and time of the correct current plan occurrence.

EQQY823E

CURRENT PLAN OPERATION OP TO BE MODIFIED DOES NOT EXIST APPLICATION ID: ID, INPUT ARRIVAL TIME: IA

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

Processing continues.

Check the program interface call identifying the occurrence and the operation that is to be modified. There must be a MODIFY CPOC request identifying the occurrence. Modify the ARGN parameter or the ARGP parameter, or both parameters, by adding the application ID and the input arrival date and time of the correct occurrence. Following the MODIFY CPOC request, there must be a MODIFY CPOP request identifying the operation. Modify the ARGN parameter or the ARGP parameter, or both parameters, by adding the correct operation number.

EQQY824E

CURRENT PLAN OPERATION OP TO BE ADDED DOES ALREADY EXIST APPLICATION ID: ID, INPUT ARRIVAL TIME: IA

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

Processing continues.

Use the HCL Workload Automation for Z dialog to check the occurrence defined in the message. Correct the program interface request and rerun it.

EQQY825E

CHANGE STATUS OF OCCURRENCE TO STAT IS NOT SUPPORTED

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

Processing continues.

Check that the status change supplied in the status argument of the CPOC call is either W (Waiting) or C (Complete).

EQQY826E

CURRENT PLAN OCCURRENCE TO BE MODIFIED ALREADY ALTERED. APPLICATION ID: ID, INPUT ARRIVAL TIME: IA.

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 MODIFY CPOC or DELETE CPOC request is rejected.

Correct the program and rerun it.

EQQY827E

CURRENT PLAN WORKSTATION WS TO BE MODIFIED ALREADY MODIFIED

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

The MODIFY CPWS or MODIFY CPWSV request is rejected.

Correct the program request and rerun it.

EQQY830I

THE REQUEST IS REQUESTRESOURCE, OCCURRENCE LTOC

A program interface request for a long-term plan is identified by:
  • The request type
  • One of the long-term plan resources
  • The key of the occurrence that is being inserted, deleted, or updated.

None.

None.

EQQY832W

UNRESOLVED DEPENDENCY

There are two possibilities:
  • You were adding an occurrence to the long-term plan, using automatic dependency resolution.
  • You were adding a predecessor to an existing occurrence in the long-term plan.

A predecessor could not be resolved because the predecessor application does not have an occurrence with an earlier start time or the same start time.

None.

Use the HCL Workload Automation for Z dialog to display the occurrence and to find out which dependency is missing.

This message is followed by message EQQY830I, which identifies the inserted or updated occurrence of the long-term plan.

EQQY833E

FAILED TO DELETE PREDECESSOR SPECIFICATION, STORAGE ALLOCATION FAILED

There are two possibilities:
  • You were deleting an occurrence from the long-term plan.
  • You were deleting a predecessor from an existing occurrence in the long-term plan.

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

None.

Repeat the request.

This message is followed by message EQQY830I, which identifies the deleted or updated occurrence in the long-term plan.

EQQY834E

FAILED TO ADD PREDECESSOR LTPDERR

There are two possibilities:
  • You were adding an occurrence to the long-term plan.
  • You were adding a predecessor to an existing occurrence in the long-term plan.

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

None.

Look in the message log of the HCL Workload Automation for Z subsystem for an error message that gives more information about the cause of the error.

This message is followed by message EQQY830I, which identifies the inserted or updated occurrence of the long-term plan.

EQQY835E

FAILED TO DELETE DEPENDENCY LTPDERR

There are two possibilities:
  • You were deleting an occurrence from the long-term plan.
  • You were deleting a predecessor from an existing occurrence in the long-term plan.

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

None.

Look in the message log of the HCL Workload Automation for Z subsystem for an error message that gives more information about the cause of the error.

This message is followed by message EQQY830I, which identifies the deleted or updated occurrence in the long-term plan.

EQQY836E

DBOPT PARAMETERS ARE MISSING.

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.

The request is rejected.

Check the server SERVOPT statement and make sure that it contains the DBOPTPRM parameter referring to a member included in the parameter library. Verify that this member contains the DBOPT statement with the DBURL and DBUSER parameters.

EQQY837E

A DELETE REQUEST WITH MORE THAN ONE RECORD SELECTED, RESOURCE IS RES

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

The request is rejected.

Check the ARGN and ARGP parameters. Correct the request and submit the job again.

EQQY900E

THE VARIABLE TABLE NAME JCLVCTAB IS INVALID

A JCL variable table name must:
  • Consist of 1 through 8 alphanumeric characters
  • Begin with an alphabetic character.

None.

Correct the JCL variable table name.

EQQY901E

THE FIELD FIELD IN TABLE JCLVCTAB IS INVALID

A field in a table has an invalid format.

None.

Correct the field.

EQQY902E

THE FIELD FIELD IN TABLE JCLVCTAB IN VARIABLE VARNAME IS INVALID

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

None.

Correct the field.

EQQY903E

THE VARIABLE VARNAME IN TABLE JCLVCTAB HAS MORE THAN 360 DEPENDENCIES

You tried to define more than 360 dependencies.

None.

Reduce the number of dependencies.

EQQY904E

THE PIFHD KEYWORD HAS NOT BEEN DEFINED IN THE SUBSYSTEM PARMS.

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

The program interface application is terminated without further processing.

Define the PIFHD keyword in the initialization statement member for the subsystem and restart the subsystem.

EQQY905E

THE NUMBER OF TEXT ROWS IN A JS RECORD, JSLINES, MUST NOT BE 0

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 JS record is not inserted.

Delete the whole JS record or insert at least one text row into the JS record.

EQQY906E

FAILED TO READ RECORD TO UPDATE, TYPE: REC, KEY: KEY

The request to write the record is rejected.

Make sure that the record to be modified exists. If you cannot find a valid reason for the error, contact your system programmer.

EQQY907E

IF USE EXTENDED INFO IS Y, EXTENDED NAME MUST CONTAIN AT LEAST ONE CHARACTER DIFFERENT FROM BLANK OR UNDERSCORE

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

Processing is ended.

Write a significant Extended Name and resubmit the job.

EQQY908E

AT LEAST ONE ARGUMENT REQUIRED IN REQ REQUEST FOR RESOURCE RES

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 Program Interface Request fails.

Correct the Program Interface Request.

EQQY909E

IF USE SCHEDULING ENVIRONMENT IS Y, THE SCHEDULING ENVIRONMENT NAME MUST HAVE AT LEAST ONE CHARACTER OTHER THAN BLANK OR UNDERSCORE

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

The Program Interface Request fails.

Correct the Program Interface Request by setting a correct value for the scheduling environment name.

EQQY910E

DEFAULT VALUE OF VARIABLE VARNAME IN TABLE JCLVCTAB CANNOT BE BLANK BECAUSE THE FIELD FIELD IS SET TO Y.

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

Processing is ended.

Specify a default value different from blank or set the field field to N, and resubmit the job.

EQQY912E

THE VARIABLE NAME VARNAME IN TABLE TABNAME CONTAINS AN INVALID CHARACTER.

See message text.

Processing is ended.

Correct the name of the variable and retry the operation.

EQQY913E

IF YOU INSERT OPERATIONS RUNNING ON AUTOMATION WORKSTATIONS, THE RELATED CPSAI SEGMENT IS REQUIRED

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

The modification of the CP operation is rejected.

Correct the input file and resubmit the job.

EQQY914E

SYSTEM AUTOMATION INFO CANNOT BE INSERTED FOR NOT AUTOMATION WORKSTATIONS

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

The modification of the CP operation is rejected.

Correct the input file and resubmit the job.

EQQY915E

DEADLINE ACTION REQUIRES DEADLINE DAY OFFSET AND TIME

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

The modification of the operation is rejected.

Correct the input and resubmit the job.

EQQY916E

NOT STARTED ACTION KEYWORDS KEYWDS HAVE BEEN SPECIFIED FOR AD OP. KEYWORDS ALL_KEYWDS MUST BE ALL SPECIFIED.

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 modification of the operation is rejected.

Correct the input and resubmit the job.

EQQY917E

FOR THE KEYWD KEYWORD, TIME VALUE VALUE IS NOT VALID.

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

The request is rejected.

Specify a valid value for the time.

EQQY918E

VARIABLE NOT STARTED ACTION KEYWORDS KEYWDS HAVE BEEN SPECIFIED FOR AD OP RUNCYCLE. KEYWORDS ALL_KEYWDS MUST BE ALL SPECIFIED.

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.

The modification of the operation is rejected.

Correct the input and resubmit the job.

EQQY919E

NOT STARTED ALERT KEYWORDS KEYWDS HAVE BEEN SPECIFIED FOR AD OP. KEYWORDS ALL_KEYWDS MUST BE ALL 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.

The modification of the operation is rejected.

Correct the input and resubmit the job.

EQQY920E

VARIABLE NOT STARTED ALERT KEYWORDS KEYWDS HAVE BEEN SPECIFIED FOR AD OP RUNCYCLE. KEYWORDS ALL_KEYWDS MUST BE ALL 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.

The modification of the operation is rejected.

Correct the input and resubmit the job.

EQQY921E

NOT STARTED ACTION REQUIRES BOTH ACTION DAY AND TIME SPECIFIED OR NONE.

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

The modification of the operation is rejected.

Correct the input and resubmit the job.