Setup for Remote Monitoring and

Administration of DB2 for z/OS

Applies to:
This article applies to all SAP products based on the SAP NetWeaver 7.0 application server ABAP and
higher. This includes also all Enhancement Packages for SAP NetWeaver 7.0 and higher.

Summary
This document describes the prerequisites and steps for setting up the monitoring and administration of
remote DB2 for z/OS subsystems.
Authors:

Dr. Matthias Gimbel, Senior Developer, SAP AG, Germany

Dirk Nakott, Software Engineer, IBM Deutschland Research & Development GmbH

Created on: 28. July 2009

Author Biographies
Matthias Gimbel works as a team lead for SAP monitoring and administration on System z in the
SAP Lab in Rot. He studied Computer Science at the University of Karlsruhe and earned his
PhD in the area of Parallel Database Systems in 2004. He joined SAP in 2005 and worked in the
BW area before taking over responsibility for monitoring. Matthias can be reached at
matthias.gimbel@sap.com.

Dirk Nakott divides his time between the IBM Bblingen Lab and the SAP Lab in Rot and works
on all aspects of SAP monitoring and administration (CCMS) of DB2 for z/OS. He studied
Computer Science at the University of Stuttgart and joined IBM in 1998. Prior to IBM, he worked
five years in computing and development centers of other companies in the database area. Dirk
can be reached at nakott@de.ibm.com.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

1

Setup for Remote Monitoring and Administration of DB2 for z/OS

Table of Contents
Definitions and Prerequisites .............................................................................................................................. 3
General Setup ..................................................................................................................................................... 3
Bind Call Level Interface (CLI) with db2radm ................................................................................................. 3
Define a Remote Connection in DBACOCKPIT ............................................................................................. 4
Define a Remote System in DBACOCKPIT .................................................................................................... 7
Monitoring Setup ................................................................................................................................................. 9
Job Control Language (JCL) Settings ............................................................................................................. 9
SAP Collector Settings .................................................................................................................................. 10
Administration ................................................................................................................................................... 11
Activate Alert Data Collection (DSNACCOR) ............................................................................................... 11
DB13 Planning Calendar............................................................................................................................... 12
Use of Remote Connections ............................................................................................................................. 12
General ......................................................................................................................................................... 12
Monitoring ..................................................................................................................................................... 12
Administration with DB13 Jobs ..................................................................................................................... 13
SAP Alert Router ........................................................................................................................................... 14
High Availability of Remote Connections ...................................................................................................... 14
Appendix ........................................................................................................................................................... 15
List of Tables Used for Monitoring and Administration ................................................................................. 15
Copyright........................................................................................................................................................... 16

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

2

Setup for Remote Monitoring and Administration of DB2 for z/OS

Definitions and Prerequisites

In the subsequent chapters, we will use the following terminology:

The term subsystem refers to a DB2 database subsystem, whereas system stands for an SAP
System.

There are two different types of systems: The monitoring system and the monitored system.
The monitoring system is the one used to display the monitoring results, and to schedule and run
administration jobs. It must be an SAP product based on SAP NetWeaver 7.0 application server
ABAP or higher. It needs to have the support package level listed in SAP note 1229346. In addition
to this, we recommend having the support package level listed in SAP note 1310148.
The monitored system can be any SAP product running on a DB2 for z/OS database subsystem. It is
also referred to as remote system.

The following procedure describes the steps to be performed in the monitoring system. The SAP product
installed in the monitored subsystem does not need to be touched.

General Setup
Bind Call Level Interface (CLI) with db2radm
Note: This step is only necessary if CLI is not already bound in the monitored DB2 subsystem (for example,
for SAP Java installations).
If you want to access the monitored subsystem remotely through a DB2 Connect gateway (fat client) and, in
parallel, through the IBM DB2 Driver for ODBC and CLI (thin client), call db2radm from a system using the fat
client. If db2radm is called from a thin client, fewer packages will be bound.
Use the following db2radm command:
db2radm -m
-C
-H
-P
-L
-S
-U
-Q
-u
-p
-B
-G
-W

db2i
<collection>
<DB2 host>
<DB2 port>
<DDF location>
<Subsystem name>
<Connect User>
<SAP schema>
<DB2 sysadm user>
<DB2 sysadm password>
force
only
secondary_only

You can choose the collection name as you like. However, the following naming convention is
recommended:
SAP<DB2 Connect Release><U>

If the SAP installation is a Unicode installation, use U at the end.

