SARDBC10

Release 11.5 or earlier database cannot be copied to database with large format data sets

Reason:

The SARDBASE COPY statement specified to copy a r11.5 or earlier release level database to a new database that contains a large format data set (with more 4369 cylinders). Large format data sets are only supported for r11.6 or higher release level databases.

Action:

Version the database level of the "FROM" database to r11.6 or higher with the SARDBASE VERSION statement. Or, recreate the "TO" database with data sets that have 4369 cylinders or less before copying the database.

SARDBD01

MEMBER =xxxxxxxx IS BEING LOADED TO DATABASE

Reason:

The specified model banner page library member is being loaded to the database.

Action:

None. This is an informational message.

SARDBD02

INPUT DATA SET IS EMPTY OR NO MEMBERS WERE LOADED

Reason:

The specified input data set is empty, or the requested members are not found in the input data set referenced by the SARBLIB DD statement.

Action:

Check the JCL to ensure that you specified the correct input data set name on the SARBLIB DD statement or that you specified the correct members to be loaded into the database.

SARDBD03

DDNAME "SARBLIB" NOT FOUND

Reason:

The SARBLIB DD statement is required for the SARDBASE utility BLOAD control statement to load model banner pages into the database.

Action:

Add the SARBLIB DD statement to the JCL, and then rerun the job.

SARDBD04

OPEN FAILED FOR DDNAME "SARBLIB"

Reason:

The SARDBASE utility BLOAD function was unable to open the SARBLIB DD statement. The job log must contain messages identifying the error.

Action:

Correct the error, and then rerun the job.

SARDBD40

DATABASE AT INCORRECT LEVEL

Reason:

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

Action:

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

SARDBG01

ERROR ON DATABASE

Reason:

An error occurred in the processing of the database. The message preceding this message indicates the error condition.

Action:

Respond to the preceding error message.

SARDBG02

DATABASE IS BEING CONVERTED

Reason:

A REORG during database conversion is in process.

Action:

None.

SARDBG04

ARCHIVAL DATE FORMAT INVALID FOR ID=xxxxxxxxxxxx, RECORD DROPPED

Reason:

An alternate control record entry cannot be added to the alternate index because the archival date for the specified SYSOUT was invalid.

Action:

None. The problem can be the result of a database corruption or a SARSTCUX user exit that was coded erroneously.

SARDBG05

REORGANIZING xxxxxxxxxxxx, GEN=nnnn, ARCHIVED ON mm/dd/yy AT hh:mm

Reason:

This informational message is a progress report issued during a SARDBASE REORG. It appears at intervals specified by the SARINIT parameter DBMSGFRQ, which only counts SYSOUT IDs. Therefore, with a default DBMSGFRQ=5000, this message appears for every 5000th SYSOUT.

Action:

None.

SARDBG06

ALTERNATE INDEX REORGANIZATION STARTED

Reason:

This informational message indicates the start of the alternate index record reorganization phase of an asynchronous SARDBASE REORG. The alternate index records identify the starting date and SYSOUT IDs of a generation. These records are updated to reflect current SYSOUTs and reports in the database.

Action:

None. This message is informational.

SARDBG07

INDEX RECORD REORGANIZATION STARTED

Reason:

This message indicates the start of the index record reorganization phase of an asynchronous SARDBASE REORG. During this phase of the REORG, the database index structure is compressed to provide optimal access time.

Action:

None. This is an informational message.

SARDBG08

REORG PROCESSING ALTERNATE INDEX GEN gen WITH count GEN(S) REMAINING

Reason:

This message indicates that the SARDBASE utility is in the second phase of the asynchronous REORG. This message is issued in response to the status operator command.

Action:

None. This message is informational.

SARDBG09

REORG SUCCESSFULLY TERMINATED DUE TO STOP COMMAND

Reason:

A stop command is issued during processing of the SARDBASE asynchronous REORG. Reorganization processing has been properly terminated, leaving all reorganization activity intact.

Action:

None. This message is informational.

SARDBG10

REORG CANCELLED DUE TO STOP COMMAND

Reason:

