IBM DB2 V8, DB2 9 User Manual

Planning And Preparation Guide For SAP NetWeaver

7.0: z/OS Implementation:

DB2 V8 DB2 9

Albert D. Rodi

Consulting IT Specialist IBM Solution Technical Sales International Business Machines Corporation 1503 LBJ Freeway Dallas, TX 75234 (972) 280-4791 or TieLine 8-542-4791 E-mail: adrodi@us.ibm.com

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 1 of 51

Trademarks

The following are trademarks of the International Business Machines Corporation in the United States and/or other countries

AIX* On Demand Business Logo

CICS* PR/SM DB2* Parallel Sysplex* DB2 Universal Database pSeries* e-business logo System z9 Enterprise Storage Server* System z GDPS* Tivoli* Geographically Dispersed Parallel Sysplex xSeries* HiperSockets z/Architecture IBM* z/OS* IBM eServer z/VM* IBM logo* zSeries* IMS

* Registered trademarks of IBM Corporation

Intel is a registered trademark of the Intel Corporation in the United States, other countries or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation. SET and Secure Electronic Transaction are trademarks owned by SET Secure Electronic Transaction LLC. SAP is a registered trademark of SAP AG, Walldorf , Germany * All other products may be trademarks or registered trademarks of their respective companies.

Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 2 of 51

Contents

I General Preparation Steps II z/OS Hardware Preparation III AIX Hardware Preparation IV z/OS Software Preparation V DB2 and DB2 Connect Preparation VI DB2 Related OSS Notes VII AIX Software Preparation VIII Windows NT Hardware/Software Preparation IX SAP Installation Preparation X Sample BPXPARMxx Member XI Sample DB2 DSNZPARMS XII TCP/IP Connectivity XIII Naming Conventions XIV Application Server On z/OS Considerations XV Sample OSA-Express GB Configuration XVI DB2 Backup/Recovery Notes XVII SAP Automation And High Availability Solution XVIII SAP Application Server On zLinux Considerations XIX Sample SMS Storage Group Assignments

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 3 of 51

What is new with SAP Web Application Server 7.0 ?

• The z/OS USS Application Server is no longer supported. However you can install the Central Services on USS as part of a High Availability solution.

• rfcoscol is replaced by sapccmsr and SAPCL

 Transaction ST04 allows monitoring of remote DB2 subsystems  The mass processing tool to convert indexes to NOT PADDED is available

(Transaction DB2_IXFIX)

 Modifications have been made to the PTF Checker Tool  New DBA Cockpit Monitoring Tool in Basis Support Package 12  DB2 9 certified July 2007

What is new with SAP Web Application Server 6.40 ?

• DB2 Version 8 is required for the SAP Web AS Release 6.40. Many new features of DB2 V8 are exploited:

- Table controlled partitioning

- System level backup and recovery

- Automatic extent management

- Accounting and WLM exploitation

- Transaction level accounting and workload management

- IFI enhancements

- Index only access for VARCHAR

• Unicode is now supported.

• DB2 Connect is used to connect non-z/OS application servers to DB2 (enhancements

in the tool db2radm to setup DB2 Connect). ICLI is no longer used. For the Java stack, the DB2 JDBC Universal Driver is delivered with DB2 Connect and is used for connectivity.

• Stored procedures have replaced the usage of FTP for JCL job submission.

• New features in the planning calendar (transaction DB13)

- Exploitation of inline statistics and utilities TEMPLATE, MODIFY RECOVERY

and MODIFY STATISTICS

- Protection of changed utility skeletons possible

- New design

• Recommendations for DB2 V8 system parameters (ZPARMs).

 The SAP Solution Manager must be installed prior to any component installation.

This is used to generate a key used during the input phase of the installation.

General Preparation Steps

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 4 of 51

1. Identify the technical implementation team members: z/OS System Programmer zLinux Administrator

Security Administrator Unix System Services Administrator Storage Administrator

