Purpose

Use the CHANGEVOLUME subcommand to update details for a volume already defined to DFSMSrmm.

Use the MEDINF operand to assign installation-defined media information in DFSMSrmm parmlib member EDGRMMxx to the volume. To reset the volume to use the internal table for IBM® media, use the following command: CV volser MEDINF(IBM).

Provide a new rack number to change the volume's shelf location in the removable media library. The new rack number empty, or available for use. The old rack number is changed to EMPTY status. You also need to replace the external label on the volume to reflect the volume's new shelf location.

Supply a new owner ID to transfer ownership of the volume.

If you change the data set name, DFSMSrmm deletes all information about data sets on this volume and creates a new skeleton entry. Use the CHANGEDATASET subcommand to supply full data set details. See CHANGEDATASET: Changing data set information for more information.

Parameters

ACCESS(NONE|READ|UPDATE)

Specifies the type of access to a volume for those users that are defined in the list of users (with the USERS operand). All users in the list have the same access level. DFSMSrmm uses the access information to build the RACF® TAPEVOL access list.

The value can be one of these:

NONE

Users do not have access to the volume

READ

Users only have read access

UPDATE

Users have write access to the volume

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

ACCOUNT(account_information)

Specifies the accounting information recorded for the volume. Accounting information is one to forty characters enclosed in single quotation marks if it contains any special characters or blanks.

If you do not use this information, DFSMSrmm records it when it records information about the first data set on the volume. At that time, DFSMSrmm gets the accounting information from the account number of the job that created the first data set.

ADDUSERS(user_ID,user_ID,...)

Specifies a list of user IDs and group names of users who can access a volume. Supply a maximum of twelve user IDs separated by blanks or commas. If you used RACF to maintain this access list, the RACF list is updated with your changes.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

ASDATE/DATE(assigned_date)

Specifies the date when the volume was assigned to a user or returned to scratch status.

Supply the year and day in one of two forms. We recommend that you use the yyyy/ddd format rather than the yyddd format for dates.

• yyyy/ddd, where yyyy is the four-digit number for the year. The maximum allowable value for yyyy is 9799. ddd is the three-digit number for the day of the year, such as 2012/001. The slash is required.
• yyddd, where yy is the last two-digit number for the year and ddd is the three-digit number for the day of the year, such as 12001. When you use the yyddd format, DFSMSrmm determines the century by using a date window:
  • DFSMSrmm uses the current century if the difference between the current year and the specified year is not greater than 50.
  • DFSMSrmm uses the previous or next century if the difference between the current year and the specified year is greater than 50.

You can specify the dates 99365 and 99366 only when the MAXRETPD NOLIMIT value is specified in parmlib. This operand is ignored for scratch volumes unless you use either STATUS(MASTER) or STATUS(USER). This operand can be changed if you have authorization to use the FORCE operand.

ASTIME(assigned_time)

Specifies the time a volume was assigned to a user or returned to scratch status. The format for ASTIME is: hhmmss where:

• hh is hours
• mm is minutes
• ss is seconds

For example, nine o'clock in the morning is 090000.

This operand is ignored for scratch volumes unless you use either STATUS(MASTER) or STATUS(USER). This operand can be changed if you have authorization to use the FORCE operand.

ASTIME can be abbreviated as TIME.

AUTOMOVE

Specifies that you want to return the volume to DFSMSrmm inventory management automatic movement control.

BIN(bin_number)

Specifies the shelf location in a storage location. Use this operand to indicate a specific bin number to which the volume is to be moved in a storage location. To assign a specific bin number, the volume's current location a shelf-managed storage location, or you must specify the LOCATION operand to identify a shelf-managed storage location that contains the bin number. If the storage location is installation defined DFSMSrmm uses the LOCDEF parameters to determine the media name to be used.

DFSMSrmm ignores this operand for scratch volumes if you do not specify either STATUS(MASTER) or STATUS(USER).

CAPACITY(nn-mb)

Use this operand to specify the volume capacity in megabytes (MB). DFSMSrmm normally sets the capacity of a volume based on the media type and the recording format, or you can manually set the capacity if the capacity cannot be determined from the media type and recording format. The MEDINF parmlib commands define the capacity of different combinations of media type and recording formats. There are built-in capacity values for IBM media types.

Specify a value between 0 and 4294967295.

CLOSE

Specifies to reset the volume OPEN condition. You can use this operand for any volume. For logical and physical volumes, use this operand to indicate that all data sets on the volume have been closed successfully. For stacked volumes, use this operand to indicate that no more volumes will be exported to it. A stacked volume is normally closed by the completion of export processing. Use this operand when you want to mark a stacked volume as ready to move. DFSMSrmm can move stacked volumes automatically only when they are marked closed.

COMPACTION(*|NONE|IDRC|YES)

Specifies the compaction technique used to record data on tape volumes. Use one of these values:

*

The compaction is not known; or the volume is not a tape volume, and compaction does not apply. This value is the default.

NONE

No compaction was used to record data on the volume.

IDRC

IDRC compaction, which DFSMSrmm displays as a compaction value of YES was used.

YES

The data on the master or user tape volumes that are being added is compacted.

This operand is ignored if you use STATUS(SCRATCH). If you use STATUS(VOLCAT), the value you specify is overridden by information in the TCDB. This operand can be changed if you have authorization to use the FORCE operand.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

CONFIRMMOVE(from_location,to_location, ALL, READYTOSCRATCH,NOTREADYTOSCRATCH)

Specifies that a pending move for a volume has taken place.

To confirm a move for a single volume, use the CHANGEVOLUME subcommand with a volume serial number and the CONFIRMMOVE operand. You do not need to use any other CONFIRMMOVE values.

To confirm volume movement for volumes that are moving from one location to another location, you can specify a from_location, to_location. To confirm volume movement for all locations, specify ALL. To confirm volume movement for volumes based on their status, you can specify READYTOSCRATCH or NOTREADYTOSCRATCH. Use these values for from_location and to_location:

ALL

All locations.

library_name

A shelf location in a system-managed library. Library names one-to-eight alphanumeric characters, $, @, or #, starting with a non-numeric character.

SHELF

A shelf location in a non-system-managed library.

LOCAL

The local storage location.

LOCDEF_location_name

An installation defined storage location. LOCDEF_location_name can be any name up to eight characters long.

DISTANT

The distant storage location.

REMOTE

The remote storage location.

In addition to specifying the from_location and to_location with the CONFIRMMOVE operand, you can use ALL, READYTOSCRATCH, or NOTREADYTOSCRATCH as follows:

ALL

All volume moves. ALL is the default.

READYTOSCRATCH

A subset of all volume moves eligible to become scratch because no other release actions are pending.

NOTREADYTOSCRATCH

These are private volumes or volumes with release actions pending other than return to scratch.

To confirm that you have moved all volumes with the same outstanding move, use CONFIRMMOVE with from and to location values for the move, ALL, and a volume serial number of *.

You can supply location values as follows to identify which move you are confirming:

• CONFIRMMOVE(from_location,to_location) to confirm all moves from one location to another location
• CONFIRMMOVE(from_location,ALL) to confirm all moves from a location to any other locations
• CONFIRMMOVE( ALL,to_location) to confirm all moves to a location from any other location
• CONFIRMMOVE( ALL,ALL) to confirm all outstanding moves regardless of starting location and destination

