EQQIC00 - EQQIC79

EQQIC00I

FILE FILE HAS BEEN CONVERTED NCOPY RECORDS COPIED, NUPD RECORDS UPDATED, NSKIP RECORDS SKIPPED

A VSAM file has been successfully built from the corresponding file in a different release of HCL Workload Automation for Z. This message documents the number of records copied without change, the number of modified records, and the number of records in the input file that were not used.

The migration program continues processing by reading the next CONVERT statement from the input file.

None.

If there is a problem using the output file, verify that the statistical information in this message is correct.

EQQIC01E

THE INPUT DATA SET, DDNAME=SYSIN, COULD NOT BE OPENED

The program could not open its input data set.

The program is terminated.

Check that the SYSIN DD statement exists and is correctly coded. Correct the errors and resubmit the JCL.

EQQIC02E

UNABLE TO CONVERT FILE FILE

The file migration program could not run the requested file conversion. This message is preceded by one or more error messages that describe the problem.

The migration program continues processing by reading the next CONVERT statement from the input file.

Correct the errors and resubmit the file migration batch job.

Check the previous messages to determine the cause of the problem.

Verify that:
  • The output data sets are empty VSAM data sets.
  • The output data sets are correctly allocated.
  • The job executing the migration program is authorized to update the output data sets.
  • The input data sets do not contain errors.
  • The input data sets are VSAM data sets at the level specified.
  • The migration program is authorized to read the input data sets.

EQQIC03E

LOGICAL RECORD SIZE FOR THE INPUT DATA SET, DDNAME SYSIN, IS NOT VALID

The program could not use the input data set, SYSIN, because its logical record length is not 80 bytes.

The program is terminated.

Correct the errors and resubmit the file migration batch job. If necessary, copy SYSIN statements to a file that has record size 80 bytes.

Check that the SYSIN DD statement exists and is correctly coded.

EQQIC04E

EQQICTOP TERMINATED BECAUSE OF UNRECOVERABLE ERRORS

A severe error occurred during the execution of the file migration program.

The migration program is terminated.

Save the HCL Workload Automation for Z message log and dump data sets. To collect appropriate documentation for problem determination, see Information to collect for migration problems. Search the IBM Support database for a solution at http://www.ibm.com/software/sysmgmt/products/support.

Review the message log and the dump data set.

EQQIC05E

WRITE OF NEW RECORD FAILED, RECORD WITH SAME KEY IS ALREADY PRESENT

A VSAM error occurred when writing a new record to the output data set. Error codes indicate that the output data set contains a record with the same key as the new record.

The migration program continues processing with the next CONVERT statement, if one is defined.

Make sure that the output data set is empty when the migration starts.

EQQIC06W

THE OUTPUT DATA SET DOES NOT CONTAIN ANY TYPE RECORDS

The Logical part of the output AD data set represented by "type" (which can be "application" or "JCL variable table") or "all WS closed" is empty: this can be because also the corresponding input is empty or because all the input records could not be converted.

The migration program continues processing by reading the next CONVERT statement from the SYSIN file. The return code for the current CONVERT statement is set to 4.

None. If the input was also empty, otherwise perform the action described for the messages issued by the migration program before this one.

Problem determination: check if the warning message can be ignored (because also the input logical part is empty) or determine from the previous message why the input records could not be converted.

EQQIC07E

APPLICATION AD WITH INPUT ARRIVAL IA AND OPERNUM OP# THE FOLLOWING SPECIAL RESOURCES CAUSE EXCEED OF THE OUTPUT RECORD SIZE:

During conversion of the current plan operation record identified in the message text, the migrated output record would be too large to store without modification. At least one special resource referenced by the operation cannot be included. The subsequent message EQQIC08I identifies the special resources that cannot fit.

The migration program is terminated. No valid current plan is created.

Start up the previous release of HCL Workload Automation for Z and delete any special resource entries from the operation that are unnecessary. The entries you delete do not have to be those identified in EQQIC08I.

As each special resource entry is expanded by 8 bytes, while the maximum record size remains the same, it is possible to encounter this problem.

EQQIC08I

SR

This message is associated with EQQIC07E. It lists those special resources that could not fit into the output current plan record.

