Reason:
This message indicates insufficient authority to write SMF records.
Action:
Add the SARSMFT module to the TSO authorization table, and ensure that it is located in an authorized library.
Reason:
The report cannot be accessed from tape because the Expanded Access Server (EAS) task is not active on the same system as DRAS.
Action:
The EAS task must be started and running on the same system as DRAS. After the task has been started, the report can be accessed from DRAS.
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:
Dynamic allocation failed for allocating the print data set to SYSOUT. The hexadecimal error and information codes are provided.
Action:
Correct the problem, and then resubmit the job.
Reason:
The attempt to dynamically create an OUTPUT statement failed. The return and reason codes are provided. For an explanation of the return and reason codes, refer to the operating system macro IEFDORC.
Action:
The SYSOUT is printed without OUTPUT statement attributes. If you want, make appropriate changes and resubmit the print request.
Reason:
Distribution identifier has not been specified for the desired report.
Action:
Specify a distribution identifier for the report or enter the keyword SAR and print through CA View directly.
Reason:
Problems are encountered with the CA Deliver database interface, or problems are encountered printing banner pages for reports in CA Deliver. Processing is terminated.
Action:
Respond to the additional message that precedes this message.
Reason:
The SYSOUT group cannot be found on the tape backup.
Action:
None. The SYSOUT group is not available on tape.
Reason:
The SYSOUT group that is located on tape is not the same as referenced in the master index.
Action:
Use the SARTCP utility to map and correct the tape.
Reason:
The backup tape cannot be found in the index file. This is normally caused by a backup cycle deleting the tape between the time the job was submitted and the time it was executed.
Action:
None. The SYSOUT group is no longer available.
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:
A permanent I/O error occurs while attempting to position the archival tape to retrieve the SYSOUT group.
Action:
Resubmit the job. If the I/O error occurs again, then the desired SYSOUT group can no longer be printed.
Reason:
The requested function cannot be performed because the specified SYSOUT group is open for output.
Action:
If the open condition is valid (for example, the SYSOUT group is still being archived or is being loaded to disk), wait for the SYSOUT group to be closed and rerun the job.
If the open condition is invalid (for example, there was a system crash or abend while the SYSOUT group was open leaving the SYSOUT group in an open status), use the CLEAN operator command to remove the open status. Two backup cycles and the duration of four hours must have elapsed before the open status is removed.
Reason:
A permanent I/O error occurs while reading the SYSOUT from tape. The print function is terminated.
Action:
Use the SARTCP utility to map and correct the tape.
Reason:
The logical view definition for the report is not found.
Action:
Respecify the print request with a new logical view.
Reason:
A subprogram returned a message that is being repeated here.
Action:
The action varies depending on the message text displayed.
Reason:
The resource group that is identified by a group control record is not found in the CA View database.
Action:
Use the SARTCP utility to map and locate the resource group. Use the SARTDR utility to reload the resource group back into the CA View database.
|
Copyright © 2013 CA.
All rights reserved.
|
|