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.
Before you begin
About this task
Procedure
To define DB2 10 to z/OS:
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.
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.
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