Reason:
The logical record length (LRECL) of the data set pointed to by the SARPATAB DD Statement in the Archival Task (SARSTC) procedure exceeds 256 characters. The Archival Task abnormally terminates with a U1012 abend code.
Action:
Re-allocate the data set with a logical record length (LRECL) of 256 characters or less and restart the Archival Task.
Reason:
The keyword KW is used in the ERO table but is not supported at the level of the current database.
Action:
Use a database where the keyword is supported or remove the conflicting keyword from the ERO table.
Reason:
When only verifying an ERO table using the TABLE parameter in SARVERO, the REGDAYS keyword cannot be verified.
Action:
Run SARVERO simulation without TABLE parameter to simulate a backup using the REGDAYS keyword.
Reason:
There is not enough space in the database to perform the archival.
Action:
Reply with either an R to reattempt archival or a T to terminate:
This message number represents one of the following:
Reason:
Each unique report id can have up to 65,535 copies per database generation. A 'generation' being the time between Full Backup Cycles. Each unique report Id in a generation is assigned a sequential number from 1 to 65,535. After 65,535, the sequence number will wrap back to zero and date selection problems will occur. This message gives the user a chance to run a backup cycle so this number can be reset to one.
The second format of SARPPS25 is displayed if a response other than 'R' or 'T' is given to the original message.
Action:
Reply with either an R after a backup cycle has been started or a T to terminate. The SARPPS25 message can be reissued after replying T and re-starting the Xerox XPPS FSS Collector.
Reason:
The PC transmittal queue is full for the user.
Action:
Have the user transmit their queue and clear the entries.
Reason:
The specified destination must be of the format PC user ID.
Action:
Correct the destination.
Reason:
The user ID specified in the destination is not defined to CA View.
Action:
Correct the destination or define the user ID to CA View.
Reason:
Your print request specified the synonym for a VTAM Print Option device. The DEFine DEVice specification for that synonym specified that the indicated special device driver was to be used when doing the printing, but that device driver cannot be found.
Action:
Either correct the device driver specification on the VTAM DEVICE ATTRIBUTE PANEL of the DEFine DEVice facility, or make the device driver accessible by putting it in the CA View LOADLIB, or in a library concatenated to CA View LOADLIB.
Reason:
Your print request specified the synonym for a real device. The DEFine DEVice specification for that synonym specified that the indicated special user exit was to be used when doing the printing, but that user exit cannot be found.
Action:
Either correct the device driver specification on the appropriate DEVICE ATTRIBUTE PANEL of the DEFine DEVice facility, or provide access to the device user exit by putting it in the CA View LOADLIB, or in a library concatenated to the CA View LOADLIB.
Reason:
An internal logic error occurred. Online retrieval or batch retrieval terminates with a U1015 abend.
Action:
Contact CA Technical Support.
Reason:
Your print request specified the synonym for a VTAM Print Option device. The DEFine DEVice specification for that synonym specified to use the indicated special device driver for printing, but that device driver cannot be found.
Action:
Either correct the device driver specification on the VTAM Device Attribute panel of the DEFine DEVice facility, or make the device driver accessible by putting it in the CA View LOADLIB or in a library concatenated to the CA View LOADLIB.
Reason:
Your print request specified the synonym for a real device. The DEFine DEVice specification for that synonym specified to use the indicated special user exit for printing, but that user exit cannot be found.
Action:
Either correct the device driver specification on the Device Attribute panel of the DEFine DEVice facility, or provide access to the device user exit by putting it in the CA View LOADLIB or in a library concatenated to the CA View LOADLIB.
Reason:
Index data cannot be printed using the external print interface or queued to a PC user.
Action:
Specify a different destination and resubmit the print request.
Reason:
An internal logic error occurred. Online retrieval or batch retrieval terminates with a U1015 abend.
Action:
Contact CA Technical Support.
Reason:
The first control statement must be a FILESEQ statement and the keyword must start in column 1.
Action:
Correct the control statement and rerun the utility.
Reason:
The second and subsequent control statements must be DATA SET NAME/VOLSER control statement. Start the data set name in column 1 and terminate with either a space or the comma of the optional [,VOLSER] volume serial number.
Action:
Correct the control statement and rerun the utility.
Reason:
A failure writing the recovery data to the recovery file has occurred.
Action:
Delete the file pointed to by the SARRECV DD Statement, allocate a new empty file, and rerun the SARRCOV Utility.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates the start of the restore process.
Action:
None. This is an informational message.
Reason:
The database that is specified by the PARM parameter of the execution JCL cannot be opened. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
Verify that the correct database prefix is specified in the PARM parameter of the execution JCL. Otherwise, see the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while opening the master index. The restore process cannot access this master index data, and is terminated. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
Ensure that the restore process by using the RESTORE control statement of the SARDBASE utility completes successfully. See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while reading the master control record. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
Ensure that the restore process by using the RESTORE control statement of the SARDBASE utility completes successfully. See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified panel to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified panel to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified panel to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified SYSOUT to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified SYSOUT to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified SYSOUT to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while reading an index record from the master index of the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
The sort phase of the restore process ends with the specified nonzero return code.
Action:
The nonzero return code from the sort phase can be caused by a critical error as indicated by a previous SARRSPxx message, a missing SYSOUT DD statement (return code 20), or a sort error as indicated in the sort message data set. Take the appropriate action, and then resubmit the job.
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:
Either STEPLIB to the correct load modules or convert the database to the correct release level.
Note: For more information, see VERSION in the SARDBASE Control Statements section of the chapter "Database Utilities" in the Reference Guide.
Reason:
The unload tape that is referenced by the SARLOAD DD statement is not produced by a compatible release level of the SARDBASE utility.
Action:
Remove the SARLOAD DD statement from the restore execution JCL, or use an unload tape from a compatible release level of the SARDBASE utility.
Reason:
The unload tape that is referenced by the SARLOAD DD statement contains unrecognizable data.
Action:
Remove the SARLOAD DD statement from the restore execution JCL, or specify a different unload tape.
Reason:
The specified SYSOUT group cannot be restored because the SYSOUT does not reside on any backup tape.
Action:
None. The status of the SYSOUT group remains unchanged, and processing continues.
Reason:
The specified SYSOUT group cannot be restored due to problems with the related backup tape. This message accompanies a SARTPOxx message indicating the nature of the error.
Action:
None. The SYSOUT group is removed from disk status and processing continues. For future use of the SYSOUT group, recover the backup tape.
Note: For more information, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The specified SYSOUT group cannot be restored because the SYSOUT cannot be found on the related backup tape. This message accompanies a SARTPOxx message indicating the nature of the error.
Action:
None. The SYSOUT group is removed from disk status and processing continues. For future use of the SYSOUT group, recover the backup tape.
Note: For more information, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The specified SYSOUT group cannot be restored due to problems with the related backup tape and therefore, is being removed from disk status.
Action:
None. The SYSOUT group is removed from disk status and processing continues. For future use of the SYSOUT group, recover the backup tape.
Note: For more information, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
An error occurs while attempting to restore the specified page layout RESOURCE to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified page layout RESOURCE to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified page layout RESOURCE to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
The specified page layout RESOURCE cannot be restored because the RESOURCE does not reside on any backup tape.
Action:
None. The status of the RESOURCE remains unchanged, and processing continues.
Reason:
The specified page layout RESOURCE cannot be restored due to problems with the related backup tape. This message accompanies a SARTPOxx message indicating the nature of the error.
Action:
None. The RESOURCE is removed from disk status and processing continues. For future use of the RESOURCE, recover the backup tape.
Note: For more information, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The specified page layout RESOURCE cannot be restored because the SYSOUT cannot be found on the related backup tape. This message accompanies a SARTPOxx message indicating the nature of the error.
Action:
None. The RESOURCE is removed from disk status and processing continues. For future use of the RESOURCE, recover the backup tape.
Note: For more information about backing up, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The specified page layout RESOURCE cannot be restored due to problems with the related backup tape and therefore, is being removed from disk status.
Action:
None. The RESOURCE is removed from disk status and processing continues. For future use of the RESOURCE, recover the backup tape.
Note: For more information about restore, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The specified panel has been successfully restored from the unload tape.
Action:
None. This is an informational message.
Reason:
The specified SYSOUT group has been successfully restored from the unload tape and now resides on disk media.
Action:
None. This is an informational message.
Reason:
The specified SYSOUT group has been successfully restored from the backup tape and now resides on disk media.
Action:
None. This is an informational message.
Reason:
This message becomes the data for the SYSOUT attempted to be restored.
Action:
None. If a tape that contains the SYSOUT can be located, the SYSOUT can be reloaded using CA View utilities.
Reason:
The specified page layout RESOURCE has been successfully restored from the unload tape and now resides on disk media.
Action:
None. This is an informational message.
Reason:
The specified page layout RESOURCE has been successfully restored from the backup tape and now resides on disk media.
Action:
None. This is an informational message.
Reason:
An error occurs while attempting to restore the specified model banner page member to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified model banner page member to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
An error occurs while attempting to restore the specified model banner page member to the database. This message accompanies a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
The specified model banner page member has been successfully restored from the unload tape.
Action:
None. This is an informational message.
Reason:
This message indicates that the restore process is finished (whether successfully or not).
Action:
None. This is an informational message.
Reason:
The parameter list that is passed to SARSAM does not contain a valid function name.
Action:
Correct the parameter list or use the SARSAM Macros which generates the correct parameter list values. The valid functions are:
Reason:
The database exists but has never been initialized.
Action:
Use the SARINIT Initialization Utility to initialize the database and rerun the SARSAM application.
Reason:
The CA View FSS (Functional Subsystem) or CA View FSA (Functional Subsystem Application) has abended. The system or user abend code is provided.
Action:
Consult the MVS System Messages manual to determine the reason for the abend. If you still cannot determine the problem, contact CA Technical Support.
Reason:
A CA View program has terminated, and a dump was generated. In this message, blk specifies the control block 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 Customer Support. Restart whatever program was terminated. For assistance, contact Technical Support at http://ca.com/support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
|
Copyright © 2013 CA.
All rights reserved.
|
|