3.5.6.2 CA MICS Database and File Space Allocation

3. Installation › 3.5 Generate a Database Unit › 3.5.6 Generate and Allocate the Database › 3.5.6.2 CA MICS Database and File Space Allocation
3.5.6.2 CA MICS Database and File Space Allocation


The OS data sets that hold your database, and, optionally,
certain work files used by the update jobstream, are
allocated by running the ALLOCATE job in prefix.MICS.CNTL.

First, however, the ALLOCATE job must be edited to fill in
certain JCL parameters, such as space requirements, device
types, and if necessary, the specific volume serials for the
allocations.  You can use the Database Space Estimator
Libname Summary Report from your DBSIZE run to estimate how
much space is needed for each of the five data sets in the
database.

Figure 3-4 illustrates the ALLOCATE job statements.  Note
that if your DASD requirements are such that any of the five
OS data sets (DETAIL, DAYS, WEEKS, MONTHS, and YEARS) must be
larger than a single volume, you should use the facilities
described in Section 2.3.3.3.2.4, CA MICS Database Split
Table (DBSPLIT).  Note also that the permanent DAYSMF DD
statements are generated only for components that you have
installed.

Note:  The ALLOCATE job does NOT allocate the incremental
       update database files or the SPLITSMF job output SMF
       data files.  These data sets are associated with a
       specific product in the unit database and are
       allocated by the individual product's cccIUALC job, or
       are dynamically allocated as required.  Data set
       allocation parameters are specified in the product's
       prefix.MICS.PARMS(cccOPS) member.  See the
       individual product guides for more information on
       incremental update database file allocation.

While EDITing the ALLOCATE member in the MICS.CNTL library,
you can FIND the statements requiring user-provided
information by looking for eye-catching arrows ('<--<<').

 //BR14 EXEC PGM=IEFBR14
 //*
 //* DATABASE ALLOCATION :
 //* SPECIFY SPACE, VOLSER, AND UNIT TYPE
 //* FOR THE DATABASE FILES.
 //* USE RECOMMENDED SPACE FROM "DBSIZE" REPORT.
 //*
 //DETAIL DD DSN=EYC.MICS.DETAIL,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______    <--<<
 //DAYS DD DSN=EYC.MICS.DAYS,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______    <--<<
 //WEEKS DD DSN=EYC.MICS.WEEKS,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______    <--<<
 //MONTHS DD DSN=EYC.MICS.MONTHS,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______    <--<<
 //YEARS DD DSN=EYC.MICS.YEARS,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______    <--<<
 //*
 //* CHECKPOINT AND RESTART.CNTL ALLOCATION :
 //* SPECIFY VOLSER AND UNIT TYPE FOR THE
 //* CHECKPOINT AND RESTART FILES
 //*
 //CHECKPT DD DSN=EYC.MICS.CHECKPT.DATA,
 // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(5,2)),
 // UNIT=____,VOL=SER=______                           <--<<
 //RESTART DD DSN=EYC.MICS.RESTART.CNTL,
 // SPACE=(TRK,(5,5)),DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200),
 // DISP=(NEW,CATLG,DELETE),
 // UNIT=____,VOL=SER=______                           <--<<

Figure 3-4. ALLOCATE Job Contents (Part 1 of 2)
 //*
 //* DAYSMF FILES ALLOCATION :
 //* SPECIFY SPACE, VOLSER, AND UNIT TYPE
 //* FOR THE PERMANENT DAYSMF FILES
 //*
 //USER DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______,   <--<<
 // DSN=EYC.MICS.USER.DATA
 //*
 //* EACH OF THE FOLLOWING ARE ALLOCATED ONLY IF REQUIRED
 //*
 //TSO DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______,   <--<<
 // DSN=EYC.MICS.TSO.DATA
 //RMF DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______,   <--<<
 // DSN=EYC.MICS.RMF.DATA
 //SMF DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______,   <--<<
 // DSN=EYC.MICS.SMF.DATA
 //CIC DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______,   <--<<
 // DSN=EYC.MICS.CIC.DATA
 //IMS DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(____,___)),UNIT=____,VOL=SER=______,   <--<<
 // DSN=EYC.MICS.IMS.DATA

Figure 3-4. ALLOCATE Job Contents (Part 2 of 2)
Database Timespan File Allocation

The Database Space Estimator Libname Report estimates the
space requirements in terms of tracks for each of the five
database timespans that equate to five OS data set
allocations.  There is no advantage to cylinder allocation
for a SAS file, and the update process is not affected by
their being on a single volume.

