Reason:
The SARDBASE RESTORE statement specified to restore 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.
Reason:
A permanent I/O error occurs while reading the tape backup of the master index.
Action:
Resubmit the job. If the error recurs, use a different backup for restoring the master index.
Reason:
The requested backup for the master index cannot be located.
Action:
Restore the master index from a newer backup.
Reason:
Dynamic allocation failed for the backup tape file. The hexadecimal error and information codes are provided.
Action:
Correct the problem, and then resubmit the job.
Reason:
The restore function has begun.
Action:
None. This is an informational message.
Reason:
This message is informational indicating that the restore process has restored the index data necessary to resume archival and online activity. The restore process continues with the restoration of SYSOUT groups and SYSOUT data.
Action:
If errors occurred during the loading of panel data or if the FROM database is omitted from the RESTORE control statement, reload online panels to the database before resuming online activity.
Reason:
This message is informational indicating that the restore process proceeds with the restoration of SYSOUT groups and SYSOUT data.
Action:
None. This message is informational.
Reason:
This message indicates that the SYSOUT groups are added to the database during the restore process. This message is also written to the operator console at intervals based on the DBMSGFRQ initialization parameter to inform the operator of the progress of the restore process.
Action:
None. This message is informational.
Reason:
A SARTAPE DD statement or a SARRECV DD statement has not been included in the JCL for the job. CA View cannot determine the backup tape to use for the restore.
Action:
Correct the JCL, and then resubmit the job.
Reason:
The master index must be contained on a single tape volume when the SARRECV DD statement is not specified.
Action:
Correct tape sequence and retry.
Reason:
Error attempting to access the recovery data set.
Action:
None. If a hardware error is not indicated. Contact CA Technical Support.
Reason:
The first record on this tape must be an index continuation record. This tape could have been used out of sequence.
Action:
Correct tape sequence and retry.
Reason:
The panel, banner, and SYSOUT data is not restored because an old database name is not specified in the RESTORE control statement.
Action:
The SARDBASE, SARRSP, and/or SARTDR utilities must be used to restore or load panel, banner, or SYSOUT data to the database.
Reason:
An I/O error occurred when opening the database.
Action:
Probably none; however, verify that there is no major problem with the database.
Reason:
The database is already at the desired level.
Action:
None. This is an informational message.
Reason:
The release level to be converted to is not supported.
Action:
Check the release number, and then resubmit the job.
Reason:
The specified release is being converted.
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 VERSION or CONVERT request.
Reason:
The specified logical view was too large to be converted to Release 11.0 format. The logical view definition is not converted.
Action:
If the logical view definition is needed, manually add the logical view definition to the Release 11.0 database.
Reason:
The SARCONV DD statement is required for the SARDBASE utility CONVERT control statement to output previous release database records.
Action:
Add the SARCONV DD statement to the JCL, and then rerun the job.
Reason:
The SARDBASE utility CONVERT function was unable to open the SARCONV DD statement. The job log must contain messages identifying the error.
Action:
Correct the error, and then rerun the job.
Reason:
A stop command was issued while processing the VERSION or CONVERT control statement of the SARDBASE utility. Control statement processing ended prematurely.
Action:
None. The database conversion has to be resubmitted and run to completion before the database can be used.
Reason:
The SARCTAB DD statement is required for the SARDBASE utility CONVERT TABLE control statement to output identifiers that require short identifier names.
Action:
Add the SARCTAB DD statement to the JCL, and then rerun the job.
Reason:
The SARDBASE utility CONVERT function was unable to open the SARCTAB DD statement. The job log must contain messages identifying the error.
Action:
Correct the error, and then rerun the job.
Reason:
The SARCTAB DD statement contains an invalid control record, a missing identifier name, or an invalid identifier name.
Action:
Correct the control statement, and then rerun the job.
Reason:
An identifier name with the same name is previously encountered in the SARCTAB DD statement or exists in the database.
Action:
Correct the SARCTAB DD statement record, and then rerun the job.
Reason:
The specified report identifier name is too long, and a short name is not supplied in the convert table referenced by the SARCTAB DD statement. The conversion process terminates.
Action:
Add a control statement to the )REPORT section of the SARCTAB DD statement identifying the specified report identifier and its associated short name and rerun the job. If the convert table has not been created, the SARDBASE utility can be run with a CONVERT TABLE statement to build a table of long identifier names that require short identifier names.
Reason:
The specified SYSOUT identifier name is too long, and a short name is not supplied in the convert table referenced by the SARCTAB DD statement. The conversion process terminates.
Action:
Add a control statement to the )SYSOUT section of the SARCTAB DD statement identifying the specified SYSOUT identifier and its associated short name and rerun the job. If the convert table has not been created, the SARDBASE utility can be run with a CONVERT TABLE statement to build a table of long identifier names that require short identifier names.
Reason:
The specified distribution identifier name is too long, and a short name is not supplied in the convert table referenced by the SARCTAB DD statement. The conversion process terminates.
Action:
Add a control statement to the )DIST section of the SARCTAB DD statement identifying the specified distribution identifier and its associated short name and rerun the job. If the convert table has not been created, the SARDBASE utility can be run with a CONVERT TABLE statement to build a table of long identifier names that require short identifier names.
Reason:
The specified distribution mask name is too long, and a short name is not supplied in the convert table referenced by the SARCTAB DD statement. The conversion process terminates.
Action:
Add a control statement to the )DISTMASK section of the SARCTAB DD statement identifying the specified distribution mask and its associated short name and rerun the job. If the convert table has not been created, the SARDBASE utility can be run with a CONVERT TABLE statement to build a table of long identifier names that require short identifier names.
Reason:
The specified logical view identifier name is too long, and a short name is not supplied in the convert table referenced by the SARCTAB DD statement. The conversion process terminates.
Action:
Add a control statement to the )VIEW section of the SARCTAB DD statement identifying the specified logical view identifier and its associated short name and rerun the job. If the convert table has not been created, the SARDBASE utility can be run with a CONVERT TABLE statement to build a table of long identifier names that require short identifier names.
Reason:
The specified note name is too long, and a short name is not supplied in the convert table referenced by the SARCTAB DD statement. The conversion process terminates.
Action:
Add a control statement to the )NOTE section of the SARCTAB DD statement identifying the specified note name and its associated short name and rerun the job. If the convert table has not been created, the SARDBASE utility can be run with a CONVERT TABLE statement to build a table of long identifier names that require short identifier names.
Reason:
The specified logical view definition contained search criteria and possible relative references to the search criteria that is dropped during conversion.
Action:
Review the logical view definition to determine that index values are extracted from the correct location of a page.
Reason:
A corrupted sysout Description Record exists in a CA View database which is being versioned to a later release.
Action:
The sysout Id is identified in the message, the corrupted record is skipped, and a return code of 4 is set by the SARBASE/VERSION Function. The record can be redefined in the database after the versioning function is complete.
Note: For more information about online specifications, see the chapter "System Administration: Defining Online Specifications" in the User Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|