Utilities › TMSVMEDT Utility—Validate the Vault Pattern Description Data Set › Control Statement Specification › Vault Pattern Control Statement

Vault Pattern Control Statement

The Vault Pattern control statement defines the location (vault name) where data sets are to be moved and the period of time they are to remain in the vault. This control statement is required and must begin in position 1. The vault name (vltx) must be either (blank)LIB LIBR, or previously defined by the Vault Name control statement. When you use (blank)LIB for the vault name, the blank character is not required (V=LIB).

If multiple Data Set Name control statements precede the Vault Pattern control statement, the movement described by the Vault Pattern control statement is applied to each of the previous Data Set Name control statements. A maximum of 28 Vault Pattern control statements may be specified for a given group of Data Set Name control statements.

In addition to the vault name (vltx), one or more of the keywords which follow must be specified. When two or more keywords are specified, they are treated as OR conditions. Two consecutive Vault Pattern control statements for the same vault are treated as AND conditions. See Vault Pattern Conditional Processing for examples. The format for the Vault Pattern control statement is:

1 3    8

V=vltx,keyword=value[,keyword=value,...,keyword=value]

Keyword Definitions

C=n

Vault for n cycles. Up to 255 cycles can be specified. A cycle is defined to VMS through a CA 1 system option. See Defining a Cycle to Vault Management.

CR=n

Vault for n days from creation. Do not use with the E= keyword. Up to 9999 days can be specified.

VR=n

Vault for n days from OUTDATE. Do not use with the E= keyword. Up to 9999 days can be specified.

EXP

Vault until the data set is expired.

E={preferred date|Julian date|PERM}

Vault until specified date. The value of E= may be an actual date in your preferred date format, a Julian date (yyyy/ddd), or PERM for permanent vaulting. Whatever date format you choose, the date must be a date in the future.

LU=n

Vault until n days after data set was last used. Up to 9999 days can be specified.

If either VOL= or CDSN= control statements were used in the preceding group of control statements, those volumes are moved only to the first specified location. They will remain at that location until the VOL= or CDSN= control statement has been removed, regardless of the keyword(s) that were included on the Vault Pattern control statement.

Important!

If you specify a preferred date for E=, any subsequent revision to the DATEFMT option in hlq.CTAPOPTN or to the DATEFMT=(fmt) parameter in the TMSVMEDT program JCL may result in an abend if the date format is changed. Therefore, use extreme caution when revising either of these patterns.

You are strongly advised to change the date pattern of preferred date so that it reflects the newly revised date pattern specified in hlq.CTAPOPTN or in the TMSVMEDT program JCL. This restriction applies only to preferred date; if you are using a date in Julian format or the CA 1 keyword PERM, this warning can be ignored.

Examples:

V=VLT1,C=5

Retain a tape in VLT1 for five cycles or creations of the data set.

V=VLT2,CR=3

Retain a tape in VLT2 for three days from creation date (CDATE).

V=VLT3,VR=8

Retain a tape in VLT3 for eight days from the vault date (OUTDATE).

V=VLT4,E=2015/365

Retain a tape in VLT4 until the Julian date 2015/365.

V=VLT5,EXP

Retain a tape in VLT5 until the volume expires (EXPDT less than or equal to the VMS system run date).

V=VLT6,LU=5

Retain a tape in VLT6 for 5 days after its last use.