Converting to DFSMSrmm from TLMS

Chapter 7. Building the CDS 269

7.2.2 EDGCNVT execution parameter

EDGCNVT has a single, optional execution parameter (Table 7-1).

Table 7-1 EDGCNVT execution parameters

7.2.3 EDGCNVT input files

Table 7-2 lists the input files used by EDGCNVT.

Table 7-2 EDGCNVT input files

DEXTRCT

The DEXTRCT file contains the records that are input to EDGCNVT for

conversion to DFSMSrmm record format. You can either use the

DFSMSrmm-supplied sample extract programs to create the input records or

generate them using any tool or method you prefer. This record-based interface

provides you with a clearly defined way to convert volume tape resource data into

a format supported by DFSMSrmm.

There are five different records that describe input to EDGCNVT. Refer to

Appendix B, “Conversion record layouts” on page 613 for details of the records

and their contents:

RECORD DESCRIPTION

TYPE

L Library. An L-Record contains details of a single volume and the first

data set on that volume.

D Data set name. A D-Record contains details of a single data set. One

D-Record is required for each additional data set on a volume. If you

supply a D-Record for a file, all previous files on the same volume

must be specified in D-Records that precede the record.

The L and D-Records have the following sequence requirements:

o Library (L) records for a multivolume set of volumes that must

appear in ascending volume sequence order, interrupted only by:

Data set name (D) records, in ascending file sequence order, after

Parameter Description

nnnn A number of one or more digits that specifies the maximum number of

LOCDEF, VOLRANGE or VOLPRE statements to support. The default value is

500 of each type. Specify a value if you want to increase the limit.

ddname Description

DEXTRCT This file contains the records that are to be converted to DFSMSrmm format.

See section DEXTRCT for information about the input records.

SYSIN The SYSIN control statements describe the processing that you would like

EDGCNVT to perform on the records to be converted. See

270 Converting to DFSMSrmm from TLMS

each L-Record that is created for the volumes from which the data

set originates.

o The count of D-Records that follow after a nonscratch L-record

must be one less than the count of data sets in the LVDSNCNT

field of that L-Record because each L-Record contains first file

data set information.

NOTE: D-Records are not supported for scratch volumes.

E Empty rack and bin. The E-Record contains details of a single, empty

shelf location. It can describe either a rack number or a bin number.

O Owner. The O-Record contains details of a single owner ID. The

owner may own resources that are being converted, but it need not

own any resources.

K VRS. The K-Record contains details of a single policy definition.

The EDGCNVT program input records have the following content requirements:

 The intention is that you will use the DFSMSrmm installation-wide exit,

EDGUX100, to check the JCL-specified EXPDT value. You should also use

that exit to check for a special date of 98000 (other vendor product's “ignore

volume”). When the date is found, the exit requests, through the parameter

list, that DFSMSrmm ignore the volume. The implication for migration, and

therefore for extract processing, is that no volumes with identical VOLSERs

can be input to EDGCNVT.

 Data sets that are retained by special keyword dates in TLMS and are to be

associated with a special expiration date VRS management value must

either:

– Contain the VRS management value in either the D-Record DSVRSVAL

field or the L-Record LDVRSVAL field in the extract program output data

set, or

– Have the VRS management value satisfied through the user exit (see 7.3,

“EDGCEBIN processing” on page 295) by updating the LDVRSVAL field in

an L-Record or the DSVRSVAL in a D-Record.

 The security level of data sets and volumes should be specified through either

the appropriate fields in the L-Records and D-Records or a series of policy

and rules statements in SYSIN. The values for security level should be the

same as those established through PARMLIB.

SYSIN control statements

EDGCNVT accepts a series of statements from SYSIN in the format shown in

Figure 7-1.