IBM DB2 9 Technical manual

Planning And Preparation Guide For SAP NetWeaver
7.0: z/OS Implementation:
D 2 V8
D 2 9
Albert D. Rodi
Consulting IT Specialist
I M Solution Technical Sales
International usiness Machines Corporation
1503 L J Freeway
Dallas, TX 75234
[phone] or TieLine 8-542-4791
E-mail: [email protected]
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 1 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

Trademarks
The following are trademarks of the International usiness Machines Corporation in the United States and/or
other countries
AIX* On emand Business Logo
CICS* PR/SM
B2* Parallel Sysplex*
B2 Universal atabase pSeries*
e-business logo System z9
Enterprise Storage Server* System z
G PS* Tivoli*
Geographically ispersed 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.
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 2 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

Contents
I General Preparation Steps
II z/OS Hardware Preparation
III AIX Hardware Preparation
IV z/OS Software Preparation
V B2 and B2 Connect Preparation
VI B2 Related OSS Notes
VII AIX Software Preparation
VIII Windows NT Hardware/Software Preparation
IX SAP Installation Preparation
X Sample BPXPARMxx Member
XI Sample B2 SNZPARMS
XII TCP/IP Connectivity
XIII Naming Conventions
XIV Application Server On z/OS Considerations
XV Sample OSA-Express GB Configuration
XVI B2 Backup/Recovery Notes
XVII SAP Automation And High Availability Solution
XVIII SAP Application Server On zLinux Considerations
XIX Sample SMS Storage Group Assignments
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 3 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

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 B2 subsystems
 The mass processing tool to convert indexes to NOT PA E is available
(Transaction B2_IXFIX)
 Modifications have been made to the PTF Checker Tool
 New BA Cockpit Monitoring Tool in Basis Support Package 12
 B2 9 certified July 2007
What is new with SAP Web Application Server 6.40 ?
• B2 Version 8 is required for the SAP Web AS Release 6.40. Many new features of
B2 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.
• B2 Connect is used to connect non-z/OS application servers to B2 (enhancements
in the tool db2radm to setup B2 Connect). ICLI is no longer used. For the Java stack,
the B2 J BC Universal river is delivered with B2 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 B13)
- Exploitation of inline statistics and utilities TEMPLATE, MO IFY RECOVERY
and MO IFY STATISTICS
- Protection of changed utility skeletons possible
- New design
• Recommendations for B2 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
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 4 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

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
B2 BA
B2 Systems Programmer
R/3 Administrator
z/OS Capacity Planning & Performance Administrator
2. Available ocumentation (SAP):
- SAP Planning Guide for SAP NetWeaver for IBM DB2 UDB for z/OS
- Co ponent Installation Guide: SAP ERP 2005 ABAP+Java on AIX: IBM
DB2 UDB for z/OS
- Co ponent Installation Guide: SAP ERP 2005 ABAP+Java on Windows:
IBM DB2 UDB for z/OS
- Co ponent 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 Ad inistration 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
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 5 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

- 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 ocumentation (IBM):
- High Availability for SAP on zSeries Using Autonomic Computing
Technologies (SC33- 8206)
- SAP on B2 U B for OS/390 and z/OS: Implementing Application
Servers On Linux for zSeries (SG24- 6847)
- SAP on IBM B2 U B for OS/390 and z/OS: Best Practices for
Installing or Migrating to B2 V8
(websmp202 sap-ag de/~form/sapnet?_SHORTKEY=01100035870000274486&)
- Tips for Installing B2 Connect V8 on SAP with B2 U B for z/OS V8
(www ibm com/support/docview wss?rs=64&uid=swg27005934)
- SAP on IBM B2 U B for z/OS: Best Practices for Installing or Migrating
to B2 9
(service.sap.com/SolutionManagerBP)
- Point-in-time recovery using B2 V8 for z/OS RESTORE SYSTEM utility
and SET LOG SUSPEN
- SAP on B2 for z/OS and OS/390: High Availability and Performance
Monitoring with ata Sharing (SG24-6950)
- SAP on B2 U B 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)
- B2 for z/OS and OS/390: Tools For Performance Management
(IBM SG24-6508)
- B2 for z/OS and OS/390 : ata Management Tools Update
(IBM SG24- 6406)
- SAP on B2 for z/OS and OS/390: B2 System Cloning
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 6 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

