The application ID NAME is specified to be in DBCS format, that is, it must start with a shift-out character (X'0E') and end with a shift-in character (X'0F'). Either the shift-out or the shift-in character, or both, are missing.

The application ID NAME is specified to be in DBCS format, that is, it must start with a shift-out character (X'0E') and end with a shift-in character (X'0F'). Either the shift-out or the shift-in character, or both, are missing.

The application ID NAME has an invalid syntax.

The application ID NAME has an invalid syntax. The first character in NAME must be an alphabetic character.

The character displayed in the message is not a valid alphabetic character.

When processing sequential operator instruction files, an invalid digit appears in NUMBER.

The value for year in the SYSIN statement of the batch program is incorrect. Year must be a number in the range 00 to 99.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The month is invalid in DATE.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The day is invalid in DATE.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The hour is invalid in TIME.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The minute is invalid in TIME.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The time specified is outside the valid range for time.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

You have attempted to access the application description data set, but it is being used by another user.

You have attempted to read the application description ADID, but this application description ID does not exist in the application description database.

During mass update of the application description database, the changes that were made have caused application description APPL to become invalid. REASON indicates the reason why validation of the application description failed. and POSITION indicates the failing position in hexadecimal form within the record.

The internal predecessor OPID could not be found for the application description APPL.

There is more than one network. This is not allowed.

There is a dependency loop in the network. This message is issued for all operations involved in the dependency loop and for all operations preceding the loop.

You have specified an operation at a workstation that uses the job setup function, but the operation OPID does not have an immediately succeeding processor operation with the same job name.

Errors were encountered from the sort program.

The long-term plan data set is being used by another HCL Workload Automation for Z function.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The end of the planning period must be later than the start of the period.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The planning period SDATESTIME- EDATEETIME is outside the current range of the long-term plan.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The parameter field is shorter than the required length.

The last backup of the active current plan to the backup current plan failed. The current plan input to daily planning could therefore be incomplete or out-of-date.

An external predecessor to the operation OPERATION for the application description APPL does not exist in the application description database.

An operation (OPERATION) is defined for a workstation (WS) that does not exist.

An occurrence in the long-term plan data set or an undecided occurrence in the old current plan data set, which has a deadline previous to the latest backup time, is assumed to be completed.

The BATCHOPT statement specifies that the daily plan is to be produced for an active subsystem defined by the keyword CHECKSUBSYS. However the subsystem cannot be reached by the daily planning program.

When no current plan exists, you must specify the period start date and time.

A daily plan period must not extend beyond 21 days. Either the SYSIN parameters were specified outside the HCL Workload Automation for Z panel or an extension length was specified in work days, and calculated elapsed time exceeds 21 days.

Daily planning requires an old current plan data set as input, but that data set does not exist.

The old current plan data set used as input when extending or replanning the current plan period is not the correct data set. The data set may have been restored from a backup copy.

The workstation WSN, which has work planned for it in the current plan, has been deleted from the workstation description database.

The workstation WSN type in the workstation description database has been changed for a workstation that is part of the current plan.

An application occurrence has been read in the long-term plan data set, but there is no valid application description.

The period start date and time cannot be changed when extending the current plan period.

The long-term plan data set used as input when extending or replanning the current plan period is not the correct data set. The data set may have been restored from a backup copy.

The status record (in the checkpoint data set) does not contain the value that the daily planning program expects when the backup completion signal is received. The data set may have been restored from a backup copy.

A start date and time was entered when running a trial extend of the current plan. The start date and time is ignored and replaced by the current plan end date and time.

All workstations are closed during the period START– END.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

This message is issued by one of the DP batch programs (print, trial, extend, or replan) when a previous DP batch program (that is, an extend or replan) has created a new current plan (message EQQ3105I A NEW NCP WAS CREATED was logged), but the controller has not completed processing the plan.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.

No external dependency has been found between operations in the occurrences OCCURRENCE and OCCURRENCE as defined in the application description database and in the default rules. This message is followed by message EQQ0333W or EQQ0334W.

No default successor operation, as defined in the installation options, has been found for the application APPL.

No default predecessor operation, as defined in the installation options, has been found for the application APPL.

The rules for automatic workstations were not satisfied for the application APPL. This message is always issued together with one of the messages EQQ0337W through EQQ0341W.

An operation uses the wrong workstation name when defining an operation that belongs to another application as its predecessor.

An operation at an automatic printer workstation and an operation at an automatic computer workstation do not have the same job name.

An automatic printer workstation operation has a predecessor on a workstation that is not an automatic computer workstation. This is not allowed.

An automatic printer workstation operation must not have an external predecessor operation.

An automatic printer workstation operation has no predecessors.

An automatic printer workstation operation has more than one internal predecessor. This is not allowed.

An operation on a workstation using the HCL Workload Automation for Z job setup facility must have a job name to combine it with a computer operation in the same application.

An operation on a workstation using the HCL Workload Automation for Z job setup facility must have a job name to combine it with a computer operation in the same application. A preparation (job setup) operation is found, but no corresponding computer operation immediately succeeding it is found.

An operation on a workstation using the HCL Workload Automation for Z job setup facility must have a job name to combine it with a computer operation in the same application. The computer operation must be an immediate successor to the preparation (job setup) operation.

A dependency could not be resolved because the predecessor occurrence is not in the current plan.

When producing a trial daily plan extension, the period start time must be equal to the current plan end.

When producing a trial daily plan extension, all predecessor applications with the input arrival time earlier than the period start time are assumed to be completed. This message is followed by EQQ0349I.

The application is assumed to be completed. See also message EQQ0348I.

Reporting can only be requested for time periods less recent than the last old current plan. The old current plan is a backup copy of the current plan and is updated either after every certain number of events (specified at installation time) or during daily planning.

Reporting can only be requested for time periods less recent than the last old current plan. The old current plan is a backup copy of the current plan and is updated either after every certain number of events (specified at installation time) or during daily planning.

