Warning Messages

Warning messages are suffixed by a nnnW message number. They give information about parameters that may lead to unexpected results.

001W NOACCESS/NOSWEEP SPECIFIED FOR area-name/record-name

Reason:

Both NOACCESS and NOSWEEP were requested for the designated area or record. NOACCESS takes precedence and NOSWEEP is ignored.

Action:

If NOSWEEP is required, review all input parameter statements (listed on the Audit Report) to determine which statement specified NOSWEEP, or caused NOACCESS. If necessary, correct the parameter statements and resubmit the job.

002W ASSUME ALL CALC RECORDS COPIED INTO SUBSCHEMA

Reason:

The CALCSETS operand was specified in the AUDIT statement. CA IDMS/DB Audit cannot ensure that all CALC records in all areas to be swept were copied into the subschema being used. A successful audit requires (and CA IDMS/DB Audit assumes) that they were copied.

Action:

None.

003W ASSUME EXTRACT FILE BEING INPUT FROM PREVIOUS AUDIT

Reason:

A FIX parameter was entered without an AUDIT parameter statement. CA IDMS/DB Audit assumes an extract file from a previous CA IDMS/DB Audit job is being input. CA IDMS/DB Audit will open the extract file for input.

Action:

If CA IDMS/DB Audit terminates abnormally immediately after this message is issued, an input extract file does not exist. Supply an AUDIT parameter statement or supply the correct extract file. Resubmit the job.

004W PARTIAL AREA AUDIT PERFORMED - AREA SWEEP IMPLIED

Reason:

CA IDMS/DB Audit has performed a partial area audit for the area listing in the preceding message 001W.

Action:

None.

005W ALL RECORDS IN AREA ARE NOACCESS/NOSWEEP

Reason:

An area that was not designated as NOACCESS or NOSWEEP contains records that were designated as NOACCESS or NOSWEEP by RECORD or SET parameter statements. The area will not be swept.

Action:

None.

006W ALL MEMBER RECORDS FOR SET IN ERROR NOT RETRIEVED

Reason:

The db-key table filled when creating extracts for a set occurrence containing integrity errors. Information about the specific set occurrence precedes this message. Not all records for the set in error were retrieved. Fixing is not allowed.

Action:

Review the associated informative and error messages.

007W LDEL AN OWNER OF NON-EMPTY SET

Reason:

The displayed logically deleted record (LDEL) is an owner of a non-empty set occurrence. CA IDMS/DB Audit did not delete the record. The set occurrence owned by the LDEL is displayed elsewhere on the Before Images Report.

Action:

You can perform the following actions in sequence to erase the member records owned by the LDEL and then erase the LDEL:

Store a fictional record of the same type as the LDEL in error.
Use the CA IDMS utility IDMSBCF, FIX PAGE function to connect the fictional record to the first member record owned by the LDEL record, and the last member record owned by the LDEL if there are prior pointers, in the non-empty set.
Use the CA IDMS utility IDMSBCF, FIX PAGE function to change the next and prior pointers (for the non-empty set) in the LDEL, so that it points back to itself (to indicate an empty set).
Erase the fictional record with all of its member records.
Rerun the fix phase of CA IDMS/DB Audit to erase the LDEL.

008W AUDIT/FIX/AREA/RECORD/SET PARAMETER STATEMENTS IGNORED SINCE REPORTS = ONLY

Reason:

In this run, CA IDMS/DB Audit did not perform an audit or fix any errors, because a REPORTS=ONLY statement was also entered. The statement indicates that only the report phase is to be performed.

Action:

None.

009W INTEGRATED INDEX SET NOT INCLUDED IN READIED AREA. SET NAME IS index-set-name

Reason:

The database contains an SR7 or a system-owned integrated index set. The subschema does not contain a description for that set, but the subschema is a partial definition of the database in regard to system owned integrated index sets.

Action:

None.

010W THIS UPPER LEVEL POINTER WAS CORRECTED PRIOR TO FIX PROCESSING

Reason:

An upper level pointer denoting an index orphan was found to be in error during the audit phase and was fixed before the fix phase was run.

Action:

Ensure that the correct version of extract files produced during the audit phase is being used.

011W NO DISCONNECT AUDITING IS PERFORMED FOR INTEGRATED INDEXES

Reason:

The SETLIMIT value was exceeded for an integrated index set, as reported in the previous message, 054E. CA IDMS/DB Audit bypassed disconnect auditing on all integrated index sets.

Action:

Choose an action appropriate for the conditions in your database:

Investigate the other errors that were found in the CA IDMS/DB Audit run.
Increase the SETLIMIT value and resubmit the job. You may also want to use the DISK option to increase the amount of storage available.
Keep the same SETLIMIT value and designate the indicated integrated index set NOACCESS. Resubmit the job.

012W A1-A5 NOACCESS AREA AND SWEEP AREA CONFLICT

Reason:

Member records of owned set in sweep area reside in a NOACCESS area.

Action:

Member records are not accessed.

013W A1-A15 NOACCESS AREA AND NOSWEEP RECORD CONFLICT

Reason:

RECORD statement is set to NOSWEEP, which implies access to area, but area where records reside is set to NOACCESS.

Action:

Records are not accessed.

014W A1-A6 NOACCESS AREA AND SWEEP RECORD CONFLICT

Reason:

Member records of owned set reside in a NOACCESS area.

Action:

Records will not be accessed.

015W A1-A9 NOACCESS AREA AND AUDIT SET CONFLICT

Reason:

Member records of owned set to be audited reside in an area that has been set to NOACCESS.

Action:

Records are not accessed.

016W R4-R2 NOACCESS AREA AND NOSWEEP RECORD CONFLICT

Reason:

RECORD statement is set to NOSWEEP, which implies access, but area where records reside is set to NOACCESS.

Action:

Records are not accessed.

017W R4-R7 NOACCESS AREA AND SWEEP AREA CONFLICT

Reason:

Member records of owned set reside in a NOACCESS area.

Action:

Records are not accessed.

018W R4-R9 NOACCESS AREA AND SWEEP RECORD CONFLICT

Reason:

Member records of owned set reside in a NOACCESS area.

Action:

Records are not accessed.

019W S6-S4 SWEEP AREA AND NOACCESS AREA CONFLICT

Reason:

Member records of owned set in sweep area reside in a NOACCESS area.

Action:

Member records are not accessed.

020W R7-R1 SWEEP AREA AND NOACCESS RECORD CONFLICT

Reason:

Member records of owned set in sweep area reside in a NOACCESS area.

Action:

Member records are not accessed.

021W R7-R4 SWEEP AREA AND NOACCESS AREA CONFLICT

Reason:

Member records of owned set in sweep area reside in a NOACCESS area.

Action:

Member records are not accessed.

022W R1-R7 NOACCESS RECORD AND SWEEP AREA CONFLICT

Reason:

Member records of owned set in sweep area have been set to NOACCESS.

Action:

Member records are not accessed.

023W R1-R8 NOACCESS RECORD AND SWEEP RECORD CONFLICT

Reason:

Owner records that are flagged as sweep have set member records that are NOACCESS.

Action:

Member records are not accessed.

024W R1-R9 NOACCESS RECORD AND SWEEP RECORD CONFLICT

Reason:

Owner records that are flagged as sweep have set member records that are NOACCESS.

Action:

Member records are not accessed.

025W S8-S10 NOACCESS RECORD AND SWEEP RECORD CONFLICT

Reason:

Owner records that are flagged as sweep have set member records that are NOACCESS.

Action:

Member records are not accessed.

026W R2-R4 NOSWEEP RECORD AND NOACCESS AREA CONFLICT

Reason:

Records set as NOSWEEP, which implies ACCESS, are flagged as NOACCESS due to area being NOACCESS.

Action:

Member records are not accessed.

027W A5-A1 NOSWEEP RECORD AND NOACCESS AREA CONFLICT

Reason:

Records set as NOSWEEP, which implies ACCESS, are in area that is set to NOACCESS.

Action:

Member records are not accessed.

028W S10-S8 NOSWEEP RECORD AND NOACCESS AREA CONFLICT

Reason:

Records set as NOSWEEP, which implies ACCESS, are in area that is set to NOACCESS.

Action:

Member records are not accessed.

029W R8-R1 SWEEP RECORD AND NOACCESS RECORD CONFLICT

Reason:

Owner records that are set to SWEEP have member records that are flagged as NOACCESS.

Action:

Member records are not accessed.

030W R9-R1 SWEEP RECORD AND NOACCESS RECORD CONFLICT

Reason:

Owner records that are set to SWEEP have member records in another area flagged as NOACCESS.

Action:

Member records are not accessed.

031W R9-R4 SWEEP RECORD AND NOACCESS AREA CONFLICT

Reason:

Owner records that are set to SWEEP have member record in an area flagged as NOACCESS.

Action:

Member records are not accessed.

032W A6-A1 SWEEP RECORD AND NOACCESS AREA CONFLICT

Reason:

Owner records that are set to SWEEP have member records in an area flagged as NOACCESS.