Network Administrator

AIX/Windows Administrator

DB2 DBA DB2 Systems Programmer R/3 Administrator

z/OS Capacity Planning & Performance Administrator

2. Available Documentation (SAP):

- SAP Planning Guide for SAP NetWeaver for IBM DB2 UDB for z/OS

- Component Installation Guide: SAP ERP 2005 ABAP+Java on AIX: IBM DB2 UDB for z/OS

- Component Installation Guide: SAP ERP 2005 ABAP+Java on Windows: IBM DB2 UDB for z/OS

- Component Installation Guide: SAP ERP 2005 ABAP+Java on Linux: IBM DB2 UDB for z/OS

- SAP ERP 2005 SR1 ASCS+SCS on z/OS: IBM DB2 UDB For z/OS: Installation Guide

- SAP Security Guide for IBM DB2 UDB for z/OS

- SAP Database Administration Guide for SAP NetWeaver on IBM DB2

UDB for z/OS

- Master Guide: SAP NetWeaver 2004s

- Technical Infrastructure Guide: SAP NetWeaver 2004s

- SAPinst Trouble Shooting Guide for SAP Web AS Java Installation

- SAP Enterpise Services Architecture and SAP NetWeaver on IBM zSeries : Technology Preview

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 5 of 51

- Installation of SAP Solution Manager

- Configuration of SAP Solution Manager

- Front End Installation

- Homogeneous and Heterogeneous System Copy for SAP Systems based on NetWeaver 2004s

3. Available Documentation (IBM):

- High Availability for SAP on zSeries Using Autonomic Computing Technologies (SC33- 8206)

- SAP on DB2 UDB for OS/390 and z/OS: Implementing Application Servers On Linux for zSeries (SG24- 6847)

- SAP on IBM DB2 UDB for OS/390 and z/OS: Best Practices for Installing or Migrating to DB2 V8 (websmp202.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000274486&)

- Tips for Installing DB2 Connect V8 on SAP with DB2 UDB for z/OS V8 (www.ibm.com/support/docview.wss?rs=64&uid=swg27005934)

- SAP on IBM DB2 UDB for z/OS: Best Practices for Installing or Migrating to DB2 9 (service.sap.com/SolutionManagerBP)

- Point-in-time recovery using DB2 V8 for z/OS RESTORE SYSTEM utility and SET LOG SUSPEND

- SAP on DB2 for z/OS and OS/390: High Availability and Performance Monitoring with Data Sharing (SG24-6950)

- SAP on DB2 UDB for OS/390 and z/OS: High Availability Solution Using System Automation (SG24- 6836)

- SAP R/3 on DB2 UDB for OS/390 and z/OS: Connectivity Guide

5th Edition (IBM SC33-7965-04)

- DB2 for z/OS and OS/390: Tools For Performance Management (IBM SG24-6508)

- DB2 for z/OS and OS/390 : Data Management Tools Update (IBM SG24- 6406)

- SAP on DB2 for z/OS and OS/390: DB2 System Cloning

IBM Solutions Technical Sales (STS) 12/18/2007Page 6 of 51

12/18/2007

(IBM SG24- 6287)

- DB2 UDB for z/OS V8: Through the Looking Glass and What SAP Found There (IBM SG24- 7088)

- Disaster Recovery with DB2 UDB for z/OS (SG24-6370)

- DB2 Performance Expert for z/OS (SG24- 6867)

- DB2 UDB for z/OS Version 8 Technical Preview (SG24- 6871)

- Distributed Functions of DB2 for z/OS and OS/390 (SG24- 6952)

- SAP on DB2 for z/OS: Multiple Components In One Database(MCOD) (SG24- 6914)

- DB2 for z/OS Version 8 : Everything You Ever Wanted to Know...and More (SG24-6079)

- DB2 9 for z/OS: Performance Topics (SG24-7473)

- Enhancing SAP by Using DB2 9 for z/OS (SG24-7239)

