Basis Errors and Solutions

Symptom

REORG jobs in transaction DB13 alter the primary and secondary space allocation, if the number of extents is greater than four. In addition, REORG and COPY jobs in DB13 are not enabled for remote maintenance.

Other terms

DB2, CCMS, DB13, z/OS, OS/390, DB13, DSNACCMR, PRIQTY, SECQTY, Backup

Reason and Prerequisites

Program deficiencies

Solution

The following changes have been made:
Altering allocation quantities:
In the past, REORG jobs in DB13 did a check regarding the number of extents. If an object consisted of more than four extents, an ALTER…PRIQTY…SECQTY command was issued before calling the REORG command. The ALTER command is not executed anymore. Starting with DB2 Version 8, DB2 can handle the extent sizes by its own, if the ZPARM MGEXTSZ is turned on. Turning on MGEXTSZ is highly recommended.
Setting PRIQTY and SECQTY to -1:
It is recommended to ALTER the primary and secondary quantity to -1. This can be done by using report: RSDB2_ADJUST_QUANTITIES. It is recommended to set DB2 ZPARM TSQTY and IXQTY to the value 144. For more information on DB2 ZPARMS, refer to the SAP DBA Guide.
Extent limit and DSNACCOR:
The stored procedure DSNACCOR has one input parameter called ‘Extent Limit’. DSNACCOR recommends table spaces and indexes for reorganizations, if the number of extents of the object exceeds the extent limit. You can configure the extent limit via DBACOCKPIT -> Configuration -> DB Alert Settings -> field ‘Extent Limit’. It is recommended to set the value to 254, because performance tests have shown, that the number of extents is no performance issue and a large number of extents should not be used for recommending a reorganization.
DB13 job ‘DB02 Refresh’ versus RTS:
The DB13 jobs for REORG, COPY and RUNSTATS need to know the sizes of table spaces and indexes to calculate the correct size for output, sort and work data sets. In the past, the object sizes have been retrieved from SAP cluster table MONI, which is filled up by the DB13 job ‘DB02 Refresh’.
This has changed for the DB13 jobs and the object sizes will now be retrieved from DB2 Real Time Statistics (RTS). Transaction DB02 continues using the data in SAP cluster table MONI.
DB13 job templates:
This support package changes the DB13 job templates. The templates to generate JCL jobs and the templates to call DB2 Utilities via DSNUTILS/DSNACCMO are affected. To benefit from the changes, unprotect the DB13 job templates in transaction DB2J. This can be done by selecting ‘Allow SAP to update utility statement skeletons’ in DB2J -> Profile -> tab General.
Volume Count:
‘VOLCNT(99)’ has been changed to ‘VOLCNT($VOLCNT)’. The value for $VOLCNT can be set in DB2J -> Profile -> tab ‘Storage’ -> field ‘Volume Count’.
Change limit:
‘CHANGELIMIT(030)’ has been changed to ‘CHANGELIMIT($CLIM)’. The value for $CLIM can be set in DB2J -> Profile -> tab ‘COPY’ -> field ‘CHANGELIMIT’.
Maximum allocation quantity:
‘MAXPRIMA 2900′ has been changed into ‘MAXPRIMA $MAXPRIMA’. The value for $MAXPRIMA can be set in DB2J -> Profile -> tab ‘Storage’ -> field ‘Max. alloc. quantity (MAXPRIME)’. This is new in DB2J. The default is 2900 cylinder.
Default allocation quantity:
There are two new fields in DB2J -> Profile -> tab ‘Storage’ called ‘Default primary quantity’ and ‘Default secondary quantity’. These values are used, if DB13 can not determine the size of an object from DB2 RTS. By default, ‘Default primary quantity’ is set to 5 MB and ‘Default secondary quantity’ to 320 MB. Please adapt these values according to your needs.
Backup of DB13 job templates:
Before changing the templates, the old templates will be copied from creator ‘SAPR3′ to creator ‘SAPR3_BACKUP’. This is helpful, if the templates were changed by the customer. You can use the following SQL statement to display the differences.
select s.jobname, s.cardno, s.creator, b.creator, s.jobcard, b.jobcard
from db2job s, db2job b
where s.jobname = b.jobname
and s.creator = ‘SAPR3′
and b.creator = ‘SAPR3_BACKUP’
and s.type = b.type
and s.cardno = b.cardno
and s.jobcard <> b.jobcard;
Remote maintenance support:
The following DB13 jobs are now enabled for remote maintenance and can be executed and scheduled from the DB13 action pad:
Backup for all SAP tablespacesBackup of suggested objectsIncrem. backup for all SAP tablespacesOnline reorg of one SAP indexOnline reorg of one SAP tablespaceOnline reorg on suggested indexesOnline reorg on suggested tablespacesRUNSTATS on obj. needing new statisticsRebuilding of one SAP indexUpdate statistics for all SAP objectsUpdate statistics for one SAP objectCentral Calendar Log Collector

Availability:
Import one of the following Support Packages:
SAP Basis 7.00 Support Package 20SAP Basis 7.01 Support Package 5SAP Basis 7.02 Support Package 2SAP Basis 7.10 Support Package 9SAP Basis 7.11 Support Package 4