Previous Topic: Implementing CA VSAMAIDNext Topic: XTNDCHK


*AMS Overrides

*AMS overrides can be used along with CA VSAMAID recommendations. If an override is specified, CA FAVER uses it instead of the recommended value.

Overrides should be used with caution, as they can invalidate another item's value, possibly causing an IDCAMS DEFINE error. One type of recommendation prevents automatic implementation when overridden: A volser change. If an override of these recommendations is encountered, a message reports that the recommendation was not implemented.

The following JCL example is used to restore a specific cluster with an AMS name override, during a single step which is also performing generic cluster restores.

Note: For this to work correctly, the specific cluster must be listed after the CL=generic group of overrides.

//SYSIN    DD *
RESTORE PURGE
 CLUSTER
  CL=HURRO01.SMPCSI.TWO.+ *AMS -
  CL (NAME(HURRO01.SMPCSI.TWO.REN2) VOL(ASM008)) -
  DATA(NAME(HURRO01.SMPCSI.TWO.REN2.DATA)) -
  INDEX(NAME(HURRO01.SMPCSI.TWO.REN2.INDEX))
  CL=HURRO01.SMPCSI.RENAMED *AMS -
  CL (NAME(HURRO01.SMPCSI.AFTERRN) VOL(ASM008)) -
  DATA(NAME(HURRO01.SMPCSI.AFTERRN.DATA)) -
  INDEX(NAME(HURRO01.SMPCSI.AFTERRN.INDEX))