Reason:
The SARDBASE LOAD or MERGE statement specified to load or merge an r11.5 or earlier release level database to a new database that contains a large format data set (data set with more than 4369 cylinders). Large format data sets are only supported for r11.6 or higher release level databases.
Action:
Recreate the new database with data sets that have 4369 cylinders or less before loading or merging the database.
Alternatively, version the old r11.5 or earlier release level database(s) to r11.6 or higher with the SARDBASE VERSION statement. Perform a new unload the database(s) now, and then load or merge the database(s).
Reason:
A SARDBASE MERGE job was submitted without DD statements.
Action:
Include the DD statements in the SARDBASE JCL.
Reason:
One of the SARDBASE MERGE input tapes is incomplete.
Action:
Verify that all SARDBASE MERGE input tapes are correct, and rerun SARDBASE MERGE.
Reason:
The MERGE input tapes do not contain any data.
Action:
Verify that all SARDBASE MERGE input tapes are correct, and rerun SARDBASE MERGE.
Reason:
One of the input tapes for SARDBASE MERGE failed to load to the database.
Action:
Verify that all SARDBASE MERGE input tapes are created by the SARDBASE UNLOAD facility.
Reason:
Input tape SARMERGx began scan processing.
Action:
None. This is an informational message.
Reason:
Input tape SARMERGx began load processing.
Action:
None. This is an informational message.
Reason:
In the SARDBASE MERGE operation, a new generation nnnnnnnn exceeded 65,535 SYSOUTs.
Action:
Reduce the number of input databases and rerun SARDBASE MERGE.
Reason:
The tape index for the output database is the same as one of the SARDBASE MERGE input tapes.
Action:
Name the output tape index differently than any of the MERGE input tapes, and rerun SARDBASE MERGE.
Reason:
One or more of the SARMERGX tapes containing data on optical disk was not properly UNLOADed with the SECOND/NOSECOND parameter of the SARDBASE MERGE facility.
Action:
Unload all databases with the SECOND/NOSECOND parameter of SARDBASE UNLOAD specified. Then rerun SARDBASE MERGE.
Reason:
SARDBASE MERGE is loading SYSOUTS to disk. The SYSOUTs were on the optical disk, and are unloaded to tape by SARDBASE UNLOAD, with the SECOND parameter specified.
Action:
None. This message is informational.
Reason:
The secondary disk storage driver specified in the MERGE control statement of SARDBASE cannot be successfully loaded for execution.
Action:
Correct the control statement, and rerun SARDBASE MERGE.
Reason:
One of the SARDBASE MERGE input tapes is missing the Master Control Record.
Action:
Check the output of all SARDBASE UNLOAD jobs that are used to create input tapes for SARDBASE MERGE. Verify that complete tapes were created. Rerun SARDBASE MERGE.
Reason:
User is attempting to MERGE databases, but the combined database exceeds 64K backup tapes.
Action:
MERGE is TERMINATED in phase1 with a return code of 16. If you are attempting to merge more than two databases into a single database, consider merging half of these databases into one database and the other half into a second database.
Reason:
User is attempting to MERGE databases, but the combined database exceeds 64K DR tapes.
Action:
MERGE is TERMINATED in phase1 with a return code of 16. If you are attempting to merge more than two databases into a single database, consider merging half of these databases into one database and the other half into a second database.
Reason:
The database from SARMERGn contains a report that is on Backup tape nnnnn, but CA View has no TCR record for this tape.
Action:
The report is dropped and processing continues. The MERGE eventually ends with a return code of 4. This error is caused by when a user runs SARTDR to TADD reports to a database, but for some reason the SARTDR abended before it added the TCR record to the database.
Reason:
A CA View program has terminated, and a dump was generated. In this message, blk specifies the control block that CA View expected but did not receive (usually IFB, SFB, XFB, or DBB). It can be suffixed with a number indicating which test point in the program detected the problem.
Action:
Send the dump to CA Technical Support. Restart whatever program was terminated. If the problem recurs, run SARDBASE VERIFY on the database. For assistance, contact Technical Support at http://ca.com/support.
Reason:
An I/O error occurred reading the SYSOUT to be restored. The SYSOUT is skipped and execution continues with the next SYSOUT group.
Action:
See the associated message for the I/O error.
Reason:
An I/O error occurred writing the SYSOUT on the output database. Execution is terminated.
Action:
See the associated message for the I/O error.
Reason:
The specified SYSOUT group is being copied.
Action:
None. This is an informational message.
Reason:
The file recorded in the backup recovery file or specified in the JCL does not contain a backup of the master index.
Action:
Use SARTCP to map the backup tape to locate the backup of the master index.
Reason:
The specified member of the online library is being copied.
Action:
None. This is an informational message.
Reason:
An external sort is used to sequence alternate index records for the date selection before writing the records to the database. The sort phase ended with the specified nonzero return code resulting in the loss of all or some of the alternate index records.
Action:
The nonzero return code from the sort phase can be caused by a critical error as indicated by a previous message or a sort error as indicated in the sort message data set (SYSOUT). Review the messages to determine the appropriate action. Recreate the new database and resubmit the RESTORE request.
Reason:
The program load modules and the database are not at the same release level. This is normally caused by the STEPLIB, JOBLIB, linklist, or LPA pointing to old load modules, or the database has not been converted to the correct release level (new releases of the product can require conversion of the database).
Action:
You can either STEPLIB to the correct load modules or convert the database to the correct release level.
Reason:
The specified member of the model banner page library is being copied.
Action:
None. This is an informational message.
|
Copyright © 2013 CA.
All rights reserved.
|
|