The migration program is terminated.

See the description for message EQQIC07E.

EQQIC09E

APPLICATION INDEX RECORD FOR AD HAS AN INVALID INPUT ARRIVAL IA FOR AN OCCURRENCE IN STATUS ST

A current plan application index record CPLREC05, identified in the message text, contains an invalid input arrival date in one of its occurrence data.

The migration program continues processing by reading the next CONVERT statement from the input file. No valid current plan is created.

Do one of the following:
  • Update the occurrence with a valid I/A date.
  • If the occurrence status is complete, run two or more CP EXTENDS to delete it from the current plan, before rerunning the conversion.

EQQIC10E

THE FILE KEYWORD IS MISSING

The current CONVERT statement does not contain the FILE keyword.

The migration program continues processing by reading the next CONVERT statement from the input file.

Add the FILE keyword to the current CONVERT statement and resubmit the file migration batch job.

EQQIC11E

A PARAMETER IS REQUIRED FOR THE FILE KEYWORD

The FILE keyword in the current CONVERT statement does not specify a value.

The migration program continues processing by reading the next CONVERT statement from the input file.

Add a file name value to the FILE keyword of the current CONVERT statement, and resubmit the file migration batch job.

EQQIC12E

THE FROMREL KEYWORD IS MISSING

The current CONVERT statement does not contain the FROMREL keyword.

The migration program continues processing by reading the next CONVERT statement from the input file.

Add the FROMREL keyword to the current CONVERT statement and resubmit the file migration batch job.

EQQIC13E

AN INCORRECT PARAMETER WAS SPECIFIED FOR THE FROMREL KEYWORD

The FROMREL keyword in the current CONVERT statement does not specify a supported value.

The migration program continues processing by reading the next CONVERT statement from the input file.

Add a supported file name value to the FROMREL keyword of the current CONVERT statement and resubmit the file migration batch job.

EQQIC14E

THE TOREL KEYWORD IS MISSING

The current CONVERT statement does not contain the TOREL keyword.

The migration program continues processing by reading the next CONVERT statement from the input file.

Add the TOREL keyword to the current CONVERT statement and resubmit the file migration batch job.

EQQIC15E

AN INCORRECT PARAMETER WAS SPECIFIED FOR THE TOREL KEYWORD

The TOREL keyword in the current CONVERT statement does not specify a supported value.

The migration program continues processing by reading the next CONVERT statement from the input file.

Add a supported file name value to the TOREL keyword of the current CONVERT statement and resubmit the file migration batch job.

EQQIC16E

INPUT APPLICATION APPL IS TOO LARGE TO BE WRITTEN TO THE OUTPUT FILE

An application description (AD) in the input AD file defined to the migration program is too large to be written to the output data set. The most likely reason for this message is that the maximum record size is larger for the input AD file than for the output AD file.

The current input AD record cannot be converted to the format of the output file. The migration program continues processing by reading the next record on the input file. The return code for the current CONVERT command is 8, or higher.

Determine if the maximum record size defined for the output AD file is too small. If it is, reallocate the output AD file and run the migration program again.

EQQIC17E

INPUT LTP OCCURRENCE APPLIA IS TOO LARGE TO BE WRITTEN TO THE OUTPUT FILE

A long-term plan (LTP) occurrence in the input LTP file defined to the migration program is too large to be written to the output data set. The most likely reason for this message is that the maximum record size is larger for the input LTP file than for the output LTP file.

The current input LTP record cannot be converted to the format of the output file. The migration program continues processing by reading the next record on the input file, but no more records are written to the output file. The return code for the current CONVERT command is 8, or higher.

Determine if the maximum record size defined for the output LTP file is too small. If it is, reallocate the output LTP file and run the migration program again.

EQQIC18E

FROMREL AND TOREL COMBINATION NOT SUPPORTED FOR FILE FILE

The file FILE specified in the current CONVERT statement is not supported by the release defined for the FROMREL or TOREL keyword.

The migration program continues processing with the next CONVERT statement, if one is defined.

Refer to Planning and Installation for information about the valid combinations. Correct the value in the FILE, FROMREL, or TOREL keyword of the current CONVERT statement and resubmit the job.

