Download PDF - IBM Redbooks

2. Define and configure TCP/IP for Gigabit Ethernet (GbE) connections:
– See Business Continuity for SAP on IBM System z, SC33-8206-04.
– Use jumbo frames (MTU = 8992).
– See SAP Note 1263782 for HiperSockets recommendations. HiperSockets for Linux on
System z with z/OS LPAR communication needs an (MTU=8K).
– DELAYACKS is the default. Use DELAYACKS for SAP on System z.
– Verify that the z/OS TCP/IP Send and Receive buffer sizes are at least 8 times the
maximum transmission unit (MTU) size.
3. Customize the OSA definitions:
– Disable TCP/IP Segmentation Offload for OSA ports.
– Specify INBPERF DYNAMIC in the LINK statement for the OSA ports.
If the OSA microcode level does not support DYNAMIC, specify MINLATENCY. This
setting reduces network latency related to the batching of packets that are presented
by the OSA Express card to the z/OS LPAR. For more information about the INBPERF
clause, see “DEVICE and LINK — MPCIPA OSA-Express QDIO devices statement” in
z/OS V1R10.0 Communications Server: IP Configuration Reference: SC31-8776-15:
http://publibz.boulder.ibm.com/epubs/pdf/f1a1b481.pdf
Preparing the z/OS Security Server (RACF)
Define the necessary USERIDS and GROUPS as explained in the SAP Security Guide: IBM
DB2 for z/OS:
1. Define z/OS ABAP Group ID SAPR3 as the SAP schema name for the ABAP DB2 objects.
2. Define DB2 Connect User ID ADBC for the ABAP database connection.
3. Define z/OS Java Group ID SAPJAVA as the SAP schema name for the Java DB2 objects.
4. Define DB2 Connect User ID JDBC for the Java database connection.
5. Define the z/OS Group IDs SAPSYS and SAPINST.
6. Define installation user ID SAPINST (superuser) for z/OS Central Services. (Linux on
System z uses the Linux root user.)
7. Define the user ID adm to run z/OS Central Services. (Linux on System z uses Linux
user adm and Linux group sapsys.)
8. Define the installation user ID with DB2 SYSADM authority for installation tasks
(SYSOPR1 or SYSOPR2 from ZPARMS can be used).
9. Post installation: Define a superuser to start or run SAPOSCOL and SAPCCMSR under
z/OS UNIX System Services.
Setting up the z/OS Shared Filesystem
SAP requires shared application server access to specific file systems, called global, profile,
and transport, on any platform.
To set up the z/OS Shared Filesystem:
1. Place the global, profile, and transport file systems on z/OS UNIX System Services zFS
file systems, which are fast, robust, and Sysplex HA capable.
The NFS server exports the files and directories in the shared file system to the
application servers.
2. Make the directories available by using NFS for Linux on System z, x86 Linux, or AIX
application servers.
Appendix B. Planning, preparing, and implementing the SAP landscape 171