Migration step 22: Bind SPUFI and DCLGEN and user-maintained database activity: DSNTIJSG

Use job DSNTIJSG to bind packages for SPUFI, DCLGEN, and the EXEC SQL utility.

About this task

In migration mode, DSNTIJSG completes the following actions:

  • Binds packages at the new release level for SPUFI, DCLGEN, and the EXEC SQL utility.
  • Creates a new resource limit facility table, DSNRLMTnn, and a new resource limit facility index, DSNMRLnn. By default, the step that creates this new table and index is commented out in the JCL. To have Db2 create DSNRLMTnn and DSNMRLnn, uncomment the step.
  • Adds new EXPLAIN tables under the SYSIBM schema.

Procedure

To bind the SPUFI, DCLGEN, and the EXEC SQL packages for Db2 12, complete the following steps:

  1. If you bound special SPUFI packages and plans in Db2 11, you need to bind those packages again in Db2 12. You do not need to bind those plans again. For example, to update special SPUFI packages that were created for use by SPUFI users who require a TSO terminal CCSID of 1047, issue the following commands.
    Begin general-use programming interface information.
    BIND PACKAGE(SPUR1047) MEMBER(DSNESM68) -
     ACTION(REPLACE) ISOLATION(UR) ENCODING(1047) -
     LIBRARY('prefix.SDSNDBRM') 
BIND PACKAGE(TIAP1047) MEMBER(DSNTIAP) -
     ACTION(REPLACE) ISOLATION(CS) ENCODING(1047) -
     LIBRARY('prefix.SDSNDBRM')
BIND PACKAGE(SPCS1047) MEMBER(DSNESM68) -
     ACTION(REPLACE) ISOLATION(CS) ENCODING(1047) -
     LIBRARY('prefix.SDSNDBRM')
BIND PACKAGE(SPRR1047) MEMBER(DSNESM68) -
     ACTION(REPLACE) ISOLATION(RR) ENCODING(1047) -
     LIBRARY('prefix.SDSNDBRM')
    End general-use programming interface information.
  2. If you are using a data sharing environment, you must ensure that the resource limit facility (RLF) is inactive on all members in the data sharing group before running DSNTIJSG. To do this, issue the STOP RLIMIT command for each member.
  3. Ensure that all your subsystems have the same maintenance level for your DSNUGSQL DBRM.
  4. Run job DSNTIJSG,
    If DSNTIJSG runs successfully, it produces a return code of 0. However, job step DSNTIJG can produce a return code of 4 if the specified access has already been granted on one or more objects.
  5. If job DSNTIJSG fails or abends, ensure that the user that is specified on the JOB statement is authorized. Use the name that you specified for either the SYSTEM ADMIN 1 option or the SYSTEM ADMIN 2 option on installation panel DSNTIPP1. (The RESTART parameter on the JOB statement can be useful.) Correct any other problems, and run job DSNTIJSG again.
  6. If you encounter resource shortages, review the parameters in job DSNTIJUZ and make any necessary modifications. Then, stop Db2, rerun DSNTIJUZ, start Db2, and rerun DSNTIJSG from the last successful step.

What to do next

Complete the following actions:
  • Alter your Db2 12 buffer pools that have frequent page reads or frequent page writes to use PGFIX YES if you have sufficient real storage available for these buffer pools. Fixing the buffer pages in real storage once and keeping them fixed avoids the processing time that Db2 needs to fix and free pages each time there is an I/O. In some cases, this processing time can be as much as 10% for I/O-intensive workloads. To use this option, issue the following command:
    Begin general-use programming interface information.
    ALTER BPOOL(bpname) VPSIZE(vpsize) PGFIX(YES)
    End general-use programming interface information.

    Where bpname is the name of the buffer pool and vpsize is the size of the virtual pool.

  • Start of changeIf you use capabilities such as ODBC, JDBC, and others with Db2, you might need to run other jobs to migrate them for use with Db2 12, for example: End of change