You chose not to confirm the original request. So it was ignored by HCL Workload Automation for Z.

The event-triggered tracking (ETT) function was already active when you requested activation of the function.

The event-triggered tracking (ETT) function was not active when you requested deactivation of the function.

The event-triggered tracking (ETT) activation request has been successfully processed.

The event-triggered tracking (ETT) deactivation request has been successfully processed.

You have attempted to use the event-triggered tracking (ETT) function, but you do not have the necessary authorization.

You have attempted to update the event-triggered tracking (ett) entry ETTENAME, but you do not have the necessary authorization.

Your modifications to the event-triggered tracking (ETT) table have successfully updated the ETT database.

Your modifications to the event-triggered tracking (ETT) table did not update the table data set due to some error in the HCL Workload Automation for Z subsystem.

Your changes to the event-triggered tracking (ETT) criteria contain a syntax error (or errors).

Another user is currently updating the event-triggered tracking (ETT) criteria table. Only one user can access the table at a time.

OCHCEXA, OCHCPFX and OCHCSFX are the national language characters for 'E' (exact), 'P' (prefix) and 'S' (suffix).

You have defined a triggering event as a resource event, but failed to indicate if event-triggered tracking (ETT) triggering should occur only for an availability status switch from N (no) to Y (yes) or if ETT triggering should occur whenever the availability is set to Y.

OCHCJOB and OCHCRES are the national language characters for 'J' (job) and 'R' (resource).

You have specified the event to be a job event, but failed to indicate whether the job name in the first operation of the added application should be replaced or not.

OCHCYES and OCHCNO are the national characters for 'Y' (yes) and 'N' (no).

You have specified the event to be a resource event. You cannot replace job name information for resource events. HCL Workload Automation for Z automatically sets this information to N (no) for resource events.

OCHCNO is the national character for 'N' (no).

You must specify the name of a valid application to be added to the current plan when an event-triggered tracking (ETT) event matching this criteria entry occurs.

You have entered a value for the dependency resolution attribute that is not recognized by the Event-Triggered Tracking dialog. You must change the value to one of the supported values defined by this message.

You have defined a triggering event as a reader event, but have specified a character other than OCHCNO or blank in the availablility switch field. The availability status switch is relevant only when the triggering event is a resource.

You have specified duplicate event names in the event-triggered tracking (ETT) table.

You have defined a triggering event as a resource event, but have specified a character other than OCHCYES or OCHCNO in the availablility switch field. The availability status switch must be set when the triggering event is a resource.

The same table name was encountered twice in a SEARCH directive of the product.

A SEARCH directive of the product contains either both GLOBAL and NOGLOBAL, or both APPL and NOAPPL.

The member specified in a FETCH directive of the product could not be found. The member name is incorrect or the member cannot be accessed.

The third and final string in a directive of the product contains more than 1024 characters after substitution, including continuation lines.

The value of a variable depends on the values of other variables, which in turn depend on its value. No value can be determined for this variable.

A closed loop of dependency definitions or variable translations exists.

If TABLE GLOBAL NOT FOUND message text appears: possible reasons are:

The user did not explicitly provide tables to be searched.

The user specified some tables to be searched but none of them are defined in the AD file.

The scheduler tried to search the variable in the global table, but the default global variable table is not defined in the AD file.

A non-dependent variable with no value was encountered in the submit phase or in a JCLPREPA simulation request.

The product was unable to submit the identified job because it contains an incorrectly coded //*%OPC statement and JCL variable scanning is active for this job.

A closed loop of dependency definitions exists.

A prompt variable cannot be dependent on a submit variable.

HCL Workload Automation for Z received an unexpected return code from an exit.

The user module caused an abend from which HCL Workload Automation for Z recovered.

The user module caused an abend from which HCL Workload Automation for Z could not recover.

The value that you supplied for the variable violates the verification rules in the variable definition.

HCL Workload Automation for Z has previously discovered an abend in this exit and marked it as not executable. This exit is not called again.

HCL Workload Automation for Z tried to allocate storage for a final build of the JCL record, but the request for storage failed.

Because you entered a comparison operator, you must enter a value length.

Because you entered a value length, you must enter a comparison operator.

The default value that you entered does not match the verification rules for the variable.

Because you asked for PICT verification, you must enter a validation pattern.

Because you asked for RANGE verification, you must enter Y (yes) or N (no) in the numeric field.

The current variable table has been deleted from HCL Workload Automation for Z database.

The value entered as a default value does not match the validation pattern defined for the variable.

You cannot use blanks in a LIST/RANGE verification value list.

You specified an odd number of values for a range verification.

You entered a range that consists of a larger number followed by a smaller number. You must specify the smaller number (beginning of the range) before the larger number (end of the range).

