DB2 Z/OS Automated UNLOAD AND RELOAD GENERATION. A Rexx exec that will build UNLOAD and RELOAD jobs for a list of tables. All the user needs to provide is a list of table names in a flat file., the source DB2 subsystem name, the source table qualifier, the target db2 subsystem name and the target table qualifier. This stream has a JCLUNLOAD, JCLRELOAD, TABLELIST and REXX.
DB2 Z/OS Intelligent Reorganization. A job that will analyze the statistics of all of your DB2 objects and decide based on the guidelines you provide which objects need to be reorganized every week. This job will also create the appropriate ONLINE REORG JCLs with the correct data set sizes that can be either submitted automatically or through the scheduler at scheduled times. This stream has a JCL , a REXX and a PARM dataset. The JCL is what queries the catalog and runs the rexx to produce the required reorg jobs. Customize the JCL and the PARM dataset to meet your shop's requirement.
DB2 Z/OS Intelligent
copy 1 ( If you do not have real time stats implemented).
Copy only those table spaces that have changed since
last copy or have not been copied in the past n days (Arbitrary number)
or if the previous image copy is about to expire even if the table data
has not changed. This will give good cost savings on tape mounts and
I/O cycles as you wont be unnecessarily copying and vaulting data that
has not changed. Automatically, generate Image copy steps for new
table spaces you add and remove Image copy steps for table spaces you
have dropped. Exclude specific table spaces or Databases from copying.
Specify different parms for special objects. This
stream has a JCL
, a REXX , a PARM
and a DONT COPY
dataset.The JCL is what
queries the catalog and runs the rexx to produce the required copy.
Customize the JCL and the PARM dataset to meet your shop's
DB2 Z/OS Intelligent copy 2 (If you have real time stats implemented). Same as above, but much more efficient. This is the preferred method. This stream has a JCL , a REXX , PARM and a DONT COPY dataset. The JCL is what queries the catalog and runs the rexx to produce the required copy. Customize the JCL and the PARM dataset to meet your shop's requirement.DB2 Z/OS Intelligent Runstats with history. A job that will automatically generate statistics for all your DB2 objects by taking a real time inventory of the DB2 objects in your subsystem. It is critical for you to have information about your tables and indexes. An unknown table is a problem waiting to happen. This stream has a JCL , a REXX and a PARM dataset. The JCL is what queries the catalog and runs the rexx to produce the required copy. Customize the JCL and the PARM dataset to meet your shop's requirement.
DB2 Z/OS Production Access Path and ASU Cost in development. One of the common problems faced by developers is that the data in production does not match the data in development. This results in different access paths for plans and packages in production as compared to development. It would be very beneficial if we can guess how a particular program will perform in production while the program is in development. This process will extract the relevant access path statistics from production for a given table and generate SQL statements that can then be run against the development system to update the statistics to match production. This stream has a JCL , a REXX and a PARM dataset. PS: The access path also depends on bufferpools and CPU serial number which is not handled by this Rexx. This Rexx also assumes that you have installed DSNREXX plan and package at your shop.
DB2 Z/OS Excess pages query. It is not uncommon to see pages being over allocated to table spaces. Some times this goes unnoticed and causes wastage of resources. For example, image copy jobs take much longer to run due to empty pages being copied, Buffer pool hit ratio goes down due to reduced buffer density, table space scan is inefficient etc. This SQL will give you the number of pages that are over allocated to each table space in your system. Be mindful of the fact that FREEPAGE, PCTFREE etc have not been taken into account in this query.
DB2 Z/OS Lopsided partitioned tablespace query. It is not uncommon to see a few partitions of a tablespace to have the bulk of the data. This defeats the whole perpose of partitioning. Use this SQL to identify those objects.