4.Define the necessary users via RACF definitions (review the SAP Security Guide for IBM DB2 UDB for z/OS):

-define z/OS groupid <SCHEMA> as this will be the creator of all DB2 objects (Default = SAPR3)

-define R/3 installation userid (superuser) for z/OS (zLinux uses linux root user)

-define userid <sid>adm and groupid SAPSYS to run z/OS System Central Services (zLinux uses linux user <sid>adm and linux group sapsys)

-define DB2 Connect Userid (for Java it is sap<sid>db, it is recommended that the user be created without a TSO segment and without an expiration date)

-define userid with DB2 SYSADM authority for installation tasks (only needed for installation)

-define superuser to start SAPOSCOL and SAPCCMSR under USS

Review the SAP Security Guide for all of the necessary security settings for DB2.

5.Test FTP and job submission between the application server and z/OS using the DB2 SYSADM userid created above in step 4. * Pre-Install Check*

6.Setup UNIX System Services parameters by modifying SYS1.PARMLIB(BPXPARMxx) , including the Physical File System definition for the TCP/IP communication protocol stack. Integrated INET is recommended over Common INET. See Sample BPXPRMxx in Section X. SAP Central Services can run under USS as well as the programs saposcol and sapccmsr.

7.z/OS no longer supports compatibility mode dispatching priorities. A WLM Goal Mode configuration is required , in particular for the DDF workload since that is where the SAP enclaves will be created via the DB2 DDF address space. The WLM configuration and setup is described in the SAP Planning Guide for SAP NetWeaver for IBM DB2 UDB for z/OS.WLM Workload attributes include: SAP work process type (dialog, batch, update, etc.), <SID>, host name, ABAP Report, and transaction code.

8.Place the JES Scheduler Work Area (SWA) above the 16MB line:

JES2 - SWA=ABOVE on JOBCLASS(STC) in SYS1.PARMLIB(JES2PARM)

JES3 - Initialization parameter CIPARM (Converter/Interpreter

Parameter List) defined to place SWA above the line.

Copyright 2006 IBM Solutions Technical Sales (STS)

12/18/2007Page 15 of 51

12/18/2007

 

Page 15
Image 15
IBM DB2 V8, DB2 9 manual 12/18/2007Page 15

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.