Substitution of a JCL command has caused the command length to exceed 71 characters or substitution of an in-stream data line has caused the in-stream data line to exceed 80 characters.

A variable substitution exit that was referred to could not be loaded by HCL Workload Automation for Z.

The expression must consist of keyword= where keyword is one of: NAME, ACTION, PHASE, MEMBER, COMP, EXIT.

This message can also be issued if all mandatory keywords have not been specified.

The name of a variable can contain one to eight alphanumeric characters, where the first character is alphabetic. This message can also be reported if a tabular variable, that is, a ?-variable, does not include the substitution column position and a default position is not defined in the JCL variable table.

A variable that is not predefined by HCL Workload Automation for Z must appear in a table that is created by the JCL variable dialog and is included in the current table concatenation.

For more information, refer to the description of the SEARCH and TABLE directives in Managing the Workload.

The tabular variable (?-variable) cannot be assigned the positions specified in the prefix or by default because part or all of the receiving string is already occupied.

For more information, refer to Managing the Workload.

During variable substitution of a job, a function that requires access to a calendar, for example, a SETVAR directive asking for an expression involving arithmetics on calendar days, could not be processed. The calendar referenced by the occurrence no longer exists.

At the end of the JCL stream, the last //*%OPC BEGIN command has not been closed by a //*%OPC END command.

A substitution exit set a return code of 8, which interrupted the JCL variable substitution. No further substitution is done for this operation.

The number of tables requested by a SEARCH directive is greater than 16.

Unless GLOBAL and APPL are explicitly excluded (NOGLOBAL and NOAPPL), they contribute to the total even if they are not specified in the SEARCH directive.

A TABLE directive has been encountered when 16 tables are already active.

The total length of all fields of a COMP expression, including COMP= and all continuations of the right side of the expression on subsequent JCL lines, cannot exceed 1024 characters after substitution.

The syntax of the COMP keyword is not correct.

Parentheses are not used correctly in the COMP keyword.

The COMP keyword does not contain any operators.

At least one comma is missing in the COMP keyword.

At least one operator is missing in the COMP keyword.

The current job contains a JCL processing directive specifying PHASE=SETUP. HCL Workload Automation for Z could not determine what action is requested by the statement because it refers to a JCL variable whose value is not determined until the submit phase.

The value entered as a default value does not match the validation pattern defined for the variable.

The same value of the independent variable is given in two different rows of the dependency table.

JCL tailoring is setting a temporary variable by a replacement with a source string. This string is blank, but a value is required.

The number of variables requested to be saved in a SAVEVAR directive is greater than 16.

A SETVAR directive requests creation of a temporary variable. There has been an earlier reference in the job to the same name and it has been found in the HCL Workload Automation for Z Variable Table.

HCL Workload Automation for Z was attempting to build a record in the VSAM data set to be inserted in the JCL repository data set, but it was unable to do so because of insufficient virtual storage.

HCL Workload Automation for Z was attempting to submit a job to JES for a ready operation on a computer workstation. However, no JCL for this operation is saved in the JCL repository data set and the job is not present as a member in the library defined by the EQQJBLIB DD statement.

The JCL library member exists in the library defined by the EQQJBLIB DD statement, but there are no records in the member.

During variable substitution of a job, a SAVEVAR directive specified the name of a variable, or a variable table, with incorrect syntax.

During variable substitution of a job, a SAVEVAR directive was found that specified only the variable name. The implied table is then the Variable Substitution global table. However, no GTABLE keyword has been specified in OPCOPTS.

The physical record length specified for the JS repository is too small.

A reference to a dynamic-format variable has been found and the format of the variable has not been set in a SETFORM directive.

During variable substitution of a job, a SETFORM directive was found where the name of the dynamic-format variable is not a HCL Workload Automation for Z-supplied dynamic format variable.

A COMP expression with operators GT, GE, LT, or LE only allows one value for expression2.

A COMP expression with operators GT, GE, LT, or LE does not allow the generic characters * or % in expression2.

During variable substitution of a job, the calculation of a SETVAR arithmetic expression resulted in a date value that exceeds HCL Workload Automation for Z limits. HCL Workload Automation for Z supports dates from 1 January 1984 to 31 December 2071. If the expression includes dynamic-format supplied variables containing the first or the last day in the month or in the year of the occurrence IA, the calculated date must fall within the range of four years earlier and seven years later than the current year.

The joblib I/O exit was called and gave a return code indicating that it could not open one of its input data sets.

HCL Workload Automation for Z was building a reord in the VSAM data set to be inserted in the JCL repository data set, but it was unable to do so because of insufficient virtual storage.

