The volume recovery (not the restore) function supports the recovery of ICF catalogs. Although ICF catalogs are VSAM, the CA Disk recover function regards them as neither VSAM nor non-VSAM, but special data sets with special recovery requirements. The CATALOGS= parameter on the SELECT command determines whether ICF catalogs are included in the recovery. When included in the recovery, CA Disk always recovers the ICF catalogs first — before any of the data sets. This allows the catalogs to be updated correctly for those data sets that are subsequently included in the recovery process.
There are three parameters — CATALOGS=catname, DEFALIAS= YES/no, and EXPORTF=NO/yes — on the SELECT command that apply specifically to ICF catalog recovery. The CATALOGS= parameter provides a higher degree of control in deciding what catalogs are to be restored. It defaults to NO and must be specifically selected to be included.
As explained in that section, CA Disk dynamically links to IBM's IDCAMS IMPORT function to recover a catalog, and will then optionally redefine the alias entries in the master catalog. A few particulars regarding the IMPORT command should be noted. (See the IBM IDCAMS manual for more specific information.) RACF profiles, if any exist, are not affected by the catalog import. If the old catalog is still on the volume, it will be overlaid. A new catalog can be preallocated if desired (perhaps to increase the size), and the preallocated space will be used. If the catalog does not exist, IMPORT will define it. You cannot give the catalog a new name, however, as the IMPORT command does not support it. Another unexplained but observed phenomenon is that if the catalog was allocated in tracks, IMPORT will increase the allocation values if it has to redefine it. If track allocations were not used, IMPORT will reuse the original space values.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|