How to convert from DB2 v8 Compatibility Mode (CM) to New Function Mode (NFM).

Document ID : KB000054705
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Converting PANSQL/Easytrieve DB2 v8 Compatibility Mode (CM) to New Function Mode (NFM).

Solution:

Client's should decide what they want/need before starting. ex. NFM, COMP, DB2 versions.
The main thing is, the new replaces the old and the new is not compatible with the old. The way it used to work doesn't work anymore.
It is important to not wipe out the old plan with the new, unless you are are positive that's what you want to do.
Remember that each Pan/SQL cailib has its own plan and each plan needs its own cailib.

To upgrade one independent system:
Change NEWFUN (NO) to NEWFUN(YES) in IJ3STGE1
//************************************************************** 
//* 
//* STEP 3: DB2COMP 
//* - PREPROCESS THE INTERFACE COMMAND PROCESSOR 
//* 
//* NOTE - THIS STEP COMPLETES WITH A CONDITION CODE OF 4 
//* 
//************************************************************** 
//DB2COMP EXEC PGM=DSNHPC,PARM='HOST(ASM),XREF,SOURCE,NEWFUN(YES)' <<< here

Run IJ3STGE1 and CB2ACMDL.

If you have multiple subsystems and want to upgrade all of them now and do not need to access the old one, run SQLINST4 at this point.
One Pan/SQL install is needed for each version of DB2 (v7, v8 CM, v8 NFM). The planname will need to be changed in the CAIMAC (OMSMCMD2) for each installation.

If are using a linklist, apply Easytrieve apar QO90560 for 6.4/SP3 for r11.
QO90560 is optional if not using a linklist. It is recommended to all customers as an upgrade enhancement.
It may cut down on the number of reported -818's. It is also more transparent to the user.

Also, have them put on these 3 apars if they don't have them on already.

*0203* -302 AND/OR NAMES >18 CHARS NOT RECOGNIZED - QO93564
*0203* OVERLAY OF FIELD BEFORE SET CURRENT :HOSTVA - QO81778
*0203* LOOP OR S0C4 IN STATIC PROGRAM (V7 & ABOVE - QO81095