Method and means for cataloging data sets using dual keyed data sets and direct pointers

Abstract

A data set catalog structure eliminates the requirement for base catalog/data volume synchronization in a multi-processing environment while enabling the operating efficiency directly addressing the data volumes. The catalog is distributed between a keyed sequential base catalog and, on each data volume, an entry sequential volume data set. Catalog information which must be synchronized with application data sets is stored in volume records in the volume data set. A method for opening a user's data set having a key comprises the steps of obtaining from the base catalog a direct pointer associated with the key to the volume record for the user data set; accessing the volume record (relative byte address) addressed by the pointer; comparing the key of the user data set with the key of the accessed volume record; if the keys do not compare, key searching the volume data set to locate the volume record containing correct key and rewriting the direct pointer in the base catalog to address the correct volume record, and obtaining from the correct volume record a direct pointer to the user data set.

Claims

I claim:

1. A method for operating a computing system under control of a catalog management facility referencing a catalog data set residing on a first data volume to open a user data set residing on a second data volume, where said first or second data volume may have been changed by events external to the catalog management facility, resulting in loss of synchronization between said user data set and said catalog data set, comprising the steps of;

searching said catalog data set for a first record keyed to said user data set, said first record including a pointer to a second record in a volume data set residing on said second data volume;

responsive to said pointer, retrieving said second record;

testing the key of said second record to detect a loss of synchronization; and,

if said second record is keyed to said user data set and thus indicates synchronization, opening the user data set described by said second record; otherwise, searching said volume data set in said second data volume to retrieve a third record keyed to said user data set, and upon locating said third record, updating said pointer to reestablish synchronization between said pointer and said user data set, and opening the user data set described by said third record;

whereby said user data set is opened without signaling an error to the user even though loss of synchronization has previously resulted from an external event such as a restoration of said first data volume or said second data volume from an archival data volume.

2. The method of claim 1 for operating said computing system further to define said user data set on said data volume, comprising the steps of:

serializing said catalog data set and said volume data set for write access;

allocating space on said data volume for said user data set;

generating said second record to include said key and extent information describing said allocated space;

writing said second record into said volume data set;

generating said first record to include said key and a pointer to said second record; and

writing said first record into said catalog data set.

3. The method of claim 1 for operating said computing system further to recatalog a second user data set, comprising the steps of:

serializing said catalog data set for write access;

searching said volume data set to retrieve a fourth record keyed to said second user data set;

generating a fifth record to include the key of said second user data set and a pointer to said fourth record;

writing said fifth record into said catalog data set.

4. The method of claim 2 for operating said computing system in a multiprocessing environment wherein said data volume is shared by at least two loosely coupled central processors, and wherein said serializing step, when performed by one central processor, comprises the further step of locking said catalog data set and said volume data set against access by all other central processsors sharing said data volume.

5. The method of claim 4, comprising the further steps of:

maintaining in said volume data set a catalog self-describing volume record including a data set characteristics field and a first time field updated during each write access to said catalog data set to record the time of write access;

maintaining for said catalog data set in said one central processor a plurality of control block fields including a second time field updated during each write access to said catalog data set by said one central processor to record the time of write access; and

the serializing step comprising the further steps performed by said one central processor of:

comparing said first and second time fields and, if not equal, updating said plurality of control block fields from data set characteristics in said self-describing volume record, and setting said second time field equal to said first time field;

whereby said catalog data set characteristics are maintained current in all central processors sharing access to said catalog data set.

6. A method for operating a computing system under control of a catalog management facility referencing a catalog data set, the computing system including at least one central processing unit coupled to at least one data volume, to open a user data set in said data volume, the user data set being identified by a data set key, and wherein said data volume may have been changed by events unknown to said catalog management facility, resulting in loss of synchronization between said user data set and said catalog data set, the method comprising the steps of:

(1) retrieving from said catalog data set a sphere record associated by key with said user data set;

(2) fetching from said sphere record a first address to a first volume record in a keyed volume data set residing on said data volume;

(3) responsive to said first address, retrieving from said volume data set said first volume record;

(4) comparing the key of said first volume record with said data set key to detect a loss of synchronization;

(5) if said keys do not compare equal, key searching said volume data set for the volume record containing the correct key, and updating said sphere record to contain the address of the correct volume record; and

(6) building user data set control blocks from data set characteristics contained in the volume record key associated with said user data set;

whereby said user data set is opened without signaling an error to a user even though the catalog data set and the user data set may have lost synchronization as a result of an external event such as restoration of said data volume from an archival data volume.

7. The method of claim 6 for operating said computing system further to define said user data set on said and volume, comprising the steps of:

serializing said catalog data set and said volume data set for write access;

allocating space on said data volume for said user data set;

generating a volume record to include said key and extent information describing the allocated space;

writing the generated volume record into said volume data set;

generating a sphere record to include said key and a pointer to said generated volume record; and

writing the generated sphere record into said catalog data set.

8. The method of claim 7 for operating said computing system to extend said user data set, comprising the steps of:

serializing said volume data set for write access;

allocating additional space on said data volume for said user data set;

retrieving from said catalog data set the generated sphere record;

responsive to the pointer and, selectively, the key fields of said generated sphere record, retrieving said generated volume record from said volume data set;

updating said generated volume record to describe the new allocation of space on said data volume;

writing the updated volume record into said volume data set; and, if the updated volume record was written into a different location than said generated volume record, updating the generated sphere record to point to said updated volume record.

9. The method of claim 7 for operating said computing system further to recatalog said user data set, comprising the steps of:

serializing said catalog data set for write access;

searching said volume data set to retrieve the volume record containing the key of said user data set;

generating a recatalog sphere record to include said key and a pointer to the retrieved volume record, and writing the recatalog sphere record into said catalog data set.

10. The method of claim 7 for operating said computing system to create, prior to defining said user data set, a volume data set for storing the volume records, comprising the steps of:

allocating space on said data volume for said volume data set;

generating a volume control record, including fields identifying the catalog data set(s) using said volume data set and a control interval space map for recording for each control interval in the volume data set indicia representative of control interval space utilization; and

writing said volume data set into said data volume.

11. The method of claim 10 for operating said computing system to write a volume record into said volume data set, comprising the steps of:

searching said volume control record for the name of the requesting catalog data set associated with a request to write a new volume record and, if not present, inserting the name;

searching said volume control record space map for a first control interval with adequate free space for said new volume record;

accessing said first control interval to insert said new volume record;

updating said free space map to reflect the new space utilization of said first control interval; and

generating a new sphere record containing the address of said first control interval as a pointer to said new volume record; and

writing said new sphere record into said requesting catalog data set.

12. The method of claim 7 for operating said computing system to define a catalog data set preliminary to defining said user data set, comprising the steps of:

allocating space on a volume for said catalog data set;

generating catalog self-describing volume records including catalog identification and extent information;

writing said catalog self-describing volume records into the volume data set;

inserting the name of said catalog data set and the addresses of said catalog self-describing volume records into a volume control record within said volume data set;

generating a catalog self-describing sphere record containing the name of said catalog data set and address pointers to said self-describing volume records; and

writing said catalog self-describing sphere record into the space allocated on the volume for the catalog data set.

13. The method of claim 12 further for opening said catalog data set when the catalog self-describing sphere record is not available such as when the catalog data set is not in an open state, comprising the steps of:

searching said volume control record for the name of said catalog data set and fetching the associated address pointers;

responsive to said associated address pointers, retrieving from said volume data set, the catalog self-describing volume records;

verifying that said associated address pointers are correct and, if not, updating said volume control record with the correct address pointers; and

opening the catalog data set from data set characteristics and extent information contained in said catalog self-describing volume records.

14. The method of claim 12 for operating said computing system, the computing system including at least two central processing units sharing said data volume for one central processing unit to serialize a read operation, the method comprising the steps of:

maintaining in said catalog self-describing volume record a first time field updated during each write access to said catalog data set to record the time of write access;

maintaining in each central processing unit a write access time field updated during each write access by said each central processing unit to said catalog data set to record the time of write access; and

after serializing a read or write operation by said one central processing unit, comparing said first time field with the write access time field of said one central processing unit, and if they do not correspond, updating catalog control blocks describing said catalog data set and updating the write access time field.

15. The method of claim 14 for operating said computing system in a multiprocessing environment to serialize a write operation by one central processor comprising the further step of locking said catalog data set and said volume data set against access by the other central processors.

16. A method for operating a computing system to catalog user data sets on a plurality of data volumes, the computing system including at least two loosely coupled processors sharing access to at least one of said data volumes, the method establishing a catalog structure, including a base catalog structure, residing on the shared data volume, which enables the opening of a user data set on a second data volume even where an external event has changed a data volume, resulting in loss of synchronization between said base catalog and said user data set, the method comprising the steps of:

defining a base catalog structure by:

allocating space on said shared data volume for the base catalog structure;

generating a data volume record and an index volume record for describing the base catalog structure data and index components;

writing said data volume record and said index volume record into addressable locations in a volume data set on said shared data volume;

inserting the catalog name and pointers to said data volume record and index volume record into a volume control record in said volume data set;

generating a catalog sphere record including direct address pointers to said data volume record and said index volume record; and

writing said catalog sphere record into said base catalog structure on said shared data volume;

and

defining a plurality of user data sets into a catalog, each data set having a key name, and the catalog including said base catalog structure and said volume data set, by executing the following steps for each user data set to be defined:

allocating space on said second data volume for a user data set:

generating one or more user volume records for describing said user data set;

writing said user volume records into an addressable location in said volume data set;

