VERIFY

Displays access and status information about KSAM file.

 

   >{ VERIFY 

      V      } [filereference] [;OFFLINE] [;NOCHECK]

With the VERIFY command, you can request a display of the characteristics of a KSAM data file, both the static information defined at file creation and dynamic file access information. The abbreviation V can be used instead of the keyword VERIFY.

PARAMETERS

filereference

Actual file designator identifying the file whose characteristics are to be displayed. The actual designator can be a back reference to a file name in an MPE :FILE command; in this case, the actual designator must be preceded by an asterisk (*). Either the data file name or the key file name may be used to identify the KSAM file.

(Optional parameter only if no parameters.)

Default: If omitted, last filereference is assumed.

OFFLINE

Display output on line printer. An MPE :FILE command may be used to specify a particular line printer.

(Optional parameter.)

Default: If omitted, display is sent to terminal.

NOCHECK

Allows specified KSAM file to be opened for read-only access by the VERIFY command; use when a system failure prevents the KSAM file from being opened.

(Optional parameter.)

Default: If omitted, VERIFY cannot open file that was open when system failed.

DISPLAY KSAM FILE CHARACTERISTICS

In a session, you will be asked to select one of four possible displays:

File information (definitions from file creation plus file access statistics)
KSAM parameters (definitions of keys from file creation)
KSAM control (key file access statistics)
All three of the above displays

In a job, the entire set of displays is printed exactly as if option 4 had been selected in a session.

To illustrate the interaction, the following VERIFY commands select each of the three separate displays; if option 4 were selected, these displays would be printed consecutively with no halt until they were finished. User entries are underlined:

 

>RUN KSAMUTIL.PUB.SYS  



 HP32208A.2,4  TUE, APR 17, 1979, 11:23 AM      KSAMUTIL VERSION:A.2.4

>VERIFY TESTFILE



                select file information only---------------------------↓

WHICH  (1=FILE INFO, 2=KSAM PARAMETERS,  3=KSAM CONTROL, 4=ALL)?1



TESTFILE,JOAN.MORRIS        CREATOR=JOAN 

FOPTIONS(004005)=KSAM, :FILE, NOCCTL, F, FILENAME, ASCII, PERM 

AOPTIONS(000400)=DEFAULT, NOBUF, DFFAULT, NO FLOCK, NO MR, IN 

RECSIZE:SUB:TYP:LDNUM:DRT:UN.:  CODE:LOGICAL PTR: END OF FILE:FILE LIMIT 

   -128:  9:  0:    2:  4:  1:     0:          0:           5:      1023 

 LOG. COUNT:PHYS. COUNT:BLK SZ:EXT SZ:NR EXT: LABELS:LDN:   DISCADDR: 

          1:          1:  -128:   129:     8:      0:  2:00000117760:

The infomation returned by selecting file information is the same as that returned by FGETINFO (described in section IV).

 



                 select key file information only----------------------------

                                                                    ↓ 

WHICH (1=FILE INFO,   2=KSAM PARAMETERS,   3=KSAM CONTROL,   4=ALL)?2



KEY FILE=TESTKEY  KEY FILE DEVICE=3            SIZE=         386  KEYS=   2 

FLAGWORD(000000)=RANDOM PRIMARY,    FIRST RECORD=0,   PERMANENT 

KEY TY LENGTH   LOC. D KEY BF  LEVEL 

  1  B     20      3 Y     72      1<----- primary key is listed first, 

  2  B      8     24 R    126      1<----- alternate keys follow

     \__________________/

                     ↑----------------------- random insertion of duplicate key 

   corresponds to KEY= descriptions in BUILD command

The actual number of keys per block (the blocking factor) is listed in this display under the heading KEY BF. Note that this number may be greater than the blocking factor you specified during file creation. This occurs if KSAM adjusts the specified blocking factor to generate a block size that makes optimum use of disc space, KSAM only increases the specified blocking factor, it never decreases it. (Refer to appendix B for full particulars on the calculation of block size and the adjustment of the blocking factor.)

