Copying the data that DSNADMSB and ADMIN_INFO_SQL collect to another subsystem

The jobs that DSNADMSB and ADMIN_INFO_SQL produce are primarily intended for the use of IBM® Software Support. However, you can modify those jobs so that you can run them on your own test systems to reproduce a problem environment.

1. Ensure that your test system does not contain data that conflicts with the data that DSNADMSB or ADMIN_INFO_SQL collects.
   Recommendation: Use a newly installed Db2 subsystem for testing.
2. Customize the jobs:
   1. Modify the JOB statement for your test system.
   2. Change the subsystem name to the subsystem name for your test system.
   3. Change the steps that run TSOBATCH so that they run IKJEFT01.
      For example, suppose that the original code looks like this:

      //SETUP    EXEC TSOBATCH,DB2LEV=DB2A

      You need to change the code to something like this:

      //SETUP EXEC PGM=IKJEFT01,DYNAMNBR=20
      //SYSTSPRT DD  SYSOUT=*                
      //SYSPRINT DD  SYSOUT=*                
      //SYSUDUMP DD  SYSOUT=*                
      //SYSTSIN  DD  *                       

   4. Change the steps that run DSNTEP3 so that they run DSNTEP2.
      For example, suppose that the original code looks like this:

      //SYSTSIN DD *        
       DSN S(SSTR) R(1) T(1)
       RUN PROGRAM(DSNTEP3) 
       END                  

      You need to change the code to something like this:

      //SYSTSIN DD *        
       DSN S(SSTR) R(1) T(1)
       RUN  PROGRAM(DSNTEP2) PLAN(DSNTEPD1) +
           LIB('DSND10.RUNLIB.LOAD')
       END
      

3. Set the subsystem parameters on the test system as indicated in the output file that contains subsystem parameter values (PARM file).

   If DSNADMSB or ADMIN_INFO_SQL output is returned in a single job stream (output-method is R), the subsystem parameter output is at the end of the job output.

4. In the data definition language job (the job that contains ** DDL Information **), make these changes:
   1. Modify the -ALTER BUFFERPOOL statements at the end of the job to contain settings that are appropriate for your test system.
   2. Remove the asterisks (**) in front of the -ALTER BUFFERPOOL statements.
   3. Move the -ALTER BUFFERPOOL statements to the place in the job that says:

      **BUFFERPOOL INFORMATION GOES HERE

5. Run the remainder of the jobs, in the following order:
   1. Data definition language job (contains ** DDL Information **)
   2. Statistics INSERTs job (contains ** Stats inserts **)
   3. Column statistics INSERTs job (contains ** Column Stats inserts **)
   4. Plan, profile and accelerator INSERTs job (contains ** Plan, Profile and Accelerator Inserts **)