The application had an invalid completion date and could not be added to the summary table of completed applications (maximum 28 days). The reason may be an incorrect day given at IPL of the system.

The current plan record is larger than 32 KB (kilobytes).

A predecessor could not be found as expected. It is probably caused by an error in the long-term plan (LTP) or the current plan (OCP), or both.

A workstation was deleted from the database EQQWSDS and then redefined with the same name but with a different value for the VIRTUAL flag. The workstation results as incorrectly defined.

The destination has been removed from the database EQQWSDS but the current plan still contained some started operations for this destination when the DP batch was run. At the next DP extend or re-plan, if no started operation is still present for this destination, it will be deleted from the current plan.

An internal error on the open interval merge occurred. Open intervals have not been correctly calculated for a virtual workstation.

A conditional dependency could not be resolved because the predecessor occurrence is not in the current plan.

The daily planning program was unable to add any more successor operation entries to a potential predecessor record. Since the record could not be updated as intended, it does not define all potential successors for application APPL. If new occurrences of this application are added by program interface (PIF) programs or by the event-triggered tracking (ETT) function it is not possible to add all possible successor dependencies automatically.

DP batch informs that the new plan contains the workstation WSNAME updated accordingly with the changes that were applied to the definition of the fault-tolerant or z-centric agent, in the workstation database.

As a consequence of the change described by message EQQ0372I, the indicated operation, which had status S, has been interrupted by DP batch and its status set to I.

The plan indicates that the operation specified in the message cannot meet its deadline. Possible reasons for this could be: insufficient workstation resources, priority too low, and late predecessors.

The plan indicates that the operation specified in the message cannot meet its deadline. Possible reasons for this could be: insufficient workstation resources, priority too low, and late predecessors.

The operation specified in this message cannot be planned to start until after the end of period. Possible reasons for this could be: insufficient workstation resources or special resources, priority too low, and late predecessors.

The operation specified in this message cannot be planned to start until after the end of period. Possible reasons for this could be: insufficient workstation resources, priority too low, and late predecessors.

The controller is still handling a turnover process or waiting for end-to-end synchronization. In this condition a new batch cannot be started.

An operation defined on a remote engine workstation has not remote job information specified.

An operation is defined on a remote engine workstation, but the remote job information is incomplete.

The operation occurrence has an internal or external predecessor (or successor) that does not have as its successor (or predecessor) this operation occurrence. This message is issued together with message EQQ0394I, which provides information about the predecessor (or successor).

The operation occurrence has an internal or external successor (or predecessor), but does not see this dependency. This message is issued together with message EQQ0393I, which provides information about the successor (or predecessor).

The operation occurrence has system automation information defined in the application. The information is ignored, because the workstation is not Automation.

The operation occurrence has remote job information defined in the application.

The remote job information is ignored, because the workstation type is not remote engine.

The remote engine type of the workstation WSN, already present in the plan, was changed.

An error occurred while writing to an intermediate work file or the track log file used by daily planning. The SYNAD routine extracted the following information: job name, stepname, unit address, device type, ddname, operation, error description, phys-DA, and access method.

This message is a continuation of message EQQ0398E.

The long-term plan batch programs encountered invalid dates when trying to generate occurrence run dates for a rule-based run cycle. Most likely, this is an internal processing error.

If the run cycle is based on a regular rule, dates after the failure point are missing. If it is based on an exclusion rule, dates after the failure point are not excluded by this run cycle. Dates generated for the other run cycles of the application are valid and appear in the plan.

A date specified to HCL Workload Automation for Z is prior to the current date.

The time span, from current date to end date, may not exceed four years.

This message is issued from a batch job. The submit request is terminated.

This message is issued from a batch job. The submit request is terminated.

This message is issued from a batch job. The submit request is terminated.

This message is issued from a batch job. The submit request is terminated. There is no calendar stored in the database.

The operations or dependencies of the occurrence have been changed using the Long-Term Planning panel.

The long-term plan data set contains references to workstations that no longer exist in the workstation description database. Most likely, the workstation descriptions were deleted after the last update of the long-term plan data set.

While modifying the long-term plan, a successor to an occurrence could not be found. This is probably due to some abnormal situation that occurred either in an earlier long-term plan run or during an update using the Long-Term Planning panel. This resulted in some inconsistency in the long-term plan data set.

While modifying the long-term plan, a predecessor to an occurrence could not be found. This is probably due to some abnormal situation which occurred either in an earlier long-term plan run or during an update using the Long-Term Planning panel. This resulted in some inconsistency in the long-term plan data set.

There are no occurrences in the long-term plan for the print period specified when requesting a print out of the long-term plan.

No occurrences for a specific application description ID are printed because no occurrences were found.

Either one or both long-term plan (LTP) report limits, specified when requesting a printout of the long-term plan, are outside the LTP range.

There is no occurrence that can be defined as a predecessor to the occurrence listed.

The negative run cycle defined by NPERNSGNNOFS, or the exception rule defined by NPER, cancels the occurrence ADIDDATETIME defined by the normal run cycle PNAMSIGNOFFS, or the regular rule defined by PNAM.

The indicated occurrence does not exist in the new long-term plan.

During a modify all run of the long-term plan, the application description for the indicated occurrence/run date/run time could no longer be found.

The LTP batch program found a repeated dependency between the two occurrences identified by the yymmdd pred_application_name hhmm and yymmdd succ_application_name hhmm LTP keys: this will start a loop at DP batch run time, making it fail. The double dependency was added with the Look Forward mechanism and is removed from the LTP to avoid the loop. This situation can occur when you create the LTP for the first time and have an application with a dependency on itself that runs several times during the day and has resolution criteria set to the same day.