EQQIC36E

CURRENT PLAN RECORD OF TYPE RECID FOR APPLICATION AD WITH INPUT ARRIVAL IA AND OPERATION NUMBER OPNUM IS NOT VALID, TOO HIGH OPERATION NUMBER, CANNOT BE CONVERTED

The operation number in one of the records in the input file is higher than the range supported by the HCL Workload Automation for Z release to which you are reoccurring to. RECID is the current plan record type:
03
An operation record
09
A rerun record
14
A joblog record.

The migration fails without producing a migrated current plan file.

None.

Use the scheduler dialog or the program interface to update the current plan file being migrated, making sure that all the operation numbers are in the range supported by the release to which you are reoccurring to.

EQQIC37E

CURRENT PLAN RECORD OF TYPE RECID FOR APPLICATION AD WITH INPUT ARRIVAL IA IS NOT VALID, TOO HIGH OCCURRENCE NUMBER, CANNOT BE CONVERTED

The occurrence number in one of the records in the input file is higher than the range supported by the HCL Workload Automation for Z release to which you are reoccurring to. RECID is the current plan record type:
03
An operation record
09
A rerun record
14
A joblog record.

The migration fails without producing a migrated current plan file.

None.

Perform daily planning to reduce the number of occurrences in the current plan being migrated. Set the BATCHOPT parameter PREVRES to NO at the replan. If the current plan still has too many occurrences, do either of the following:
  • Run HCL Workload Automation for Z until enough occurrences have been completed.
  • Delete occurrences, using the scheduler dialog or the program interface.
Repeat the plan.

EQQIC38W

RECTYP RECORD FOR OCCURRENCE AD AI, OPERATION OPNUM IS TOO LARGE TO BE WRITTEN TO THE OUTPUT FILE

A record in the input JS file defined to the migration program is too large to be written to the output file. The most likely reason is that the maximum record size is larger for the input JS file than for the output JS file.

The record that is too large is ignored. The migration program continues to process normally. The return code for the current CONVERT run is 4 or higher.

Determine whether the maximum record size defined for the JS file is too small, reallocate the file, and rerun the migration job.

EQQIC39E

AD RECORD FOR APPLICATION AD WITH OPERATION NUMBER OPNUM IS NOT VALID, TOO HIGH OPERATION NUMBER, CANNOT BE CONVERTED PREOP PREAD

The operation number OPNUM is higher than the maximum value supported by the release of HCL Workload Automation for Z to which you are performing the fallback (values higher than 99 were introduced in Version 2.2.0.). The PREOP and PREAD variables might be displayed unresolved in the normal case. Alternatively, if the error has been discovered checking the corresponding section of the input operation, the variables might contain the operation number and the application ID of an external predecessor .

The fallback fails without producing the output AD file.

None.

Use the scheduler dialog or the programming interface to update the AD file input to the fallback. Ensure that all the operation numbers are in the range supported by the release to which the output refers.

EQQIC40E

INVALID BLKSIZE — THE OUTPUT JS FILE MUST BE ALLOCATED WITH THE SIZE INCREASED BY 4 BYTES

In OPC Version 2.3.0 the record size of the JS files was increased by 4 bytes more than in previous versions. Check the cluster definition of the VSAM JS file and increase the minimum and maximum record size with the same length.

The conversion fails without producing a converted JS file.

For conversion from OPC Version 2.2.0 to later versions:
  • Define the cluster for the output JS file with increased record size
  • Submit the conversion job again

EQQIC41E

CALENDAR CAL HAS ALL DAYS FREE. AT LEAST ONE WORKDAY IS REQUIRED

Calendar CAL is rejected because it has no work days. It has not been migrated.

Application descriptions referencing Calendar CAL are migrated referencing an unexisting calendar.

Define a consistent Calendar with at least a work day.

EQQIC42E

THE NAME OF THE SUBSYSTEM CONVERTING FROM IS MISSING, KEYWORD FROMSUBSYSTEM

The name of the subsystem converting from is required when converting history data.

The migration program terminates.

Add the FROMSUBSYSTEM keyword to the CONVERT statement and resubmit the migration job.

EQQIC43W

