06.01.2013 Views

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3. Optional: Make the directories available as network drives by using DFS SMB for Windows<br />

application servers.<br />

4. Store the executable (.exe) files locally on each application server or place them in a<br />

central or shared directory by platform.<br />

Shared executable files: Shared executable files make sense for application servers<br />

that share the SAP kernel version, simplifying SAP release management. For staged<br />

release management, also consider separating the shared file system for production,<br />

QA, and test or development instances.<br />

Setting up Workload Manager for SAP<br />

z/OS and DB2 use the Workload Manager to manage priorities of SAP workload threads.<br />

SAP created a special policy to optimize the processing behavior.<br />

Configure Workload Manager Service Policy as explained in the Planning Guide SAP on <strong>IBM</strong><br />

DB2 for z/OS, version 2.50 - 2011-10-01:<br />

1. Set rdisp/prio/wlm/enabled = 1 for ASCS and SCS.<br />

2. Set the DB2 address spaces DBM1, MSTR, and DIST to the same velocity with<br />

Importance = 1.<br />

For z/OS before 1.11: Place OMVS in the SYSTEM service class (occurs automatically in<br />

z/OS 1.11 and later).<br />

Miscellaneous settings from the Planning Guide<br />

The Planning Guide SAP on <strong>IBM</strong> DB2 for z/OS, version 2.50 - 2011-10-01, addresses many<br />

more z/OS parameters to configure. Additional parameters are listed here. To ensure that all<br />

parameters are up to date, see the Planning Guide SAP on <strong>IBM</strong> DB2 for z/OS, version 2.50 -<br />

2011-10-01, and the appropriate SAP Notes.<br />

Configure the following additional parameters:<br />

1. Set STRNO using a value in the range of 5 - 7 (default is 4) for highly active ICF catalogs.<br />

Review <strong>IBM</strong> informational APAR II10752 for further explanations.<br />

2. Set the SMFPRMxx parameter MEMLIMIT = NOLIMIT. The default value is 0, which prevents<br />

64-bit applications, such as the SCS, from starting.<br />

3. Include the modules SCEERUN and SCEERUN2 in the LINKLIST concatenation, which you can<br />

verify by using the z/OS command /D PROG,LNKLIST.<br />

4. Use VLF caching of the RACF user ID (UIDs) and group identifiers (GIDs) in the COFVLFxx<br />

parmlib member:<br />

CLASS NAME(IRRGMAP)EMAJ(GMAP)<br />

CLASS NAME(IRRUMAP)EMAJ(UMAP)<br />

CLASS NAME(IRRGTS)EMAJ(GTS)<br />

CLASS NAME(IRRACEE)EMAJ(ACEE)<br />

5. <strong>Download</strong> the Java Runtime Environment (JRE) or JVM if required for the SAP instance.<br />

See SAP Note 723909.<br />

6. Place the JES scheduler work area (SWA) above the 16-MB line.<br />

7. Configure the Resource Recovery Services (RRS) subsystem as explained in the<br />

Planning Guide SAP on <strong>IBM</strong> DB2 for z/OS, version: 2.50 - 2011-10-01.<br />

8. See Chapters 2 and 3 in the Planning Guide SAP on <strong>IBM</strong> DB2 for z/OS, version: 2.50 -<br />

2011-10-01.<br />

172 Running SAP Solutions with <strong>IBM</strong> DB2 10 for z/OS on the <strong>IBM</strong> zEnterprise System

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!