The LTP batch program found a repeated dependency between the two occurrences identified by the yymmdd pred_application_name hhmm and yymmdd succ_application_name hhmm LTP keys: this will start a loop at DP batch run time, making it fail. The double dependency was added with the Look Forward mechanism and is removed from the LTP to avoid the loop. This situation can occur when you create the LTP for the first time and have an application with a dependency on itself that runs several times during the day and has resolution criteria set to the same day.

An end date specified for a create or extend run of the long-term plan, should be later than or the same as the current date.

The report type specified for a long-term plan print request is invalid. Valid report types are F for full report, and D for dependencies only.

The start date and time for the report interval in a long-term plan print request must be earlier than the end date and time.

Extension of the long-term plan is determined by specific start and end dates in the long-term plan header record. Dates outside the range specified by these dates for updating, printout, or display, are not allowed.

The sort order specified is not valid. Valid sort orders are I, O, and A.

The application (ADID) specified in the long-term plan occurrence is no longer found in the application description database. Most likely, the specified application description has been deleted from the application description database while the corresponding occurrences in the long-term plan data set have not been deleted.

This message is issued from a long-term plan (LTP) batch program. The calendar specified in the application description could not be found in the database. The default calendar is used.

This message is issued from a long-term plan (LTP) batch program. The calendar specified in the application description could not be found in the database or the calendar specified in the CALENDAR parameter of BATCHOPT could not be found. The DEFAULT calendar is used. If there is no DEFAULT calendar, all days are treated as work days.

This message is issued from a long-term plan (LTP) batch program. The calendar specified in the application description could not be found in the database and the CALENDAR keyword is not defined on BATCHOPT. The DEFAULT calendar is used. If there is no DEFAULT calendar, all days are treated as work days.

An occurrence has been generated and moved to the date shown. The move resulted in a date outside the validity limits specified in the application description or resulted in a date after the end date of the long-term plan. If the reason was that the occurrence was moved after the end date of the long-term plan, then the occurrence is included in the next extend of the long-term plan.

A group definition is specified for this application, but the group definition cannot be found in the application description database.

The group definition specified for this application has no run cycle information.

The long-term plan batch job has detected that for the application APPL, the run cycle RUNC specifies a REPEAT END TIME that is not consistent with the application calendar work day end time. The REPEAT END TIME must be a value between the input arrival time of the run cycle and the calendar work day end time of the application.

The long-term plan (LTP) batch program has found that the input LTP file does not contain a valid long-term plan, but the LTP backup file is valid. The most likely cause of this message is that the previous execution of the LTP batch program failed before the new LTP file was successfully built.

The long-term plan (LTP) batch program determined that the current occurrence referenced more occurrences than the maximum possible defined by the maximum size of a record in the LD work file.

An occurrence has been generated and moved to the date shown. The move resulted in a date outside the generating span. Span start is defined as the highest date of the application description (AD) valid-from date, run cycle in-effect date and long-term plan (LTP) start date. Span end is defined as the lowest date of AD valid-to date, run cycle out-of-effect date minus 1, and LTP end date.

The long-term plan (LTP) batch program or the daily planning batch program was unable to copy the LTP file to the LTP backup file.

Sort was invoked to sort on a long-term plan data set, but the program issued a return code of 16.

This message indicates the maximum number of predecessors and successors that can be created per occurrence using the maximum record sizes specified for the VSAM files defined by the EQQLDDS and EQQLTDS DD statements.

When you create or extend the long-term plan, the end date must be a work day.

The period or run cycle group specified in the application description database does not exist in the calendar database.

For a given application/run cycle number, the offset is greater than the period length for the specified period.

The occurrence ADIDDATE has an offset that is greater than the length of closed interval of the noncyclic period PNAM. (A closed interval has both origin and interval end dates defined.)

The occurrence ADIDDATE has been moved by free-day rule RULE. The moved date is outside the closed interval of a noncyclic period. (A closed interval has both origin and interval end dates defined.)

The deadline is set before the input arrival time, therefore is moved to 24:00.

The indicated occurrence cannot be created because the old long-term plan contains the same occurrence, but is marked as deleted.

To be sure of the correct use of the calendar database, for a noncyclic period, you must have at least one origin date beyond the specified end date of the long-term plan. This ensures that no work remains unplanned for the period in question.

The run date calculated using the run cycle information identified in the message for the occurrence ADID DATETIME is a free day, and the specified free-day rule is 1 (run on the closest work day before the free day). However, HCL Workload Automation for Z could not move the occurrence prior to the free day because the closest work day is before the current plan end date.

The occurrence indicated cannot be moved, modified, or deleted because it has at least one successor in the current plan. It occurs in the current plan as a pending predecessor. This message is followed by message EQQ0537I, which identifies the successor occurrence.

This message identifies the successor to a pending occurrence in the current plan. This message is issued together with message EQQ0536W.

Due to the application of the SHIFT option, the execution of the occurrence takes place on a date that is beyond the extent of the LTP.

In the Application Description, a variable duration or variable deadline is associated with a run cycle group, but the LTP cannot find the run cycle group.

You are requesting a printout of the long-term plan data set for a period of longer than four years, but the long-term plan can have a span of up to four years only.

A long-term plan batch function is trying to reference a long-term plan data set that has no header. The long-term plan is either empty or in error.

The actual occurrence has been deleted from the long-term plan, probably by a non-HCL Workload Automation for Z function.

A long-term plan must not be longer than four years.

Occurrences in the long-term plan have been selected by daily planning and might have been included in the current plan. It is not possible to create the long-term plan without first refreshing it using the Service Function panel.

The start date must be earlier than the end date.

The actual occurrence has been deleted from the long-term plan, probably by a non-HCL Workload Automation for Z function.

The actual occurrence has been deleted from the long-term plan, probably by a non-HCL Workload Automation for Z function.

The record format for the user input data set in the application print program should be either fixed or variable. Undefined is not supported.

When the record format was fixed, the user data set in the application print program had a record length of less than 16.

The specified application ID contains more than 16 characters.

When printing an operations using particular work stations report during an application description PRINT, the specified workstation name does not appear in any application description.

