Reason:
The distribute to/description information on the Dynamic Distid Listing report was not available due to access error(s) as indicated by the SARBCT08 message. The report is produced. The distribution to/description field contains text of '***Error***' for those entries that had an access error.
Action:
Refer to the SARBCT08 message for an explanation of the error.
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 list 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 groups. If the SYSOUT identifier (ID), and/or generation (GEN) was specified incorrectly, change the parameter specification, and then resubmit the list request.
Reason:
The requested user ID does not exist in the master index. This is normally caused by an incorrect specification of the USER parameter or the user ID was already deleted by another job or user by using the online retrieval facility or batch retrieval facility (SARBCH).
Action:
Verify the existence of the user ID. If the user ID (USER parameter) was specified incorrectly, change the parameter specification, and then resubmit the list request.
Reason:
The USER parameter cannot be specified with the EXCP, GEN, ID, and/or SEQ parameter.
Action:
Either remove the USER parameter or remove the EXCP, GEN, ID, and/or FORMAT parameters from the control statement, and then resubmit the list request.
Reason:
The USERID extracted by the SARUSBUX utility does not have sufficient authority (master authority) to list USERIDs from the database. The USERID that requires authority is indicated in the SARBCH05 message.
Action:
Consult your security administrator or systems programming group to determine the reason why the authorization was not provided.
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:
When listing a logical view definition, these keywords are not permitted.
Action:
Remove the mutually exclusive keywords.
Reason:
Listing a logical view definition requires MASTER authority.
Action:
Request that the job be run by a user with master authority.
Reason:
The requested logical view definitions do not exist in the master index. This is usually caused by an incorrect specification of the VIEW parameter.
Action:
Verify the existence of the logical view definitions. If the logical view definition (VIEW parameter) was specified incorrectly, change the parameter specification and then resubmit the list request.
Reason:
The SARBCH LISTVIEW function processed a logical view definition with more than 99 column headings.
Action:
Change the logical view to use 99 or less column headings.
Reason:
This message identifies the profile attributes of the online user after processing the DEFUSER request.
Action:
None. This message is informational.
Reason:
The online user and profile attributes are successfully added to the CA View database. This message is accompanied by the SARBCU02 message that details the user profile information.
Action:
None. This message is informational.
Reason:
The online user and profile attributes for an existing user were successfully changed. This message is accompanied by the SARBCU02 message, which details the user profile information.
Action:
None. This message is informational.
Reason:
The SYSOUT and DISTID references used to qualify selection of SYSOUT for online users in SAR mode have been successfully added to the CA View database.
Action:
None. This message is informational.
Reason:
Master authority is required to perform the DEFDIST, DEFSYS, or DEFUSER request.
Action:
Consult with your security administrator or systems programming group to determine the reasons why the authorization was not provided.
Reason:
The SARSECUX security exit or external security has denied authorization to create or update a user, SYSOUT, or distribution definition.
Action:
Consult with your security administrator or systems programming group to determine the reasons why the authorization was not provided.
Reason:
The parameter specification for the MODE keyword on the DEFUSER control statement is invalid. The acceptable values are ALL, EXPO, EXP, SARO, or SAR.
Action:
Correct the MODE keyword specification on the DEFUSER control statement, then resubmit the define request.
Reason:
The USER keyword was not specified, or a user ID is not supplied with the USER keyword. The USER parameter is required on the DEFUSER control statement.
Action:
Correct or add the USER keyword specification on the DEFUSER control statement, then resubmit the define request.
Reason:
The distribution identifier specified on the DISTID keyword of the DEFUSER request does not match the masking pattern of the DISTID mask.
Action:
Either change the distribution identifier on the DISTID keyword to conform to the DISTID mask or change the DISTID mask to encompass the specification of the specified distribution identifier.
Reason:
The access mode specified on the MODE parameter of the DEFUSER control statement is not accessible based on the access mode indicators defined to the user.
Action:
Either change the access mode specified on the MODE parameter to an accessible mode or change the access mode indicators to allow access to the specified access mode.
Reason:
The access mode indicator specification on the ACC parameter of the DEFUSER control statement is not valid. The access mode indicator specification can be Y or N for each of the five access modes, ALL, EXPO, EXP, SARO, and SAR, respectively.
Action:
Correct the specification of the access mode indicators on the ACC parameter, and then resubmit the define request.
Reason:
The USER keyword is not specified on the DEFUSER control statement, or the SYSOUT keyword is not specified on the DEFDIST or DEFSYS control statement.
Action:
Add the appropriate keyword specification to the define request, and then resubmit the request.
Reason:
The DISTID keyword is not specified on the DEFDIST or DEFSYS control statement and is required.
Action:
Add the DISTID keyword specification to the define request, and then resubmit the request.
Reason:
An error occurred while reading or writing data from the CA View database. This message must 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 online panels for the specified language are not found in the CA View database. When the LANGUAGE keyword is specified on the DEFUSER control statement, the CA View database is queried for the online member name SAxRP1, where x is the language specification. This error message is generated when that online member is not found.
Action:
Load the appropriate language panels into the CA View database or specify a language that is defined to your CA View database.
Reason:
This message identifies the profile attributes of the online View definition after processing the DEFVIEW request.
Action:
None. This message is informational.
Reason:
The online View attributes are successfully added to the CA View database. This message is accompanied by the SARBCV02 message that details the View definition information.
Action:
None. This message is informational.
Reason:
The online View attributes for an existing definition were successfully changed. This message is accompanied by the SARBCV02 message, which details the View 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 VIEW keyword on the DEFVIEW control statement was not specified or is invalid.
Action:
Correct the VIEW keyword specification on the DEFVIEW control statement, and then resubmit the request.
Reason:
The ALINE keyword value specified on the DEFVIEW control statement was greater than 9. Valid ALINE keyword values are 1 through 9.
Action:
Correct the ALINE keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The EXCRECS keyword value specified on the DEFVIEW control statement was greater than 60. Valid EXCRECS keyword values are 1 through 60.
Action:
Correct the EXCRECS keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The DISPRECS keyword value specified on the DEFVIEW control statement was greater than 254. Valid DISPRECS keyword values are 1 through 254.
Action:
Correct the DISPRECS keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The total EXCRECS and DISPRECS keyword values specified on the DEFVIEW control statement was greater than 254. The total value specified on the EXCRECS and DISPRECS keywords cannot exceed 254.
Action:
Correct the EXCRECS and or DISPRECS keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
An I/O error occurred while attempting to index data for the referenced report.
Action:
Correct the I/O error by re-indexing the report. If problems continue, restore the database.
Reason:
An internal parameter error occurred while attempting to index data for the referenced report.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The NUM keyword value specified on the DEFVIEW control statement is 0. Valid NUM keyword values are 1 through 255.
Action:
Correct the NUM keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The NUM keyword value specified on the DEFVIEW control statement is greater than 255. Valid NUM keyword values are 1 through 255.
Action:
Correct the NUM keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The ALINES keyword value specified on the DEFVIEW control statement is 0. Valid ALINES keyword values are 1 through 9.
Action:
Correct the ALINES keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The ACL1 or ACL2 keyword value specified on the DEFVIEW control statement is invalid. Valid ACL1 and ACL2 keyword values are B, R, P, G, T, Y, or W.
Action:
Correct the ACL1 or ACL2 keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The AHL1 or AHL2 keyword value specified on the DEFVIEW control statement is invalid. Valid AHL1 and AHL2 keyword values are B, R, or U.
Action:
Correct the AHL1 or AHL2 keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The FILTER keyword value specified on the DEFVIEW control statement contains invalid characters. Valid FILTER characters are limited to alphanumeric, national, and limited special characters.
Action:
Correct the FILTER keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The DEFVIEW statement keyword xxxxxxx subparameter number n is not valid.
Action:
Correct the keyword and then resubmit the define request.
Reason:
The DEFVIEW SEARCH keyword refers to an undefined DEFVIEW HDGn (HDG1-HDG99) keyword.
Action:
Correct the SEARCH keyword specification or add the missing HDGn keyword on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The CLRn (CLR1-CLR6) keyword value specified on the DEFVIEW control statement is invalid. Valid CLRn keyword values are B, R, P, G, T, Y, or W.
Action:
Correct the CLRn keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The HLTn (HLT1-HLT6) keyword value specified on the DEFVIEW control statement is invalid. Valid HLTn keyword values are B, R, or U.
Action:
Correct the HLTn keyword specification on the DEFVIEW control statement, and then resubmit the define request.
Reason:
View definition record exceeds maximum length.
Action:
Reduce HEADING, COLUMN, HDGn, or SEARCH definitions on the DEFVIEW control statement, and then resubmit the define request.
Reason:
HEADING, COLUMN, HDGn, or SEARCH definition contains more than 255 entries.
Action:
Reduce the number of HEADING, COLUMN, HDGn, or SEARCH entries on the DEFVIEW control statement, and then resubmit the define request.
Reason:
HDGn definitions specified without corresponding COLUMN definitions.
Action:
Either delete the HDGn definitions or add the corresponding COLUMN definitions on the DEFVIEW control statement, and then resubmit the define request.
Reason:
The SARSECUX security exit or external security has denied authorization to perform DEFVIEW function.
Action:
Consult your security administrator or systems programming group to determine the reasons why the authorization was not provided.
Reason:
The SARSECUX security exit or external security has denied authorization to create or update the logical view definition.
Action:
Consult your security administrator or systems programming group to determine the reasons why the authorization was not provided.
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 reasons why the authorization was not provided.
Reason:
The ID parameter is specified without a SYSOUT identifier, which is required on the control statement.
Action:
Change the ID parameter to include the SYSOUT identifier that is to be extracted, then resubmit the extract request.
Reason:
The CA Balancing Report Control (CA Balancing) extraction program, INBEXTP, was not found.
Action:
Ensure that the INBEXTP load module is accessible from the STEPLIB, JOBLIB, or the linklist; resubmit the request.
Reason:
The CA Balancing extraction for the request SYSOUT group completed successfully.
Action:
None. This message is informational.
Reason:
The CA Balancing extraction completed, but there were warning messages that were issued.
Action:
Review the warning message to determine if action is necessary.
Reason:
The CA Balancing extraction was unsuccessful due to a previous error.
Action:
Refer to the previous error to determine the appropriate action.
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 extract 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 the sequence number (SEQ) were specified incorrectly, change the parameter specification. Then resubmit the load request.
Reason:
The SYSOUT group is not loaded to the CA View database because it already resides on disk. Initial processing of the extract request determined that the SYSOUT group that resides on tape or secondary disk must be loaded to the CA View database to perform the extraction. Later, it was determined that the SYSOUT group is reloaded by another batch or online request.
Action:
Resubmit the extract request.
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 the one that is 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 extract 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, and then resubmit the extract 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 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 extract request. If the I/O error occurs again, use the SARTCP utility to map and correct the tape. In addition, for recovery procedures, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
A CA View backup cycle has been initiated.
Action:
None. This message is informational.
Reason:
An I/O error occurred attempting to backup the specified SYSOUT group. The remainder of the SYSOUT group is skipped.
Action:
Probably none; however, verify that there is no major problem with the database.
Reason:
An I/O error occurred attempting to delete the specified SYSOUT group. The group is not deleted.
Action:
Probably none; however, verify that there is no major problem with the database.
Reason:
The database contains references to tape volumes owned by another database. This condition is the result of a database merge.
Action:
Run SARPAC to copy the SYSOUT groups on tape to new tape volumes owned by this database.
Reason:
A dynamic allocation request for allocating the print data set to SYSOUT failed. The hexadecimal error and information codes are provided.
Action:
Determine the reason for the failure and fix the problem. Then resubmit the job.
Reason:
Error attempting to access the recovery data set. The CA View backup cycle is terminated.
Action:
None. If a hardware error is not indicated, contact CA Technical Support.
Reason:
There is no DD statement for the backup recovery file in the started task.
Action:
None, if you wish to run without the backup recovery file. Otherwise, change the started task JCL and restart.
Reason:
The CA View started task issues the IEFSSREQ macro to verify that a SYSOUT is not yet being written to the CA View database when the backup cycle attempts to migrate it off disk. The IEFSSREQ macro had a return code of xx.
Action:
See the IBM documentation for return codes for the IEFSSREQ macro.
Reason:
The CA View started task issues the IEFSSREQ macro to verify that a SYSOUT is not yet being written to the CA View database when the backup cycle attempts to migrate it off disk. The IEFSSREQ macro had a return code of xx. Field SSOBRETN contained an unanticipated value. This could be caused by changes to JES control blocks SSOB and SSCS.
Action:
See the IBM documentation for return codes for the IEFSSREQ macro.
Reason:
This message is issued after message SARBKT57 or SARBKT58. It indicates that the identified SYSOUT sub-file data was to have been deleted from disk because it has expired through the NGEND initialization parameter value. Because the attempt to verify that the SYSOUT group was not still being processed failed, it is not deleted from disk.
Action:
See the IBM documentation for the IEFSSREQ return code indicated in the previously issued SARBKT57 or SARBKT58 message. Possibly, use the DD online command to manually change the location to TAPE to free the allocated disk space.
Reason:
The CA View started task discovered a SYSOUT was still in OPEN status. This message is issued when the IEFSSREQ macro verifies whether the sysout is still being written to disk.
This message can also be produced during the backup cycle if a temporary ACIF resource subfile exists on the database. The SYSOUT group name references a report that does not appear to exist. This circumstance can occur when the ACIF Printer subtask (FSA) is terminated and then restarted without also terminating the FSS Collector at the same time an AFP report is being archived. A temporary ACIF resource subfile created during the archival process remains on the database until the FSS Collector is recycled, even though the report and associated resources were archived normally once the FSA restarted.
Action:
None. If the message persists, and you want to free the disk space, use the C online command to change the location from OPEN to DISK. With the next backup cycle, the partial SYSOUT is backed up to tape unless you delete it first.
If the message is caused by a temporary ACIF resource subfile, then the SYSOUT GROUP name shows the four character System Id followed by the eight character job number of the FSS Collector task. This temporary resource subfile can be residual from a database full condition. The backup cycle produces the message until the FSS Collector is stopped and restarted
Reason:
This message identifies which internal backup phase is beginning. Phase 1 backs up the current generation to tape and performs ERO processing. Phase 2 backs up the master index to tape, deletes expired reports, and uncatalogs expired tapes.
Action:
None. This message is informational.
Reason:
This message identifies which internal backup phase is ending. The number of reports on the database includes those that are not currently on DASD (they are on tape). The number processed only includes those in the current generation. Because archiving can continue during the backup, these numbers can change from backup phase to backup phase.
Action:
None. This message is informational..
Reason:
This message is a progress report issued during a backup. It appears at intervals specified by the SARINIT parameter DBMSGFRQ.
Action:
None. This message is informational.
Reason:
An error occurred attempting to delete the report form optical disk.
Action:
Verify that the optical device is functioning properly.
Reason:
The named storage group is being copied from disk to tape. STORGRP0 is named DEFAULT by CA View.
Action:
None. This message is informational.
Reason:
Clean processing has been initiated.
Action:
None. This message is informational.
Reason:
Clean processing has completed.
Action:
None. This message is informational.
Reason:
The Initialization parameter CLEAN has been set to NO and the clean processing is not performed and is bypassed.
Action:
None. This message is informational.
Reason:
Secondary disk migration is scheduled for this backup cycle and driver initialization has completed successfully.
Action:
None. Informational message.
Reason:
Secondary disk migration ended and xxx reports have been migrated to secondary disk and yyy reports have expired from secondary disk.
Action:
None. Informational message.
Reason:
Backup cycle ended.
Action:
None. This message is informational.
Reason:
Issued with SARBKT99 to advise you of current archival generation and whether the generation number has changed because of the just completed backup.
Action:
None. This message is informational.
Reason:
Direct-to-tape archival must be suspended until the backup cycle has completed.
Action:
None. Direct-to-tape archival resumes following completion of the backup cycle.
Reason:
Another backup cycle has been started, possibly by the operator or due to insufficient storage, and so on. SYSOUT archival must be suspended until the backup cycle has completed.
Action:
None. This message is informational.
Reason:
The operator has attempted to stop SAR with a P command. The SYSOUT archival termination must be suspended until the backup cycle has completed.
Action:
None. This message is informational.
Reason:
The request for the type of backup indicated (standard or interim) has been ignored since to honor it would cause multiple backups to queue and you have specified STACKBU=NO as an initialization parameter.
Action:
None. This message is informational.
Reason:
The backup cycle is bypassed because a SARDBASE RESTORE operation is in progress. The backup cycle scratches the old recovery files and creates new ones, but SARDBASE RESTORE is reading the old recovery files.
Action:
None. This message is informational.
Reason:
You attempted to stop the archival task with a STOP (P) operator command while a backup cycle was running. This message gives you the option of having CA View terminate its backup.
Warning! If you cause CA View to terminate its backup, it will continue from where it left off the next time it is brought up. This is a consideration if you are using a tape management system, and canceling a tape backup job could result in the tape being scratched.
Action:
Reply W to let the backup cycle complete running or T to terminate it.
Note: If the backup cycle terminates before an operator response is received, the Archival Task (SARSTC) terminates normally and the outstanding operation action message is canceled.
Reason:
The database's generation number is greater than 32759 and is approaching the maximum limit of 32767.
Action:
See the action plan for message SARBKU09.
Reason:
The database's generation number has reached its maximum limit of 32767. No standard backup cycles run until this condition is resolved.
Action:
The database must be unloaded and merged to a new empty database. SARDBASE/MERGE re-sequence the Sysout generation numbers based on the oldest Sysout in the database, correcting the high generation number.
Reason:
The CA View backup cycle has abended. The system or user abend code is provided.
Action:
Consult the IBM MVS System Messages manual to determine the reason for the abend. If you still cannot determine the problem, for assistance contact CA Technical Support.
Reason:
The model banner page cannot be found in the database.
Action:
Correct the model banner page name if it is in error, or add the model banner page member to the database with the BLOAD function of the SARDBASE utility.
Reason:
Record number nnn of the model banner page definition contains an invalid control statement.
Action:
Correct the statement and reload the model banner page member into the database with the BLOAD function of the SARDBASE utility.
Reason:
The symbolic variable in record number nnn of the model banner page definition is missing its terminator.
Action:
Correct the symbolic variable and reload the model banner page member into the database with the BLOAD function of the SARDBASE utility.
Reason:
The symbolic field following the variable name in record number nnn of the model banner page definition is not blank.
Action:
Correct the symbolic field and reload the model banner page member into the database with the BLOAD function of the SARDBASE utility.
Reason:
The symbolic variable in record number nnn of the model banner page definition is not in the correct syntax.
Action:
Correct the symbolic variable and reload the model banner page member into the database with the BLOAD function of the SARDBASE utility.
Reason:
Record number nnn contains a symbolic field without any variable name.
Action:
Correct the symbolic field and reload the model banner page member into the database with the BLOAD function of the SARDBASE utility.
Reason:
CA View was not able to allocate space for the SYSOUT data set indicated in the error message.
Action:
Correct and retry.
Reason:
No distribution identifiers for the report exist.
Action:
Correct and retry.
Reason:
No reports exist for the distribution identifier.
Action:
Correct and retry.
Reason:
A file on the mounted tape is null.
Action:
Correct and retry.
Reason:
The file specified is not the selected group.
Action:
Correct and retry.
Reason:
The backup tape specified does not exist.
Action:
Correct and retry.
Reason:
Tape allocation was not possible because of reasons referenced by code.
Action:
Correct and retry.
Reason:
I/O was not possible because of error positioning the tape.
Action:
Correct and retry.
Reason:
The SYSOUT group specified is open for output.
Action:
Correct and retry.
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 bundle or portions of the bundle are printed without OUTPUT statement attributes. If you want, make appropriate changes and resubmit the bundle print request.
Reason:
A permanent I/O error occurred when reading the tape.
Action:
Use SARTCP to correct the problem with the tape.
Reason:
The SARSECUX security user exit or external security does 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 PRINTIDX statement.
Action:
Change the ID parameter to include the SYSOUT identifier that is to be printed, and then resubmit the print request.
Reason:
The JCL statement name specified in the DDNAME parameter of the PRINTIDX statement of the SARBCH utility was not provided.
Action:
Either remove the DDNAME parameter or specify the respective DDNAME.
Reason:
The index for the SYSOUT group was successfully queued to print.
Action:
None. This message is informational.
Reason:
The index for the SYSOUT group is successfully copied to the specified JCL DD statement.
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 the batch retrieval facility (SARBCH).
Action:
Verify the existence of the SYSOUT group. If the SYSOUT identifier (ID), generation (GEN), and/or the sequence number (SEQ) was specified incorrectly, change the parameter specification, and then resubmit the print request.
Reason:
The requested logical view for the SYSOUT group does not exist in the master index. This is normally caused by a mistyped logical view number or by the deletion of the logical view from the online retrieval facility or batch retrieval facility (SARBCH).
Action:
Verify the existence of the logical view for the SYSOUT group. If the logical view (VIEW) was specified incorrectly, change the parameter specification, and then resubmit the print request.
Reason:
The requested index for the SYSOUT group was not found.
Action:
Verify the existence of the index for the SYSOUT group. If the index was specified incorrectly, change the parameter specification, and then resubmit the print request. If the index data does not exist for the SYSOUT group, the SYSOUT group can be re‑indexed from the online retrieval facility or batch retrieval facility (SARBCH).
Reason:
The index data for the SYSOUT group does not reside in the database, and access is not available from the Expanded Access Server (EAS).
Action:
Start the appropriate Expanded Access Server (EAS) task, or load the index data for the SYSOUT group to disk using the online retrieval facility or batch retrieval facility (SARBCH) and resubmit the print request.
Reason:
The VIEW or INDEX parameter was not specified and is required on the PRINTIDX control statement.
Action:
Add the VIEW or INDEX parameter to the PRINTIDX statement and resubmit the print request.
Reason:
A unique selection value can be specified for each index field for a logical view index, ACIF index, or XPPS index to limit the amount of index data that is printed. The SELECT parameter specified values that do not correspond to an index field for the requested index.
Action:
Correct or remove the SELECT parameter and resubmit the request.
Reason:
Index data that corresponds to the SELECT parameter is not found for the requested index.
Action:
Verify that the SELECT parameter references the correct values. If the SELECT parameter was specified incorrectly, correct the parameter and resubmit the print request.
Reason:
Index data cannot be queued for download to a PC user or printed using the external print interface.
Action:
Change the print destination (DEST) to a valid destination and resubmit the print request.
Reason:
The SARBCH print request failed because the SARDSTUX user exit denied printing to the requested destination.
Action:
See your system administrator or specify an authorized destination for the reprint.
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, and then resubmit the print 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 index for the SYSOUT group is printed without OUTPUT statement attributes. If you want, make appropriate changes and resubmit the print request.
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 resubmit.
Reason:
An I/O error occurred while opening or reading the index data for a SYSOUT group. The data is unreadable.
Action:
Do one of the following actions:
Reason:
The requested index for the SYSOUT group was not found.
Action:
Verify the existence of the index for the SYSOUT group. If the index is specified incorrectly, change the parameter specification and resubmit the print request. If the index data does not exist for the SYSOUT group, the SYSOUT group can be re‑indexed from the online batch retrieval facility or batch retrieval facility (SARBCH).
Reason:
Your print request exceeded the maximum number of lines permitted during online 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:
Do one of the following actions:
Reason:
Your print request exceeded the maximum number of lines permitted during 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:
Do one of the following actions:
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:
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.
* *
* CENTERA ACCESS SERVER *
* SARCAS (XXXX) HAS ABENDED WITH CODE XXXXX *
* ****** RESTART SARCAS ASAP ****** *
* *
*********************************************************
Reason:
The CENTERA access server has abended. The system or user abend code is provided.
Action:
See the IBM MVS System Messages Guide to determine the reason for the abend. If you still cannot determine the problem, contact CA Technical Support at http://ca.com/support.
Reason:
A Centera processing thread has abended. The system or user abend code, TCB address, process request entry address, process request type, and requester's job ID are provided.
Action:
Consult the IBM MVS System Messages Guide to determine the reason for the abend. For assistance, contact Technical Support at http://ca.com/support.
Note: The task is restarted automatically and processing continues.
Reason:
A Centera processing thread of the expanded access server for tape and robotics has abended and is being restarted automatically.
Action:
None. This message is informational.
Reason:
This message is displayed whenever the server is stopped. You can use the information provided to adjust the NREQ initialization parameter.
Action:
None. This message is informational.
Reason:
The primary server is already active and cannot be started again.
Action:
None. This message is informational.
Reason:
The server is already active on this system and cannot be started again.
Action:
None. This message is informational.
Reason:
The specified operator command is invalid.
Action:
Reissue the operator command in its correct form.
Reason:
The specified parameter is invalid. The server uses the default value for the parameter and continues processing.
Action:
Correct the initialization parameter in the start procedure JCL.
Reason:
The specified server type is invalid. The server uses the default value ONLY for the server type and continues processing.
Action:
Correct the initialization parameter in the start procedure JCL.
Reason:
A listing of the parameters used by the server is provided at startup time.
Action:
None. This message is informational.
Reason:
The specified XCF request failed. The hexadecimal return and reason codes are provided.
Action:
For the return and reason codes to determine the cause of the failure, see the IBM Authorized Assembler Reference Guide. If you still cannot determine the problem, contact CA Technical Support at http://ca.com/support.
Reason:
The specified communication mechanism is invalid. The server uses the default value XCF for the communication mechanism and continues processing.
Action:
Correct the initialization parameter in the start procedure JCL.
Reason:
The COMMRESET operator command was successfully executed.
Action:
None. This message is informational.
This message number represents one of the following messages:
Unable to modify NTHREADS to nnn for SARCAS (taskname/smfid) Maximum value is xxx. Current value is yyy.
Reason:
SARCAS has processed a modify NTHREADS command request and rejected the new value (nnn) for NTHREADS. xxx is the value that was specified when the task was started, and yyy is the current value for NTHREADS.
Action:
Correct the NTHREADS value. This value cannot exceed what was defined when the task was started.
Reason:
SARCAS has processed a modify NTHREADS command request and accepted the new value (nnn) for NTHREADS.
Action:
None. This message is informational.
Reason:
The EMC Centera API modules (FPAPIDLL, FPMDZDLL, FPPOSDLL, FPPAIDLL, and/or XERCES26) were not found. This message occurs if a release 3.0 or prior EMC Centera load library is referenced.
Action:
Add the EMC Centera load library to JOBLIB, STEPLIB, or the link list. The EMC Centera load library can also be copied to CVDELOAD.
Reason:
An unsupported version of the EMC Centera API modules is found in JOBLIB, STEPLIB, or the link list.
Action:
Add the EMC Centera load library distribute with CA View to JOBLIB, STEPLIB, or the link list. The EMC Centera load library can also be copied to CVDELOAD.
Reason:
The SARCAS server whose name appears in the CENTNAME parameter is not active.
Action:
See your system administrator to determine why SARCAS is not active. Generally, CA View attempts to directly mount the volume containing the report.
Reason:
The primary server (responsible for access to the Centera Cluster) is not active.
Action:
See your system administrator to determine why SARCAS is not active.
Reason:
A severe problem has occurred in the Centera EAS Task.
Action:
Collect the appropriate information for problem analysis, and then see your system administrator to restart the server.
Reason:
An attempt is made to view a report directly from Centera, using the Centera Access Server. After one minute, the Centera Access Server (SARCAS) did not return any data.
Action:
Retry later.
Reason:
You are viewing a tape report, and the Centera Access Server was unable to locate a page record vector.
Action:
See your system administrator. Each report's page record vector is located using a field in the GCR in the DASD database. The report could have been damaged. The system administrator can restore the report from the tape backup and can migrate another copy, after which you must be able to access it.
Reason:
A report on Centera storage tape was being viewed using the Centera access server. The END OF DATA was unexpectedly reached.
Action:
The report's mapping information could have been overwritten. The system administrator can restore the report from the tape backup and can migrate another copy.
Reason:
An attempt is made to view a report on Centera storage, but the report is not found on the Centera device.
Action:
See your system administrator. The system administrator can restore the report from the tape backup and can migrate another copy.
Reason:
An attempt is made to view a report on tape using the Centera access server, and an I/O error was encountered.
Action:
See your system administrator. The system administrator can restore the report from the tape backup and can migrate another copy.
Reason:
An internal error has occurred.
Action:
The migration sub-task has unexpectedly terminated. Add an FPCONFIG DD Statement to failing task. The FPCONFIG statement must point to a symbolic data set which contains the name of the Centera API Trace file (see System Reference Guide). Rerun the task and provide CA Technical Support with the data collected in the Centera API Trace file. For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error has occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error occurred. SARCENT does not recognize the format of this GCR.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The EMC Centera API modules (FPAPIDLL, FPMDZDLL, FPPOSDLL, FPPAIDLL, and/or XERCES26) were not found. This message occurs if a release 3.0 or prior EMC Centera load library is referenced.
Action:
Add the EMC Centera load library to JOBLIB, STEPLIB, or the link list. The EMC Centera load library can also be copied to CVDELOAD.
Reason:
An unsupported version of the EMC Centera API modules is found in JOBLIB, STEPLIB, or the link list.
Action:
Add the EMC Centera load library distribute with CA View to JOBLIB, STEPLIB, or the link list. The EMC Centera load library can also be copied to CVDELOAD.
Reason:
SYSOUT archival was terminated.
Action:
None. This message is informational.
Reason:
The CA View CICS conversational interface has abended.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
This message is issued when CA Spool rejected a request made by CA View in an unexpected fashion (no other more specific error message applies). fffff is the function, which can be OPEN, WRITE, or CLOSE. dddddddd is the target CA Spool device. rr is the CA Spool return condition found in the CA Spool parameter list field @OPENSTA. ppp is only present when the error is an invalid CA Spool parameter list, and identifies the unacceptable parameter as found in the CA Spool parameter list field @OPENPID.
Action:
Check the CA Spool documentation for the return condition that was found.
Reason:
CA Spool rejected a CA View open request because the CA Spool subsystem is not available. dddddddd is the target CA Spool device.
Action:
Bring up the CA Spool subsystem. If the problem still occurs, verify that the SARINIT parameter CMASPOOL= has the same value as the CA Spool ESFPARM parameter SUBID=. If you are using the CA View DEFine DEVice facility, and have overridden the SARINIT CMASPOOL parameter by specifying SUB–SYSTEM ID, then it must be the same as the CA Spool ESFPARM SUBID= parameter.
Reason:
The CA Spool database is full. dddddddd is the target CA Spool device.
Action:
Make room in the CA Spool database by either waiting for SYSOUT to finish printing, deleting items, or making the database larger.
Reason:
You are trying to print to a device that is not defined to CA Spool. dddddddd is the target CA Spool device.
Action:
Specify a device that is already defined to CA Spool, or define the new device to CA Spool.
Reason:
The installation of the CA View-to-CA Spool interface was not finished. It requires a link-edit of the AESFPRIV routine provided on the user's CA Spool distribution tape into the SARCMAIX program provided on the CA View distribution tape. dddddddd is the target CA Spool device.
Action:
Finish the installation.
Reason:
CA View posted an unacceptable request code to CA Spool. dddddddd is the target CA Spool device.
Action:
Contact CA Technical Support.
Reason:
A non zero return code is encountered from a Centera API function call. The error code and message are provided. These errors normally indicate network errors, server errors, client errors, or Z/OS errors.
Action:
Centera error messages include a message class to identity where the error occurred.
The class of message:
Reason:
Internal error indicating that the incorrect request is issued during the migration of data to Centera.
Action:
For assistance, contact Technical Support at http://ca.com/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 will be re-migrated the next time the CA View started task or migration task is started.
Action:
None.
Reason:
The distribution ID referenced in the CA View user profile is not defined, or it has no reports defined to it. For EXP mode users, the DISTID and applicable reports are defined in CA Deliver. For SAR mode users, the DISTID and applicable reports are defined in CA View.
Action:
To produce lists of reports for the user, reports must be defined to the associated DISTID with CA Deliver (for EXP mode users) or CA View (for SAR mode users).
Reason:
The library containing the RMOGAM module is not defined to the DRAS task or is not accessible.
Action:
Add the CA Deliver load library to the STEPLIB or JOBLIB concatenation for the DRAS job or started task, or add the CA Deliver load library to the linklist.
Reason:
A SYSOUT must be on the primary disk to be indexed.
Action:
Reload the SYSOUT to disk (Online L Command or SARBCH LOAD), then resubmit the index request.
Reason:
No page separation criteria is specified with any logical view for this SYSOUT.
Action:
Specify the desired page separation criteria online, with at least one logical view definition.
Reason:
An I/O error occurred opening the SYSOUT.
Action:
Report the problem to your CA View administrator.
Reason:
An I/O error occurred reading the SYSOUT.
Action:
Report the problem to your CA View administrator.
Reason:
The database is possibly out of space.
Action:
Run SARDBASE STATUS, to check the percentage of utilization of the database. If the utilization is high, report the problem to your CA View administrator for appropriate action.
Reason:
An I/O error occurred writing the page index, possibly because the database is out of space.
Action:
Report the problem to your CA View administrator.
Reason:
An I/O error occurred updating the SYSOUT Group Control Record.
Action:
Report the problem to your CA View administrator.
Reason:
An I/O error occurred when deleting the old page index.
Action:
Report the problem to your CA View administrator.
Reason:
A new page index has been created.
Action:
None. This message is informational.
Reason:
An I/O error occurred rewriting the SYSOUT Group Control Record.
Action:
Report the problem to your CA View administrator.
Reason:
The database is possibly out of space.
Action:
Run SARDBASE STATUS, to check the percentage of utilization of the database.
Reason:
A database I/O error occurred.
Action:
Report the problem to your CA View administrator.
Reason:
SARBCH INDEX cannot index An AFP report, archived using the AFP Conversion and Indexing Facility (ACIF).
Action:
AFP reports are indexed with ACIF index control statements. For more information, see Indexing AFP Reports in the chapter "Archival" in the Reference Guide.
Reason:
The requested SYSOUT is being loaded to disk to perform index extraction for the report.
Action:
None. This message is informational.
Reason:
Indexing data cannot be extracted for distributed files.
Action:
None.
Reason:
An internal error has occurred within CA View.
Action:
Contact Technical Support.
Reason:
An internal error has occurred within CA View.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The CICS interface subtask has been started.
Action:
None. This message is informational.
Reason:
The CICS interface subtask has ended.
Action:
None. This message is informational.
Reason:
A request has been made to deactivate the CA View CICS subtask, but the subtask is already inactive.
Action:
None.
Reason:
A request has been made to deactivate the CA View CICS subtask, but active users were found.
Action:
Enter Y to force termination, or N to cancel subtask inactivation.
Reason:
Unable to terminate the CICS interface subtask.
Action:
Correct the problem and retry.
Reason:
The CICS interface subtask has been successfully terminated.
Action:
None. This message is informational.
Reason:
The index prefix in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The unit name in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The block size in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
A catalog management error was received when attempting to catalog the data set. The decimal value of registers 15, 0, and 1 are provided.
Action:
Determine the reason for the catalog error, and then correct the problem.
Reason:
The optical disk device cannot be accessed directly from VM/CMS.
Action:
Use the L selection code to submit a batch job to temporarily load the SYSOUT group to primary disk so that it can be accessed.
Reason:
An unexpected end of data condition was encountered when accessing the SYSOUT group on secondary disk storage. This condition must never happen.
Action:
Delete and re-archive the SYSOUT group.
Reason:
The SYSOUT group is identified in the master index as residing on secondary disk storage, but it cannot be found there.
Action:
Delete the disk copy of the SYSOUT group to enable the tape copy to be accessed.
Reason:
The driver is abnormally terminated by the system when attempting to create a data set. The abend code is provided.
Action:
Determine the reason for the abnormal termination and correct the problem.
Reason:
A dynamic allocation request for allocating a data set failed. The hexadecimal error and information codes are provided.
Action:
Determine the reason for the allocation failure and correct the problem.
Reason:
The internal format of the archived SYSOUT group is in error and cannot be used.
Action:
Delete and re-archive the SYSOUT group.
Reason:
The unit name in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The low or high volume serial number in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The low or high volume serial number in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
Only one volume serial number for the range of volume serial numbers in the DSK2PARM initialization parameter was specified.
Action:
Specify both volume serial numbers for the range.
Reason:
Either the low or high volume serial is specified without a numeric character as its last character.
Action:
Review and correct the specified volume serial.
Reason:
When specifying a range of volume serial numbers in the DSK2PARM initialization parameter, the volume serial numbers must be the same format.
Action:
Correct the volume serial numbers.
Reason:
The optical disk device cannot be accessed directly from VM/CMS.
Action:
Use the L selection code to submit a batch job to temporarily load the SYSOUT group to primary disk so it can be accessed.
Reason:
An unexpected end of data condition was encountered when accessing the SYSOUT group on secondary disk storage.
Action:
Delete and re-archive the SYSOUT group.
Reason:
The SYSOUT group is identified in the master index as residing on secondary disk storage, but it cannot be found there.
Action:
Delete the disk copy of the SYSOUT group to enable the tape copy to be accessed.
Reason:
An error occurred when writing to the optical disk device.
Action:
Correct the problem with the optical disk device.
Reason:
The SYSOUT group has been deleted by another user between the time the selection list was created and the time you made your request to access the SYSOUT group.
Action:
None. The SYSOUT group is no longer archived.
Reason:
A dynamic allocation request for allocating the secondary disk storage copy failed. The hexadecimal error and information codes are provided.
Action:
Determine the reason for the allocation failure and correct the problem.
Reason:
An error occurred attempting to position the secondary disk storage emulation tape to retrieve the SYSOUT group.
Action:
Resubmit the request. If the problem occurs again, then the SYSOUT group can no longer be accessed from secondary disk. You can then delete the disk copy of the SYSOUT group to enable the tape copy to be accessed.
Reason:
An I/O error occurred attempting to access the secondary disk storage emulation tape.
Action:
Resubmit the request. If the problem occurs again, then the SYSOUT group can no longer be accessed from secondary disk. You can then delete the disk copy of the SYSOUT group to enable the tape copy to be accessed.
Reason:
The index prefix in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The account identification code in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The account password in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The storage machine identifier in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
When loading the FileTek Callable Interface, module LSMCALL cannot be found.
Action:
Verify that the FileTek Callable Interface library is available to the step.
Reason:
The optical disk device cannot be accessed directly from VM/CMS.
Action:
Use the L selection code to submit a batch job to temporarily load the SYSOUT group to primary disk so it can be accessed.
Reason:
An unexpected end of data condition was encountered when accessing the SYSOUT group on secondary disk storage. This condition must never happen.
Action:
Delete and re-archive the SYSOUT group.
Reason:
The SYSOUT group is identified in the master index as residing on secondary disk storage, but it cannot be found there.
Action:
Delete the disk copy of the SYSOUT group to enable the tape copy to be accessed.
Reason:
The index prefix in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The account identification code in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The account password in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The storage machine identifier in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
When loading the FileTek Callable Interface, module LSMCALL cannot be found.
Action:
Verify that the FileTek Callable Interface library is available to the step.
Reason:
An unexpected end of data condition was encountered when accessing the SYSOUT group on secondary disk storage. This condition must never happen.
Action:
Delete and re-archive the SYSOUT group.
Reason:
The SYSOUT group is identified in the master index as residing on secondary disk storage, but it cannot be found there.
Action:
Delete the disk copy of the SYSOUT group to enable the tape copy to be accessed.
Reason:
CA View is waiting for more platters to be inserted into the FILETEK jukebox.
Action:
Reply R after the platters are inserted or T to terminate optical migration. Any other response is an invalid reply.
Reason:
CA View was accessing the FILETEK jukebox when the preceding error occurred.
Action:
For the LSMCALL macro return codes, refer to the documentation provided by FILETEK.
Reason:
The internal format of the archived SYSOUT group is in error and cannot be used.
Action:
Delete and re-archive the SYSOUT group.
Reason:
The unit name in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The low or high volume serial number in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The low or high volume serial number in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
Only one volume serial number for the range of volume serial numbers in the DSK2PARM initialization parameter was specified.
Action:
Specify both volume serial numbers for the range.
Reason:
Either the low or high volume serial is specified without a numeric character as its last character.
Action:
Review and correct the specified volume serial.
Reason:
When specifying a range of volume serial numbers in the DSK2PARM initialization parameter, the volume serial numbers must be of the same format.
Action:
Correct the volume serial numbers.
Reason:
An unexpected end of data condition was encountered when accessing the SYSOUT group on secondary disk storage.
Action:
Delete and re-archive the SYSOUT group.
Reason:
The SYSOUT group is identified in the master index as residing on secondary disk storage, but it cannot be found there.
Action:
Delete the disk copy of the SYSOUT group to enable the tape copy to be accessed.
Reason:
An error occurred when writing to the optical disk device.
Action:
Correct the problem with the optical disk device.
Reason:
When loading MDRS, the MDRSCALL module cannot be found.
Action:
Verify that the MDRS library is available to the step.
Reason:
The specified subsystem ID is not defined to MDRS for a connected optical disk device.
Action:
Check that the specified subsystem ID is correct for the desired optical disk device.
Reason:
The requested emulated tape volume cannot be found on the optical disk device. This condition could occur if the tape volume was deleted before your request for access.
Action:
Check the requested volume serials for validity.
Reason:
The Data/Ware MDRS interface has encountered an error.
Action:
Consult your Data/Ware MDRS documentation for the meaning of the return code.
Reason:
The index prefix in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The storage class in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The management class in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The DB2 system ID in the DSK2PARM initialization parameter is invalid.
Action:
Correct the value.
Reason:
The OAM or DB2 request failed with the specified return and reason codes.
Action:
For a list of reason and return codes, see the Object Access Method Application Programmer's Reference.
Reason:
An unexpected end of data condition was encountered when accessing the SYSOUT group on secondary disk storage.
Action:
Delete and re-archive the SYSOUT group.
Reason:
The SYSOUT group is identified in the master index as residing on secondary disk storage, but it cannot be found there.
Action:
Delete the disk copy of the SYSOUT group to enable the tape copy to be accessed.
Reason:
The internal format of the archived SYSOUT group is in error and cannot be used.
Action:
Delete and re-archive the SYSOUT group.
Reason:
No database high-level index is specified in the SARDSK2B batch job for optical disk migration.
Action:
Rerun the job with the appropriate parameters.
Reason:
ERO (Expanded Retention Option) settings are not specified for this database.
Action:
Verify that you have implemented the Expanded Retention Option for the reports in the database.
Note: For more information, see the chapter "Expanded Retention Option" in the Reference Guide.
Reason:
No DSK2DRVR parameter is specified in the SARINIT job.
Action:
Specify the appropriate DSK2DRVR parameter for the optical device you are using.
Reason:
An error occurred loading the secondary disk driver.
Action:
Verify that the DSK2DRVR ERO initialization parameter is appropriately specified (00, 01, 02, and so on).
Reason:
An error occurred initializing the secondary (optical) disk driver.
Action:
Verify that all components of your optical system, including hardware, OAM (if it is used) and so forth, are properly working. If the problem persists, contact CA Technical Support.
Reason:
An error occurred while initializing ERO (Expanded Retention Option).
Action:
Verify that the SARPATAB DD statement is specified in your CA View started task JCL (SARSTC), and that the correct name of the table is specified.
Reason:
An error occurred while finalizing ERO (Expanded Retention Option).
Action:
Verify that your ERO table is valid. If the problem persists, contact CA Technical Support.
Reason:
The SYSOUT group was not deleted from secondary disk due to an I/O error.
Action:
See the discussion and action for the previously issued I/O error message.
Reason:
This informational message is issued every 10 minutes, when the optical migration subtask is reading the GCRs (Group Control Records) from the disk database.
Action:
None. This message is informational.
Reason:
The backup cycle began running, so the optical migration subtask stopped.
Action:
None. This message is informational.
Reason:
Since the ERO initialization parameter DSK2MIGD parameter had an N specified (no migration), optical migration has ended.
Action:
None. This message is informational.
Reason:
This message is informational.
Action:
None. This message is informational.
Reason:
The requested space has been added to the database. Physical attributes of the newly added data set are provided. Non-SMS data sets are shown as having a management, storage, and data class of NON-SMS.
Action:
None. This message is informational.
Reason:
The database was successfully renamed.
Action:
None. This is an informational message.
This message ID represents one of these messages.
Reason:
The database, index file data sets, or data file data sets were successfully deleted.
Action:
None. This is an informational message.
Reason:
The control statement has an invalid operator.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The high-level index name is missing or invalid.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The volume serial number is invalid.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The number of cylinders specification is invalid or missing.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The unit name is missing or invalid.
Action:
Correct the control statement, and then resubmit the job.
This message number represents one of the following messages:
Note: One of these messages may be issued if a lock file has been created for the database:
Reason:
A request for the status of the database was made with the SARDBASE STATUS command. Statistics on the database are presented. Depending on the options specified, statistics on the index are also presented.
Note: For more information about the STATUS control statement and the SARDBA09 index statistics, see STATUS in the chapter "Database Utilities" in the Reference Guide.
Action:
None. This message is informational.
Reason:
The database was successfully copied.
Action:
None. This is an informational message.
Reason:
The master index is successfully written to the sequential output file.
Action:
None. This message is informational.
Reason:
The online library members are successfully loaded to the database.
Action:
None. This message is informational.
Reason:
The specified operand is invalid.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The relative generation number that is specified is invalid or a backup of the relative generation does not exist.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The user is not authorized to perform the requested function.
Action:
Contact the appropriate personnel to obtain authorization to perform the function.
Reason:
The database INDEX was successfully reorganized.
Action:
None. This is an informational message.
Reason:
The database was successfully restored.
Action:
None. This is an informational message.
Reason:
The database was successfully loaded.
Action:
None. This is an informational message.
Reason:
The database was successfully unloaded.
Action:
None. This is an informational message.
Reason:
The database was successfully verified.
Action:
None. This is an informational message.
Reason:
A critical error as indicated by previous SARDBV and/or SARDVP messages disallowed successful completion of the verify process.
Action:
The recovery process must be accomplished by using the RESTORE control statement of the SARDBASE utility.
Note: For more information, see the chapter "Backing Up and Recovering the Database" in the Reference Guide.
Reason:
The lock data set was successfully allocated and formatted.
Action:
None. This is an informational message.
Reason:
The lock data set was successfully deleted.
Action:
None. This is an informational message.
Reason:
The unlock function of the SARDBASE utility attempted to release a lock held on the lock data set but no lock existed.
Action:
None. This is an informational message.
Reason:
The lock held to the lock data set was unsuccessfully released.
Action:
None. This is an informational message.
Reason:
The databases were successfully merged.
Action:
None. If the newly merged database contains backup tapes from the merge process, run the SARPAC utility to copy the SYSOUT groups on tape to new tape volumes owned by this database.
Reason:
The high-level tape index name indicated on the MERGE control statement is invalid. The tape index name is from 1 to 17 bytes and must conform to data set naming conventions.
Action:
Correct the tape index name, and then resubmit the job.
Reason:
A syntax error is present in the secondary disk driver specification of the MERGE control statement.
Action:
Verify that the secondary disk driver specification is the same as the DSK2DRVR initialization parameter. Check to see that it is the name of an accessible authorized load module.
Reason:
A syntax error is present in the secondary disk driver parameters specification of the MERGE control statement.
Action:
For the parameters required, see the chapter "Using the Optical Disk Interface" in the Reference Guide.
Reason:
This message indicates that a SARDBASE UNLOCK request was entered; however, the database does not have an associated VM lock file.
Action:
None. This is an informational message.
Reason:
The block size is invalid.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The CA View programs being used are not at the same release level as what is specified in the SARDBASE control statement.
Action:
Verify the STEPLIB or linklisted version of the programs.
Reason:
The database version has been successfully changed with the SARDBASE VERSION control statement.
Action:
None. This is an informational message.
Reason:
Database statistics were successfully calculated using the SARDBASE STATUS control statement.
Action:
None. This is an informational message.
Reason:
The keyword specified in the ADDDS control statement specifications was not a valid ADDDS keyword.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The appropriate syntax of keyword=value is not used in the ADDDS control statement specifications.
Action:
Correct the control statements to follow the keyword=value syntax, and then resubmit the job.
Reason:
The SMS data class specified in the ADDDS control statement specifications was not valid.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The SMS management class specified in the ADDDS control statement specifications was not valid.
Action:
Correct the control statement, and then resubmit the job.
Reason:
The SMS storage class specified in the ADDDS control statement specifications was not valid.
Action:
Correct the control statement, and then resubmit the job.
Reason:
CA View requires a higher genlevel for CA Common Services to perform licensing authentication.
Action:
Install a more current version of CA Common Services. For more information about CA Common Services, see the CA View Installation Guide.
Reason:
The DATA or INDEX parameter is requested on the ADDDS statement of the SARDBASE utility to indicate whether to add an index file or a data file space to the database.
Action:
Add the DATA or the INDEX parameter to the ADDDS statement and resubmit the request.
|
Copyright © 2013 CA.
All rights reserved.
|
|