generating a user sphere record, including direct address pointers to said user volume records and the key names of the user data set components;

writing said user sphere record into said base catalog structure.

17. The method of claim 16 further for operating said computing system to open a specified user data set identified by a given key comprising the steps of:

searching said base catalog for a specified sphere record containing said given key;

retrieving from said specified sphere record a first address pointer to a first volume record;

responsive to said first address pointer, retrieving said first volume record;

comparing said given key with the key name of said first volume record; if said given key and said key name of said first volume record do not correspond and thus indicate a loss of synchronization, searching said volume data set to retrieve a second volume record having a key name corresponding to said given key, and updating said first address pointer to address said second volume record; and

building the control blocks to open said specified user data set from data set characteristics contained in the volume record identified by said given key.

18. Apparatus for cataloging user data sets stored on a data volume to enable opening of a user data set by a central processor having access to the data volume and a main storage, said apparatus enabling opening of a user data set even though residing on a volume which, due to some external event, has been changed to cause loss of synchronization, the apparatus comprising:

means providing a volume data set for storing a plurality of volume records each containing identification information including at least one key field and extent information for user data sets recorded on the data volume;

base catalog means for storing a plurality of sphere records, each sphere record containing one or more key fields identifying a user data set and a direct address pointer to a corresponding volume record;

means for opening a first user data set having a key name by building, in the main storage, control blocks providing user data set identification and extent information, said means for opening including:

first means for searching said base catalog means for a first sphere record containing said key name in its key field;

second means responsive to the direct address pointer stored in said first sphere record for retrieving a first volume record;

third means for comparing said key name with a first key field of said first volume record;

fourth means, responsive to a failure of correspondence between said key name and said first key field and thus indicative of a loss of synchronization, for searching said volume data set means for a second volume record containing a second key field corresponding to said key name, and for writing into said first sphere record a direct address pointer to said second volume record; and

means for retrieving information defining the extent of said first user data set from that one of said volume records which contains a key field corresponding to said key name.

19. The apparatus of claim 18 further comprising:

self-describing sphere record means stored in said base catalog means for storing direct address pointers to self-describing volume records containing extent information for said base catalog means;

volume control record means stored in the volume data set for storing direct address pointers to said self-describing volume records containing extent information for said base catalog means;

means for opening said base catalog means, including means responsive selectively to said self-describing sphere record means or said volume control record means for accessing said self-describing volume records to obtain the base catalog extent information.

20. The apparatus of claim 18 further comprising:

means responsive to a request for defining a first user data set on a data volume for allocating space on said data volume for said volume data set; and

means for generating and writing into said volume data set a volume control record including fields for identifying related base catalog means and fields for recording indicia representative of the space utilization of control intervals within said volume data set.

21. The apparatus of claim 20, further responsive to a request to define a user data set for generating associated sphere record and volume records, the means for generating including:

means for searching said volume control record for an addressable control interval with sufficient space for said associated volume record;

means for writing said associated volume record into said addressable control interval;

means for recording in said associated sphere record the address of said addressable control interval.

Description

TECHNICAL FIELD

This invention relates generally to data processing systems, and more particularly to a catalog structure and method for opening data sets on shared volumes in a multi-processing environment.

BACKGROUND ART

As used in this specification, the term "computing system" includes a CPU with main storage, input/output channel control units, direct access storage devices, and other I/O devices coupled thereto such as is described in G. M. Amdahl, et al., U.S. Pat. No. 3,400,371, issued Sept. 3, 1968 and entitled, "Data Processing System". An "operating system" consists of a set of supervisory routines for controlling the operating of a computing system, including one or more of the following major functions: task management, storage management, input/output management, and data management. An "application program" is a program written to do a user's work, usually in a high-level language, and is loade into main storage and executed under the supervision of the operating system's task manager. A "data set" is any group of related data that one or more users may wish to access. A "record" is a subset of a data set containing all information relating to one element of related data that comprises a data set. A "pointer" is a register, main storage location, or portion of a data set record which contains the main storage or auxiliary storage address of a data item. An example of a pointer is the relative byte address (RBA) of a control interval (CI). A "key" is a register, main storage location, or portion of a data set record which provides an identifier (which may be unique) of the record. A "volume" is a certain portion of data, together with its data carrier (such as a drum, a disk pack, or part of a disk storage module) that can be conveniently handled as a unit. "Open" means to prepare a data set or file for processing; this is done by establishing control blocks in main storage describing the data set and controlling access thereto.

Data management performs the function of controlling the acquisition, analysis, storage, retrieval, and distribution of data. In so doing, it must control all operations associated with input/output devices, such as: allocating space on volumes, channel scheduling, storing, naming, and cataloging data sets, moving data between real and auxiliary storage, and handling errors that occur during input/output operations. The data management routines include access methods, catalog management, direct access device space management (DADSM), and open/close/end-of-volume support. Inasmuch as the method of this invention, in its operation of a computing system, relates to certain portions of these routines, they will be more fully described. Reference is made to IBM System/370 System Summary, IBM Publication Number GA 22-7001-6 (Dec. 1976), and IBM System/360 Operating System Introduction, IBM Publication Number GC 22-6534.

Access methods operate the computing system to move information between virtual storage and external storage, and maintain it in external storage. A variety of techniques and data set organizations are known in the prior art for gaining access to a data set.

A variety of data set organizations may be employed, including the following: sequential, partitioned, indexed sequential, and direct. Basic access methods, which can be used with each of the above data set organizations, include the following: basic sequential (BSAM), basic direct (BDAM), basic indexed sequential (BISAM), and basic partitioned (BPAM). Queued access methods, which can be used only with sequential and indexed sequential data set organizations, are the queued sequential (QSAM) and queued indexed sequential (QISAM).

BSAM sequentially organizes data and stores or retrieves physical blocks of data.

BDAM organizes records within a data set on direct access volumes in any manner the pro grammer selects. Storage or retrieval of a record is set by actual or relative address within the data set. This address can be that of the desired record, or a starting point within the data set, where a search for the record based on a key furnished by a programmer begins. BDAM also uses addresses as starting points for searching for available space for new records.

BISAM stores and retrieves records randomly from an indexed sequential data set. It reads selectively by using the READ macro instruction and specifying the key of the logical record to be retrieved. Individual records can be replaced or added randomly.

BPAM, when used in conjunction with BSAM, stores and retrieves discrete sequences of data (members) belonging to the same data set on a direct access device. Each member has a simple name with the address where the sequence begins. Members can be added to a partitioned data set as long as space is available. (BPAM is usually used to store or retrieve programs).

QSAM organizes data sequentially. It retrieves and stores logical records as requested. QSAM anticipates the need for records based on their sequential order, and normally has the desired record in virtual storage, ready for use before the request for retrieval. When writing data to external storage, the program normally continues as if the record has been written immediately although QSAM's routines may block it with other logical records, and defer the actual writing until the output buffer has been filled.

QISAM creates an indexed sequential data set and retrieves and updates records sequentially from such a data set. Synchronization of the program with the completion of I/O transfer and record blocking/deblocking are automatic. QISAM can also reorganize an existing data set.

The virtual storage access method (VSAM) employs a modified basic and queued access technique and applies to both direct and sequential data sets. VSAM is used with direct access storage devices on the IBM System/370 VS1, SVS and MVS operating systems. It creates and maintains two types of data sets. One is sequenced by a key field within each record and is called a key-sequenced data set (KSDS). Data records are located by using the key field and an index that records key fields and the address of the associated data, similar to ISAM. The other is sequenced by the time of arrival of each record into the data set and is called an entry-sequenced data set (ESDS). Data records are located by using the record's displacement from the beginning of the data set. The displacement is called the RBA (relative byte address). The RBA is similar to the relative block address used with BDAM.

DADSM consists of routines that allocate space on direct access volumes to data sets. The routines are used primarily by job management routines during the initiation of job steps when space is obtained for output data sets. They are also used by other data management routines for increasing the space already assigned to a data set, and for releasing space no longer needed.

When space is needed on a volume, the DADSM routines check the volume table of contents (VTOC) for enough available contiguous tracks to satisfy the request. If there are not enough contiguous tracks, the request is filled using noncontiguous groups of free tracks.

Open/close/end-of-volume (O/C/EOV) support routines;

Open a data control block (DCB) or access method control block (ACB) before a data is read or written.

Close a data control block or access method control block after a data set has been read or written.

Process end-of-volume (EOV) conditions when an end-of-volume or end-of-data (EOD) set condition occurs during an I/O operation.

Open Processing: Before accessing a data set, an OPEN macro instruction must open the DCB (data control block) or ACB (access method control block) for that data set. When a processing program issues an OPEN macro instruction, the open routine of the control program:

Verifies the mounting of volumes.

Merges data set attributes from the data definition (DD) statement, VTOC or catalog into the control blocks.

Determines access method routines.

Close Processing: After processing has been completed for a data set, a CLOSE macro instruction must close the DCB or ACB for that data set. When a processing program issues a CLOSE macro instruction, the close routine of the control program:

Processes input and output labels.

Updates data set attributes and statistics in the catalog.

Disposes of volumes.

Frees control blocks.

Restores the DCB or ACB to its original pre-open condition.

End-of-Volume Processing: EOV processing is performed when end-of-data set or end-of-volume conditions occur during I/O operations on sequentially organized data sets. When a routine of a sequential access method encounters a tape or file mark (end-of-data set) or an end-of-volume condition, the routine issues a supervisor call instruction to pass control to the EOV routine.