You can use CONFIRMMOVE in conjunction with the LOCATION operand to have DFSMSrmm immediately record the volume's new location. You can set a new destination for a volume using the LOCATION operand as well.

When you move a volume to an automated tape library, the move is automatically confirmed as you enter the volume. If the system is down or DFSMSrmm is inactive, you can use the CHANGEVOLUME subcommand with CONFIRMMOVE to confirm the move if the volume has already been moved and now resides in that library.

To confirm a volume move between system-managed libraries, you must issue the CHANGEVOLUME subcommand with the CONFIRMMOVE operand from a system on which those libraries are defined. During DFSMSrmm inventory management, DFSMSrmm ignores the confirmation of volume moves between any libraries not defined on the system running inventory management, and defines those moves as pending.

See LISTCONTROL: Displaying parmlib options and control information for information about the LISTCONTROL subcommand, which you can use with the MOVES operand to display information about outstanding moves.

CONFIRMRELEASE/CRLSE(REPLACE,RETURN,ERASE,INIT,NOTIFY,SCRATCH)

Specifies that you have performed the requested actions and that release processing can continue. You only need to confirm those actions which you perform manually. DFSMSrmm confirms those actions it performs automatically.

Use CONFIRMRELEASE with a volume serial to confirm an action for a volume. Use CONFIRMRELEASE with a volume serial of * to confirm that you have performed an action for all volumes awaiting the indicated action.

Use CONFIRMRELEASE with one of these values to confirm actions taken manually for the volume being released. Use commas to separate these values from the first action you specify and from each other.

REPLACE

You have replaced the volume with a new volume

RETURN

You have returned the volume to its owner

ERASE

You have erased the volume

INIT

You have initialized the volume

NOTIFY

You have notified the owner of the volume's release.

SCRATCH

You have performed all cleanup activities necessary before returning the volume to scratch status. The necessary activities depend on your environment and may include updating the TCDB, uncataloging data sets, and deleting RACF profiles. Failing to perform a needed action can lead to inconsistencies.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

CONTAINER(container_name)

Specifies the name of the stacked volume that containins this volume. The container can be a physical stacked volume or any other receptacle where a volume can reside. The value can be any alphanumeric or special characters up to 6 characters in length. To clear the container value, specify CONTAINER(' '). For VTS support, when a volume is removed from a container and you have enabled stacked volume support, DFSMSrmm sets the volume location based on the HOME location of the stacked volume unless you provide a new location using the LOCATION operand.

When a logical volume is added to a stacked volume container using the DFSMSrmm TSO subcommands, DFSMSrmm allows this only if the volume was once exported to that stacked volume and the stacked volume has not been reused. DFSMSrmm tracks unique information to ensure that you can associate a logical volume with the correct stacked volume container. Reusing the stacked volume container or writing to the logical volume prevents DFSMSrmm from associating the logical volume with the stacked volume container.

When stacked volume support is enabled, you can add container information for a volume if the stacked volume you specify is already defined to DFSMSrmm. If the stacked volume is not defined, DFSMSrmm fails the request.

CRDATE(create_date)

Specifies the date when the volume was created. CRDATE can be abbreviated as DATE.

Supply the year and day in one of two forms. We recommend that you use the yyyy/ddd format rather than the yyddd format for dates.

• yyyy/ddd, where yyyy is the four-digit number for the year. The maximum allowable value for yyyy is 9799. ddd is the three-digit number for the day of the year, such as 2012/001. The slash is required. You can specify a date in the range between 0000/000 to 9799/365.
• yyddd, where yy is the last two-digit number for the year and ddd is the three-digit number for the day of the year, such as 12001. When you use the yyddd format, DFSMSrmm determines the century by using a date window:
  • DFSMSrmm uses the current century if the difference between the current year and the specified year is not greater than 50.
  • DFSMSrmm uses the previous or next century if the difference between the current year and the specified year is greater than 50.

You can specify a date in the range between 00000 to 99366.

CRSYSID

Specifies the ID of the system on which the volume was created. Specify a unique system name one-to-eight characters long. CRSYSID can be abbreviated as SYSID.

CRTIME(create_time)

Specifies the time when the volume was created. The CRTIME format is hhmmss where:

• hh is hours
• mm is minutes
• ss is seconds

You can specify a time in the range between 000000 to 235959.

For example, nine o'clock in the morning is 090000.

CRTIME can be abbreviated as TIME.

CURRENTLABELVERSION(1|3|4)

Specifies that the ISO/ANSI label version set for the volume is to be changed.

DELUSERS(USER_ID LIST|*)

Specifies a list of user IDs and group names to be deleted from the list of users who can access a volume. Supply a maximum of twelve user IDs separated by blanks or commas. If you need to delete all user IDs from the list, use an asterisk instead of the list.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

DENSITY(*|1600|3480|6250)

Specifies the recording density of the volume. For a 3420 tape reel, this value can be 1600 or 6250. For a 3480 tape cartridge, use a value of 3480. Supply a value of * if you do not know the density. This operand can be changed if you have authorization to use the FORCE operand.

DESCRIPTION(text)

Specifies the volume description. Descriptive text is one to thirty characters enclosed in single quotation marks if it contains any special characters or blanks.

DSNAME(data_set_name)

Specifies the recorded name of the first data set on the volume. DFSMSrmm deletes all information previously recorded for the data set, and uncatalogs all the data sets on the volume. If the data set name you give matches the data set name on the volume, DFSMSrmm uncatalogs only the subsequent data sets on the volume.

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 masks will not match to data sets with all uppercase characters.

DFSMSrmm does not check quoted data set names for valid characters. Any string of up to 44 characters is accepted, except those that start with a blank or x'00'. Data set names without quotation marks must pass these data set naming rules:

