Configuring Your Product › Customization Options › The Auto-Restore Function › Installing the Auto-Restore Function

Installing the Auto-Restore Function

The auto-restore function applies to MVS installations only, and should be implemented only after a thorough review of the following installation procedure. Be sure to complete each step in the process before continuing to the next. The following discussion applies to all three hooks.

To install the Auto-Restore Function

1. See the procedure named DMSAR in the proclib library shipped with your CA Disk system. In particular, see the following items:

   Note: If you rename the DMSAR catalog procedure, you must also change the value of sysparm ARTASKNM (the default name is DMSAR). Otherwise, the support does not work.

   • Reviews the dispatching priority assigned to the procedure and makes any necessary adjustments based on your installation's requirements.
   • Supply the proper data set name for the STEPLIB.
   • If you want dynamic tape allocation, leave the asterisk in column 3 of the ARCHIVES DD statement. If you do not want dynamic allocation to be performed by CA Disk, remove the asterisk. The preferred method is to let CA Disk dynamically allocate the tape device, since this allows requests that do not require tape devices to be processed immediately, even if no tape devices are available. This condition occurs for those data sets that have been archived to disk, have no record in the CA Disk archive index, or are rejected by the user screening exit ARESPREX.
   • If you put an ARCHIVES or ARCHIVER DD statement in your JCL, do not specify the DSN= parameter. If you specify a data set name, no concurrent auto-restores can take place. In addition, you cannot be able to run auto-restores at the same time as CA Disk backup, archival, restore or recover jobs.
   • If the archives reside on disk rather than tape, the appropriate disk archive data set is dynamically allocated with no operator intervention required.
   • See the IDCUT1 and IDCUT2 DD statements. These statements are discussed in the Activating VSAM Support section in the chapter “Installation.”
   • If your installation maintains multiple FILES and you want to make them all available to the auto-restore function, use the MFILES DD statement instead of the FILES DD statement. Add each files data set name to the MFILES concatenation, up to 256 data sets are supported. The order of the concatenation determines the order of search for the data set. The first data set that contains an index record for the archived data set is used, even if another files data set contains a more recent version of the data set. Therefore, it is very important that the FILES be specified in the proper order. If you are using all FDBs in the MFILES DD statement, then the databases are logically joined and searched as single entity.

     Note: The FILES DD statement is ignored if there is also an MFILES DD statement in the procedure. Note that concatenated files data sets are not supported with the FILES DD statement.

   • Ensure that the DMSAR proc is in a proclib accessible during an MVS START command; for example, SYS1.PROCLIB.
   • Users with security packages should note that since the CA Disk auto-restore started task cannot be identified by a JOB statement or a LOGON procedure, most security packages have a Started Procedures Table to associate a started task name with a user ID and possible group name. If your security package protects resources accessed by started tasks and you would like to auto-restore data sets protected by your security package, you must create an entry in your Started Procedures Table to associate the CA Disk auto-restore started task name DMSAR with a user ID and possible group name.
   • For RACF, the Started Procedures Table is documented in the IBM manual RACF Installation Reference and in the IBM manual Systems Programming Library: RACF.
   • Now that you have the DMSAR started task identified to your security package, anyone can auto-restore user data sets in the CA Disk archives. Although this causes no security exposure (after an auto-restore completes, OPEN, SCRATCH, RENAME or IDCAMS processing prevents user access to data sets to which they are not authorized), two methods have been provided which control this effect.

   Front-End Method

   This method is always in effect and works well if your security package does not use strict volume rules (for example, a user might have access to a data set on one volume, but does not have access to it on another volume), and you do not make extensive use of discrete RACF profiles.

   CA Disk auto-restore processing uses the System Authorization Facility (SAF) to determine if the user has READ access to the data set name in question. Unfortunately, the auto-restore front-end processing does not have actual volume or discrete RACF profile information available. If queried from the catalog management hook, CA Disk passes to SAF the CA Disk pseudo- volume volser along with the data set name. If queried from the S213 exit, CA Disk passes to SAF the volume on which the OPEN was attempted along with the data set name. CA Disk allows the auto-restore to proceed only if it receives a return code of less than 8 from SAF.

   If you are an CA ACF2 user, you must activate your SAF interface to let the SAF call issued by CA Disk work properly. Also, you must add the following entry to your SAFPROT GSO list:

       SAFPROT.DMS CLASSES(DATA SET) CNTLPTS(ADSAR010)
       SUBSYS(DMS)
   

   Back-End Method

   If you use the CA Disk RACF security interface, or if you use the CA Disk/CA Top Secret Security interface and have implemented the facility activated by sysparm ARSECURE, you can use this additional method.

   Note: For more information, see the section Installing the CA Top Secret Security Interface in the chapter "Installation".

   To install this method, specify sysparm ARSECURE with a value of R or Y. For more information, see the sysparm description for ARSECUREn in the Systems Guide.

