Reason:
The report is printed for the DIST ID indicated on the printer specified.
Action:
None. This message is informational.
Reason:
The report cannot be printed for the DIST ID indicated on the printer specified because of another error in the print request.
Action:
Correct the error as indicated in the associated error message and try the print request again.
Reason:
A subprogram returned a message that is being repeated here. The print request was to print the DISTID indicated on the printer specified.
Action:
The action varies depending on the message text displayed.
Reason:
The SELECT keyword and the PAGE and/or RECORD keywords are mutually exclusive.
Action:
Either remove the SELECT parameter or remove the PAGE and/or RECORD parameters from the control statement, then resubmit the print request.
Reason:
The SELECT keyword was specified but the SYSOUT group resides on tape.
Action:
Either remove the SELECT keyword to print the entire SYSOUT group, or temporarily reload the SYSOUT group to the database so that its index is available for printing.
Reason:
The SELECT keyword was specified and either the CA View keyword was omitted or specified for an invalid logical view.
Action:
Correct the parameter specification, and then resubmit the print request.
Reason:
An error occurred attempting to obtain the index for the SYSOUT group.
Action:
Either remove the SELECT keyword to print the entire SYSOUT group or re-archive the SYSOUT group to create an index.
Reason:
The page separation definition in the logical view either did not exist when the SYSOUT group was archived or was changed subsequently.
Action:
Either remove the SELECT keyword to print the entire SYSOUT group, re-index the SYSOUT group, or re-archive the SYSOUT group to create an index.
Reason:
The selection text does not exist in the index for the logical view of the SYSOUT group. An incorrect spelling on the SELECT keyword normally causes this, or the page separation criteria is never defined for the SYSOUT group.
Action:
Either change the SELECT parameter to reference a different index specification or remove the SELECT keyword to print the entire SYSOUT group.
Reason:
The SARDSTUX user exit did not allow the report to be printed to its respective destination.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The specified view does not exist in the master index.
Action:
Verify the existence of the view. If the view number was specified incorrectly, change the parameter specification, and then resubmit the print request.
Reason:
The page index value specified on the SELECT keyword of the print request is not found for the requested SYSOUT group.
Action:
Verify that the correct page index value, SYSOUT group, and view are being specified. Otherwise, remove the SELECT parameter and print the entire SYSOUT group.
Reason:
An attempt is being made to print a SYSOUT group from tape, but certain vital backup tape control information cannot be found.
Action:
Normally, tape control information is retained as long as there are reports that reference it. The tape control record (TCR) can be reinstated by re-adding the tape back into the database with the TADD facility of the SARTDR utility.
Important! This condition could identify a serious problem with the database or problems with the supporting code. Report the problem to CA Technical Support.
Reason:
An error occurred opening a report on optical disk, or on tape accessed through an EAS tape server.
Action:
Browse the report online to see any error messages from the DSK2 driver or EAS tape server interface routine.
Reason:
The SARSECUX security user exit or external security has denied access to the logical view of the report.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The SARSECUX security user exit or external security has denied access to the specified index of the report.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The ID keyword is not specified on the DEFFILT or LISTFILT control statement.
Action:
Add the appropriate keyword specification to the define or list request, and then resubmit the request.
Reason:
This message identifies the profile attributes of the Filter definition after processing the DEFFILT request.
Action:
None. This message is informational.
Reason:
The Filter attributes are successfully added to the CA View database. This message is accompanied by the SARBCF02 message that details the View definition information.
Action:
None. This message is informational.
Reason:
The Filter attributes for an existing definition were successfully changed. This message is accompanied by the SARBCF02 message, which details the Filter definition information.
Action:
None. This message is informational.
Reason:
An error occurred while reading or writing data from the CA View database. This message is to be accompanied by a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
The listing of Filter is successfully written to the REPORT DD statement.
Action:
None. This message is informational.
Reason:
The REPORT JCL DD statement was not provided and is required for the control statement.
Action:
Specify the REPORT JCL DD statement, and then resubmit the job.
Reason:
Listing a Filter definition requires MASTER authority.
Action:
Request that the job be run by a user with master authority.
Reason:
The requested filter does not exist in the master index. This is typically caused by an incorrect specification of the ID parameter and/or the USER parameter, or another user or job already deleted the filter by using the online retrieval facility or batch retrieval facility (SARBCH).
Action:
Verify the existence of the filter. If the filter (ID parameter) or user identifier (USER parameter) was specified incorrectly, change the parameter specification and resubmit the request.
Reason:
Filter definition record exceeds maximum length.
Action:
Reduce FILTER definitions on the DEFFILT control statement, and then resubmit the define request.
Reason:
Filter definition contains more than 255 entries.
Action:
Reduce the number of FILTER entries on the DEFFILT control statement, and then resubmit the define request.
Reason:
The DEFFILT statement keyword xxxxxxx subparameter number n is not valid.
Action:
Correct the keyword and then resubmit the define request.
Reason:
Modifying a Filter definition requires MASTER authority.
Action:
Request that the job be run by a user with master authority.
Reason:
The user ID extracted by the SARUSBUX does not have sufficient authority (master authority) to list filters defined in the database. The user ID that requires authority is indicated in a previous (SARBCH05) message.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The listing of Devices is successfully written to the REPORT DD statement.
Action:
None. This message is informational.
Reason:
The Device is successfully added to the CA View database. This message is accompanied by the SARBCG15 message that details the Device definition information.
Action:
None. This message is informational.
Reason:
The Device attributes for an existing definition were successfully changed. This message is accompanied by the SARBCG15 message, which details the Device definition information.
Action:
None. This message is informational.
Reason:
An error occurred while reading or writing data from the CA View database. This message is to be accompanied by a SARDBIxx message indicating the nature of the error.
Action:
See the explanation and action of the SARDBIxx message for resolution.
Reason:
The ID keyword or TYPE keyword is not specified on the DEFDEV control statement.
Action:
Add the appropriate keyword specification to the DEFDEV request, and then resubmit the request.
Reason:
The CNODE, PUSERID, EXTPRT, or VNODE parameter is required for specified DEFDEV TYPE.
Action:
Add the missing keyword parameter to the DEFDEV request, and then resubmit the request.
Reason:
The specified DEFDEV CEXIT or VEXIT device-specific user exit did not start with “SAR$” or is not found in STEPLIB.
Action:
Correct or remove the DEFDEV CEXIT or VEXIT parameter, and then resubmit the request.
Reason:
The REPORT JCL DD statement was not provided and is required for the control statement.
Action:
Specify the REPORT JCL DD statement, and then resubmit the job.
Reason:
The requested LISTDEV device does not exist in the master index. This is typically caused by an incorrect specification of the ID, USER, or TYPE parameters.
Action:
Verify the existence of the device. If the LISTDEV ID, USER or TYPE parameter was specified incorrectly, change the parameter specification and resubmit the request.
Reason:
The user ID extracted by the SARUSBUX does not have sufficient authority (master authority) to list devices, or add or modify a device to the database. The user ID that requires authority is indicated in a previous (SARBCH05) message.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The keyword parameter xxxxxxxx is not supported for the specified DEFDEV TYPE.
Action:
Remove the unsupported keyword parameter from the DEFDEV request, and then resubmit the request.
Reason:
The keyword parameter xxxxxxxx value is not valid.
Action:
Correct the keyword parameter value on the DEFDEV request, and then resubmit the request.
Reason:
The following DEFDEV keyword parameters are mutually exclusive:
Action:
Remove one of the mutually exclusive parameters on the DEFDEV request, and then resubmit the request.
Reason:
This message identifies the profile attributes of the device definition after processing the DEFDEVT request.
Action:
None. This message is informational.
Reason:
The specified DEFDEV VDRIVER driver did not start with “SARVPS” or is not found in STEPLIB.
Action:
Correct or remove the DEFDEV VDRIVER parameter, and then resubmit the request.
Reason:
The device type found in device xxxxxxxx was invalid.
Action:
Correct the device type using Online DEF DEV or SARBCH DEFDEV.
Reason:
The SARATHUX security user exit did not allow the job or user access to the database.
Action:
Consult with your security administrator or system programming group to determine the reason why the authorization was not provided.
Reason:
A slash (/), denoting a new control statement, is expected in column 1 of the control statement but is not found.
Action:
Review syntax of control statement, insert a slash (/) before the function name in column 1 of the control statement, and then resubmit the job.
Reason:
The specified function name (name that follows the slash) contains invalid characters, contains too many characters, or is not a valid batch retrieval function.
Note: The function name must immediately follow a slash (/) that is coded in column 1 of the control statement. Also, control statements that continue onto multiple control statements are not prefixed with the slash.
Action:
Review the spelling of function name and the syntax of the control statement, correct the control statement specification, and then resubmit the job.
Reason:
The user ID determination exit (SARUSBUX) provided successful logon for the specified user ID to the specified database.
Action:
None. User ID logon is performed during initial access to the database.
Reason:
The user ID determination exit (SARUSBUX) did not allow logon for the specified user ID to the specified database.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The specified keyword name contains invalid characters, contains too many characters, or is not a valid name.
Action:
Review syntax of control statement and spelling of the keyword name, correct the parameter specification, and then resubmit the job.
Reason:
The parameter data for the specified keyword contains invalid characters or is not an acceptable value.
Action:
Review syntax of control statement, correct the parameter specification, and then resubmit the job.
Reason:
The parameter data for the specified keyword contains a quoted string that is not terminated by an ending quote.
Action:
Review syntax of control statement, correct the parameter specification, and then resubmit the job.
Reason:
The parameter data for the specified keyword contains an incorrect number of parentheses. For every right parenthesis, there must be a matching left parenthesis.
Action:
Review syntax of control statement, correct the parameter specification, and then resubmit the job.
Reason:
The parameter data for the specified keyword contains too many characters.
Action:
Review syntax of control statement, correct the parameter specification, and then resubmit the job.
Reason:
The parameter data for the specified keyword contains too many values.
Action:
Review syntax of control statement, correct the parameter specification, and then resubmit the job.
Reason:
The program load modules and the database are not at the same version 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 version level (new versions of 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 SARSECUX security user exit or external security did not allow access to the SYSOUT group.
Action:
Consult with your security administrator or system-programming group to determine the reason why the authorization was not provided.
Reason:
The ID parameter is incorrectly specified without a SYSOUT identifier.
Action:
Change the ID parameter to include the SYSOUT identifier that is to be re‑indexed, and then resubmit the index request.
Reason:
The requested SYSOUT group does not exist in the master index. This is normally caused by a misspelled SYSOUT identifier, a backup cycle deleting the SYSOUT group before completion of the index process, or the manual deletion of the SYSOUT group using the online retrieval facility or batch retrieval facility (SARBCH).
Action:
Verify the existence of the SYSOUT group. If the SYSOUT identifier (ID), generation (GEN), and/or sequence number (SEQ) was specified incorrectly, change the parameter specification, and then resubmit the index request.
Reason:
Indexing a report requires the report and INDEX to be replaced on CENTERA storage. Since this copy of the report is under REGDAYS retention, it cannot be deleted or changed.
Action:
Report cannot be Indexed or re-indexed.
Reason:
The SARSECUX security user exit or external security did not allow access to the SYSOUT group.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The ID parameter is incorrectly specified without a SYSOUT identifier and is required on the control statement.
Action:
Change the ID parameter to include the SYSOUT identifier that is to be set to or removed from permanent status, then resubmit the PERM request.
Reason:
The DISK, TAPE, and/or DELETE keywords are mutually exclusive and cannot be specified on the same control statement.
Action:
Change control statement to specify DISK, TAPE, or DELETE, and then resubmit PERM request.
Reason:
The SYSOUT group is successfully set to a permanent on disk status (location of PERM). The long-term status of the SYSOUT group depends on the setting of the Expanded Retention Option initialization parameters and table parameters.
Action:
None. This message is informational.
Reason:
The SYSOUT group is successfully set to permanent on tape status (location of PDSK, PTMP, or PTAP). The long-term status of the SYSOUT group depends on the setting of the Expanded Retention Option initialization parameters and table parameters.
Action:
None. This message is informational.
Reason:
The SYSOUT group was successfully removed from permanent status. The disk and tape retention of the SYSOUT group depends on the setting of the NGEND and NGENT initialization parameters.
Action:
None. This message is informational.
Reason:
The SYSOUT group resides on secondary disk storage and must remain in permanent status.
Action:
None. Permanent status cannot be deleted.
Reason:
The requested SYSOUT group does not exist in the master index. This is normally caused by a misspelled SYSOUT identifier, a backup cycle deleting the SYSOUT group before completion of the PERM process, or the manual deletion of the SYSOUT group by using the online retrieval facility or batch retrieval facility (SARBCH).
Action:
Verify the existence of the SYSOUT group. If the SYSOUT identifier (ID), generation (GEN), and/or sequence number (SEQ) was specified incorrectly, change the parameter specifications, and then resubmit the PERM request.
Reason:
The SYSOUT group is not set to or removed from permanent status because the SYSOUT group is in open status. The SYSOUT group can be in open status due to a currently pending temporary load operation, a pending migration operation, or initial creation.
Action:
Wait until the status of the SYSOUT group has changed from open status, then resubmit PERM request. If the open condition is invalid (for example, a system crash or an abend occurred while the SYSOUT group was in open status and being processed), use the CLEAN operator command to remove the open status. Two backup cycles and the duration of 4 hours must have elapsed before the open status is removed.
Reason:
The SYSOUT group cannot be set to a permanent on disk status because the SYSOUT group does not reside on disk media.
Action:
Temporarily load SYSOUT group to the database, then resubmit PERM request.
Reason:
The SARSECUX security user exit or external security did not allow access to the SYSOUT group.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The ID parameter is incorrectly specified without a SYSOUT identifier and is required on the control statement.
Action:
Change the ID parameter to include the SYSOUT identifier that is to be loaded, then resubmit the load request.
Reason:
The JCL DD statement name specified in the DDNAME parameter was not provided.
Action:
Remove the DDNAME parameter or specify the respective JCL DD statement, and then resubmit the load request.
Reason:
The SYSOUT group is successfully loaded from tape to the database and resides in a temporary on disk status.
Action:
None. This message is informational.
Reason:
The SYSOUT group is successfully copied to the specified JCL DD statement.
Action:
None. This message is informational.
Reason:
The page index file for the requested SYSOUT group is successfully loaded from tape or secondary disk to the CA View database.
Action:
None. This message is informational.
Reason:
The requested SYSOUT group does not exist in the master index. This is normally caused by a misspelled SYSOUT identifier, a backup cycle deleting the SYSOUT group before completion of the load process, or the manual deletion of the SYSOUT group by using the online retrieval facility or batch retrieval facility (SARBCH).
Action:
Verify the existence of the SYSOUT group. If the SYSOUT identifier (ID), generation (GEN), and/or sequence number (SEQ) was specified incorrectly, change the parameter specification, and then resubmit the load request.
Reason:
The SYSOUT group is not loaded to the database because it already resides on disk.
Action:
Since the original intent of the load request has been satisfied, no further action is necessary. If the SYSOUT group was incorrectly loaded or is empty, the disk portion of the SYSOUT group can be deleted by using the online retrieval facility or batch retrieval facility, and the load request can be resubmitted.
Reason:
The SYSOUT group cannot be found on any tape backup.
Action:
None. The SYSOUT group is not available on tape.
Reason:
The SYSOUT group located on the backup tape is not the same as referenced in the master index.
Action:
Use the SARTCP utility to map and correct the backup tape.
Reason:
The backup tape cannot be found in the master index. This is normally caused by the backup cycle deleting the tape before completion of the load request.
Action:
None. The SYSOUT group is no longer available.
Reason:
Dynamic allocation failed for allocating the backup tape file. The hexadecimal error and information codes are provided.
Action:
Consult the online retrieval HELP facility for a description of the dynamic allocation error code. Take appropriate action to correct the allocation error, and then resubmit the load request.
Reason:
A permanent I/O error occurred attempting to position the archival tape to retrieve the SYSOUT group.
Action:
Resubmit the request. If the I/O error occurs again, use the SARTCP utility to map and correct the tape.
Reason:
The requested function cannot be performed because the specified SYSOUT group is open for output. The SYSOUT group can be in open status due to a currently pending temporary load operation, a pending migration operation, or initial creation.
Action:
Wait until the status of the SYSOUT group has changed from open status, then resubmit load request. If the open condition is invalid, that is, a system crash or an abend occurred while the SYSOUT group was in open status and being processed; 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 occurred attempting to read SYSOUT data from a backup tape.
Action:
Resubmit the load request. If the I/O error occurs again, use the SARTCP utility to map and correct the tape. Also, for recovery procedures, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The specified view does not exist in the master index.
Action:
Verify the existence of the view. If the view number was specified incorrectly, change the parameter specification, and then resubmit the load request.
Reason:
A load request was issued specifically to load the page index file for the requested SYSOUT group from tape or secondary disk to the CA View database, but the page index file already resides on the disk.
Action:
Since the page index file already resides on disk, the load request is not necessary. If something is wrong with the page index file on the CA View database, the page index file can be deleted and then reloaded.
Reason:
A load request was issued specifically to load the page index file for the requested SYSOUT group from tape or secondary disk to the CA View database, but no page index file was generated for the SYSOUT group.
Action:
Re‑index or re-archive the report to generate a page index file for the SYSOUT group.
Reason:
The SARSECUX security user exit or external security did not allow access to the specified SYSOUT group.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The ID parameter is incorrectly specified without a SYSOUT identifier and is required on the control statement.
Action:
Change the ID parameter to include the SYSOUT identifier that is to be printed, then resubmit the print request.
Reason:
A non-zero return code is encountered from a Centera API function call. The error code and message is provided. These errors normally indicate network, server, client, or Z/OS errors.
Action:
Centera error messages include an error class to identity where the error occurred.
The error class determines the action:
Reason:
Internal error indicating that the incorrect request is issued during the migration of data to Centera.
Action:
Contact CA Support.
Reason:
The backup cycle or migration task terminated migration of a report. This message is issued when the CA View started task or migration task is brought down while migrating a report to Centera. The report that was being migrated is again migrated the next time the CA View started task or migration task is started.
Action:
None.
Reason:
The JCL DD statement name specified in the DDNAME parameter was not provided.
Action:
Either remove the DDNAME parameter or specify the respective DDNAME.
Reason:
The SYSOUT group was successfully queued to print.
Action:
None. This message is informational.
Reason:
The SYSOUT group is successfully copied to the specified JCL DD statement.
Action:
None. This message is informational.
Reason:
The CA Deliver report is successfully queued for download to a PC. The download process is complete at the user's discretion from the online retrieval interface.
Action:
None. This message is informational.
Reason:
The requested SYSOUT group does not exist in the master index. This is normally caused by a misspelled SYSOUT identifier, a backup cycle deleting the SYSOUT group before the completion of the print process, or the manual deletion of the SYSOUT group by using the online retrieval facility or batch retrieval facility (SARBCH).
Action:
Verify the existence of the SYSOUT group. If the SYSOUT identifier (ID), generation (GEN), and/or sequence number (SEQ) was specified incorrectly. Change the parameter specification, and then resubmit the print request.
Reason:
The SYSOUT group is not loaded to the database because it already resides on disk.
Action:
Since the original intent of the load request has been satisfied, no further action is necessary. If the SYSOUT group was incorrectly loaded or is empty, the disk portion the SYSOUT group can be deleted by using the online retrieval facility or batch retrieval facility, and the load request can be resubmitted.
Reason:
The SYSOUT group cannot be found on any backup tape.
Action:
None. The SYSOUT group is not available on tape.
Reason:
The SYSOUT group located on the backup tape is not the SYSOUT as referenced in the master index.
Action:
Use the SARTCP utility to map and correct the backup tape.
Reason:
The backup tape cannot be found in the master index. This is normally caused by the backup cycle deleting the tape before completion of the load request.
Action:
None. The SYSOUT group is no longer available.
Reason:
Dynamic allocation failed for allocating the backup tape file. The hexadecimal error and information codes are provided.
Action:
Consult the online retrieval HELP facility for a description of the dynamic allocation error code. Take appropriate action to correct the allocation error, and then resubmit the print request.
Reason:
A permanent I/O error occurred attempting to position the archival tape to retrieve the SYSOUT group.
Action:
Resubmit the request. If the I/O error occurs again, use the SARTCP utility to map and correct the tape.
Reason:
The requested function cannot be performed because the specified SYSOUT group is open for output. The SYSOUT group can be in open status due to a currently pending temporary load operation, a pending migration operation, or initial creation.
Action:
Wait until the status of the SYSOUT group has changed from open status, then resubmit print request. If the open condition is invalid, that is, a system crash or abend occurred while the SYSOUT group was in open status and being processed; 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 occurred attempting to read SYSOUT data from a backup tape.
Action:
Resubmit the request. If the I/O error occurs again, use the SARTCP utility to map and correct the tape.
Note: For more information about recovery procedures, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The specified view does not exist in the master index.
Action:
Verify the existence of the view. If the view number was specified incorrectly, change the parameter specification, and then resubmit the print request.
Reason:
Dynamic allocation failed for allocating the print SYSOUT data set. The hexadecimal error and information codes are provided.
Action:
Consult the online retrieval HELP facility for a description of the dynamic allocation error code. Take appropriate action to correct the allocation error, then resubmit load request.
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 IEFDORC macro.
Action:
The SYSOUT is printed without OUTPUT statement attributes. If you want, make appropriate changes and resubmit the print request.
Reason:
The PC transmittal queue is full for the user.
Action:
Have the user transmit their queue and clear the entries.
Reason:
The destination specified 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:
The requested banner page name is not found in the database, and a default banner page member is used.
Action:
None. If you want, change the banner page name to one that is defined to the database or add the banner page member to the database with the BLOAD function of the SARDBASE utility and resubmit the request.
Reason:
The requested banner page name is not found in the database, and the SYSOUT is printed without banner pages.
Action:
None. If you want, change the banner page name to one that is defined to the database or add the banner page member to the database with the BLOAD function of the SARDBASE utility and resubmit the request.
Reason:
The external print request was successfully queued for processing.
Action:
None. This message is informational.
Reason:
The SARBCH print request has failed because the PRINTER keyword is mutually exclusive with the DEST and/or DDNAME specifications.
Action:
Eliminate either the DEST or DDNAME keyword specifications, then resubmit the print request.
Reason:
The SARBCH print request has failed because the SELECT keyword is mutually exclusive with the PAGE and RECORD specifications.
Action:
Eliminate either the SELECT, PAGE, or RECORD keyword specification, then resubmit the print request.
Reason:
The SARBCH print request specifying the SELECT keyword has failed because the SYSOUT does not reside on disk. The most likely reason for this is that the location is TAPE.
Action:
Reload the SYSOUT to disk. Verify that the index is present, and then resubmit the print request.
Reason:
The SARBCH print request specifying the SELECT keyword has failed because no views exist for the SYSOUT.
Action:
Do one of the following:
Note: Page indexing occurs only during archival.
Reason:
The SARBCH print request specifying the SELECT keyword has failed because an I/O error occurred while opening or reading the page index data from the database. The data is unreadable.
Action:
Do one of the following:
Note: The index can be rebuilt only by re-archiving the SYSOUT.
Reason:
The SARBCH print request specifying the SELECT keyword has failed because indexing has not been established for the view.
Action:
Establish indexing criteria for the view if it does not exist. Re‑index or re-archive the SYSOUT. Page indexing occurs only during archival.
Reason:
The SARBCH print request specifying the SELECT keyword has failed because the SELECT text ID did not match any index selection.
Action:
Check that the SELECT text and index selection criteria are as intended. The SYSOUT must be archived again if the page indexing criteria is changed. Page indexing occurs only during archival.
Reason:
The SARBCH print request has failed because the user exit SARDSTUX has denied the request.
Action:
See your system administrator or specify an authorized destination for the reprint.
Reason:
Your print request exceeded the maximum number of lines 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 actions:
Reason:
Your print request exceeded the maximum number of lines permitted during the CA Spool Print Management 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:
Do one of the following actions:
Reason:
The DEFine DEVice record is invalid. A record that was not completely defined could cause this error.
Action:
Correct the DEFine DEVice record and retry.
Reason:
The page index value specified on the SELECT keyword of the print request is not found for the requested SYSOUT group.
Action:
Verify that the correct page index value, SYSOUT group, and view are being specified; otherwise, remove the SELECT parameter, then print the entire SYSOUT group.
Reason:
An attempt is being made to print a SYSOUT group from tape, but certain vital backup tape control information cannot be found.
Action:
Normally, tape control information is retained as long as there are reports that reference it. The tape control record (TCR) can be reinstated by re-adding the tape back into the database with the TADD facility of the SARTDR utility.
Important! This condition could identify a serious problem with the database or problems with the supporting code. Report the problem to CA Technical Support.
Reason:
An error occurred opening a report on optical disk or on tape accessed through an EAS tape server.
Action:
Browse the report online to see any error messages from the DSK2 driver or EAS tape server interface routine.
Reason:
Distributed files archived into a CA View database can only be viewed and printed from CA Output Management Web Viewer.
Action:
Access and print the distributed file from the CA Output Management Web Viewer product.
Reason:
The SARSECUX security user exit or external security has denied access to the logical view of the SYSOUT group.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
This message is issued by SARBCP when a non-zero return code is returned by SARPRTUX.
Action:
This message is informational, no action is required.
Reason:
The DSLIST parameter cannot be specified with the SELECT parameter.
Action:
Remove the DSLIST or SELECT parameter specification, then resubmit the print request.
Reason:
The requested SYSOUT does not have an associated data set list and data set list entries cannot be printed. Data set list information is not captured for SYSOUT archived with a pre-r11.0 release.
Action:
The DSLIST parameter cannot be used to print pages related to data set list information. Specific pages or records can be printed by specifying the PAGE or RECORD parameters.
Reason:
The specified ddname, step name, and/or procedure step name could not be found in the data set list for the SYSOUT.
Action:
Verify the data set list information from online retrieval by entering the "?" line command on the Sysout/Report Selection List panel for the SYSOUT. Correct the DSLIST specification, then resubmit the print request.
Reason:
The SARSECUX security user exit or external security has denied access to the specified index of the SYSOUT group.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not provided.
Reason:
The listing of SYSOUT groups or USERIDs is successfully written to the REPORT DD statement.
Action:
None. This message is informational.
|
Copyright © 2013 CA.
All rights reserved.
|
|