16.The recommendation is to develop a DB2 system libraries configuration that allows each DB2 subsystem to be migrated to a new level of DB2, or DB2 maintenance, individually. For instance, if this is a DB2 data sharing group, you want to migrate members one at a time. The system libraries include SDSNLOAD, SDSNEXIT, SDSNMACS, SDSNSPFP, etc. The RUNLIB.LOAD, DBRMLIB.DATA and SRCLIB. DATA libraries are groups level libraries and are changed when the first data sharing member is migrated to a new DB2 version or maintenance level.
This can be accomplished two ways:
1.Each DB2 subsystem, or data sharing member has their own set of system libraries, and when maintenance, or migration to a new level of DB2 takes place.the new SMP/E libraries are copied into the system libraries of the DB2 subsystem being updated.
2.Maintain a N and a N+1 copy of the system libraries. In this case, the PROCs for the DB2 subsystem that is being updated would be changed to point to the N+1 level of system libraries. You would still maintain separate SDSNEXIT libraries for each subsystem or data sharing member.
17.Review DB2 virtual storage considerations in Chapter 5 of the SAP Database Administration Guide for SAP NetWeaver on IBM DB2 UDB for z/OS. It is important to folow the guidelines on estimating the use of virtual storage below the 2GB bar because in DB2 V8 there are memory structures that exist below this bar. For DB2 9 the procedure for estimating virtual storage requirements nelow the 2GB bar is described in the document ‘SAP on IBM DB2 for z/OS: Best Practice for Installing or Migrating to DB2 9’.
18.For Online Reorg use normal SHRLEVEL CHANGE parameters plus the following:
MAXRO 10 | (maximum time for last iteration) |
TIMEOUT TERM | (if utility times out then terminate) |
DRAIN ALL | (readers and writers during final phase , prevents deadlocks) |
LONGLOG DRAIN DELAY 0
DRAIN_WAIT 120
RETRY 10
RETRY_DELAY 120
Copyright 2006 IBM Solutions Technical Sales (STS) | 12/18/2007Page 22 of 51 |
12/18/2007 |
|