THERE IS NO FROMREL/FROMSUBSYSTEM OPERATIONS HISTORY DATA

The input file to the conversion program contains no records of the specified release, FROMREL, and subsystem, FROMSUBSYSTEM.

The problem occurred because there is no input data or because you defined the wrong HCL Workload Automation for Z subsystem, the wrong version, or both.

The migration program terminates.

Check the input file to the EQQICTOP conversion program.

EQQIC44E

OPER OF FILE DDNM FAILED

A sequential I/O request failed.
OPER
is the operation requested
DDNM
is the ddname of a file to be allocated to the migration program EQQICTOP

The migration program terminates.

Check the file allocations to the migration program. This message can be preceded by message EQQ0959 with more information about the error.

EQQIC45W

INPUT JCL VARIABLE TABLE JVT IS TOO LARGE TO BE WRITTEN TO THE OUTPUT FILE

A JCL variable table in the input AD file defined to the migration program is too large to be written to the output data set. The most likely reason for this message is that the maximum record size is larger for the input AD file than for the output AD file.

The current input AD record is skipped. The migration program continues normal processing by reading the next record on the input file. The return code for the current CONVERT command is 4 or higher.

Determine if the maximum record size defined for the output AD file is too small. If it is, reallocate the output AD file and run the migration program again.

EQQIC46W

THE WORKSTATION WSNAM WAS DEFINED AS VIRTUAL WS. AFTER MIGRATION IT BECOMES A NORMAL WORKSTATION, PLEASE REVIEW YOUR PLAN ACCORDINGLY

You requested a fallback to a version that does not support virtual workstations.

The program converts WSNAM to a standard computer workstation.

Verify the resulting destination field for WSNAM in the workstation description. Consider defining a computer workstation for each item in the destination list of the original workstation.

EQQIC47W

THE WORKSTATION WSNAM WAS DEFINED AS Z-CENTRIC. AFTER MIGRATION IT BECOMES A NORMAL WORKSTATION, PLEASE REVIEW YOUR PLAN ACCORDINGLY.

You requested a fallback to a version that does not support z-centric workstations.

The program converts WSNAM to a standard computer workstation.

Verify the resulting destination field for WSNAM in the workstation description.

EQQIC48E

ROLL-BACK AD MIGRATION NOT POSSIBLE. STEP DEPENDENCIES MUST BE REMOVED. CHECK FOLLOWING CONDITION: ADID OPNO CONDID.

You requested a fallback to a version that does not support step-level dependencies. This message is not issued if you are requesting a fallback to a version earlier than 8.5.

The migration ends in error without producing a migrated AD file.

Remove the step dependency definitions from the indicated conditions identified by the application name ADID, operation number OPNO, and condition ID CONDID.

EQQIC49E

ROLL-BACK CP MIGRATION NOT POSSIBLE. STEP DEPENDENCIES MUST BE REMOVED. CHECK FOLLOWING CONDITION: ADID IA OPNO CONDID.

You requested a fallback to a version that does not support step-level dependencies. This message is not issued if you are requesting a fallback to a version earlier than 8.5.

The migration ends in error without producing a migrated CP file.

Remove the step dependency definitions from the indicated operations.

EQQIC50E

ROLL-BACK MIGRATION NOT POSSIBLE. MULTIPLE CP AD INDEX RECORDS FOUND FOR APPLICATION APPL

The number of CP AD index records for the specified application in the input file is greater than one. This happens when more than 877 occurrences are defined in the CP for the application.

The migration ends in error without producing a migrated CP file.

Remove all occurrences exceeding the limit of 877 from the specified application. Do a REPLAN for the current plan and rerun the migration job

EQQIC51E

ROLL-BACK MIGRATION NOT POSSIBLE. OPERATIONS IN X STATUS FOUND IN THE CURRENT PLAN.

Operations in suppressed by condition status (X status) were found during a migration process from version 8.6 or 8.5.1 to version 8.5 or earlier, or from version 8.5 to version 8.5.1 or 8.6.

The migration operation is interrupted and the conversation fails without producing the output current plan.

Consider identifying the operations in X status by using the dialog operation list, filtering by status. Then you can:
  • Delete the operations in X status from the CP.
  • Set to complete the occurrences that are not in C status and contain operations in X status. Then run a replan, to remove the previous occurrences from the plan.