Catalog management routines maintain the collection of data set indexes (the catalog) that is used by the control program to locate volumes. The catalog management routines also locate the cataloged data sets. The catalog, itself a data set, resides on one or more direct access volumes. It contains indexes that relate data set names to the serial nubers and device types of the volumes containing the data sets. In maintaining the catalog, the catalog management routines create and delete indexes, and add or remove entries.

Prior art catalog management routines include the IBM OS Catalog (see OS/VS2 System Program Library, Data Management, IBM Publication No. GC 26-3830-1) and the IBM VSAM Catalog (see VSAM Primer and Reference, IBM Publication No. G820-5774-0.)

The OS Catalog contains indexes that relate data set names to the serial numbers and device types of the volumes containing the data sets. A volume table of contents (VTOC) resides on each volume, which contains the data set characteristics of the data sets residing on the volume. To open a data set, catalog management routines search through the OS catalog for the name of the data set. The catalog entry for that data set name includes the volume serial number. In order to access a data set on a volume, it is necessary to sequentially search the VTOC for the record containing the data set name, which record will include direct pointers to the start and end of all segments of the user data set. The user data set can then be read from the external device into main or virtual storage, where it will be available to the application program. The serial scan of the VTOC is a seriously time-consuming process, which increases in severity as hardware advances continue to increase the capacity of DASD devices.

One approach to avoiding the VTOC scan required in the operation of the OS catalog is implemented in the prior art VSAM catalog. The VSAM catalog includes, for each data set, not only the volume serial number of the volume containing the data set, but data set extent and other characteristics. Thus, from information in a central VSAM catalog, access is made directly to data sets on different volumes without the necessity of searching the VTOC of those different volumes. This catalog structure, while enabling the opening of a data set without the VTOC scan, introduced severe operational limitations, among which are catalog/data volume synchronization failure and volume ownership problems. The prior art VSAM catalog, with the catalog and the data sets residing on different volumes and with the data set characteristics stored in the catalog, requires that synchronization be maintained between catalog entries and the data sets (for example, the catalog record must contain correct extent information to reflect the location of the associated data set). This prevents a user from being able to restore a data volume or catalog from a back-up copy since to do so would most likely introduce out-of-synch conditions. Hence, more complex time consuming recovery procedures must be adopted by the user when error conditions in the catalog or data sets occur.

In order to detect this synchronization problem, the prior art VSAM catalog requires that only a single VSAM catalog can manage or reference data sets on any given volume, and a single volume cannot incude more than one VSAM catalog. These restrictions impose severe usability problems in many multiprocessing or multiprogramming system installations where a plurality of VSAM catalogs are required by different users. For instance, it would be highly advantageous to permit users to share volumes for both catalogs and data sets.

SUMMARY OF THE INVENTION

It is accordingly an object of this invention to provide a data base catalog for managing data sets. Further, it is an object of this invention to provide a data base catalog which eliminates catalog/data volume out-of-synch as an error condition. It is a further object of the invention to provide a data base catalog which, in multiprogramming and multiprocessing environments enables users to share volumes for both catalogs and data sets. Further, it is an object that the invention be implementable either within an assembly level language instruction set of contemporary computing systems or as new assembly (machine) level instructions. It is also an objective that the invention be invocable by any system running on the computer, such as an operating system (OS) and/or a data base system (DB).

The above objects are satisfied by a method of operating a computing system on a catalog distributed between a base catalog structure (BCS) on one volume, and a plurality of volume data sets (VVDS), with one VVDS residing on each volume containing user data sets. The base catalog structure (BCS) comprises a plurality of sphere records organized in a key sequential data set, such as a VSAM KSDS. Each volume data set (VVDS) includes a plurality of volume records (VVR) organized in a sequential data set, which may be a VSAM key sequential data set (KSDS) or VSAM entry sequential data set (ESDS). For each user data set, a sphere record is provided in the BCS which includes one or more direct pointers to the locations of the corresponding VVR's, and the VVR's include all extent and other information which must be kept in synchronization with the user data set, which user data set resides on the same volume as the VVR.

The method of the invention operates to use and maintain a data base catalog to open a user data set, the data base catalog including a first keyed data set, and on each volume containing user data sets, a second keyed data set, comprising the steps of searching said first keyed data set for a direct pointer to a first volume record in said second keyed data set; comparing the key of the user data set to be opened with the key of said first volume record; and, if the keys match, opening for access the data set addressed by a direct pointer in said first volume record; if the keys do not match, searching said second keyed data set for a second volume record containing the correct key, updating the direct pointer in said first keyed data set to address said second volume record, and opening for access the user data set addressed by a direct pointer in said second volume record.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram representation of a typical computing system, showing loosely coupled CPU's sharing a direct access storage device (DASD).

FIG. 2 is a block diagram representation of a system environment adapted for operation according to the method of the invention.

FIG. 3 is a block diagram representation of certain relationships between catalog records and user data sets selected to illustrate the operation of the invention.

FIGS. 4 and 5 are a flow chart representation of the method steps to define an ICF catalog.

FIGS. 6 and 7 are a flow chart representation of the method steps to define or recatalog an VSAM data set into an ICF catalog.

FIGS. 8 and 9 are a flow chart representation of the method steps to open a VSAM data set. FIG. 10 is a flow chart representation of the method steps to open an ICF catalog.

FIG. 11 is a flow chart representation of the method steps performed under control of the VVDS manager.

FIG. 12 is a flow chart representation of the method steps to write VVR's.

FIG. 13 is a flow chart representation of the method steps to read VVR's.

FIG. 14 is a flow chart representation of the method steps to open BCS.

FIG. 15 is a flow chart representation of the method steps to extend a VSAM data set.

FIG. 16 is a flow chart representation of the method steps to update VVR for extend.

FIGS. 17 and 18 are flow chart representations of the method steps for catalog serialization.

DISCLOSURE OF THE INVENTION

The machine implementable method of the invention may be more fully appreciated by consideration of the following examples as embodied in IBM System/360 machine instructions, said instructions being described in the aforementioned Amdahl patent herewith incorporated by reference, U.S. Pat. No. 3,400,371, and with reference to the drawings.

Referring to FIG. 1, one implementation of the invention operates a computing system, including a central processor 26 and main storage 28, such as an IBM System/370 and a direct access storage device (DASD) 20. A plurality of such DASD devices is shown in FIG. 3, designated as volumes 21, 22, 23, 24 and 25. CPU 29, having a main storage 27, is loosely coupled through DASD 20 to CPU 26. In such a case, DASD 20 would contain a BCS 60, and each CPU maintains catalog control blocks in its main storage 27, 28. Illustrated in FIG. 2 is the architectural environment showing the interrelationship of various components of an operating system and their relationship with a DASD volume 20 containing cataloging data sets BSC 60 and VVDS 70.

Integrated cataloging facility (ICF) 30 includes basic catalog structure (BCS) manager 32, volume data set (VVDS) manager 34, and direct access device space manager (DADSM) 36. ICF 30 responds to access method services 42, VSAM open/close/end-of-volume 44 and other data management subsystems 46, and utilizes the services of VSAM record management 52 and media manager 54 to DEFINE, OPEN, EXTEND, CLOSE, DELETE, and RECATALOG data sets on volumes 20-25, as will more fully be described hereafter.

BCS manager 32 receives control following a supervisor call from the operating system 42, 44, 46, and performs a catalog transaction as specified in the accompanying catalog parameter list (CPL) of Table 1, field vector table (FVT) of Table 2, and field parameter lists (FPB). BCS manager 32 invokes VVDS manager 34 and DADSM 36, as required, to complete the catalog request, as will be more fully described hereafter.

BSC manager 32 initializes and maintains base catalog structure (BCS) 60, using VSAM record management 52. BCS 60 primarily includes volume and association information, and thus can be used to translate a symbolic name into the actual data components reflected by that name, and the volume serial numbers associated with each data component. BCS 60, herein, is a keyed data set, such as a VSAM key sequential data set (KSDS).

