z/OS DFSMS Implementing System-Managed Storage
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Designing the Storage Class Routine for CICS Data

z/OS DFSMS Implementing System-Managed Storage
SC23-6849-00

The high-level qualifier (HLQ) identifies CICS® data sets and the LLQ identifies data types requiring specialized performance and availability services. Each of the special service database data types are identified by a FILTLIST statement. Figure 1 shows the FILTLIST section of the storage class ACS routine for CICS database data sets.

Figure 1. FILTLIST Section for CICS from Storage Class ACS Routine
FILTLIST SPECIAL_USERS       INCLUDE('SYSPROG','STGADMIN','DBA')
FILTLIST VALID_STORAGE_CLASS INCLUDE('BACKUP','CRITICAL','FAST','FASTREAD',
                                     'FASTWRIT','GSPACE','MEDIUM','NONVIO',
                                     'STANDARD','DBCRIT')
/**********************************************************************/
/*             Start of CICS-related FILTLISTs                        */
/**********************************************************************/
FILTLIST CICS                INCLUDE(%CICS.**)
FILTLIST CICS_PROD_CAVM      INCLUDE(PCICS*.**.DFHXRMSG,
                                     PCICS*.**.DFHXRCTL)
FILTLIST CICS_PROD_DB        INCLUDE(PCICS*.EMPLOYEE.DB.*)
FILTLIST CICS_PROD_LIB       INCLUDE(PCICS*.**.LOADLIB,
                                     PCICS*.**.COB2CICS,
                                     PCICS*.**.COB2LIB,
                                     PCICS*.**.PLILINK)
FILTLIST CICS_USER_DB        INCLUDE(TCICS*.PAYEXTRT.DB.*)
FILTLIST CICS_PROD_LOG       INCLUDE(PCICS*.**.DFHJ01%)
FILTLIST CICS_PROD_RESTART   INCLUDE(PCICS*.**.DFHRSD)
FILTLIST CICS_PROD_CSD       INCLUDE(PCICS*.**.DFHCSD)
FILTLIST CICS_PROD_INTRA     INCLUDE(PCICS*.**.DFHINTRA)
FILTLIST CICS_PROD_TEMP      INCLUDE(PCICS*.**.DFHTEMP)
/**********************************************************************/
/*             End of CICS-related FILTLISTs                          */
/**********************************************************************/

Figure 2 shows the coding required to let database and storage administrators and system programmers assign a storage class externally. Additionally, this restricted set of users can use the artificial class, NONSMS, to exclude data sets from system management.

Figure 2. Segment to Permit Special Users to Override SMS allocation
  WHEN (&GROUP = &SPECIAL_USERS &&         /*  Permit storage admin., */
        &STORCLAS = &VALID_STORAGE_CLASS)  /*  system programmers,    */
    DO                                     /*  and DBAs to specify    */
      SET &STORCLAS = &STORCLAS            /*  a storage class        */
      EXIT
    END
  WHEN (&GROUP = &SPECIAL_USERS &&         /*   Permit storage admin. */
         &STORCLAS = 'NONSMS')             /*   or data base admin.   */
    DO                                     /*   to create             */
      SET &STORCLAS = ''                   /*   non-system-managed    */
      EXIT                                 /*   data sets             */
    END

CICS database data sets are first identified by the HLQ, PCICS, UCICS, or TCICS. Selected system and recovery database data sets are identified and assigned a storage class having attributes set to provide the required services. In this sample routine, production databases are given DASD fast write and cache services. User databases receive better than average service and, if allocated behind a cache-capable 3990 storage control, become may-cache candidates. In keeping with our ACS coding recommendations, once a data type has been identified, it is assigned an appropriate storage class and then the routine is exited. Figure 1 shows the coding for the CICS database data sets.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014