Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

CHECK-FILE-CONSISTENCY

&pagelevel(3)&pagelevel

Check NK-ISAM file for consistency

Component:

BS2000

Functional area:

File processing

Domain:

FILE

Privileges:

STD-PROCESSING

The command CHECK-FILE-CONSISTENCY checks an ISAM file that is of type BLOCK-CONTROL-INFO = *WITHIN-DATA-BLOCK and has not been correctly closed to ensure that it is consistent. This command is only meaningful for NK-ISAM files which are processed with WRITE-IMMEDIATE=*YES.

Only files identified as open (see the STATUS=*PAR(REPAIR-NEEDED=*YES) option in the SHOW-FILE-ATTRIBUTES command) are selected. The file lock is removed.
Concurrent copy locks remain in place if the concurrent copy session has not yet ended. If a file is identified as open, the LLP (last logical page) is set to the last PAM page used.

If the file is on a mirrored disk (see the “DRV” manual [11]), the consistency (contents) of file blocks is restored if required.

If the file contains secondary keys, the secondary index is checked to ensure that it was created or deleted completely (since processing may have aborted at the time of creating or deleting the secondary index).

Multiblocks (an ISAM data block consisting of several PAM pages) are checked for consistency, i.e. to determine whether processing was aborted when writing a multiblock. For information on “multiblocks” see the “Introductory Guide to DMS” [13].

An existing file lock can also be removed by using the command REMOVE-FILEALLOCATION-LOCKS. But no inconsistencies are detected in the process Inconsistencies in a file can be eliminated with the REPAIR-DISK-FILES command.

Format

CHECK-FILE-CONSISTENCY                                                                                                                   

FILE-NAME = <filename 1..54> / <partial-filename 2..53>

,SELECT = *ANY-DISK / *PRIVATE-DISK / *PUBLIC-DISK / *NET-STORAGE

Operands

FILE-NAME = <filename 1..54> / <partial-filename 2..53>
Names of the files to be checked. Write access authorization is required for files which are not under the user’s own user ID.

SELECT = *ANY-DISK / *PRIVATE-DISK / *PUBLIC-DISK
Restricts the files which are to be checked to the specified volume type. This operand is of use only if a partially qualified name, or the name of a file generation group, is specified for FILE-NAME.

SELECT = *ANY-DISK
Any files can be checked, irrespective of their volume types.

SELECT = *PRIVATE-DISK
Checks files which are stored on private disks.

SELECT = *PUBLIC-DISK
Checks files which are stored on public disks.

SELECT = *NET-STORAGE
Checks files which are stored on a Net-Storage volume.

Return codes

(SC2)

SC1

Maincode

Meaning/Guaranteed messages


0

CMD0001

Command executed


0

CMD0001

No action required


0

DMS06E6

File specified in command is empty


0

DMS06E9

No valid record found during reconstruction of ISAM file


0

DMS06ED

Error on writing unrecoverable blocks to scratch file


1

CMD0202

Syntactical or semantic error in command


32

DMS0584

A state that does not allow the function to continue was reported during processing


64

CMD0216

Privileges error


64

DMS0501

Requested catalog not available


64

DMS0512

Requested catalog not available


64

DMS051B

Requested user ID not in pubset


64

DMS051C

User not authorized to access pubset


64

DMS0533

Requested file not cataloged in pubset


64

DMS0535

Specified file not shareable


64

DMS055C

Requested file not cataloged in pubset


64

DMS0583

An error occurred when reconstructing the file


64

DMS0585

Error detected during catalog processing or multihost processing


64

DMS0586

Currently not possible to access or reserve volume


64

DMS0587

Use of specified command restricted by system administrator


64

DMS0588

It was not possible to allocate disk space


64

DMS05F8

It was not possible to allocate disk space Guaranteed message: DMS05F8


64

DMS05FC

Specified user ID not in HOME pubset


64

DMS0609

No access to system file


64

DMS0609

No file corresponds to specified selection criterion


64

DMS06CC

No file corresponding to specified operands


64

DMS06E4

Reconstruction for this file type not possible with specified command


64

DMS06FF

BCAM connection severed


64

DMS06FF

File created with WROUT=NO. Consistency check is not practical


130

DMS0524

System address space full


130

DMS053C

Insufficient space in pubset catalog file


130

DMS0582

File is currently locked or in use and cannot be processed


130

DMS0585

Error detected during catalog processing or multihost processing


130

DMS0586

Currently not possible to access or reserve volume


130

DMS0588

It was not possible to allocate disk space


130

DMS0594

Not enough virtual memory available


130

DMS05C8

Maximum permitted number of files reached