The indicated application ID was read from the user data set and was found to be less than 16 characters. It is padded with blanks up to the sixteenth character. This message is issued only if the input data set has a variable record length.

When printing an owner ID report type or displaying the long-term plan for one owner, the specified owner ID does not appear in any application description.

No application description records were found that met the required specifications.

The application print program found a record that was not sorted in the proper sequence.

Sort was invoked on a work data set for an application description printout, but the program issued a return code of 16.

A detailed application description printout is requested for a specific application, valid on a specific date, but no such description exists in the application description database.

It is not possible to select input type 3 when report type 3 or 4 has been chosen.

The number of items is greater than 12 or does not equal the number of items in the list.

A record in the user input data set was found that was blank or the application ID did not start in position one.

The internal representation of rule RULE in application ADID is invalid and the corresponding rule command cannot be derived from it.

You have specified that a certain field should be changed by the mass update function, but no field in the application description database matched the specifications.

An occurrence has been found that has too many predecessors to be saved in the long-term plan (LTP) dependency work file defined by the EQQLDDS DD statement.

When building a network for operations within a single application, a loop or an inconsistency was found. This message indicates that an error in the application description was introduced after the application description was created.

An occurrence has been found that has too many successors to be saved in the long-term plan (LTP) dependency work file defined by the EQQLDDS DD statement.

Parameters in the SYSIN statement are specified incorrectly. The error can arise, for example, when the alignment of parameters is wrong or when there is an extra parameter.

When creating a long-term plan (LTP), HCL Workload Automation for Z builds a calendar that begins four years before the start of the LTP period and ends four years after the end of the LTP period. HCL Workload Automation for Z cannot handle dates later than 31 December 2071. The specified LTP time period would result in an LTP calendar extending beyond 2071.

No parameters were specified in the SYSIN statement for a batch job.

No dates are generated for this run cycle group in the LTP because of rule errors. This message is preceded by another message that explains the error in the rule.

The data set with the ddname DDNAME could not be opened.

The DD statement for the file with ddname DDNAME is missing.

You must specify either a new end date or an extension length, not both.

The extension length must be not longer than 4 years, that is, 1461 days.

You must specify either an extension length or a start date and an end date.

To simulate the long-term plan (LTP) create function you must specify both a start date and an end date.

This message is issued by the daily planning (DP) batch programs to the DP report data set when the default segment of a special resource differs from what is defined in the special resource database.

The indicated application name or operation number, or both, for which you want to create an operator instruction, cannot be found in the application description database.

A program interface (PIF) initialization request to subsystem SUBSYS was a failure. When the job does not allocate the EQQOIDS file, HCL Workload Automation for Z uses the PIF to retrieve or update operator instructions.

A program interface (PIF) request to subsystem SUBSYS was a failure. When the job does not allocate the EQQOIDS file, HCL Workload Automation for Z uses the PIF to retrieve or update operator instructions.

When doing a mass update of operator instructions, the record format must be fixed for the sequential input data set.

When doing a mass update of operator instructions, the record length must be 80 for the sequential input data set.

The first record encountered while creating operator instructions from a sequential input file is not a header record.

A header record is encountered, but no key field is specified.

You specified a key field for the key NAMENO, but the length of the value that you gave to it is too large.

You specified a valid-from field (for operator instruction NAME) that is less than 10 characters long.

An operator instruction must contain a valid application name and operation number corresponding to an existing application.

The operator instruction (NAME) that you attempted to add already exists in the operator instructions database.

The valid-from date that you specified in the operator instruction NAME is later than the valid-to date and time. The valid-from date must be earlier than the valid-to date.

Either the date or the time was omitted. Both are required.

The operator instruction has no instruction text.

Temporary operator instructions for application NAME have periods that overlap. Temporary operator instructions with overlapping periods are not allowed.

The specified operator instruction is not within the valid-from and valid-to time period for the application description.

The EQQUOTOP program failed to open the data set referenced by the EQQOSLCO DD statement. The statement was incorrectly specified, or it is missing.

The EQQUOTOP program failed to open the data set referenced by the EQQOSLCI DD statement. The statement was incorrectly specified, or it is missing.

The EQQUOTOP program failed to read the contents of the data set referenced by the EQQOSLCO DD statement. The logical record length is not equal to 80 bytes.

The EQQUOTOP program failed to read the contents of the data set referenced by the EQQOSLCI DD statement. The logical record length is not equal to 80 bytes.

The scheduler could not locate the load module shown in the message text for the OSLC integration function.

The EQQOSLCI DD statement in the EQQOSLCP job references an empty data set.

The data set referenced by the EQQOSLCI DD statement could not be read, an I/O error occurred.

An I/O error occurred in the routine performing the encryption of the password contained in the PASSWORD keyword.

The EQQUOTOP program found a syntax error in the OSLCOPTS statement.

HCL Workload Automation for Z was not able to display message MSG. The message is not in the HCL Workload Automation for Z message log data set.

The indicated message is longer than 120 characters.

An operation record was detected with a zero operation number.

A batch program attempted to perform the function FUNC against the VSAM file FILE, but the attempt failed. The I/O request is from module MODULE.

A batch program attempted to perform the function FUNC against the file FILE, but the file had not been opened. The I/O request is from module MODULE.

A batch program attempted to perform the function FUNC against the file FILE, but the attempt failed. The I/O request is from module MODULE. The program forces the failure because of a mismatch among the allowed record length and the one specified in the JCL submitting the batch. This might happen if you used the old LTP batch skeleton after migrating to version 8.5.1.

A batch program attempted to read a record in the data set FILE, but the record no longer exists in the data set.

A batch program attempted to perform the function FUNC against the file FILE, but the attempt failed. The I/O request is from module MODULE.

A batch program attempted to perform the function FUNC against the file FILE, but the attempt failed. The I/O request is from module MODULE.

