EQQX000E

XROW IS NOT A VALID ROW COMMAND

Data entry error.

Specify a valid row command and rerun the task to use the selected value. See Data entry errors

EQQX001E

ZCMD IS NOT A VALID PRIMARY COMMAND

Data entry error.

Specify a valid primary command and rerun the task to use the selected value. See Data entry errors

EQQX002E

A ROW CANNOT BE SELECTED INSIDE A BLOCK THAT IS TO BE DELETED

Data entry error.

Select the row command outside a block that is to be deleted. See Data entry errors.

EQQX003E

COMMANDS AT START AND END OF REPEAT BLOCK DO NOT MATCH

Data entry error.

You assigned different iteration factors at the start and the end of a repeat block. Either use the same factor at both the start and the end, or set the iteration factor at the start or the end only. See Data entry errors.

EQQX004E

A DELETE BLOCK CANNOT BE ENTERED INSIDE A REPEAT BLOCK

Data entry error.

Specify a delete block outside a repeat block and rerun the task. See Data entry errors.

EQQX005E

A ROW COMMAND IS FOUND INSIDE A BLOCK THAT IS TO BE DELETED

Data entry error.

Specify a row command outside a block that must be deleted and rerun the task. See Data entry errors.

EQQX006E

A BLOCK COMMAND HAS NO MATCHING END

Data entry error.

Specify a matching end for the block command and rerun the task. See Data entry errors.

EQQX007E

ISPF DISPLAY SERVICE FOR PANEL PAN GAVE RC DISPRET

Panel PAN could not be displayed.

Processing continues.

Check that the panel is available in the panel library allocated to the TSO session. If it is a user-specified JCL EDIT panel, check that the correct name is specified in the HCL Workload Automation for Z dialog, option 0.6.

EQQX008E

XCMD IS NOT A VALID PRIMARY COMMAND

Data entry error.

Specify a valid primary command and rerun the task. See Data entry errors.

EQQX009I

XSELTR

This message is written to the ISPF log data set when an HCL Workload Automation for Z module is loaded or when an ISPF select is requested by the dialog. The message is used to trace HCL Workload Automation for Z activity for a dialog user.

Processing continues.

None.

EQQX010E

SPECIFY FORMAT FOR DATE

Data entry error.

Specify a valid date format and rerun the task. See Data entry errors.

EQQX011E

YEAR MUST BE SPECIFIED AS YY IN THE DATE FORMAT

Data entry error.

Specify the year in the format YY and rerun the task. See Data entry errors.

EQQX012E

Y MAY BE SET ONLY ONCE AND ONLY IN YY

Data entry error; see Data entry errors.

Specify Y only once and in the YY date format. See Data entry errors.

EQQX013E

MONTH MUST BE SPECIFIED AS MM IN THE DATE FORMAT

Data entry error.

Specify the month in the format MM and rerun the task. See Data entry errors.

EQQX014E

M MAY BE SET ONLY ONCE AND ONLY IN MM

Data entry error.

Specify M only once and in the MM date format. See Data entry errors.

EQQX015E

DAY MUST BE SPECIFIED AS DD OR DDD IN THE DATE FORMAT

Data entry error.

Specify the day in the format DD or DDD and rerun the task. See Data entry errors.

EQQX016E

D MAY BE SET ONLY ONCE AND ONLY IN DD OR DDD

Data entry error.

Specify D only once in the DD or DDD date format and rerun the task. See Data entry errors.

EQQX017E

MONTH CANNOT BE SPECIFIED TOGETHER WITH JULIAN DATE

Data entry error.

Do not specify month if you specified the Julian date. Delete the invalid value and rerun the task. See Data entry errors.

EQQX018E

THE NAME DOES NOT CONFORM TO THE RULES FOR SUBSYSTEM NAMES

Data entry error.

Specify a valid value and rerun the task. See Data entry errors.

EQQX019E

CENTURY MUST BE SPECIFIED AS TWO ADJACENT CHARACTERS

Century is optional. If it is specified, it must be two adjacent characters.

The system waits for you to respond.

If century is used, specify century as CC and rerun the task.

EQQX020E

VER STATEMENT HAS INVALID SYNTAX

An error in the panel has caused invalid syntax in the VER statement.

The system waits for you to respond.

Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX021E

AN INVALID DELIMITER WAS FOUND

Data entry error.

Specify a valid delimiter and rerun the task. See Data entry errors.

EQQX022E

YEAR MUST BE 00 - 99, OR CENTURY WITH YEAR MUST BE 1972 - 2071

Year must be specified as 72 to 99 for years 1972 to 1999 or 00 to 71 for years 2000 to 2071. If century is specified, century and year must be specified as 1972 to 2071.

The panel is redisplayed with this error message.

Specify a valid value and rerun the task. See Data entry errors.

EQQX023E

JULIAN DAY NUMBER IS NOT COMPATIBLE WITH YEAR

Data entry error.

Specify a Julian day in the range 1-365 and rerun the task. See Data entry errors.

EQQX024E

MONTH MUST BE 01 - 12

Data entry error.

Specify a month value in the range 01-12 and rerun the task. See Data entry errors.

EQQX025E

DAY IS NOT COMPATIBLE WITH MONTH AND YEAR

Data entry error.

Specify a day compatible with the month and the year and rerun the task. See Data entry errors.

EQQX026E

HOUR MUST BE 00 - 24

Data entry error.

Specify a value in the range 00-24 and rerun the task. See Data entry errors.

EQQX027E

MINUTE MUST BE 00 - 59

Data entry error.

Specify a value in the range 00-59 and rerun the task. See Data entry errors.

EQQX028E

MINUTE MUST BE 00 WHEN HOUR IS 24

Data entry error; see Data entry errors.

Specify the 00 value and rerun the task. See Data entry errors.

EQQX029E

YEAR MUST BE 00 - 99, OR CENTURY WITH YEAR MUST BE 1972 - 2071

Year must be specified as 72 to 99 for years 1972 to 1999 and 00 to 71 for years 2000 to 2071. If century is specified, century and year must be specified as 1972 to 2071.

The panel is redisplayed with this error message.

Enter a value in the supported range.

EQQX030I

NO CHANGE WAS MADE

You selected a data item using the M command, but you did not actually changed it.

The processing continues.

None.

EQQX031E

SORT ORDER MUST BE A NUMERIC VALUE

Data entry error.

Specify a numeric value and rerun the task. See Data entry errors.

EQQX032E

DIRECTION MUST BE A - ASCENDING OR D - DESCENDING

Data entry error.

Specify A or D and rerun the task. See Data entry errors.

EQQX033E

SPECIFY FORMAT FOR TIME

Data entry error.

Specify the format for time and rerun the task. See Data entry errors.

EQQX034E

HOURS MUST BE SPECIFIED AS HH IN TIME FORMAT

Data entry error.

Specify the hours in the HH format and rerun the task. See Data entry errors.

EQQX035E

H MAY BE SET ONLY ONCE AND ONLY IN HH

Data entry error; see Data entry errors.

Specify H only in HH date format and rerun the task. See Data entry errors.

EQQX036E

MINUTES MUST BE SPECIFIED AS MM IN TIME FORMAT

Data entry error.

Specify the minutes in the MM format and rerun the task. See Data entry errors.

EQQX037E

M MAY BE SET ONLY ONCE AND ONLY IN MM

Data entry error; see Data entry errors.

Specify M only in MM date format and rerun the task. See Data entry errors.

EQQX038E

COLOR MUST BE ONE OF THOSE LISTED ON THE PANEL

Data entry error.

Specify one of the colors listed on the panel and rerun the task. See Data entry errors.

EQQX039E

HIGHLIGHT ATTRIBUTE MUST BE ONE OF THOSE LISTED ON THE PANEL

Data entry error.

Specify one of the value listed on the panel and rerun the task. See Data entry errors.

EQQX040I

THE JOB HAS BEEN SUBMITTED FOR SUBFUNC

The job has been submitted.

Normal processing continues.

None.

EQQX041E

THE NAME SPECIFIED FOR THE SYSOUT DATA SET IS INVALID

Data entry error.

Specify a valid value and rerun the task. See Data entry errors.

EQQX042E

AT LEAST THE FIRST JOB STATEMENT MUST BE SPECIFIED

Data entry error.

Specify the job statement in the card and rerun the task. See Data entry errors.

EQQX043E

THE EDIT OPTION MUST BE EITHER S OR E

Data entry error.

Specify S to submit the job or E to edit the job and rerun the task. See Data entry errors.

EQQX044E

VALID REPLY IS Y OR N

Data entry error.

Confirm deletion of OI list from AD specifying Y or N and rerun the task. See Data entry errors.

EQQX045W

PRESS ENTER TO GENERATE JCL OR END TO CANCEL

Press ENTER to generate the JCL or enter END to leave the panel without generating the JCL.

The system waits for you to respond.

Press ENTER or enter END.

EQQX047E

YEAR MUST BE 00 - 99, OR CENTURY WITH YEAR MUST BE 1972 - 2071

Year must be specified as 72 to 99 for years 1972 to 1999 or 00 to 71 for years 2000 to 2071. If century is specified, century and year must be specified as 1972 to 2071.

The panel is redisplayed with this error message.

Enter a value in the supported range.

EQQX048E

CORRECT VALUES ARE Y AND N

The only allowed values are Y and N.

The panel is redisplayed with this error message.

Enter a value of Y or N.

EQQX049E

CONFIRM PANEL MUST BE N WHEN CONSISTENCY CHECK IS N

The Confirm Panel value is meaningful only if consistency checking has been activated. Therefore, if Consistency Check is set to No, the Confirm Panel value must also be No.

The panel is redisplayed with this error message.

Set the correct value.

EQQX051E

DURATION FORMAT MISSING

The panel is redisplayed with this error message.

Set duration format.

EQQX052E

CONFLICTING CHARACTER

Duration format not allowed. It must be:

HH.MM.SS
HHMMSS
HHMM.SS
MMMM.SS
MMMMSS

The panel is redisplayed with this error message.

Set the correct duration format.

EQQX053E

SECOND INVALID

Invalid value for seconds. You can specify a number from 00 to 59.

The panel is redisplayed with this error message.

Set the correct seconds value.

EQQX054E

MINUTE INVALID

Invalid value for minute. You can specify a number from 0000 to 5999.

The panel is redisplayed with this error message.

Set the correct minutes value.

EQQX055E

DURATION IS INVALID

Operation duration must be greater than zero.

The panel is redisplayed with this error message.

Set duration value greater then zero.

EQQX056E

DURATION IS INVALID

Operation duration must be not greater than 5999 M, 1 S.

The panel is redisplayed with this error message.

Set the correct duration value.

EQQX057E

DURATION IS INVALID

Operation duration must be not greater than 99 H, 59 M, 1 S.

The panel is redisplayed with this error message.

Set the correct duration value.

EQQX058E

DURATION IS INVALID

Duration must be greater than zero and not greater than 99 H, 59 M, 1 S.

The panel is redisplayed with this error message.

Set the correct duration value.

EQQX059E

DURATION IS INVALID

Duration format is XDFM.

The panel is redisplayed with this error message.

Set duration value in the correct format XDFM.

EQQX060E

CONFLICTING VALUES FOR USE EXTENDED INFO AND EXTENDED NAME FIELDS.

Use extended info cannot be set to Y if Extended name is not specified.

The request is rejected.

Correct the input. If the message is issued in a Mass update batch program, check the EQQDUMP data set showing the current Application Description and the position of the invalid value in the AD record.

EQQX061E

EXTENDED INFO NOT AVAILABLE.

Extended info not available for the operation browsed.

The request is rejected.

Specify an extended info for the selected operation and run the task again.

EQQX062E

THE CORRECT VALUES FOR USE EXTENDED INFO ARE Y OR N.

The only correct values for the Use Extended Info field are Y or N.

The request is rejected.

Check the entered data and correct it, if the error occurred in batch, resubmit the job.

EQQX063E

SE NAME REQUIRED - CONFLICTING VALUES FOR USE SE NAME FIELD AND SE NAME FIELD.

Data entry error.

None.

Specify a scheduling environment name and run the task again. See Data entry errors.

EQQX064E

INVALID VALUE - THE ACCEPTED VALUES FOR USE SE NAME ARE Y OR N.

Data entry erro.

None.

Specify Y or N and run the task again. See Data entry errors.

EQQX065E

AUTOMATION INFO CANNOT BE BLANK OR EMPTY. VALID VALUES ARE Y OR N.

System automation information cannot be blank or empty. Valid values are Y (yes) and N (no).

The request is rejected.

Specify a valid value.

EQQX067E

AUTOMATED FUNCTION NAME MUST BE UPPERCASE ALPHANUMERIC

The automated function must be an alphanumeric value, all uppercase.

The request is rejected.

Specify a valid value.

EQQX069E

SYSTEM AUTOMATION INFO NOT AVAILABLE

System automation information is not available.

The request is rejected.

Specify a valid value.

EQQX070E

CONFLICTING VALUES FOR USE AUTOMATION INFO AND SA INFORMATION

Conflicting values were specified for Use Automation Info and system automation information.

The request is rejected.

Specify a valid value.

EQQX071E

SYSTEM AUTOMATION COMMAND TEXT CANNOT BE EMPTY

The System Automation command text cannot be empty or blank.

The request is rejected.

Specify a valid value.

EQQX072E

THE SELECTED OPERATION IS NOT ON A CRITICAL PATH.

You entered the TCJ row command for an operation that is not a logical predecessor of a critical job.

The request is rejected.

Select a critical job and run the task again. See Data entry errors.

EQQX073E

NO WORKSTATION DEFINITION IS FOUND IN THE WS DATABASE.

The workstation database is empty.

The request is rejected.

Specify the required workstation definitions in the database, and submit the request again.

EQQX074E

THE NUMBER OF CONDITIONS MUST BE GREATER OR EQUAL 0

You requested to define a conditional dependency without specifying any condition.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify at least one condition.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX075E

THE CONDITION DEPENDENCIES NUMBER MUST BE GREATER OR EQUAL 0

You requested to define a condition without specifying any conditional dependency.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify at least one condition dependency.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX076E

COND (OP CCID) IS A DUPLICATE CONDITION

You defined the same condition twice.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Remove the duplicate entry.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX077E

CONDITION CONTAINS NOT VALID CHARACTERS

The condition segment contains incorrect characters. Possible reasons for this error are free fields not initialized.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Check the format of the segment fields. Consider initializing unused character fields to blank and unused signed field to zero.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX078E

