5. Maintenance › 5.14 Vertical Checkpoint Expansion

5.14 Vertical Checkpoint Expansion

 If your unit has exceeded its current checkpoint entry limit,
 you can increase the size of the checkpoint file up to a
 maximum of 9999 entries.  However, you should first consider
 reviewing your CA MICS configuration for alternatives that
 will improve CA MICS performance while concurrently resolving
 the checkpoint size constraint.
 
 To increase the checkpoint size, complete the checklist
 Below:
 
 Note:  This procedure assumes you have already completed all
        installation processing for this unit database and
        that the database is populated with valid data.
 
 __  1.  Backup Checkpoint Data Set
 
         Run a BACKUP operational job to backup all of your
         databases, especially your checkpoint data set.
 
 __  2.  (Conditional) Allocate Larger Checkpoint Data Set
 
         Determine if you need a larger data set to hold the
         expanded number of checkpoint records.  Bear in mind
         that 2 tracks will hold about 100 records.  A single
         primary space allocation is preferrable.
 
         If needed, manually rename the current
         prefix.MICS.CHECKPT.DATA data set, and manually
         allocate the new prefix.MICS.CHECKPT.DATA data set.
 
         Now manually copy the old checkpoint data set to the
         new data set.
 
 __  3.  (Conditional) Incremental Update in Use
 
         If incremental update processing is done for a
         component in this unit, its incremental update
         checkpoint data set will also need to hold the
         expanded number of checkpoint records.  Consider
         repeating step 2 above on behalf of any incremental
         update checkpoint data sets in this unit.
 
 __  4.  Modify CKPTCNT Parameter
 
         Modify the CKPTCNT parameter in
         prefix.MICS.PARMS(SITE).  CKPTCNT must be a number
         between 100 and 9999.  Specify no more checkpoint
         entries than you will reasonably need.
 
         NOTE: A good rule of thumb is to set checkpoint size
         to twice the size of the original checkpoint.  For
         example, if your original CKPTCNT specification is
         100, then 200 is a reasonable size for your enlarged
         checkpoint.  If you run out of checkpoint entries at
         200, then try expanding the checkpoint size to 400
         entries.  Remember that the maximum checkpoint size
         is 9999.
 
 __  5.  Execute BASPGEN
 
         Execute the job in prefix.MICS.CNTL(BASPGEN) to
         validate your CKPTCNT specification and generate the
         %CKPTCNT macro for the unit database.
 
 __  6.  Execute CKPTINIT
 
         Execute the following job to resize your checkpoint
         data set:
 
            'prefix.MICS.CNTL(CKPTINIT)'
 
 __  7.  (Conditional) Execute Incremental CKPTINIT
 
         If incremental update processing is done for a
         component in this unit, its incremental update
         checkpoint data set must also be resized.  Since the
         component's prefix.MICS.CNTL(cccIUALC) job contains
         more than 1 job step, temporarily modify it so that
         only the last step with step name CKPTINIT is
         present.  Execute this job to resize the data set.
 
 __  8.  Resume Operations
 
         Resume normal operational job processing.