SARICF02

ICSF error - Service=xxxxxxxx RC=nnn Reason=nnn Entry=nnn

Reason:

ICSF has returned an error code. The return and reason codes are described in Appendix A of the IBM publication ICSF Application Programmers Guide (SA22-7522).

xxxxxxxx is the name of the ICSF service that failed.

Action:

For assistance, contact Technical Support at http://ca.com/support.

SARICF03

ICSF not active - Service=xxxxxxxx RC=nnn Reason=nnn Entry=nnn

Reason:

The ICSF services task is not active or available. The return and reason codes are described in Appendix A of the IBM publication ICSF Application Programmers Guide (SA22-7522).xxxxxxxx is the name of the ICSF service that failed.

Action:

Ensure that ICSF is running on the system where the error occurred.

SARICF04

ICSF not installed - Service=xxxxxxxx Entry=nnn

Reason:

The ICSF service routine xxxxxxxx is not resident in the link list. During ICSF installation, the ICSF service routines are placed in the link list and made available to all applications. The non-availability of the service routine indicates that ICSF has not been installed.

Action:

Ensure that ICSF is installed correctly. For assistance, contact Technical Support at http://ca.com/support.

SARICF05

ICSF key xxxxxxxx not found - Entry=nnn

Reason:

CA View has requested the above key from the ICSF key store (CKDS) and it was not found. This type of error occurs when the CKDS has been restored to an old version or multiple CKDS data sets are used for the same CA View database.

xxxxxxxx is the name of the missing key

Action:

Contact Technical Support at http://ca.com/support to determine if the key can be recovered and the extent of the data loss.

SARIFP01

Invalid group control record, ID=reportid, Gen=xxxx, and Seq=xxxx encountered, program terminated

Reason:

An attempt is made to add or update a SYSOUT group index record with an invalid generation and sequence number. Processing is terminated with a USER 100 abend.

Action:

If this occurs during a SARDBASE REORG, the program automatically corrects the error and you can ignore this message. If bad records reside in the database from prior releases of the product, correct the database with the VERIFY control statement from the SARDBASE utility. Otherwise, the processing can be resumed.

For assistance, contact Technical Support at http://ca.com/support.

SARIFP02

Critical error, program terminated with dump. Invalid blk

Reason:

A CA View program has terminated, and a dump was generated. In this message, blk specifies the control block CA View expected but did not receive (usually IFB, SFB, XFB, or DBB). It can be suffixed with a number indicating which test point in the program detected the problem.

Action:

Send the dump to CA Technical Support. Restart whatever program was terminated. If the problem recurs, run SARDBASE VERIFY on the database. For assistance, contact Technical Support at http://ca.com/support.

SARIFP03

bt-Index block corruption (et) at block dccb on database
bt - Indicates block type:
DL - Data level index block
HL - High level index block

et - Indicates error type:
HK - High key encountered in block
ID - Incorrect block identifier
IS - Index record too small
IL - Invalid index record length
KL- Incorrect key length
LK - Low key encountered in block
LN - Invalid index block length
NI - No index keys in block
SC - Invalid split count
SQ - Index records out of sequence
UN - Unknown type of index block

dccb - Block DASD location
database - Database high level prefix

Reason:

A master index block in the database contains abnormal data. This is usually due to a system failure, power outage, cancellation, or timeout.

An error type (et) of HK, LK, or SQ indicates the results of an incomplete block split. The block can be corrected as indicated by a subsequent SARIFR07 message. The applicable index records are bypassed.
The other error types indicate more severe corruption of the master index.

Action:

For #1, the error condition can be automatically corrected as indicated by a SARIFR07 message. If not, resolve this error condition by performing a standard REORG or an unload/load. For #2, resolve these problems by a database verify or restore.

SARIFP04

bt-Index block corruption at block dccb on database - corrected

bt - Indicates block type:
DL - Data level index block
HL - High level index block

dccb - Block DASD location
database - Database high level prefix

Reason:

A master index block in the database, which contains abnormal data, was corrected. When a system failure, power outage, cancellation, or timeout occurs, I/O to the master index can be interrupted while inserting index records. This condition creates inconsistencies in the master index that can be corrected. This message is preceded by the SARIFR06 message identifying the specific error.

Action:

None. This message is informational.

SARIFR02

REORG HAS PROCESSED TO KEY=xxxxxxxxxxxx

Reason:

This informational message is periodically issued to indicate the progress of an asynchronous SARDBASE REORG.

Action:

None. This message is informational.

SARIFR03

RECOVERED INDEX BLOCKS = nnnn

Reason:

This informational message specifies the number of empty blocks in the index file that have been recovered by an asynchronous SARDBASE REORG.

Action:

None. This message is informational.

SARIFR04

DATABASE AT INCORRECT LEVEL FOR THIS RELEASE

Reason:

The program load modules and the database are not at the same release level. This is normally caused by the STEPLIB, JOBLIB, linklist, or LPA pointing to old load modules, or the database has not been converted to the correct release level (new releases of product may require conversion of the database).

Action:

You can either STEPLIB to the correct load modules or convert the database to the correct release level.

SARIFR05

REORG ENDED AT KEY=xxxxxxxxxxx

Reason:

A stop command is issued during processing the SARDBASE asynchronous REORG. This message indicates where the asynchronous REORG ended.

Action:

None. This message is informational.

SARIFR06

bt-INDEX BLOCK CORRUPTION (et) AT BLOCK dccb ON database

bt - Indicates block type:
DL - Data level index block
HL - High level index block