EQQIC52I

STATUS CHANGED FROM W TO ST FOR OPERATION AD IA OPER.

The current operation has condition dependencies defined in the input current plan, with undefined overall condition status.

The migration program continues.

Consider starting the operation by using a manual action.

EQQIC53E

ROLL-BACK MIGRATION NOT POSSIBLE. Z-CENTRIC STARTED OPERATIONS STILL IN PLAN.

You requested to perform a fallback to a previous version, but the process has found started operations running on z-centric agent workstations.

The fallback migration stops.

Manually complete the started operations that are running on the z-centric agent workstation, then retry the migration.

EQQIC54W

A FALLBACK CANNOT BE PERFORMED ON THE REMOTE WORKSTATION WSNAM. THIS TYPE OF WORKSTATION IS NOT SUPPORTED IN EARLIER VERSIONS OF THE PRODUCT. THE RECORD IS SKIPPED.

The process detected a workstation defined as a remote workstation. You cannot perform a fallback on this type of workstation because it is not supported in earlier versions of the product.

The fallback continues, skipping the remote workstation.

You must manually remove all applications that refer to this workstation from the Application Description database and the Current Plan.

EQQIC55W

A FALLBACK CANNOT BE PERFORMED ON THE DYNAMIC WORKSTATION WSNAM. THIS TYPE OF WORKSTATION IS NOT SUPPORTED IN EARLIER VERSIONS OF THE PRODUCT. THE RECORD IS SKIPPED.

The process detected a workstation defined as a dynamic workstation. You cannot perform a fallback on this type of workstation because it is not supported in earlier versions of the product.

The fallback continues, skipping the dynamic workstation.

You must manually remove all applications that refer to this workstation from the Application Description database and the Current Plan.

EQQIC56E

ROLLBACK MIGRATION NOT POSSIBLE. REMOTE ENGINE INFO MUST BE REMOVED. CHECK FOLLOWING OPERATION:ADID OPER.

The remote job information is specified for the application operation identified by application name ADID and operation number OPER, which means the operation is a shadow job defined to implement cross dependencies. Cross dependencies are supported only from HCL Workload Automation for Z Version 8.6 and later. For this reason, the fallback migration is not possible.

After scanning the Application Description database to detect all possible migrations problems, the migration ends in error without producing a migrated AD database.

Remove or modify all of the operations containing the remote job information, and then retry the migration.

EQQIC57E

ROLLBACK MIGRATION NOT POSSIBLE. REMOTE ENGINE INFO MUST BE REMOVED. CHECK FOLLOWING OPERATION: ADID IA OPER.

Remote job information is specified for the operation identified by application name ADID, input arrival time IA, and operation number OPER which means the operation is a shadow job defined to implement cross dependencies. This type of job is supported only from HCL Workload Automation for Z Version 8.6 and later. For this reason, the operation will not be migrated.

The migration fails.

You must manually remove the shadow jobs from the plan, run a replan, and then retry the migration.

EQQIC58E

ROLLBACK MIGRATION NOT POSSIBLE. JOBS ON DYNAMIC WORKSTATIONS MUST BE REMOVED. CHECK FOLLOWING OPERATION: ADID IA OPER.

The operation identified by application name ADID, input arrival time IA, and operation number OPER is a job defined on a dynamic workstation. This type of job is supported only from HCL Workload Automation for Z Version 8.6 and later. For this reason, the operation will not be migrated.

The migration fails.

You must manually remove the dynamic jobs from the plan, run a replan, and then retry the migration.

EQQIC59W

A FALLBACK CANNOT BE PERFORMED ON RUN CYCLE GROUP RGNAM. IT IS NOT SUPPORTED IN EARLIER VERSIONS OF THE PRODUCT. THE RECORD IS SKIPPED.

The process detected a run cycle group definition. You cannot perform a fallback on this type of resource because it is not supported in earlier versions of the product.

The fallback process continues, but the run cycle group definition is skipped.

Remove or modify all the applications that refer to this type of resource.

EQQIC60W

