LISTVRS: Displaying information about a vital record specification

Purpose

Before you begin: To use the RMM LISTVRS subcommand, you need READ access to the STGADMIN.EDG.VRS resource profile.

Use the LISTVRS subcommand to display details about a single vital record specification. Specify a data set name when requesting information about a data set vital record specification. You can optionally use the JOBNAME operand when requesting information about a data set vital record specification. Specify a volume serial number when requesting information about a volume vital record specification. Specify a vital record specification name when requesting information about a vital record specification used to link to other vital record specifications.

The values in the Type field in the LISTVRS output are DSN, GDG, or PGDG. These values indicate if the vital record specification was specified with a NOGDG, GDG, or a pseudo-GDG data set name.

Use the SEARCHVRS subcommand to create lists of vital record specifications. See SEARCHVRS: Creating a list of vital record specifications for more information.

Format


>>-+-LISTVRS-+-------------------------------------------------->
   '-LS------'   

>--+-DSNAME(data_set_name)-+-----------------------+-+---------><
   |                       '-JOBNAME(jobname_mask)-' |   
   +-NAME(VRS_name)----------------------------------+   
   '-VOLUME(full_or_generic_volume_serial)-----------'

Parameters

DSNAME(data_set_name)

Specifies the name of the data set for which the vital record specification is defined.

The data set name mask is 1 to 44 characters, enclosed in quotes if any special characters are included. If the data set name mask is not enclosed in quotes, PROFILE PREFIX is applied. This operand is required and must immediately follow the CHANGEVRS subcommand.

DSNAME is mutually exclusive with the NAME and VOLUME operands.

Note: DFSMSrmm does not fold data set names to uppercase letters when you specify quoted data set names. When you specify data set names or data set name masks, be sure to specify the correct case for each character. If you create VRS data set name masks with lowercase or mixed case letters, these will not match to data sets with all uppercase characters.

You can also specify an SMS management class name, a vital record specification management value, or the reserved data set name masks, ABEND, DELETED, or OPEN. The name can be eight alphanumeric characters, beginning with an alphabetic character, and must follow standard z/OS® data set naming conventions. This name must be a single qualifier, and is already assigned by your installation. For example, you can specify DSNAME('M99000').

DSNAME is mutually exclusive with the NAME and VOLUME operands.

NAME(VRS_name)

Specifies the eight-character name of a vital record specification. NAME is mutually exclusive with the DSNAME and VOLUME operands.

JOBNAME(jobname_mask)

Specifies the job name for the vital record specification. A job name is one-to-eight alphanumeric characters or $, #, or @. The job name must start with an alphabetic character, $, #, or @. You can specify a specific jobname or a jobname mask. Use % to match any one character and * to match any character string in the mask. The job name mask you specify must exactly match the job name mask in the vital record specification. This operand is optional. Specify JOBNAME to display a vital record specification defined with a jobname mask.

VOLUME(full_or_generic_volume serial)

Specifies the serial number of the volume for which the VRS is defined. A full volume serial number is one-to-six alphanumeric, national, or special characters. A generic volume serial number is one-to-five alphanumeric, national, or special characters followed by an asterisk. Enclose a full or generic volume serial number in single quotation marks if it contains any special characters. You can specify a generic volume serial number if it exactly matches an existing vital record specification.

VOLUME cannot be used with the DSNAME and NAME operands.

Task: List a vital record specification based on job name by coding both DSNAME and JOBNAME where both must match the corresponding values in the vital record specification. For example, if you want to list the two vital record specifications shown in Figure 1 :

Figure 1. Listing vital record specification information examples

RMM ADDVRS DSNAME('A.B') WHILECATALOG
RMM ADDVRS DSNAME('A.B') JOBNAME(BENSJOY) WHILECATALOG

Command:

  RMM LISTVRS DSNAME('A.B')

DFSMSrmm does not list the second vital record specification. You must also specify the JOBNAME operand on the LISTVRS subcommand.

Task: Request information about the data set vital record specification defined for the data set named DATA.SET.ONE.

Command:

  RMM LISTVRS DSNAME('DATA.SET.ONE')

or, if DATA is your own TSO PROFILE PREFIX, you can enter:

  RMM LISTVRS DSNAME(SET.ONE)

Output: DFSMSrmm displays information such as that shown in Figure 2:

Figure 2. Sample LISTVRS output

 Data set mask = DATA.SET.ONE                                 Type = DSNAME
 Job name mask = *                            Retain until expired = NO
 Count        = 99999 CYCLES                Retain while cataloged = NO
 Delay        = 0     Days in the HOME location
 Store number = 99999 CYCLES  in the HOME     location
 Priority     = 500
                                                   Release Options:
                                                Expiry date ignore = NO
                                                 Scratch immediate = YES
 Next VRS in chain    = AADN1     using ANDVRS

 VRS Owner    = OWN000
 Description  = User data sets
 Last Reference: Date  = 2010/111   Time  = 12:00:00
 Vital Record Specification to be deleted on 31/12/1999

 Last Change information:                                           
 Date             = 01/05/2011  Time = 08:50:39  System  = EZU0000  
 User change date = 01/05/2011  Time = 08:31:00  User ID = D008210

Return codes

See DFSMSrmm return codes and reason codes for DFSMSrmm reason codes.

0: Subcommand completed normally.
4: Warning. Subcommand completed but some operands could have been ignored or modified. DFSMSrmm sets a reason code.
8: User not authorized.
12: Subcommand ended with an error. DFSMSrmm sets a reason code.
16: Error. The DFSMSrmm subsystem is not active.
20: Error. The data is incomplete or incorrect and the TSO user has set NOPROMPT.
24: The TSO subcommand is not APF authorized.
28: The user pressed the attention key.