Configuring Your Product › Tailoring and Other Considerations › Implementing Support for Masstor M860 › Distinguishing the M860 Device

Distinguishing the M860 Device

CA Disk supports the M860 as a distinct device only using dynamic allocation. If archives are written to the M860 by referencing it on a DD statement in your JCL, it appears that it is a 3420 or 3480 and is recorded as such in the ARCHVOLS record (which is subsequently used by restore, recover, and merge processing to allocate what is thought to be the proper type of device).

You inform CA Disk that an M860 device is being used and should be tracked in the ARCHVOLS as requiring special allocation by providing the proper value for sysparms ARC0TYPE, ARCCTYPE, MERPnTYP, MERCnTYP, and MERTnTYP. The standard values for these sysparms are TAPE, 3480, or DISK. For the M860, a value of DYN1 must be specified. This causes the DYN1 special unit flag bit to be set in the ARCHVOLS record. Subsequent CA Disk dynamic allocation processing examines this bit and, if on, uses the unit name provided by sysparm ARESUNI1 for auto-restore, and sysparm DYN1UNIT for all other functions. (DYN2 through DY20 options are also provided, but are explained later.)

The following table indicates which sysparms you use to provide the unit name for each device type value of sysparm ARC0TYPE. Sysparms beginning provides unit names for the auto-restore function with ARES, while all other functions take their unit names from sysparms beginning with DYNn/DYnn. The following table shows possible M860 values for ARCOTYPE.