Mainframe Enablers TimeFinder SnapVX and zDP 8.5 Product Guide

SIBBATCH

If you plan to run with full IBM SNAPSHOT compatibility, place the Dell-supplied SIBBATCH in the search list ahead of the IBM-supplied SIBBATCH.

SIBBATCH uses the same DD statements as SNAPSHOT. If you want any TimeFinder functions, code the statement exactly as it is coded in TimeFinder. For instance, a GLOBAL statement could be added to the input stream.

SRS

If the installation uses the Space Management Software from DTS Software, you should exclude TimeFinder from SRS recovery by coding the following rule:

DEFRULE NOEMC
IF PGM=EMCSNAP
THEN EXIT

FlashCopy

IBM 2105 and 2107 controllers are recognized, and IBM FlashCopy is automatically invoked as a data mover, if appropriate. TimeFinder recognizes FlashCopy V2 support and uses FlashCopy V2 to copy dataset extents.

TimeFinder recognizes whether a storage system is FlashCopy capable. It also recognizes when a FlashCopy session is active at the logical volume level.

FlashCopy and Snap sessions can co-exist and the value in the site options table for &EMCDSSU_FLASH_SNAP is always used. If the site options table has Snap as the preferred copy method (&EMCDSSU_FLASH_SNAP=SNAP) and a FlashCopy session existed on the device, TimeFinder would use Snap.

A FlashCopy target cannot be used as a SnapVX source. However, a SnapVX gatekeeper device can have a Remote Pair FlashCopy session.

Transparent Cloud Tiering (TCT)

Source and target devices of Transparent Cloud Tiering (TCT) operations cannot be involved in TimeFinder sessions. Devices that are in-use in active TimeFinder sessions cannot be involved in TCT operations.

Virtual volumes (vVol)

Virtual volume (vVol) devices cannot be used as a SnapVX snapshot or linked target.