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.
- 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 is empty: this can be because the corresponding input is empty or because all the input records could not be converted. Ignore this message if you are migrating from a version earlier than V9.5.
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.
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.
- 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 CONVERT statement is not supported by the release that is set in the FROMREL or TOREL keyword, or the value specified in FROMREL is higher than the value set in TOREL.
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
- 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
- 03
- An operation record
- 09
- A rerun record
- 14
- A job log record.
The migration fails without producing a migrated current plan file.
None.
- Run HCL Workload Automation for Z until enough occurrences have been completed.
- Delete occurrences, using the scheduler dialog or the program interface.
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.
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.
- 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
- OPER
- The operation requested
- DDNM
- 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.
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.
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.
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.