(IBM SG24- 6287)
- B2 U B for z/OS V8: Through the Looking Glass and What SAP
Found There (IBM SG24- 7088)
- isaster Recovery with B2 U B for z/OS (SG24-6370)
- B2 Performance Expert for z/OS (SG24- 6867)
- B2 U B for z/OS Version 8 Technical Preview (SG24- 6871)
- istributed Functions of B2 for z/OS and OS/390 (SG24- 6952)
- SAP on B2 for z/OS: Multiple Components In One atabase(MCO )
(SG24- 6914)
- B2 for z/OS Version 8 : Everything You Ever Wanted to Know...and
More (SG24-6079)
- B2 9 for z/OS: Performance Topics (SG24-7473)
- Enhancing SAP by Using B2 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).
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 7 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

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 B2 V8 for SAP Components
746924: Planning information for customers with SAP on zSeries
606682: High availability and automation solution for Linux zSeries
563060: B2/390: Configuring the AppServer on Linux for zSeries
731937: B2-z/OS: Customizing B2 Connect for WebAS 6.20 and B2 V8
710466: Upgrade to 6.40 - OS Platforms not supported
183311: B2/390: Automated PTF Check
427748: B2-z/OS: CCMS corrections (6.10, 6.20, 6.40,7.00)
943145: B2-z/OS: Transports and Support Packages for 7.0
943144: B2-z/OS: Transports and Support Packages for 7.0
823245: B2-z/OS: Transports and Support Packages for 7.0
858969: SAP NetWeaver 2004s Installation:IBM B2 U B for z/OS
81737: B2/390: APAR List
146289: Parameter Recommendations for 64-Bit SAP Kernel
138906: B2/390: Planning Info (release,connectivity matrix)
103135: B2/390: Installing saposcol manually
682077: B2-z/OS: Premigration checks for B
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: B2 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 ependencies 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: B2 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
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 8 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

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: B2 for z/OS: IC 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 B2 ata Sharing Configuration
SAP Sysplex Failover Scenarios for High Availability
SAP High Availability Enqueue Instance (Central Services Instance)
SAP Application Server on zLinux
Network Connectivity
atabase Backup/Recovery
isaster Recovery
7. Prepare a migration plan for submission to SAP if necessary.
8. Setup OSS connection, FTP capability to SAP.
9. Order R/3 eveloper Keys if necessary.
10. Generate Backup/Recovery Plan for z/OS, zLinux, AIX, Windows, and the SAP
atabase.
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 9 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