Note: SAP Manuals are available at:

service.sap.com/instguides service.sap.com/erp-inst service.sap.com/installNW2004s

IBM Manuals are available at:

www.s390.ibm.com/zos/bkserv

IBM Redbooks are available at:

www.redbooks.ibm.com

3. Plan and conduct a planning session/readiness review for the installation and migration (if migrating an existing SAP database).

4. Obtain the required hardware/software plus all necessary PTFs (OSS Note 81737).

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 7 of 51

5. Important OSS Notes: (service.sap.com/notes)

660528: Requirements to run SAP NetWeaver on zSeries 661260: Transports and Support Pac kages for 6.40 728743: zSeries: Release of DB2 V8 for SAP Components 746924: Planning information for customers with SAP on zSeries 606682: High availability and automation solution for Linux zSeries 563060: DB2/390: Configuring the AppServer on Linux for zSeries 731937: DB2-z/OS: Customizing DB2 Connect for WebAS 6.20 and DB2 V8 710466: Upgrade to 6.40 - OS Platforms not supported 183311: DB2/390: Automated PTF Check 427748: DB2-z/OS: CCMS corrections (6.10, 6.20, 6.40,7.00) 943145: DB2-z/OS: Transports and Support Packages for 7.0 943144: DB2-z/OS: Transports and Support Packages for 7.0 823245: DB2-z/OS: Transports and Support Packages for 7.0 858969: SAP NetWeaver 2004s Installation:IBM DB2 UDB for z/OS 81737: DB2/390: APAR List 146289: Parameter Recommendations for 64-Bit SAP Kernel 138906: DB2/390: Planning Info (release,connectivity matrix) 103135: DB2/390: Installing saposcol manually 682077: DB2-z/OS: Premigration checks for DB 35010: Service connections: Composite note (overview) 46902: Security aspects in remote access 44864: SAP Remote Services: Technical preparation 171356: SAP Software on Linux: Essential Comments 209384: CCMS Agent Technology 978817: DB2 for z/OS OEM Package 805390: SAP Solution Manager is required for SAP Software 407325: Released Operating Systems SAP Kernel 6.x/7.x 852008: Release restrictions for SAP NetWeaver 2004s 855498: Installation Prerequisite Checker 856272: SAP Software on UNIX - OS Dependencies NetWeaver 2004s 855297: SAP ERP 2005 Installation on UNIX 852235: Release restrictions for SAP ERP 2005 851251: SAP NetWeaver 2004s Installation on UNIX 811923: Generating the SAP Solution Manager Key 848950: SAP NetWeaver 2004s Installation on Windows 815202: DB2 for z/OS: Upgrade to SAP NW AS 7.0 611361: Configuring the App Server on Linux for zSeries 563060: SAP ERP Central Component 5.0 on UNIX 544623: New Installation of Unicode SAP Systems 73606: R/3 Language Combinations (non-Unicode) 35010: Service Connections:Composite Note 46902: Security aspects in remote access 33135: Guidelines for OSS1 31515: Service Connections

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 8 of 51

797084: SUSE Linux Enterprise Server 9: Installation Note 892818: Application servers on Linux for zSeries: Settings 821904: Separating SCS instances for ABAP and J2EE 686905: DB2 for z/OS: DDIC Corrections (6.40, 7.0) 818291: zSeries: Windows 64 bit app server 144864: SAP Remote Services: Technical preparation

6. Prepare a project plan for the implementation. The following architecture highlights should be addressed:

 Parallel Sysplex with DB2 Data Sharing Configuration  SAP Sysplex Failover Scenarios for High Availability  SAP High Availability Enqueue Instance (Central Services Instance)  SAP Application Server on zLinux  Network Connectivity  Database Backup/Recovery  Disaster Recovery

7. Prepare a migration plan for submission to SAP if necessary.

8. Setup OSS connection, FTP capability to SAP.

9. Order R/3 Developer Keys if necessary.

