Download PDF - IBM Redbooks

4.2.4 Considerations for data sharing
With DB2 for z/OS, you can perform the DB2 10 migration completely online if systems are
configured in a data sharing environment. For details about the process and example
scenarios, see the sdn best practice document “Migrating SAP systems to DB2 10 for z/OS”
at:
http://service.sap.com/~sapidb/011000358700001414122010E
During the process, the subsystems of the data sharing group operate on different release
levels. For monitoring and operations, consider the following recommendations:
► At most, have one Alert router instance running to run on the member with the lowest
release in the group.
► If you want to perform monitoring, use the DBA Cockpit on an application server
connected to the member with the lowest release.
► Prepare the startup JCL jobs for the application environments used by the ADMIN stored
procedures as explained in “Mixed releases in a data sharing group” in DB2 10 for z/OS
Data Sharing: Planning and Administration, SC19-2973-03. With this setup, you can
match the DB2 load module with the DBM1 code level of the respective member to allow
calls to WLM-managed stored procedures at any time.
► Ensure that no support package updates and transports run into the system during these
phases.
4.2.5 After the migration
After you successfully enter DB2 10 NFM, you must perform several steps to adapt the
installation to the new features and naming standards.
Rebinding packages and subsystem parameter EDMPOOL
As explained in 3.1.3, “Virtual storage constraint relief for DB2 10: Larger number of threads”
on page 31, the EDM pool is moved above the bar in DB2 10. However, this change takes
effect only after the packages are rebound. To perform the rebind for the CLI packages, use
the following statement:
db2radm -m db2i -B force
To rebind SAPCL, see “Adapting the SAPCL installation” on page 73.
To ensure that all packages are rebound, check the timestamp of the last bind with the
statement shown in Example 4-3.
Example 4-3 Checking bind timestamps
SELECT NAME, BINDTIME FROM SYSIBM.SYSPACKAGE ORDER BY TIMESTAMP.
Before DB2 10, the EDMPOOL subsystem parameter controlled the overall storage allocated for
the EDM pool. With DB2 10, this parameter no longer determines a fixed storage size, but
constrains the maximum size of the EDM pool storage below the bar. SAP has not yet
changes the recommendation for the EDMPOOL parameter for customers who have not yet
done a rebind. When all packages are rebound, you can change this parameter to the DB2 10
installation default of 0 (zero). However, because the storage is not allocated if it is not used
with DB2 10, you can retain the SAP recommended setting.
72 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System