System Setup › Oracle Host Software Component (HSC) and Storage Management Component (SMC) › Method Three: HSC/SMC Parameters

Method Three: HSC/SMC Parameters

We recommend that you implement the POLICY statements as discussed in the section Method One: POLICY Statements, to avoid updating your TAPEREQ parameters each time you modify the CA Vtape filters. If you choose to use this method, and your release of the HSC/SMC software still supports these parameters, then you must make the following changes:

• SLSSYSxx for the virtual scratch pool tape range.

  SCRPOOL  NAME(VTAPE) RANGE(V00001-V99999) LABEL(SL)
  

  Note: After changing SLSSYSxx, a Recycle of the HSC started task is required to activate the change.

• TAPExx for the data sets to be intercepted by CA Vtape.

  TAPEREQ  DSN(VTAPE.**) MED(LONG) REC(36) SUBPOOL(VTAPE)
  

• VOLxx entry for the virtual tape range.

  VOLATTR SERIAL(V00001-V99999) MEDIA(LONG) RECTECH(36)
  

• UNITxx entry for the virtual tape device range.

  UNITATTR ADDRESS(0F00-0F1F) MODEL(9490)
  

Note: Review the HSC manuals to verify the preceding information concerning HSC setup.

If a new esoteric will be defined for CA Vtape, the NNLBDRV HSC parameter in the LIBGEN should be updated with the esoteric as follows:

NNLBDRV=VTAPE  or  NNLBDRV=(VTAPE,VTAPE)

Where VTAPE is the new esoteric on Host0, or Host0 and Host1.

If the parameter already has a value coded, using IBM's HCD software, define a new esoteric containing all the nonlibrary devices and code the NNLBDRV HSC parameter as follows:

NNLBDRV=NONSILO  or  NNLBDRV=(NONSILO,NONSILO)

Where NONSILO is the new esoteric on Host0, or Host0 and Host1.

The new esoteric is only used for the NNLBDRV HSC parameter. The original esoteric and the new CA Vtape esoteric will be used in JCL or software parameters as needed.