II z/OS Hardware Preparation
1. Review Checklist in Installation Manual and at service.sap.co /platfor s for
supported z/OS server models.
2. etermine Hardware Configuration by completing the SAP sizing
questionnaire for R/3. Review the sizing deliverable document prepared by the
IBM ISV TechLine Sizing epartment 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 [email protected].
3. Minimum AS 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 B2 active logs
(1) 3390-3 volume for B2 catalog, directory, BS S
(2) 3390-3 volumes for B2 SN B07
(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 B2 active logs
(3) 3390-3 volumes for B2 catalog, directory, BS S
(4) - (15) 3390-3 volumes for B2 SN B07
(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 B2 logs are archived to AS )
(PAV implementation is highly recommended)
z/Linux Application Server for ECC 6.0 (NetWeaver 7.0):
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 10 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

1.2 GB (Temporary installation disk space)
2 x zLinux Guest Memory (Swap Space)
4.3 GB (temporary disk space for every Installation V to be copied locally for
installation)
13GB (disk space for the SAP filesystems)
8-12GB (Linux)
200MB (CMS and the Linux boot disk)
4. efine a (400) track VTOC for each AS volume that will contain B2 data through
ICK SF AS initialization. VV S should be (180) tracks and the VTOC Index should
be (50) tracks.Triple these values if the AS geometry is 3390-9. For 3390-54
geometry use 8,000 tracks for the VTOC, 3600 tracks for the VV S, and 1000 tracks
for the VTOC Index.
5. ICF Catalog Size for B2 datasets: (50) cylinders primary, (5) cylinders
Secondary.
6. 15 MB JES Spool Space.
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 11 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

III AIX Hardware Preparation
1. Review Checklist in theComponent Installation Guide : SAP ERP 2005 ABAP+Java
on AIX: IBM B2 U B for z/OS for base Hardware Requirements .
2. etermine Hardware Configuration by completing the SAP sizing
questionnaire for R/3. Review the sizing deliverable document prepared by the
IBM ISV TechLine Sizing epartment 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 [email protected].
3. Minimum required disk space for a standard installation is 20GB, 4.3GB temporary
disk space for every V 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) .
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 12 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

IV z/OS Software Preparation
1. Review Software Checklist in Installation Manual.
REQUIRE
•z/OS 1.6* or higher with the following components installed: UNIX System Services,
FSMS, TCP/IP, LE370, FSORT
•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 ata Services (ERB SQRY, ERB SREC, ERB2X GS,
ERB3X RS)
•B2 U B for z/OS V8.1 or higher
•Control Center for B2 U B for z/OS (FMI J B881 )
•B2 Utilities Suite for z/OS
•B2 Connect V8.1, FixPak 14 or
•B2 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 RECOMMEN E
•z/OS FSMSdfp (base element): Provides storage, data, program, and device
management functions. Related optional features are :
•FSMSdss (optional zOS feature): FlashCopy, volume level dumps and restores
•FSMShsm (optional zOS feature): Automated AS storage management,
including space management for low and inactive data. Required for B2
BACKUP SYSTEM utility.
•z/OS S SF (Spool isplay Search Facility) or equivalent
•z/OS FSMSrmm (Tape Management) or equivalent
•B2 Performance Expert (5655-I21) or equivalent
•Tivoli Workload Scheduler for z/OS or equivalent
NICE TO HAVE
•B2 Automation Tool (5697-G63)
•Tivoli Workload Scheduler for SAP or equivalent
REQUIRE FOR HIGH AVAILABILITY ENQ/SCS SOLUTION
•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)
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 13 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

** ocumentation 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.
REQUIRE 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 RECOMMEN E 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 B2 PTFs listed in OSS note 81737.
3. TCP/IP is required as the communication protocol and OSA-Express GbE is strongly
recommended as the connectivity type. Review configuration and parameters in the
SAP R/3 on B2 U B for OS/390 and z/OS: Connectivity Guide.
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 14 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