Action:

Member records are not accessed.

033W A9-A1 AUDIT SET AND NOACCESS AREA CONFLICT

Reason:

Set that is flagged to be audited has member records in an area flagged as NOACCESS.

Action:

Member records are not accessed.

034W S4-S6 NOACCESS AREA AND SWEEP AREA CONFLICT

Reason: Set that is flagged to audit has member records in an area flagged as NOACCESS.

Action: Member records are not accessed.

035W INCONSISTENT NEXT/PRIOR/OWNER POINTER TYPES IN MULTI-MEMBER SET

Reason:

Pointer type flagged does not exist in all member records in set.

Action:

Inconsistent pointer type is ignored in records where it exists.

036W A1-A10 NOACCESS AREA AND SWEEP AREA CONFLICT

Reason:

Owner records in an area set to sweep have member records in an area flagged as NOACCESS.

Action:

Member records are not accessed.

037W A1-A11 NOACCESS AREA AND SWEEP RECORD CONFLICT

Reason:

Owner records set to sweep have member records in another area flagged as NOACCESS.

Action:

Member records are not accessed.

038W A1-A12 NOACCESS AREA AND AUDIT SET CONFLICT

Reason:

Set that is flagged to audit has member records in an area flagged as NOACCESS.

Action:

Member records are not accessed.

039W A4-A1 SWEEP AREA AND NOACCESS AREA CONFLICT

Reason:

Owner records in an area set to sweep have member records in an area flagged as NOACCESS.

Action:

Member records are not accessed.

040W A10-A1 SWEEP AREA AND NOACCESS AREA CONFLICT

Reason:

Owner records in an area to sweep have member records in an area flagged as NOACCESS.

Action:

Member records are not accessed.

041W A11-A1 SWEEP RECORD AND NOACCESS AREA CONFLICT

Reason:

Owner records that are set to sweep have member records in an area flagged as NOACCESS.

Action:

Member records are not accessed.

042W A12-A1 AUDIT SET AND NOACCESS AREA CONFLICT

Reason:

Set that is flagged to be audited has member records in an area flagged as NOACCESS.

Action:

Member records are not accessed.

043W record-name RECORD IS NOACCESS. THIS CANCELED CALCSET PROCESSING IN AREA area-name.

Reason:

Record that is set to NOACCESS is also a CALC record.

Action:

CALC set is not audited.

045W FSBUFFERS KEYWORD WAS BYPASSED - REFER TO SYSIDMS PREFETCH CAPABILITY

Reason:

FSBUFFERS parameter is no longer valid.

Action:

Use SYSIDMS PREFETCH as an alternative to FSBUFFERS.

        DBIO Major Error Status Codes
 FS = FAST-SCAN
 GP = FIND/OBTAIN PAGE
 PR = PAGE RETURN
        DBIO Minor Error Status Codes
 A1 = New page returned
 A2 = Function not supported
 A3 = Invalid page range
 A4 = Invalid qualifier
 A5 = Page not current of run unit
 A6 = Area not bound
 A7 = Page return not on
 A8 = Page return already on
 A9 = Fast scan not on
 B1 = Fast scan already on
 B2 = SR4 chain error
 B3 = SR2/SR3 chain error
 B4 = HDR/FTR page number mismatch
 B5 = Error closing file
 B6 = Record not logically deleted
 B7 = SMP currency error with page return on
 B8 = Bad 'line space used' length in footer
 B9 = No space in page
 C1 = Duplicate DBKEY
 C2 = Invalid Store
 C3 = Skipped index
 C4 = Broken chain
 C5 = IXDET member of multiple sets
 C6 = Ignored page reserve
 C7 = Invalid Length - discrepancy in RDW lengths encountered
      during attempted MODIFY RECORD
 C8 = DMCL/SCHEMA CA IDMS release mismatch
 C9 = Decompress error
 D1 = Invalid record length
 D4 = Invalid page displacement
 D5 = Invalid request
 D7 = GSDTPARM cannot be loaded
 D8 = Record not found in PSUB
 D9 = Segment named in DBNAME table entry is mismatched with current DMCL
 DA = DBNAME not valid or segment name cannot be used as DBNAME
  Minor return codes prefixed with an I indicate an internal error:
 I1 = Invalid parameter list
 I2 = Function not supported
 I3 = File already open/close
 I4 = Insufficient work space--record read is larger than subschema description
 I5 = Invalid currency data
 I6 = VSAM block error
 I7 = Bad fast scan DMCL block
 I8 = File not assigned

Figure 6.1: DBIO Error Codes