Modify each of the SPACE, UNIT, and VOLUME parameters to be
in accordance with your database allocation requirements.
For example, to allocate the database with the following
track allocations to the 3390 volume MICS01, the statements
would be modified as shown below.

 //DETAIL DD DSN=EYC.MICS.DETAIL,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(3000,150)),UNIT=3390,VOL=SER=MICS01    <--<<
 //DAYS DD DSN=EYC.MICS.DAYS,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(2000,100)),UNIT=3390,VOL=SER=MICS01    <--<<
 //WEEKS DD DSN=EYC.MICS.WEEKS,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(1500,075)),UNIT=3390,VOL=SER=MICS01    <--<<
 //MONTHS DD DSN=EYC.MICS.MONTHS,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(2500,125)),UNIT=3390,VOL=SER=MICS01    <--<<
 //YEARS DD DSN=EYC.MICS.YEARS,
 // DISP=(NEW,CATLG,DELETE),DCB=(DSORG=PS,RECFM=FS),
 // SPACE=(TRK,(1000,250)),UNIT=3390,VOL=SER=MICS01    <--<<

Figure 3-5. ALLOCATE Database Example
ALLOCATING CHECKPOINT AND RESTART FILES

Modify each of the UNIT, and VOLUME parameters to be in
accordance with unit and volume that are to be used for the
Checkpoint and Job Restart Files.  For example, to allocate
the files to the 3390 volume MICS01, the statements would be
modified as shown below.

 //CHECKPT DD DSN=EYC.MICS.CHECKPT.DATA,
 // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(5,2)),
 // UNIT=3390,VOL=SER=MICS01                           <--<<
 //RESTART DD DSN=EYC.MICS.RESTART.CNTL,
 // SPACE=(TRK,(5,5)),DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200),
 // DISP=(NEW,CATLG,DELETE),
 // UNIT=3390,VOL=SER=MICS01                           <--<<

Figure 3-6. ALLOCATE Checkpoint Example



ALLOCATING WORK FILES

The DAILY job requires a work file for each CA MICS product
that takes its input from SMF, if there are two or more of
them installed (refer to the discussion of the SMFRECORDING
statement in Section 2.3.3.2.1.1, "Control Definitions").
If work files are used, they will have names of the following
form:

prefix.MICS.component.DATA

where "component" is any of the three letter component
identifiers.  These files are used to pass SMF data from the
DAYSMF job step to the update processor job step for their
product.  These data sets can be optionally defined as
permanent or temporary.  The definition is made in the JCLDEF
PARMS member and is described as the DAYSMF option in section
2.3.3.2.1.3, Execution Option Definitions.  These work files
will not be included in this job if the DAYSMF option
described above is set to TEMPORARY.

Note:  These data sets apply only to the DAILY job and are
       populated in the DAYSMF step.  If you are using the
       optional incremental update facility for two or more
       products, then you may choose to use the SPLITSMF job
       and associated INCRSPLIT USE option for INCRccc job
       input data preparation.  Data sets created by the
       SPLITSMF job are allocated dynamically when required,
       with data set allocation parameters being specified in
       the prefix.MICS.PARMS(cccOPS) INCRSPLIT USE parameter.
       Please see the individual product guides for more
       information on incremental update SPLITSMF job output
       data set allocation.

Work file space requirements can be estimated by either of
the following methods:

  1.  For each product, use the output of IFASMFDP to obtain
      the number and average length of each type of record
      used by the component.  Section 6.1.2 of the Batch and
      Operations Analyzer Guide lists the record types used
      by each component that takes data from SMF.  Estimate
      the amount of space needed to hold these records.

  2.  Allocate files temporarily and run the DAYSMFR step of
      the DAILY job.  This step produces the work files.  See
      how much space is actually needed for each file, and
      use those figures for the permanent allocation.

Modify each of SPACE, UNIT, and VOLUME parameters to be in
accordance with the work file requirements.  For example, to
allocate the work files with the following track allocations
to the 3390 volume MICS02, the statements would be modified
as shown below.

 //USER DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(100,050)),UNIT=3390,VOL=SER=MICS02,   <--<<
 // DSN=EYC.MICS.USER.DATA
 //TSO DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(300,100)),UNIT=3390,VOL=SER=MICS02,   <--<<
 // DSN=EYC.MICS.TSO.DATA
 //RMF DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(200,100)),UNIT=3390,VOL=SER=MICS02,   <--<<
 // DSN=EYC.MICS.RMF.DATA
 //SMF DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(700,200)),UNIT=3390,VOL=SER=MICS02,   <--<<
 // DSN=EYC.MICS.SMF.DATA

 //CIC DD DISP=(NEW,CATLG,DELETE),
 // SPACE=(TRK,(300,100)),UNIT=3390,VOL=SER=MICS02,   <--<<
 // DSN=EYC.MICS.CIC.DATA

Figure 3-7. ALLOCATE Work File Example


When you have finished EDITing it, you can submit the job:

    SUB 'prefix.MICS.CNTL(ALLOCATE)'
Tell Technical Publications how we can improve this information