2. See the documentation for sysparms ARESUNIT, ARESUNIC, and ARESUNIn (if multiple types of cartridge devices are used). If the defaults are unacceptable, specify their values in your production sysparms.
3. See the documentation for sysparm ARTAPEOK. This sysparm controls the degree to which tape mounts will be accepted--if at all--from auto-restore tasks.
4. See the documentation for user exit ARESPREX. This user screening exit can selectively reject auto-restore requests, and can also perform logging activities.
5. If you are installing the catalog management hook and the DFHSM SVC hook, you can use pool support as well. Pool support allows you to dynamically decide the volume to which to restore a data set, based on a combination of pool definitions and an optional user exit. See the Setting Up DASD Pools for Auto-Restore section. This does not have to done at installation time. You can install the basic auto-restore facilities first and add pool support later.
6. The catalog management hook and DFHSM SVC hook of CA Disk are installed with a started task. A system IPL is not required. You install the hooks by issuing the following command from the operator's console:

   S DMSAR,DMSAR=INSTALL
   

   Output is directed back to the operator's console. When the interface is successfully installed, this started task will end.

   Implementation Notes:

   • DMSAR will attempt to install and identify several modules in CSA and will use the CSVDYLPA function to identify those modules. If your installation has restricted access to the CSVDYLPA.ADD.modname and CSVDYLPA.DELETE.modname resources, it may be necessary to define multiple FACILITY class resources in your security system and grant access to those resources for DMSAR to execute properly. The resource names are of the format CSVDYLPA.ADD.modname and CSVDYLPA.DELETE.modname, where modname will be:
     • ADSAR010
     • ADSHS001
     • ADSAR026
     • DIMCH400

     If access to these resources is not granted, the DMSAR INSTALL fails with a DIM427I message. For more information, see Granting or Denying Access to System-Installed Intercept Modules.

   • You must issue this command on each CPU for which you want CA Disk's auto-restore function implemented.
   • The CA Disk catalog management hook and DFHSM SVC hook are removed each time you IPL. Therefore, you must use the above procedure to reinstall the hooks when you IPL. Consider installing the command in the automatic start-up procedures.
   • If you run CA Allocate, issue the start command for DMSAR before the start command for CA Allocate.

     You can check if the CA Disk catalog management hook and DFHSM SVC hook are installed by issuing the operator command:

     S DMSAR,DMSAR=STATUS
     

     or simply:

     S DMSAR
     

     You can remove the CA Disk catalog management hook and DFHSM SVC hook by issuing the operator command:

     S DMSAR,DMSAR=REMOVE
     

     If you do issue this removal command, there are several processing steps to be aware of:

     After a remove command is accepted, the SVC table entries for SVC 26 and the DFHSM SVC are modified to point to their original addresses. This disables the hooks. The removal task waits eight seconds so that current requests can complete, then DMSAR deletes its hooks from CSA memory. The hooks are completely removed and the started task terminates.

   • If you plan to use a CA Disk pseudo-volume name other than ARCIVE, it must be specified through sysparm RECATVOL. Do not select a pseudo-volume name that is a real volume name, or likely to become one. If your pseudo-volume name is a real volume, you cannot reference your data sets on that volume through the catalog. Set the pseudo-volume name as the value for the sysparm RECATVOL.
   • For more information, see the sysparm description for PSUDEVTPn in the Systems Guide.
   • An auto-restore diagnostic facility exists within both the Catalog management hook and the DFHSM SVC hook which can display applicable data used to determine if an auto restore is to be performed. These diagnostic messages are available if you have installed the Test Auto-Restore Interface as described next, and if your job name is equal to the test jobname (default is TESTDISK). If you want to change this default jobname, simply zap the jobname you prefer. For more information, see the TSTHOOKS member in the INSTALL library and installation instructions for the Test Auto-Restore Hook.

     Similar diagnostic facilities are provided for the CA Disk SVC module and VSAM date stamp module. The default jobname for the other diagnostic facilities is DMSTEST, so you can make this the same name for all functions. The ability to change the job names for the other functions is discussed where applicable.