9. Configure the TCP/IP protocol for GB Ethernet:
A. Define the z/OS I/O configuration for the
-Define channel path ID for
-Define
-Define 2
-Define Unit Addresses for the Control Unit
(2 Devices for LCS (D118,D119)
B. Customize the
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. *
10.Test the TCP/IP configuration using the TCP/IP HOMETEST facility. This looks for errors in the configuration.
*
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
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
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
Copyright 2006 IBM Solutions Technical Sales (STS) | 12/18/2007Page 16 of 51 |
12/18/2007 |
|