THE CONDITION ID MUST BE 1 - 999

Condition number incorrect. It must be in the range 1-999.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a condition number in the range 1-999.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX079E

NUMBER OF CONDITION DEPENDENCIES IS NOT VALID FOR COND CCID

No condition dependency defined.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify at least one condition dependency.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX081E

COND(OP CCID): SUBSET VALUE CCCNT NOT VALID.

You specified an incorrect number as subset value. It cannot exceed the number of defined conditional dependencies.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Correct the number.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX082E

COND(OP SCID SCAD SCWS SCOP): IS DUPLICATED.

You defined the same conditional dependency twice.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Remove the duplicate entry.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX083E

COND(OP SCID SCAD SCWS SCOP): COND ID NOT FOUND.

The process did not find any condition matching the specified condition ID value.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Correct the condition ID value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX084E

COND(OP SCID SCAD SCWS SCOP): TYPE SCTYP NOT VALID.

You specified an incorrect predecessor type. It must be I or E.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify I or E as predecessor type.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX085E

COND(OP SCID SCAD SCWS SCOP): INT PRED AD NOT VALID.

The process did not find any internal predecessor matching the specified predecessor application ID value.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Correct the predecessor application ID value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX086E

COND(OP SCID SCAD SCWS SCOP): EXT PRED AD NOT VALID.

The process did not find any external predecessor matching the specified predecessor application ID value.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Correct the predecessor application ID value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX087E

COND(OP SCID SCAD SCWS SCOP): PRED WS NOT VALID.

The process did not find any predecessor matching the specified predecessor workstation value.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Correct the predecessor workstation value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX088E

COND(OP SCID SCAD SCWS SCOP): PRED OP.NO NOT VALID.

The process did not find any predecessor matching the specified predecessor operation number value.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Correct the predecessor operation number value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX089E

COND(OP SCID SCAD SCWS SCOP): TYPE SCTYP NOT VALID.

You specified an incorrect type value. It must be RC or ST.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify RC or ST as type value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX090E

COND (OP SCID SCAD SCWS SCOP): OPERATOR SCLOG NOT VALID.

You specified an incorrect logical operator. Valid values are GE, GT, LE, LT, EQ, NE, and RG. With condition type ST, valid values are EQ or NE only.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX091E

COND (OP SCID SCAD SCWS SCOP): RC VALUE SCVRC NOT VALID.

You specified an incorrect return code value, or you used the RG operator without specifying both the required boundaries. Valid values are in the range 0-9999.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX092E

COND (OP SCID SCAD SCWS SCOP): ST VALUE SCVST NOT VALID

You specified an incorrect ST value. Valid values are C, E, S, and X. Value S is allowed using the EQ operator only.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX093E

COND (OP SCID SCAD SCWS SCOP): NOT VALID CHARACTERS.

The conditional dependency segment contains incorrect characters. Possible reasons for this error are free fields not initialized.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Check the format of the segment fields. Consider initializing unused character fields to blank and unused signed field to zero.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX094E

COND (OP SCID SCAD SCWS SCOP): INTERNAL PRED NOT VALID.

The job specified as conditional internal predecessor does not exist in the database.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Check the operation number and the workstation name that identify the predecessor.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX095E

COND (OP CCID): CANNOT BE DEFINED ON NOT CENTRALIZED OPERATION.

You cannot define a conditional predecessor for a not centralized job.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Remove the inconsistency.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX096E

COND (OP SCID SCAD SCWS SCOP): ALSO NORMAL PRED.

You cannot define the same job as both conditional and normal predecessor.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Remove the inconsistency.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX097E

COND (OP CCID): INCONGRUENT NUMBER OF CONDITION DEPENDENCIES.

The number of defined conditional dependencies must match the number of definitions specified in the current condition.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Remove the inconsistency.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX098E

COND (OP SCID SCAD SCWS SCOP): RANGE SCVRC-SCVR2 NOT VALID.

One or both the specified return codes are incorrect. They must be numeric values in the range 0-9999, or string values in the form Uxxx amd Sxxx.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify valid return code values.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX099E

COND (OP SCID SCAD SCWS SCOP): CANNOT REFER ITSELF.

The operation number specified for the conditional predecessor is equal to the owning operation number.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.If you cannot determine the cause of the error and the error persists, contact the Software Support.

Remove the inconsistency.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX100E

ONLY ONE ROW COMMAND CAN BE SPECIFIED ON THIS PANEL

You are not allowed to specify more than one row command on this panel.

The system waits for you to respond.

Enter the RESET command to remove all row commands and enter one row command.

EQQX101I

PENDING APPLICATION DESCRIPTIONS DO NOT GIVE OCCURRENCES

The Modify LTP One program, which is generated with the L command, deletes any entry of the pending version of the application and adds any active versions of it. Also, being a Modify LTP One, dependencies are not resolved.

Processing continues.

Decide whether to submit the job.

EQQX102W

NO DURATION ALERT IS ISSUED FOR VALUE ODUR

No duration alert is issued for a value of 99 hours 59 minutes 01 second.

The panel is redisplayed with this warning message. Processing continues after pressing Enter.

Check your operation network.

EQQX103E

COND(OP SCID SCAD SCWS SCOP): PRINT WS CANNOT HAVE INT. PRED.

You requested to define an internal conditional predecessor for an operation associated to a print workstation.

The request is rejected.

Verify the specified input.

EQQX104E

COND(OP SCID SCAD SCWS SCOP): INTERNAL COND PRED NOT FOUND.

The process tried to define SCAD SCWS SCOP as conditional predecessor of OP, but SCAD SCWS SCOP is not defined in the database.

The request is rejected.

Verify the specified input.

EQQX105E

CONDITION TYPE RC IS REQUIRED TO DEFINE STEP LEVEL DEPENDENCIES.

You specified a condition type different from RC.

The request is rejected.

Specify RC as condition type.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX106E

PROCSTEP CANNOT BE BLANK WHEN STEPNAME IS SPECIFIED.

When STEPNAME is specified, PROCSTEP is required.

The request is rejected.

Specify STEPNAME and PROCSTEP only if the step is in a procedure, otherwise use PROCSTEP to identify a step in the predecessor job.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX107E

USER FIELDS NAME MUST BE UNIQUE FOR THE SAME OPERATION.

The same user field name was specified twice.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Remove the duplicated entry.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX109E

USER FIELD CANNOT BE BLANK.

User field name cannot be blank or empty.

The request is rejected.

Specify a user field name and run the task again.

EQQX110E

XOPCNM IS NOT A VALID SUBSYSTEM NAME

Data entry error; see Data entry errors.

Change the subsystem name to a valid name by using 0, OPTIONS on the HCL Workload Automation for Z main menu.

EQQX111E

XOPCNM IS NOT AN ACTIVE SUBSYSTEM

The subsystem (XOPCNM) that you selected is not active.

The system waits for you to respond.

Start the subsystem.

Change the subsystem name to a valid name by using 0, OPTIONS on the HCL Workload Automation for Z main menu. If the name is a valid subsystem name, ask your system programmer to start the subsystem.

EQQX112E

NOT ENOUGH STORAGE AVAILABLE

A GETMAIN failed at the logon to HCL Workload Automation for Z because there is not enough available storage.

The system waits for you to respond.

Log on again to TSO with a larger region size.

EQQX113E

INCORRECT PARAMETERS TO THE LOGON ROUTINE

The logon failed because of incorrect parameters in the input to the logon routine.

The system waits for you to respond.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX114E

PRODUCT SERVICES REQUIRE TSO/E R2

HCL Workload Automation for Z cannot be run because the prerequisite TSO/E Release 2 system programs are not installed.

The system waits for you to respond.

Make sure that TSO/E Release 2 is installed before any user attempts to use the HCL Workload Automation for Z dialogs.

Contact your system programmer.

EQQX115E

TSO SERVICE FACILITY RC: XSSRC, RSNC: XSSRS, ABEND: XSSAB

The TSO Service facility, IKJEFTSR, which is used for communication between the dialog and the HCL Workload Automation for Z subsystem, gave an error return code. The field RC gives the IKJEFTSR return code (XSSRC). The values and their meanings are:

8: Confirms that the requested function is terminated as a result of a user pressing ATTN (attention).
12: The invoked function has abended. The RSNC field contains the IKJEFTSR reason code and the ABEND field contains the abend code.
20: There is a problem with the IKJEFTSR parameter list. XSSRS is the reason code for the problem.

The request is rejected.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

If the return code is other than 8 (a result of you pressing ATTN), leave the dialog and retry. If the error persists, contact your system programmer.

Use the return code, reason code, and abend code to determine the cause of the error. For more information, refer to the documentation of IKJEFTSR for the currently active z/OS system.

EQQX116E

ERROR IN SUBSYSTEM INTERFACE, RETURN CODE: XRC

An error occurred in the subsystem interface. Return code XRC provides debugging information.

The request is rejected.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX117E

ERROR IN EQQMINOx ROUTINE, RETURN CODE: XRC

An error, with return code XRC, occurred in the EQQMINOx routine. The return code is returned from the z/OS subsystem interface routine at a subsystem call request.

The request is rejected.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Contact your system programmer.

Use the return code to determine the cause of the error. For more information, refer to the documentation of return codes from the IEFSSREQ macro for the currently active z/OS system.

EQQX118E

ERROR IN LOGON ROUTINE. RETURN CODE: XSSRC. REASON CODE XSSRS

An error, with return code XSSRC and reason code XSSRS, occurred in the logon routine. Return code XSSRC and reason code XSSRS provide debugging information.

The request is rejected.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX119E

LOGOFF REQUEST REJECTED, USER IS NOT LOGGED ON

You have attempted to disconnect a session from HCL Workload Automation for Z, but you are not connected.

None.

Use the HCL Workload Automation for Z message log. to determine why you are logged off. (HCL Workload Automation for Z has been stopped and restarted since you logged on.)

EQQX120E

THE EQQMINOI PROGRAM CAN ONLY BE CALLED BY AN APF-AUTHORIZED TASK

The cause of the problem is one of the following:

The EQQMINOI program could not be called by an APF-authorized task because it does not reside in an APF-authorized library. EQQMINOI is one of a number of HCL Workload Automation for Z load modules that must reside in an APF-authorized library.
The EQQMINOI program is not defined in the IKJTSOnn member of the SYS1.PARMLIB data set.

The request is rejected.

Move EQQMINOI to an APF-authorized library and verify that it is defined in the IKJTSOnn member of the SYS1.PARMLIB data set. For further information see HCL Workload Scheduler for Z: Planning and Installation.

Contact your system programmer.

EQQX121E

YOU ARE NOT AUTHORIZED TO REQUEST ON FIXED RESOURCE RESOURCE

REQUEST is READ or UPDATE, RESOURCE is the name of a HCL Workload Automation fixed resource. For details about fixed resources and how to implement security, refer to Customization and Tuning.

The request is rejected.

Contact your security administrator to check your RACF authorizations for the reported resource and its associated subresources.

EQQX122E

CURRENT SUBSYSTEM REQUEST WAS NOT RECOGNIZED

The subsystem interface has been called with an invalid parameter.

The request is rejected.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX123E

XOPCNM IS NOT A PRODUCT SUBSYSTEM NAME

XOPCNM may be a subsystem name, but it is not a valid HCL Workload Automation for Z subsystem name.

The system waits for you to respond.

Enter a valid HCL Workload Automation for Z subsystem name.

EQQX124E

YOU ARE NOT CONNECTED TO XOPCNM. RESTART FROM PRIMARY PANEL

The subsystem XOPCNM has been restarted. You are no longer connected to it.

The system waits for you to respond.

Restart from the primary panel.

EQQX125E

YOU ARE ALREADY CONNECTED TO THE PRODUCT

You have attempted to reconnect your session to HCL Workload Automation for Z, but you are already connected.

The system waits for you to respond.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Log off from TSO and log on again. If the problem persists, contact your system programmer.

EQQX127E

USER NOT AUTHORIZED TO REQUESTRESOURCE, RC:XRC, RSNC:XRSN

You have attempted to access (read or update) a HCL Workload Automation for Z resource, but you are not authorized. The retrieval and update of data in the HCL Workload Automation for Z database is controlled by parameter values in the AUTHDEF initialization statement, the definition of the RACF resources, and the access lists to the RACF resources. RESOURCE is the name of a HCL Workload Automation fixed resource. For details about fixed resources and how to implement security, refer to Customization and Tuning.

The request is rejected.

Check your RACF authorizations.

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

EQQX128E

YOU ARE NOT AUTHORIZED TO REQUESTRESOURCE MEMBER

You have attempted to access (read or update) a HCL Workload Automation for Z resource, but you are not authorized. The retrieval and update of data in the HCL Workload Automation for Z database is controlled by parameter values in the AUTHDEF initialization statement, the definition of the RACF resources, and the access lists to the RACF resources.

The request is rejected.

Contact your security administrator to check your RACF authorizations for the reported resource and its associated subresources.

EQQX129E

YOU CANNOT DELETE AN ALLOCATED SPECIAL RESOURCE

You have attempted to delete a special resource that is allocated currently for operations. This deletion is not allowed.

The request for the delete of a special resource is rejected.

Wait till the special resource is released by the operations using it.

EQQX130E

THE NUMBER OF USER FIELDS MUST BE GREATER THAN OR EQUAL TO 0.

The number of user fields is an invalid value.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX131E

NOT ENOUGH STORAGE AVAILABLE

A GETMAIN for communication storage area between the dialog and the HCL Workload Automation for Z subsystem failed. The request is for common storage area (CSA) storage, subpool 241.

The request is rejected.

Make sure that sufficient CSA storage is available.

Contact your system programmer. When more CSA storage is available, log on to TSO again.

EQQX132E

YOU ARE NOT CONNECTED TO XOPCNM. RESTART Z/OS SERVER.

While you were attempting to perform an operation, the connection to the subsystem XOPCNM was interrupted.

The operation is stopped.

Start the HCL Workload Automation for Z server again.

EQQX133E

THE SPECIFIED SUBSYSTEM, XOPCNM, IS ENDING

You cannot access subsystem XOPCNM, because it is terminating.

The request is rejected.

Review the HCL Workload Automation for Z message log to determine the reason for the subsystem termination.

Contact your system programmer.

EQQX134E

REQUESTED SERVICE IS CURRENTLY NOT AVAILABLE

Your request to use the general service function could not be granted because the general service task is not active.

The request is rejected.

Review the HCL Workload Automation for Z message log to determine why the general service task is not active.

