Loudwater
Systems
Management

Managing EPDM database size

Use TSO %SPACE to list EPDM tablespaces and their VSAM characteristics (Primary, secondary allocs; number of extents). To control number of extents, do not do as described in EPDM Admin Guide (creating a job) because the process described DOES NOT DOCUMENT the change. 
     1. Use ISPF to make an appropriate SQL statement eg DEFS(ALTTS)
        with your documenting comments in.
     2. Using the EPDM Dialog Other/DB2I
        issue the command -STOP TABLESPACE DATABASE(DRLDB) SPACENAM(DRLS....)
     3. Using the EPDM Dialog Other/Process PRM Statements
        execute the SQL statement
     4. Using the EPDM Dialog Other/DB2I
        issue the command -START TABLESPACE DATABASE(DRLDB) SPACENAM(DRLS....)
At next REORG, the new values will be used.

Indexes are separate VSAM datasets with PRI and SEC set when they are defined. The above process works for indexes too, but use the external VSAM name. Then a REORG will remove the excess extents.

Use this SQL to find what the internal index name is from the external VSAM name: 

     SELECT * FROM SYSIBM.SYSINDEXES WHERE INDEXSPACE = 'vsam_name';
or REXX exec does the same but much faster via the indirect copies of the DB2 tables (changes less than 24 hrs old not reflected) 
     %LIX vsam_name
or REXX exec does the same as the SQL above (ie direct, up-to-date) 
     %HOTLIX vsam_name  /* Now is that a good name for an EXEC, or what? */

Use TSO %QTAB to list EPDM tables and their sizes (based on data in SYSIBM tables, so you must run a RUNSTATS job or the QTAB data is misleading). TSO %QTABF causes the output to be stored as EPDM.CNTL(BADB)

To control growth of individual tables, change PURGE condition, or change the UPDATE to 'zap' a key.