Planning is an important part of running the CATVMFX utility. The CATVMFX utility creates new volume base records in the VMF. Every TLMS sharing the VMF must be at the correct maintenance level to perform an EXTEND. CATVMFX checks the maintenance level of every TLMS it finds by reading the VMF PRINTCPU field in the control record. If any of the TLMSs are not at the correct maintenance level, a STATE of "Old Code" is issued in the status message. The new VMF and the alias must belong to the same z/OS user catalog, for example, their high level qualifiers must match.
The new VMF must be large enough to contain all active records currently in the old VMF. The new VMF can reside on the same volume or a different volume than the original VMF. Catalog the new VMF to the same user catalog as the alias. You can execute CATVMFX as a z/OS started task or a batch job.
During the extend process, all TLMS tasks perform synchronous updates to both VMFs while records from the old VMF are copied to the new VMF. Once all active records are copied, a z/OS Catalog alias points to the new VMF. All batch and online tape activity references the new VMF through this z/OS Catalog alias. After the EXTEND process completes, all CA TLMS tasks drop the old VMF, ending the process.
Since both the old and new VMFs are updated synchronously during the extend process, you do not need to stop batch and online tape activity. All jobs referencing either the old or the new VMF can run to completion safely.
|
Copyright © 2014 CA.
All rights reserved.
|
|