Contact your system programmer.

EQQX135E

AN ERROR OCCURRED WHILE POSTING THE SUBSYSTEM

Your request to use the general service function could not be granted because the general service task is inaccessible due to an error that occurred in the HCL Workload Automation for Z subsystem.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for messages concerning the general service task to determine the cause of the error.

Check if the subsystem is running.

EQQX136E

OU ARE NOT AUTHORIZED TO REQUEST RESOURCE

You have attempted to perform an action on an HCL Workload Automation for Z resource, but you are not authorized. Retrieving and updating data in the HCL Workload Automation for Z database is controlled by the parameters set in the AUTHDEF initialization statement, by the definition of the RACF resources, and by the access lists to the RACF resources.

The request is rejected.

Check that your RACF authorizations are valid for the operation that you want to perform.

EQQX137E

THE LOGICAL VSAM FILE IS NOT DEFINED

Your request to use the general service function failed because the logical VSAM file is not defined. This error indicates that a serious error has occurred in the HCL Workload Automation for Z subsystem.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for messages concerning the general service task and the logical file handler to determine the cause of the error.

Check if the VSAM file is defined and catalogued.

EQQX138E

AN I/O REQUEST SPECIFIES TOO LARGE A VSAM KEY SIZE

Your request to use the general service function failed because an I/O request specifies a VSAM key size that is too large. This error indicates that a serious error has occurred in the HCL Workload Automation for Z subsystem.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for messages concerning the general service task and the logical file handler to determine the cause of the error.

Verify that the VSAM key is not greater that 19 byte.

EQQX139E

VSAM I/O REQUEST FAILED. RETURN CODE: XSSRC, REASON CODE: XSSRS

Your request to use the general service function resulted in a VSAM I/O that failed. The reason for the failure is indicated by return code XSSRC and reason code XSSRS, which are the VSAM return and reason codes for a record management request.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for VSAM I/O error messages to determine the cause of the error.

Contact your system programmer.

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

EQQX140E

REMAINING STORAGE NOT ENOUGH TO OPEN LOGICAL VSAM FILE

Your request to use the general service function failed because the remaining storage is not enough to open a logical VSAM file.

The request is rejected.

Allocate a larger region to the HCL Workload Automation for Z subsystem and restart the subsystem.

Try again. If the error persists, contact your system programmer.

EQQX142E

VSAM I/O WAS ATTEMPTED ON AN UNOPENED LOGICAL VSAM FILE

Your request to use the general service function failed because the VSAM I/O was attempted on an unopened logical VSAM file. This error indicates that a serious error has occurred in the HCL Workload Automation for Z subsystem.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for messages concerning the general service task and the logical file handler to determine the cause of the error.

Open the logical VSAM file before attempting to perform an I/O operation on it.

EQQX143E

OPEN WAS REQUESTED FOR ALREADY OPENED LOGICAL VSAM FILE

Your request to use the general service function failed because the open request was for an already opened logical VSAM file. This error indicates that a serious error has occurred in the HCL Workload Automation for Z subsystem.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for messages concerning the general service task and the logical file handler to determine the cause of the error.

Check if another process is already using the same VSAM file.

EQQX144E

ERROR IN DB RECORD AT OFFSET OFFS, REASON CODE: XSSRS

The subsystem detected an inconsistency in a record that it was requested to write.

The request is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error. If you cannot find a valid reason for the error, contact your system programmer.

EQQX145E

THE SUBSYSTEM PROGRAM IS NOT OF THE CORRECT RELEASE

The dialog or HCL Workload Automation for Z batch program is at a different release than the HCL Workload Automation for Z subsystem. HCL Workload Automation for Z checks that the subsystem name specified in the dialog or in the SUBSYS parameter of the BATCHOPTS statement (or its default) matches the name of one of your HCL Workload Automation for Z subsystems. If there is a match, HCL Workload Automation for Z checks if the dialog or batch program and the subsystem are at the same release or maintenance level.

This message is issued if the subsystem is at a different release than the dialog or batch program, or if the dialog or user interfaces are at an inconsistent maintenance level of HCL Workload Automation for Z release.

Note: During the migration phase, the following temporary situation might occur in your environment: LPAR (a) with controller located in HCL Workload Automation for Z is at level x and the SSX is in HCL Workload Automation for Z at level x also; LPAR (b) referencing in its definition the updated LOADLIB of HCL Workload Automation for Z subsystem of LPAR (a). If in this LPAR the SSX subsystem was not updated by an IPL at the start of the migration, it is still at level x-n, and it does not match the level of the HCL Workload Automation for Z batch processing. For this transitory environment setup, the EQQX145E message is issued.

The subsystem request is rejected.

Check that the correct subsystem start JCL is used and the correct data sets are allocated to ISPLLIB. If the error persists and you cannot determine its cause, search the IBM Support database for a solution at Support. If the dialog or user interfaces are at the same release of HCL Workload Automation for Z, ensure that also the maintenance level is at the same level.

Check on the main panel that you are using the correct subsystem. If the message is issued by a batch program, check that the BATCHOPTS statement specifies the correct subsystem. If the error persists, contact your system programmer.

This message is expected if the controller is started using the BUILDSSX(REBUILD) keyword and the address space is not currently started.

EQQX146E

THE EQQMINOI LEVEL DOES NOT MATCH THE SUBSYSTEM LEVEL.

This error occurs if a non-authorized STEPLIB or JOBLIB is used for the step that runs EQQMINOI and the EQQMINOI in the LINKLIST is from a different HCL Workload Automation for Z version.

The request is rejected.

If you cannot determine the cause of the error contact your IBM representative.

Use the EQQMINOI at the same level of the SUBSYSTEM.

Check the EQQMINOI level you are using.

EQQX150E

PDF BROWSE/EDIT WORK FILE CONNECT FAILURE - RC = MSGRC

The connect to the work data set used by PDF EDIT or BROWSE failed. Return code MSGRC gives the reason.

The function is terminated.

If the return code indicates that this is not a user error, search the IBM Support database for a solution at Support.

Contact your system programmer.

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

EQQX152E

PDF BROWSE/EDIT WORK FILE - RC = MSGRC, REASON CODE = MSGEF

Dynamic allocation for the PDF BROWSE/EDIT work file failed. Return code MSGRC and reason code MSGEF give the reason.

The function is terminated.

Determine the cause of the error and take the appropriate action.

Contact your system programmer.

Use the DYNALLOC return code and reason code to determine the cause of the error. For more information, refer to the appropriate DYNALLOC documentation for the currently active z/OS system.

EQQX153E

PDF BROWSE/EDIT WORK FILE - RC = MSGRC, REASON CODE = MSGEF

Dynamic deallocation for PDF BROWSE/EDIT work file failed. Return code MSGRC and reason code MSGEF give the reason.

The function is terminated.

Determine the cause of the error and take the appropriate action.

Contact your system programmer.

Use the DYNALLOC return code and reason code to determine the cause of the error. For more information, refer to the appropriate DYNALLOC documentation for the currently active z/OS system.

EQQX154E

OPERATOR INSTRUCTION CANNOT BE EMPTY

A PIF request was received with no text line in the input operator instruction segment.

The request is rejected.

Check that the text field is specified in the input operator instruction segment.

EQQX161E

AN INTERNAL CONTROL BLOCK IS IN ERROR

An internal HCL Workload Automation for Z control block is in error.

The system waits for you to respond.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX162E

AN AUTHORITY CHECK FAILED, RESOURCE RESOURCE NOT RECOGNIZED

You have attempted to access a HCL Workload Automation for Z resource, but the resource RESOURCE is unknown to HCL Workload Automation for Z. The retrieval and update of data in the HCL Workload Automation for Z database is controlled by parameter values in the AUTHDEF initialization statement, the definition of the RACF resources, and the access lists to the RACF resources.

The request is rejected.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Verify that you have specified the correct resource name.

EQQX163E

INCORRECT PARAMETER IN GENERAL SERVICE REQUEST

Your request for the general service function failed because of an incorrect parameter in the request.

The system waits for you to respond.

Make sure that the correct load module library is accessed and that the data set contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to this error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Try again. If the error persists, contact your system programmer.

EQQX164E

AN ERROR OCCURRED WHILE UPDATING THE RESOURCE DATASPACE

The request to update a special resource record failed because an error occurred when the general service task updated the resource data space.

The request is rejected.

Look for message EQQQ505E in the HCL Workload Automation for Z message log, EQQMLOG. This message contains additional information about the error. If the error persists, collect information in the form of the sequence of actions leading to this error and, if possible, the data it may be dependent on. Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX198E

ERROR, RC: XRC, RS: XRSN, FROM SUBSYSTEM RC: XSSRC, RS: XSSRS

A HCL Workload Automation for Z request failed with an error code that is not recognized by the message module. XRC, XRSN, XSSRC, and XSSRS provide debugging information.

The request is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX213E

The command is not valid for operations in X or W status.

The command submitted is not valid for operations in X (Suppressed by condition) or W (Wait) status. For example, you cannot submit a set NEXT logical status (N) command on operations in X or W status.

The command does not run.

Submit a command consistent with the current status of the operation.

EQQX220E

THE INPUT ENTERED IS TOO LONG

Data entry error; see Data entry errors.

The longest value accepted is HH.MM, where:

HH: The hour in the range 00–24
MM: The minute

Specify a value in the range 00–24 and rerun the task.

EQQX226E

HOUR PART MUST BE A NUMBER FROM 0 TO 99

Data entry error.

Specify a value in the range 0–99 and rerun the task. See Data entry errors.

EQQX227E

OPERATION DURATION MUST BE GREATER THAN 00.00

Data entry error; see Data entry errors.

Specify a value greater than 00.00 and rerun the task. See Data entry errors.

EQQX229E

OPERATION OP DEADLINE EARLIER THAN OPERATION INPUT ARRIVAL

The deadline must be the same as, or later than, the input arrival time.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Change the deadline or the input arrival time and resubmit the job. If the error persists, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX255E

BROWSE PERIOD NOT ALLOWED. ALARM=YES

It is not possible to perform a BROWSE PERIOD row command on rule-based run cycles.

The command is rejected.

Select an offset-based run cycle and rerun the task.

EQQX256E

MODIFY PERIOD NOT ALLOWED. ALARM=YES

It is not possible to perform a MODIFY PERIOD row command on rule-based run cycles.

The command is rejected.

Select an offset-based run cycle and rerun the task.

EQQX257E

GENDAYS NOT ALLOWED. ALARM=YES

It is not possible to perform a GEN row command on a run cycle that is offset-based and not rule-based.

The command is rejected.

Select a rule-based run cycle and rerun the task.

EQQX259E

NORMAL MODE MANAGER SUPPORT REQUIRED; TASK NOT ACTIVE

The request has resulted in a request to the HCL Workload Automation for Z subsystem. The request cannot be handled because the normal mode manager (NMM) is not active.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for messages concerning the NMM. Correct all errors and restart the HCL Workload Automation for Z subsystem.

Verify that the normal mode manager (NMM) is active. If it is not active, reactivate it and rerun the task.

EQQX260E

AN INTERNAL CONTROL BLOCK IS IN ERROR: REASON CODE XSSRS

Validation checking of the data received as input to a routine has detected a damaged control block. Reason code XSSRS provides debugging information. Reason code 102 is given when the dialog code is of an earlier release than the HCL Workload Automation for Z subsystem code.

The request is rejected.

Make sure that the correct load module library is set up to the HCL Workload Automation for Z subsystem and to the user. Check that the library contains the correct version of the HCL Workload Automation for Z modules. If the error persists, collect information in the form of the sequence of actions leading to this error and, if possible, the data it may be dependent on. Contact the Software Support.

If the reason code in the message is 102, check your ISPLLIB concatenation against the release of the subsystem that you are using. If the error persists, contact your system programmer.

EQQX261E

NOT ENOUGH STORAGE AVAILABLE: REASON CODE XSSRS

The general service task has failed to carry out a request due to failure to allocate enough virtual storage because either the controller or the server region is too small. Reason code XSSRS provides debugging information.

The request is rejected.

Allocate a larger region to the HCL Workload Automation for Z subsystem and restart the subsystem. If the error persists, contact the Software Support.

If possible try to limit the storage demand of the request. For example, if this is a request for a list of operations, choose a narrower selection criterion remembering that there is a limit of 16MB for all data transfers. If the error persists, contact your system programmer.

EQQX262E

TIME LIMIT EXCEEDED WHEN TRANSFERRING DATA FROM OR TO THE SUBSYSTEM

The request was terminated because the HCL Workload Automation for Z subsystem had to wait too long for data to be transferred to or from the dialog address space. The HCL Workload Automation for Z subsystem rejected the request to be able to service other requests.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for messages concerning the general service task and preceding the long delay. Correct all errors and restart the HCL Workload Automation for Z subsystem.

Try again, and if the error persists, contact your system programmer.

EQQX264E

THE REQUEST TO CHANGE THE OPERATION FAILED, REASON CODE XSSRS

The request to change the status of the operation was rejected by the event manager. Reason code XSSRS provides debugging information.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for messages concerning the event manager and those issued at the time of the request. Correct all errors and restart the HCL Workload Automation for Z subsystem. 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 critical path problems". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX265E

ATTEMPT TO READ A RECORD FAILED, REASON CODE XSSRS

The attempt to read a record failed. Reason code XSSRS provides debugging information.

The request is rejected.

Review the HCL Workload Automation for Z message log and look for I/O error messages issued at the time of the request. Correct all errors and restart the HCL Workload Automation for Z subsystem. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. 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 critical path problems". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQX266E

A JOBLIB OR PROCLIB RECORD READ FAILED, REASON CODE XSSRS

Reason code XSSRS gives the reason for the failure to read a record. The code issued depends on the type of request.

The reason codes and their meanings are:

1: The HCL Workload Automation for Z JCL library data set (EQQJBLIB) could not be opened. Message EQQW500E in the HCL Workload Automation for Z message log, when issued at the time of HCL Workload Automation for Z start, further explains the reason for the failure.
2: The HCL Workload Automation for Z JCL library data set (EQQJBLIB) contains records with invalid length. Message EQQW501E in the HCL Workload Automation for Z message log, when issued at the time of HCL Workload Automation for Z start, further explains the reason for the failure.
3: The joblib I/O exit, EQQUX002, was not loaded. Message EQQW521E in the HCL Workload Automation for Z message log, when issued at the time of HCL Workload Automation for Z start, further explains the reason for the failure.
4: The joblib I/O exit, EQQUX002, gave a return code of 241, which indicates that an I/O error has occurred in the exit routine. Message EQQW520E in the HCL Workload Automation for Z message log further explains the reason for the I/O error.
5: The joblib I/O exit, EQQUX002, gave a return code of 242, which indicates that it could not open one of its input data sets. Message EQQW516E in the HCL Workload Automation for Z message log further explains the reason for the I/O error.
6: The joblib I/O exit, EQQUX002, gave an invalid return code.

