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.

Additional information: For more information about setting up ICF, see 3.1.2.1, “ICF<br />

Catalog Performance” in the Planning Guide SAP on <strong>IBM</strong> DB2 for z/OS, version 2.50 -<br />

2011-10-01.<br />

6. Reserve DASD storage for DB2 logs.<br />

You define the log and DASD settings only for the SAP installation phase now. This initial<br />

setup requires adaption in the post installation phase or at least a few weeks after the<br />

environment goes live. DB2 administrators must perform regular monitoring of the storage<br />

situation for each DB2 instance to avoid system constraints and to adapt storage to the<br />

real needs.<br />

a. Configure the DB2 active logs for the SAP installation:<br />

For nonproduction, use a minimum of three log data sets at 1000 - 3390 cylinders<br />

each for LOGCOPY1 and LOGCOPY2 on separate volumes.<br />

For production, use six 3390-3 volumes for active log data sets (one data set per<br />

volume) and three active log data sets with dual logging.<br />

Rule of thumb: Keep LOGCOPY1 and LOGCOPY2 in separate SMS storage<br />

groups for availability.<br />

b. Configure the archive log environment.<br />

Rule of thumb: Maintain 24 hours of active logs in a production environment. You<br />

can use the DB2 utility BSDS Print to determine the frequency of log archiving.<br />

For production systems, you might start with two or three times the size you need for the<br />

production environment. Depending of the SLAs with your LOB, adjust it toward a capacity<br />

that can store the number of days required for recovery.<br />

7. Define and use DASD for archiving the SAP installation.<br />

Use a minimum of 40 GB of archive space for an ECC installation. The space varies by<br />

SAP application and must be adapted after installation for SAP backup archiving.<br />

8. Obtain DB2 system documentation, and install the DB2 subsystem:<br />

For each installation step, check the SAP documentation for definitions and adjustments<br />

that are specific to SAP.<br />

a. Specify the DB2 initialization parameters.<br />

Set the DSNZPARMS (DB2 system parameters or ZPARMS), DSNTIPD installation<br />

values, and initial the buffer pool parameters as explained in Chapter 3 of the SAP DBA<br />

Guide: DB2 for z/OS (V10) and in SAP Note 1476146 (for DB2 10). You might need to<br />

revisit the ZPARMS after the SAP application installation and to optimize them<br />

occasionally during the application lifetime.<br />

b. See Chapter 3 about DB2 parameterization in the SAP DBA Guide: DB2 for z/OS<br />

(V10).<br />

c. Ensure that all required parameters are set as explained in 3.3.1 of the SAP DBA<br />

Guide: DB2 for z/OS (V10).<br />

d. Set all SAP highly recommended parameters as explained in 3.3.2 of the SAP DBA<br />

Guide: DB2 for z/OS (V10).<br />

e. Consider using the SAP recommended DB2 parameter settings as documented in<br />

3.3.3 of the SAP DBA Guide: DB2 for z/OS (V10).<br />

174 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!