Download PDF - IBM Redbooks

You must make the following changes:
► If you want to switch to the new environments delivered with DB2 10, enter the new
environment name in the WLM application environment field. Then, click the 1. Step:
Create stored procedure button to recreate the SAPCL stored procedure.
► If SAPCL is linked into the DB2 load library, repeat the link-edit step after the release
migration. Enter the name of the new load library in the DB2 load library for link-edit field.
Then click the 2. Step: Link-edit SAPCL button.
► To move the package above the bar, click the 3. Step: Bind DBRM button to perform a
rebind.
► To regrant the privileges after the recreation, click the 5. Step: Grant usage privileges
button. Then to convert the collector tables to the DB2 10 format, click 6. Step: Create
tables button.
Adapting the scheduling settings in the SAP Collector Profile
The SAP Alert Router can collect information regularly at fixed intervals for the following
information:
► Global Times
► DBM1 Storage Overview
► Statement Cache History
► DB02 Space History
The intervals for the collection of Global Times, DBM1, and Statement Cache History are
based on the IFCID 225 externalization interval. This interval was controlled by the DB2
installation parameter STATIME before DB2 10. Within the SAP Collector profile, it was
possible to enter multiples of STATIME to configure the frequency of the collection.
With DB2 10, the interval for IFCID 225 is changed to fixed one-minute intervals. You must
specify the configuration in the DBA Cockpit in minutes. Figure 4-11 on page 75 shows the
modified Collector Profile panel for DB2 10.
Interval for history collection: Because the constraint on DBM1 Storage is relieved in
DB2 10, reassess the interval setting for DBM1 storage history collection.
74 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System