Mainframe Enablers TimeFinder SnapVX and zDP 8.5 Product Guide

Specifies various snapshot settings.

Syntax

CoNFiG

(

TaRGet

({

VOLume(volser)|

UNIT({cuu|lowcuu-highcuu|lowcuu:highcuu|cuu(count)})|

SYMDV#({symdv#|lowsymdv#-highsymdv#|lowsymdv#:highsymdv#|symdv#(count)})|

SCFGroup(gnsgrp)

})

[optional_parameters]

)

Where optional_parameters are:

[CONTROLLER({[xxxxxxx-]xxxxx|name})]

[EXPIration(days) NAME(snapshot_name)]

[GROUP(grpname[,grpname,..])]

[LOCAL({

UNIT(cuu) [CONTROLLER({[xxxxxxx-]xxxxx|name})]|

VOLUME(volser) [CONTROLLER({[xxxxxxx-]xxxxx|name)}]|

DDNAME(ddname) [CONTROLLER({[xxxxxxx-]xxxxx|name)}]|

CONTROLLER({[xxxxxxx-]xxxxx|name})

})]

[MODE({COPY|NOCOPY|NOCOPYRD})]

[NAME(snapshot_name)]

[READY(Yes|No)]

[RELEASE(Yes|No)

[REMOTE (RAGROUP(nn.nn.nn.nn)

{UNIT(cuu) [CONTROLLER({[xxxxxxx-]xxxxx|name})]|

VOLUME (volser) [CONTROLLER({[xxxxxxx-]xxxxx|name})]| DDNAME(ddname) [CONTROLLER({[xxxxxxx-]xxxxx|name})]})]

[SECure(Yes) NAME(snapshot_name)]

Command-specific parameters

CONTROLLER({[xxxxxxx-]xxxxx|name})

You can use the CONTROLLER subparameter on LOCAL or REMOTE as a separate parameter. It allows you to verify that the storage system found using the gatekeeper (and RAGROUP if REMOTE) (where the request is to take place) is the storage system you want. When you use the separate CONTROLLER parameter, you do not include the LOCAL and REMOTE parameters.

NOTE:The CONTROLLER parameter is only needed and can only be used if you use the SYMDV# parameter.

You may specify a five-digit (xxxxx) or a 12-digit (xxxxxxx-xxxxx) serial number. Or, you may specify a logical storage system name if you previously defined that name to ResourcePak Base.

If the logical storage system name is simple in format (single-word string, all upper case and no more than 64 characters), you can specify the storage system name without quotation marks. If the logical storage system name is mixed case or contains spaces, you must enclose it in single quotation marks.

EXPIration(days)

See EXPIration.

The EXPIRATION parameter on the CONFIG command cannot be used to extend the time to live of a snapshot. For example, if the time to live is 5 hours and you issue CONFIG EXPIRATION(1), the time to live is set to one day, but not one day and five hours.

The EXPIRATION parameter on the CONFIG command cannot be used to decrease the expiration time for a secure snapshot. For example, if a secure snapshot is to expire in two days, a CONFIG EXPIRATION(1) command results in an error message.

The EXPIRATION parameter on the CONFIG command requires a NAME(snapshot_name) parameter, which can be set on the CONFIG or GLOBAL command.

MODE({COPY|NOCOPY|NOCOPYRD})

See MODE.

Changing the copy mode on linked zDP snapshots with the CONFIG command is not supported. To change the copy mode on a linked zDP snapshot, unlink it and link again, specifying the required copy mode.

NAME(snapshot_name)

See NAME. The NAME parameter is ignored when specified with the MODE(COPY) parameter.

SECure(Yes)

See SECure.

NOTE:Secure snapshots may only be terminated after they expire or by customer-authorized Dell Customer Support. For more information, see Knowledge Base article 498316.

When running a CONFIG command, the GLOBAL SECURE setting and the &SECURE site option are ignored.

The SECURE parameter on the CONFIG command requires a NAME(snapshot_name) parameter, which can be set on the CONFIG or GLOBAL command.