Reason:
The CA Spool Java Transformation request failed.
Action:
Determine if additional messages were written at the time of the error that could provide information regarding the cause of the failure. Check the transformation report to determine the cause of the problem.
Reason:
The message shows that a JES document has been selected for processing by the PDF FSS Collector. The message also displays when the processing of the PDF document has completed.
Action:
None.
Reason:
A JES document has been sent to a PDF Collector, which is not a PDF document. The report is placed on hold.
Action:
Re-route the JES document to the correct JES printer definition to process correctly.
Reason:
A parameter in the View printer definition is in error, the invalid parameter is displayed.
Action:
Correct the invalid parameter and restart the JES printer.
Reason:
A parameter value in the View printer member is invalid. The invalid parameter and value are displayed.
Action:
Correct the invalid value in the View printer member and restart the JES printer to validate the changes made.
Reason:
A value in the View printer member for the NAME parameter has not been specified or has been specified incorrectly.
Action:
Correct the invalid value in the View printer member NAME parameter and restart the JES printer to validate the changes made.
Reason:
A JES form name is specified on the processed document but a member with this same name was not found in the PDFINDEX dataset specified in the PDF Collector FSS proc. This member is used for indexing the PDF document.
Action:
Add a member with the form name in the PDFINDEX dataset. If no indexing is required, then either remove the form name from the JES document or add the member with no parameters.
Reason:
There is no PDFINDEX DD specified in the PDF Collector FSS PROC being used by the JES printer definition.
Action:
Add the PDFINDEX DD in the PROC associated with the JES printer being used for the PDF collection. Restart JES printer to verify change.
Reason:
The CA View database name specified in the printer member is not at the required release to support PDF Indexing. The database must be at release 11.5 or later.
Action:
Specify either the correct database name or version the database up to r11.5.
Reason:
There was an error in the processing of a PDF document and it cannot be indexed correctly into the database. A more detailed error message was issued prior explaining the reason for the error.
Action:
Review the error message issued before you determine the problem. Correct the problem and release the held PDF document from the JES queue to be processed through the PDF Collector.
Reason:
The specified DD could not be opened. Either the DD specified in the PDFINDEX member associated with this report is not included in the PDF Collector FSS proc, or it was specified incorrectly.
Action:
Review your PDFINDEX member and your PDF Collector FSS proc, make the necessary corrections, restart the JES printer if necessary and release the held PDF document.
Reason:
The SYSOUT line count exceeds the database MAXLINES initialization parameter value.
Action:
None. This message is informational.
Reason:
An I/O error occurs while writing out the index data for the SYSOUT group. Any index data that is already written is deleted.
Action:
Correct the error with the database.
Reason:
The MAXOBJCT parameter in the specified PDFINDEX member does not contain a numeric value or is not specified with a value from 1 to 2097151.
Action:
Correct the MAXOBJCT parameter so that it contains a value from 1 to 2097151.
Reason:
The MEMORY parameter in the PDFINDEX DD member does not contain a numeric value or is not specified with a value from 1 to 2097151.
Action:
Correct the MEMORY parameter so that it contains a valid value from 1 to 2097151.
Reason:
An invalid keyword has been specified in the PDFINDEX member associated with the report being processed. The invalid keyword is displayed.
Action:
Correct the invalid keyword and release the held JES document.
Reason:
This message lists all of the keywords and values from the associated PDFINDEX member for the PDF document being processed. The indexing member name used is shown in the displayed message (membername).
Action:
None.
Reason:
The option specified on the trace command is invalid.
Action:
Correct the value specified for the TRACE option and release the held PDF document from the JES queue to process correctly.
Reason:
There is not enough space in the database to perform the archival.
Action:
Reply with either an R to reattempt archival or a T to terminate:
This message number represents one of the following messages:
Reason:
Each unique report Id can have up to 65,535 copies per database generation. A 'generation' being the time between Full Backup Cycles. Each unique report id in a generation is assigned a sequential number from 1 to 65,535. After 65,535, the sequence number will wrap back to zero and 'date selection'problems will occur. This message gives the user a chance to run a backup cycle so this number can be reset to one.
The second message of CAHPDF19E is displayed if a response other than 'R' or 'T' is made to the original message.
Action:
Reply with either an R after a backup cycle has been started or a T to terminate. The CAHPDF19E message can be reissued after replying T and re-starting the PDF FSS Collector.
Reason:
The PDF document that is being processed requires more memory to process the complete document.
Action:
Adjust the MEMORY= parameter in the PDFINDEX member to a larger value. Memory = ### is the number of 1-KB blocks of memory for this document, that is, ###=96801 X 1024 = 99124224 = 94-MB. For more information, see the chapter titled 'PDF Indexing in CA View' in the Reference Guide.
Reason:
The PDF document being processed requires more MAXOBJCT to process the complete document.
Action:
Adjust the MAXOBJCT in the PDFINDEX member to a larger value. MAXOBJT=### is the maximum number of objects for the document, that is ###=1500 is the maximum number of objects. Change this number to a larger number and release the document from the JES queue to test new setting. For more information, see the chapter titled 'PDF Indexing in CA View' in the Reference Guide.
Reason:
The PDF document being processed is complex and has over 150 references to other objects from one or more objects.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
There are more than 100 INDEX commands specified in the PDFINDEX member associated with the report being processed.
Action:
Contact CA Technical Support.
Reason:
An INDEX statement in the PDFINDEX member associated with the report being processed contains and invalid end-of-character value.
Action:
Correct the end-of-character value and release the held PDF document from the JES queue. For more information, see the chapter titled 'PDF Indexing in CA View' in the Reference Guide.
Reason:
An INDEX command has been incorrectly formatted in the PDFINDEX member.
Action:
The invalid INDEX command is displayed in the PDF Collector FSS SARLOG report dataset. Correct the format of INDEX command and release the PDF document from the JES queue.
Reason:
All INDEX command has been incorrectly formatted in the PDFINDEX member and contains an invalid length field, which must be L(NN). NN=Numeric field.
Action:
The invalid INDEX command is displayed in the PDF Collector FSS SARLOG report dataset. Correct the format of INDEX command and release the PDF document from the JES queue.
Reason:
An INDEX command has been incorrectly formatted in the PDFINDEX DD member and contains an invalid operator expression, which must be one of those listed in the message.
Action:
The invalid INDEX command is displayed in the PDF Collector FSS SARLOG report dataset. Correct the format of INDEX command and release the PDF document from the JES queue.
Reason:
The ENDPAGE or XYPAGES parameter in the specified PDFINDEX member does not contain a numeric value or is not specified with a value from 0 to 2147483647.
Action:
Correct the ENDPAGE or XYPAGES parameter so that it contains a valid value from 0 to 2147483647.
Reason:
A PDF document to be processed has been password protected and also encrypted. It is not possible to index these types of PDF documents.
Action:
None.
Reason:
This message is displayed when a PDF document is requeued into the JES spool. An error message is written into the SARLOG report and also to SYSLOG if the ARCHMSG=YES has been specified.
Action:
Correct the error for the failing PDF document and release the JES document to process again.
Reason:
There is not enough virtual storage to allocate buffers based on the MEMORY and MAXOBJCT parameter specification. The amount of storage required is based on the following formula:
Storage = (MEMORY value * 1024) + (MAXOBJCT value * 684)
The default for MEMORY is 96801 (94 meg) and MAXOBJCT is 30000 (20 meg)
Action:
Increase the REGION size for the FSS printer or specify a lower value for the MEMORY and/or MAXOBJCT parameter. The sysout data set containing the PDF document is queued to a held status. After correcting the problem, the sysout data set can be released for subsequent archival.
Reason:
An exceptional condition identified by message occurs for the specified job.
Action:
Take appropriate action.
Reason:
The database is not opened or the SAMOPEN had failed.
Action:
Open the database or process the SAMOPEN non-zero return code with the SAMMSG function to determine why the database did not open.
Reason:
The database is not opened or the SAMOPEN had failed.
Action:
Open the database or process the SAMOPEN non-zero return code with the SAMMSG function to determine why the database did not open.
Reason:
The auxiliary sub-file is not opened or the SAMAOPN had failed.
Action:
Open the auxiliary sub-file or process the SAMAOPN non-zero return code with the SAMMSG function to determine why the auxiliary sub-file did not open.
Reason:
Reading the auxiliary sub-file has resulted in End of File.
Action:
This is an expected condition.
Reason:
The database is not opened or the SAMOPEN had failed.
Action:
Open the database or process the SAMOPEN non-zero return code with the SAMMSG Function to determine why the database did not open.
Reason:
The control element (such as Sysout) does not have an auxiliary sub-file (page separation index) or the auxiliary sub-file is no longer on the database.
Action:
Verify that the element can contain an auxiliary sub-file and that the auxiliary sub-file is on the database.
Reason:
The auxiliary sub-file is opened while the data is being archived or a system failure has left an auxiliary sub-file in open status.
Action:
If the data is being archived, wait for the completion of the archival function. If the auxiliary sub-file was left in open status, the Sysout must be deleted.
Reason:
The application user does not have authority to read the sub-file.
Action:
Add Browse authority to the application user for this Sysout.
Reason:
The database is not opened or the SAMOPEN had failed.
Action:
Open the database or process the SAMOPEN non-zero return code with the SAMMSG Function to determine why the database did not open.
Reason:
The SAMGET parameter list did not contain a correct GET Function Code.
Action:
Correct the GET Function Code and rerun the SARSAM application. The valid GET Function codes are:
Reason 1:
The SAMGET function requested a record which was not found.
Action 1:
This maybe an expected condition or the record no longer exists in the database, such as a Tape Control Record (TCR) for an expired tape.
Reason 2:
The application is reading the index backwards and all records have been read, this is the reverse of reaching 'End of File' while reading forward.
Action 2:
This is an expected condition when reading backwards.
Reason 3:
The application is reading the index forwards all records have been read.
Action 3:
This is an expected condition.
Reason:
The database is not opened or the SAMOPEN had failed.
Action:
Open the database or process the SAMOPEN non-zero return code with the SAMMSG Function to determine why the database did not open.
Reason:
The USER ID associated with the SARSAM application program is not defined in the database (DEF USER) and the default user mode is 'NNNNN'.
Action:
Add the USER ID to the database using the SARBCH/DEF USER Command.
Reason:
The database is not opened or the SAMOPEN had failed.
Action:
Open the database or process the SAMOPEN non-zero return code with the SAMMSG Function to determine why the database did not open.
Reason:
The database is not opened or the SAMOPEN had failed.
Action:
Open the database or process the SAMOPEN non-zero return code with the SAMMSG Function to determine why the database did not open.
Reason:
The sub-file is not opened or the SAMSOPN had failed.
Action:
Open the sub-file or process the SAMSOPN non-zero return code with the SAMMSG Function to determine why the sub-file did not open.
Reason:
Reading the sub-file has resulted in End of File.
Action:
This is an expected condition.
Reason:
The database is not opened or the SAMOPEN had failed.
Action:
Open the database or process the SAMOPEN non-zero return code with the SAMMSG Function to determine why the database did not open.
Reason:
The control element (such as Sysout) does not have a sub-file or the sub-file is no longer on the database.
Action:
Verify that the element can contain a sub-file and that the sub-file is on the database.
Reason:
The sub-file is opened while the data is being archived or a system failure has left a sub-file in open status.
Action:
If the data is being archived, wait for the completion of the archival function. If the sub-file was left in open status, the Sysout must be deleted.
Reason:
The application user does not have authority to read the sub-file.
Action:
Add Browse and All Pages authority to the application user for this Sysout.
Reason:
The user has misused or misspelled parameter xxxxxx in the member yyyyyyyy. The parameter has been ignored.
Action:
Correct parameter xxxxxx in the member yyyyyyyy.
Reason:
The SVC screening product must be initialized, it cannot be found.
Action:
Verify that the SVC screening product is available.
Reason:
The APKACIF module cannot be found in your IBM target libraries.
Action:
Verify that the STEPLIB statement is concatenated to CAI.CVDELOAD, or verify that they are both in the LNKLST.
Reason:
A keyword is misspelled in the //PRTnnn statement.
Action:
Correct the keyword, and then resubmit the job.
Reason:
A keyword is assigned an invalid value.
Action:
Correct the keyword, and then resubmit the job.
Reason:
The database name specified as the NAME statement was not found.
Action:
Correct the name, and then resubmit the job.
Reason:
Either the index member name was misspelled or it does not exist.
Action:
Correct the name, and then resubmit the job.
Reason:
There is a media problem.
Action:
Verify that the volume is online and functioning properly.
Reason:
The database is not at the appropriate level.
Action:
Verify that your database level (set with the SARDBASE utility) is correct, then rerun SARDBASE if necessary.
Reason:
An error came back from ACIF, the return code is provided.
Action:
Check the IBM documentation on APKACIF messages.
Reason:
The RACROUTE request returned with an error code indicating that the security rules do not permit access to the userlib.
Action:
Ensure that the userlib is correctly specified and/or change the security rules for it.
Reason:
This message is informational.
Action:
None. This message is informational.
Reason:
There is not enough space in the database to perform the archival.
Action:
Reply with either an R to reattempt archival or a T to terminate:
This message number represents one of the following messages:
Reason:
Each unique report id can have up to 65,535 copies per database generation. A 'generation' being the time between Full Backup Cycles. Each unique report id in a 'generation' is assigned a sequential number from 1 to 65,535. After 65,535, the sequence number wraps back to zero and date selection problems will occur. This message gives the user a chance to run a backup cycle so this number can be reset to one.
The second format of SARACI25 is displayed if a response other than 'R' or 'T' is given to the original message.
Action:
Reply with either an R after a backup cycle has been started or a T to terminate. The SARACI25 message can be reissued after replying T and re-starting the ACIF FSS Collector.
Reason:
An I/O error occurred at job initiation when an attempt is made to update the job accounting data set.
Action:
If this error persists, recreate the job accounting data set.
Reason:
Userid is not authorized to access the requested resource for the specified CLASS and ENTITY value. SARATH92 messages is only displayed when the SARINIT FEATURE=1 parameter is specified.
Action:
Consult with your security administrator or systems programming group to determine the reason why the authorization was not granted.
Reason:
User Logon has completed successfully.
task – DRAS
ROSCOE
VTAM
XMS/CICS
XMS/IMS
XMS/TSO
XMS/SPF
userid - the User's id
Action:
None. This message is informational.
Reason:
User Logon was successfully completed.
task – DRAS
ROSCOE
VTAM
XMS/CICS
XMS/IMS
XMS/TSO
XMS/SPF
userid - the User's id
Action:
None. This message is informational.
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 bundle was successfully produced.
Action:
None. This message is informational.
Reason:
The requested SYSOUT group does not exist in the master index. This is normally caused by a backup cycle deleting the SYSOUT group before completion of the bundling 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 all SYSOUT groups, change, or omit any nonexistent SYSOUT groups, then resubmit the bundle reprint request.
Reason:
The BID parameter was not specified and is required on the control statement.
Action:
Add the BID parameter to the /BPRINT control statement, and then resubmit the bundle reprint request.
Reason:
The BCONT parameter was not specified and is required on the control statement.
Action:
Add the BCONT parameter to the /BPRINT control statement, and then resubmit the bundle reprint request.
Reason:
The syntax of the BCONT parameter is invalid. Null parameter data, invalid character data, or excessive parentheses or commas usually cause these.
Action:
Review the syntax of the BCONT parameter on the /BPRINT control statement, correct the parameter specification, and then resubmit the bundle reprint request.
Reason:
The specified distribution identifier contains too many characters. The distribution identifier on the BCONT parameter must be from 1 to 32 characters in length.
Action:
Review the syntax of the BCONT parameter on the /BPRINT control statement, correct the parameter specification, and then resubmit the bundle reprint request.
Reason:
The specified report identifier contains too many characters. The report identifier on the BCONT parameter must be from 1 to 32 characters in length.
Action:
Review the syntax of the BCONT parameter on the /BPRINT control statement, correct the parameter specification, and then resubmit the bundle reprint request.
Reason:
The specified report identifier is not defined to the specified bundle in the CA Deliver Output Management database because the report identifier was incorrectly named, was deleted from the bundle before completion of the bundle reprint request, or is never defined to the bundle.
Action:
Review the bundle definition in CA Deliver, change or delete the report identifier specification, and then resubmit the bundle reprint request.
Reason:
The specified distribution identifier is not defined to specified report in the CA Deliver database because the distribution identifier was incorrectly named, was deleted from the report before completion of the bundle reprint request, or is never defined to the report.
Action:
Review the bundle definition in CA Deliver, change or delete the distribution identifier specification, and then resubmit the bundle reprint request.
Reason:
The specified generation contains too many characters. The generation field in the BCONT parameter must be 1 to 5 characters in length.
Action:
Review the syntax of the BCONT parameter on the /BPRINT control statement, correct the parameter specification, and then resubmit the bundle reprint request.
Reason:
The specified generation contains invalid characters. The generation field in the BCONT parameter specifies an absolute or relative numeric value.
Action:
Review the syntax of the BCONT parameter on the /BPRINT control statement, correct the parameter specification, and then resubmit the bundle reprint request.
Reason:
The specified sequence number contains too many characters. The sequence number field in the BCONT parameter must be 1 to 5 characters in length.
Action:
Review the syntax of the BCONT parameter on the /BPRINT control statement, correct the parameter specification, and then resubmit the bundle reprint request.
Reason:
The specified sequence number contains invalid characters. The sequence number field in the BCONT parameter specifies an absolute or relative numeric number.
Action:
Review the syntax of the BCONT parameter on the /BPRINT control statement, correct the parameter specification, and then resubmit the bundle reprint request.
Reason:
I/O operation against the CA Deliver database failed. The error message can range from a severe error condition such as physical or logical I/O error to non-severe error condition such as record not found or database not defined.
Action:
If a database not found message is produced, verify that the EXPRESS initialization parameter references the correct database. If a record not found message is produced, the respective identifier may have to be removed from the bundle reprint request. Consult the CA Deliver documentation to remedy severe error conditions.
Reason:
The SARDSTUX user exit did not allow the bundle 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 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 reasons 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 changed, and then resubmit the print request.
Reason:
The SYSOUT group is successfully updated with the requested information.
Action:
None. This message is informational.
Reason:
The requested SYSOUT group does not exist in the master index. A misspelled SYSOUT identifier normally causes this, the SYSOUT group was manually deleted from the online or batch retrieval facilities, or the backup cycle deleted the SYSOUT group before the completion of the change process.
Action:
Verify the existence of the SYSOUT group. If the SYSOUT identifier (ID), generation number (GEN), and/or sequence number (SEQ) was specified incorrectly, change the parameter specification, then resubmit the change request.
Reason:
The BACKUP=OFF parameter is specified on the change request to reset the tape backup indicator. When the tape backup indicator is reset, the SYSOUT group is re-archived to tape during the next backup cycle. The backup cycle requires that the SYSOUT group reside on disk, but the SYSOUT group specified on the change request does not currently reside on disk.
Action:
If the change request is being requested against the correct SYSOUT group, the SYSOUT group can be reloaded to disk using the LOAD request of the SARBCH utility.
Reason:
The DELETE=OFF parameter is specified on the CHANGE request to reset the delete indicator for the SYSOUT group, but the SYSOUT group is not currently in a delete status.
Action:
Verify that the correct SYSOUT group is being referenced on the change request. If additional parameters are being changed, remove the DELETE=OFF parameter, then resubmit the change request.
Reason:
A SARBCH /CHANGE ARCHDATE function is trying to determine the new generation and sequence number for the report which is being back-dated and an error has occurred in the database which has prevented this process to successfully complete.
Action:
Save all the documentation associated with the job, run a SARDBASE IDXOUT and TERSE the output file, and notify CA Technical Support.
Reason:
A SARBCH /CHANGE ARCHDATE function is trying to determine the new generation and sequence number fir report which is being back-dated and an error has occurred in the database which has prevented this process to successfully complete.
Action:
Save all the documentation associated with the job, run a SARDBASE IDXOUT and TERSE the output file, and notify CA Support.
Reason:
A SARBCH /CHANGE Statement was provided and the ARCHDATE parameter has either an invalid format or an invalid month, day, or year.
Action:
Correct the format error and re-run the job.
Reason:
A SARBCH /CHANGE Statement was provided and the ARCHDATE parameter has date which is higher than the current date. Reports can be 'back-dated' but cannot be 'forward-dated."
Action:
Correct the date to a previous date and re-run the job.
Reason:
A SARBCH /CHANGE Statement is provided with an ARCHDATE parameter and some other CHANGE parameter. The archival date is the only change that can be made to the Sysout and the other parameters are ignored.
Action:
The other changes can be specified on a second /CHANGE Statement if desired.
Reason:
A SARBCH /CHANGE Statement is provided with an ARCHDATE parameter and the function completed successfully, the old generation number, sequence number, archival date and time, and the new generation number, sequence number, archival date and time are displayed in the message.
Action:
None, informational message.
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 disk space, if any, occupied by the requested SYSOUT group and the respective master index references have been successfully deleted from the database.
Action:
None. This message is informational.
Reason:
The disk space occupied by the requested SYSOUT group has been successfully deleted from the database. The SYSOUT group resides in non-disk status.
Action:
None. This message is informational.
Reason:
The requested view(s) were successfully deleted from the master index.
Action:
None. This message is informational.
Reason:
The requested user ID and all associated online variables were successfully deleted from the master index.
Action:
None. This message is informational.
Reason:
The disk space occupied by the report index for the requested SYSOUT group has been successfully deleted from the database.
Action:
None. This message is informational.
Reason:
The requested device or filter was successfully deleted from the master index.
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 delete process, or the manual deletion of the SYSOUT group by using the online retrieval facility or batch retrieval facility (SARBCH).
Note: A generic SYSOUT identifier cannot be specified in the delete request.
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 respective parameters, and then resubmit the delete request.
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 deleted, then resubmit the delete request.
Reason:
The disk space for the requested SYSOUT group was not deleted 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, and then resubmit the delete request. If the open condition is invalid (for example, 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:
The disk space for the requested SYSOUT group was not deleted because the SYSOUT group has no tape or optical archival copy. If the delete request was honored, the SYSOUT group would not have any archival copy and would therefore render it useless.
Action:
Wait until the completion of the backup cycle, or the next run of the optical migration subtask, and then resubmit the delete request.
Reason:
The SYSOUT group does not reside on disk. This is normally caused by a backup cycle deleting the disk space for the SYSOUT group before completion of the delete request, or another user or job deleted the disk space by using the online retrieval facility or batch retrieval facility (SARBCH). See the initialization parameter NGEND for more information.
Action:
None; since the SYSOUT group no longer resides on disk, the original intent of the delete disk request has been satisfied.
Reason:
The SYSOUT group cannot be deleted because it resided on secondary disk storage, and no secondary disk storage driver was available.
Action:
Run SARINIT to redefine the secondary disk storage driver.
Reason:
The VIEW parameter is incorrectly specified without a view number.
Action:
Change the VIEW parameter to include the view number that is to be deleted or * to delete all views, and then resubmit the delete request.
Reason:
The VIEW parameter cannot be specified with the DISK, GEN, SEQ, and/or INDEX parameters.
Action:
Either remove the VIEW parameter or remove the DISK, GEN, SEQ, and/or INDEX parameters from the control statement, then resubmit the delete request.
Reason:
The requested view does not exist in the master index. This is normally caused by an incorrect specification of the ID parameter and/or the VIEW parameter, or another user or job already deleted the view by using the online retrieval facility or batch retrieval facility (SARBCH).
Action:
Verify the existence of the view. If the view (VIEW parameter) or SYSOUT identifier (ID parameter) was specified incorrectly, change the parameter specification, and then resubmit the delete request.
Reason:
The USER parameter is incorrectly specified without a user ID.
Action:
Change the USER parameter to include the user ID that is to be deleted, and then resubmit the delete request.
Reason:
The USER parameter cannot be specified with the DISK, GEN, ID, SEQ, and/or INDEX parameters.
Action:
Either remove the USER parameter or remove the DISK, GEN, ID, SEQ, and/or INDEX parameters from the control statement, and then resubmit the delete 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).
Note: A generic user ID cannot be specified in the delete request.
Action:
Verify the existence of the user ID. If the user ID (USER) parameter was specified incorrectly, change the parameter, and then resubmit the job.
Reason:
The user ID extracted by the SARUSBUX does not have sufficient authority (master authority) to delete user IDs from 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 user re-indexed a Sysout Group (with the 'I' command or the Batch '/INDEX' command) and the Sysout Group has not been re-written to the backup tape.
Action:
Wait for the backup cycle to complete or force a new backup cycle and retry the command.
Reason:
The SYSOUT group is a resource group and resource groups cannot be deleted.
Action:
Add the 'DISK' parameter to the /DELETE statement and rerun the step.
This message number represents one of the following:
Reason:
The SYSOUT identified in the DELETE command is in OPEN status. The job can still be running and the command requires the confirmation to delete the SYSOUT.
Action:
Reply with either a Y if the job is not running and the delete must continue normally or C to cancel the delete function.
Reason:
The user responded C to message SARBCD30.
Action:
None.
Reason:
The SYSOUT is in OPEN status and cannot be deleted.
Action:
Use the FORCE parameter on the DELETE command and confirm that the job is not running.
Action:
The DELETE function fails because it violates REGDAYS retention for this report
Reason:
The copy of the report you are trying to delete is controlled by REGDAYS retention – it cannot be deleted.
Reason:
The DEV parameter cannot be specified with the DISK, GEN, ID, SEQ, INDEX, VIEW and/or USER parameters.
Action:
Either remove the DEV parameter or remove the DISK, GEN, ID, SEQ, INDEX, VIEW and/or USER parameters from the control statement, and then resubmit the delete request.
Reason:
The requested device or filter does not exist in the master index. This is usually caused by an incorrect specification of the DEV or FILT parameter, or the device or filter 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 device or filter. If the DEV or FILT parameter was specified incorrectly, change the parameter and resubmit the job.
Reason:
The user ID extracted by the SARUSBUX does not have sufficient authority (master authority) to delete the device or filter from the database. The user ID that requires authority is indicated in a previous (SARBCH05) message.
Action:
Consult your security administrator or systems programming group to determine the reason why the authorization was not provided.
|
Copyright © 2013 CA.
All rights reserved.
|
|