10. Generate Backup/Recovery Plan for z/OS, zLinux, AIX, Windows, and the SAP Database.

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 9 of 51

II z/OS Hardware Preparation

1. Review Checklist in Installation Manual and at service.sap.com/platforms for supported z/OS server models.

2. Determine Hardware Configuration by completing the SAP sizing questionnaire for R/3. Review the sizing deliverable document prepared by the IBM ISV TechLine Sizing Department in conjunction with your IBM Sales Team or implementation partner. Memory estimates will be provided as well. The questionnaire is available online at: http://www.ibm.com/erp/sizing or by request from eSizings@us.ibm.com.

3. Minimum DASD requirements for new installation are:

A. Non-Production (65) + (n) 3390-3 volumes

(60) 3390-3 volumes for SAP data (2) 3390-3 volumes for DB2 active logs (1) 3390-3 volume for DB2 catalog, directory, BSDS (2) 3390-3 volumes for DB2 DSNDB07 (n) 3390-3 volumes for z/OS datasets(LINKLIB, PROCLIB, etc.)

(5) 3390-3 volumes for each z/VM LPAR (RES, Spool, Paging)

B. Each additional Non-Production system (65) 3390-3 volumes

C. Production (13) + (n) 3390-3 volumes plus (x) volumes for SAP data

(6) 3390-3 volumes for DB2 active logs (3) 3390-3 volumes for DB2 catalog, directory, BSDS (4) - (15) 3390-3 volumes for DB2 DSNDB07 (x) 3390-3 volumes for SAP data (minimum 60 for installation) (n) 3390-3 volumes for z/OS datasets

(5) 3390-3 volumes for each z/VM LPAR (RES, Spool, Paging)

(plus additional volumes if DB2 logs are archived to DASD) (PAV implementation is highly recommended)

z/Linux Application Server for ECC 6.0 (NetWeaver 7.0):

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 10 of 51

1.2 GB (Temporary installation disk space) 2 x zLinux Guest Memory (Swap Space)

4.3 GB (temporary disk space for every Installation DVD to be copied locally for installation) 13GB (disk space for the SAP filesystems) 8-12GB (Linux) 200MB (CMS and the Linux boot disk)

4. Define a (400) track VTOC for each DASD volume that will contain DB2 data through ICKDSF DASD initialization. VVDS should be (180) tracks and the VTOC Index should be (50) tracks.Triple these values if the DASD geometry is 3390-9. For 3390-54 geometry use 8,000 tracks for the VTOC, 3600 tracks for the VVDS, and 1000 tracks for the VTOC Index.

5. ICF Catalog Size for DB2 datasets: (50) cylinders primary, (5) cylinders Secondary.

6. 15 MB JES Spool Space.

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 11 of 51

III AIX Hardware Preparation

1. Review Checklist in theComponent Installation Guide : SAP ERP 2005 ABAP+Java on AIX: IBM DB2 UDB for z/OS for base Hardware Requirements .

2. Determine Hardware Configuration by completing the SAP sizing questionnaire for R/3. Review the sizing deliverable document prepared by the IBM ISV TechLine Sizing Department in conjunction with your IBM Sales Team or implementation partner. Memory estimates will be provided as well.The questionnaire is available online at: http://www.ibm.com/erp/sizing or by request from eSizings@us.ibm.com.

3. Minimum required disk space for a standard installation is 20GB, 4.3GB temporary disk space for every DVD to be copied to the local hard disk, plus an additional 1.2GB of temporary disk space.

4. Install GB Ethernet adapter for Gigabit Ethernet connectivity to d atabase.

5. 20GB paging space is required for 64 bit kernels (OSS Note 153641).

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 12 of 51

IV z/OS Software Preparation

1. Review Software Checklist in Installation Manual.

REQUIRED

•z/OS 1.6* or higher with the following components installed: UNIX System Services, DFSMS, TCP/IP, LE370, DFSORT

•JES2 or JES3

