Migrating from enabling-new-function mode (from Version 8 or Version 9) to new-function mode

New-function mode can be activated any time after enabling-new-function mode (from Version 8 or Version 9) processing is complete.

About this task

When the DB2® subsystem is in new-function mode, all DB2 10 function is available for use. Start of change From new-function mode, you cannot fall back to your previous version (Version 8 or Version 9.1) or return to conversion mode from Version 8, enabling-new-function mode from Version 8, conversion mode from Version 9, or enabling-new-function mode from Version 9. A DB2 subsystem in DB2 10 enabling-new-function mode (from Version 8 or Version 9) or DB2 10 new-function mode cannot coexist with a Version 8 or Version 9.1 subsystem. End of change

Procedure

To migrate from enabling-new-function mode (from Version 8 or Version 9) to new-function mode:

Run job DSNTIJNF. New-function mode begins after job DSNTIJNF completes successfully.
Optional: Check for consistency between catalog tables by running the queries in member DSNTESQ of prefix.SDSNSAMP.
Optional: Stop DB2 10.
After job DSNTIJNF completes successfully, run job DSNTIJNG. Job DSNTIJNG modifies the application defaults load module, dsnhdecp, to allow the DB2 precompiler to accept DB2 10 new-function SQL statements by default.
If you stopped DB2 before you ran job DSNTIJNG, start DB2 10.
If you migrated from Version 8, run job DSNTIJNX to bind the packages for SPUFI to enable XML support in new-function mode.
Run job DSNTIJRT. Job DSNTIJRT executes DSNTRIN, which installs and customizes all DB2-supplied routines and supporting objects that were deferred until new-function mode. This job was customized when the CLIST was run in MIGRATE mode.
Run job DSNTIJRV. Job DSNTIJRV validates all DB2-supplied routines and augments existing installation verification procedures (IVPs) for specific DB2-supplied routines. It also provides a report that identifies successful validations, warnings, and failures. This job was customized when the CLIST was run in MIGRATE mode.
If you used the SYSPROC.XSR_COMPLETE stored procedure during conversion mode from Version 9, then update the WLM environment that you use for running XSR_COMPLETE to use DB2 10 class paths:
1. Edit the Java Language Environment® (JAVAENV) data set for the WLM environment by adding the following parameter to the environment variable (ENVAR) list. Change the file and path names to the name of the environment variable that was created when you ran job DSNTIJMV, job step DSNTIJR:
```
"_CEE_ENVFILE=/usr/lpp/db2/db2a10_base/classes/!dsn!envfile.txt",
```
2. Refresh the WLM environment that you use for running XSR_COMPLETE.

What to do next

Recommendations:

In new-function mode, specify NEWFUN=V10 in your application defaults module. In a data-sharing environment, if you use more than one application defaults module, modify and run the jobs that you use to maintain these modules to specify NEWFUN=V10.
Alter your DB2 10 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 for each 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:
```
ALTER BPOOL(bpname) VPSIZE(vpsize) PGFIX(YES)
```
Where bpname is the name of the buffer pool and vpsize is the size of the virtual pool.
If you installed or migrated QMF™ before migrating the DB2 subsystem, you must rerun some QMF jobs to ensure continued proper operation of QMF. For more information, see Tasks to perform when you upgrade DB2 for z/OS® after you install QMF.