No more occurrences of this application can be added. The current plan can contain approximately 970 occurrences of each application.

When the HCL Workload Automation for Z panel is used to add occurrences, a lower limit (approximately 870) is used.

No more occurrences can be added to the current plan because the maximum number of occurrences has been reached.

The EQQUPTOP program failed to open the data set referenced by the EQQUSRIN DD statement. The statement was incorrectly specified, or it is missing.

The EQQUPTOP program failed to open the data set referenced by the SYSIN DD statement. The statement was incorrectly specified, or it is missing.

The EQQUPTOP program failed to read the contents of the data set referenced by the EQQUSRIN DD statement. The logical record length is not equal to 80 bytes.

The EQQUPTOP program failed to read the contents of the data set referenced by the SYSIN DD statement. The logical record length is not equal to 80 bytes.

The EQQE2EPW password encryption job does not specify any SYSIN DD statement or specifies a DUMMY DD statement.

A severe error occurred during the execution of the EQQUPTOP program.

The scheduler could not locate the load module shown in the message text for the end-to-end function.

The SYSIN DD statement in the EQQE2EPW job references an empty data set.

The data set referenced by the SYSIN DD statement could not be read, an I/O error occurred.

The error occurred while processing the SYSIN data referenced by the EQQE2EPW JCL. The EQQUPTOP program expects to find a sequence of triplets, each one containing the USRCPU, USRNAM, and USRPSW keywords, combined without repetition. Each of the triplets must correspond to a consistent set of keywords for a USRREC statement. All the three keywords must be present in the SYSIN, and only one keyword per row is allowed. The message variable shows the keyword that is missing.

An internal error occurred in the routine performing the encryption of the password contained in the USRPSW keyword CARD.

An I/O error occurred in the routine performing the encryption of the password contained in the USRPSW keyword.

A duplicate USRREC statement was found in the SYSIN data set, in the specified member of the EQQUSRIN data set, or while copying the SYSIN data to the EQQUSRIN data set member. The last statement was kept while the oldest one was removed. CPU and NAM correspond to the statement key.

When processing the USRPSW keyword of the USRREC statement, the EQQE2EPW JCL detected that no password was supplied. USRPSW(‘’) was specified.

The daily planning print program could not open any output data set.

The exit for daily planning print is activated.

The exit for daily planning print is not activated.

Parameters in the SYSIN statement must be a character string. Valid values are 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, and 14.

Lines longer than 120 characters have been truncated in the report.

No parameters were specified in the SYSIN statement for a batch job.

The daily planning program has detected an error in the input data. The validation error action specified in the BATCHOPT statement is to end the daily planning program.

The daily planning program was unable to find a predecessor to the occurrence defined by this message.

The daily planning program was unable to find a successor to the occurrence defined by this message.

The daily planning program was unable to find an occurrence record for an occurrence referenced in a rerun record (record type 09).

The daily planning program was unable to find an occurrence record for an occurrence referenced in a ready list record (record type 11).

The daily planning program was unable to find an operation record for an operation defined as an internal predecessor to an operation in the occurrence defined by this message.

The daily planning program was unable to create an operation record because it would be too large for the output data set defined by the EQQNCPDS DD statement.

The daily planning program was unable to find an index entry in the current plan record type 05 for the occurrence with the specified operation.

The daily planning program found an error when processing special resources.

The daily planning program found an invalid external dependency in an operation.

The daily planning program was unable to find an operation record for an operation defined as an internal conditional predecessor to an operation in the occurrence defined by this message.

The daily planning program was unable to find a conditional successor to the occurrence defined by this message.

While processing internal control blocks, the daily planning program was unable to find the indicated condition dependency.

While processing internal control blocks, the daily planning program was unable to find the indicated condition dependency.

While trying to add a default dependency, the daily planning program detected an inconsistent conditional dependency already present for the current operation.

A daily plan extend request failed because the record containing the all information on condition CONDID for application APPLID and operation number OPERNR is out of size.

A daily plan extend request failed, because the user field record for application APPLID and operation number OPERNR exceeds the maximum size.

User has defined two domains with the same workstation as domain manager..

In topology information member missing some DOMAINPARENT into DOMREC definition.

No domain definition has been specified in the topology member (for example, tplginfo) of EQQPARM, but some workstation definition (CPUREC) is present.

No first level domains have been defined. This implies the presence of a loop in the network.

User has defined at least a first level domain with a manager workstation that is not in the symphony.

Domain DOM1 specifies a parent domain that does not exist.

User has defined workstation CPU1 as belonging to MASTERDM, but this is not allowed.

User has defined a domain with the scheduler as domain manager workstation. This is not allowed.

A domain definition has specified as manager a workstation that has not the CPUTYPE keyword set to FTA.

Domain manager must be in fullstatus mode.

The domain has not been specified in the CPUREC definition.

This message states that CPU1 is set as domain manager for domain DOM1.

The domain definition specifies a manager that is not in the symphony.

The extended or standard agent CPUREC definition does not specify a host name.

A circular reference between domains has been detected.

The extended or standard agent CPUREC definition does not specify a host name.

A host for the agent is specified but the agent and the host workstations belong to different domains.

The CPUREC definition of the referred extended or standard agent CPU1 has incorrect info in the CPUHOST parameter: either a host name is specified for which no workstation does exist in the workstation database, or for this host name no CPUREC exists.

Standard agent CPU2 specifies a host that is not a domain manager.

The domain specified in the CPUREC definition does not exist or is not defined.

The CPU1 was selected to be the domain manager of the DOM1 domain, but its domain specification differs from DOM1.

CPUREC statement was specified without a CPUNAME keyword.

CPUNAME keyword specifies a CPU name that already exists, but it must be unique.

CPUREC statement does not have CPUOS keyword.

The CPUREC statement does not have a CPUNODE keyword.

A CPUREC statement for a standard agent does not have CPUHOST keyword.

