Migration step 13: Define DB2 10 to z/OS: DSNTIJMV

Job DSNTIJMV completes some of the steps that are required to identify DB2® to z/OS®, including updating members of SYS1.PARMLIB and SYS1.PROCLIB.

Start of change

Before you begin

Ensure that you completed the task in Make DB2 load modules available to TSO and batch users.End of change

About this task

Start of changeDSNTIJMV renames your Version 8 or DB2 9 procedures so that they do not conflict with DB2 10 procedures, which replace your old procedures.End of changeStart of change The job also creates Language Environment® options data sets for the DB2 core WLM environment for Java routines.End of change

Procedure

To define DB2 10 to z/OS:

  1. Run job DSNTIJMV. If job DSNTIJMV runs successfully, it produces return codes of 0. Because a rename can fail without setting the return code, verify all renames.
  2. Start of changeReview the content of the Language Environment options data set and adjust the following environment variables as needed. The data set is created by DSNTIJMV and must be allocated by the JAVAENV DD of the address space procedure for the DB2 core WLM environment for Java routines.
    • _CEE_ENVFILE, if present, needs to be set to the name and path of the environment variable file that was created by job step DSNTIJR.
    • JVMPROPS needs to be set to the name and path of the JVM startup options file that was created by job step DSNTIJS.
    • DB2_BASE and JCC_HOME need to be set to the names of the HFS directories that you selected for the DB2 for z/OS and JCC product classes.
    End of change
  3. Start of change
    Begin DB2 9 to DB2 10 migration information
    If you are migrating from DB2 9, review the content of the environment variable file that was created by job step DSNTIJR. Adjust the following information as needed:
    • Start of changeCLASSPATH needs to specify the path for the Java class that contains the JAR files for z/OS XML System Services XML schema registration (/usr/include/java_classes). CLASSPATH cannot specify gxljapi.jar or gxljosrglmpl.jarEnd of change
    • LIBPATH needs to specify the path for the native library for z/OS XML System Services (libGXLNVBAT.so).
    • STEPLIB needs to specify the name of the DB2 for z/OS run time library.
    End DB2 9 migration information
    End of change

What to do next

Because different sites have different requirements for identifying DB2 to z/OS, DSNTIJMV cannot anticipate all the necessary updates. For this reason, the updates that job DSNTIJMV makes in SYS1.PARMLIB and SYS1.PROCLIB are incomplete. You might have additional procedures of your own to rename, or you might have to provide procedures for both releases, using alias names to indicate the current release. If you changed the DB2 subsystem name, the names of the DB2 address space startup procedures also change. If you made any changes to your Version 8 or DB2 9 procedures (such as data set names), make similar changes to the DB2 10 procedures. You can complete these updates either by making the updates directly in SYS1.PARMLIB and SYS1.PROCLIB or by editing DSNTIJMV.

Recommendation: For SYS1.PROCLIB, submit the procedure-update section of DSNTIJMV as necessary. However, before you make the updates, read the information about DSNTIJMV, and examine DSNTIJMV to study the updates that it makes. Edit the updates directly in SYS1.PARMLIB instead of submitting the updates in the DSNTIJMV job.

Before starting DB2, check the private area sizes in the SYS1.PROCLIB update section to ensure that you have enough user private area.

Also, examine the size of the private area on the DB2 startup procedures. If necessary, modify them to satisfy the requirements for EDM pool size, buffers, numbers of open data sets, and the amount of available private address space.

Start of change

Begin DB2 9 to DB2 10 migration information
If you are migrating from DB2 9, the installation CLIST removes the _CEE_ENVFILE environment variable from the Language Environment options data set. This action allows the data set to maintain compatibility with the DB2 9 run time environment for the SYSPROC.XSR_COMPLETE stored procedure. After you migrate to new-function mode, you must add the _CEE_ENVFILE environment variable as part of enabling the DB2 10 run time environment, as explained in Migrating from enabling-new-function mode (from Version 8 or Version 9) to new-function mode
End DB2 9 migration information
End of change