Example 1: SAP non-Unicode installation with DB2 V8.1
SAP0801

Example 2: SAP Unicode installation with DB2 V9.1

SAP0901U

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

3

Setup for Remote Monitoring and Administration of DB2 for z/OS

Define a Remote Connection in DBACOCKPIT

Start transaction DBACOCKPIT in the monitoring SAP system and select DB Connections.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

4

Setup for Remote Monitoring and Administration of DB2 for z/OS

Select Add to insert a new database connection.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

5

Setup for Remote Monitoring and Administration of DB2 for z/OS

Select DB2 for z/OS as the database system and enter values into the required fields.
Note: The connection name must not start with CCMS_DB2_. The DB2 location must be entered in the field
labeled Database Name.

Save and Test the connection.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

6

Setup for Remote Monitoring and Administration of DB2 for z/OS

Define a Remote System in DBACOCKPIT

Start DBACOCKPIT and press System Configuration to define the remote SAP system.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

7

Setup for Remote Monitoring and Administration of DB2 for z/OS

Select Add to insert the new system. Enter the required fields.

In the field System you can enter the same name as the previously defined database connection. If the
remote system is a BW system, you also need to define the RFC destination in addition to the database
connection. This is necessary for the RUNSTATS jobs (transaction DB13).
Select Save and change to the new defined system. This can take a couple of seconds because the
DBACOCKPIT requires a set of tables that is created automatically in the remote system.
The creator (schema) of all tables is the schema name which has been defined for the remote connection.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

8

Setup for Remote Monitoring and Administration of DB2 for z/OS

Monitoring Setup
Job Control Language (JCL) Settings
The jobs that need to be submitted in order to set up monitoring require a minimum number of settings.
Select Configuration and JCL Settings in the DBACOCKPIT navigation tree. Press Profile to define the
profile settings. The profile settings are stored in the remote system in table DB2JOB.
Enter values for the marked fields on the General tabstrip.

Press Save and return to the previous screen. Select the Password button to set the password for the stored
procedure user you entered in the General tabstrip. The password is encrypted and stored in the monitoring
system.
Leave this screen to return to the navigation tree.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

9

Setup for Remote Monitoring and Administration of DB2 for z/OS

SAP Collector Settings

The SAP Collector (SAPCL) is a stored procedure. It collects performance data from the DB2 subsystem. To
make SAPCL accessible for DB2, you must store the SAPCL files in the HFS and then link them into the
DB2 load libraries. In addition, the SAPCL tables need to be defined and the access privileges granted. All
this can be done using buttons Step 1 to Step 6.
Restart transaction DBACOCKPIT and change to the remote system. This is necessary because the JCL
settings from the previous section are not active without restarting the DBACOCKPIT.
Select Configuration and SAP Collector Settings in the navigation tree. The fields are supplied with default
values. Check the values and make changes where necessary. Ensure that the SAPCL files sapdb2cl and
DBRM.db2cldb are located in the specified HFS path.

Press the buttons Step 1 to Step 6 in ascending order.

For further information on SAPCL, required permissions, and configuration options, refer to the SAP
Database Administration Guide for DB2 for z/OS, Chapter Monitoring and Performance.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

10

Setup for Remote Monitoring and Administration of DB2 for z/OS

Administration
Activate Alert Data Collection (DSNACCOR)
The DB2 stored procedure DSNACCOR is used for collecting data for tablespaces and index spaces that
require RUNSTATS, REORG, or COPY. The DB13 jobs RUNSTATS on obj. needing new statistics, Online
reorg on suggested tablespaces, Online reorg on suggested indexes, and Backup of suggested object are
based upon the results of DSNACCOR.
Switch on Collect Alert Data in the system configuration on one of the monitoring systems and save the
changed configuration.

In order to activate the alert collection, make sure that the Control Center stored procedures are completely
installed, as described in the chapter Stored Procedure Enablement of the SAP Database Administration
Guide for DB2 for z/OS.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

11

Setup for Remote Monitoring and Administration of DB2 for z/OS

DB13 Planning Calendar

