-recommended production initial definitions for DSNDB07 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.Define archive log environment. If archiving to DASD, create a SMS storage group and configure enough DASD to maintain enough archives between HSM migrations. Develop 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 DB2 ZPARM. Setting OFFLOAD=NO will disable DB2 archive processing for the installation. This should be removed after the installation.

6.Set DSNZPARMS , DSNTIPD installation panel values, and Buffer Pool

Parameters as per the SAP Database Administration Guide for SAP NetWeaver on IBM DB2 UDB for z/OS. OSS Note 1032273 addresses the ZPARM recommendations for DB2 9.

7.Install and Enable WLM Stored Procedures support as described in Chapter 3 of the SAP Database Administration Guide for SAP NetWeaver on IBM DB2 UDB for z/OS. SAP uses WLM established address spaces for DB2 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

DEADLOK=5,1

SCOPE=LOCAL (GLOBAL if DB2 Data 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. DB2 V8 and DB2 9 require IRLM 2.2, which is delivered with DB2 V8 and DB2 9. You must use the DB2–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 DSNACCOR as described in Chapter 3 of the SAP Database Administration Guide for SAP NetWeaver on IBM DB2 UDB for z/OS.

Copyright 2006 IBM Solutions Technical Sales (STS)

12/18/2007Page 19 of 51

12/18/2007

 

Page 19
Image 19
IBM DB2 V8, DB2 9 manual MLMT=4 MAXCSA=0 DEADLOK=5,1

DB2 V8, DB2 9 specifications

IBM DB2 is a family of data management products that provide powerful capabilities for managing large amounts of data. Among its various versions, DB2 9 and DB2 V8 stand out due to their advanced features and technologies that cater to both enterprise needs and modern database requirements.

DB2 9, also known as "Viper," was a significant release that brought substantial enhancements to the database management system. One of its standout features is its support for XML data. This version introduced a native XML storage architecture, allowing users to store, retrieve, and manage XML data efficiently. The advanced query capabilities for XML data made it easier to integrate both structured and unstructured information into applications.

Another notable aspect of DB2 9 is its enhanced security features. It introduced features like label-based access control, ensuring that sensitive data could be properly managed according to the security policies of an organization. This version also included a transparent data encryption mechanism, protecting data at rest without impacting performance.

DB2 V8, released prior to DB2 9, presented several key features that had a lasting impact on database technology. One of its major advancements was the introduction of pureXML, which laid the groundwork for handling XML data. DB2 V8 also provided improved performance through enhancements such as table partitioning, which allowed for more efficient data organization and retrieval.

Additionally, DB2 V8 emphasized high availability and disaster recovery, incorporating features like DB2 HADR (High Availability Disaster Recovery). This allowed organizations to ensure data continuity even in the event of system failures, a critical aspect for enterprise environments that rely on uninterrupted access to their data.

Both versions of DB2 leveraged advanced technologies such as multi-version concurrency control (MVCC), which enhanced transaction integrity and performance. Their ability to support various platforms, including Linux, UNIX, and Windows, demonstrated IBM's commitment to providing flexible solutions tailored to different environments.

In summary, both IBM DB2 9 and DB2 V8 established a strong foundation in the database management ecosystem. With features focused on XML data management, enhanced security, performance improvements, and high availability, these versions have equipped organizations with the tools necessary to handle contemporary data challenges efficiently and effectively. Their legacy continues to influence database technology today, highlighting IBM's enduring impact on data management solutions.