INPUT LTP OCCURRENCE APPL &IA HAS HAS A BLANK DEADLINE. IT IS SET TO A DEFAULT VALUE (2071-12-31 24.00).

The occurrence contains a blank deadline date/time. To proceed with the fallback to a previous release it is automatically set to a default value (2071-12-31 24.00).

The migration program continues.

Make sure that the occurrence migrated and that the default deadline date/time is valid for it.

EQQIC61W

INPUT CURRENT PLAN OCCURRENCE AD IA HAS A MANDATORY PENDING STATUS. IT IS NOT SUPPORTED IN EARLIER VERSION. THIS OCCURRENCE IS SKIPPED.

The occurrence indicates that it is in the Mandatory Pending status. This is not supported when performing a fallback to a previous release.

The occurrence is skipped (it is not migrated) and the migration program continues.

None.

EQQIC62E

ROLL-BACK MIGRATION NOT POSSIBLE. JOBS IN MANDATORY PENDING STATUS MUST BE REMOVED. CHECK FOLLOWING OPERATION: ADID IA OPER.

During the migration of a CP or XD data set the process found that the operation identified by application name ADID, input arrival time IA, and operation number OPER is in the mandatory pending status. An operation in this status is supported only in HCL Workload Automation for Z Version 9.1 or later. For this reason, the operation will not be migrated.

The migration of the CP or XD data set fails.

Manually remove the operation from the plan or delete the mandatory dependency, run a replan, and then retry the migration. Note that to successfully remove all the data related to mandatory pending predecessors, you must run a DP batch replan.

EQQIC63W

APPLICATION AD HAS EXTERNAL OR CONDITIONAL PREDECESSORS USING RESOLUTION OPTIONS THAT CANNOT BE ROLLED BACK: THEY WILL BE CONVERTED TO OLD CRITERIA (CLOSEST PRECEDING, NO MANDATORY).

See message text.

Converts the matching criteria for predecessor to closest preceding and not mandatory.

None

EQQIC64W

APPLICATION AD HAS A RUN CYCLE WITH INPUT BLANK ARRIVAL TIME AND CANNOT BE ROLLED BACK: APPLICATION WILL BE SKIPPED.

See message text.

The application is not rolled back.

None.

EQQIC65W

APPLICATION AD HAS A RUN CYCLE WITH BLANK DEADLINE THAT CANNOT BE ROLLED BACK: DEADLINE WILL BE SET TO 002400.

See message text.

The deadline for the application is set to 2400 hours.

None.

EQQIC67W

IN THE FALLBACK PROCESS OF THE WORKSTATIONS DATABASE, THE NUMBER OF PARALLEL SERVERS DEFINED FOR SOME WS_NAME INTERVALS WAS FORCED TO 99 BECAUSE THE 99 LIMIT WAS EXCEEDED.

While converting the workstations database, the process found that the number of parallel servers specified for certain intervals exceeds the limit allowed for the target release.

The migration program continues its process and forces the exceeding values to the limit supported by the release.

No action is requested.

EQQIC68W

IN THE FALLBACK PROCESS OF THE CURRENT PLAN, THE NUMBER OF PARALLEL SERVERS DEFINED FOR SOME WS_NAME INTERVALS WAS FORCED TO 99 BECAUSE THE 99 LIMIT WAS EXCEEDED.

While converting the current plan, the process found that the number of parallel servers specified for certain workstation intervals exceeds the limit allowed for the target release.

The migration program continues its process and forces the exceeding values to the limit supported by the release.

No action is requested.

EQQIC69W

LTP OCCURRENCE APPL IA HAS MANDATORY PENDING PREDECESSORS: THEY HAVE BEEN MARKED AS DELETED.

The fallback action cannot be performed on mandatory pending predecessors as they are non-existing entities in a long term plan.

The LTP migration program flags them as DELETED and issues this message.

No action is requested.

EQQIC70E

ROLL-BACK MIGRATION NOT POSSIBLE. APPLICATION DEPENDENCIES MUST BE REMOVED. CHECK FOLLOWING APPLICATION: AD.

For the application AD, the fallback action cannot be performed because the application contains application dependencies, which are not supported on output release.
The migration program skips this record and issues this message. The migration fails.
Remove the application dependencies before performing the roll back.