• A data set name can have one or more qualifiers.
• Each qualifier is one to eight characters. The first character alphabetic (A to Z) or national (# @ $). The remaining seven characters can be either alphabetic, numeric (0 - 9), national, or a hyphen (-).
• Qualifiers are separated by a period.
• DFSMSrmm adds your TSO PROFILE PREFIX value as the high-level qualifier.
• The data set name must not include a member name.

This operand can be changed if you have authorization to use the FORCE operand.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

EJECT

Specifies that you want to eject the volume from a system-managed tape library. Specify this operand on a system with access to the library in which the volume resides. DFSMSrmm marks the volume as intransit.

Use EJECT(CONVENIENCE) to eject the volume to the convenience output station. Use EJECT(BULK) to eject the volume to the high capacity output station. If you use EJECT(BULK) for a volume residing in a manual tape library, DFSMSrmm handles this as a normal EJECT. Do not use this operand for a volume that is currently not residing in a system-managed library. CONVENIENCE is the default.

A logical volume cannot always be ejected. DFSMSrmm processes any request to eject a volume but the request can fail if the VTS does not support the request. Requests supported by a VTS include an eject for any volume in insert category or any volume in a category with the fast ready attribute. When you specify EJECT for logical volumes that are scratch volumes, the volume serial number is removed from the inventory in the Library Manager database and from the TCDB.

ERROR(READ(count),WRITE(count))

Use this operand to specify new error count values for read and write errors. These are assumed to be the permanent errors for the volume.

You can specify an absolute value or an incremental value. Incremental values are specified as follows: WRITE(+23). If the value specified causes the count to exceed 65 535, the maximum value of 65 535 is set.

EXPDT(expiration_date)

Specifies the volume expiration date which is the date when the volume should be considered for release. The value cannot exceed the maximum retention period MAXRETPD set by your installation in parmlib member EDGRMMxx.

Supply the year and day in one of two forms. We recommend that you use the yyyy/ddd format rather than the yyddd format for dates.

• yyyy/ddd, where yyyy is the four-digit number for the year. The maximum allowable value for yyyy is 9799. ddd is the three-digit number for the day of the year, such as 2012/001. The slash is required.
• yyddd, where yy is the last two-digit number for the year and ddd is the three-digit number for the day of the year, such as 12001. When you use the yyddd format, DFSMSrmm determines the century by using a date window:
  • DFSMSrmm uses the current century if the difference between the current year and the specified year is not greater than 50.
  • DFSMSrmm uses the previous or next century if the difference between the current year and the specified year is greater than 50.

When you specify the expiration date for a volume that is a part of a multivolume set that is managed by the EXPDT retention method and retained by SET, DFSMSrmm updates the expiration date and time for all the volumes of the multivolume set. When you specify the expiration date for a volume that is managed by the EXPDT retention method and retained by FIRSTFILE, the expiration date will be ignored.

EXPDT is mutually exclusive with RETPD.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

FEATCD(feature_code)

Specifies the software product feature code. A feature code is one-to-four alphanumeric characters.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

FORCE

Specifies information that DFSMSrmm recorded during O/C/EOV processing. You can specify the FORCE operand to

1. Change information that DFSMSrmm records during O/C/EOV processing.
2. Mark a volume as ejected from a system-managed tape library even when the library is not known or offline when you combine FORCE with the EJECT operand.
3. Mark a volume as moved from a system-managed tape library when you combine FORCE with the LOCATION operand. Using the FORCE operand does not prevent updates to the TCDB. If the TCDB is available and can be updated, DFSMSrmm updates it. Using the FORCE operand allows the command to complete successfully even if the TCDB is not available or incorrect.

To use the FORCE operand, you must have CONTROL access to STGADMIN.EDG.MASTER security resource and UPDATE access to STGADMIN.EDG.FORCE security resource.

HOLD | NOHOLD

HOLD

Use the HOLD operand to set the volume HOLD attribute. Setting the HOLD attribute prevents automatic expiration and also prevents use of the RMM DELETEVOLUME subcommand with the RELEASE operand. The HOLD operand is only valid for non-scratch, non-pending release volumes. The RETAINBY(SET) option does not consider the HOLD attribute; each volume is subject to hold independently. HOLD and NOHOLD are mutually exclusive. Authorization requires either CONTROL access to STGADMIN.EDG.MASTER, or UPDATE access to STGADMIN.EDG.CV.HOLD.volser

NOHOLD

Use the NOHOLD operand to reset the volume HOLD attribute. While the HOLD attribute is set it prevents automatic expiration and also prevents use of the RMM DELETEVOLUME subcommand with the RELEASE operand. The NOHOLD operand is only valid for volumes which have the HOLD attribute set. HOLD and NOHOLD are mutually exclusive. Authorization requires either CONTROL access to STGADMIN.EDG.MASTER, or UPDATE access to STGADMIN.EDG.CV.NOHOLD.volser

HOME(library_name|LOCDEF_location_name|SHELF)

Specifies the location where the volume returns when it is no longer retained by a vital record specification. This location can be either an automated or a manual tape library, or a shelf location in a non-system-managed library. This storage location can be defined to DFSMSrmm as a home location. This value does not cause any volume movement.

LOCDEF_location_name indicates that the volume is stored in a storage location. When you store volumes in a storage location as their home location, you enable volumes to return to scratch in the named storage location. Storing volumes in this way allows you to avoid using the location SHELF.

DFSMSrmm processes the HOME operand before the LOCATION operand.

You specify SHELF or a VTS library name for a logical volume.

A home location name is one-to-eight alphanumeric or national characters.

INITIALIZE(Y|N)

Specifies whether the volume should be initialized. Specify INITIALIZE(Y) for all volumes, except stacked volumes, to indicate that the volume requires initializing. You cannot use the volume until you confirm that the volume is initialized. Specify INITIALIZE(N) to indicate that the volume does not need to be initialized.

If you request initialization for a scratch volume, and the initialize action is still pending when you enter the volume into an automated tape library, DFSMSrmm defers initialization to the DFSMSdfp labeling program. If the volume is later ejected without being initialized, DFSMSrmm reinstates the initialization. If you specify INITIALIZE(Y) for volumes residing in an automated tape library, the action is set pending and you must initialize the volume before it can be used.

Specify INITIALIZE(Y) to relabel a duplicate volume so that DFSMSrmm no longer manages it as a duplicate.

DFSMSrmm accepts the abbreviation INIT.

JOBNAME(job_name)

Specifies the name of the job that created the first file on the volume. A job name is one-to-eight characters other than blank, comma, and semicolon. You cannot use a generic job name. Any job name you use specific. This operand can be changed if you have authorization to use the FORCE operand.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

KEYENCODE1

Specifies the encoding mechanism used for KEYLABEL1.

L

Label

H

Public key hash

If KEYLABEL1 is specified and no encoding method is yet defined to DFSMSrmm for this volume, the default value for KEYENCODE1 is L.

KEYENCODE2

Specifies the encoding mechanism used for KEYLABEL2.

L

Label

H

Public key hash

If KEYLABEL2 is specified and no encoding method is yet defined to DFSMSrmm for this volume, the default value for KEYENCODE2 is L.

KEYLABEL1(keylabel1_name)

Specifies the key encryption key label number 1 for a non-scratch volume that is encrypted. A key label is 1-to-64 characters with blanks padding the field on the right. A key label contains alphanumeric, national, or special characters with some additional characters also allowed. Enclose it in single quotation marks if it contains any blanks or special characters.

When a volume is rewritten in a non-encryption format, DFSMSrmm does not clear the encryption key label related fields. Instead, the fields continue to be displayed until the volume is reused from scratch, or a release action causes them to be cleared.

When you specify this optional operand, you can also specify a value for the key encoding mechanism using the KEYENCODE1 operand.

KEYLABEL1 is mutually exclusive with NOKEYLABEL1.

KEYLABEL2(keylabel2_name)

Specifies the key encryption key label number 2 for a non-scratch volume that is encrypted. A key label is 1-to-64 characters with blanks padding the field on the right. A key label contains alphanumeric, national, or special characters with some additional characters also allowed. Enclose it in single quotation marks if it contains any blanks or special characters.

When a volume is rewritten in a non-encryption format, DFSMSrmm does not clear the encryption key label related fields. Instead, the fields continue to be displayed until the volume is reused from scratch, or a release action causes them to be cleared.

When you specify this optional operand, you can also specify a value for the key encoding mechanism using the KEYENCODE2 operand.

KEYLABEL2 is mutually exclusive with NOKEYLABEL2.

LABEL(SL|NL|AL)

Specifies the label type of the volume.

SL

Standard IBM volume label.

NL

No label

AL

ISO/ANSI labels

DFSMSrmm updates the label type when a data set on the volume is opened. This operand can be changed if you have authorization to use the FORCE operand.

LEVEL(version)

Specifies the version of the software product with which the volume is associated. Supply version in the form, VnnRnnMnn, indicating the version, release and modification level. 'nn' is two alphanumeric or national characters. Use the ADDPRODUCT subcommand to add a new version of a software product number already defined to DFSMSrmm.

The default value is V01R01M00, Version 1, Release 1, Modification 0, when NUMBER is specified and the LEVEL has not yet been set.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

LOANLOC(loan_location)

Specifies the location where a volume resides other than the removable media library or a storage location. A loan location is up to eight characters enclosed in single quotation marks if it contains any special characters or blanks. For example, if you removed the volume from the removable media library, you could use your owner ID as the loan location to let others know where the volume is stored. If a volume is stored in a system-managed tape library, DFSMSrmm automatically ejects the volume if you define a loan location. You can clear the loan location by specifying a blank loan location.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

LOCATION(SHELF|HOME|library_name|LOCDEF_location_name|built-in_name)

Specifies a volume's location. When you give a location value, you manually request a volume move. You can specify any location.

If you do not use the HOME operand, DFSMSrmm uses the LOCATION value to set the home location name in the DFSMSrmm control data set if the HOME location is not a storage location.

You can use the LOCATION operand to correct the location information recorded by DFSMSrmm when it does not match the library name in the TCDB. Using the LOCATION operand, you can correct the DFSMSrmm control data set without physically moving the volume.

If the location name you specify does not match the volume's current location, DFSMSrmm attempts to move the volume. If the current location for the volume is a system-managed library, DFSMSrmm attempts to eject the volume. To move the volume, DFSMSrmm sets the required location for the volume. If the volume is a logical volume and stacked volume support is enabled, or a volume that is moving to a shelf-managed storage location, DFSMSrmm inventory management performs any required movement for the volume. In all other cases, DFSMSrmm sets the volume destination and ejects the volume if necessary. Non-scratch logical volumes cannot be ejected.

If you have enabled stacked volume support, DFSMSrmm inventory management uses the required location to determine if the stacked volume container is moved. You can use the required location for logical volumes to build an export list. If stacked volume support is not enabled, you can use the destination to build an export list.

Use one of these to request a volume move:

SHELF

To indicate that the volume be stored in a shelf location in a non-system-managed library.

HOME

To indicate that the volume returns from its current location to the location identified by the HOME operand.

library_name

To indicate that the volume be stored in a specific system-managed library.

This library can be either a manual tape library or an automated tape library. A library name is one-to-eight alphanumeric characters, or $, #, or @, starting with a non-numeric character. If you change this value to the same location that DFSMSrmm has set for the volume, DFSMSrmm checks the TCDB to see if the volume is defined and in that library.

If the library is a manual tape library, DFSMSrmm adds the volume to the TCDB. If the library is an automated tape library and the volume does not currently reside in the automated tape library, DFSMSrmm sets a volume move in progress to get the volume moved to the automated tape library. You can specify a distributed library name only if the library is an IBM Virtualization Engine.

LOCDEF_location_name

To indicate that the volume should be stored in an installation defined storage location.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

built-in_name

To indicate that the volume should be stored in an DFSMSrmm built-in storage location you can specify:

LOCAL

The LOCAL storage location

DISTANT

The DISTANT storage location

REMOTE

The REMOTE storage location

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

Use LOCATION with CONFIRMMOVE to mark the volume move as complete. You can use the LOCATION operand to cancel a pending move by specifying the volume's current location.

MANUALMOVE

Specifies to turn off DFSMSrmm automatic move processing or to cancel a pending move.

MEDIANAME

Specifies the media name for a volume so it matches the media name defined for it in the EDGRMMxx parmlib VLPOOL command.

MEDIATYPE(*| CST | ECCST | EHPCT |HPCT | MEDIA5 | MEDIA6 | MEDIA7 | MEDIA8 | MEDIA9 | MEDIA10 | MEDIA11 | MEDIA12 | MEDIA13 | medinf_mediatype)

Specifies the volume's physical media type. Use one of these:

*

The volume is not a cartridge.

CST

Cartridge System Tape

ECCST

Enhanced Capacity Cartridge System Tape

EHPCT

Extended High Performance Cartridge Tape

HPCT

High Performance Cartridge Tape

MEDIA5/ETC

IBM Enterprise Tape Cartridge

MEDIA6/EWTC

IBM Enterprise WORM Tape Cartridge 3592

MEDIA7/EETC

IBM Enterprise Economy Tape Cartridge 3592

MEDIA8/EEWTC

IBM Enterprise Economy WORM Tape Cartridge 3592

MEDIA9/EXTC

IBM Enterprise Extended Tape Cartridge 3592

MEDIA10/EXWTC

IBM Enterprise Extended WORM Tape Cartridge 3592

MEDIA11/EATC

IBM Enterprise Advanced Tape Cartridge

MEDIA12/EAWTC

IBM Enterprise Advanced WORM Tape Cartridge

MEDIA13/EAETC

IBM Enterprise Advanced Economy Tape Cartridge

medinf_mediatype

Specify a non-IBM media type if your installation definition contains media information for medinf_mediatype that matches the media information assigned to the volume. When you change the media type, DFSMSrmm sets the volume capacity based on the matching media information.

Recommendation: Specify the known media type for system-managed, non-scratch volumes. If you use an incorrect value, the volume can be mounted on a tape drive that can neither read nor write to the volume. If you do not specify a value, DFSMSrmm sets a default value that is valid for the media type you specify.

If you use STATUS(VOLCAT), the value you specify is overridden by information in the TCDB. This operand can be changed if you have authorization to use the FORCE operand.

See Table 2 for information about how DFSMSrmm assigns MEDIATYPE and RECORDINGFORMAT.

There is no default value.

MEDINF(medinf_name)

Specifies the assigned installation-defined media information to the volume. This value is one-to-eight alphanumeric characters and defined once in your installation. You can use the LISTCONTROL subcommand with the MEDINF operand to display the media information. For more information about MEDINF, see z/OS DFSMSrmm Implementation and Customization Guide. When you change the installation-defined media information, DFSMSrmm sets the volume capacity based on the matching media information.

Default: None.

NEWVOLUME(volser)

Specifies the volume serial number of a volume in the DFSMSrmm control data set. Using this operand does not change the tape label on the physical media. DFSMSrmm associates the new volume serial number with the information that is recorded for the old volume. You cannot use this operand to change the volume serial number for a logical or stacked volume. You can use this operand to identify a duplicate volume.

DFSMSrmm assigns a rack number for the volume that matches the new volume serial number and changes the rack number that is associated with the old volume serial number to empty status. To change the rack number that DFSMSrmm assigned to the volume, use the RACK operands or POOL operands to assign a rack number to the volume. To keep the volume in its current shelf location, use the RACK operand with the rack number that was associated with the old volume serial number.

To change a volume serial number that was recorded by DFSMSrmm during O/C/EOV processing, use the FORCE operand to force the change.

NOABEND

Specifies to reset the ABEND flag for a volume.

NOCONFIRMMOVE|NOCMOVE(from_location,to_location,ALL)

Specifies to reverse a previous move confirmation for one or more volumes. You can only reverse a previous move confirmation as long as inventory management has not started.

You must use NOCONFIRMMOVE with a volume serial of * and location values.

Any of these values can be used for from_location and to_location to identify the moves for which you are reversing confirmation:

ALL

All locations

library_name

A shelf location in a system-managed library. Library names one-to-eight alphanumeric characters, or $, #, or @, starting with a non-numeric character.

LOCDEF_location_name

To indicate that the volume should be stored in an installation defined storage location.

SHELF

A shelf location in a non-system-managed library

LOCAL

The LOCAL storage location

DISTANT

The DISTANT storage location

REMOTE

The REMOTE storage location

Supply location values as follows to identify the move confirmation you are reversing:

• NOCONFIRMMOVE(from_location,to_location) to reverse a move confirmation from one specific location to another location
• NOCONFIRMMOVE(from_location,ALL) to reverse a move confirmation from a location to any other locations
• NOCONFIRMMOVE( ALL,to_location) to reverse a move confirmation to a location from any other location.
• NOCONFIRMMOVE(ALL,ALL) to reverse a move confirmation for all volume moves.

You can only use ALL with the NOCONFIRMMOVE operand if you initially supplied it on the move confirmation you are reversing. The from_location and to_location values must also be exactly as specified on the initial confirmation with the CONFIRMMOVE operand. For example, to reverse a previous move confirmation initially supplied as

CHANGEVOLUME * CONFIRMMOVE(ALL,REMOTE)

you can use

CHANGEVOLUME * NOCONFIRMMOVE(ALL,REMOTE)

but you cannot use

CHANGEVOLUME * NOCONFIRMMOVE(ALL,ALL)

NOCONFIRMRELEASE|/NOCRLSE(REPLACE, RETURN, ERASE, INIT, NOTIFY, SCRATCH)

Specifies to reverse a previous release action confirmation.

Use the CHANGEVOLUME subcommand with an asterisk to reverse a release action confirmation for all volumes awaiting the indicated action.

Use NOCONFIRMRELEASE with any of these values to reverse confirmation of release actions performed manually for the volume being released. You can use one or more of these operands separated from the first operand and from each other by commas:

REPLACE

You have not replaced the volumes with new volumes

RETURN

You have not returned the volumes to their owner

ERASE

You have not erased the volumes

INIT

You have not initialized the volumes

NOTIFY

You have not notified the owner that one or more owned volumes is eligible for release

SCRATCH

You have not performed all return to scratch cleanup actions required for the volume

You can only reverse a previous action confirmation as long as inventory management has not started.

NOKEYLABEL1

Specify the NOKEYLABEL1 operand to clear an existing key encryption key label number 1 and encoding mechanism.

NOKEYLABEL1 is mutually exclusive with KEYLABEL1.

NOKEYLABEL2

Specify the NOKEYLABEL2 operand to clear an existing key encryption key label number 2 and encoding mechanism.

NOKEYLABEL2 is mutually exclusive with KEYLABEL2.

NOPREVVOL

Specify to remove a single volume from the end of a multivolume chain.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

NOPREVVOL is mutually exclusive with RETENTIONMETHOD. To remove a volume from a volume set and also change the retention method requires two subcommands.

NORACK

Specifies to remove an assigned rack number from any volume. This allows the volume to be entered as a logical volume.

NOSECLEVEL

Specify to remove the security classification from a volume.

NOSTORAGEGROUP

Specifies to remove the name of the storage group to which the volume belongs. You can use this operand to assign a null storage group for a system-managed volume, or to remove an existing storage group name for a non-system managed volume.

NOWORM

Use this operand to identify that the volume is not a WORM volume. You cannot specify this operand for a volume recorded automatically by DFSMSrmm during open processing.

Use the WORM operand to set the WORM attribute.

NOWORM is the default value.

NUMBER(product_number)

Specifies the number of a software product with which the volume is associated. A software product number is one to eight characters enclosed in single quotation marks if it contains any special characters or blanks.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

OPEN

Specifies to set the volume OPEN condition. You can specify this operand for any type of volume. For a logical or physical volume, you are specifying that a data set is still open or has been left open by an application. Use this operand when you want to mark a stacked volume as not ready to move. A stacked volume is normally opened by the start of export processing and closed by the completion of export processing. DFSMSrmm can move stacked volumes automatically only when they are marked closed.

OPENCOUNT(count | +nn)

Use this operand to specify how many times any data set on the volume has been opened.

You can specify an absolute value or an incremental value. Incremental values are specified as follows: OPENCOUNT(+1). If the value specified causes the count to exceed 65535, the maximum value of 65535 is set.

ORIGINALEXPDT(expiration_date)

Specifies the original JCL expiration date of the volume. It should be the highest original expiration date of all the files on the volume.

Supply the year and day in one of two forms. We recommend that you use the yyyy/ddd format rather than the yyddd format for dates.

• yyyy/ddd, where yyyy is the four-digit number for the year. The maximum allowable value for yyyy is 9799. ddd is the three-digit number for the day of the year, such as 2007/001. The slash is required.
• yyddd, where yy is the last two-digit number for the year and ddd is the three-digit number for the day of the year, such as 12001. When you use the yyddd format, DFSMSrmm determines the century by using a date window:
  • DFSMSrmm uses the current century if the difference between the current year and the specified year is not greater than 50.
  • DFSMSrmm uses the previous or next century if the difference between the current year and the specified year is greater than 50.

There is no default.

ORIGINALEXPDT can be abbreviated as OEXPDT.

OWNER(owner)

Specifies the owner ID of the volume's owner. An owner ID consists of one-to-eight alphanumeric characters, $, #, or @. The first character cannot be a number. We suggest that you use a RACF user ID or RACF group name.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

OWNERACCESS(ALTER|READ|UPDATE)

Specifies the type of access the owner has to the volume.

When the RACF TAPEVOL class is active, and TPRACF(P) or TPRACF(A) is in effect, DFSMSrmm uses the OWNERACCESS information to build the RACF TAPEVOL access list. OWNERACCESS can be used together with OWNER to define the initial RACF TAPEVOL volume profile access, specifying the type of access the volume owner has to a volume.

The OWNERACCESS value can be one of these:

ALTER

The volume owner is allowed to read from the tape volume, to write add and delete data sets to the volume, and to create or destroy tape volume labels through OPEN or end-of-volume operations. For discrete tape volume profiles, the volume owner is allowed to change the profile, including the access list.

ALTER is the default value.

READ

The volume owner has only read access.

UPDATE

The volume owner is allowed to read from the tape volume, and to write additional data sets to the volume.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

For more information, refer to the topic Maintaining the User Access List in z/OS DFSMSrmm Implementation and Customization Guide.

PERCENT(percent)

Use this operand to specify how full the volume is. You can specify a value between 0 and 100.

POOL(pool_ID)

Specifies the pool ID of the pool where the volume is stored in the removable media library. A pool ID is one-to-five alphanumeric, national, or special characters followed by an asterisk. The pool ID defined by your installation. Enclose it in quotation marks if it contains any special characters. If you supply a pool ID, do not give a rack number.

You cannot use this operand for a volume residing in an automated tape library or a manual tape library. POOL cannot be used with RACK.

PREVVOL(previous_volser)

Specifies to add a single volume to the end of a multivolume chain. Supply a fully qualified volume serial number which is one-to-six alphanumeric, national, or special characters. Enclose it in quotation marks if it contains any special characters.

The RETAINBY value for the added volume is taken from the previous volume and the expiration date will be updated, as required.

To remove a single volume from the end of a multivolume chain, specify PREVVOL('') or use the NOPREVVOL operand as shown in the example in Examples of using the CHANGEVOLUME Command.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

PREVVOL is mutually exclusive with RETENTIONMETHOD. To remove a volume from a volume set and also change the retention method requires two subcommands.

PREVVOL is mutually exclusive with RETAINBY.

RACK(rack_number)

Specifies the shelf location of a volume in the removable media library. A full rack number is one-to-six alphanumeric, national, or special characters. Enclose it in quotation marks if it contains any special characters. The rack number that you use available for use. You cannot specify a rack number for a volume residing in a system-managed tape library. The volume serial number and the rack number the same for volumes residing in a system-managed tape library. RACK cannot be used with POOL.

READDATE(last_read_date)

Specifies when the volume was last read.

Supply the year and day in one of two forms.

Recommendation: Use the yyyy/ddd format rather than the yyddd format for dates.

• yyyy/ddd, where yyyy is the four-digit number for the year. The maximum allowable value for yyyy is 9799. ddd is the three-digit number for the day of the year, such as 2012/001. The slash is required.
• yyddd, where yy is the last two-digit number for the year and ddd is the three-digit number for the day of the year, such as 12001. When you use the yyddd format, DFSMSrmm determines the century by using a date window:
  • DFSMSrmm uses the current century if the difference between the current year and the specified year is not greater than 50.
  • DFSMSrmm uses the previous or next century if the difference between the current year and the specified year is greater than 50.

If you want to set a date in the future, the FORCE operand is required.

This operand can be changed if you have authorization to use the FORCE operand.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

RECORDINGFORMAT(*| 18TRACK | 36TRACK | 128TRACK | 256TRACK | 384TRACK | EFMT1 | EFMT2 | EEFMT2 |EFMT3 | EEFMT3 | DEFMT4 | EEFMT4 |medinf_recordingformat)

Specifies the basic recording format for tape volumes.

*

An asterisk indicates that the format is unknown or that the volume is not a tape volume.

18TRACK

Data has been written to the volume in 18 track format. Recording format 18TRACK is valid with MEDIATYPE(CST) and MEDIATYPE(ECCST) only.

36TRACK

Data has been written to the volume in 36 track format. Recording format 36TRACK is valid with MEDIATYPE(CST) and MEDIATYPE(ECCST) only.

128TRACK

Data has been written to the volume in 128 track format. Recording format 128TRACK is valid with MEDIATYPE(EHPCT) and MEDIATYPE(HPCT) only.

256TRACK

Data has been written to the volume in 256 track format. Recording format 256TRACK is valid with MEDIATYPE(EHPCT) and MEDIATYPE(HPCT) only.

384TRACK

Data has been written to the volume in 384-track format. A recording format of 384TRACK is valid with MEDIATYPE(EHPCT) and MEDIATYPE(HPCT) only.

EFMT1

Data has been written to the volume in Enterprise Format 1 recording technology. You can only specify EFMT1 with MEDIATYPE(MEDIA5), MEDIATYPE(MEDIA6), MEDIATYPE(MEDIA7), and MEDIATYPE(MEDIA8).

EFMT2

Data has been written to the volume in Enterprise Format 2 recording technology. You can only specify EFMT2 with MEDIATYPE(MEDIA5), MEDIATYPE(MEDIA6), MEDIATYPE(MEDIA7), MEDIATYPE(MEDIA8), MEDIATYPE(MEDIA9), and MEDIATYPE(MEDIA10).

EEFMT2

Data has been written to the volume in Enterprise Encrypted Format 2 recording technology. You can only specify EEFMT2 with MEDIATYPE(MEDIA5), MEDIATYPE(MEDIA6), MEDIATYPE(MEDIA7), MEDIATYPE(MEDIA8), MEDIATYPE(MEDIA9) and MEDIATYPE(MEDIA10).

EFMT3

Data has been written to the volume in EFMT3 (enterprise format 3) recording format. A recording format of EFMT3 is valid with MEDIATYPE(MEDIA5, MEDIA6, MEDIA7, MEDIA8, MEDIA9, and MEDIA10) only.

EEFMT3

Data has been written to the volume in EEFMT3 (enterprise encrypted format 3) recording format. A recording format of EEFMT3 is valid with MEDIATYPE(MEDIA5, MEDIA6, MEDIA7, MEDIA8, MEDIA9, and MEDIA10) only.

EFMT4

Data has been written to the volume in EFMT4 (enterprise format 4) recording format. A recording format of EFMT4 is valid with MEDIATYPE(MEDIA9, MEDIA10, MEDIA11, MEDIA12, and MEDIA13) only.

EEFMT4

Data has been written to the volume in EEFMT4 (enterprise encrypted format 4) recording format. A recording format of EEFMT4 is valid with MEDIATYPE(MEDIA9, MEDIA10, MEDIA11, MEDIA12, and MEDIA13) only.

medinf_recordingformat

Specify a non-IBM media recording format if your installation definition contains media information for medinf_recordingformat that matches the media information assigned to the volume. When you change the recording format, DFSMSrmm sets the volume capacity based on the matching media information.

You must specify the RECORDINGFORMAT operand when you are changing information about volumes that reside in a manual tape library.

If you use STATUS(VOLCAT), the value you specify is overridden by information in the TCDB. For scratch volumes, DFSMSrmm lets the system set this value when the volume is first used. This operand can be changed if you have authorization to use the FORCE operand.

See Table 2 for information about how DFSMSrmm assigns MEDIATYPE and RECORDINGFORMAT.

There is no default value.

RELEASEACTION(SCRATCH,REPLACE,RETURN,INIT,NOINIT,ERASE, NOERASE,NOTIFY,NONOTIFY)

Specifies the action to be taken when the volume is eligible for release. Use RELEASEACTION with one or more values identifying the release actions to be taken. The first value describes what should happen to the volume at the time it is released. Any following values specify other actions to be performed for the released volume.

You can use one of these mutually exclusive release actions:

SCRATCH

To indicate that the volume should be returned to scratch status. SCRATCH is mutually exclusive with RETURN.

REPLACE

To indicate that the volume should be replaced with a new volume and returned to scratch status.

RETURN

To indicate that the volume should be returned to its owner. RETURN is mutually exclusive with SCRATCH.

You can supply up to three of these values, separated from any previous value and from each other by commas. Use NOINIT, NOERASE, and NONOTIFY to request that DFSMSrmm remove an existing release action of INIT, ERASE, and NOTIFY for the volume.

INIT

To request that DFSMSrmm initialize the volume

NOINIT

To specify that DFSMSrmm not initialize the volume

ERASE

To request that DFSMSrmm erase the volume

NOERASE

To specify that DFSMSrmm not erase the volume

NOTIFY

To request that DFSMSrmm notify the owner that the volume is being released

NONOTIFY

To specify that DFSMSrmm not notify the owner of the volume's release.

You can request multiple actions for a volume. For example, if you want an owner to be automatically notified when a volume is released, and if the volume is to be returned to scratch status and initialized, use this: RELEASEACTION(SCRATCH,INIT,NOTIFY)

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

REPLACE(YES | NO)

Use the REPLACE operand to change the setting of the replace action.

Specify YES to set on the REPLACE action when a volume is pending release with the SCRATCH release action, or if the volume is scratch. If a private volume is not pending release, you cannot change the REPLACE action (see instead the RELEASEACTION operand). DFSMSrmm processing sets off the pending SCRATCH action and sets the REPLACE action. DFSMSrmm processing for a scratch volume sets the volume to a master volume pending release with the REPLACE action pending. Any change from scratch to master for a system-managed volume requires access to the TCDB to update the volume status. Otherwise, the CV subcommand fails.

Specify NO to reset the replace action if it is a pending action. For pending release volumes, the SCRATCH action is set on by DFSMSrmm processing. This is not a confirmation that the REPLACE action is completed. Instead, use the CV subcommand with CRLSE(REPLACE) to confirm the REPLACE action. When you specify REPLACE(NO), you are avoiding the REPLACE action.

REQUIREDLABELVERSION(0|3|4)

Specifies the ISO/ANSI label version in the VOL1 label for the volume when creating or rewriting a tape with AL type labels. Use 0 to clear the required label field.

RETAINBY( FIRSTFILE | SET | VOLUME)

Specifies how DFSMSrmm is to retain a volume or multivolume set managed by the EXPDT retention method. Specify this operand for the first volume in a multivolume sequence. All other volumes added to the set assume the same RETAINBY value.

FIRSTFILE

The expiration date of the first file is used to set the expiration date of a single volume or a multivolume set. All volumes in a multivolume set will have exactly the same expiration date and will be released to scratch in the same run of DFSMSrmm inventory management.

Additional data sets added later to a volume or to a multivolume set can have different expiration dates that are independent of the volume expiration date.

SET

DFSMSrmm uses the highest expiration date of all volumes in the set and each file on a volume set can increment it. All volumes in the set will have exactly the same expiration date and will be released to scratch on the same run of DFSMSrmm inventory management.

VOLUME

The expiration date of the volume is considered for each volume separately and each file on a volume can increment the volume expiration date.

Specify this operand for the first volume in a multivolume sequence. All other volumes added to the set will assume the same RETAINBY value.

Note:

1. The RETAINBY operand cannot be specified:
   • For a volume managed by the VRSEL retention method. Use the RETAINBY operand only for volume sets that use the EXPDT retention method.
   • For a SCRATCH volume.
   • If the PREVVOL operand is specified the volume.
2. When a RETAINBY value is defined for a non-scratch volume, it is not overridden to the default during OPEN output processing, but can be changed using CHANGEVOLUME subcommand.

Authorization requires either CONTROL access to STGADMIN.EDG.MASTER, or UPDATE access to STGADMIN.EDG.CV.RM

Default: If RETAINBY is omitted, the RETENTIONMETHOD(EXPDT(RETAINBY(value)) value specified in parmlib is used.

RETENTIONMETHOD(EXPDT | VRSEL)

Use this operand for any volume to set the retention method for a tape volume set. Specify this operand only for the first volume in a volume set. All other volumes in the set assume the same retention method.

Specify EXPDT to set the retention method for a tape volume set to be based on EXPDT. Data sets and volumes managed by this retention method are never processed by VRSEL inventory management. If the retention method is changed from VRSEL to EXPDT, then the RETAINBY field is set from the CV command, if specified, or from the parmlib. The expiration date of the volume or multivolume set is updated according to the RETAINBY value.

Specify VRSEL to set the retention method for a tape volume set to be VRSEL. This option enables DFSMSrmm inventory management to attempt to match data sets and volumes to vital record specifications, and if a match is found, to determine if the data set or volumes are to retained by VRS. If RETENTIONMETHOD(EXPDT) is changed to RETENTIONMETHOD(VRSEL), then the RETAINBY field for the volume is cleared.

When you change the retention method from VRSEL to EXPDT and the volume was retained as a vital record, the vital record attribute is reset and the retention date set to the current date. If the new retention method is the EXPDT retention method, the data set records will be excluded from VRSEL and the vital record attribute and retention date similarly changed. In addition, DFSMSrmm performs additional processing for all multivolume data sets in the volume set: the maximum expiration date and time for each multivolume data set is determined from the data set records and used to equalize the expiration for the multivolume data set.

RETENTIONMETHOD is mutually exclusive with PREVVOL and NOPREVVOL operands. To remove a volume from a volume set and also change the retention method requires two subcommands.

Authorization requires either CONTROL access to STGADMIN.EDG.MASTER, or UPDATE access to STGADMIN.EDG.CV.RM

RETENTIONMETHOD cannot be specified for a SCRATCH volume, unless the STATUS operand is also specified.

RETENTIONMETHOD can be specified as RM.

RETPD(retention_period)

Specifies the new volume retention period. This is the number of days for which DFSMSrmm retains the volume before considering it for release. The value is a decimal number from 0 to 93000 and is added to today's date to compute the new expiration date. The value cannot exceed the maximum retention period MAXRETPD set by your installation in parmlib member EDGRMMxx.

When you specify the retention period for a volume that is a part of a multivolume set that is managed by the EXPDT retention method and retained by SET, DFSMSrmm updates the expiration date and time for all the volumes of the multivolume set. When you specify the expiration date for a volume that is managed by the EXPDT retention method and is retained by FIRSTFILE, RETPD will be ignored.

RETPD is mutually exclusive with EXPDT.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

SECLEVEL(security_class)

Specifies a volume's security class. The value one to eight characters and one of the security classes defined for your installation.

Use the LISTCONTROL subcommand with the SECCLS operand to display the security classes defined for your location. See LISTCONTROL: Displaying parmlib options and control information for more information.

To reset the security classification for a volume, use the NOSECLEVEL operand.

This operand cannot be specified for a SCRATCH volume, unless you specify the STATUS operand.

SPECIALATTRIBUTES(NONE|RDCOMPAT)

Specifies any special attributes associated with the tape volume.

NONE

The tape volume has no special attributes.

RDCOMPAT

The tape volume was created using one format and can be mounted on a drive that supports reading but not writing of that format.

For example, a volume recorded at 18TRACK can be read by a device that writes at 36TRACK and also has the ability to read 18TRACK tape volumes.

STATUS(MASTER|USER)

Specifies the volume's status. The value can be one of these:

MASTER

To indicate that the volume cannot be overwritten except when the data set names match.

USER

To indicate that the volume can be overwritten by any data set.

STORAGEGROUP|STORGRP(storage_group_name)

Specifies the SMS-defined storage group to which the volume belongs.

A storage group name is one-to-eight alphanumeric characters. A storage group name can be a value that matches to a VLPOOL NAME value but does not need to be defined on a VLPOOL definition.

For volumes in a system-managed library, DFSMSrmm uses the current location or the location specified on the command to validate the specified storage group. For volumes with a system-managed home location defined, DFSMSrmm uses the home location for validation. For other volumes, any value you specify is accepted as long as the value is valid in the current SMS configuration.

A storage group name can be assigned to any volume, even a scratch volume. The storage group name can be used for scratch pooling, except when the volume is in a system-managed automated tape library. For system-managed scratch volumes, the storage group name is not maintained in the TCDB because it is not supported by SMS tape processing.

For system-managed manual tape library volumes, the storage group name is used for scratch pool validation only when you request that a specific storage group name is used for pooling. For all non-system managed scratch pooling validation, the storage group name is significant and is always used to ensure that a volume from the correct pool is mounted.

DFSMSrmm accepts the abbreviation STORGRP.

TYPE(LOGICAL|PHYSICAL|STACKED)

Specify to change the type that is defined to DFSMSrmm.

TYPE(LOGICAL) and TYPE(STACKED) are not allowed if the LOCATION specifies a system-managed library that is not a VTS.

TYPE(LOGICAL) is not allowed if the volume has a rack number that is different from the volume serial number. If the rack number matches the volser, the rack number is removed from the volume and left empty.

TYPE(PHYSICAL) is not allowed if the LOCATION specifies a system-managed library that is a VTS.

TZ({+|-}HH[:MM[:SS]])

Specifies the time zone offset when date and time values are specified. The format is {+|-}HH[:MM[:SS]] where:

• +|- is the offset direction. Specify + to indicate that the offset is East of the zero median (UT). Specify - to indicate that the offset is West of the zero median (UT). The offset direction is required.
• HH is hours
• MM is minutes
• SS is seconds

An optional colon (:) separates hours from optional minutes and optional seconds.

You can specify a time in the range between 00:00:00 to 15:00:00 for HH:MM:SS. MM and SS value range is 00 to 59.

USE(IRMM,MVS,VM)

Specifies the operating systems where the volume can be used. You can select one or more of: IRMM, MVS™, and VM. When you change the systems where a volume can be used, include all the systems you need. To indicate multiple operating systems are valid, enter the values with a comma as a separator.

VENDOR(vendor_name)

Specifies the manufacturer or supplier of the volume. The vendor value is 1 to 8 alphanumeric or special characters that you can set or change at any time. Vendor information enclosed in single quotation marks if it contains any special characters or blanks. DFSMSrmm never changes or uses this value. You can use it for reporting purposes and tracking supplier information for batches of volumes.

There is no default.

volser,*

Specifies the serial number of the volume being changed. A volume serial number is one-to-six alphanumeric, national, or special characters. Enclose it in quotation marks if it contains any special characters. When you are changing information for volumes that reside in a manual tape library or adding system-managed volumes in an automated tape library, you can only specify volume serial numbers that consist of alphanumeric characters.

Specify an asterisk with the CONFIRMRELEASE or CONFIRMMOVE operand to confirm one or more outstanding actions or moves for volumes. Use an asterisk with the NOCONFIRMRELEASE or NOCONFIRMMOVE operand to reverse a confirmation for one or more outstanding actions or moves for volumes.

When you want to change a volser that is defined with volser *, you must specify CHANGEVOLUME '* ' to differentiate the command from the global CONFIRMRELEASE or CONFIRMMOVE command. At least one space (blank) is required after the asterisk that is enclosed in quotation marks.

VOL1(volser)

Specifies a standard label volume serial number. Use this operand to change information that DFSMSrmm recorded. It does not change the tape label information. The variable volser is one-to-six alphanumeric, national, or special characters. You cannot use the VOL1 operand for scratch volumes, logical volumes, stacked volumes, or NL volumes. To clear the VOL1 volser for a volume, specify the volume serial number as the VOL1 volser value.

There is no default.

WMC(count | +nn)

Use this operand to set the write mount count for any volume. The write mount count reflects how many times the volume has been mounted for output and actually written to while mounted.

You can specify an absolute value or an incremental value. Incremental values are specified as follows: WMC(+1). If the value specified causes the count to exceed 65 535, the maximum value of 65 535 is set.

WORLDWIDEID|WWID(world_wide_identifier)

Use this operand to specify the unique world wide identifier set on the volume by the manufacturer. The world wide ID is 12 characters in hexadecimal. You can specify the value as 12 characters, a hex string of 24 characters (x'...'), or as a binary string (b'....'). When entered in hex, you specify 24 characters 0-9, A-F. An example of a world wide identifier is WWID(x’12345678ABCDEF090000FFEE’). When you specify a character string, it can be any string of 12 alphanumeric, national, special, or EBCDIC text characters, enclosed in quotes when special or EBCDIC text characters are specified. DFSMSrmm converts your character string to hex.

The WWID is maintained and displayed as a hexadecimal value and is displayed using 24 characters.

In some publications, the world-wide unique cartridge identifier (WWCID) may also be referred to as the world-wide identifier (WORLDWIDEID or WWID).

There is no default.

Do not use the DFSMSrmm subcommands to set or change the WWID value. Instead, add volumes as you normally would do, and DFSMSrmm records the value when the volume is first used. Subsequent use of the volume causes DFSMSrmm to ensure that the recorded WWID and the WWID obtained from the mounted volume both match. If the values do not match, the volume is rejected. Once the WWID is set by command or recorded by DFSMSrmm when the volume was used while mounted, you cannot change the value in the DFSMSrmm control data set. If the WWID is incorrect in DFSMSrmm, your choice is to either delete and then re-add the volume, or to use RMM REPLACE processing. If DFSMSrmm already has data set details for the volume, keep a record of these so they can be added back by using the DFSMSrmm subcommands.

WORM

Use this operand to identify that the volume is a WORM volume. When you set the WORM attribute and the volume is OPENed for input or output on z/OS®, DFSMSrmm volume validation checks that the write mount count and worldwide unique volume ID values recorded in DFSMSrmm match those obtained from the cartridge and maintained by the drive.

Use the NOWORM operand to reset the WORM attribute.

WRITEDATE(last_write_date)

Specifies when the volume was last written to.

Supply the year and day in one of two forms. We recommend that you use the yyyy/ddd format rather than the yyddd format for dates.

• yyyy/ddd, where yyyy is the four-digit number for the year. The maximum allowable value for yyyy is 9799. ddd is the three-digit number for the day of the year, such as 2012/001. The slash is required.
• yyddd, where yy is the last two-digit number for the year and ddd is the three-digit number for the day of the year, such as 12001. When you use the yyddd format, DFSMSrmm determines the century by using a date window:
  • DFSMSrmm uses the current century if the difference between the current year and the specified year is not greater than 50.
  • DFSMSrmm uses the previous or next century if the difference between the current year and the specified year is greater than 50.

This operand is ignored for scratch volumes unless you use either STATUS(MASTER) or STATUS(USER). This operand can be changed if you have authorization to use the FORCE operand.

If you want to set a date in the future, the FORCE operand is required.

Examples of using the CHANGEVOLUME Command

  RMM CHANGEVOLUME ABC123 PREVVOL('')

  RMM CHANGEVOLUME ABC123 NOPREVVOL

  RMM CHANGEVOLUME ABC001 VOL1(ABC001)

  RMM CHANGEVOLUME 8E1U02 -
       DELUSERS(OWNER12,OWNER25,OWNER44,OWNER45) RETPD(365)

  RMM CHANGEVOLUME * CONFIRMMOVE(REMOTE,SHELF,READYTOSCRATCH)

  RMM CHANGEVOLUME * CONFIRMRELEASE(REPLACE)

  RMM CHANGEVOLUME 8E1U02 RETPD(5)

  RMM CHANGEVOLUME ABC123 LOC(MYATL)

  RMM CHANGEVOLUME ABC123 NUMBER(1234-456) -
       FEATCD(1234) LEVEL(V01R01M00)

  RMM CHANGEVOLUME ABC123 LOCATION(new_destination) CONFIRMMOVE

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.