The maximum number of levels in the key file structure for each key is noted under the heading LEVEL.

 

                 select dynamic KSAM file information--------------------

                                                                 ↓

WHICH (1=FILE INFO,  2=KSAM PARAMETERS,  3=KSAM CONTROL,  4=ALL)?3



DATA FILE = TESTFILE     VERSION= A.2.4 

KEY CREATED=107/'79  10:58:17.4      KEY ACCESS= 107/'79 11:23:35.9 

KEY CHANGED=107/'79  11:21: 7.7      COUNT START=107/'79 11:21: 8.0 

DATA RECS  =           5 DATA BLOCKS=          4 END BLK WDS=         64

DATA BLK SZ=          64 DATA REC SZ=        128 ACCESSORS=            0

FOPEN                  1 FREAD                 0 FCLOSE                1

FREADDIR               0 FREADC                0 FRFADBYKEY            0

FREMOVE                0 FSPACF                0 FFINDBYKEY            0

FGETINFO               3 FGETKEYINFO           1 FREADLABEL            0

FWRITELABEL            0 FCHECK                0 FFINDN                0

FWRITE                 5 FUPDATE               0 FPOINT                0

FLOCK                  0 FUNLOCK               0 FCONTROL              0

FSETMODE               0

KEYBLK READ            3 KEYBLK WROTE          2 KEYBLK SPLIT          0

KEY FILE EOF          18 FREE KEY HD           0 SYSTEM FAILURE        0

MIN PRIME              3 MAX PRIME             1 RESET DATE

DATA FIXED          TRUE DATA B/F              1 TOTAL KFYS            2

FIRST RECNUM           0 MIN PECSIZE          31

The dynamic key file information displayed by option 3 together with the static key file information displayed by option 2 comprise the information displayed by the FGETINFO intrinsic described in section IV. Note that the version number displayed by VERIFY is the version of KSAM under which the file was created. The intrinsic HP32208 described in section IV can be used to determine the current version of KSAM.

TERMINATING THE >VERIFY COMMAND

In order to terminate the VERIFY command in a session, you must press the RETURN key (CR) in response prompt:

 

   WHICH (1=FILE INFO, 2=KSAM PARAMETERS, 3=KSAM CONTROL, 4=ALL)?

Any other response either causes a display followed by reiteration of this prompt or else causes this prompt to be issued. For example:

 

WHICH (1=FILE INFO, 2=KSAM PARAMETERS, 3=KSAM CONTROL, 4=ALL)?6



WHICH (1=FILE INFO, 2=KSAM PARAMETERS, 3=KSAM CONTROL, 4=ALL)?0



WHICH (1=FILE INFO, 2=KSAM PARAMETERS, 3=KSAM CONTROL, 4=ALL)?CR

                                                              ↑

>EXIT                                  only response to terminate VERIFY.

END OF PROGRAM

DIRECTING VERIFY OUTPUT TO LINE PRINTER

If you want a "hard copy" of the information displayed by VERIFY, you should use the OFFLINE option. When included, OFFLINE directs the VERIFY information to a line printer. You can use the :FILE command to specify a different output device or a particular line printer.

USING VERIFY FOR RECOVERY

In case of a system failure when a KSAM file is open, the VERIFY command provides the following useful information:

EOF marker on the data file (END OF FILE header in option 1)
EOF marker on key file (KEY FILE EOF header in option 3)
Flag indicating whether system failure occurred (SYSTEM FAILURE heading in option 3)
Number of processes that had opened the file for non read-only access when the system failure occurred (ACCESSORS heading in option 3)

Note that you must use the NOCHECK option in order to run VERIFY when a system failure prevents KSAM files from being opened. This option overrides the restriction on opening files after a system failure and allows a file to be opened for read-only access in order to get the VERIFY information. (This access is not counted in the ACCESSORS count.)

(Refer to the KEYINFO command description for an example of how the VERIFY information can be used for recovery after system failure.)