An empty JCL member is presented.

To determine the cause of the error, use the reason code and the corresponding message (if any) in the HCL Workload Automation for Z message log. Correct all errors and restart the HCL Workload Automation for Z subsystem. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Contact the Software Support.

Edit the empty JCL member. Notify your system programmer about the error.

EQQX267W

ACCESS REJECTED, DATA SET USED BY ANOTHER FUNCTION

The record could not be read because the data set was held for update by another HCL Workload Automation for Z function.

The request is rejected.

Try again later.

EQQX268W

UPDATE REJECTED, DATA SET USED BY ANOTHER FUNCTION

The record update could not be carried out because the data set was held for update by another HCL Workload Automation for Z function.

The request is rejected.

Try again later.

EQQX269E

THE LTP DATA SET IS BEING USED BY A BATCH FUNCTION, TRY LATER

You cannot access the long term plan (LTP) data set because it is being used by a batch function.

This message is issued during the invocation of a DP function, when a previous ongoing DP function did not release the LTP dataset yet.

The request is rejected.

You can repeat the request after few seconds: the invocation of the DP function is submitted successfully after that the following messages, related to the previous ongoing DP function, appear in the subsystem EQQMLOG:

EQQN051I A CURRENT PLAN BACKUP PROCESS HAS STARTED
...                                               
...                                               
EQQN090I THE JOB TRACKING LOG DATA SET DEFINED BY 
         DDNAME EQQJTxx HAS BEEN COPIED          
EQQN090I TO THE JOB TRACKING LOG ARCHIVE DATA SET

EQQX270E

THE JS DATA SET IS IN USE, TRY LATER

You have requested a function that requires access to the JCL repository file, but this file is not available.

The request is rejected.

Wait a few seconds and repeat the request.

EQQX271E

A SEVERE ERROR OCCURRED IN THE GENERAL SERVICE TASK

The request to use the general service function could not be granted because a severe error occurred in the general service task.

The request is rejected.

To determine the cause of the error, review the HCL Workload Automation for Z message log and look for messages concerning the general service task and those issued at the time of the request. Correct all errors and restart the HCL Workload Automation for Z subsystem. If the error persists, collect information in the form of the sequence of actions leading to the error and, if possible, the data it may be dependent on. Contact the Software Support.

Try again later. If the error persists, contact your system programmer.

EQQX274E

AN I/O REQUEST SPECIFIES TOO LARGE RECORD SIZE

The request to create or modify a record resulted in the record exceeding the maximum size of the VSAM record.

The request is rejected.

Check the record size against the VSAM file definition. For more information, refer to the Planning and Installation

Contact your system programmer.

EQQX275E

CANNOT DELETE FALSE CONDITIONS

The status of the condition you requested to delete is false. Conditions in false status cannot be deleted.

The request is rejected.

Check the condition status before repeating the request.

EQQX300E

AN APPLICATION DESCRIPTION RECORD IS TOO LARGE TO BE SAVED

The current application description (AD) record is larger than the maximum record size of the AD database.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support. If the current AD record is valid, it may become necessary to change the maximum record size of the AD file. The recommended way of doing this is to define a new VSAM cluster similar to the current AD file, but with a larger maximum record size. Copy the current AD file to the new AD file using IDCAMS REPRO. Change all JCL that references the old AD file so that it references the new AD file. Restart the controller and retry the failing AD file update request.

Check the entered data and, if the error occurred in batch, resubmit the job. The application may have to be split into two applications. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX301E

THE DB RECORD VERSION VERS IS INVALID

The version of the record is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures. If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX302E

THE APPLICATION ID AD IS INVALID

The application ID that was entered contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Enter a valid application ID and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX303E

STATUS AST FOR AD AD IS INVALID

The application status is not A or P in the indicated application description.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX304E

THE DB VALID-TO DATE VALTO IS INVALID

The valid-to date is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Enter a valid date and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX305E

THE RUN CYCLE POINTER IS INVALID

The pointer to the next run cycle is invalid. All run cycles must be before the first operation in the application description record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX306E

THE RECORD SIZE DOES NOT INCLUDE THE RUN CYCLE

The size of the application description record does not include the run cycles.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX307E

OFFSET TO NEXT RUN CYCLE IN RECORD IS INVALID

The offset to the next run cycle in the application description record is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX308E

THE OPERATION POINTER IS INVALID

All operations must be last in the application description record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX309E

THE RECORD SIZE DOES NOT INCLUDE OPERATION DATA

The size of the application description record does not include operation data.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX310E

OFFSET TO NEXT OPERATION IN RECORD IS INVALID

The offset to next operation in the application description record is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX311E

THE RECORD SIZE DOES NOT INCLUDE DEPENDENCIES AND SRS

The application description record size does not include dependencies and special resources.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX312E

THE DB VALID-FROM DATE VALFR IS INVALID

The valid-from date entered is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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. If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid date and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX313E

VALID-FROM DATE VALFR IS LATER THAN VALID-TO DATE VALTO

The valid-to date must be later than the valid-from date.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter correct dates and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX314E

AUTHORIZATION GROUP AUTHGR IS INVALID

The authorization group field contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid authorization group name and the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX315E

OWNER ID IS MISSING IN DBNAME

Owner ID is a required input field.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter an owner ID and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX316E

LATEST UPDATE DATE LUDATE IS INVALID OR MISSING

The date for the latest update is invalid or missing.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX317E

LATEST UPDATE TIME LUTIME IS INVALID OR MISSING

The time for the latest update is invalid or missing.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX318E

APPLICATION PRIORITY PRIO IS INVALID OR MISSING

The application priority is invalid or missing.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid application priority and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX319E

THE NUMBER OF OPERATIONS IS NOT IN THE RANGE 1 - 255

The number of operations cannot be less than one or greater than 255.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX320E

THE NUMBER OF RUN CYCLES NRUNC IS INVALID

The number of run cycles in the application description record is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX321E

THE DB RECORD IDENTIFIER RECID IS INVALID

The record identifier is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX322E

OFFSET TO FIRST RUN CYCLE IS INVALID IN AD AD

The offset to the first run cycle is invalid in the indicated application description record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX323E

OFFSET TO FIRST OPERATION IS INVALID IN AD AD

The offset to the first operation is invalid in the indicated application description record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX324E

INVALID CHARACTERS IN COMMON PART IN AD AD

The common part of the indicated application description contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX325E

INVALID CALENDAR ID CALID IN AD AD

An invalid calendar ID was entered in the indicated application description.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid calendar ID and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX326E

THE CALENDAR CALID DOES NOT EXIST

The calendar ID that was entered does not exist in the calendar database.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX327E

THE DB VALID-FROM TIME TVALFR INVALID

The valid-from time for the indicated record is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid date and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX328E

THE DB VALID-TO TIME TVALTO IS INVALID

The valid-to time for the indicated record is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid date and, if the error occurred in batch, resubmit the job.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX329E

THE RUN CYCLE PERIOD RUNPER CANNOT BE FOUND

The period that was entered could not be found in the calendar database.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support .

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX330E

A POSITIVE RUN DAY OFFSET IS NOT BLANK OR NUMERIC 1 - 999

The positive run day offset that was entered is not blank or a number from 1 to 999.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid offset and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX331E

THE FREE DAY SPECIFICATION FDRULE IS INVALID

The free day rule that was entered is not E, 1, 2, 3, or 4.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid free day rule and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX332E

THE RUN CYCLE TYPE RCTYPE IS INVALID. IT MUST BE N, X, R OR E

The run cycle type that was entered is invalid. Valid run cycle types are:

N: Normal offset-based run cycles
X: Negative offset-based run cycles
R: Regular rule-based run cycles
E: Exception rule-based run cycles.

The request to write the record is rejected.

Enter a valid run cycle type and, if the error occurred in batch, resubmit the job.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX333E

THE INPUT ARRIVAL TIME IAT IS INVALID

The input arrival time that was entered is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid time and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX334E

INVALID RELATIVE DEADLINE DAY DLINER, MUST BE NUMERIC 0 - 99

The relative deadline day that was entered is not a number from 0 to 99.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid relative day and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX335E

THE DEADLINE TIME DLINET IS INVALID

The deadline time that was entered is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid time and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX336E

INVALID CHARACTERS IN RUN CYCLE SECTION IN AD AD

The run cycle section in the indicated application description contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX337E

THE WORK STATION DESCRIPTION WS DOES NOT EXIST

The workstation description for the indicated workstation could not be found in the workstation database.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX338E

INVALID OPERATION NUMBER OP IN AD AD

The indicated operation number is invalid in the indicated application description.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid operation number and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX339E

THE DURATION OF OPERATION WSOP IS INVALID, DUR

The duration time is invalid for the indicated operation.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid duration time and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX340E

SMOOTHING FACTOR OF WSOP IS INVALID, SMOOTH, must be 0 - 999

The smoothing factor is not a number between 0 and 999.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid smoothing factor and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX341E

FEEDBACK LIMIT OF WSOP IS INVALID, FBLIM, MUST BE 100 - 999

The feedback limit is not a number between 100 and 999.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid feedback limit and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX342E

ERROR TRACKING INDICATOR OF WSOP IS INVALID, AEC, MUST BE Y or N

The error tracking indicator is not Y (yes) or N (no).

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid value and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX343E

THE JOBNAME JOBNAME INVALID IN OPERATION WSOP

The job name that was entered contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid job name and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX344E

START DAY OF WSOP IS INVALID, STRELD, MUST BE 0 - 99

The relative input arrival day of the indicated operation is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid day and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX345E

OPERATION WSOP INPUT ARRIVAL TIME IS INVALID

The input arrival time of the indicated operation is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid time and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX346E

DEADLINE DAY OF WSOP IS INVALID, DLINER, MUST BE 0 - 99

The relative deadline day of the indicated operation is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid day and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX347E

OPERATION WSOP DEADLINE TIME IS INVALID

The relative deadline time of the indicated operation is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid deadline time and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX348E

WS RESOURCE USAGE OF WSOP IS INVALID, RWS, MUST BE 0 - 99

The amount of workstation resource that was entered is not a number between 0 and 99.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a number between 0 and 99 and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX349E

NUMBER OF PS REQUIRED BY WSOP INVALID, PARSERV, MUST BE 1 - 99

The number of parallel servers for the indicated operation is not a number between 1 and 99.

If the operation is related to a shadow job, the number of parallel servers is not considered, but it is anyway required that you insert a valid number.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid number and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

If the operation is related to a shadow job, the number of parallel servers is not considered, but it is anyway required that you insert a valid number.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX350E

NUMBER OF INTERNAL PREDECESSORS NOINPR INVALID IN WSOP

The number of internal predecessors is invalid in the operation part of the application description record for the indicated operation.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX351E

NUMBER OF EXTERNAL PREDECESSORS NOEXPR INVALID IN WSOP

The number of external predecessors is invalid in the operation part of the application description record for the indicated operation.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX352E

NUMBER OF SPECIAL RESOURCES NOSR INVALID IN WS OP

The number of special resources is invalid in the operation part of the application description record for the indicated operation.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX353E

INVALID CHARACTERS IN OPERATION PART IN AD AD

The operation part of the indicated application description contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX354E

WORK STATION PREIWS IS INVALID AS A PREDECESSOR TO WSOP

The indicated internal predecessor workstation could not be found in the workstation description database.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX355E

INVALID OPERATION NUMBER IOP IN PREDECESSOR TO WSOP

The indicated internal predecessor operation number could not be found.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid operation number and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX356E

INVALID TRANSPORT TIME TRTI FOR PREDECESSOR PREIWSIOP

The transport time for the indicated internal predecessor is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid transport time and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX357E

INVALID CHARACTERS IN PREDECESSOR BLOCK FOR WSOP

The predecessor part for the indicated operation contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX358E

INVALID AD PREAD IN THE PREDECESSOR FOR WSOP

The indicated external predecessor application description (AD) could not be found in the AD database.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX359E

INVALID WORK STATION PREEWS IN THE PREDECESSOR FOR WSOP

The indicated external predecessor workstation could not be found.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX360E

INVALID OPERATION NUMBER EOP IN PREDECESSOR FOR WSOP

The indicated external predecessor operation number could not be found.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid operation number and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX361E

INVALID LTP PRINT OPTION LTPPO IN PREDECESSOR PREEWSEOP

The long term plan (LTP) print option in the indicated external predecessor is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid print option and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX362E

SPECIAL RESOURCE NAME IS BLANK IN OPERATION WSOP

The special resource name for the indicated operation is blank.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a special resource name and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX363E

SPECIAL RESOURCE HELD OPTION TYPE HOPT IS INVALID

The special resource held option type is not X or S.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid held option type and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX364E

SPECIAL RESOURCE BLOCK CONTAINS INVALID CHARACTERS

The special resource part in the application description contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX365E

DUPLICATE OPERATIONS OP EXIST IN AD AD

The indicated application description contains two or more operations with the same operation number.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter unique operation numbers for all operations and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX366E

A PREDECESSOR TO OPERATION WSOP DOES NOT EXIST

One predecessor for the indicated operation could not be found in the application description record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX367E

THERE IS A LOOP IN THE APPLICATION NETWORK

The application network contains a loop.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX368E

ALL OPERATIONS NOT IN NETWORK IN AD AD

All operations are not in the network in the indicated application description.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX369E

JOBNAME MISSING FOR OPERATION WSOP

The indicated job setup, processor, or print operation has no job name.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid job name and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX370E

JOB SETUP OPERATION WSOP HAS NOT A PROCESSOR SUCCESSOR

The indicated job setup operation does not have a processor successor.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX371E

PRINT OPERATION WSOP HAS NO PREDECESSOR

The indicated operation does not have a predecessor. A predecessor is required for print operations.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and, if the error persists, contact the Software Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX372E

PRINT OPERATION WSOP HAS MORE THAN ONE PREDECESSOR

Only one predecessor is allowed for print operations.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX373E

PRINT OPERATION WSOP HAS NOT A PROCESSOR PREDECESSOR

Print operations must have a processor as predecessor.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX374E