A CPUREC statement for a standard agent does not support access method, fullstatus, and resolve dependencies.

The CPUREC statement for an Extended Agent must have access method and host CPU specified.

The CPUREC statement for an Extended agent does not support autolink, fullstatus, resolve dependencies, and server attributes.

The CPUREC statement for a fault-tolerant agent does not support host and access method attributes.

The CPUREC statement for a domain manager does not support the server attribute.

The CPUREC statement for an Extended Agent must specify the host CPU. The CPU parsing process will end.

The DOMAIN keyword is missing from the DOMREC statement.

The DOMAIN keyword specifies a domain name that already exists, but it must be unique.

The definition of domain DOM1 does not have a domain manager specified, but this is required.

In the topology information member it was found a CPUREC definition for a CPU CPU1 that does not exist in the Host Workstation database.

The required keyword is missing or incorrectly specified in the related statement.

A previous batch job has created the Symphony successfully but NMM has not yet processed it.

The previous Symphony progress status is not compatible with the next, probably because an error has occurred in the meantime.

Current Plan has a fault-tolerant workstation whose definition is missing in the topology information member.

The TPLGYPRM keyword of the TOPOLOGY statement in the topology parameters member (for example, TPGYPARM) is missing or incorrectly specified.

TEXT can be either blank or WORKSTATION WSNAME REQUIRES IT.

The job definition JOBNM in EQQSCLIB must specify one, and only one of either the JOBSCR or JOBCMD keywords. Either these keywords are both missing or both present.

If you are running EQQSLCHK sample JCL, workstation field is filled with N/A (Not applicable), because the CPU name is not available for the sample.

A job definition JOBNM specifies a WNT workstation, but the user USRNM for that workstation is bad defined in users information member (for example, USRINFO).

The job definition does not specify a user name. The default user specified for CPUNM will be used to execute the job.

If you are running EQQSLCHK sample JCL, workstation field is filled with N/A (Not applicable), because the CPU name is not available for the sample.

The TOPOLOGY statement of the topology parameters member (for example, TPLGPARM) does not specify any topology information member name.

BINDIR keyword is required.

WRKDIR keyword is required.

The USRMEM keyword is missing. This means that you are not using WNT fault-tolerant workstations.

The USRREC statement requires the USRNAM keyword.

In a USRREC statement, the USRCPU keyword is not specified or the CPU name specified in the keyword is not an existing CPU.

An incorrect memory area is passed by the PLX code to the C code.

The task is unable to get the UNIX System Services user IDfor the user that has executed the planning batch job.

The task is unable to allocate memory for the header record of Symphony file.

The task is unable to build the symphony file.

The task is unable to set the access mode to the SUF1 Symphony file.

The task is unable to open the SUF1 Symphony file.

The task is unable to put information for the CPU CPU1 in the SUF1 Symphony file.

The task is unable to read information for the SCH1 Job Stream from the SUF1 Symphony file as expected.

The task is unable to put information for the SCH1 Job Stream in the SUF1 Symphony file.

The task is unable to allocate memory for the Job Stream record of Symphony file.

The task is unable to allocate memory for the Job record of the Symphony file.

The task is unable to put information for the JOB1 job in the SUF1 Symphony file.

The task is unable to read information for the JOB1 Job from the SUF1 Symphony file as expected.

The task is unable to update information for the JOB1 job in the SUF1 Symphony file.

The task is unable to update information for the SCH1 job Stream in the SUF1 Symphony file.

The task is unable to found information for the SCH1 job Stream in the SUF1 Symphony file.

The task is unable to find information for the JOB1 job in the SUF1 Symphony file.

The task is unable to put information for the USR1 NT user in the SUF1 Symphony file.

The task is unable to update the last information in the SUF1 Symphony file.

The task is unable to rename the SUF1 Symphony file as SNF1.

An incorrect function has been called by the PLX code to the C code.

The task is unable to open the PDS specified by EQQSCLIB DDNAME.

The task is unable to use the PDS specified by EQQSCLIB DDNAME because of an incorrect record length.

The task finds a wrong job definition in EQQSCLIB for the indicated JB1NAM job.

The task is unable to find the specified occurrence in the Current Plan.

The task is unable to find any occurrences in the Current Plan.

A previous error prevents the task from producing the Symphony.

An error has occurred closing the data set associated with the EQQSCLIB DDNAME.

The task is unable to find the specified job in the Current Plan.

The keyword LOGLINES has been not specified in the TOPOLOGY statement.

The LOGLINES keyword in the TOPOLOGY statement has an incorrect value specified.

The TRCDAYS keyword has been not specified in the TOPOLOGY statement.

The TRCDAYS keyword in the TOPOLOGY statement has an incorrect value specified.

The batch job has successfully created the Symphony file.

The batch job was unable to produce the Symphony file.

The PORTNUMBER keyword in the TOPOLOGY statement has an incorrect value specified.

The PORTNUMBER keyword has not been specified in the TOPOLOGY statement.

The NMM task was not able to synchronize with the TWS distributed environment. There might be a communication problem between the controller and the server.

The CPUTYPE parameter was not specified in the topology definitions for the CPU identified in the message text. The CPUTYPE is set to the value displayed in the message text.

The script definition of FTW job JOBNM contains more than one JOBREC statement. Only one JOBREC statement for member is allowed.

The keyword CPULIMIT was not used in the CPUREC statement for the fault-tolerant workstation CPU1.

An invalid value has been specified in the CPULIMIT keyword in the CPUREC statement for fault-tolerant workstation CPU1

No workstations have been added to the symphony file but some domain definitions (DOMREC) are present in the topology member (ex.: tplginfo) of EQQPARM.

The batch job detectedthat the controller is not active and the Topology member is specified in the batch options.

This error provides more detail on what caused the previous error and is issued when a system call failed for some reason.

The keyword CODEPAGE has not been specified in the Topology statement.

During the processing of the daily plan NUMJOB jobs were added to the file.

