The PRIME parameter primes objects that were exported in an empty, nonprimed state. The NOPRIME parameter prevents objects that have already been primed from being primed.
Note: At this level, PRIME|NOPRIME is a global parameter; it applies for the entire RESTORE. Specify PRIME|NOPRIME at the local level to limit its effect to a specific group of clusters. For more information about PRIME|NOPRIME as a local parameter, see Cluster Names: Optional Parameters.
Syntax
This parameter has no operands.
PRIME|NOPRIME
►►─┬───────────┬──────────────────────────────────────────────────────────────►◄ ├─ PRIME ───┤ └─ NOPRIME ─┘
Example
The following example shows how the PRIME and NOPRIME parameters can be used in the same job to prime some clusters and not to prime others:
RESTORE PRIME REMP CLUSTER CL=PRIME.THESE.CLUSTERS.+ CL=LEAVE.THESE.CLUSTERS.ALONE.+ NOPRIME
Usage Rule
NOPRIME is the default unless the GVPARMS utility is used to change it to PRIME.
Note: There is no 'priming' involved with VSAM ESDS data sets. These are flat files as in sam only controlled by VSAM. KSDS on the other hand has an index set that has to be initialized (primed) before it can be opened for other than output. RRDS is the same as KSDS.
|
Copyright © 2011 CA.
All rights reserved.
|
|