4. Operation › 4.4 Administering CA MICS › 4.4.8 CA MICS Administration in SMS-Controlled Environment › 4.4.8.1 SMS Allocation of SAS Data Sets

4.4.8.1 SMS Allocation of SAS Data Sets

 SAS data sets are allocated and appear to z/OS and DFSMS as
 sequential data sets.  These data sets have a proprietary
 internal construction and require a proprietary SAS access
 method to be read or written at the record level.  They are
 not, in fact, sequential data sets.
 
 SAS supports many allocation scenarios.  These are discussed
 in the SAS Companion for z/OS.  In the 9.2 version of that
 guide there is a section entitled Assigning SAS Libraries.
 Of particular interest may be the subsection entitled Using
 Multivolume SAS Libraries.
 
In the case of multivolume libraries, there is
 no protection or flagging in SAS for data sets that get out
 of sync when a volume restore is done on one of the units
 where the data library resides.  Such a situation can cause
 unpredictable errors that are difficult to diagnose.
 
 SAS libraries are allocated in different ways depending on
 usage and operating environment.  Because of the differences
 in allocation, these can be assigned different Data Classes.
 
 o  The CA MICS Unit Database, CA MICS Accounting and
    Chargeback files, and CA MICS Capacity Planner files are
    permanently allocated libraries.
 
 o  All SAS invocations require a WORK file; this is usually
    a temporarily allocated library.  Use the WORKSMSPARMS
    parameter in sharedprefix.MICS.PARMS(JCLDEFC) and
    prefix.MICS.PARMS(JCLDEF) to specify STORCLAS, MGMTCLAS,
    DATACLAS, etc. for WORK file allocations.
 
 o  All CA MICS cataloged procedures allocate temporary sort
    work data sets (SORTWK01-SORTWK99).  Use the SORTSMSPARMS
    parameter in sharedprefix.MICS.PARMS(JCLDEFC) and
    prefix.MICS.PARMS(JCLDEF) to specify STORCLAS, MGMTCLAS,
    DATACLAS, etc. for sort work data set allocations.
 
 o  CA MICS components enabled to multiple work file support
    allocate additional WORKnn DDs.  Data set allocation
    parameters are specified in the product's cccOPS member
    WORK parameter.  This parameter supports the SMS STORCLAS,
    MGMTCLAS, and DATACLAS parameters in addition to UNIT and
    VOLSER.  See the product guides for more information.
    Refer also to Section 2.3.1.6, Database Complex JCL
    Definitions, for an example.
 
 o  CA MICS components enabled to internal step restart
    support dynamically allocate and catalog the restart
    control data set and multiple intermediate SAS work file
    data sets.  Data sets are allocated and cataloged at the
    beginning of the database update job step, and are
    retained if the step abends.  The data sets are deleted
    after the database update completes successfully.  Data
    set allocation parameters, including the SMS STORCLAS,
    MGMTCLAS, and DATACLAS parameters, are specified in the
    product's cccOPS member.  For more information, see the product guides.
.
 
 o  Several SAS data libraries are dynamically allocated by
    the CA MICS Information Center Facility (MICF).  These
    include data libraries allocated to the following
    ddnames:
 
      BICFUSER
      CAPACITY
      PMWFSAS
      SASPROF
      TEMPSAS
      USER
      WORK
      UMWFSAS
 
    Use the CA MICS Administrator Facility Options dialog to
    specify allocation parameters for these data sets (see
    Section 4.4.2.4).  MICF users can override the shared
    defaults allocation parameters through the MICF options
    dialog.  Both options dialogs support SMS parameters in
    the Additional Allocation Parameters free-form data entry
    field.