DB13 provides a number of different administration jobs.
With the Support Package level listed in SAP note 1229346, the following jobs are supported:
Backup of suggested objects
RUNSTATS on obj. needing new statistics
Rebuilding of one SAP index
Update statistics for all SAP objects
Update statistics for one SAP object
With Support Package level listed in SAP note 1310148 and 1362838, the following jobs are supported:
Backup System at DB2 System Level
Backup for all SAP tablespaces
Backup of suggested objects
Increm. backup for all SAP tablespaces
Online reorg of one SAP index
Online reorg of one SAP tablespace
Online reorg on suggested indexes
Online reorg on suggested tablespaces
RUNSTATS on obj. needing new statistics
Rebuilding of one SAP index
Update statistics for all SAP objects
Update statistics for one SAP object

Use of Remote Connections

General
This section discusses the need for multiple remote connections to a monitored system. If multiple
connections are required, this implies that for each remote connection a remote system has to be defined.
For details, refer to the section General Setup.
Monitoring
For remote monitoring, you must define one remote connection to the monitored system. This applies to SAP
ABAP systems, to SAP Java systems, and to SAP double stack systems. It also applies to DB2 data sharing
systems. If the monitored system contains a schema that belongs to an ABAP system, we recommend using
this schema in the definition of the remote connection.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

12

Setup for Remote Monitoring and Administration of DB2 for z/OS

Administration with DB13 Jobs

Depending on the SAP installation, it may be necessary to define one or two remote connections to the
monitored system. This is irrespective of the number of DB2 data sharing members. The table below
illustrates this:
Monitored
SAP ABAP system

Monitored
SAP Java system

Monitored
SAP double stack system

Remote connection
to ABAP schema

Remote connection
to Java schema

Remote connection
to ABAP schema

Backup System at
DB2 System Level

Backup for all SAP

tablespaces

Backup of
suggested objects

Increm. backup for

all SAP
tablespaces

Online reorg of one

SAP index

Online reorg of one

SAP tablespace

Online reorg on
suggested indexes

X1

Online reorg on
suggested
tablespaces

X1

RUNSTATS on obj.
needing new
statistics

X1

Rebuilding of one
SAP index

Update statistics
for all SAP objects

X1

Update statistics
for one SAP object

DB13 job

Remote connection
to Java schema

see OSS note 1278135

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

13

Setup for Remote Monitoring and Administration of DB2 for z/OS

SAP Alert Router

Starting, checking, and stopping the Alert Router requires a direct connection to the subsystem on which the
Alert Router runs. Hence, if DB2 data sharing is used, the definition of a remote connection is necessary to
start and stop the SAP Alert Router for each DB2 data sharing member from the monitoring system.
Note: This behavior is different from the local case. For local data sharing, the monitoring system
automatically generates connections with the naming convention CCMS_DB2_<SSID> to all members of the
data sharing group. Therefore, this name prefix is reserved for such connections and must not be used for
manually created connections.
High Availability of Remote Connections
Today, remote connections (also known as secondary connections) are not high available. If the host or the
DB2 subsystem that has been defined in the DBACOCKPIT (DB connections) is not available, the remote
connection cannot connect. In this case, the action requiring the remote connection fails. The mechanism for
primary connections using connect.ini does not apply to secondary connections.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

14

Setup for Remote Monitoring and Administration of DB2 for z/OS

Appendix
List of Tables Used for Monitoring and Administration
Here is a list of the tables that are created at the remote system:
Table Name

DB2CCMO_IN1

DB2CCMO_IN2

DB2CCMO_PARMS

DB2CCMO_OUTTS

DB2CCMO_ERROR

DB2CCMO_OBJERR

DB2UTILS_PARMS

DB2UTILS_OUT

DB2JOB

DB2MISC

DB2CCDAILY

DB2CCHOUR

DBSTATC

DB2REOTS

DB2REOIX

DB2NORUN

DB2ALERTSLIMITS

DB2TREORG

SAP COMMUNITY NETWORK

2009 SAP AG

Function
For calling the stored procedure DSNACCMO and
for storing the results of DSNACCMO

For calling the stored procedure DSNUTILS and for

storing the results of DSNUTILS

For storing DB2J profile parameters

For storing the results of the stored procedure

DSNACCOR

Filled with data from DB2CCDAILY and used from

DB13 jobs RUNSTATS on obj. needing new
statistics, Online reorg on suggested tablespaces,
Online reorg on suggested indexes

Used by DB13 jobs

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

15

Setup for Remote Monitoring and Administration of DB2 for z/OS

Copyright
2009 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,
zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,
Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of
IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All
other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may
result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and
does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.
Any software coding and/or code lines/strings (Code) included in this documentation are only examples and are not intended to be
used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of
certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors
or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

SAP COMMUNITY NETWORK

2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

16