WSOP HAS A PREDECESSOR WITH A DIFFERENT JOBNAME

The indicated print operation has a predecessor with a different job name.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the job name and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX375E

THE RUN CYCLE VALIDITY END VALTO IS INVALID OR BEFORE/AT THE START

The run cycle valid-to date that was entered either is invalid or is not later than the start date.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid date and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX376E

A NEGATIVE RUN DAY OFFSET IS NOT BLANK OR NUMERIC 1 - 999

The negative run day offset that was entered is invalid.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid offset, and if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX377E

THE APPLICATION DESCRIPTION AD DOES NOT EXIST

The indicated application description (AD) does not exist in the AD database.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX378E

APPLICATION DESCRIPTION AD HAS NO WS WORK STATION

The indicated workstation does not exist in the indicated application description.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX379E

APPLICATION DESCRIPTION AD HAS NO OPERATION OP

The indicated operation does not exist in the indicated application description.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX380E

APPLICATION DESCRIPTION AD HAS NO WS OP operation

The indicated operation does not exist in the indicated application description.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX381E

RUN CYCLE VALID-FROM DATE VALFR IS INVALID OR MISSING

The valid-from date for the run cycle in invalid or missing.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid date, and if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX382E

APPLICATION ID AD IS NOT BRACKETED DBCS

The application identification field is specified to be in DBCS format, which means that it should start with a shift-out (X'0E') character and end with a shift-in (X'0F') character. Either shift-out or shift-in, or both, are missing.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX383E

OWNER ID OWNER IS NOT BRACKETED DBCS

The owner identification field is specified to be in DBCS format, which means that it should start with a shift-out (X'0E') character and end with a shift-in (X'0F') character. Either shift-out or shift-in, or both, are missing.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX384E

DBCS FIELD OF APPLICATION ID AD IS BLANK

The application identification field is blank, and as it must contain at least one DBCS character, it is invalid.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX385E

APPL ID AD CONTAINS UNPAIRED SHIFT-OUT / SHIFT-IN CHAR

The application identification field contains one or more superfluous shift-out or shift-in characters.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX386E

OWNER ID OWNER CONTAINS UNPAIRED SHIFT-OUT / SHIFT-IN CHAR

The owner identification field contains one or more superfluous shift-out or shift-in characters.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX387E

APPLICATION ID AD CONTAINS INVALID DBCS-CHARACTER(S)

The field indicated by the cursor contains out-of-range DBCS characters. With the exception of DBCS blank, X'4040', each byte must be in the range X'41'– X'FE'.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX388E

OWNER ID OWNER CONTAINS INVALID DBCS-CHARACTER(S)

The field indicated by the cursor contains out-of-range DBCS characters. With the exception of DBCS blank, X'4040', each byte must be in the range X'41'– X'FE'.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX389E

OWNER ID OWNER IS BLANK

The owner identification field is blank and, as it must contain at least one DBCS character, it is invalid.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX390E

THE APPLICATION ID WAS NOT SPECIFIED

No data has been entered in the application identification field.

An empty field is not accepted.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX391E

THE OWNER ID WAS NOT SPECIFIED

No data has been entered in the owner identification field.

An empty field is not accepted.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX392E

THE APPLICATION ID AD CONTAINS AN ODD NUMBER OF BYTES

The application identification field is specified as a DBCS field and requires two bytes per character. Hence, 2, 4, 6, …, bytes per character must be entered.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX393E

THE OWNER ID OWNER CONTAINS AN ODD NUMBER OF BYTES

The owner identification field is specified as a DBCS field and requires two bytes per character. Hence, 2, 4, 6, …, bytes per character must be entered.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX394E

ALL SPECIAL RESOURCES IN AN OPERATION MUST BE UNIQUE

A special resource must have a unique name in an operation.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check for misspellings or delete the duplicate entry. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX395E

ALL INTERNAL PREDECESSORS IN AN OPERATION MUST BE UNIQUE

A duplicate internal predecessor was found in an operation.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Delete the duplicate internal predecessor and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX396E

ALL EXTERNAL PREDECESSORS IN AN OPERATION MUST BE UNIQUE

A duplicate external predecessor was found in an operation.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Delete the duplicate external predecessor and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX397E

OWNER ID OWNER CONTAINS LOWER CASE CHARACTERS

The owner ID cannot contain lowercase characters.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX398E

DUPLICATE POSITIVE RUN DAY OFFSETS WERE FOUND IN A RUN CYCLE

All positive run day offsets must be unique in a run cycle.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Delete the duplicates and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX399E

DUPLICATE NEGATIVE RUN DAY OFFSETS WERE FOUND IN A RUN CYCLE

All negative run day offsets must be unique in a run cycle.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Delete the duplicate run days and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX400E

THE CALENDAR DATA BASE RECORD SIZE IS INVALID

The calendar description record cannot be greater than 32768 bytes (32KB) or less than the size of the common part of the calendar.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

If the size is too large, the calendar may have to be split into two calendars. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX401E

THE CALENDAR ID CALID IS INVALID

The calendar ID in the calendar description record either contains invalid characters or does not start with a capital letter or national language characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the calendar ID and retry. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX402E

WORK DAY END TIME IS INVALID OR MISSING

Work day end time must be a value in the range '0000' to '2400', where the first two characters represent the hour and the last two characters represent the minutes.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the time and retry. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX403E

NUMBER OF WEEKDAYS / SPECIFIC DATES IS INVALID

The number of weekday/specific dates has an invalid value in the calendar description record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Investigate the record and correct the error. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX404E

INVALID CHARACTERS IN COMMON SECTION OF CALENDAR

An invalid character was found in a reserved field in the common section of the calendar description record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Investigate the record and correct the error. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX405E

THE RECORD SIZE DOES NOT INCLUDE WEEK DAYS/SPECIFIC DATES

The total record size of the calendar description record is too short to contain the common section and all week days/specific dates.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Investigate the record and correct the error. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX406E

A WEEK DAY IN CALENDAR IS INVALID

For a week day, the second character in the variable section is blank. The first character has a value of 1 to 7, which corresponds with Monday to Sunday.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the day and retry. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX407E

WEEK DAYS IN CALENDAR ARE NOT IN ASCENDING ORDER

The week days are not correctly sorted.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the sequence and retry. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX408E

STATUS OF WEEK DAY / SPECIFIC DATE IS NOT WORK NOR FREE

The status of weekday/specific date in the calendar description record must be W (work) or F (free).

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the error and retry. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX409E

A SPECIFIC DATE IN CALENDAR IS INVALID

A specific date must have the format YYMMDD where YY is the last two characters in the year, MM is the month number, and DD is the day in the month.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the date and retry. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX410E

SPECIFIC DATES IN CALENDAR ARE NOT IN ASCENDING ORDER

Specific dates are not correctly sorted.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Correct the sequence and retry. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX411E

VARIABLE SECTION OF CALENDAR CONTAINS INVALID CHARACTERS

An invalid character was found in a reserved field in the variable section of the calendar description record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Investigate the record and correct the error. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX412E

CANCEL IF LATE IS ONLY ALLOWED FOR TIME JOBS

Cancel if late can only be specified for time-dependent jobs.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Specify cancel = no or make the operation time dependent. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX413E

RELATIVE START DAY IS MISSING FOR WSOP

If the operation is time dependent, an operation input relative start day must be specified.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a relative start day and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX414E

START TIME IS MISSING FOR WSOP

If the operation is time dependent, an operation input start time must be specified.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a start time and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX415E

JOBNAME IS MISSING IN OPERATION WSOP

Job name must be specified for the computer, printer, and job setup operations.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid job name and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX416E

JOB SETUP OPERATION WSOP HAS NO SUCCESSOR WITH SAME JOBNAME

The indicated job setup operation has no successor with the same job name.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Check and correct the job names for the computer operations succeeding the indicated operation. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX417E

THE VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER

Data entry error.

Specify a valid value and run the task again. See Data entry errors.

EQQX418E

THE VARIABLE TABLE IS NOT DEFINED IN THE AD FILE

Data entry error; see Data entry errors.

You have tried to define a variable table ID that does not exist in HCL Workload Automation for Z database.

Define the variable table an run the task again. See Data entry errors.

EQQX419E

NUMBER OF PARALLEL SERVERS MUST BE 1 FOR OPERATION WSOP

The specified operation runs on a computer workstation and can use only one parallel server.

The application description is not updated. The current application description record is printed on the dump data set (ddname EQQDUMP).

Change the number of parallel servers to one and, if the error occurred in batch, resubmit the batch job.

EQQX420E

REQUEST TYPE REQ IS NOT SUPPORTED

An internal parameter list, consisting of a sequence of control blocks, is validated and found to have an invalid request type.

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, make the dump data set and the message log available and contact the Software Support.

This is likely to be an internal error. If the error occurs in a program using the program interface function, do the requests in a different order and rerun.

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

EQQX421E

THE SPECIFIED CONTROL BLOCK LENGTH LEN IS INVALID

An internal parameter list, consisting of a sequence of control blocks, is validated and found to have an invalid length.

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, make the dump data set and the message log available and contact the Software Support.

This is likely to be an internal error. If the error occurs in a program using the program interface function, do the requests in a different order and rerun.

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

EQQX422E

THE INPUT ARRIVAL DATE IS REQUIRED BUT NOT AVAILABLE

The input arrival date is a required parameter in the request. No input arrival date is specified.

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.

Specify input arrival date as an argument in the program interface request.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX423E

INPUT ARRIVAL DATE IAD IS INVALID

The input arrival date is not a valid internal HCL Workload Automation for Z date, in the format YYMMDD.

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.

Correct the invalid date and rerun.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX424E

THE INPUT ARRIVAL TIME IS REQUIRED BUT NOT AVAILABLE

The input arrival time is a required parameter in the request. No input arrival time is specified.

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.

Specify input arrival time as an argument in the program interface request.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX425E

THE REQUEST CONTAINS INCONSISTENT APPLICATION IDS, AD and RAD

In the program interface request an application description is given by the data area parameter. The ID of an application is also given by the arguments parameters. The data area application description ID differs from the ID given by the arguments.

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.

Either set the data area pointer to zero or remove the application ID from the arguments parameter of the program interface request.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX426E

EITHER BOTH DEADLINE DATE AND TIME MUST BE GIVEN OR NEITHER DATE NOR TIME

If the deadline date is specified, the deadline time must also be specified, and vice versa.

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.

Specify both deadline date and deadline time or remove both from the arguments parameter of the program interface request.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX427E

THE DEADLINE DATE DLD IS INVALID

The deadline date is not a valid internal HCL Workload Automation for Z date, in the format YYMMDD.

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.

Correct the invalid date and rerun.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX428E

THE PREDECESSOR INPUT ARRIVAL DATE IS REQUIRED BUT NOT AVAILABLE

The predecessor input arrival date is a required parameter in the request. It is not specified.

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.

Specify predecessor input arrival date as an argument in the program interface request.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX429E

THE PREDECESSOR INPUT ARRIVAL TIME IS REQUIRED BUT NOT AVAILABLE

The predecessor input arrival time is a required parameter in the request. It is not specified.

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.

Specify predecessor input arrival time as an argument in the program interface request.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX430E

THE PREDECESSOR APPLICATION ID IS REQUIRED BUT NOT AVAILABLE

The predecessor application ID is a required parameter in the request. It is not specified.

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.

Specify the predecessor application ID as an argument in the program interface request.

