Moving backup pools and using extent information. Sequence of searching for allocation information.
Article ID: 13697
Updated On:
Products
Issue/Introduction
We have backed up our production Datacom databases to a Dynam DASD pool, then we dumped the DASD pool to tape. We now want to access this Datacom database on another VSE system that shares both the Dynam catalog and the Datacom backup on the DASD pool.
In the meantime the first Datacom backup has been deleted and a new backup has been made to the Dynam DASD pool.
The tape backup of the DASD pool has been restored to the other VSE, to a NEWLY defined DASD pool.
We want to load the Datacom backup on the other VSE not from the original Dynam backup DASD pool but instead from the new DASD pool I restored the tape to.
How can I point to the newly defined DASD pool so that the Datacom load files are selected from there and not from the most recent backup done to the Dynam DASD pool ?
Resolution
Dynam/D will search for catalog information in the following sequence:
1 - System Options Default definitions
2 - Catalog definitions
3 - JCL definitions (TLBL, DLBL, overrides, EXTENT information etc).
If the full extent is specified, Dynam/D will use the extent information instead of the catalog information when creating a file and the version will not be cataloged.
If you want to read a file which is NOT Dynam/D controlled (not in the catalog) then Dynam/D will search all DASD volumes defined to the VSE to find this file from low address to high address.
To restrict Dynam/D to only search on a specific DASD volume or on a specific range of DASDs defined in a DASD POOL an // EXTENT card is required for the // DLBL card for the file name to search.
Feedback