•z/OS Security Server (RACF V 2.2 or higher) or a similar security function

•z/OS RMF (Resource Management Facility) or another compatible product that

supports the Sysplex Data Services (ERBDSQRY, ERBDSREC, ERB2XDGS, ERB3XDRS)

•DB2 UDB for z/OS V8.1 or higher

•Control Center for DB2 UDB for z/OS (FMID JDB881D)

•DB2 Utilities Suite for z/OS

•DB2 Connect V8.1, FixPak 14 or

•DB2 Connect 9 FP 2 Special Build 17586 (APAR IY99846)

*z/OS 1.6 is required for SAP NetWeaver based on WebAS 7.00 - SAP NetWeaver 2004S and SAP components, Business Suite 2005, based on that technology release, but service ended for z/OS 1.6 in September 2007.

HIGHLY RECOMMENDED

•z/OS DFSMSdfp (base element): Provides storage, data, program, and device

management functions. Related optional features are :

•DFSMSdss (optional zOS feature): FlashCopy, volume level dumps and restores

•DFSMShsm (optional zOS feature): Automated DASD storage management,

including space management for low and inactive data. Required for DB2 BACKUP SYSTEM utility.

•z/OS SDSF (Spool Display Search Facility) or equivalent

•z/OS DFSMSrmm (Tape Management) or equivalent

•DB2 Performance Expert (5655-I21) or equivalent

•Tivoli Workload Scheduler for z/OS or equivalent

NICE TO HAVE

•DB2 Automation Tool (5697-G63)

•Tivoli Workload Scheduler for SAP or equivalent

REQUIRED FOR HIGH AVAILABILITY

•Tivoli Netview for z/OS (5697-ENV)

•Tivoli Systems Automation for zSeries (5645-006 MLC, 5698-A14 OTC) or equivalent**

•Tivoli Systems Automation for Linux for zSeries (required only if using z/Linux

application servers)

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 13 of 51

ENQ/SCS SOLUTION

**Documentation and sample scripts for TSA are available from IBM. If the customer chooses an equivalent product they take full responsibility for configuring and testing that product with mySAP. High availability solutions are available from a number of providers, the customer is responsible for checking with the provider directly to verify their ability to support mySAP HA scenarios.

REQUIRED FOR

zLINUX APPLICATION SERVERS

•SuSE Linux Enterprise Server 10 for zSeries - SLES 10 SP1 (glibc 2.4.31.30, kernel

2.6.16.46-0.12-default) or

•SuSE Linux Enterprise Server 9 for zSeries - SLES 9 SP3 (glibc 2.3.3-98.61,

kernel-s390x-2.6.5-7.244)

HIGHLY RECOMMENDED FOR zLINUX APPLICATION SERVERS