The dump data set (ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.

EQQX431E

AST IS NOT A VALID STATUS CODE

Status AST is not a valid status code. The supported codes are V, T, S, and C.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and, if the error persists, contact the Software Support.

Enter a valid status code and resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX432E

AEC IS NOT A VALID CODE FOR ADDING FUNCTION

Code AEC specifies an updating function that is not supported.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If the error persists, contact the Software Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX433E

A MAXIMUM OF 100 EXTERNAL PREDECESSORS ARE ALLOWED

No more than 100 external predecessors can be specified in an application.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and, if the error persists, contact the Software Support.

Check the entered data and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX434E

IADIATAD CANNOT HAVE A DEPENDENCY ON ITSELF

An occurrence cannot be dependent on itself.

A dump of the record is written to the dump data set (EQQDUMP).

Check your dependency specifications.

EQQX435E

ROW COMMAND IS NOT VALID FOR A PENDING APPLICATION

Calculate and Print run days (A) row command is valid only for application versions that are active.

The request is rejected.

Use these row commands against only active applications.

EQQX436E

NO RUNCYCLE OFFSETS HAVE BEEN DEFINED FOR RUNCYCLE PERIOD = RUNPER

An attempt was made to save an invalid application description record. The record being saved contained a run cycle that did not have any run cycle offsets. This is not valid since each run cycle must contain at least one run cycle offset.

If this message is issued in a HCL Workload Automation for Z dialog, the dialog waits for you to correct the error. If the message is issued in a HCL Workload Automation for Z batch program, additional messages may be issued and the batch program may terminate. The invalid application description record is not saved.

Enter at least one run cycle offset value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX437E

NEGATIVE RUNDAY SPECIFICATION CONTAINS ERRORS

The runday fields in the current application description contain embedded blanks and the application description cannot be saved.

The dialog waits for you to correct the error.

Enter a valid runday value.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX438E

THE RESOURCE QUANTITY IS NOT IN THE RANGE 1 - 999,999

The quantity specified for a resource is not within the valid range.

The request to write the record is rejected.

Enter a valid resource quantity. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX439E

THE ON ERROR FIELD FOR A RESOURCE CONTAINS AN INVALID VALUE

The value of the On error field for a resource is invalid.

The request to write the record is rejected.

Enter a valid On error value. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX440E

THE ETT DATA BASE RECORD SIZE IS INVALID

The size of the record in the event-triggered tracking (ETT) database is not acceptable by the system.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

For further information, look in the dump data set (ddname EQQDUMP). The current record in the ETT database is printed in the dump data set and the position of the invalid field in the record is given.

EQQX441E

THE NAME OF THE ETT TRIGGER IS BLANK

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

For further information, look in the dump data set (ddname EQQDUMP). The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX442E

RESERVED FIELDS IN ETT RECORD MUST BE NULLS

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX443E

THE ALL WORK STATION CLOSED DATA BASE RECORD SIZE IS INVALID

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

For further information, look in the dump data set (ddname EQQDUMP). The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX444E

RESERVED FIELDS IN ALL WORK STATION CLOSED RECORD MUST BE BLANK

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX445E

THE PERIOD DATA BASE RECORD SIZE IS INVALID

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX446E

THE PERIOD INTERVAL START OR END DATE IS INVALID

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is rejected.

If the error occurred in batch, correct the record and resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX447E

RESERVED FIELDS IN PERIOD RECORD MUST BE BLANK

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX448E

PERIOD TYPE MUST BE REQCLEANUP - Created by ActiveSystems 12/10/99 Entity not defined., REQCLEANUP - Created by ActiveSystems 12/10/99 Entity not defined. OR REQCLEANUP - Created by ActiveSystems 12/10/99 Entity not defined.

Data entry error.

CYCA is the national language character for 'A' (?), CYCW is for 'W' (?), and CYCN is for 'N' (?).

Specify one of the valid values and run the task again. See Data entry errors.

EQQX450E

THE WORK STATION DATA BASE RECORD SIZE IS INVALID

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX451E

RESERVED FIELDS IN WORK STATION RECORD MUST BE BLANKS

The error is detected when you try to validate the record before writing it to the database.

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX452E

A DEADLINE TIME DLTIME BEFORE INPUT ARRIVAL TIME IAT WAS SPECIFIED

The deadline time specified is earlier than the input arrival time.

The request to write the record is rejected.

Specify a valid deadline time and, if the error occurred in batch, submit the job again.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX453E

AN INVALID WEEK DAY NAME WAS SPECIFIED

The error is detected when validating the record before writing it to the database.

The request to write the record is rejected.

If the error occurred in batch, correct the record and resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX454E

WEEK DAY/SPECIFIC DATES NOT ENTERED IN ASCENDING ORDER

The error is detected when validating the record before writing it to the database.

The request to write the record is rejected.

If the error occurred in batch, correct the record and resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the invalid field in the record is given.

EQQX455E

AN INVALID SPECIFIC DATE WAS SPECIFIED

Data entry error.

Specify a valid value and run the task again. See Data entry errors.

EQQX456E

INVALID DATES HAVE BEEN SPECIFIED FOR RUN DAYS GENERATION

For the specified rule, the application valid from date is greater than the application valid to date.

On the Application Description dialogs, check the valid from date and on the Run Days dialog, check the specified rules.

EQQX457E

NO RUN DAYS HAVE BEEN GENERATED FOR THIS RULE

The Gendays command has not generated run days for the specified rule.

Activate the General Service diagnose flag and look at the return code from the Spawner in EQQGSGNS.

EQQX458E

THE REPEAT EVERY REPEV IS INCORRECT FOR RUN CYCLE RUNC

The REPEAT EVERY value must be in the format HH.MM and within the range 00.01-23.59. If you set the REPEAT EVERY, you must also set the REPEAT END TIME.

The request to write the record is rejected.

Specify a valid value for the REPEAT EVERY.

EQQX459E

THE REPEAT END TIME REPET IS INCORRECT FOR RUN CYCLE RUNC

The REPEAT END TIME must be:

In the format HH.MM
In the range 00.00-23.59
Different from the input arrival time of the run cycle and work day end time of the application
A value between the input arrival time of the run cycle and the calendar work day end time of the application

If you set the REPEAT END TIME, you must also set the REPEAT EVERY.

The request to write the record is rejected.

Specify a valid value for the REPEAT END TIME.

EQQX461E

INCORRECT DEADLINE FEEDBACK LIMIT FBLIM FOR ADID. MUST BE 100-999

The deadline feedback limit must be a number from 100 to 999.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error.

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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

Enter a valid value for the feedback limit and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the error is given.

EQQX462E

FIELD HIPERBATCH IS INVALID, MUST BE Y OR N

The request to write the record is rejected.

Enter a valid Hiperbatch™ value. If the error occurred in batch, resubmit the job.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX463E

FIELD USED FOR IS INVALID, MUST BE N,P,C OR B

The request to write the record is rejected.

Enter a valid Used For value. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX464E

DAY OF WEEK MUST BE ZERO OR DATE MUST BE BLANK IN FIRST INTERVAL

The request to write the record is 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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Supportv.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. The first interval contains default values, that is, Day of Week must be zero or Date must be blank.

EQQX465E

DEFAULT QUANTITY INVALID, MUST BE IN INTERVAL 1 TO 999999.

The request to write the record is rejected.

Set Default Quantity in the common segment of the resource record to an integer value as given in the message. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX466E

DAY OF WEEK IS ZERO AND DATE IS BLANK IN INTERVAL OTHER THAN FIRST

The request to write the record is rejected.

The Day of week or Date must be specified in all but the first interval of a resource description. Set either Day of week to the value for a week day (1-7) or the value for the Standard day (8). In that case the Date field should be reset. Or, set the Day of week to 0 and the Date to a specific date in the form YYMMDD. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX467E

DEFAULT AVAILABILITY IS INVALID, MUST BE Y OR N

Enter a valid Default Avail value. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX468E

FIELD AVAIL IS INVALID IN INTERVAL IVLID. IT MUST BE Y, N OR BLANK

Enter a valid Avail value. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1-7), the standard day number (8) or a date, followed by the interval start time.

EQQX469E

INCORRECT DEADLINE SMOOTHING FACTOR SMOOTH FOR ADID. MUST BE 0-999

The deadline smoothing factor must be a number from 0 to 999.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Enter a valid value for the smoothing factor and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current record is printed in the dump data set and the position of the error is given.

EQQX470E

FIELD WEEK DAY IS INVALID IN INTERVAL IVLID, MUST BE IN RANGE 0-8

Enter a valid Week day value. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day number (8) or a date, followed by the interval start time.

EQQX471E

BOTH FIELD WEEK DAY AND DATE IN INTERVAL IVLID HAVE A VALUE

Reset either Week day or Date. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1-7), the standard day number (8) or a date, followed by the interval start time.

EQQX472E

FIELD DATE IS INVALID IN INTERVAL IVLID, MUST BE IN FORMAT YYMMDD

Enter a Date in format YYMMDD. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1-7), the standard day number (8) or a date, followed by the interval start time.

EQQX473E

FIELD FROM TIME IS INVALID IN INTERVAL IVLID, MUST HAVE FORMAT HHMM

Enter a From time in format HHMM. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1-7), the standard day number (8) or a date, followed by the interval start time.

EQQX474E

FIELD TO TIME IS INVALID IN INTERVAL IVLID, MUST BE IN FORMAT HHMM

Enter a To time in format HHMM. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1-7), the standard day number (8) or a date, followed by the interval start time.

EQQX475E

FIELD FROM TIME NOT EARLIER THAN TO TIME IN INTERVAL IVLID

Change the From time or To time, From time must be earlier than To time. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day number (8) or a date, followed by the interval start time.

EQQX476E

ANOTHER INTERVAL OVERLAPS INTERVAL IVLID

Change the From and To times in the interval definitions for the identified day. An interval may start on the same minute as the preceding interval ends, or later. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given. IVL identifies the interval by the week day number (1-7), the standard day number (8) or a date, followed by the interval start time.

EQQX477E

FIELD ONERROR IS INVALID, MUST BE F, FX, FS, K OR BLANKS

The request to write the record is rejected.

Set Onerror in the common segment of the resource record to a two character value as given in the message. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX478E

FIELD DEVIATION IS INVALID, MUST BE IN INTERVAL -999999 TO 999999

The request to write the record is rejected.

Set Deviation in the common segment of the resource description record to an integer value as given in the message. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX479E

FIELD GLOBAL AVAILABILITY IS INVALID, MUST BE Y, N OR A BLANK

The request to write the record is rejected.

Set Global (override) Availability in the common segment of the resource record to a one character value as given in the message. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX480E

FIELD GLOBAL QUANTITY IS INVALID, MUST BE IN INTERVAL 0 TO 999999

The request to write the record is rejected.

Set Global (override) Quantity in the common segment of the resource description record to an integer value as given in the message. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource description is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX481E

FIELD INTERVAL DATE IS OMITTED, THERE MUST BE A VALID DATE

The request to write the record is rejected.

Set Date in the interval segments of the resource record to a valid date. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX482E

FIELD INTERVAL QUANTITY IS NEGATIVE, MUST BE IN INTERVAL 0 TO 999999

The request to write the record is rejected.

Set Quantity in the interval segments of the resource record to a valid value. If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX483E

WORKSTATION NAME WS DOES NOT MATCH ANY EXISTING WORKSTATION

The request to write the record is rejected.

Set Workstation Names in the default segment and in the interval segments of the resource record to values that each match at least one of the workstation descriptions or, if this is a current plan resource, at least one of the current plan workstations. Or, if the error occurred in batch and it is a resource description, set the resource verification option to accept the workstation names as they are. The verification option can be set either via the program interface OPTIONS request or via the program interface INIT statement in the EQQYPARM file. Resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the invalid resource specification in the record is given.

EQQX484E

WORKSTATION NAME WS DOES NOT MATCH ANY EXISTING WORKSTATION

Remove the duplicate.

Review the dump data set (ddname EQQDUMP) for further information. The erroneous resource is printed in the dump data set and the position of the invalid specification is given.

EQQX485E

THE RESOURCE NAME MUST NOT BE BLANK.

The request to write the record is rejected.

Specify a valid resource name.

Review the dump data set (ddname EQQDUMP) for further information. The erroneous resource is printed in the dump data set and the position of the invalid specification is given.

EQQX486E

THE CRITICAL JOB ATTRIBUTE MUST BE P, W OR N.

The critical job attribute is invalid.

The request is rejected.

If you are using the programming interface, provide the correct critical job attribute, and if the error persists, contact the Software Support.

Enter a valid critical job attribute. If you cannot find a valid reason for the error, contact your system programmer.

EQQX487E

THE LATE JOB POLICY MUST BE E, D, L, C, OR BLANK

The late job policy is invalid. The only valid values are:

E: Estimated Duration. The job is assisted if it runs beyond its estimated duration.
D: Deadline. The job is assisted if it has not finished when its deadline time is reached.
L: Latest Start Time. The job is assisted if it is submitted after its latest start time.
C: Conditional An algorithm calculates whether to apply the Deadline policy or the Latest Start Time policy.
'': The scheduler WLM will eventually use the policy specified in OPCOPTS.

The request is rejected.

If you are using the programming interface, provide the correct late job policy attribute, and if the error persists, contact the Software Support.

Enter a valid late job policy attribute. If you cannot find a valid reason for the error, contact your system programmer.

EQQX488E

JCL SIZE RETRIEVED THROUGH EXIT2 CANNOT EXCEED 608 KB

The size of the JCL to be retrieved through the EXIT2 exceeds the documented limit of 608 000 bytes.

The request is rejected.

Reduce the size of the JCL to the lowest between the value of 608 000 bytes and the record size of the JCL repository. For information about JCL repository data sets, refer to Managing the Workload and Installation Guide.

EQQX489E

INVALID DURATION

Duration of operation WS OP is invalid, the value is DUR in the format FORMAT.

The request is rejected.

Set the correct duration value in the current FORMAT.

EQQX490E

FIELD ONCOMPLETE IS INVALID, MUST BE Y, N, R, OR BLANK

The controller received a request to write a special resource record, but the value of the On Complete field is not valid.

The request to write the record is rejected.

Set a correct value for the specified field (Y, N, R, or blank).

If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the incorrect resource specification in the record is given.

EQQX491E

FIELD MAXUSAGELIMIT IS INVALID, MUST BE IN RANGE 0 TO 999999

The controller received a request to write a special resource record but the value of the Max Usage Limit field is not valid.

The request to write the record is rejected.

Set a correct value for the specified field (an integer from 0 to 999999).

If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the incorrect resource specification in the record is given.

EQQX492E

FIELD MAXUSAGETYPE IS INVALID, MUST BE Y, N, OR R

The controller received a request to write a special resource record but the value of the Max Usage Type field is not valid.

The request to write the record is rejected.

Set a correct value for the specified field (Y, N, or R).

If the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current resource is printed in the dump data set and the position of the incorrect resource specification in the record is given.

EQQX493E

ON COMPLETE FIELD IS INVALID, MUST BE Y, N, R, OR BLANK

The controller received a request to write an operation record, but the special resource segment On Complete value is not valid.

The request to write the record is rejected.

Set a correct value for the specified field (Y, N, R, or blank).

If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current application description resource is printed in the dump data set and the position of the incorrect resource specification in the record is given.

EQQX500E

GROUP DEFINITION ID GRPDEF IS INVALID

The group definition ID field contains invalid characters.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error, contact the Software Support.

Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX501E

GROUP DEF ID GRPDEF NOT IN BRACKETED DBCS FORMAT

The group definition ID field should be in DBCS format, that is, it should start with a shift-out (X'0E') character and end with a shift-in (X'0F') character. Either shift-out or shift-in, or both, are missing.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error, contact the Software Support.

Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX502E

UNPAIRED SHIFT-OUT OR SHIFT-IN CHARS IN GRPDEF

The group definition ID field contains one or more extra shift-out or shift-in characters.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error, contact the Software Support.

Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX503E

INVALID DBCS-CHARACTER(S) IN GRPDEF

The group definition ID field contains out-of-range DBCS characters. With the exception of DBCS blank, X'4040', each byte must be in the range X'41' to X'FE'.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error, contact the Software Support.

Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX504E

ODD NUMBER OF BYTES IN GRPDEF

The group definition ID field is specified as a DBCS field and requires two bytes per character, that is, the number of bytes must be a multiple of two.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error, contact the Software Support.

Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX505E

NO ID SPECIFIED FOR DBCS GROUP DEFINITION

The group definition ID field contains shift-out and shift-in DBCS characters, but you have not specified a valid value for the group definition.

The data is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error, contact the Software Support.

Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot find the reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX506E

THE APPLICATION DESCRIPTION (GROUP DEFINITION) GRPDEF DOES NOT EXIST

The request to write the record is rejected.

Set Application Group Definition in the common segment of the application description record to the name of an existing application description that is defined as an Application Group Definition. Or, if the error occurred in batch, set the Application Group verification option to accept the application group names as they are. Use either the program interface OPTIONS request or the program interface INIT statement in the EQQYPARM file to set the verification option. Resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Review the dump data set (ddname EQQDUMP) of the controller for further information. The current application description is printed in the dump data set and the position of the invalid specification in the record is given.

EQQX507E

EXTENDED INFORMATION ARE ASSOCIATED TO AN INVALID OP NUMBER

A program interface (PIF) program has requested an ADEXT insert with an invalid argument in OWNOPN value.

The request is rejected.

Correct the PIF program and resubmit the job.

EQQX508E

OPERATION OPN HAS MORE THAN 40 DEPENDENCIES

