Reason:
The distribution id is not within the requested page range for printing.
Action:
Adjust the Deliver definition for this report so the pages are distributed to the distribution id listed or change the index to include pages defined for this distribution id. If no pages were expected to be printed to this distribution id, this is a notification and no action is required.
Note: When using the external print interface, no destination is available. The message appears without the dest as follows:
Reason:
The SYSOUT group is successfully queued for PC transmittal.
Action:
None. This is an informational message.
Reason:
The PC transmittal queue for the user is full. The SYSOUT group cannot be added to the queue.
Action:
Transmit and clear the queue.
Reason:
The destination is not of the form PC user ID.
Action:
Correct the destination.
Reason:
The PC user is not defined to CA View.
Action:
Correct the user ID in the destination.
Reason:
The DEFine DEVice information requests that output be processed by an optional device driver called xxxxxxxx, but it cannot be found.
Action:
Either make the device driver available (perhaps through LINKLIST or STEPLIB), or remove it from the DEFine DEVice.
Reason:
Your print request exceeded the maximum number of lines that are permitted during a batch or on-line print request. The reprint line limit could have been defined in the VTAM Printer Device Definition, the CA Spool Device Definition, or the OUTLIM Initialization Parameter.
Action:
Do one of the following options:
Reason:
This destination has no problems printing, but an error occurs while printing to another destination in your reprint request.
Action:
Do one of the following actions:
Reason:
The DEFine DEVice record is invalid. A record that is not completely defined can cause this.
Action:
Correct the DEFine DEVice record and retry.
Reason:
You are attempting to print more than one SYSOUT or report on the same VTAM printer at the same time. This cannot be done.
Action:
Either use more than one printer or make more than one print request to the printer in question.
Reason:
Your print request exceeds the maximum number of lines that are permitted during CA Spool print processing.
Action:
Do one of the following options:
Reason:
The DEFine DEVice information requests that the output be processed by an optional device-specific user exit called xxxxxxxx, but it cannot be found.
Action:
Either make the device driver available (perhaps through LINKLIST or STEPLIB), or remove it from the DEFine DEVice.
Reason:
The external print request was successfully queued for processing.
Action:
None. This is an informational message.
Reason:
An internal logic error has occurred. Online retrieval or batch retrieval terminates with a U1111 abend.
Action:
Contact CA Technical Support.
Reason:
A dynamic allocation request for allocating the archival copy for the automatic report archival feature failed. The hexadecimal error and information codes are provided. Execution continues without creating the archival copy of the SYSOUT—no archival of the SYSOUT is done.
Action:
Correct the parameter information for the automatic report archival feature.
Reason:
The open request failed for the archival copy for the automatic report archival feature.
Action:
Correct the problem with open.
Reason:
Initialization has completed for the archival task.
Action:
None. This is an informational message.
Reason:
A subsystem request failed. The hexadecimal return code is provided.
Note: Conditions that cause error message SARSTC01 in turn cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct-To-Tape function and a backup cycle function to also terminate normally. The Direct-To-Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide to either terminate the backup cycle immediately or wait until the completion of the backup cycle.
Responding "Wait" to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
The job name of the SYSOUT passed to CA View for archival is the same as the archival started task, and the producing ddname is SYSnnn. To prevent a potential archival-print loop, CA View deletes the SYSOUT without ever archiving it.
Action:
Correct or specify the NEWCLSL, NEWDEST, or NEWFORM options to prevent the archival of SYSOUT automatically printing the archival started task.
Reason:
The named sub-task (Backup, Archive, or Comm) has terminated with a 'nnnn' return code.
Action:
Determine the required action from other accompanying messages which can indicate a component failure.
Reason:
A SARACT DD statement was present in the job stream, but the data set failed to open successfully.
Action:
Verify that the data set is correct, or remove the DD statement to disable accounting.
Note: This message number represents one of these messages.
Reason:
The data set specified by the SARACT DD statement has an invalid logical record length, an invalid block size, or is not a CA View accounting file.
Action:
Verify that the data set is correct, or remove the DD statement to disable accounting.
Reason:
An ESTAE failed. The hexadecimal return code is provided.
Action:
Contact your systems programmer.
Reason:
The modify command for the archival started task is invalid and ignored.
Action:
Correct and reissue the modify command.
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 attributes. If you want, make appropriate changes and resubmit the print request.
Reason:
Another archival task with the same database is already executing.
Action:
Correct the problem.
Reason:
The program load modules and the database are not 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 master index indicates that the archival task is already active on system xxxx. This message can also be issued if the archival task abended or the system crashed the last time the archival task was active.
Action:
Verify whether the archival task is active on the specified system. If it is, reply N to terminate this task; if not, reply Y to continue.
Important! Never run the archival task for the same index file on more than one system at the same time; this can destroy the master index.
Reason:
CA View is processing the specified SYSOUT data set.
Action:
None. This is an informational message.
Reason:
The maximum number of lines that can be archived for a SYSOUT data set (defined by the MAXLINES initialization parameter) has been exceeded. If BYPASS has been coded as a subparameter of MAXLINES, all remaining SYSOUTs for the data set are deleted without archival. If BYPASS is not coded, the records are passed to SARSTCUX for processing.
Action:
None. This is an informational message.
Reason:
The database is out of space.
The second format of SARSTC24 is displayed if a response other than ‘R’, 'B', ‘N’, ‘C’, or 'T' is given to the original message.
Action:
Your recovery options are as follows:
Reason:
Each unique reportid can have up to 65,535 copies per database generation. A generation is the time between Full Backup Cycles. Each unique reportid in a generation is assigned sequential numbers from 1 to 65,535. After 65,535, the sequence number would wrap back to zero and date selection problems would 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 SARSTC25 is displayed if a response other than 'B' or 'T' is given to the original message.
Action:
Reply with either a B to run a backup cycle or a T to terminate. The SARSTC25 message can be reissued after replying T and re-starting the archival (SARSTC) task.
Reason:
This message is informational. The message informs a user that CA View is operative, though JES has not had any outputs in the queue in the predefined five-minute time spans.
Action:
None. This message is informational.
Reason:
An I/O error occurs while writing out the index data for the SYSOUT group. Any index data that is already written is deleted.
Action:
Correct the error with the database.
Reason:
CA View initialization failed because the program authorization using the Authorized Program Facility (APF) is required.
Action:
APF authorize the libraries containing the CA View load modules or move the load modules to an authorized library.
Reason:
The SARSTC archival task has encountered an error while writing a duplex copy of a SYSOUT to the forward recovery data set.
Action:
Archival continues without forward recovery capture. Check the RCVPRIM, RCVSEC, RCVSPACE, and RCVUNIT initialization parameters for values that could cause problems allocating, reading, or writing to the forward recovery data set.
***************************************************
SARSTC30 *
*
SARSTC30 * SARSTC has abended with code xxxx *
SARSTC30 * Sysoutid=xxxxxxxx
Jobname=xxxxxxxx Jobid=xxxxxxxx
*
*****************************************************
Reason:
The CA View started task 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:
The PC transmittal queue is full for the user. The SYSOUT group is not queued for transmittal to the PC.
Action:
Have the user transmit the 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 exceeded the maximum number of lines that are permitted during VTAM print processing. This message can also occur on non-VTAM printers as an indication that an error occurred while printing on both devices simultaneously.
Action:
Increase the maximum permitted for this device by using the DEFine DEVice facility or increase the maximum permitted for all devices by using SARINIT parameter VPRTMAXO.
Reason:
Your print request exceeded the maximum number of lines that are permitted during online CA Spool print processing. This message can also occur on non-VTAM printers as an indication that an error occurred while printing on both devices simultaneously.
Action:
Increase the maximum permitted for this device by using the DEFine DEVice facility or increase the maximum permitted for CA Spool devices by using SARINIT parameter CMAMAX.
Reason:
The device record is invalid. A record that was not completely defined could cause this.
Action:
Correct the device record by using the DEFine DEVice facility.
Reason:
An unknown return code is detected in response to a print request.
Action:
For assistance, contact Technical Support at http://ca.com/support.
|
Copyright © 2013 CA.
All rights reserved.
|
|