The keyword CPUTZ was not used in the CPUREC statement for the fault-tolerant workstation CPU1.

The keyword HOSTNAME was not used in the Topology statement.

A new current plan (NCP) was created during the creation, extension, or replanning of the daily plan.

Duing DP extent, DP replan or symphony Renew, the batch is waiting for SCP to start the Symphony file creation.

During DP extend, DP replan or symphony Renew, the batch has been notified that the SCP VSAM data set is available so the addition of the jobs to the symphony file can start.

During DP extend, DP replan or Symphony Renew, the batch has added all the jobs to the symphony file. The Symphony creation process can continue adding other definitions, for example the job dependencies or the user's definitions.

There is no member named MEMBER in the EQQSCLIB library. This may not necessarily be an error: if the operation is defined as centralized, the EQQSCLIB member containing the job definition is optional.

The member named MEMBER in EQQSCLIB does not contain any statements.

An I/O error has prevented the task from parsing member MEMBER of EQQSCLIB.

Member MEMBER in EQQSCLIB does not contain the required STMT statement.

An incorrect value for keyword KEYWORD in statement STMT was found while parsing a job definition.

A syntax error for keyword KEYWORD in statement STMT was found while parsing a job definition. The left parenthesis that is before the keyword is not matched with a right parenthesis.

An incorrect value for keyword KEYWORD in statement STMT was found while parsing a job definition. The value specified is too long, it cannot exceed LEN characters.

An error was found while parsing a job definition. Keyword KEYWORD in statement STMT was specified twice. A keyword can only be used once in a statement.

An error was found while parsing a job definition. Statement STMT was specified twice. A statement can only be used once in a job definition.

The CPUREC statement that defines the configuration of workstation CPU1 does not contain the CPUUSER keyword.

The value specified for keyword KEYWD in statement STMT is not correct.

Keyword KEYWD has not been specified in statement STMT.

The value specified for keyword KEYWD in the CPUREC statement for workstation CPU1 is not correct.

There was an internal error during the execution of the FNM1 routine called to build the symphony file. The next EQQ3099E message will display the reason of this error.

The recovery statement in member JOBNM in EQQSCLIB will be ignored because job JOBNM is centralized.

The JOBCMD and JOBSCR keywords in statement JOBREC of member JOBNM in EQQSCLIB will be ignored because job JOBNM is centralized.

The value of TIMEZONE parameter is incorrect.

While running the call PUTENV in module FNM1, an error occurred when a new environment variable ENVVAR was being added or the value of an existing environment variable was being changed. The environment variable contains the string used in the PUTENV call.

The batch job is waiting for the backup of the current plan to complete.

The daily planning job is creating a new current plan (NCP). The normal mode manager (NMM) controller subtask is waiting for the process to complete.

The daily planning job is creating and initializing the new Symphony file, based on the new current plan (NCP). The RUNNO value is the run number of this Symphony file.

Workstation CPU is a WNT workstation, but not even a USRREC definition was specified for it.

Loop analysis message, issued in the EQQLOOP data set together with message EQQ3136I or EQQ3137I. Possible values for objects are OCCURRENCES and OPERATIONS.

Loop analysis message, issued in the EQQLOOP data set. It identifies the occurrence of the network when a loop type NO ENTRY POINT or NO EXIT POINT , or both, are detected and the loop analysis fails.

For each occurrence involved in the loop, one message EQQ3136I is issued.

Loop analysis message, issued in the EQQLOOP data set. It identifies the operation that was not checked in the network when a loop type SOME NODES COULD NOT BE CHECKED is detected and the loop analysis fails.

For each operation involved in the loop, one message EQQ3137I is issued.

TIMEZONE parameter is missing in the TOPOLOGY statement.

You entered a name that is longer than four characters in the CPUHOST parameter of the CPUREC statement. OPCMASTER is the only name that can exceed this limit. OPCMASTER can be used only for standard or fault-tolerant agents that are directly attached to the end-to-end server and belong to the MASTERDM domain.

In the CPUREC statement you specified a fault-tolerant agent in the MASTERDM domain with the CPURESDEP parameter set to ON. Fault-tolerant agents in domain MASTERDM must have CPURESDEP set to OFF.

In the CPUREC statement you specified a fault-tolerant agent in the MASTERDM domain with the FULLSTATUS parameter set to ON. Fault-tolerant agents in domain MASTERDM must have FULLSTATUS set to OFF.

The CPULIMIT keyword in the CPUREC statement for workstation WSNAME has a value different from the value stored in the current plan. The value in the current plan cannot be updated by simply running the Symphony Renew option, therefore the CPULIMIT is ignored and the value in the current plan is used to create the Symphony file.

The CPUREC for an extended agent does not refer to an existing CPUHOST. No default values exist as host.

An error in the CPUREC for workstation CPU2 was found. The CPUHOST value is reset to the default value CPU1.

The CPUHOST for the extended agent was incorrectly specified. It was set either to OPCMASTER, a non-existent CPU, or another extended agent. An extended agent cannot use OPCMASTER or another extended agent as a host.

The CPUDOMAIN parameter for the extended agent either does not exist or does not coincide with the domain of the CPUHOST workstation.

This message is issued after message EQQ3146W, if an extended agent was specified as CPUHOST.

An extended agent did not specify the CPUDOMAIN parameter, but its CPUHOST has an incorrect value for it.

Loop analysis message, issued in the EQQLOOP data set. The reduction process was iteratively performed by the loop analysis function and only the operations directly involved in the loop were left in the matrix representing the network. For details, refer to Managing the Workload.

For each operation involved in the loop, one message EQQ3153I is issued.

Loop analysis message, issued in the EQQLOOP data set. It identifies a successor of the operation specified in message EQQ3153I.

Loop analysis message, issued in the EQQLOOP data set. It identifies a predecessor of the operation specified in message EQQ3153I.