•z/VM 5.3 - for running zLinux application servers as VM guests (If using zLinux Application Servers under z/VM, CPINT is available for download from http://linuxvm.org/Patches/ This product allows for calls back to the hosting /VM system from within the zLinux guest.

•z/VM Performance Toolkit

2. Install all applicable z/OS and DB2 PTFs listed in OSS note 81737.

3. TCP/IP is required as the communication protoco l and OSA-Express GbE is strongly recommended as the connectivity type. Review configuration and parameters in the SAP R/3 on DB2 UDB for OS/390 and z/OS: Connectivity Guide.

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 14 of 51

4. Define the necessary users via RACF definitions (review the SAP Security Guide for IBM DB2 UDB for z/OS):

- define z/OS groupid <SCHEMA> as this will be the creator of all DB2 objects (Default = SAPR3)

- define R/3 installation userid (superuser) for z/OS (zLinux uses linux root user)

- define userid <sid>adm and groupid SAPSYS to run z/OS System Central Services (zLinux uses linux user <sid>adm and linux group sapsys)

- define DB2 Connect Userid (for Java it is sap<sid>db, it is recommended that the user be created without a TSO segment and without an expiration date)

- define userid with DB2 SYSADM authority for installation tasks (only needed for installation)

- define superuser to start SAPOSCOL and SAPCCMSR under USS

Review the SAP Security Guide for all of the necessary security settings for DB 2.

5. Test FTP and job submission between the application server and z/OS using the DB2 SYSADM userid created above in step 4. * Pre-Install Check*

6. Setup UNIX System Services parameters by modifying SYS1.PARMLIB(BPXPARMxx) , including the Physical File System definition for the TCP/IP communication protocol stack. Integrated INET is recommended over Common INET. See Sample BPXPRMxx in Section X. SAP Central Services can run under USS as well as the programs saposcol and sapccmsr.

7. z/OS no longer supports compatibility mode dispatching priorities. A WLM Goal Mode configuration is required , in particular for the DDF workload since that is where the SAP enclaves will be created via the DB2 DDF address space. The WLM configuration and setup is described in the SAP Planning Guide for SAP NetWeaver for IBM DB2 UDB for z/OS.WLM Workload attributes include: SAP work process type (dialog, batch, update, etc.), <SID>, host name, ABAP Report, and transaction code.

8. Place the JES Scheduler Work Area (SWA) above the 16MB line:

JES2 - SWA=ABOVE on JOBCLASS(STC)

in SYS1.PARMLIB(JES2PARM)

JES3 - Initialization parameter CIPARM (Converter/Interpreter

Parameter List) defined to place SWA above the line.

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 15 of 51

9. Configure the TCP/IP protocol for GB Ethernet:

A. Define the z/OS I/O configuration for the OSA-ExpressCard:

- Define channel path ID for OSA-Express channel with type=OSA

- Define OSA-Express control unit with type=OSA

- Define 2 OSA-Express devices

- Define Unit Addresses for the Control Unit (2 Devices for LCS (D118,D119) B. Customize the OSA-Express Feature through OSA/SF or TSO. C. Configure the MPC interface using the DEVICE, LINK, HOME, GATEWAY, and START statements in the TCP/IP Profile Dataset. Jumbo frames are recommended if network hardware supports it (MTU = 8992). D. Configure the AIX or NT network connection. E. Test the connection using ping or oping. * Pre-Install Check*

10. Test the TCP/IP configuration using the TCP/IP HOMETEST facility. This looks for errors in the configuration.

* Pre-Install Check*

11. Setup the RRS subsystem and monoplex environment . DB2 Stored Procedures used by SAP exploit the RRS Attach Facility. Configure a DASD only logstream if running in a monoplex mode. Allocate Coupling Datasets and System Logger datasets.

12. Review the Pre-Installation Activities and Administration C hapters (3 and 4) in the SAP Planning Guide for SAP NetWeaver for IBM DB2 UDB for z/OS.

13. Cache the DB2 User Catalog (catalogs the SAP tablespaces and indexspaces) in a Data Space accessed through VLF. To do this add the following to the COFVLFxx parmlib member:

CLASS NAME(IGGCAS) EMAJ(name of user catalog dataset)

14. Switch off unnecessary traces. Activate SMF type 70-79 and 100-102 records.

15. Use the IBM Health Checker for z/OS and Sysplex Tool. The IBM Health Checker for z/OS and Sysplex is a tool that checks the current active z/OS and sysplex settings and definitions for an image and compares their values to those either suggested by IBM or defined by you, as your criteria. The objective of the IBM Health Checker for z/OS and Sysplex is to identify potential problems before they impact your availability, or in worst cases, cause outages. This tool runs on all z/OS releases. It is available at www.ibm.com/servers/eserver/zseries/zos/downloads and is a part of the base release as of z/OS 1.7.

16. After the SAP installation is complete setup and install the SAP Operating System Collector saposcol , the CCMS agent SAPCCMSR, and the SAP DB2 Stored Procedure

12/18/2007

IBM Solutions Technical Sales (STS) 12/18/2007Page 16 of 51