HCL Workload Automation for Z was attempting to submit a job to JES for a ready operation on a computer workstation. However, no JCL for this operation is saved in the JCL repository data set, and the joblib I/O exit could not find the job in any input data set.

The joblib I/O exit was called to retrieve a job to be submitted, but the exit did not return any data.

The joblib I/O exit was called to retrieve a job to be submitted, but the exit gave a return code indicating that an I/O error had occurred on an input data set.

During variable substitution of a job, a SETVAR directive was found where the name of the temporary variable is incorrect. The possible errors are: termwidth=

• The variable name does not start with a T.
• The rest of the variable name contains one or more characters that are not alphanumeric.

The joblib I/O exit was called to retrieve a job to be submitted, but the returned job exceeds the maximum supported size, which is 608 KB (kilobytes) of data.

A job that is about to be submitted to JES is too large to be saved in the JCL repository data set.

The job submit exit was called and returned the name of a TSO user on whose behalf the job submit should be done. An authority error occurred when trying to build a job submit environment for this user.

During variable substitution of a job, a SETVAR directive was found and created a temporary variable. The temporary variable was not referred to anywhere in the JCL.

During variable substitution of a job, a SAVEVAR directive was found requesting update of the default value of a variable. This variable was not referred to anywhere in the JCL.

This job exceeds 65 535 records, which is the limit that HCL Workload Automation for Z can process.

The job is using an ETT occurrence-related variable, but the job was not added through the Event-Triggering Tracking (ETT) mechanism.

See text.

See text.

You can enter only Y (for Yes) or N (for No) in this field.

The position that you have entered is out of the 80-column range for instream data or a JCL line.

Because you entered a comparison operator, you must enter a value length.

Because you entered a value length, you must enter a comparison operator.

The default value that was specified for the variable VAR does not comply with the verification rules for the variable.

Because you asked for PICT verification, you must enter a validation pattern.

Because you asked for RANGE or LIST verification, you must set the Numeric field to Yes.

The dependency that you modified has been inserted into the database.

The dependency that you created has been inserted into the database.

The dependency that you deleted has been removed from the database.

You have tried to delete a JCL variable table that you are not authorized to delete.

A JCL imbed exit that was referenced in a FETCH directive of the current JCL returned an invalid return code.

HCL Workload Automation for Z was trying to build a JCL record from the data supplied by the exit defined in a FETCH directive, but it could not do so because of insufficient virtual storage.

The exit gave a return code indicating that the JCL could not be found in the exit's input data sets.

The exit was called to return JCL to HCL Workload Automation for Z, but no data was returned.

The exit was called to return JCL to HCL Workload Automation for Z, but more than 256KB (kilobytes) of data was returned.

HCL Workload Automation for Z was unable to load the exit. HCL Workload Automation for Z does not try to call it again. The exit is flagged as not executable.

The exit abended while processing. HCL Workload Automation for Z does not try to call it again. The exit is flagged as not executable.

HCL Workload Automation for Z has previously discovered an abend in this exit and marked it as not executable. This exit is not called again.

HCL Workload Automation for Z tried to allocate storage for a record read from the JS data set, but the request for storage failed.

The JCL variable table has been removed from the HCL Workload Automation for Z database.

You cannot access the variable table because it is being updated by another user.

You have tried to create a table that already exists.

The JCL variable table has been modified and successfully updated in the database.

You have tried to access a JCL variable table that has been deleted since the variable table list was displayed.

A JCL variable definition has been created and inserted in the database.

The JCL variable table has been modified and successfully replaced in the database.

Another variable is dependent on this variable.

You specified an odd number of values for a range verification.

One of the pairs of values that you specified is in error.

The value that you entered contains a character that is not numeric.

You defined as valid a value that contains more than 44 characters. This is not allowed.

The dependent value that you entered does not comply with the verification rules for the dependent variable.

In this field, you can enter only Y (for Yes), N (for No), or P (for Prompt).

You specified verification type RANGE or LIST, but did not specify any values.

You specified a valid numeric field type, but did not specify RANGE or LIST verification.

Valid types are ALPHA, NUM, ENUM, HEX, BIT, PICT, NAME, DSNAME, RANGE and LIST.

The length must be in the range 1 to 44.

Valid operators are:

There are no dependencies defined for this variable.

You specified a duplicate value for the independent variable.

There are no verification criteria defined for this variable.

You have defined a variable that already exists in this table.

See text.

See text.

See text.

See text.

You tried to define more than 360 dependencies.

You tried to enter a value for an independent variable without specifying an independent variable name.

You have specified a verification length that is shorter than one of the values listed in the valid VALUES or RANGES.

The value in the value-of-dependent field is longer than the value length specified on the Specifying Verification Criteria panel.