11.01.2013 Views

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2.17 VTOC and DSCBs<br />

VTOC<br />

DSCBs<br />

Figure 2-17 Data set control block (DSCB)<br />

Data set control block (DSCB)<br />

The VTOC is composed <strong>of</strong> 140-byte data set control blocks (DSCBs) that point to data sets<br />

currently residing on the volume, or to contiguous, unassigned (free) tracks on the volume<br />

(depending on the DSCB type).<br />

DSCBs also describe the VTOC itself. CVAF routines automatically construct a DSCB when<br />

space is requested for a data set on the volume. Each data set on a DASD volume has one or<br />

more DSCBs (depending on its number <strong>of</strong> extents) describing space allocation and other<br />

control information such as operating system data, device-dependent information, and data<br />

set characteristics. There are seven kinds <strong>of</strong> DSCBs, each with a different purpose and a<br />

different format number.<br />

The first record in every VTOC is the VTOC DSCB (format-4). The record describes the<br />

device, the volume the data set resides on, the volume attributes, and the size and contents <strong>of</strong><br />

the VTOC data set itself. The next DSCB in the VTOC data set is a free-space DSCB<br />

(format-5) that describes the unassigned (free) space in the full volume. The function <strong>of</strong><br />

various DSCBs depends on whether an optional Index VTOC is allocated in the volume. Index<br />

VTOC is a sort <strong>of</strong> B-tree, to make the search in VTOC faster.<br />

Table 2-1 on page 47 describes the various types <strong>of</strong> DSCBs, taking into consideration<br />

whether the Index VTOC is in place or not.<br />

In z/<strong>OS</strong> V1R7 there is a new address space (DEVMAN) containing trace information about<br />

CVAF events.<br />

46 <strong>ABCs</strong> <strong>of</strong> z/<strong>OS</strong> <strong>System</strong> <strong>Programming</strong> <strong>Volume</strong> 3<br />

F4 F0 F1 F1 F1<br />

F4<br />

DATA SET C<br />

DATA SET A<br />

DATA SET B

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!