et - Indicates error type:
HK - High key encountered in block
ID - Incorrect block identifier
IS - Index record too small
IL - Invalid index record length
KL - Incorrect key length
LK - Low key encountered in block
LN - Invalid index block length
NI - No index keys in block
SC - Invalid split count
SQ - Index records out of sequence
UN - Unknown type of index block

dccb - Block DASD location
database - Database high level prefix

Reason:

A master index block in the database contains abnormal data. This is usually due to a system failure, power outage, cancellation, or timeout.

An error type (et) of HK, LK, or SQ indicates the results of an incomplete block split. The block can be corrected as indicated by a subsequent SARIFR07 message. The applicable index records are bypassed.
The other error types indicate more severe corruption of the master index.

Action:

SARIFR07

bt-INDEX BLOCK CORRUPTION AT BLOCK dccb ON database- CORRECTED

bt - Indicates block type:
DL - Data level index block
HL - High level index block

dccb - Block DASD location
database - Database high level prefix

Reason:

Action:

None. This message is informational.

SARINA11

Open failed for accounting file

Reason:

The SARACT DD statement is not provided and is required.

Action:

Specify SARACT DD statement in execution JCL, and then resubmit the job.

SARINA12

Multiple extents for accounting file

Reason:

The accounting file has multiple extents.

Action:

Recreate the accounting file, and then resubmit the job.

SARINA22

Utility processing successfully completed

Reason:

Processing has successfully completed.

Action:

None. This is an informational message.

SARINI01

Syntax error

Reason:

The specified option statement contains a syntax error.

Action:

Correct the option statement, and then resubmit the job.

SARINI02

Option not found

Reason:

The specified option is not valid.

Action:

Correct the option; then resubmit the job.

SARINI03

Invalid value

Reason:

The specified value is invalid for the option.

Action:

Correct the value; then resubmit the job.

SARINI04

Duplicate statement

Reason:

The option has been previously specified.

Action:

Correct the problem; then resubmit the job.

SARINI05

TVSER1/TVSER2 specified without the other in the storage group

Reason:

Only one volume serial number for a range of volumes has been specified.

Action:

Correct the problem; then resubmit the job.

SARINI06

Code page "XXXXXXXX" is not available

Reason:

The CODEPAGE initialization parameter references a codepage member name that does not exist.

Action:

Ensure that the codepage name indicated on the error message resides in your STEPLIB, JOBLIB, or linklist and rerun.

SARINI07

Tape volume serial numbers do not end with a numeric

Reason:

One of the volume serial numbers for a range of tape volumes does not end with numeric characters.

Action:

Correct the volume serial number, and then resubmit the job.

SARINI08

Tape volume serial numbers are different formats

Reason:

When specifying a range of tape volumes, the volume serial numbers must be of the same format.

Action:

Correct the volume serial numbers, and then resubmit the job.

SARINI09

Secondary disk storage driver not found or not authorized

Reason:

The DSK2DRVR parameter specifies the name of a load module that cannot be found or is not authorized.

Action:

Verify that DSK2DRVR specifies the name of an authorized load module accessible to SARINIT.

SARINI10

Language code "_" is not installed

Reason:

The CA View database contains no panels for the indicated language code.

Action:

Either install the desired panels or specify a language code for panels that are already in the database.

SARINI19

Job/User not authorized to access data base

Reason:

The authorization user exit does not allow the job or user to access the database.

Action:

Consult the system programming group or security group to determine the reason why the authorization user exit explicitly denies access to the database.

SARINI20

Processing terminated due to previous errors

Reason:

Previous errors have occurred.

Action:

A '*' is displayed on the line following the invalid parameter. Correct the invalid parameter or value and retry.

SARINI22

Utility processing successfully completed

Reason:

Processing has successfully completed.

Action:

None. This is an informational message.

SARINI23

Database at incorrect level for this release

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.

SARINI24

GEN=, TAPESEQ=, DRTSEQ= only valid during first init of database; ignored

Reason:

The GEN=, TAPESEQ=, and DRTSEQ= initialization parameters can only be used for newly created databases.

Action:

None. The unacceptable parameters are ignored.

SARINI25

FINDLIM must be less than or equal to FINDMAX

Reason:

The second portion of the FINDLIM initialization parameter is a maximum for the parameter (that is, FINDLIM=limit,max-limit).

Action:

Correct the parameter and rerun.

SARINI26

Tape storage group names must be unique

Reason:

The tape storage group names which are defined by the STORGRPn initialization parameters must be unique.

Action:

Correct the STORGRPn parameter and rerun.

SARINI27

Tape storage volser ranges must not partially overlap

Reason:

The tape VOLSER ranges specified for the STORGRPn initialization parameters must be either the same, or disjoint. No partial overlaps are allowed.

Action:

Correct the tape VOLSER ranges for the STORGRPn parameter and rerun.

SARINI28

ERO option is not active

Reason:

The EROOPT=NO initialization parameter was specified and all of the ERO parameters have been removed from the CA View database.

Action:

None. This is an informational message.

SARINI29

Parameter conflict with ERO parameter specification and EROOPT=NO specification

Reason:

The EROOPT=NO initialization parameter was specified, indicating that all ERO options are to be removed and new ERO initialization parameters are being specified.

Action:

Either remove the EROOPT=NO parameter, or remove the ERO initialization parameters and rerun.

SARINI30

Previous update by Job: jjjjjjjj on mm/dd/yyyy hh:mm:ss

Reason:

The job specified in the message updated the database initialization parameters on the specified date and time.

Action:

None.