VVDS manager 34 initializes and maintains volume data set (VVDS) 70. VVDS 70, herein, is keyed data set, such as a VSAM entry sequential data set (ESDS) or KSDS. It contains the data set characteristics of VSAM data sets residing on the same volume as the VVDS itself, and there exists one VVDS 70 on each volume containing VSAM data. That single VVDS can be shared by plural BCS 60's, as will be more fully described.

                  TABLE 1
    ______________________________________
    Catalog Parameter List (CPL)
    NAME      DESCRIPTION
    ______________________________________
    CTGOPTN1  First option byte:
    CTGBYPSS  Bypass the catalog management security veri-
              fication process.
    CTGMAST   Check the master password.
    CTGCI     Check the control interval password.
    CTGUPD    Check the update password.
    CTGREAD   Check the read password.
    CTGNAME   The CTGENT field contains the address of a
              44-byte DSNAME, or a 6-byte volume serial
              number (padded with binary 0's).
    CTGCNAME  The CTGCAT field contains the address of a
              catalog's 44-byte DSNAME.
              The CTGCAT field contains the address of a
              4-byte field containing a VSAM catalog's
              ACB address.
    CTGGENLD  Generic locate request.
    CTGOPTN2  Second option byte:
    CTGEXT    Extend option (with UPDATE).
    CTGNSVS   Catalog cleanup request (with DELETE).
    CTGERASE  Erase option (with DELETE).
    CTGSMF    Write SMF record option (with LSPACE).
    CTGREL    Reset to empty status.
    CTGGTALL  Search all catalogs (with LISTCAT).
    CTGPURG   Purge option (with DELETE).
    CTGVMNT   The caller is VSAM Open/Close/EOV:
              Volume Mount and Verify routine (IDA0192V).
    CTGRCATN  Return the catalog name (with generic
              LOCATE).
    CTGTTNXT  Get-next option (with LISTCAT).
    $ CTGDELRC
              Delete recovery.
    CTGDISC   Disconnect option (with EXPORT).
    CTGOVRID  Erase override option (with DELETE).
    CTGSCR    Scratch space option (with DELETE).
    $ CTGBOTH Caller can accept the ICF catalog architecture.
    CTGOPTN3  Third option byte:
    CTGFUNC   Specifies the caller-requested function:
    CTGLOC    LOCATE
    CTGLSP    LSPACE
    CTGUPDAT  UPDATE
    CTGCMS    A Catalog Management Services function.
    CTGSUPLT  SUPERLOCATE function.
    CTGCDCL   GDG locate request-the caller supplied the
              base generation level (CTGWAAGB field in
              CTGWA).
    CTGSRH    Search the master catalog only.
              Search the user's catalog first (specified
              by CTGCAT or, if CTGCAT=0, search the
              user's catalogs available to the caller
              via JOBCAT or STEPCAT DD statements,
              then search the master catalog).
    CTGNUM    Search one catalog.
              Search both catalogs.
    CTGAMO    The call is an OS/VS2 catalog management
              request.
              The call is an OS catalog management request;
              the caller supplied a CAMLST parameter list
              that was translated into this CTGPL and
              CTGFLs.
    CTGOPTN4  Fourth option byte:
    CTGLBASE  Locate the base level (with
              SUPERLOCATE-GDG only).
    CTGDOCAT  If the needed catalog is not open, dynamically
              allocate and open it.
              Do not dynamically open the needed catalog.
    CTGNPROF  No RACF profile to be defined or deleted.
    CTGCOIN   Controller intercept requested.
    CTGBYPMT  Bypass security prompting to system operator.
    CTGTIOT   Caller owns SYSTIOT exclusive.
    CTGICFC   The catalog is of the new ICF architecture.
              This bit is set by ICF Catalog Management
              on return if the request caused orienta-
              tion to an ICF Catalog.
    CTGICFOR  Request is for ICF catalog only.
    CTGENT    Address of the catalog record identifier, as
              defined in CTGOPTN1. When the request is
              generic locate, byte 1 of the field pointed
              to by CTGENT is a length byte, followed by
              a 1 to 43 character generic name.
    CTGFVT    Address of the caller's CTGFV.
    CTOGCAT   Address of catalog's DSNAME or of a 4-byte
              field that contains the address of the
              catalog's ACB, as specified in CTGOPTN1.
    CTGCVOL   Address of an OS/VS system-catalog name
              area, if the request is SUPERLOCATE. The
              catalog name area contains the catalog's
              DISNAME and if the catalog is identified
              with an alternate DSNAME, the catalog's
              alias. The OS/VS2 Scheduler uses this
              information to build the catalog's PCCB.
    CTGWKA    Address of the caller's work area.
    CTGDSORG  Data set organization, if the request is
              SUPERLOCATE.
    CTGOPTNS  Catalog Management Services request options:
    CTGDEFIN  DEFINE
    CTGALTER  ALTER
    CTGDELET  DELETE
    CTGLTCAT  LISTCAT
    CTGNVTV   CONVERTV
    CTGF2WKA  User Work Area format 2.
    CTGTYPE   Type of catalog record.
    CTGTALIN  NonVSAM data set
    CTGTGBS   Generation data group (GDG) base.
    CTGTCL    Cluster
    CTGTDATA  Data set
    CTGTFREE  Free (not supported in ICF).
    CTGTAIX   Alternate index.
    CTGTINDX  Index
    CTGTMCAT  Master catalog.
    CTGTPGSP  Page space.
    CTGTPTH   Path.
    CTGTTNE   True name entry (ICF only)
    CTGTUCAT  User catalog.
    CTGTVOL   Volume.
    CTGTANM   Alias name.
    CTGTUFG   Upgrade.
    CTGNOFLD  Number of entries contained in CTGFILED.
    CTGDDNM   Address of the JCL DD statement, if one is
              associated with this request.
    CTGNEWNM  Address of the new DSNAME, if the request is
              ALTER and the object's name is being
              changed.
    If the request is SUPERLOCATE:
    CTGFDBK   Feedback area.
    CTGFBFLG  Flags:
    CTGPAR    Parallel mount.
    CTGKEEP   Forced keep.
    CTGSDGB   GDG Base locate.
    CTGNGDSN  Generation data set name was generated (in
              the form `dsname.gxxxxvyy`)>
    CTGJSCB   Address of the JCSB.
    CTGPSWD   Address of the call-supplied password.
    CTGFIELD  The 4-byte address of each CTGFL, to specify
              each catalog field to be processed. The
              length of the CTGFIELD is the CTGNOFLD
              value times 4.
    ______________________________________

                  TABLE 2
    ______________________________________
    Field Vector Table (FVT)
    FIELD NAME
              DESCRIPTION
    ______________________________________
    CTGFVTYP  RECORD TYPE
    CTGPVALN  NONVSAM
    CTGFVGBS  GENERATION DATA GROUP (GDG)
    CTGFVCL   CLUSTER
    CTGFVDTA  DATA
    CTGFVAIZ  AIX
    CTGFVIDX  INDEX
    CTGFVPTH  PATH
    CTGFVANM  ALIAS
    CTGFVVOL  VOLUME (NOT USED FOR ICF)
    CTGFVPRO  CMS PROCESSING OPTION FLAGS
    CTGFVAVL  ALTER: Add volumes
    CTGFVRVL  ALTER: Remove volumes
    CTGFVNDC  NO DEVICE TYPE CONVERSION
    CTGFVDRC  DEFINE A RECOVERABLE CATALOG
              (NOT ICF)
    CTGFVRON  TURN RACF INDICATOR ON
    CTGFVROF  TURN RACF INDICATOR OFF
              RESERVED
    CTGFVELM  ELEMENT NUMBER OF CMSPCATR
    CTGFVFL2  CMS PROCESSING OPTION FLAGS
    CTGFVDCR  DEFINE with DIRECTED CREATE
    CTGFVNAL  DEFINE with NO-ALLOCATION
    CTGFVICF  DEFINE an ICF catalog
              0 = VSAM catalog
              1 = ICF catalog
    CTGFVRCT  DEFINE RECATALOG (ICF ONLY)
              RESERVED
    CTGFVDCH  ADDRESS OF THE CLUSTER's DATA FVT
    CTGFVICH  ADDRESS OF THE CLUSTER's
              INDEX FVT
    CTGFVVCH  ADDRESS OF THE SPACE FVT
    CTGFVIND  ADDRESS OF THE DDNAME JCL
              STATEMENT
    CTGFVENT  ADDRESS OF THE ENTRY NAME
    CTGFVSTY  ADDRESS OF THE SECURITY INFO FPL
    CTGFVOWN  ADDRESS OF THE OWNER IDENT FPL
    CTGFVEXP  ADDRESS OF EXPIRATION DATE FPL
    CTGFVCRE  ADDRESS OF CREATION DATE FPL
    CTGFVVLT  ADDRESS OF THE VOLUME SERIAL
              NUMBER LIST
    CTGFVRNG  ADDRESS OF THE KEYRANGE FPL
    CTGFVDVT  ADDRESS OF THE DEVICE TYPE FPL
              (nonvsam)
    CTGFVSPC  ADDRESS OF THE SPACE ALLOCATION
              FPL
    CTGFVTTR  ADDRESS OF THE DSCB TTR FPL
              (nonvsam)
    CTGFVAMD  ADDRESS OF THE AMDSB FPL
    CTGFVFSN  ADDRESS OF THE FILE SEQ # FPL
              (nonvsam)
    CTGFVATR  ADDRESS OF THE DATA SET ATTR FPL
    CTGFVBUF  ADDRESS OF THE BUFFERSIZE FPL
    CTGFVLRS  ADDRESS OF THE RECORDSIZE FPL
    CTGFVLMT  ADDRESS OF THE GDG LIMIT FPL
    CTGFVEXT  ADDRESS OF THE EXCEPTION EXIT FPL
    CTGFVGAT  ADDRESS OF THE GDG ATTRIBUTES
              FPL
    CTGFVUPG  ADDRESS OF THE RGATTR RPL
    CTGFVNAM  ADDRESS OF THE TRUE NAME FPL
              (alias)
    CTGFVPWD  ADDRESS OF THE RELATED OBJECTS
              PASSWORD
    CTGFVWKA  ADDRESS OF THE CRA FEEDBACK
              AREA (not ICF)
    CTGFVELT  ADDRESS OF THE EXTENT LIST FOR
              DEFINE
    ______________________________________


                                  TABLE 3
    __________________________________________________________________________
    VVR Header Cell (Example)
     ##STR1##
     ##STR2##
    NAME            DESCRIPTION
    __________________________________________________________________________
    VVRHDLEN        Length of VVR Header (includes itself)
    VVRTYPE         Type code field.
                    The primary VVR has a type code of C`Z`
                    (the data set and AMDSB cells are present).
                    The secondary VVR has a type code of C`Q`.
    VVRFLAG         Flag field.
    VVRCOMTP        Data Component.
                    Index Component.
    VVRSELFD        Self describing VVR for VVDS.
    VVRCATSD        Catalog self describing VVR.
    VVRKRQ          Key Range Qualifier.
    VVRCMPNL        Length of component name (does not include
                    itself).
    VVRCMPNM        Component name.
    VVRKEYL         Length of key (cluster name + pad)
                    (does not include itself).
    VVRKEY          Key (cluster name + pad).
    VVRCATNL        Length of catalog name (does not include
                    itself).
    VVRCATNM        Catalog name.
    VVRAIXNL        Length of AIX name (does not include itself).
    VVRAIXNM        AIX name.
    __________________________________________________________________________


                                  TABLE 4
    __________________________________________________________________________
    VVR Data Set Information Cell
     ##STR3##
     ##STR4##
    NAME               DESCRIPTION
    __________________________________________________________________________
    VVRDSLEN           Length of data set cell (includes itself).
    VVRDSTYP           Type code.
                       Set to X`21`.
    VVRATTR1           Data set attributes.
    VVRA1SPD           Speed
    VVRA1UNQ           Unique
    VVRA1REU           Reusable
    VVRA1ERS           Erase
    VVRA1IUP           Inhibit update
    VVRA1TEX           Temporary export
    VVRA1TKO           Track overflow
    VVRATTR2           Share attributes.
    VVRA2REG           Regional sharing attributes
    VVRA2RL1           READ share or 1 UPDATE/OUTPUT user
    VVRA2RL2           READ share and 1 UPDATE/OUTPUT user
    VVRA2RL3           Fully shared
    VVRA2RL4           Fully shared with VSAM assistance
    VVRA2SYS           System sharing attributes
    VVRA25L1           Fully shared
    VVRA2SL2           Fully shared with VSAM assistance
    VVRA2INT           Internal system data set
    VVRA2NUS           Component is not usable
    VVROPIND           Open indicator.
    VVRBUFSZ           Minimum buffer size.
    VVRPRISP           Primary space allocation.
    VVRSECSP           Secondary space allocation.
    VVRSPCOP           Space option flags.
    VVRSPCTK           Track allocation
    VVRSPCCY           Cylinder allocation
    VVRDSHU            Data set high used RBA.
    VVRDSHA            Data set high allocated RBA.
    VVRLRECL           Average logical record length.
    VVREXCPX           Exception exit.
    VVRDSHK            Data set high key RBA.
    VVRCLSFG           Cluster attribute flag.
    VVRCFSWS           Cluster describes swapspace
    VVRCFPGS           Cluster describes pagespace
    VVRAIXFG           AIX attribute flag.
    VVRAIUPG           Upgrade AIX
    VVRNODSE           Number of data set extents.
    __________________________________________________________________________


                                  TABLE 5
    __________________________________________________________________________
    VVR Volume Information Cell
     ##STR5##
     ##STR6##
    NAME                        DESCRIPTION
    __________________________________________________________________________
    VVRVOLLN                    Length of volume cell (includes itself).
    VVRVOLTP                    Type code X`23`.
    VVRVOLFG                    Volume flags.
    VVRPRIME                    Prime volume.
    VVROVFLW                    Overflow volume.
    VVRNOEXT                    Number of volume data set extents.
    VVRHKRBA                    High key RBA.
    VVRHURBA                    High used RBA.
    VVRHARBA                    High allocated RBA.
    VVRBLKSZ                    Block size.
    VVRBLKTK                    Number of blocks per track.
    VVRTRKAU                    Number of tracks per allocation unit.
    VVRTPEXT                    Extent type flag.
    VVRSSDAT                    Sequence set with data.
    VVRNOPFM                    Extents not performatted.
    VVRBYTTK                    Number of bytes per track.
    VVRBYTTAU                   Number of bytes per allocation unit.
    VVRLOKYL                    Low key length (does not include itself.)
    VVRLOKYV                    Low key on volume.
    VVRHIKYL                    High key length (does not include itself).
    VVRHIKYV                    High key on volume.
    VVRXTNTL                    Length of extent section (does not
                                include itself).
    VVRXTNT                     Extents (one or more 20 byte
    __________________________________________________________________________
                                sets).


              TABLE 6
    ______________________________________
    AMDSB Cell
     ##STR7##
    Statistics section of AMDSB
    ______________________________________
    AMDSTSP        System time stamp.
    AMDNIL         Number of index levels.
    AMDNEXT        Number of extents.
    AMDNLR         Number of logical records.
    AMDDELR        Number of deleted records.
    AMDIREC        Number of inserted records.
    AMDUPR         Number of updated records.
    AMDRETR        Number of retrieved records.
    AMDASPA        Bytes of free space in data set.
    AMDNCIS        Number of CI splits.
    AMDNCAS        Number of CA splits.
    AMDEXCP        Number of EXCP's.
    ______________________________________

                  TABLE 7
    ______________________________________
    Example of VVR Cells for Primary Volume VVR
    ______________________________________
     ##STR8##
    ______________________________________


              TABLE 8
    ______________________________________
    Example of VVR Cells for Non-Primary Volume VVR
    ______________________________________
     ##STR9##
    ______________________________________

                  TABLE 9
    ______________________________________
    Sphere Record
    ______________________________________
     ##STR10##
    CLUSTER COMPONENT
     ##STR11##
    DATA COMPONENT
    ______________________________________

                  TABLE 10
    ______________________________________
    Sphere Record Name Cell
     ##STR12##
    NAME       DESCRIPTION
    ______________________________________
    CLCELLN    Name Cell length includes itself.
    CLTYPE     Type `C` for Cluster.
    CLCOMPLN   Length of the Cluster component.
    CLNOEXT    Number of Extension Records (240 max.).
    CLNMLEN    Length of cluster key (45 bytes).
    CLNAME     Cluster name is part of the key.
    CLNMPAD    Pad character is also part of the key.
    ______________________________________


              TABLE 11
    ______________________________________
    Sphere Record Owner Cell
     ##STR13##
    NAME         DESCRIPTION
    ______________________________________
    OWNCELLN     Ownership Cell length includes itself.
    OWNTYPE      Type X`01` for Ownership Cell.
    OWNID        Owner identification.
    OWNFLAG      Flag Byte.
    OWNRACF      RACF protected (VSAM only).
    OWNKSDS      Index component present.
    OWNREUS      Reusable data set.
    OWNERASE     Erase specified (cluster only).
    OWNNUSED     Currently not used.
    OWNSWAP      Swapspace (Cluster only).
    OWNPAGE      Pagespace (Cluster only).
    OWNCREDT     Creation date.
    OWNEXPDT     Expiration date.
    ______________________________________


                                  TABLE 12
    __________________________________________________________________________
    Sphere Record Security Cell
     ##STR14##
     ##STR15##
    NAME                  DESCRIPTION
    __________________________________________________________________________
    SECELLN               Security Cell length includes itself.
    SECTYPE               Type X`02` for security.
    SECPSWD               Passwords.
    SECMSPSW              Master password.
    SECCIPSW              Control intervat processing password.
    SECUPPSW              Update password.
    SECRDPSW              Read password.
    SECPMTCD              Password prompting code.
    SECATMP               Maximum number of attempts.
    SECVRMOD              User security verification module.
    SECRCDLN              User authorization record length.
    SECRCD                1-256 byte user authorization record.
    __________________________________________________________________________


              TABLE 13
    ______________________________________
    Sphere Record Association Cell
     ##STR16##
     ##STR17##
    NAME        DESCRIPTION
    ______________________________________
    ASCLEN      Association Cell length includes itself.
    ASCTYPE     Type X`03` for association.
    ASCOUNT     Count of Associations.
    ASKEYS      Array of length and key information.
    ASCFLAG     Association key flag - (for relate cell).
    ASCKYLEN    Length of condensed key.
    ASCKEY      1-45 byte condensed key.
    ______________________________________


                                  TABLE 14
    __________________________________________________________________________
    Sphere Record Volume Cell
     ##STR18##
     ##STR19##
    NAME                   DESCRIPTION
    __________________________________________________________________________
    VOLLEN                 Volume Cell length includes itself.
    VOLTYPE                Type X`04` for Volume.
    VOLSERN                Volume serial number.
    VOLDEVIP               Device type.
    VOLFLAG1               Volume flag.
    VOLPRIME               Indicates a prime volume.
    VOLCANDI               Indicates a candidate volume.
    VOLOFLOW               Indicates an overflow volume.
    VOLNVSAM               Indicates a non-VSAM volume.
    VOLKYRNG               Indicates keyrange qualifier present.
    VOLVPCI                Indicates primary VVR.
    VOLSSQWD               Indicates sequence set with data.
    VOLVVRBA               RBA of VVR.
    VOLDSTTR               TTR of Format 1 DSCB for non-VSAM.
    VOLFLSEQ               For non-VSAM a file sequence number.
    VOLKRQL                Keyrange qualifier (VSAM only).
    VOLLKYLN               Length of low key range key.
    VOLLOWKY               1-64 byte low key.
    VOLHKYLN               Length of high key range key.
    VOLHIKY                1-64 byte high key.
    __________________________________________________________________________

                  TABLE 15
    ______________________________________
    ICF Catalog - VSAM Data Set Define Processing
    ______________________________________
    320  Serialize the BCS for write access.
    321  If the data set is to be recataloged, then
    322  Call VVDS manager to read the VVR's for the data set.
    323  Build the data set sphere record, using information
         from the VVR's and the RBA's
         returned by VVDS manager.
    324  Else the data set is being defined for the first time.
    325  Call DADSM to allocate DASD space for the data set.
    326  Build the VVR for the data component of the data set,
         using information provided by the caller.
    327  If the data set is to be key-sequenced, then
    328  Build the VVR for the index component of the data
         set.
    329  If the sequence set is to reside with the data
         component, then
    330  Build the VVR for the sequence set.
    331  Call VVDS manager to write the VVR's for the data set.
    332  Build the data set sphere record, using information
         provided by the caller and the RBA's returned by
         VVDS manager.
    333  Call VSAM record management to
         write the data sphere record.
    334  Release BCS serialization.
    ______________________________________

                  TABLE 16
    ______________________________________
    VVDS Manager Protocol Parameter List (VVDS PARM)
    FIELD NAME
              DESCRIPTION
    ______________________________________
    Header Section
    VDSRQTYP  Request type flags
    VDSFREAD  Type READ
    VDSFISRT  Type INSERT
    VSDFDLET  Type DELETE
    VDSGETUP  Type GET FOR UPDATE
    VDSGENRD  Type GENERIC READ
    VDSDELCT  Type DELETE CATALOG NAME
    VDSENDUP  Type END UPDATE
    VDSBCSOP  Type BCS OPEN
    VDSGENDT  Type GENERIC DELETE
    VDSPUTUP  Type PUT FOR UPDATE
    VDSRETCT  Type RETURN CATALOG NAMES
    VDSHRSVD  Reserved bytes
    VDSUCBAD  Address of UCB (or DEVTYP if VDSDVTYP
              is set)
    VDSVOLSR  Volume serial number
    VDSFLAG1  Volume section flags
    VDSDVTYP  Indicates VDSUCBAD contains the device type
    VVDSLNCHG Indicates Get for Update with length change
    VDSFRBA   Ptr to first RBA entry
    RBA Section
    VDSNXRBA  Address of next RBA entry
    VDSRBAFG  RBA entry flags
    VDSNOSCH  Do not perform automatic search of VVDS if
              incorrect RBA passed
    VDSCATLG  This VVR is for a Catalog
    VDSCLUS   For Generic Read/Delete, treat component
              name field as 45 byte key (cluster name)
    VDSERRFG  Error indicator
    VDSERRBA  The RBA passed was incorrect. A correct
              RBA may be found in its corresponding
              VDSNWRBA field in this parameter list
    VDSERBUF  The buffer provided for this entry is not
              sufficient. The correct length can be
              found in the corresponding VDSNWBFL field
              for this entry
    VDSBUFLN  Length of buffer for this entry (see
              VDSBUFAD)
    VDSBUFAD  Address of variable length buffer for
              this entry. For GENERIC READ, address
              of RBA table.
    VDSRBA    RBA of CI containing desired record.
    VDSNWRBA  Corrected RBA of CI
    VDSCIPTR  Ptr to CI for Get for Update
    VDSNWBFL  Corrected buffer length.
    VDSCMPLN  Length of Component name for this entry
              up to 44 bytes).
    VDSCMPNM  Component name.
    VDSCATLN  Length of Catalog name for this entry.
    VDSCATNM  Catalog name.
    VDSLKRGL  Length of low Key Range for this entry.
    VDSLKYRG  Low Key Range for this entry (variable
              length).
    ______________________________________


              TABLE 17
    ______________________________________
    Volume Control Record (VVCR) Layout
    CATALOG ENTRY
    ______________________________________
     ##STR20##
    ______________________________________

    ______________________________________
    (a) VDSNXRBA     points to next RBA entry or zero if end
                     of chain.
    (b) VVDSBUFLN    set to length of buffer to receive VVR.
    (c) VDSBUFAD     set to address of buffer to receive VVR.
    (d) VDSRBA       set to RBA of CI containing the VVR to
                     be read.
    (e) VDSCMPLN     set to number of characters to use in
                     next field (VDSCMPNM).
    (f) VDSCMPNM     set to component name for desired VVR.
    (g) VDSCATLN     set to zero (catalog name not required
                     on READ).
    (h) VDSLKRGL     set to number of characters in keyrange
                     if a particular keyrange is desired.
    (i) VDSLKYRG     set to keyrange if a particular keyrange
                     is desired.
    (j) VDSSEQS      set to on to read sequence set VVR for
                     specified component.
    ______________________________________

    ______________________________________
    (a) VDSNXRBA     set to zero.
    (b) VDSCATLG     set to one if specified VVR is for a
                     catalog.
    (c) VDSBUFLN     set to length of buffer containing VVR.
    (d) VDSBUFAD     set to address of a buffer containing
                     the VVR to be inserted (including the
                     length of the VVR).
    (e) VDSCATLN     set to number on characters to use in
                     next field (VDSCATNM).
    (f) VDSCATNM     set to catalog name.
    ______________________________________

    ______________________________________
    (a)  VDSNWRBA     set to the RBA of the CI in which the
                      VVR was inserted.
    ______________________________________

    ______________________________________
    (a)  VDSNXRBA     points to next RBA entry or zero if
                      end of chain.
    (b)  VDSCATLG     set to one if specified VVR is for
                      a catalog.
    (c)  VDSRBA       set to RBA of CI containing VVR to
                      be deleted.
    (d)  VDSCMPLN     set to number of characters in next
                      field (if deleting a non-catalog VVR).
    (e)  VDSCMPNM     set to component name (if deleting a
                      non-catalog VVR).
    (f)  VDSCATLN     set to number of characters in next
                      field.
    (g)  VDSCATNM     set to catalog name (if deleting a
                      catalog VVR).
    (h)  VDSLKRGL     set to number of characters in next
                      field.
    (i)  VDSLKYRG     set to low keyrange to delete a
                      specific keyrange VVR (if deleting
                      a non-catalog VVR).
    ______________________________________

    ______________________________________
    (a)  VDSNXRBA      set to zero.
    (b)  VDSCATLG      set to 1 if VVR is for a catalog.
    (c)  VDSBUFLN      set to length of buffer to receive
                       VVR.
    (d)  VDSBUFAD      set to address of buffer to receive
                       VVR.
    (e)  VDSRBA        set to RBA of CI containing VVR
                       to be read.
    (f)  VDSCMPLN      set to number of characters in next
                       field.
    (g)  VDSCMPNM      set to component name.
    (h)  VDSCATLN      set to number of characters in next
                       field.
    (i)  VDSCATNM      set to catalog name.
    (j)  VDSLKRGL      set to number of characters in next
                       field (if keyrange is desired).
    (k)  VDSLKYRG      set to keyrange desired.
    ______________________________________

    ______________________________________
    (a) VDSNXRBA    set to zero.
    (b) VDSCATLS    set to one if VVR is for a catalog.
    (c) VDSBUFLN    set to length of buffer containing VVR.
    (d) VDSBUFAD    set to address of buffer containing VVR.
    ______________________________________

    ______________________________________
    (a)  VDSNXRBA      set to address of next RBA entry or
                       zero if last one.
    (b)  VDSBUFLN      set to length of buffer to receive
                       VVR.
    (c)  VDSBUFAD      set to address of buffer to receive
                       VVR.
    (d)  VDSCMPLN      set to 0.
    (e)  VDSCATLN      set to number of characters in next
                       field (specify only in first RBA
                       entry).
    (f)  VDSCATNM      set to catalog name.
    ______________________________________

    ______________________________________
    (a)  VDSNWRBA      set to the RBA of the CI containing
                       the desired VVR.
    ______________________________________

    ______________________________________
    (a) VDSNXRBA     set to zero.
    (b) VDSCMPLN     set to zero.
    (c) VDSCATLN     set to number of characters in the next
                     field.
    (d) VDSCATNM     set to catalog name to be deleted.
    ______________________________________

    ______________________________________
    (a)   VDSNXRBA     set to zero.
    (b)   VDSBUFLN     set to length of buffer to contain
                       the list of catalog names.
    (c)   VDSBUFAD     set to address of buffer to contain
                       the list of catalog names.
    ______________________________________

    ______________________________________
    (a)  VDSNXRBA      set to zero.
    (b)  VDSBUFLN      set to length of buffer to contain
                       the generic read entries.
    (c)  VDSBUFAD      set to address of buffer to contain
                       the generic read entries.
    (d)  VDSCMPLN      set to number of characters in next
                       field.
    (e)  VDSCMPNM      set to component name.
    (f)  VDSCATLN      set to number of characters in next
                       field.
    (g)  VDSCATNM      set to catalog name.
    ______________________________________

                  TABLE 18
    ______________________________________
    VVDS Manager
    ______________________________________
    340   Request dynamic allocation to ensure that the required
          volume is available.
    341   If the required VVDS is not already open, then
    342   If there is no VVDS on the volume, then
    343   Call DADSM to allocate DASD space for the VVDS.
    344   Build the control blocks required to access the VVDS;
          i.e. Open the VVDS.
    345   If the VVDS has not already been preformatted, then
    346   Call media manager to preformat the VVDS.
    347   Build a VVCR and a VVDS self-describing VVR.
    348   Call media manager to write the VVCR and the
          self-describing VVR.
    349   Serialize VVDS access appropriately for this request.
    350   Invoke the requested VVDS function (read, write, BCS
          open, etc.)
    351   Release VVDS serialization.
    ______________________________________

                  TABLE 19
    ______________________________________
    VVDS Manager - Write Request Processing
    ______________________________________
    370   Allocate the VVDS on the correct volume and serialize
          for write access.
    371   Call media manager to retrieve the VVCR.
    372   Do for each VVR to be written:
    373   Search the space map in the VVCR for a CI with
          sufficient free space for the VVR.
    374   Call media manager to retrieve the selected CI.
    375   Return the RBA of the CI.
    376   Search the VVCR for the catalog name.
    377   If the catalog name is not in the VVCR, then
    378   Insert the catalog name into the VVCR.
    379   If the VVR to be written is for the catalog, then
    380   Update the appropriate RBA in the catalog entry
          in the VVCR.
    381   Copy the VVR into the selected CI.
    382   Update the space map in the VVCR.
    383   Call media manager to write the VVCR and the new VVR.
    384   End.
    385   Release VVDS serialization.
    ______________________________________

                  TABLE 20
    ______________________________________
    VVDS Manager, Read Request Processing
    ______________________________________
    400    Allocate the VVDS on the correct volume and
           serialize (Table 18, line 6376) for read access.
    401    Do for each VVR requested:
    402    If the caller specified an RBA for the VVR, then
    403    If the CI identified by the RBA is not already
           in storage, then
    404    Set up a buffer for the desired CI.
    405    End.
    406    If any CI's have been identified which must be read,
           then,
    407    Call Media Manager to retrieve the CI's.
    408    Do for each VVR requested:
    409    If the caller specified an RBA for the VVR, then
    410    Look for the VVR in the specified CI.
    411    If the VVR is in the CI, then
    412    Indicate VVR found.
    413    Else VVR not found
    414    Indicate the caller's RBA is incorrect.
    415    End.
    416    Do for each CI in the VVDS until all CI's processed
           or all VVR's found.
    417    If the next CI is not already in storage, then
           call Media Manager to retrieve the CI.
    418    Do for each VVR not already found:
    419    Look for the VVR in CI
    420    If VVR is in the CI, then
           Indicate VVR found.
    421    End.
    422    End.
    423    Do for each VVR requested:
    424    If the VVR was found, then
    425    If the caller's RBA was incorrect,
           or if the caller did not specify an RBA, then
    426    Return the correct RBA value.
    427    Copy the VVR into the caller's buffer.
    428    Else the VVR was not found.
    429    Return the VVR-not-found code.
    430    End.
    431    Release VVDS serialization.
    ______________________________________

                                      TABLE 21
    __________________________________________________________________________
    VVDS Manager Process A Read Request
    (Module IGGOCLE0)
    __________________________________________________________________________
    6305
       IGGPVRED:
    6306
       PROC OPTIONS(NOSAVEAREA,NOSAVE):
                                     /* SPECIFY PROCEDURE OPTIONS
                                                          */
    6555
       R1=1;                         /* GET ONE BUFFER    */
    6556
       CALL IGGPVGWA;                /*                   */
    6367
       VWOENQS=ON;                   /* ENQ SHARED        */
    6376
       CALL IGGPVALO:                /* ALLOC VVDS AND ENQ SHARE
                                                          */
    6377
       ZRENTRYP=VDSFRBA;             /* FIRST VVR ENTRY   */
    6378
       RFY
    6379
       VDSENTRY BASED(ZRENTRYP);
    6380
       ZR1=1;                        /* FIRST WA VVR ENTRY
                                                          */
    6381
       DO WHILE ZRENTRYP.noteq.0;    /* FOR ALL ENTRIES   */
    6382
       DO VWCMPLN(ZR1)=VDSCMPLN TO 1 BY-1 WHILE
    6383
       VDSCMPNM(VWCMPLN(ZR1))=";     /* SET COMPRESSED COMPONENT
    6384                               NAME LENGTH IN VVR ENTRY
                                                          */
    6385
       END;
    6386
       IF VDSSEQS=ON THEN            /* IF SEQUENCE SET VVR
                                                          */NTED
    6387
       DO;
    6388
       VWVSINDX(ZR1)=ON;             /* SEARCH FOR INDEX VVR
                                                          */
    6389
       VWVSSEQS(ZR1)=ON;             /* SEARCH FOR SEQUENCE SET
                                                          */R
    6390
       END;
    6391
       VWENTRYP(ZR1)=ZRENTRYP;       /* ADDRESS OF PARM LIST
                                                          */TRY
    6392
       VWVRBA(ZR1)=VDSRBA;           /* RBA PASSED        */
    6393
       IF VWVRBA(ZR1)-=0 THEN        /* IF NOT ZERO       */
    6394
       VWVFCRBA(ZR1)=ON;             /* READ PASSED RBA FIRST
                                                          */
    6395
       ELSE
    6396
       VWVRBA(ZR1)=VVVRFST;          /* START SEARCH AT FIRST
    6397                               USER CI            */
    6398
       IF VDSNOSCH=ON THEN           /* IF NOT TO AUTO SEARCH
                                                          */
    6399
       VWVFNOSC(ZR1)=ON;
    6400
       VWVFRD(ZR1)=ON;               /* VVR SHOULD BE READ
                                                          */
    6401
       VWVSCOMP(ZR1)=ON;             /* SEARCH BY COMPONENT
                                                          */ME
    6402
       IF VDSLKRGL-=0 THEN           /* IF LOW KEYRANGE SPECIFIED
                                                          */
    6403
       VWVSLOKR(ZR1)=ON;             /* SEARCH ON IT      */
    6404
       ZRENTRYP=VDSNXRBA;            /* NEXT VVR ENTRY    */
    6405
       ZR1=ZR1+1;                    /* NEXT WA VVR ENTRY */
    6406
       END;
    6414
       CALL IGGPVRDX;                /* READ THE VVRS     */
    6415
       ZRENTRYP=VDSFRBA;             /* FIRST VVR ENTRY   */
    6416
       ZR2=1;                        /* FIRST WA VVR ENTRY
                                                          */
    6417
       DO WHILE ZRENTRYP-=0;         /* FOR ALL ENTRIES   */
    6418
       IF VWVFINCR(ZR2)=ON THEN      /* IF RBA PASSED INCORRECT
                                                          */
    6419
       DO;
    6420
       VDSERRBA=ON;                  /* SET INCORRECT IN PARM
                                                          */
    6421
       VDSNWRBA=VWVRBA(ZR2);         /* NEW RBA           */
    6427
       END;
    6428
       IF VWVFZIP(ZR2)=OFF THEN      /* IF VVR FOUND      */
    6429
       DO;
    6442
       R0=VDSBUFAD;                  /* POINT TO USERS BUFFER
                                                          */
    6443
       R8=VWVVVRP(ZR2);              /* ADDRESS OF VVR IN CI
                                                          */
    6444
       R9=R8->VVRLEN;                /* SIZE OF VVR       */
    6445
       IF VDSBUFLN>=VWVVVRP(ZR2)->VVRLEN THEN
                                     /* IF COMPLETE VVR
    6446                               WILL FIT IN USERS BUFFER
                                                          */
    6447
       R1=R9;                        /* SIZE OF VVR       */
    6448
       ELSE                          /* USERS BUFFER TOO SMALL
                                                          */
    6449
       DO;
    6450
       R1=VDSBUFLN;                  /* MOVE ALL THAT WILL FIT
                                                          */
    6451
       VDSERBUF=ON;                  /* SET INCORRECT IN PARM
                                                          */
    6452
       VDSNWBFL=VWVVVRP(ZR2)->VVRLEN;
                                     /* CORRECT LEN       */
    6458
       END;
    6459
       MVCL(R0,R8);                  /* MOVE VVR TO USERS BUFFER
                                                          */
    6465
       END;
    6466
       ELSE                          /* VVR NOT FOUND     */
    6467
       DO;
    6481
       CALL IGGPVXIT;                /* EXIT TO CALLER    */
    6482
       END;
    6483
       ZRENTRYP=VDSNXRBA;            /* NEXT VVR ENTRY    */
    6484
       ZR2=ZR2+1;                    /* NEXT WA VVR ENTRY */
    6485
       END;
    6494
       CALL IGGPVXIT;                /* EXIT              */
    6500
       END;                          /* END OF INNER PROCEDURE
                                                          */
    __________________________________________________________________________


                                  TABLE 22
    __________________________________________________________________________
    VVDS Manager Read VVR's
    (Module IGGOCLE2)
    __________________________________________________________________________
    6478
       IGGPVRDX:
    6479
       PROC OPTIONS(NOSAVEAREA,NOSAVE);    /* SPECIFY PROCEDURE
                                                                 */TIONS
    6574
       ZRFRD=OFF;                          /* RESET FLAG         */
    6575
       DO ZR1=1 TO DIM(VWVVRSEC);          /* FOR ALL VVR ENTRIES
                                                                 */
    6576
       VWVRELP(ZR1)=0;                     /* PRESET TO VVR NOT
                                                                 */UND
    6577
       IF VWVFRD(ZR1)=ON&VWVFCRBA(ZR1)=ON THEN
                                           /* IF VVR IS TO BE READ
    6578                                     FROM A SPECIFIC RBA */
    6579
       DO;
    6588
       IF VWVRBA(ZR1)=>VDBHIRBA THEN       /* IF GREATER THAN HI RBA
                                             IN VVDS             */
    6598
       CALL IGGVVER;                       /* CLOSE AND OPEN
                                                                 */DS
    6606
       ZRFRD=ON;                           /* INDICATE A READ
                                                                 */QUIRED
    6616
       R1=1;                               /* ONE BUFFER WANTED  */
    6625
       CALL IGGPVGBU;                      /* GET A BUFFER       */
    6633
       ZR2=R1;                             /* INDEX OF UNUSED
                                                                 */FFER
    6637
       VWVBUFN(ZR1)=ZR2;                   /* BUFFER NUMBER FOR THIS
                                                                 */R
    6638
       VWBFUSE(ZR2)=ON;                    /* MARK BUFFER IN USE */
    6639
       VWBFRD(ZR2)=ON;                     /* SCHEDULE BUFFER FOR
                                                                 */AD
    6640
       VWBRBA(ZR2)=VWVRBA(ZR1);            /* SET RBA IN BUFFER
                                                                 */TRY
    6651
       VQNAME=VQNAMVDS;                    /* MAJOR NAME         */
    6652
       VRNAMRBA=VWBRBA(ZR2);               /* MINOR NAME         */
    6653
       CCAEQDQ=ZZRES;                      /* COPY IN PARM LIST  */
    6656
       R1=ADDR(CCAEQDQ);                   /* ENQ/DEQ PARM LIST
                                                                 */EA
    6657
       GEN REFS (VQNAME,VRNAME,R1,WAREG,VWUCBAD);
    6658
       RESERVE (VQNAME(WAREG),VRNAME(WAREG),E,4,SYSTEMS),
    6659
       UCB=VWUCBAD(WAREG),RELATED=(RBA),MF=(E,(1))
    6660
       @ENDGEN;
    6663
       VWBFENGR(ZR2)=ON;                   /* INDICATE ENQ DONE  */
    6668
       END;
    6669
       END;
    6677
       IF ZRFRD=ON THEN                    /* IF ANY BUFFERS ARE TO BE
                                                                 */AD
    6680
       CALL IGGPVMMB;                      /* CALL MEDIA MANAGER TO
    6681                                     READ VVRS           */
    6696
       DO ZR1=1 TO DIM(VWVVRSEC);          /* FOR ALL VVRS
    6697
       IF VWVFRD(ZR1)=ON&VWVFCRBA(ZR1)=ON THEN
                                           /* IF VVR IS TO BE READ
    6698                                     FROM A SPECIFIC RBA */
    6699
       DO;
    6702
       R1=ZP1;
    6711
       CALL IGGPVCMP;                      /* SEE IF VVR IN CI   */
    6721
       IF VWVRELP(ZR1)-=0 THEN             /* IF VVR FOUND       */
    6722
       DO;
    6723
       VWVFRD(ZR1)=OFF;                    /* RESET READ FLAG    */
    6724
       VWBFVALD(VWVBUFN(ZR1))=ON;          /* VALID CI IN BUFFER */
    6725
       END;
    6726
       ELSE                                /* VVR NOT FOUND      */
    6727
       DO;
    6728
       VWVFINCR(ZR1)=ON;                   /* RBA PASSED IS
                                                                 */CORRECT
    6729
       IF VWVFNDSC(ZR1)=OFF THEN           /* IF SEARCH ALLOWED  */
    6730
       VWVRBA(ZR1)=VVVRFST;                /* RBA TO START SEARCH
                                                                 */
    6731
       ELSE                                /* NO SEARCH ALLOWED  */
    6732
       DO;
    6733
       VWVFZIP(ZR1)=ON;                    /* VVR NOT FOUND      */
    6734
       VWVFRD(ZR1)=OFF;                    /* DONT TRY TO SEARCH */
    6735
       END;
    6736
       END;
    6737
       END;
    6738
       END;
    6783
       ZRRBA=MAXVAL;                       /* HI STARTING RBA FOR
                                                                 */ARCH
    6784
       ZRCOUNT=0;                          /* COUNT OF VVRS      */
    6792
       DO ZR1=1 TO DIM(VWVVRSEC);          /* FOR ALL VVR ENTRIES
                                                                 */
    6793
       IF VWVFRD(ZR1)=ON THEN              /* IF VVR IS TO BE
                                                                 */AD
    6794
       DO;
    6795
       ZRRBA=MIN(ZRRBA,VWVRBA(ZR1));       /* FIND LOWEST START
                                                                 */A
    6796
       ZRCOUNT=ZRCOUNT+1;                  /* COUNT THE REMAINING
                                                                 */RS
    6797
       END;
    6798
       END;
    6807
       DO WHILE ZRCOUNT>0&ZRRBA<VDBHIRBA;  /* DO WHILE THERE ARE VVRS
    6808                                     TO FIND AND END OF VVDS
    6809                                     NOT REACHED         */
    6838
       DO ZR2=1 TO DIM(VWBUFSEC);          /* SEARCH ALL BUFFERS */
    6839
       IF VWBFUSE(ZR2)=ON&VWBRBA(ZR2)=ZRRBA THEN
                                           /* IF CI IS IN THIS
    6840                                     BUFFER              */
    6841
       LEAVE;                              /* FOUND IT           */
    6842
       END;
    6843
       IF ZR2>DIM(VWBURFSEC) THEN          /* IF CI NOT ALREADY IN A
    6844                                     BUFFER              */
    6845
       DO;
    6846
       DO ZR2=1 TO DIM(VWBUFSEC);          /* FOR ALL BUFFERS    */
    6847
       IF VWBFBUFF(ZR2)=ON&VWBFUSE(ZR2)=OFF THEN
                                           /* IF BUFFER
    6848                                     EXISTS AND IS UNUSED
                                                                 */
    6849
       LEAVE;                              /* LEAVE DO LOOP      */
    6850
       END;
    6851
       IF ZR2>DIM(VWBUFSEC) THEN           /* IF NO FREE BUFFERS */
    6852
       DO;
    6853
       RFY
    6854
       R1 RSTD;
    6855
       R1=1;                               /* ONE BUFFER WANTED  */
    6863
       CALL IGGPVGBU;                      /* GET A BUFFER       */
    6871
       ZR2=R1;                             /* INDEX OF UNUSED
                                                                 */FFER
    6874
       END;
    6875
       VWVBUFN(ZR1)=ZR2;                   /* BUFFER NUMBER FOR THIS
                                                                 */R
    6876
       VWBPBA(ZR2)=ZRRBA;                  /* RBA                */
    6877
       VWBFUSE(ZR2)=ON;                    /* MARK BUFFER IN USE */
    6878
       VWBFRD(ZR2)=ON;                     /* SCHEDULE BUFFER FOR
                                                                 */AD
    6879
       IF VWGERBA=ON THEN                  /* IF RBA ENQ REQUIRED
                                                                 */
    6880
       DO;
    6888
       VQNAME=VQNAMVDS;                    /* MAJOR NAME         */
    6889
       VRNAMRBA=VVWBRBA(ZR2);              /* MINOR NAME         */
    6890
       CCAEQDQ=ZZRES;                      /* COPY IN PARM LIST  */
    6891
       VWBFENQR(ZR2)=ON;                   /* INDICATE ENQ DONE  */
    6894
       R1=ADDR(CCAEQDQ);                   /* ENQ-DEQ PARM LIST
                                                                 */EA
    6895
       GEN REFS(VQNAME,VRNAME,R1,WAREG,VWUCBAD);
    6896
       RESERVE (VQNAME(WAREG),VRNAME(WARED),E,4,SYSTEMS),
    6897
       UCB=VWUCBAD(WAREG),RELATED=(RBA),MF=(E,(1))
    6898
       @ENDGEN;
    6901
       END;
    6903
       CALL IGGPVMMB;                      /* CALL MEDIA MANAGER
                                             INTERFACE           */
    6911
       END;
    6919
       DO ZR1=1 TO DIM(VWVVRSEC);          /* FOR ALL VVR ENTRIES
                                                                 */
    6920
       IF VWVFRD(ZR1)=ON&VWVRBA(ZR1)<=ZRRBA THEN
                                           /* IF VVR IS TO BE
    6921                                     SEARCHED AND WE ARE AT
    6922                                     START RBA           */
    6923
       DO;
    6924
       VWVBURN(ZR1)=ZR2;                   /* BUFFER NUMBER      */
    6927
       R1=ZR1;
    6936
       CALL IGGPVCMP;                      /* SEE IF VVR IN CI   */
    6946
       IF VWVRELP(ZR1).noteq.0 THEN        /* IF VVR FOUND       */
    6947
       DO;
    6948
       VWVFRD(ZR1)=OFF;                    /* RESET READ FLAG    */
    6949
       VWVRBA(ZR1)=VWBRBA(ZR2);            /* PUT RBA INTO VVR
                                                                 */TRY
    6950
       VWBFVALD(ZR2)=ON;                   /* VALID CI IN BUFFER */



    6951
       ZRCOUNT=ZRCOUNT-1;                  /* VVRS LEFT TO READ  */
    6952
       END;
    6953
       END;
    6954
       END;
    6962
       IF VWBFVALD(ZR2)=OFF THEN           /* IF NO VVR IN THIS
                                                                 */
    6963
       DO;
    6964
       VWBFUSE(ZR2)=OFF;                   /* BUFFER NOT IN USE  */
    6965
       IF VWBFENQR(ZR2)=ON THEN            /* IF RBA ENQED FOR THIS
                                                                 */FFER
    6966
       DO;
    6974
       VQNAME=VQNAMVDS;                    /* MAJOR NAME         */
    6975
       VRNAMRBA=VWBRBA(ZR2);               /* MINOR NAME         */
    6976
       CCAEQDQ=ZZDEQ;                      /* COPY IN PARM LIST  */
    6977
       VWBFENQR(ZR2)=OFF;                  /* INDICATE DEQ DONE  */
    6980
       R1=ADDR(CCAEQDQ);                   /* ENQ/DEQ PARM LIST
                                                                 */EA
    6981
       GEN REFS(VQNAME,VRNAME,R1,WAREG,VWUCBAD);
    6982
       DEQ (VQNAME(WAREG),VRNAME(WAREG),4,SYSTEMS),
    6983
       UCB=VWUCBAD(WAREG),RELATED=(RBA),MF=(E,(1))
    6984
       @ENDGEN;
    6987
       END;
    6988
       END;
    6989
       ZRRBA=ZRRBA+VCISIZE;                /* NEXT RBA TO CHECK
    6990
       END;
    6998
       IF ZRCOUNT.noteq.0 THEN             /* IF SOME VVRS WEREN'T