The request failed because the GENERAL SERVICE task detected more than 40 dependencies defined for the operation. A dependency can be:

a predecessor operation;
one or more special resources required by the operation. In this case, one dependency has to be considered regardless the number of required resources.

The request is rejected.

Check the controller message log for EQQG016E message. It provides the complete key of the object which breaks the dependencies limit. Decrease the number of dependencies specified for the operation and repeat the request.

EQQX509E

CANNOT APPLY RC RESTART TO A NOPED OPERATION

You cannot execute the following restart and clean actions: STEP RESTART, JOB RESTART, FSR and FJR fast commands, to a noped operation.

RESTART is not executed.

None.

EQQX510E

REMOTE JOB INFORMATION CANNOT BE SPECIFIED FOR OPERATION OP

You are creating or modifying an operation defined to run on a workstation that is not a remote engine workstation. For this operation you cannot specify the remote job information.

The data is rejected.

Correct the data and reenter. If the error occurred in batch, resubmit the job.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX511E

REMOTE JOB INFORMATION MUST BE SPECIFIED FOR OPERATION OP

You are creating or modifying an operation defined to run on a remote engine workstation. For this operation you must specify the remote job information.

The data is rejected.

Correct the data and reenter. If the error occurred in batch, resubmit the job.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX512E

COMPLETE IF BIND FAILS OPTION MUST BE Y OR N FOR OPERATION OP

The only correct values for the “Complete if bind? option are Y or N.

The request is rejected.

Check the entered data and correct it, if the error occurred in batch, submit the job again.

EQQX513E

REMOTE APPLICATION ID IS MISSING OR INVALID FOR OPERATION OP

No data has been entered in the remote application ID field or the remote application ID that was entered contains invalid characters.

The request to write the record is rejected.

Enter a valid application ID and, if the error occurred in batch, resubmit the job.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX514E

REMOTE OPERATION NUMBER MUST BE 1-255 FOR OPERATION OP

The indicated remote operation number is invalid. It must be a number in the range 1-255.

The request to write the record is rejected.

Enter a valid operation number and, if the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX515E

REMOTE JOB NAME IS MISSING OR INVALID FOR OPERATION OP

No data has been entered in the remote job name field or the remote job name that was entered contains invalid characters.

The request to write the record is rejected.

Enter a valid job name and, if the error occurred in batch, resubmit the job.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX516E

REMOTE JOB STREAM WORKSTATION IS MISSING OR INVALID FOR OP OP

No data has been entered in the remote job stream workstation name field or the remote job stream workstation name that was entered contains invalid characters.

The request to write the record is rejected.

Enter a valid job stream workstation and, if the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX517E

REMOTE JOB STREAM NAME IS MISSING OR INVALID FOR OPERATION OP

No data has been entered in the remote job stream name field or the remote job stream name that was entered contains invalid characters.

The request to write the record is rejected.

Enter a valid job stream name and, if the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX518E

REMOTE APPLICATION ID CONTAINS AN ODD NUMBER OF BYTES FOR OP OP

The remote application identification field is specified as a DBCS field and requires two bytes per character. Hence, 2, 4, 6, ..., bytes per character must be entered.

The data is rejected.

Correct the data and reenter. If the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX519E

REMOTE APPLICATION ID IS NOT BRACKETED DBCS FOR OPERATION OP

The remote application identification field is specified to be in DBCS format, which means that it should start with a shift-out (X'0E') character and end with a shift-in (X'0F') character. Either shift-out or shift-in, or both, are missing.

The data is rejected.

Correct the data and reenter. If the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX520E

REMOTE JOB INFORMATION CANNOT BE SPECIFIED FOR OPERATION OP

The remote application identification field is blank, and as it must contain at least one DBCS character, it is invalid.

The data is rejected.

Correct the data and reenter. If the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX521E

REMOTE APPL ID CONTAINS UNPAIRED SHIFT-OUT/SHIFT-IN CHAR FOR OP OP

The remote application identification field contains one or more superfluous shift-out or shift-in characters.

The data is rejected.

Correct the data and reenter. If the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX522E

REMOTE APPLICATION ID CONTAINS INVALID DBCS-CHARACTER(S) FOR OP OP

The field indicated by the cursor contains out-of-range DBCS characters. With the exception of DBCS blank, X'4040', each byte must be in the range X'41'– X'FE'.

The data is rejected.

Correct the data and reenter. If the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX523E

RESOURCES AND CONDITIONS CANNOT BE SPECIFIED FOR OPERATION OP.

The specified operation is a shadow job. Shadow jobs cannot have special resources, resources or conditions defined.

The request to write the record is rejected.

Correct the definition and, if the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX524E

SCHEDULING ENVIRONMENT CANNOT BE SPECIFIED FOR OPERATION OP.

The specified operation is a shadow job. Shadow jobs cannot use scheduling environment.

The request to write the record is rejected.

Correct the definition and, if the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX525E

DEADLINE WTO MESSAGES CANNOT BE ISSUED FOR OPERATION OP.

The specified operation is a shadow job. Shadow jobs cannot have deadline WTO option set to Y.

The request to write the record is rejected.

Correct the definition and, if the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX526E

OPERATION OP CANNOT BE SET ELIGIBLE FOR WLM ASSISTANCE.

The specified operation is a shadow job. Shadow jobs cannot have critical job option set to W.

The request to write the record is rejected.

Correct the definition and, if the error occurred in batch, submit the job again.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the failing record and the position of the error.

EQQX530E

A RUN CYCLE GROUP RECORD CANNOT BE SAVED BECAUSE IS TOO SHORT

The size of the current application description (AD) record is less than the minimum record size of the AD database.

The request to write the record is rejected.

Check the entered data and, if the error occurred in batch, resubmit the job.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX531E

THE RUN CYCLE GROUP ID RG IS INVALID

The run cycle group ID that was entered contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Enter a valid run cycle group ID and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX532E

THE RULE NAME MUST BE UNIQUE WITHIN A RUN CYCLE GROUP

You have specified a rule name that has already been defined in this run cycle group.

The request is rejected.

Specify a unique rule name.

EQQX533E

OFFSET TO FIRST RUN CYCLE IS INVALID IN RG RG

The offset to the first run cycle is invalid in the indicated run cycle group record.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX534E

INVALID CALENDAR ID CALID IN RG RG

An invalid calendar ID was entered in the indicated run cycle group.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Enter a valid calendar ID and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX535E

INVALID CHARACTERS IN COMMON PART IN RG RG

The common part in the indicated run cycle group contains invalid characters.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX536E

A VALID RULE NAME MUST BE SPECIFIED

You have not entered a valid rule name. A valid rule name has a maximum of 8 characters, where the first character is alphabetical and the remaining characters are alphanumeric or national.

The request is rejected.

Specify a valid rule name.

EQQX537E

THE RULE ON WHICH THE RUN CYCLE IS BASED MUST BE DEFINED

A run cycle was inserted or replicated in the run cycle group, but no rule definition was specified.

The request is rejected.

Use the S row command to select the Rule Modification panel and define the rule.

EQQX538E

RUN CYCLE RUN_CYCLE_ID IN RG RG HAS NO IA TIME NOR DEFAULT VALUE

The input arrival time is mandatory in a run cycle group, either at run cycle group level or in each run cycle of the group.

The request is rejected.

Specify an IA time either for the run cycle group (which becomes the default for all run cycles in the group) or for each run cycle in the group.

EQQX539E

THE FREE DAY SPECIFICATION FDRULE IS INVALID

The free day rule that was entered is not E, 1, 2, 3, or 4.

The request to write the record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Enter a valid free day rule and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX540E

THE RUN CYCLE TYPE RCTYPE IS INVALID. IT MUST BE R, E, A, OR D

The run cycle type that was entered is invalid. Valid run cycle types are:

R: Regular rule-based run cycles
E: Exception rule-based run cycles.
A: Regular rule-based run cycles belonging to the same set.
D: Exception rule-based run cycles belonging to the same set.

The request to write the record is rejected.

Enter a valid run cycle type and, if the error occurred in batch, resubmit the job.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX541E

MULTIPLE INSTANCES DETECTED. SPECIFY IA TO OVERRIDE THEM.

Multiple instances have been detected. They cannot be accepte.d

None.

Specify an Input Arrival in the application to ignore the detected multiple instances.

EQQX542E

THE RUN CYCLE SUBSET ID IS INVALID

One or more invalid characters were used in the subset name. Only alphanumeric characters are admitted.

The run cycle is not saved.

Use only alphanumeric characters to specify the subset name.

EQQX550E

NO VARIABLE VALUE WAS SPECIFIED.

This message is issued because a variable run cycle name was specified, without at least one of the available variable fields:

Duration
Deadline
NOP option
Critical job indicator
Not started alert
Not started action

The request to write the record is rejected.

Specify at least one of the variable values listed in the explanation.

EQQX551E

THE VARIABLE DURATION VDUR SECx100 SPECIFIED IS NOT VALID.

The variable duration time is not valid.

The request to write the record is rejected.

Set the correct variable duration value in the format SECx100.

EQQX552E

THE VARIABLE DEADLINE DAY VDEADD IS NOT VALID, MUST BE NUMERIC 0-99.

The variable relative deadline day that was entered is not a number from 0 to 99.

The request to write the record is rejected.

Enter a correct variable relative deadline day.

EQQX553E

THE VARIABLE DEADLINE TIME VDEADT IS NOT VALID

The variable deadline time that was entered is not valid.

The request to write the record is rejected.

Specify a correct variable deadline time.

EQQX554E

A RCG OR RULE MUST BE ASSOCIATED IF AT LEAST ONE VARIABLE VELUE IS SET.

You specified at least one variable value, but you did not associated that value with an existing run cycle group or a rule defined in the application.

The request to write the record is rejected.

Specify either an existing run cycle group or application rule.

EQQX555E

VRCG SET FOR VARIABLE VALUES IS NOT A RUN CYCLE GROUP NOR APPL RULE.

You specified a run cycle group or application rule to be associated with a variable value that does not correspond to an existing run cycle group or application rule.

The request to write the record is rejected.

Specify an existing run cycle group or application rule.

EQQX556E

VRCG SET FOR VARIABLE DURATION OR DEADLINE IS NOT UNIQUE.

The same rule name was specified twice.

The request to write the record is rejected.

Remove the duplicated entry.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX557E

VARIABLE DEADLINE EARLIER THAN OPERATION INPUT ARRIVAL.

The operation input arrival time that was specified is later than one or more variable deadlines specified for the application.

The request is rejected.

Specify an IA time that is earlier than the deadline.

EQQX601E

CONNINFO FUNC IN STATE STATE FAILED, RC RC, RS RS, TCPIPMSG.

The TCP/IP communication between the server and either the dialog or the program interface application failed. The server issued a TCP/IP service request that ended with a nonzero return code.

The server deallocates the TCP/IP conversation. The communication between the server and either the dialog or the program interface application is broken.

Check the meaning of the TCP/IP return codes. In case of SSL error, the most common causes are listed in SSL errors. CONNINFO contains the IP address and the port number of the server you are connecting to. TCPIPMS contains an additional diagnostic message. If the problem recurs, report the error to IBM Software Support.

EQQX602E

THE COMMUNICATION WAS UNEXPECTEDLY RESET BY THE PEER.

A problem occurred at the server side. Most common causes of this problem are:

The server was stopped.
The partner connection parameters are inconsistent.

The server closes the TCP/IP connection. Contact between the remote interface and subsystem is lost. The partner of the TCP/IP connection is informed about the error.

Check the status of the server and the connection parameters. Look for additional information in the peer EQQMLOG. If the problem persists, report the error to IBM Software Support.

EQQX604E

SELECT ONE OF THE LU NAME LINES

There must be at least one entry in the subsystem name table and exactly one row must be selected by a / in the first column.

The system waits for you to respond.

If you are logged on to TSO on the z/OS where the controller is running, select the row with the Controller subsystem name and no Server LU name. If you are logged on to TSO on another z/OS, select a row with a LU name specified, thereby selecting the proper Controller subsystem and the LU name of the Server handling the communication to the Controller.

EQQX605E

SELECT ONE AND ONLY ONE OF THE LU NAME LINES

Only one of the entries in the subsystem name table can be selected by a / in the first column.

The system waits for you to respond.

If you are logged on to TSO on the z/OS where the controller is running, select the row with the Controller subsystem name and no Server LU name. If you are logged on to TSO on another z/OS, select a row with a LU name specified, thereby selecting the proper Controller subsystem and the LU name of the Server handling the communication to the Controller.

EQQX606E

EACH ROW MUST HAVE A DIFFERENT SUBSYSTEM NAME/LU/HOST NAME COMBINATION.

The subsystem name table must have unique rows.

The system waits for you to respond.

Remove one of the rows with the same values on both controller subsystem name and server destination.

EQQX607E

EACH ROW MUST SPECIFY ONE PROTOCOL. HOST NAME AND LU NAME ARE BOTH SET.

Select either the APPC or the TCP/IP communication protocol to perform the remote logon to the subsystem. The LU NAME field is used for APPC, while the HOST NAME field is used for TCP/IP. You cannot specify both.

The logon parameters are not saved.

Deselect the unneeded value.

EQQX608E

VALID VALUES FOR PORT NUMBER ARE FROM 0 TO 65535.

Data entry error; see Data entry errors.

EQQX609E

ERROR IN PARSING TCPOPTS STATEMENTS OR MSG LOG MISSING.

An error occurred while processing the TCPOPTS statement during the remote dialog execution. Either the TCPOPTS statement contains a syntax error or the TSO logon procedure does not specifies the EQQMLOG file.

The request is rejected.

Check the TSO user EQQMLOG file to identify the reason for the TCPOPTS parsing error. If you do not find the EQQMLOG file, you might have missed to define the EQQMLOG DD statement in the TSO logon procedure: this can be confirmed by message EQQZ030E in the TSO user JESMSGLG file.

EQQX610E

VERB IN STATE STATE FAILED, RC RC, SR SR, DR DR

An APPC service request issued for server communication failed. The verb VERB was issued when the conversation was in state STATE. APPC returned: Return_Code RC, Status_Received SR and Data_Received DR.

The request is rejected.

Check the meaning of the APPC return codes (see EQQXnnn messages). Check the message log of the server for a message explaining the communication loss. If the error recurs, report the error to IBM Software Support.

Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z primary option panel or rerun the program interface application.

EQQX611E

APPC/MVS VERB VERB FAILED RC RC, SR SR, DR DR

