Memorex LOCK - VERSION 2-24 Informacje Techniczne Pobierz pdf (Strona 294)

100

101

Direct Access Datasets

7-26 User Reference

Use Pursuant to Company Instructions

Direct Access Datasets

Description When using direct access datasets:

 LUB allocation is inhibited automatically.

 Allocation is on cylinder boundaries and datasets are not

truncated.

 Secondary extents are not supported for controlled datasets.

When using uncontrolled direct access datasets with the configuration

option UNCDSK:

 There is no limit to the number of extents when UNCDSK=NO.

 There is a limit of 5 extents when UNCDSK=YES.

DSN Catalog There are no special EDD requirements.

JCL

Requirements

The VSE job control program requires you to use a DLBL and a complete

EXTENT statement. For BIM-EPIC purposes, however, only the file type

(access method DA) on the DLBL and the extent sequence numbers on

the EXTENT statement must be correct. For both cataloged and Start

Track 1 datasets, the extent sequence numbers must begin with one (1).

VSE also requires that secondary extents reside on separate volumes.

Examples The following example shows the EXTENT statement for a controlled

dataset. BIM-EPIC supplies the volume serial number, starting address,

and number of tracks/blocks from information in the catalog.

// DLBL RESDA,'dataset.name',,DA

// EXTENT SYS020,,1,1

The following example shows the EXTENT statement for a Start Track 1

dataset. BIM-EPIC supplies the actual volume serial number and starting

address.

// DLBL RESDA,'dataset.name',,DA

// EXTENT SYS020,POOL01,1,1,1,15

On BIM-EPIC DD statements, specify DCB=DSORG=DA or

DCB=DSORG=DAU. This example could be used to read or update a

controlled DA dataset.

* //RESDA DD DSN=INVOICE.TICKETS,DISP=(OLD,KEEP),

* // DCB=DSORG=DA

1 2 ... 289 290 291 292 293 294 295 296 297 298 299 ... 567 568

Komentarze do niniejszej Instrukcji

Brak uwag

Memorex LOCK - VERSION 2-24 Informacje Techniczne Strona 294

Komentarze do niniejszej Instrukcji