4. efine the necessary users via RACF definitions (review the SAP Security Guide for
IBM B2 U B for z/OS):
- define z/OS groupid <SCHEMA> as this will be the creator of all B2 objects
( efault = 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 B2 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 B2 SYSA M 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 B 2.
5. Test FTP and job submission between the application server and z/OS using the
B2 SYSA M 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 F workload since that is where
the SAP enclaves will be created via the B2 F address space. The WLM
configuration and setup is described in the SAP Planning Guide for SAP NetWeaver for
IBM B2 U B for z/OS.WLM Workload attributes include: SAP work process type
(dialog, batch, update, etc.), <SI >, 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.
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 15 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

9. Configure the TCP/IP protocol for GB Ethernet:
A. efine the z/OS I/O configuration for the OSA-ExpressCard:
- efine channel path I for OSA-Express channel with type=OSA
- efine OSA-Express control unit with type=OSA
- efine 2 OSA-Express devices
- efine Unit Addresses for the Control Unit
(2 evices for LCS ( 118, 119)
B. Customize the OSA-Express Feature through OSA/SF or TSO.
C. Configure the MPC interface using the EVICE, LINK, HOME,
GATEWAY, and START statements in the TCP/IP Profile ataset. Jumbo
frames are recommended if network hardware supports it (MTU = 8992).
. 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 . B2 Stored Procedures
used by SAP exploit the RRS Attach Facility. Configure a AS only logstream if
running in a monoplex mode. Allocate Coupling atasets 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 B2 U B for z/OS.
13. Cache the B2 User Catalog (catalogs the SAP tablespaces and indexspaces) in a
ata 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 B2 Stored Procedure
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 16 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

SAPCL as per Chapter 4 of the SAP Planning Guide for SAP NetWeaver for IBM B2
U B for z/OS. These processes run under Unix System Services (USS).
17. For z/OS V1.7 and z/OSe V1.7: If the SAP implementation will exploit the IBM
System z9 Integrated Information Processor(zIIP), this requires the "IBM
System z9 Integrated Information Processor Support for z/OS and z/OSe Web
eliverable, available on the z/OS downloads website plus PTFs.
This Web deliverable contains FMI JBB772S for z/OS and z/OS.e V1.7:
Http://www-03.ibm.com/servers/eserver/zseries/zos/downloads/
Install the service identified in the program directory that comes with this Web
deliverable and the recommended service in the appropriate ZOSV1Rn BCPZIIP
PSP bucket. IBM B2 U B for z/OS V8 with PTFs, is also required for exploitation
for portions of eligible workloads. See Flash10477 on the Techdocs website for
more information. For z/OS and z/OS.e V1.8 this Web deliverable is not needed.
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 17 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

V B2 Preparation
1. Install B2 subsystem. A separate ICF catalog is recommended for each B2
subsystem based on the High Level Qualifier for B2 datasets. the ICF Catalog should
contain only the catalogued objects for a single B2 subsystem. However, with B2 V8
and B2 9 the recommendation is to have two ICF Catalogs, one for each Copy Pool.
There is a ataBase Copy Pool, that will contain the SAP tablespaces, SAP
indexspaces, B2 Catalog, and B2 irectory. There is also a Log Copy Pool that will
contain the Active Log atasets and the BS S atasets. The reason for this separation
is that during a RESTORE SYSTEM only the ataBase Copy Pool will be restored to
AS , not the Log Copy Pool, and we do not want the ICF Catalog containing the Logs
and BS S restored. This is explained in Chapter 7 of the redbook SG24-7088.
Review all of the setup information in Chapter 3 of the SAP atabase Administration
Guide for SAP NetWeaver on IBM B2 U B for z/OS.
This chapter describes in detail the setup activities such as RRS, Stored Procedure
Setup, and z/OS Unicode Conversion Services.
2. Apply all recommended PTFs from OSS Note 81737.
3. Modify group attach name in SYS1.PARMLIB(IEFSSNxx) if using data sharing. The
recommendation is to use the SAP SI for the group attach name, and the SAP SI
followed by a member number for each B2 memb er within the group. See the
recommended naming conventions in Section XIV.
4. Configure B2 active log datasets and SN B07:
- for a nonproduction system (3) log datasets @ 1000 3390-3 cylinders each for
LOGCOPY1 and LOGCOPY2 minimum on separate volumes
- for a production system (6) volumes are recommended for active log datasets
(one dataset per volume)
- for installation disable archiving with the hidden zparm OFFLOA =NO and use
(6) volumes for active log datasets (one dataset per volume)
- place active log datasets and BS S datasets on separate controllers
for maximum availability
- recommended production initial definitions for SN B07 for a large installation
(each should be on a separate volume, ~1300 logged in users) :
(7) 4K TableSpaces @ 660 cylinders each
(5) 4K TableSpaces @ 500 cylinders each
(3) 32K TableSpaces @ 185 cylinders each , Total = 7675 cylinders
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 18 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

- recommended production initial definitions for SN B07 for an initial installation
(each should be on a separate volume):
(4) 4K TableSpaces @ 200 cylinders each
(2) 32K TableSpaces @ 200 cylinders each , Total = 1200 cylinders
5. efine archive log environment. If archiving to AS , create a SMS storage group
and configure enough AS to maintain enough archives between HSM migrations.
evelop and implement a HSM migration strategy. If archiving to tape then set
ARCWTOR=NO and ensure that tapes are available via a loader. The installation will
require at least 30 GB of archive space. There will be approximately 40 log archives
during the load phase of the installation. Another option is to use a hidden B2
ZPARM. Setting OFFLOA =NO will disable B2 archive processing for the installation.
This should be removed after the installation.
6. Set SNZPARMS , SNTIP installation panel values, and Buffer Pool
Parameters as per the SAP atabase Administration Guide for SAP NetWeaver on
IBM B2 U B for z/OS. OSS Note 1032273 addresses the ZPARM recommendations
for B2 9.
7. Install and Enable WLM Stored Procedures support as described in Chapter 3 of the
SAP atabase Administration Guide for SAP NetWeaver on IBM B2 U B for z/OS.
SAP uses WLM established address spaces for B2 Stored Procedures. WLM
dynamically creates and deletes address spaces and manages the work and the
number of address spaces according to a defined goal.
8. Set IRLM Parameters in the JCL: (use REGION=0M) (Watch for IEFUSI exit limit)
PC=YES (use IRLM Private Storage Area),
MLMT=4,
MAXCSA=0
EA LOK=5,1
SCOPE=LOCAL (GLOBAL if B2 ata Sharing is being used)
The PC and MAXCSA parameters are no longer used, but you must maintain them for
compatibility reasons. You must specify the parameters and values, but their values are
not used. B2 V8 and B2 9 require IRLM 2.2, which is delivered with B2 V8 and
B2 9. You must use the B2–supplied IRLM procedure. To modify an existing IRLM
procedure for use with IRLM, you must do the following:
•Add the MLMT (MEMLIMIT) parameter with the appropriate setting.
•Specify YES for the PC parameter.
•Specify 0 for the MAXCSA parameter.
9. Install Real Time Statistics and Stored Procedure SNACCOR as described in
Chapter 3 of the SAP atabase Administration Guide for SAP NetWeaver on IBM B2
U B for z/OS.
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 19 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation

10. Install the Control Center Stored Procedures required by SAP as described in
described in Chapter 3 of the SAP atabase Administration Guide for SAP NetWeaver
on IBM B2 U B for z/OS. The procedures are used for atabase administration and
replace the FTP submission of JCL streams used in previous releases.
11. efine <SCHEMA> as a secondary authorization I of the B2 Connect userid.
To do this replace the default secondary exit routine as described in
section 3.4.2.2 of the IBM B2 V8 Administration Guide or Appendix A of the B2 9
Administration Guide. Use the sample exit routine provided to use the RACF group
name <SCHEMA> as a B2 secondary I . This is setup through B2 installation job
SNTIJEX. SAPR3 is the default schema.
12. Setup the B2 F environment as described in Chapter 3 of the SAP atabase
Administration Guide for SAP NetWeaver on IBM B2 U B for z/OS.
13. Install B2 Connect V8.1, Fixpak 12 on each application server (except for z/OS
application servers). Create a 64 bit instance and reference OSS Note 731937 and the
document Tips for Installing B2 Connect V8 on SAP with B2 U B for z/OS V8
for SAP customization information. Test the connection to B2 using the ‘db2 connect’
command.
OR
Install the B2 Connect V9 CLI river. The information on how to complete this
installation is contained in OSS Note 1031213.
14. Initialize ECSA and ESQA so that the BM1 address space is allowed 1800MB of
extended private region.
Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 20 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6 40: z/OS Implementation