Reason:
CA View supports only one type of secondary disk feature for a given database. Centera is implemented as a form of secondary disk storage and cannot be configured in a database which is also using an optical secondary disk feature. The parameters CENTADR and DSK2DRVR are mutually exclusive and only one form of secondary disk can be configured. SARINIT terminates with a return code 16.
Action:
Code either Centera configuration parameters or optical secondary disk parameters for this database.
Reason:
A subsystem request failed. The hexadecimal return code is provided.
Note: Conditions that cause error message SARJPS01 will, in turn, cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct‑To‑Tape function and a backup cycle function to terminate normally also. The Direct‑To‑Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide either to terminate the backup cycle immediately or to wait until the completion of the backup cycle.
Responding WAIT to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
A process SYSOUT request failed for the subsystem. The hexadecimal return code is provided.
A return code of X'1C' indicates an invalid destination. Verify that the destination specified with the DEST initialization option is known to JES.
Note: Conditions that cause error message SARJPS02 will, in turn, cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct‑To‑Tape function and a backup cycle function to terminate normally also. The Direct‑To‑Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide either to terminate the backup cycle immediately or to wait until the completion of the backup cycle.
Responding WAIT to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
Dynamic allocation failed for the process SYSOUT data set. The hexadecimal error and information codes are provided.
Note: Conditions that cause error message SARJPS03 will, in turn, cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct‑To‑Tape function and a backup cycle function to terminate normally also. The Direct‑To‑Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide either to terminate the backup cycle immediately or to wait until the completion of the backup cycle.
Responding WAIT to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
A subsystem open request failed. The hexadecimal error and return codes are provided.
Note: Conditions that cause error message SARJPS04 will, in turn, cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct‑To‑Tape function and a backup cycle function to terminate normally also. The Direct‑To‑Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide either to terminate the backup cycle immediately or to wait until the completion of the backup cycle.
Responding WAIT to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
A subsystem GET request failed. The hexadecimal feedback code is provided. This is normally due to a system crash while the job that created the data set was executing.
Note: For RPL=08022C, the problem is usually attempting to send a line longer than 32767 bytes.
Action:
None. This is an informational message.
Reason:
A subsystem request failed. The return code is provided.
Note: Conditions that cause error message SARJSA01 will, in turn, cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct‑To‑Tape function and a backup cycle function to terminate normally also. The Direct‑To‑Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide either to terminate the backup cycle immediately or to wait until the completion of the backup cycle.
Responding WAIT to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
A process SYSOUT request failed for the subsystem. The return and reason codes are provided. For an explanation of the reason and return codes, refer to the operating system IAZSSS2 macro.
A return code of 32 and a reason code of 36 indicate an invalid destination. Verify that the destination specified with the DEST initialization option is known to JES.
Note: Conditions that cause error message SARJSA02 will, in turn, cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct‑To‑Tape function and a backup cycle function to terminate normally also. The Direct‑To‑Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide either to terminate the backup cycle immediately or to wait until the completion of the backup cycle.
Responding WAIT to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
Dynamic allocation failed for the process SYSOUT data set. The hexadecimal error and information codes are provided.
Note: Conditions that cause error message SARJSA03 will, in turn, cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct‑To‑Tape function and a backup cycle function to terminate normally also. The Direct‑To‑Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide either to terminate the backup cycle immediately or to wait until the completion of the backup cycle.
Responding WAIT to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
A subsystem open request failed. The return code and hexadecimal error code is provided.
Note: Conditions that cause error message SARJSA04 will, in turn, cause the started task to perform normal termination.
The normal termination of SARSTC (the CA View started task) causes the Direct‑To‑Tape function and a backup cycle function to terminate normally also. The Direct‑To‑Tape function terminates after completion of the current SYSOUT processing if one is in progress.
A backup cycle is also terminated if one is in progress but based on the response of the operator to the SARBKU07 message. SARBKU07 requests the operator to decide either to terminate the backup cycle immediately or to wait until the completion of the backup cycle.
Responding WAIT to the SARBKU07 message can cause an unwanted delay in restarting the CA View started task.
Action:
Contact your systems programmer.
Reason:
A subsystem GET request failed. The hexadecimal feedback code is provided. This is normally due to a system crash while the job that created the data set was executing.
Note: For RPL=08022C, the problem is usually attempting to send a line longer than 32767 bytes.
Action:
None. This is an informational message.
Reason:
A Scheduler JCL Facility request failed trying to obtain output statement attributes for a SYSOUT data set. The hexadecimal return code is provided. No output statement attributes are obtained for the SYSOUT.
Action:
None. This is an informational message.
Reason:
During network input processing, the product was unable to positively identify the version of JES2 being used to locate the JES2 PDDB, which is required to obtain SYSOUT information. The product continues processing assuming OS/390 V2R10 or higher is being used. This is a WARNING error only. It can occur only during network input processing and would, most likely, occur after an MVS and/or JES2 upgrade.
Action:
Determine if network input processing is functioning correctly. The JES2 PDDB can change with the release of JES2. Check the CA Technical Support web site, supportconnect@ca.com, to ensure that you have applied the solutions that are needed for your release of the operating system.
Reason:
The parameter value is invalid due to one of the following conditions:
Action:
Correct the value and resubmit the Metrics job.
Reason:
The parameter value is invalid due to one of the following conditions:
Action:
Correct the value and resubmit the Metrics job.
Reason:
The parameter value is invalid due to one of the following conditions:
Action:
Correct the value and resubmit the Metrics job.
Reason:
The parameter value is invalid due to one of the following conditions:
Action:
Correct the value and resubmit the Metrics job.
Reason:
The parameter is not located on the first parameter statement.
Action:
If the user does not wish to copy to a work file, remove this parameter statement. If the user does wish to copy the input file, make certain that this parameter statement is specified as the first in the group.
Reason:
The parameter specified value is repeated in the previous parameter statement.
Action:
Remove the parameter statement containing the duplicate RPT value and resubmit the Metrics job.
Reason:
The maximum number of control statements to execute at one time is four.
Action:
Remove the extraneous statements and resubmit the Metrics job.
Reason:
An error occurred during loading of a report program.
Action:
Resubmit the Metrics job. If the condition persists, contact CA Technical Support.
Reason:
An error occurred during the processing of SMF record subtypes.
Action:
Rerun the Metrics job. If the condition persists, contact CA Technical Support.
Reason:
Either RECFM, LRECL, or BLKSIZE has been omitted for the output file. Default attributes have been used.
Action:
Verify that the default attributes are wanted.
Reason:
The output file has been assigned an invalid DCB attribute.
Action:
Correct the DCB specifications for the output file.
Reason:
An invalid generation number has been passed to the program in the parm field.
Action:
Correct the problem and start SARMFP again.
Reason:
The SARMFPUX user exit did not select any GCR records. SARMFP issues return code 4 for the step.
Action:
Do one of the following options:
Reason:
One of the options, MSORT1, MSORT2, and so on, contains an invalid value. The field is ignored and processing continues.
Action:
Correct the option.
Reason:
The program load modules and the database are not of the same release level. CA View does not execute.
Action:
Correct the problem and retry.
Reason:
The online interface LMP key is invalid.
Action:
Verify that your LMP code and product code are correctly specified (in CAIRIM) for the online feature that you are attempting to use. For complete instructions on how to set up your LMP keys, see the chapter "Configuring Your Product" in the Installation Guide.
Reason:
The product code is invalid.
Action:
Verify that your product code and LMP code are correctly specified (in CAIRIM) for the feature that you are attempting to use.
Note: For more information about the instructions on how to set up your LMP keys, see the chapter "Configuring Your Product" in the Installation Guide.
Reason:
CAIRIM is not started or initialized before the starting of SARSTC.
Action:
If CAIRIM is not started, start it. If CAIRIM is initialized within 15 minutes of the first message being issued, no action is required.
If CAIRIM is not initialized within 15 minutes of the first message being issued, you receive the SARMHL99 error message. See the action for the SARMHL99 message.
Reason:
CAIRIM is not started or is at an incorrect genlevel.
Action:
Start CAIRIM. When you receive the INITIALIZED message in CAIRIM, restart SARSTC. If you are at an incorrect genlevel of CAIRIM, apply genlevel maintenance on CAIRIM before starting SARSTC.
Reason:
This message indicates a logic error with interconnection of internal product routines.
Action:
Contact CA Technical Support.
Reason:
An attempt is made to retrieve the indexes for a report, but the report is not indexed.
Action:
None. Only the native view of the report is accessible.
Reason:
An attempt is made to retrieve the indexes for a report, but the report is not indexed.
Action:
None. Only the native view of the report is accessible.
Reason:
The program load modules and the database are not of the same release level. CA View does not execute.
Action:
Correct the problem and retry.
Reason:
The translation table (xxxxxxxx) as specified by SARINIT parameter CODEPAGE cannot be loaded. The system uses the default CODEPAGE EBCCP037.
Action:
Ensure that SARINIT parameter CODEPAGE has been properly defined. If CODEPAGE has been defined, CA View libraries have probably lost authorization (that is, ISPF startup procedures).
Reason:
The Expanded Retention Option (ERO) has never been initialized, sets return code 16.
Action:
Run SARINIT to initialize the Expanded Retention Option.
Reason:
Another consolidation task with the same database is already executing, sets return code 16.
Action:
Correct the problem.
Reason:
The database indicates that a tape consolidation job (SARPAC) is already active on system 'xxxx'. This message can also be issued if a tape consolidation job (SARPAC) terminated with an ABEND or the system crashed the last time a tape consolidation job (SARPAC) was active.
Action:
Verify whether a tape consolidation job (SARPAC) is active on the specified system. If it is active, reply N to terminate this job; if it is not active, reply Y to continue.
Replying N causes message SARPAC03 to be displayed and return code 16 set.
Important! Never run a tape consolidation job (SARPAC) for the same database on more than one system at the same time because this can destroy the database's master index.
Reason:
An error occurs while reading the input tape, sets return code 8.
Action:
See the associated SARTPIxx message.
Reason:
An error occurs while writing to the output tape, sets return code 16.
Action:
See the associated SARTPOxx message.
Reason:
No SYSOUT groups are on expired CA View backup tapes; therefore, consolidation is not necessary, sets return code 4.
The return code is set to 4 when this message is issued.
Action:
None. This is an informational message.
Reason:
Tape consolidation has completed and copied xxxxx SYSOUT groups, sets return code 0.
Action:
None. This is an informational message.
Reason:
The program load modules and the database are not of the same release level, sets return code 16.
Action:
Correct the problem and retry.
Reason:
Optional SYSIN control statements are being used for this run of SARPAC, set return code 0.
Action:
None. This is an informational message.
Reason:
SYSIN control statements did not specify either a storage group or tape sequence number, sets return code 16.
Action:
Either remove the optional SYSIN DD statement, or use the TAPESEQ= or STORGRP= control statement.
Reason:
Only one STOPGRP= or one TAPESEQ= control statement is valid as SYSIN, sets return code 16.
Action:
Use only one control statement for each run of SARPAC. You can run SARPAC multiple times to accomplish the desired result.
Reason:
SYSIN control statement STORGRP= specified a storage group whose definition does not currently exist in the database using the SARINIT parameter's STORGRPn, sets return code 16.
Action:
Check the storage group name for misspelling. If the storage group name is correct, be sure that the database name is correct. The storage group name must be correct, and a backup cycle must have run to set the storage group name in the reports in the database. SARPAC does not read the ERO table directly.
Reason:
The tape sequence number that is specified on the TAPESEQ control statement contains invalid characters. Or, no tape control records are found in the database that match the specified tape sequence number or range of tape sequence numbers, sets return code 16.
Action:
Change the tape sequence number specification on the TAPESEQ control statement to reference an existing tape sequence number, and resubmit the job.
Reason:
The database contains references to tape volumes owned by another database, sets return code 16. This condition is the result of a database merge.
Note: This message continues to appear even after all tape volumes have been copied until the started task backup cycle is executed.
Action:
Run SARPAC, as necessary, to copy the SYSOUT groups on tape to new tape volumes owned by this database, and then execute a backup cycle.
Reason:
The SARPAC parameter must be VIEW-database-name,REPORT, or VIEW-database-name. The parameter specified was not the keyword REPORT, sets return code 16.
Action:
Correct the parameter and rerun.
Reason:
A modify command is issued against the SARPAC job but the parameter "xxxx" is not a valid command, does not set a return code.
Action:
Correct the modify command.
Reason:
A "STOP" modify command is issued against the SARPAC job, SARPAC terminates once the current report is moved to the output tape, does not set a return code.
Action:
None. This message is informational.
Reason:
The operator has issued a STOP command to terminate SARPAC.
Action:
SARPAC will terminate normally after the completion of the current report.
Reason:
The program load modules and the database are not at the same release level. CA Deliver-direct-to-CA View archival does not operate.
Action:
Set the version of the database (with the VERSION control statement of the SARDBASE utility) to the current release level, and then resubmit the job.
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 maximum number of lines (as defined by the MAXLINES initialization parameter for reports defined to CA Deliver as Direct-to-CA View) has been exceeded. Records in excess of the specified limit are discarded. If the report is designated for printing, the entire report is printed.
Action:
None. This message is informational.
Reason:
The database has no more space to hold direct-to-CA View archival reports from CA Deliver.
Action:
Create more space in the database by either deleting SYSOUTS or adding more space to the database by either ADDDS or SARDBASE. Reply R to retry or reply T to terminate (abend) the application job.
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 sequential numbers 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 format of SARPAM25 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 SARPAM25 message can be reissued after replying T and re-starting the application job.
Reason:
When report data is being written directly to a CA View database and the job abends, is canceled, or times out, outstanding I/O requests can be pending for the database. To avoid potential corruption of the database, all I/O requests to the database are completed.
Action:
None. This message is informational.
|
Copyright © 2013 CA.
All rights reserved.
|
|