A stop command is issued during processing of the SARDBASE standard REORG. Reorganization processing was terminated and the database was reset to the pre-organization state.

Action:

None. This message is informational.

SARDBI00

DATABASE

database

DOES NOT EXIST <<PDC

Reason:

An access error occurred trying to access the CA View database.

Action:

Correct the problem. This can require copying the database with the SARDBASE utility or, in the extreme case, recovering the database. For more information, see the chapters "Database Utilities" and "Backing Up and Recovering the Database" in the Reference Guide.

SARDBI01

DDname "SARIOUT" not found

Reason:

The SARIOUT DD statement is required for the SARDBASE utility IDXOUT control statement to write the master index.

Action:

Add the SARIOUT DD statement to the JCL, and then rerun the job.

SARDBI02

Open failed for DDname "SARIOUT"

Reason:

The SARDBASE utility IDXOUT function was unable to open the SARIOUT DD statement. The job log must contain messages identifying the error.

Action:

Correct the error, and then rerun the job.

SARDBI03 through SARDBI10

SARDBI00 DATABASE database DOES NOT EXIST
SARDBI03 BLOCK OUT OF RANGE ON database - DCCB=dccb
SARDBI04 DATA SET RENAME FAILED REQ=function RC=nnn REASON=xxxx
SARDBI05 UNSUPPORTED DEVICE TYPE - BLKS/CYL=nnn
SARDBI06 MAXIMUM OF 255 DATA SETS DEFINED TO database
SARDBI07 NO MORE SPACE IN DATABASE database
SARDBI08 MISSING HIGH-LEVEL INDEX NAME OF DATABASE
SARDBI09 LOGICAL I/O ERROR eeee ON database - DCCB=dccb
SARDBI10 UNEXPECTED END OF DATA, cccKEY=kkkkkkkkkkkkkkkk'

Reason:

An allocation error, access error, or I/O error occurred with the CA View database as described by the text of the message where:

database	Identifies the high‑level prefix of the database
dccb	Represents a hexadecimal string identifying the data set, relative cylinder, and relative block in the database
filetype	Indicates the type of database file, either DATA or INDEX
function	Identifies the type of catalog function that failed for a RENAME
ccc	Indicates the internal control block being accessed (SFB, IFB, or XFB)
eeee	Identifies the internal error code of the logical I/O error
kkkkkkkkkkkkkkkk	Specifies the key of the record in hex (if the key is longer than 16 bytes, only the first 16 bytes are shown)
nnn	Represents a number to identify a data set number, number of blocks, return code, or error code
xxxx or xxxxxxxx	Represents a hexadecimal number for an error code, information code, or reason code

Action:

Correct the problem with the database. This can require copying the database with the SARDBASE utility or, in the extreme case, recovering the database. For more information, see the chapters "Database Utilities" and "Backing Up and Recovering the Database" in the Reference Guide.

SARDBI11

This number represents one of the following:

Record not found, cccKEY=x'kkkkkkkkkkkkkkkk'

Record not found, Panel= panel_name

Record not found, Banner= banner_name

Record not found, RCR=resource_id

Record not found, GCR=report_id GEN=gen SEQ=seq

Reason:

A database read function was executed and the required record is not found in the database. The format can include the report, resource, banner, panel, or the binary key for other formats.

ccc	Indicates the internal control block being accessed (SFB, IFB, or XFB)
kkkkkkkkkkkkkkkk	Specifies the key of the record in hex (if the key is longer than 16 bytes, only the first 16 bytes are shown)
panel_name	Specifies the name of the panel record
banner_name	Specifies the name of the banner record
Resource_id	Specifies the Id of the ACIF/Xerox resource record
Report_id	Specifies the Id of the report
Gen	Specifies the database generation number assigned to the report
Seq	Specifies the database sequence number assigned to the report

Action:

SARDBI12

LOCK FILE FOR

database

ALREADY EXISTS

Reason:

An allocation error, access error, or I/O error occurred with the LOCKFILE for the CA View database as described by the text of the message.

Action:

Verify that the LOCKFILE exists. If necessary, reallocate the LOCKFILE.

