Enhanced dump conditioning

This section describes DFSMSdss dump conditioning, introduced with APAR OW45674, and the enhancements to the dump conditioning functions of DFSMSdss since OS/390 R10.

5.2.1 Overview

Prior to the introduction of dump conditioning, when performing a full volume copy of a SMS-managed volume, DFSMSdss required that the COPYVOLID keyword was specified. This resulted in the target volume being varied offline automatically due to a duplicate volser.

Dump conditioning was added as a means to perform a full volume COPY operation which allows both the source and target volumes to remain online, so that full volume DUMP operations can be performed against the source data on an intermediary target location.

The DFSMSdss COPY command DUMPCONDITIONING keyword specifies that you want to create a copy of the source volume for backup purposes, not for the purpose of using the target volume for general applications.

The two DFSMSdss COPY command keywords, DUMPCONDITIONING and COPYVOLID, are mutually exclusive.

5.2.2 DUMPCONDITIONING phase I with OW45674

When DUMPCONDITIONING is specified, the result of a full volume copy is a target volume with a VTOC index and VVDS name identical to the source volume. However the target volume serial remains unchanged. The target volume of a full volume copy operation with DUMPCONDITIONING specified is referred to as a conditioned volume.

The resulting dump data set will have all of the data from the original source volume. The dump data set will, however, have the volser from the conditioned volume (target volume) in the dump tape header.

If a full volume RESTORE is performed from the conditioned volume (target volume) dump data set to an SMS volume, the COPYVOLID keyword must be specified at restore time and the volser must be clipped back to the original source volser.

Physical data set RESTORE from a dump of a conditioned volume is not supported.

5.2.3 DUMPCONDITIONING phase II with OW48234

The enhancements introduced with APAR OW48234, and included in z/OS V1R3 DFSMS, improve the usability of dump conditioning in two areas:

򐂰 Full volume restore enhancement 򐂰 Allow physical data set restore

Full volume restore enhancement

A full volume dump of a conditioned volume will look the same as it did

previously. That is, the resulting dump data set will have all of the data from the original source volume, and the dump data set will have the volser from the conditioned volume (target volume) in the dump tape header.

A full volume copy of a source volume (VOL001 for example) to a target volume (VOL002 for example) specifying the DUMPCONDITIONING keyword, followed by a full volume dump of the target volume (VOL002), results in a dump data set that looks as if it was created by dumping the source volume (VOL001). The dump data set will appear as if it was created from a volume where the VVDS name matched the volume’s volser.

This eliminates the requirement of having run another job to clip the volser of the target volume following a subsequent restore.

If DUMPCONDITIONING is not specified on a full volume copy of a conditioned volume, the copy operation fails with message ADR814E.

Allow physical data set restore

You can now use a full volume dump of a dump conditioned volume as input to a physical data set restore. The restore will work exactly the same as if restoring from any other full volume dump. No indication that you are restoring from conditioned dump is given.

A new message, ADR808I is issued during a full restore of a conditioned volume.

Note: A volume with a volser which does not match the VVDS and VTOC index name may have data accessibility problems. The target volume from a COPY with DUMPCONDITIONING should only be used as a source for full volume DUMP operations.

Chapter 5. DFSMSdss enhancements 117

5.2.4 Restrictions

There are a few restrictions when using DUMPCONDITIONING:

򐂰 If you attempt to perform a full volume copy of a dump conditioned volume, you must specify the DUMPCONDITIONING keyword. If this is not specified, the copy will fail with new message ADR814E.

򐂰 The DUMPCONDITIONING keyword can be used with COPY TRACK operations, but only those that include the VTOC tracks.

򐂰 For a conditioned volume, the VVDS name will not match the volume serial number.

This makes the VVDS invisible to the system. One side effect of this is that a full volume copy or full volume restore operation to a conditioned volume may fail when DFSMSdss attempts to do expiration date checking because the VVDS cannot be located.

To avoid this problem, specify the PURGE keyword during full volume copy and restore operations if the target volume is a previously used conditioned volume, or if the target volume was copied with neither COPYVOLID nor DUMPCONDITIONING specified.

5.2.5 Performance

You can combine physical volume copy using DUMPCONDITIONING with Snapshot or Flashcopy to reduce the amount of time that your data is unavailable when you back it up.

A full volume copy in conjunction with Snapshot or Flashcopy can produce a copy of a volume in seconds. Then, the copy can be dumped to tape while your applications are accessing the data on the original volume.

5.3 Large volume support

z/OS V1R3 DFSMS has introduced large volume support (LVS). Before LVS the largest volume available was a 3390-9, introduced in 1993. This volume had 10,017 cylinders (150,255 tracks). A large volume is any DASD volume with between 10,018 and 32,760 cylinders (491,400 tracks). All DFSMSdss functions now fully support devices defined as having up to 32,760 cylinders.

Coexistence

Full LVS is available for OS/390 Release 10 and higher with APAR OW50405. Toleration support is also provided on releases prior to OS/390 Release 10 by APAR OW49148. This toleration support prevents a large volume from being varied online to an earlier level system.

© Copyright IBM Corp. 2002 119

Chapter 6.

DFSMSrmm enhancements

In this chapter we describe the changes introduced with the DFSMSrmm component. We also describe the new functions introduced since DFSMSrmm Release 10.

These are the changes introduced with DFSMSrmm in z/OS V1R3: 򐂰 Special character support

򐂰 Changed messages for improved diagnostics

򐂰 HELP moved from SYS1.SEDGHLP1 to SYS1.HELP

These new functions have been introduced since DFSMSrmm R10: 򐂰 Software MTL support

򐂰 Multi-Volume alert in RMM Dialog 򐂰 Updated conversion tools

򐂰 VSAM Extended function support for DFSMSrmm CDS 򐂰 RMM Application Programming Interface

򐂰 PARMLIB options SMSACS and PREACS 򐂰 Storage location as Home location 򐂰 Enhanced bin management 򐂰 DSTORE by location 򐂰 Extended extract file 򐂰 Report generator

򐂰 Buffered tape marks support for A60 controller