HP 3000 MPE/iX Computer Systems KSAM/3000 Reference Manual ABCDE HP Part No. 30000-90079 Printed in U.S.A.
The information contained in this document is subject to change without notice. HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this material.
PREFACE This publication is the reference manual for KSAM/3000. KSAM stands for Keyed Sequential Access Method, a method of accessing les indexed by keys. KSAM/3000 operates on the HP 3000 Computer System. The methods used to access a KSAM/3000 le di er depending on the particular language used. A COBOL user, an RPG user, a BASIC user, and an SPL user each has his own set of procedures with which to access a KSAM le; a FORTRAN user can choose to access a KSAM le with either COBOL or SPL procedures.
Contents 1. INTRODUCING KSAM/3000 OVERVIEW . . . . . . . . . . . . . . . . . . FILE STRUCTURE . . . . . . . . . . . . . . FILE ACCESS . . . . . . . . . . . . . . . . KSAM/3000 FEATURES . . . . . . . . . . . . MULTIPLE KEYS . . . . . . . . . . . . . . DUPLICATE KEYS . . . . . . . . . . . . . GENERIC KEYS . . . . . . . . . . . . . . . APPROXIMATE MATCH . . . . . . . . . . . DATA RECORD FORMAT . . . . . . . . . . HOW TO USE KSAM FILES . . . . . . . . . . CREATING A KSAM FILE . . . . . . . . . .
BUILD . . . . . . . . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . . . . . . KEY DESCRIPTION . . . . . . . . . . . . . . . CREATING A KSAM FILE . . . . . . . . . . . . ERASE . . . . . . . . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . . . . . . CLEARING A KSAMFILE . . . . . . . . . . . . PURGE . . . . . . . . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . . . . . . PURGING A KSAM FILE . . . . . . . . . . . . . RENAME . . . . . . . . . . . . . . . . . . . .
3. USING KSAM FILES IN COBOL PROGRAMS OVERVIEW . . . . . . . . . . . . CALLING A KSAM PROCEDURE . . FILETABLE PARAMETER . . . . . FILETABLE . . . . . . . . . . . . EXAMPLE . . . . . . . . . . . STATUS PARAMETER . . . . . . . STATUS . . . . . . . . . . . . . STATUS . . . . . . . . . . . . . . USING STATUS . . . . . . . . . KSAM LOGICAL RECORD POINTER SHARED ACCESS . . . . . . . . SAMPLE KSAM FILE . . . . . . CKCLOSE . . . . . . . . . . . . . PARAMETERS . . . . . . . . . USING CKCLOSE . . . . . . . .
CKUNLOCK . . . . . . . . . . . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . . . . . . . . . . . USING CKUNLOCK . . . . . . . . . . . . . . . . . . . . EXAMPLES . . . . . . . . . . . . . . . . . . . . . . . . CKWRITE . . . . . . . . . . . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . . . . . . . . . . . USING CKWRITE . . . . . . . . . . . . . . . . . . . . . EXAMPLES . . . . . . . . . . . . . . . . . . . . . . . . EXAMPLES OF KSAM FILE ACCESS FROM COBOL PROGRAM EXAMP1.
USING FFINDBYKEY . . . . . . . . . USING APPROXIMATE KEYS . . . . USING PARTIAL (GENERIC) KEYS . . SHARED ACCESS . . . . . . . . . . FFINDN . . . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . CONDITION CODES . . . . . . . . . . SPECIAL CONSIDERATIONS . . . . . . USING FFINDN . . . . . . . . . . . . SHARED ACCESS . . . . . . . . . . FGETINFO . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . CONDITION CODES . . . . . . . . . . USING FGETINFO . . . . . . . . . . . FGETKEYINFO .
USING FREAD . . . . . . SHARED ACCESS . . . . FREADBYKEY . . . . . . . FUNCTIONAL RETURN . . PARAMETERS . . . . . . CONDITION CODES . . . . USING FREADBYKEY . . . SHARED ACCESS . . . . DUPLICATE KEYS . . . FREADC . . . . . . . . . . FUNCTIONAL RETURN . . PARAMETERS . . . . . . CONDITION CODES . . . . USING FREADC . . . . . . SHARED ACCESS . . . . FREADDIR . . . . . . . . . PARAMETERS . . . . . . CONDITION CODES . . . . SPECIAL CONSIDERATIONS USING FREADDIR . . . . . FREADLABEL . . . . . . . . PARAMETERS . .
FUPDATE . . . . . . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . . . . . CONDITION CODES . . . . . . . . . . . . . . SPECIAL CONSIDERATIONS . . . . . . . . . . USING FUPDATE . . . . . . . . . . . . . . . SHARED ACCESS. . . . . . . . . . . . . . . . UPDATING RECORDS WITH DUPLICATE KEYS. FWRITE . . . . . . . . . . . . . . . . . . . . PARAMETERS . . . . . . . . . . . . . . . . CONDITION CODES . . . . . . . . . . . . . . SPECIAL CONSIDERATIONS . . . . . . . . . . USING FWRITE . . . . . . . . .
PARAMETERS . . . . USING BKDELETE . . Shared Access . . . . BKERROR . . . . . . . PARAMETERS . . . . USING BKERROR . . . BKLOCK . . . . . . . . PARAMETERS . . . . USING BKLOCK . . . . BKOPEN . . . . . . . . PARAMETERS . . . . USING BKOPEN . . . . Access Modes . . . . Shared Access . . . . Dynamic Locking . . . Sequence Checking . . BKREAD . . . . . . . . PARAMETERS . . . . USING BKREAD . . . . Shared Access . . . . BKREADBYKEY . . . . PARAMETERS . . . . USING BKREADBYKEY BKREWRITE . . . . . . PARAMETERS . .
B. KSAM/3000 INTERNAL STRUCTURE AND TECHNIQUES OVERVIEW . . . . . . . . . . . . . . . . . . . . KSAM FILE STRUCTURE . . . . . . . . . . . . . B-TREE STRUCTURE . . . . . . . . . . . . . . ADDING OR DELETING KEYS. . . . . . . . . KSAM KEY FILE STRUCTURE . . . . . . . . . . CONTROL BLOCK. . . . . . . . . . . . . . . KEY DESCRIPTOR BLOCK. . . . . . . . . . . KEY ENTRY BLOCKS. . . . . . . . . . . . . . RELATION OF KEY TO DATA FILE . . . . . . . KSAM FILE SIZE . . . . . . . . . . . . . . . . . KEY BLOCK SIZE . .
Figures 1-1. 2-1. 3-1. 3-2. 3-3. 3-4. 3-5. 4-1. 4-2. 4-3. 4-4. 4-5. 4-6. 4-7. 4-8. 4-9. 4-10. 4-11. 4-12. 4-13. 4-14. 5-1. 5-2. 5-3. 5-4. 6-1. 6-2. 6-3. 6-4. 6-5. 6-6. 6-7. 6-8. 6-9. 6-10. 6-11. B-1. B-2. B-3. B-4. B-5. B-6. A Simpli ed View of the KSAM File Structure . . . . . . . . EDITOR Listing of Job to be Streamed . . . . . . . . . . . Filetable Structure . . . . . . . . . . . . . . . . . . . . Representation of KSAMFILE Used in COBOL Examples . . . Sequential Write Using COBOL . . . . . . . . . . .
B-7. B-8. B-9. B-10. B-11. E-1. F-1. F-2. F-3. F-4. F-5. Data File/Key File Relation . . . . . . . . . Formula to Determine File Space per Key . . . Calculation of Total Key File Size with Two Keys Extra Data Segments for Shared Access . . . . KSAM Extra Data Segment . . . . . . . . . KSAM File and an Extra Data Segment . . . . KSAM File Test Program . . . . . . . . . . Results Returned By The NLKEYCOMPARE Intrinsic Generic Key Searches . . . . . . . . . . . . Generic Key Searches . . . . . . . . . . . .
Tables 2-1. 2-2. 2-3. 2-4. 2-5. 3-1. 3-2. 3-3. 3-4. 4-1. 4-2. 4-3. 4-4. 4-5. 4-6. 4-7. 4-8. 6-1. 6-2. 6-3. 6-4. 6-5. A-1. A-2. A-3. A-4. A-5. B-1. B-2. B-3. C-1. F-1. F-2. Summary of KSAM Utilities . . . . . . . . . . . . . . . . . . . Key Types . . . . . . . . . . . . . . . . . . . . . . . . . . . Character Equivalent to Signed Digit for NUMERIC Keys . . . . . . FCOPY Functions with KSAM Files . . . . . . . . . . . . . . . KSAM Options of FCOPY . . . . . . . . . . . . . . . . . . . .
1 INTRODUCING KSAM/3000 OVERVIEW The Keyed Sequential Access Method (KSAM) is a method of organizing records in a le according to the content of key elds within each record. As implemented for the HP 3000 computer system, KSAM/3000 is similar to and competitive with other indexed sequential access methods. Every record in a KSAM le contains a primary key eld whose contents determine the primary logical sequence of records in the le.
FILE ACCESS Although separate in fact, the two les that comprise a KSAM le are treated as one le by the procedures that reference the le. The data le is the only le directly referenced by a user; the key le is updated by the system to re ect any changes to the data le and is not directly accessed by the user. Thus , from the user's point of view , accessing a KSAM le is very similar to accessing any other MPE le .
MULTIPLE KEYS Each data record can contain from one to sixteen keys. Of these keys, one is required, called the primary key; any others are alternate keys. For example, in an employee record, the primary key could be the employee's social security number; alternate keys might be the employee's name, phone number, or zip code. The values in these key elds determine the orders in which data records are sequenced. PRIMARY KEY. One eld in each data record is de ned to contain the primary key.
Note Generic keys cannot be used when accessing KSAM les through RPG. APPROXIMATE MATCH When retrieving by key value, you can specify that the key you are looking for have a value that exactly matches a speci ed value, or you can specify that it bear a certain relation to a speci ed value. The choices are: equal to, equal to or greater than, or greater than. The last two relations let you search for an approximate match.
Figure 1-1. A Simplified View of the KSAM File Structure HOW TO USE KSAM FILES Although a KSAM le consists physically of two separate les, a data and a key le, it is treated as one le for most purposes. For example, reading from a KSAM le in primary key sequence is equivalent to reading sequentially from a non-KSAM le. Similarly, creating the data le portion of a KSAM le is equivalent to creating a non-KSAM le.
CREATING A KSAM FILE A KSAM le can be created in two ways: interactively with the > BUILD command of the utility program KSAMUTIL, or programmatically with a call to the MPE le system intrinsic FOPEN. (A COBOL or BASIC programmer can create a KSAM le only through the > BUILD command, not FOPEN.) Whether > BUILD or FOPEN is used, le creation consists of creating a data le in very much the same way you would create any HP 3000 le. The name assigned to the data le is the name by which the KSAM le is known.
UPDATING RECORDS IN A KSAM FILE You can change the contents of an existing record by program calls that read the record into storage where you update it and then write it back to the le. The updated record overwrites the existing record in its current location if the new record and the old record are the same length. Otherwise, the new record is written to the end of the le and the old record is marked for deletion.
SHARED ACCESS TO KSAM FILES Several programs can access the same KSAM le simultaneously. Shared access is assumed when the le is only being read, exclusive access is assumed when the le is being written to or updated. Thus, you can choose to make all your access shared or all exclusive. Note that shared access uses more memory than exclusive access since each open KSAM le requires a separate extra data segment.
HOW TO USE THIS MANUAL There are some di erences in the way in which KSAM les can be accessed depending on the language in which you are programming. You should read the paragraphs below appropriate to your programming language and then turn to the last paragraph of this section, For All Programmers. RPG PROGRAMMER This manual does not describe the code required to access a KSAM le using RPG.
For ANSII standard COBOL, only alternate keys, not primary keys, can be duplicated. SPL PROGRAMMER If you are programming in SPL, you should read section II in order to learn how to: Create, purge, rename, clear the contents, display the status of, or save a KSAM le. These functions are provided by KSAMUTIL. Copy a KSAM le to another KSAM le in any key order. Display the contents of a KSAM le in any key order on the standard list device. These functions are provided by FCOPY.
FORTRAN PROGRAMMER If you are programming in FORTRAN, you should read section II in order to learn how to: Create, purge, rename, clear the contents, display the status of, or save a KSAM le using KSAMUTIL. Copy a KSAM le to another KSAM le in any key order with FCOPY. Display the contents of a KSAM le in any key order on the standard list device using FCOPY.
Change the key in preparation for a sequential read. Rewrite or delete an existing record. Dynamically lock and then unlock the le during shared access. ALL PROGRAMMERS Programmers using any of the languages that access KSAM les will probably need to refer to appendix A. This appendix contains an explanation of the error messages, condition codes, and status returns that can result from le access. Appendix B describes the internal structure of KSAM les.
2 USING KSAM UTILITIES USING KSAM UTILITIES A pair of utility programs and a set of commands allow you to create and manipulate KSAM les. OVERVIEW The program KSAMUTIL provides MPE capabilities that allow you to manipulate KSAM les. With KSAMUTIL commands, you can create a KSAM le, rename both the data and key les, save a temporary le as a permanent le, clear all data from a le, purge a le, and verify the contents and access history of an existing le.
Table 2-1. Summary of KSAM Utilities UTILITY KSAMUTIL FCOPY OPTION/COMMAND FUNCTION >BUILD or >B Create KSAM le consisting of a data le and key le. >ERASE Clear contents of KSAM data le and reset key le pointers. >PURGE Remove KSAM le from system. >RENAME or >R Change name of KSAM key or data le to a new name. >SAVE or >S Save session/job temporary KSAM le as a permanent le. >VERIFY or >V Display information on current status of data and keys in KSAM le.
KSAMUTIL UTILITY KSAMUTIL provides a number of capabilities, among which is the essential capability to create KSAM les. For a COBOL, BASIC, or RPG programmer, KSAM les can be created only through the BUILD command of the program KSAMUTIL. Although SPL and FORTRAN programmers can create KSAM les with the FOPEN intrinsic (described in section IV), the BUILD command may still provide these users with the simplest method for creating a KSAM le.
The resulting output is sent to the line printer identi ed as SLOWLP. OPTIONAL PARAMETERS. Wherever a command parameter is shown with brackets, [], that parameter can be omitted. For certain commands, SAVE, VERIFY, KEYDUMP, KEYSEQ, and KEYINFO, the lereference parameter is optional if no other parameters are speci ed. When this parameter is omitted, it assumes a prior command has speci ed a lereference and it uses the last lereference to identify the selected le.
HELP Requests help using KSAMUTIL HELP > H This command returns a summary description of each of the KSAMUTIL commands when entered at a terminal. The keyword \HELP" can be abbreviated to \H" . REQUESTING HELP The HELP command lists all the valid KSAMUTIL commands and then asks if you need information on a particular command. When you enter the name of a KSAMUTIL command, HELP displays the command syntax. HELP is terminated by entering N in response to the prompt MORE (Y/N)?.
ERASE MORE (Y/N)?Y ENTER COMMAND NAME: PURGE PURGE [,TEMP] MORE (Y/N)?Y ENTER COMMAND NAME: R RENAME , [,TEMP] MORE (Y/N)?Y ENTER COMMAND NAME: S SAVE [ ] MORE (Y/N)?Y ENTER COMMAND NAME: V VERIFY [ ] [;OFFLINE] [;NOCHECK] MORE (Y/N)?Y ENTER COMMAND NAME: KD KEYDUMP [ ] [;SEQ= ] [;SUBSET=[ [ minus;] ][, ]] I I ["CHAR-STRING"] [;FILE = ] I I [;OFFLINE ] [;SORT] MORE
BUILD Creates a KSAM le.
PARAMETERS lereference1 Actual le designator. This is the name that identi es the KSAM le (both data and key les) and also identi es the data le when speci ed independently of the key le. It has the form: lename [/lockword] [.groupname [.accountname] ] All four sub-parameters are names that contain from 1 to 8 alphanumeric characters, beginning with a letter. Note If speci ed, account name must be that of your log-on account; you cannot create a le in another account .
treated by MPE as a le with xed-length records, each record the size of a KSAM block (refer to blockfactor above for calculation of block size). Although the MPE LISTF command shows the data le as xed-length, the KSAMUTIL VERIFY command, option 3, shows DATA FIXED as FALSE when the le is a variable-length KSAM le. (Optional parameter.) BINARY ASCII TEMP DEV=device CODE= lecode Default: If both F and V are omitted, records are xed-length . Data le contains binary-coded records. (Optional parameter.
Note The CODE parameter applies only to data les; the key le code value is always 1080. DISC=numrec Total maximum le capacity, in terms of logical records (for les containing xed-length records). For les containing variable-length records, this is the maximum le capacity if all the records are maximum length. Maximum le capacity allowed is 2,097,120 sectors. (Optional parameter.) Default: If omitted, 1024 records is the default .
keylocation keysize keyblocking Location of the rst character of the key within the data record counting from the rst character in the record. The rst character in the data record is always numbered 1. Only one key can start at the same location. (Required parameter.) Length of the key in characters.
DUPLICATE In order to allow duplicate key values, this word must be included in the KEY speci cation. If DUPLICATE (or DUP) is not speci ed, records with DUP duplicate key values are rejected and an error message issued when such records are written to the le. DUP is a legal abbreviation of DUPLICATE. When you use this option to specify duplicate keys, each new duplicate key is inserted at the end of the duplicate key chain. This maintains the chronological order of duplicate keys.
is assigned to the same machine, and the key le device is speci ed in the KEYDEV= parameter. Device class names and logical device numbers are assigned to devices during system con guration. For KSAM les, the device must be a random-access device such as the disc. (Optional parameter.) Default: If omitted, the device class name DISC is used . FIRSTREC= Determines whether record numbers in the data le are to start with zero or one.
Table 2-2. Key Types keytype keysize (In Characters) Format BYTE 1-255 Each character requires 8 bits of a computer word. A character may contain any of the HP ASCII character set consisting of letters of the alphabet, numbers, and special characters. (Refer to appendix C.) INTEGER 1-255 (default = 2) Single-word xed-point format permits two's complement representation of positive and negative integers.
Table 2-3.
maximum number of data records), duplicate keys are prohibited, and record numbering starts with zero. File KSAMFILE is now created. Default values were used where possible so that the BUILD command speci cation shown above is the minimum needed to create a KSAM le. You could create the same le, KSAMFILE, with the following BUILD command in which default parameters are speci ed.
> > KEY=B,15,30,10;&<--------KEY=I,51,2,10&<----------- alternate key (employee name) alternate key (employee age) The keys are located in the data record as follows: Note that the keys need not be contiguous. In this example, the primary key is located nearer to the beginning of the record than the other keys. This is not a requirement; the primary key can physically follow any alternate keys in the record, although the primary key is always the rst key speci ed in the BUILD command.
ERASE Clears the contents of a KSAM le. lereference The contents of a KSAM le, both the data and key les, can be cleared to an empty state with the KSAMUTIL ERASE command. >ERASE PARAMETERS lereference Actual le designator that identi es the KSAM data le. It is speci ed exactly like lereference1 in the >BUILD command. (Required parameter.) CLEARING A KSAMFILE EXECUTE access is required to erase a KSAM le.
PURGE Purges a KSAM le from the system. lereference [,TEMP] The KSAMUTIL PURGE command can be used to remove a KSAM le, both data and key les, from the system. Although the MPE :PURGE command can also be used, it must be speci ed twice, once for the data le and once for the key le. If you are programming in COBOL, BASIC, or RPG, you should use the KSAMUTIL PURGE command to purge a KSAM le. In SPL or FORTRAN you could also use the FCLOSE intrinsic (described in section IV) to purge a KSAM le.
RENAME Renames either the data or key le of a KSAM le. > 2 3 RENAME old lereference, new lereference ,TEMP R The KSAMUTIL RENAME command can be used to change either the KSAM data le name or the KSAM key le name to a new name. Following execution of RENAME, the data and key les retain their relation to each other. Note that if the MPE :RENAME command is used, this relation is severed . The FRENAME intrinsic cannot be used to rename a KSAM le.
Note that only one RENAME command is used. This one command insures that both the data le and the key le are in the same group.
SAVE Saves a temporary KSAM le as a permanent le. SAVE > S 2 lereference 3 A temporary KSAM data le and its associated key le are made permanent with the KSAMUTIL SAVE command. The keyword \SAVE" can be abbreviated to \S". PARAMETERS lereference Actual le designator identifying the session/job temporary le to be saved, speci ed exactly like lereference1 in the >BUILD command. (Optional parameter.) Default: If omitted, last lereference is assumed .
VERIFY Displays access and status information about KSAM le. VERIFY > V 2 32 32 lereference ;OFFLINE ;NOCHECK 3 With the VERIFY command, you can request a display of the characteristics of a KSAM data le, both the static information de ned at le creation and dynamic le access information. The abbreviation V can be used instead of the keyword VERIFY. PARAMETERS lereference Actual le designator identifying the le whose characteristics are to be displayed.
HP32208A.2,4 TUE, APR 17, 1979, 11:23 AM >VERIFY TESTFILE KSAMUTIL VERSION:A.2.4 select le 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.
MIN PRIME DATA FIXED FIRST RECNUM 3 MAX PRIME TRUE DATA B/F 0 MIN PECSIZE 1 RESET DATE 1 TOTAL KFYS 31 2 The dynamic key le information displayed by option 3 together with the static key le 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 le was created.
KEYSEQ Veri es sequence of key values in KSAM le. KEYSEQ > KS 2 32 32 32 lereference ;SEQ=keysequence ;OFFLINE ;NOLIST 3 This command compares all the key values in a particular key (primary or alternate) to determine whether they are in ascending sequence. If any values are out of sequence, a list of numbers identifying such values is displayed, unless NOLIST is speci ed. In any case, the number of outquence values is returned.
VERIFY KEY SEQUENCE If you suspect that your key le has out of order key values in any key, you can run KEYSEQ. If any key values are not in ascending sequence, the key numbers associated with those key values are displayed. Note that the number of a key value refers to its position in the key le. For example, if the third, fourth, and fth key values of a particular key are out of sequence, the numbers 3, 4, and 5 are displayed.
Note that NOLIST was speci ed. In general this is good practice. If any key values are not in sequence, the le should be reloaded, so it is seldom important to know which keys are out of sequence.
KEYDUMP Provides formatted, structural dump of key le. 3 32 KEYDUMP 2 lereference ;SEQ=keysequence > KD 33 92 2 82 3 , number 0 ;SUBSET= position "string" 2 32 3 ;OFFLINE ;SORT 2 ;FILE =formaldesignator 3 The key le dump consists of three items of information for each key value: 1. Key Value The actual value of each key in ascending order The record number ( xed-length les) or word o set (variable-length les) of 2. Record the data record to which the associated key value points. Pointer 3.
(Optional parameter.) SUBSET= [0]position \string " ,number FILE = lename Default: If omitted, the primary key is selected. Select a portion of the key le to dump, based on the numeric position of the key or the key value, and the number of key values. Start dump with key whose number is speci ed. This number is the same as the key number issued by KEYSEQ. It corresponds to the position of the key value in the le in ascending sequence.
Default: If omitted, key dump is in ascending sequence by key value. DUMPING THE KEY FILE The dump produced by KEYDUMP consists of three columns: the rst contains the key value, the second a pointer to a record number in the data le, and the third contains the key block address and the number of key values in that block. The key block address is given as the record number of the rst record in any block. For example, assume that TESTFILE contains an INTEGER type primary key whose values we want to see.
length records each one sector long|128 words. Thus, the record number is also the sector number. A keyblock consists of more than one sectors|default is 8 sectors). Key values are organized into blocks using a B-Tree structure (refer to appendix B for details). This structure has one or more levels where the rst or highest level, is known as the \root" and lower level are \leaves". This dump shows the level structure of the key le by indenting the key block addresses to correspond to levels.
DUMPING A SUBSET OF THE KEY FILE If you want to dump a selected number of key values rather than all the values in a key, you can use the SUBSET option of KEYDUMP. The starting key value can be located in two ways: if you know the key number of the rst key value you want displayed, use the SUBSET=position format; if you know the actual key value (or a value less than the key value), then you can use the SUBSET=\string" format.
KEY REC.PTR. KEY BLOCK ADR. GIBBS GILLESPIE GLADSTONE HERTZ HIGGINS JONES LOOMIS MORRIS MYERS NOLAN 3 12 4 8 0 7 13 5 6 1 2 (4) 2 2 2 8(3) 16(4) 16 16 16 8 SORTING DUMP BY RECORD POINTER If you use the SORT option of KEYDUMP, you must also specify ENTITY = lename , where the speci ed le name is that of a disc le. (Note that you must not name an existing le; a new le is created for the dump.) In this case, you might also want to suppress the indention of the key block address levels.
KEYINFO Displays information about the key le, and attempts recovery of a KSAM le in case of system failure when the le is open. KEYINFO > K1 2 32 32 lereference ;OFFLINE ;RECOVER 3 KEYINFO performs two operations: it collects and displays information about the key le, and it takes steps to recover the KSAM le in case a system crash occurred when the le was open. The second operation is performed only after a system crash or if the RECOVER parameter is speci ed.
(Optional parameter.) Default: If omitted, recovery performed only if system crashed with le open. REQUESTING KEY FILE INFORMATION Information is displayed by KEYINFO for each key in the key le, in key order starting with the primary key.
KEY ENTITY=KEYFIL KEY FILE DEVICE=2 SIZE= 50 KEYS= FLAGWORD(000000)=RANDOM PRIMARY, FIRST RECORD=0, PERMANENT KEY TY LENGTH LOC. D KEY BF LEVEL | |----------- blocking factor, keys/block 1 B 30 1 Y 52 1 2 B 2 31 Y 202 1 3 B 6 33 Y 144 1 3 # OF KEYS IN B-TREE - This is the total number of key values in the key le for each key.
MIN PRIME DATA FIXED FIRST PECNUM 11 MAX PRIME TRUE DATA B/F 0 MIN PECSIZE 5 RESET DATE 1 TOTAL KEYS 38 67/'79 3 RECOVERING AFTER SYSTEM FAILURE KEYINFO only performs the recovery operations if there has been a system failure or if you specify the RECOVER parameter. If there has been a system failure while the KSAM le is open for non-read access, a ag is set that prevents the le from being opened. Whenever this occurs, KEYINFO must be used in order to reset this ag so that the le can be opened.
>KI TEST RECOVERY BEGINS DATA FILE EOF DAMAGED DATA FILE MPE EOF HAS BEEN RESET TO KSAM EOF reset end-of- le for data le -------- INFO FOR KEY 1 --------- # OF LEVELS OF B-TREE # OF KEY BLOCKS # OF SECTORS PER KEY BLOCK # OF KEYS IN ROOT KEY BLOCK # OF KEYS IN B-TREE # OF KEY BLOCK UTILIZATION THE LARGEST KEY BLOCK ADDRESS 2 16 8 14 1000<------| 52.
group, and home group, but does not increment the SYSTEM FAILURE count displayed by VERIFY. Note that checking each record and key in a le with a lot of data is very time consuming. Therefore, you should not use RECOVER unless it is necessary to reconstitute your le.
USING KSAMUTIL IN BATCH MODE A batch job can be developed on the text editor (EDITOR) and then executed with the MPE :STREAM command. In order to distinguish the MPE commands within a streamed batch job from those external to the job, an exclamation point (!) is used as the command pre x rather than a colon (:). KSAMUTIL commands have no command pre x when executed in a batch job.
Figure 2-1.
FCOPY UTILITY FCOPY/3000 is the standard HP 3000 utility program that allows you to copy data from one le to another, creating a new KSAM le is desired, to copy selected data, to make multiple copies of the same le, or to display data in a variety of formats. With some exceptions, the same FCOPY functions used to copy other HP 3000 les can be used to copy KSAM les. Table 2-4 contains a summary of the FCOPY function parameters that apply to copying KSAM les.
FCOPY FROM COMMAND Copies data from one le to another. > FROM= [from le] ;TO= [to le] [;functionlist] The FROM command speci es the le from which data is copied and the le to which it is copied. It optionally includes one or more function speci cations in the functionlist parameter. PARAMETERS from le to le functionlist Speci es the le to be copied. For a KSAM le this should be the actual le designator.
Table 2-4. FCOPY Functions with KSAM Files FUNCTION LIST ENTRY* ACTION PERFORMED ;KEY=nn Copy active records from KSAM le in sequence by key located at nn ; if omitted, copy le in primary key sequence; if nn is zero, copy le in chronological order. The KSAM EOF is used. ;NOKSAM Copy all records, including deleted records, from data le of KSAM le to any other le. Copy is in chronological sequence; records must be xed length.
Table 2-4. FCOPY Functions with KSAM Files (continued) FUNCTION LIST ENTRY* 2 32 3 ;OCTAL ;CHAR ;NORECNUM 2 3 2 3 ;HEX ;CHAR ;TITLE= "title" 3 2 32 ;CHAR ;NORECNUM ;TITLE= "title" 2 3 ;OCTAL ;NORECNUM ;HEX 3 2 ;TITLE= "title" ACTION PERFORMED Display contents of \from" le as octal images on a word-by-word basis. Display contents of \from" le as hexadecimal images on a word-by-word basis. Display contents of \from" le as character images on a word-by-word basis.
failure, you should rst run the KEYINFO command of KSAMUTIL to reset the end-of- le markers and delete any invalid key values. If the le is still damaged and you choose to reload it, you should use FCOPY to transfer existing records to a new undamaged KSAM le. In this case, you use the KEY=0 option rather than the NOKSAM option, unless you want to keep all the deleted records or the key le was lost. FCOPY WITH NO OPTIONS.
The new le, KSAMFIL3, is created with exactly the same speci cations as the existing le KSAMFILE, but with no data. This is easier than building the le with the BUILD command, but should be used only if the new le is to have keys in the same position and the same length as the existing le. Following any of these operations, only active records are contained in the new KSAM les.
FCOPY WITH KEY = OPTIONS. 1. Assume that a company's employee records have been maintained in sequence by social-security-number in a KSAM le, EMPLOY, but a new policy requires that they be maintained in sequence by employee number. FCOPY can be used to transfer the data to a new le, EMPLOY2, in which all employees are re-ordered by their unique employee numbers. Assume EMPLOY was created with the following command: :RUN KSAMUTIL.PUB.
The new le EMPLOY is sequenced by the key starting in column 19 (employee name) and only contains records for employees whose last names start with A. 3. If you want to copy the KSAM le in chronological sequence, you can use the KEY=0 option. Since this option copies only active records, it can be used to compact a le in which many records are tagged for deletion while retaining the chronological order in which the le was created.
only valid records. Normally, you use the KEY=0 option to reload KSAM les after a system failure. (Refer to appendix E, Recovery From System Failure, for a full discussion of using FCOPY to reload a KSAM le following a system failure.) COPYING VARIABLE-LENGTH KSAM FILES You can copy a variable-length KSAM data le by rst copying it to an MPE le and then copying the MPE le to a new KSAM le. First use the MPE :LISTF,2 command to list the attributes of the KSAM data le.
>FROM=JNAMES;TO=;KEY=11;SUBSET=0,2 JEANNE ALOGICAL 226-0295 4942 COUSIN CT SUNNYVALE POLLY CHROMATIC 267-1413 1148 COLORFUL CT SAN JOSE 95054 95030 2 RECORDS PROCESSED *** 0 ERRORS 2.
Another example using SUBSET= lists ve records starting with the fourth record; sequence is by alternate key in location 67: records numbered from O | | | >FROM=JNAMES;TO=;KEY=67;SUBSET=3,5 ANNA LOGUE 224-9934 1707 JEANNE ALOGICAL 226-0295 4942 RHEA PREYSELLE 365-8551 10789 ANNE HOWE 372-4328 6547 MIKE ROMETER 269-1712 1681 5 RECORDS PROCESSED *** 0 ERRORS INVERSE WY COUSIN CT REVIEW ROAD EXUBERANCE WY MACHINIST DR MOUNTAIN VIEW SUNNYVALE SAN JOSE CAMPBELL SUNNYVALE 95051 95054 95070 95112 95112 4.
:STORE AND :RESTORE COMMANDS The :STORE and :RESTORE commands are used primarily to provide back-up for user disc les. The le or set of les is copied to magnetic tape or serial disc by the :STORE command in a special format that permits the serial device to be read back onto disc with the :RESTORE command. The use of these two commands for KSAM les is identical to their use with any HP 3000 les. (Refer to the MPE Commands Reference Manual for a complete description of the :STORE and :RESTORE commands.
USING THE :STORE COMMAND Before issuing a :STORE command, you must identify the store le as a magnetic tape or as a serial disc with the :FILE command using the following format: :FILE formaldesignator [= lereference] ;DEV=device The device parameter must indicate the device class name or logical unit number of a magnetic tape or serial disc unit, All other parameters for store le are supplied by the :STORE command executor; if you attempt to supply any of these yourself, MPE rejects the :STORE command.
RESTORE Restores KSAM le from magnetic tape or serial disc. :RESTORE restore le ; lereference1, lereference2[, . . .] [;KEEP] [;DEV=device] [;SHOW] [;FILES=maxfiles] Restores to disc, one or more les stored o -line to magnetic tape or serial disc by the :STORE command. To restore a KSAM le, both the data le and the key le names must be speci ed. PARAMETERS restore le lereference1 lereference2 KEEP DEV=device 2-56 Name of magnetic tape or serial disc le on which les to be retrieved now reside.
and the key le on di erent devices, then RESTORE twice using di erent DEV=device in each RESTORE. SHOW (Optional parameter.) Request to list names of restored les. If you omit SHOW, only total number of les restored, list of les not restored (and the reason each was not restored), and count of les not restored, are listed. FILES= (Optional parameter.) Maximum number of les that may be restored. If omitted, 4000 is assigned by default. max les (Optional parameter.
3 USING KSAM FILES IN COBOL PROGRAMS OVERVIEW KSAM les are accessed from COBOL programs through calls to a set of procedures. These procedures allow you to open, open for shared access, write records to, read records from, lock, unlock, update, position, and close a KSAM le. (Refer to Table 3-1 for a list of the procedures and their associated functions.) The COBOL procedures provided with KSAM/3000 correspond to the INDEXED I-O module statements in COBOL 74.
Table 3-1. KSAM Procedures for COBOL Interface PROCEDURE NAME PARAMETERS FUNCTION PAGE CKCLOSE letable status Terminates processing of KSAM le identi ed by letable . 3-12 CKDELETE letable status Logically removes record from KSAM le; deleted record is identi ed by previous read. 3-13 CKERROR status , result Converts numeric value returned in status to character string result . 3-17 Dynamically locks le opened for shared access, conditionally depending on lockcond .
CALLING A KSAM PROCEDURE The KSAM interface procedures (refer to Table 3-1 for a complete list) are called using a CALL statement of of the following general form: CALL "name" USING letable,status [,parameter[,. . .] ] Where: \name" letable status parameter identi es the procedure to which control is transferred.
FILETABLE PARAMETER The rst parameter in every KSAM procedure call must be letable , a table describing the le and its access. This table is de ned in the WORKING-STORAGE SECTION of the COBOL program. It requires eight words as illustrated in Figure 3-1. Figure 3-1. Filetable Structure lenumber lename input-output type access mode A number identifying the le returned by the CKOPEN procedure after the le named in words 2-5 has been successfully opened.
FILETABLE previous operation lock/unlock A code in the right byte of word 8 of the le table indicating the previous successful operation: 0 = previous operation unsuccessful or there has been no previous operation on this le 1 = CKOPEN successful 2 = CKSTART successful 3 = CKREAD successful 4 = CKREADBYKEY successful 5 = CKDELETE successful 6 = CKWRITE successful 7 = CKREWRITE successful 8 = CKCLOSE successful 9 = CKOPENSHR This eld should be set to zero when the le table is initially de ned and thereaft
STATUS PARAMETER The status parameter is a two-character item to which the status of the input-output operation is returned. It is always the second parameter in a KSAM procedure call. The status parameter must be de ned in the WORKING-STORAGE SECTION of the COBOL program. Status consists of two separate characters: the left character is known as status-key-1, and the right is known as status-key-2.
STATUS If status = \10" = \21" = \22" = \23" = \24" = \30" = \31" = \9n " At End condition | In a sequential read using CKREAD, no next logical record was in the le. Invalid key; Sequence error | A call to CKWRITE attempted to write a record with a key that is not in sequentially ascending order, to a le opened for sequential access. A call to CKREWRITE was attempted but the primary key value was changed by the program since the previous successful call to CKREAD.
STATUS USING STATUS The value of status can be tested as a whole, or the two characters can be tested separately as status-key-1 and status-key-2 . In any case, the status of each call should be tested immediately following execution of the call. Unless the rst character of status = \0", the call was not successful. For example, a sample status parameter de nition might be: WORKING-STORAGE SECTION. . . . 01 STAT. 02 STATUS-KEY-1 PIC X. 02 STATUS-KEY-2 PIC X.
Table 3-3. Positioning the Logical Record Pointer Procedure Name PointerDependent Position of Pointer After Execution of Procedure CKSTART NO Points to key whose value was speci ed in call. CKREADBYKEY NO Points to key whose value was speci ed in call. CKWRITE NO Points to key whose value is next in key sequence to key value in record just written.
SAMPLE KSAM FILE The le KSAMFILE illustrated in Figure 3-2 is used in all subsequent examples associated with the COBOL procedure calls. Figure 3-2.
CKCLOSE A call to CKCLOSE terminates le processing for the speci ed le. letable, status When processing is completed, a KSAM le should be closed with a call to CKCLOSE. No further processing is allowed on the le until a CKOPEN procedure call opens the le. CKCLOSE can be executed only for a le that is open.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
CKDELETE This procedure logically deletes a record from a KSAM le. leable, status In order to logically delete records from a KSAM le, you can use the procedure CKDELETE. A logically deleted record is marked by a code of binary 1's in the rst two characters of the record, but is not physically removed from the le. The deletion mark makes such a record inaccessible but does not physically reduce the size of the le.