Loop analysis message, issued in the EQQLOOP data set. It indicates the dependency that was identified as being removed from the matrix representing the network, to resolve the loop. It also explains the reason for the removal according to the loop analysis that was done.

Possible values for the reason are: IA TIME CHECK, CLOSEST TO LOOP ENTRY, and MINIMAL NET DISTORTION. For details about the meaning of these values, refer to Managing the Workload.

For each application involved in the loop, one message EQQ3158I is issued, in descending order according to the last update made to the application definitions.

Loop analysis failed. Possible values for objects are OCCURRENCES and OPERATIONS. This message is issued in the EQQMLOG data set.

The specified action could not be performed on the specified event data set. Possible values for ACTION are OPENED and READ. This message is issued in the EQQMLOG data set.

The message shows the following status information related to the event data set with DDNAME DDNAME:

• Number of records (excluding the header): RECNUM
• Status: STATUS
• Number of unprocessed event records: RECNOT
• Percentage of unprocessed events over total: PERCENTAGE

The header of the event data set with DDNAME DDNAME has inconsistent or unrecognized data. The data set cannot be used.

A loop was found in a network during the daily planning activity. This message is issued in the system log.

A loop was found in a network during the daily planning activity. The inconsistent definition includes condition dependencies. This message is issued in the system log.

All workstations are closed during the period of time extending from PER1 to PER2. The format of PER1 and PER2 is YYMMDD HHHH.

While processing the index blocks for occurrences belonging to the old current plan, the daily plan batch detected a blank value in the IA time.

The recovery statement (JOBREC) in member JOBNM in EQQSCLIB cannot specify the keyword MESSAGE if the recovery option is STOP. It is not possible to use recovery option STOP with recovery action prompt reply.

The recovery statement (JOBREC) in member JOBNM in EQQSCLIB specifies a non-valid user name USRRE for the recovery job. The user name must be defined on the in the PARMLIB in the users information member (for example, USRINFO)..

The recovery statement (JOBREC) in member JOBNM in EQQSCLIB must specify one of either the JOBSCR or JOBCMD keywords. The two keywords are both either missing or present.

The JOBUSR keyword is missing from the recovery statement (JOBREC) in member JOBNM in EQQSCLIB. The default one specified for CPU CPURE in the CPUREC statement will be used in its place.

The JOBWS keyword is missing from the recovery statement (JOBREC) in member JOBNM in EQQSCLIB. The workstation defined for job JOBNM will be used in its place.

If you are running EQQSLCHK sample JCL, workstation field is filled with N/A (Not applicable), because the CPU name is not available for the sample.

In RECOVERY statement in member JOBNM in EQQSCLIB, there are no JOBCMD or JOBSCR keywords: JOBNM has no recovery job then JOBUSR, JOBWS, INTERACTV, and RCCONDSUC recovery statement keywords will be ignored.

The task is unable to put information for the prompt record of JOB1 job in the SUF1 Symphony file.

In member JOBNM in EQQSCLIB, in JOBREC/RECOVERY statement the length of RCCONDSUC value is not allowed because the length of RCCONDSUC plus the length of JOBSCR/JOBCMD is greater than 4095.

The VARSUB statement was inserted incorrectly in the member JOBNM of the SCRIPTLIB. The VARSUB statement must always be in the first position.

The SCTN definition of the EQQSCLIB library specifies the VAR variable which is neither predefined by the scheduler nor appears in a JCL variable table of the scheduler database.

The variable substitution exit setting of the VAR variable might be set to blank.

The name of a variable can contain from one to eight alphanumeric characters. The first character must be alphabetic.

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

The JOBNM definition of EQQSCLIB library specifies the INTRACTV keyword in the JOBREC or RECOVERY statements. This keyword is ignored because it is supported on Windows workstations only.

The independent variable is currently set to a value that is not included in the dependency value list of the dependent variable.

Data not found in the Extended Info field in the Current Plan operation record.

The variable substitution caused the system automation command text to exceed its maximum length (255 bytes). The operation is identified by the owning application ID, operation input arrival date and time, and operation number.

All data sets associated with the EQQSCLIB ddname are empty.

The recovery statement in member JOBNM in EQQSCLIB specifies a workstation CPURE that is not defined in the topology information member (for example, TPLGINFO).

Job JOBNM processed from EQQSLCHK sample JCL is defined in the script library CONCNUM of the EQQSCLIB DDNAME.

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. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.

The independent variable is currently set to a value that is not included in the list of dependency values related to the dependent variable. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.

The variable used in the command text is not valid. The name of a variable can contain from 1 to 8 alphanumeric characters, and the first character must be alphabetic. The operation is identified by the owning application ID, operation input arrival date and time, and operation number. The variable in error is shown.

Data not found for the variable VAR. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.

The variable substitution exit could set the variable VAR to blank.

The variable used in the system automation command text was not found. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.

An internal error occurred in the workstation definition. Some records result as being defined for destinations but no virtual workstation record with that name are defined in the data base.

The value set for MAXSTNUM in the JTOPTS statement is outside of the allowed range.

The value set for MAXSTWAIT in the JTOPTS statement is outside of the allowed range.

The value set for SMOOTHSUBCONFLEVEL in the JTOPTS statement is outside of the allowed range.

The value of the occurrence number limit is invalid.

The value of the PAGESIZE keyword in the BATCHOPT parameter must be a number from 30 through 500. The default value is 55.

The value of the PLANHOUR keyword in the BATCHOPT parameter is invalid.

The batch program could not open the parameter library (EQQPARM) data set.

The batch program could not find the BATCHOPT initialization statement in the data set specified in the EQQPARM DD statement.

The value of the DP algorithm (DPALG) option in the BATCHOPT parameter is invalid.

The DB2 system specified in the DB2SYSTEM keyword of the BATCHOPT statement is not started, has been stopped, or has abended, or the specified name is incorrect.

DB2 module DB2MOD failed to load during the daily planning batch run.