EQQIC71E

ROLL-BACK MIGRATION NOT POSSIBLE. OPERATION DEPENDENCIES ON APPLICATIONS MUST BE REMOVED. CHECK FOLLOWING OPERATION: AD OPER.

For the application AD, the fallback action cannot be performed because the application contains operations with application dependencies, which are not supported on output release.
The migration program skips this record and issues this message. The migration fails.
Remove the application dependencies before performing the roll back.

EQQIC72E

INPUT CURRENT PLAN OCCURRENCE AD IA HAS APPLICATION DEPENDENCIES. CURRENT PLAN CANNOT BE CONVERTED.

The occurrence identified by application name AD and input arrival time IA contains application dependencies, which are not supported by the output release. Current plan cannot be migrated.
The migration program skips this record and issues this message. The migration fails.
Remove the application dependencies before performing the roll back.

EQQIC73E

INPUT CURRENT PLAN OPERATION AD IA OPER HAS APPLICATION DEPENDENCIES. CURRENT PLAN CANNOT BE CONVERTED.

The operation identified by application name AD, input arrival time IA, operation number OPER contains application dependencies, which are not supported by the output release. Current plan cannot be migrated.
The migration program skips this record and issues this message. The migration fails.
Remove the application dependencies before performing the roll back.

EQQIC74W

FOR APPLICATION AD, THE NOT STARTED ACTIONS OR DEADLINE ACTIONS CANNOT BE ROLLED BACK. THEY ARE REMOVED.

For the application AD, the fallback action cannot be performed on Not Started Actions or Deadline Actions, because they are non-existing entities on output release.
The migration program creates an output record without the actions that are not supported, and issues this message.
No action is requested.

EQQIC75W

FOR INPUT CURRENT PLAN OPERATION AD IA OPER, THE NOT STARTED ACTIONS OR DEADLINE ACTIONS CANNOT BE ROLLED BACK. THEY ARE REMOVED.

For the application AD IA OPER, the fallback action cannot be performed on Not Started Actions or Deadline Actions, because they are non-existing entities on output release.
The migration program creates an output record without the actions that are not supported, and issues this message.
No action is requested.

EQQIC76W

EQQIVTOP TERMINATED BECAUSE OF UNRECOVERBLE ERRORS.

A severe error occurred during the execution of the file migration program.

The migration program is terminated.

Save the HCL Workload Automation for Z message log and dump data sets. To collect appropriate documentation for problem determination, see Information to collect for migration problems. Search the IBM Support database for a solution at Support.

Review the message log and the dump data set.

EQQIC77W

INPUT PGT VARIABLE TABLE PGT IS TOO LARGE TO BE WRITTEN TO THE OUTPUT FILE.

A PGT variable table in the input AD file defined to the migration program is too large to be written to the output data set. The most likely reason for this message is that the maximum record size is larger for the input AD file than for the output AD file.

The current input AD record is skipped. The migration program continues normal processing by reading the next record on the input file. The return code for the current CONVERT command is 4, or higher.

Determine if the maximum record size defined for the output AD file is too small. If it is, reallocate the output AD file and run the migration program again.

EQQIC78W

INPUT FX RECORD FX IS TOO LARGE TO BE WRITTEN TO THE OUTPUT FILE.

An FX record in the input AD file defined to the migration program is too large to be written to the output data set. The most likely reason for this message is that the maximum record size is larger for the input AD file than for the output AD file.

The current input AD record is skipped. The migration program continues normal processing by reading the next record on the input file. The return code for the current CONVERT command is 4, or higher.

Determine if the maximum record size defined for the output AD file is too small. If it is, reallocate the output AD file and run the migration program again.

EQQIC79W

THE POTENTIAL PREDECESSOR RECORD FOR APPLICATION APPL CONTAINS MORE THAN 1000 POTENTIAL SUCCESSOR OPERATIONS, EXCEEDING THE MAXIMUM ALLOWED. THE EXCEEDING POTENTIAL SUCCESSORS ARE NOT DEFINED.

The potential predecessor record for application APPL has a number of potential successors which exceeds the maximum value allowed (1000). The potential successors over that limit are not defined.

The migration program continues normal processing.

None.