SARDBI13

LOCK FILE FOR

database

DOES NOT EXIST

Reason:

An allocation error, access error, or I/O error occurred with the LOCKFILE for the CA View database as described by the text of the message.

Action:

SARDBI14

DATACLAS/MGMTCLAS/STORCLAS ALLOWED ONLY FOR SMS DATA SETS

Reason:

In the ADDDS statement of a SARDBASE job, one of the SMS parameters (DATACLAS/MGMTCLAS/STORCLAS) was specified, but the data set CA View attempted to allocate for the database was a non-SMS data set.

Action:

If the data set must not be SMS-managed, follow these steps:

Remove the SMS parameters from the ADDDS statement.
Ensure that the storage class is not defaulted by a site-written ACS routine.
Resubmit the SARDBASE job.

If the data set must be SMS-managed, specify an appropriate STORCLAS, or ensure that storage class is selected by a site-written ACS routine, then resubmit the SARDBASE job.

SARDBI15

UNIT/VOLSER ALLOWED ONLY FOR NON-SMS DATA SETS

Reason:

In the ADDDS statement of a SARDBASE job, the UNIT or VOLSER parameter was specified, but the data set CA View attempted to allocate for the database was an SMS data set.

Action:

If the data set must not be SMS-managed, follow these steps:

Remove any SMS parameters from the ADDDS statement.
Ensure that the storage class is not selected by a site-written ACS routine.
Resubmit the SARDBASE job.

If the data set must be SMS-managed, remove the UNIT and VOLSER parameters from the ADDDS statement, then resubmit the SARDBASE job.

SARDBI16

DATABASE IS INCOMPATABLE WITH CA VIEW 2.0
DATABASE IS INCOMPATABLE WITH CA VIEW 2.0 SARPAM FUNCTION 'nn'
DATABASE 'HLQ' AT INCORRECT RELEASE LEVEL
DATABASE 'HLQ' AT INCORRECT RELEASE LEVEL SARPAM FUNCTION 'nn'

Reason:

Incorrect release of the CA View program is attempting to access a CA View database.

Accessing a CA View r11 or higher database with the CA View 2.0 programs results in the Format #1 SARDBI16 message.

Accessing a CA View r11 or higher database with CA Deliver 1.7 "Direct-to-View" Archival using the CA View 2.0 program library results in the Format #2 SARDBI16 message. The application program abnormally terminates U0041.

Accessing a CA View 2.0 database with the CA View r11 or higher programs can result in either of two messages.

If an index extent has not been allocated, message "SARDBI00 Index file for 'hlq' does not exist" is displayed.
If an index extent has been allocated for the CA View database but the database has not been "versioned" to CA View r11 or higher, the Format #3 SARDBI16 message is displayed.

Accessing a CA View 2.0 Database with the CA Deliver "Direct-to-View" Archival using a CA View r11 or higher program library can result in either of the following two messages:

If an index extent has not been allocated, message "SARDBI00 Index file for 'hlq' does not exist, SARPAM FUNCTION 'nn'" is displayed.
If an index extent has been allocated for the CA View database but the database has not been "versioned" to CA View r11 or higher, the Format #4 SARDBI16 message is displayed.

Action:

Correct the STEPLIB to point to the correct release of CA View or refresh LLA with the correct release of CA View if STEPLIB is not used.

SARDBI17

DATABASE SPACE FOR THE FILE DELETED OR REUSED

Reason:

A user is browsing a report which is deleted by another user or system function, such as, the backup cycle expiring the report and the space is re-used by an archival function. The space is no longer owned by this report and can no longer be browsed.

Action:

If the report is needed, contact your site's CA View administrator who can recover the report if it is available on tape. If the report is not needed, no additional action is required.

SARDBI18

NO MVS SUPPORT FOR COMPRESSION SERVICES

Reason:

A report was compressed and archived to disk using MVS compression service, but your current operating system does not support MVS compression service.

Action:

If the report is archived to tape, delete the disk copy and reload the report from tape. If the report is not archived to tape, access the report from the same machine that archived it.