An APPC service request issued for server communication failed. The verb VERB was issued when the conversation was in state STATE. APPC returned: Return_Code RC, Status_Received SR and Data_Received DR.

The request is rejected.

Check the meaning of the APPC return codes (see EQQXnnn messages). Check the message log of the server for a message explaining the communication loss. If the error recurs, report the error to IBM Software Support.

Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z primary option panel, or rerun the program interface application.

EQQX612E

INSUFFICIENT VIRTUAL STORAGE, DIAGNOSTIC INFO ALT

A routine for communication with the server failed because it could not obtain sufficient amount of virtual storage.

The request is rejected.

Log on to TSO with a larger SIZE parameter value or rerun the program interface application with a larger specified region.

EQQX614E

REQUEST FAILED, SEVERE ERROR AT SERVER LU

An error occurred at the server preventing it from completing a service.

The dialog or program interface application cannot continue.

Check the message log of the server for a message explaining the error at the server.

Check the message log of the server for a message explaining the communication problem. If the problem recurs, report the error to IBM Software Support.

Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z primary option panel, or rerun the program interface application.

EQQX615E

FAILED TO SET UP COMMUNICATION WITH SERVER LU, RC RC

An APPC allocate request issued for server communication failed. LU shows the LU name of the server. RC shows the return code of the Allocate request.

The user cannot enter the scheduler dialog. The INIT request of program interface application gets a return code of 8.

Check the meaning of the APPC return codes (see EQQXnnn messages). Check the message log of the server for a message explaining the communication loss. If the error recurs, report the error to IBM Software Support.

Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z primary option panel or rerun the program interface application.

EQQX616E

SECURITY ENVIRONMENT CREATE FAILED, THE SERVER RECEIVED NO USERID

No user ID was available for the server. It is required by the server when building a security environment for this user.

The user cannot start the scheduler dialog via this server. The INIT request of program interface application gets a return code of 8.

Check that the LU name has been defined in the APPL statement, in SYS1.VTAMLST. Refer to the Planning and Installation for the correct value of the SECACPT keyword. For the dialog the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z primary option panel or rerun the program interface application.

EQQX617E

SECURITY ENVIRONMENT CREATE FAILED, SAF RC XSSRC RACF RC XSSRS, RS XSSAB

The server failed to create a security environment for this user. The SAF return code and the RACF return and reason codes of the failing RACROUTE VERIFY=CREATE is given in the message.

The user cannot start the scheduler dialog remotely. The INIT request of program interface application gets a return code of 8.

If you are using APPC communication, check that the correct LU name is specified. For the dialog, the LU name is set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z primary option panel or rerun the program interface application.

If you are using the TCP/IP communication to access HCL Workload Automation for Z, you should check the authorizations related to the RACF user linked to the HCL Workload Automation for Z user provided by the API or Dynamic Workload Console.

EQQX618E

THE TCP/IP COMMUNICATION SUBTASK ABENDED.

The ISPF dialog abnormally ended during the current dialog-to-server TCP/IP session.

The dialog-to-server TCP/IP session and the TCP/IP server subtask abnormally end.

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". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at Support.

EQQX619E

THE CONNECTION TIMEOUT EXPIRED, THE CONNECTION WAS NOT ESTABLISHED.

This message is issued on the client when the connection cannot be established within the time specified in the CONNTIMEOUT parameter. This condition might occur because the server has temporarily reached the maximum number of concurrent connection requests it can manage. Message EQQPH49W is also issued in the server MLOG.

The connection is rejected, and the client receives an error.

On the client, increase the value set for the CONNTIMEOUT parameter.

EQQX620E

VERB in state STATE failed, RC RC, SR SR, DR DR, APPCMSG MID

An APPC service request issued for server communication failed. The verb VERB was issued when the conversation was in state STATE. APPC returned: Return_Code RC, Status_Received SR, Data_Received DR and APPC_Message_Code MID.

The request is rejected.

Check the meaning of the APPC return codes (see EQQXnnn messages). Check the message log of the server for a message explaining the communication loss. If the error recurs, report the error to IBM Software Support.

Check that the proper LU name is specified. For the dialog the LU name is set through the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT request. Repeat the dialog action from the HCL Workload Automation for Z primary option panel or rerun the program interface application.

EQQX700E

PREDECESSOR PREAD EOP NOT VALID MANDATORY FOR WS OP.

The Application Description validation failed. The predecessor identified by Application name PREAD and Operation number EOP, and referenced by the operation identified by workstation WS and operation number OP contains an invalid value in the Is mandatory field.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid Is mandatory value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX701E

PREDECESSOR PREAD EOP NOT VALID CRITERIA FOR WS OP.

The Application Description validation failed. The predecessor identified by Application name PREAD and Operation number EOP, and referenced by the operation identified by workstation WS and operation number OP contains an invalid value in the Dependency field.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid dependency value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX702E

PREDECESSOR PREAD EOP NOT VALID ADID FOR WS OP.

The Application Description validation failed. The external predecessor identified by Application name PREAD and Operation number EOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid application name.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid dependency interval. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX703E

PREDECESSOR PREAD EOP NOT VALID OP.NUM FOR WS OP.

The Application Description validation failed. The external predecessor identified by Application name PREAD and Operation number EOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid operation number.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid operation number. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX704E

PREDECESSOR PREAD EOP NOT VALID TYPE FOR WS OP.

The Application Description validation failed. The external predecessor identified by Application name PREAD and Operation number EOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid resolution criteria value.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid resolution criteria. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX705E

PREDECESSOR PREAD EOP NOT VALID FROM: FOR WS OP.

The Application Description validation failed. The external predecessor identified by Application name PREAD and Operation number EOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid FROM: value.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid FROM: value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX706E

PREDECESSOR PREAD EOP NOT VALID TO: FOR WS OP.

The Application Description validation failed. The external predecessor identified by Application name PREAD and Operation number EOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid TO: value.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid TO: value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX707E

COND. PRED. SCID SCAD SCOP NOT VALID ADID FOR WS OP.

The Application Description validation failed. The conditional external predecessor identified by Condition Id SCID, Application name SCAD, and Operation number SCOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid Application name.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid Application name. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX708E

COND. PRED. SCID SCAD SCOP NOT VALID OP.NUM FOR WS OP.

The Application Description validation failed. The conditional external predecessor identified by Condition Id SCID, Application name SCAD, and Operation number SCOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid operation number.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid operation number. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX709E

NUMBER OF EXTERNAL PRED. IVL NOEXPR NOT VALID IN WS OP.

The Application Description validation failed. The number of external predecessor intervals NOEXPR in the operation identified by workstation WS and operation number OP contains an invalid value: it must be 0 or greater.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid number of external predecessor intervals. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX710E

NUMBER OF CONDITIONAL PRED. IVL NOEXPR NOT VALID IN WS OP.

The Application Description validation failed. The number of conditional predecessor intervals NOEXPR in the operation identified by workstation WS and operation number OP contains an invalid value: it must be 0 or greater.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid number of conditional predecessor intervals. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX711E

COND. PRED. SCID SCAD SCOP NOT VALID IVL TYPE FOR WS OP.

The Application Description validation failed. The conditional external predecessor identified by Condition Id SCID, Application name SCAD, and Operation number SCOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid resolution criteria value.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid resolution criteria value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX712E

COND. PRED. SCID SCAD SCOP NOT VALID FROM: FOR WS OP.

The Application Description validation failed. The conditional external predecessor identified by Condition Id SCID, Application name SCAD, and Operation number SCOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid FROM: value.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid FROM: value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX713E

COND. PRED. SCID SCAD SCOP NOT VALID TO: FOR WS OP.

The Application Description validation failed. The conditional external predecessor identified by Condition Id SCID, Application name SCAD, and Operation number SCOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid TO: value.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid TO: value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX714E

COND. PRED. SCID SCAD SCOP NOT VALID COND ID: FOR WS OP.

The Application Description validation failed. The conditional external predecessor identified by Condition Id SCID, Application name SCAD, and Operation number SCOP, and referenced by the operation identified by workstation WS and operation number OP contains an interval definition with an invalid Condition id value.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid Condition id value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX715E

NO EXTERNAL PRED FOUND FOR EXT PRED IVL PREAD EOP.

The Application Description validation failed. The external predecessor interval must refer to en existing external predecessor. This is not true for the external predecessor identified by Application name PREAD and by operation number EOP.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify an existing external predecessor. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX716E

NO EXTERNAL PRED FOUND FOR EXT COND IVL SCID SCAD SCOP.

The Application Description validation failed. The conditional external predecessor interval must refer to en existing external predecessor. This is not true for the conditional external predecessor identified by Condition id SCID, Application name SCAD, and operation number SCOP.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify an existing external predecessor. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX717E

CRITERIA DEFINITION NOT COHERENT WITH INTERVAL DEFINITION.

The Application Description validation failed. The conditional or external predecessor interval type is not coherent with the resolution criteria value. For example, this can happen if a resolution criteria R is specified but no interval definition, or an absolute interval, is provided.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a coherent definition. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX719E

NOT VALID DEPENDENCY RESOLUTION FROM SPECIFICATION IN WS OP.

The Application Description validation failed. The value in the FROM field in the Resolution criteria data for the cross dependency predecessor is not valid for the operation identified by workstation WS and by operation number OP.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid FROM value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX720E

NOT VALID DEPENDENCY RESOLUTION TO SPECIFICATION IN WS OP.

The Application Description validation failed. The value in the TO field in the Resolution criteria data for the cross dependency predecessor is not valid for the operation identified by workstation WS and by operation number OP.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid TO value. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX722E

COND. PRED. SCID SCAD SCOP NOT VALID CRITERIA FOR WS OP.

The Application Description validation failed. The conditional external predecessor identified by Condition Id SCID, Application name SCAD, and Operation number SCOP, and referenced by the operation identified by workstation WS and operation number OP contains an invalid value for the resolution criteria.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid value for the resolution criteria. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX723E

START IS AFTER END OF EXT PRED IVL PREAD EOP FOR WS OP.

The Application Description validation failed. The external predecessor identified by Application name PREAD and Operation number ECOP, and referenced by the operation identified by workstation WS and operation number OP contains an invalid resolution criteria interval. This is because the start of the interval was defined to be later than the end.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid value for the resolution criteria interval. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX724E

START IS AFTER END OF COND PRED IVL SCID SCAD SCOP FOR WS OP.

The Application Description validation failed. The conditional external predecessor identified by Condition id SCID, Application name SCAD, and Operation number SCOP, and referenced by the operation identified by workstation WS and operation number OP, contains an invalid resolution criteria interval. This is because the start of the interval was defined to be later than the end.

The request to write the AD record is rejected.

Review the HCL Workload Automation for Z message log to determine the cause of the error. If you cannot determine the cause of the error and the error persists, contact the Software Support.

Specify a valid value for the resolution criteria interval. If the error occurred in batch, submit the job again. If you cannot find a valid reason for the error, contact your system programmer.

Look in the dump data set (ddname EQQDUMP) for further information. This data set contains a copy of the record and the position of the error.

EQQX725E

USER LEVEL IS LOWER THAN CONTROLLER LEVEL: CANNOT GET AD.

This message is issued when you try to access an Application Description that has application dependencies, but you are not using the level of code required to access this kind of objects. The user code level is identified by the USRLEV value.

The request is rejected.

Ensure that you are using the appropriate level of code, which is identified by the value in USRLEV. Note that if you are changing the user level value, you must recompile your user-written program to see the changed layouts.

EQQX726E

NOT STARTED DAY OF WS OP IS INVALID, DLINER, MUST BE 0-99.

The not started day specified for the indicated operation is not valid.

The request to write the record is rejected.

To determine the cause of the error, review the HCL Workload Automation for Z message log. To collect appropriate documentation for problem determination, see the section about the problem analysis procedures in Diagnosis Guide and Reference. If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution.

Enter a valid day and, if the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.

For further information, look in the dump data set (ddname EQQDUMP), which contains a copy of the record and the position of the error.

EQQX727E

USER LEVEL IS LOWER THAN CONTROLLER LEVEL: CANNOT GET CP RECORDS.

This message is issued when you try to access an operation in the current plan, but you are not using the level of code required to access this kind of objects. The user code level is identified by the USRLEV value.

The request is rejected.

Ensure that you are using the appropriate level of code, which is identified by the value in USRLEV. Note that if you are changing the user level value, you must recompile your user-written program to see the changed layouts.

EQQX728E

THE OBJECT CANNOT BE IDENTIFIED BECAUSE THE KEY IS NOT UNIQUE.

The request cannot be run because the key that was specified to identify the object is not unique. For example, to issue a valid LIST CRITSUCS request the operation must be identified by specifying the complete key (application name, input arrival, and operation number).

The request is rejected.

Ensure that you are using the appropriate level of code, which is identified by the value set in INIT USRLEV. Consider that if you modify the USRLEV value, you need to recompile your user-written program to see the changed layouts.

EQQX729W

INSUFFICIENT VIRTUAL STORAGE FOR THE LIST.

The user address space cannot allocate enough storage to complete your request.

The request is rejected.

Log on again by increasing the region size, or specify filtering values to reduce the amount of data that is returned.

EQQX000 - EQQX729

EQQX000E

EQQX001E

EQQX002E

EQQX003E

EQQX004E

EQQX005E

EQQX006E

EQQX007E

EQQX008E

EQQX009I

EQQX010E

EQQX011E

EQQX012E

EQQX013E

EQQX014E

EQQX015E

EQQX016E

EQQX017E

EQQX018E

EQQX019E

EQQX020E

EQQX021E

EQQX022E

EQQX023E

EQQX024E

EQQX025E

EQQX026E

EQQX027E

EQQX028E

EQQX029E

EQQX030I

EQQX031E

EQQX032E

EQQX033E

EQQX034E

EQQX035E

EQQX036E

EQQX037E

EQQX038E

EQQX039E

EQQX040I

EQQX041E

EQQX042E

EQQX043E

EQQX044E

EQQX045W

EQQX047E

EQQX048E

EQQX049E

EQQX051E

EQQX052E

EQQX053E

EQQX054E

EQQX055E

EQQX056E

EQQX057E

EQQX058E

EQQX059E

EQQX060E

EQQX061E

EQQX062E

EQQX063E

EQQX064E

EQQX065E

EQQX067E

EQQX069E

EQQX070E

EQQX071E

EQQX072E

EQQX073E

EQQX074E

EQQX075E

EQQX076E

EQQX077E

EQQX078E

EQQX079E

EQQX081E

EQQX082E

EQQX083E