IBM 4.6 APARs, Buffer pools, Idle thread timeout, Determining the values JCL location Description

Page 14

5 IBM DB2

Tuning IBM DB2 to run with the IBM Tivoli Identity Manager product involves adjusting the buffer pools, modifying the number of connections, modifying internal database values, adding table space, adjusting logs, indexing, and running runstats.

The tuning JCL provided applies to the z/OS 1.6 LDAP server. The z/OS 1.8 LDAP server was not available at the time this document was prepared.

5.1APARs

Two ODBC APARs have been linked to poor LDAP performance on z/OS. It is recommended that these APARs be installed on the system:

PK21695 – Mutex lock contention

PK17652 – High CLI CPU utilization

5.2Buffer pools

Tuning the IBM DB2 buffer pools has shown to decrease deadlocks and improve overall performance. IBM Tivoli Identity Manager includes three JCL scripts to tune the IBM DB2 buffer pools based on which database is being tuned and how WebSphere Application Server is set up.

Determining the values

#

JCL location

Description

 

 

 

1

hlg.SAERSAMP(AERTNDBC)

Tune ITIM database when using a WAS cluster

 

 

 

2

hlg.SAERSAMP(AERTNDBS)

Tune ITIM database when using a single WAS server

 

 

 

3

hlg.SAERSAMP(AERTNLDP)

Tune LDAP database

 

 

 

Identify which JCL script is needed to tune your Tivoli Identity Manager database (either 1 or 2). JCL script 3 is used for the LDAP database for both single and clustered WebSphere configurations.

Setting the values

1)Edit the JCL to conform to your installation’s standards.

2)Update DB2 schema names, such as the database name, to match your environment.

3)Submit the JCL for execution.

5.3Idle thread timeout

DB2 continually checks for idle threads to cancel. Sometimes during SQL queries that return large amounts of data, if there is a delay between the sending of one DRDA query block and another, an abend 04E reason code 00D3003B, may occur, indicating that the idle thread timeout was exceeded. Increase the idle thread timeout to avoid this error.

Determining the values

idle_thread_timeout – Total time in seconds before an idle thread will timeout. Default value: 120.

Recommended value: 7200. This value is in the DB2 DSNTIJUZ customization job, located on the IDTHTOIN operand for the DSN6FAC macro

Page 12

IBM Tivoli Identity Manager Performance Tuning Guide

Image 14
Contents Issue Date Copyright Notice TrademarksTable of contents About this guide Who should use this guideIntroduction Vital tuningsInitial tunings Resource allocationDisk space Memory2 CPU Java virtual machine JVM size Workload management WLM timeoutIBM WebSphere Application Server Select Container Services Select ORB Service Message driven bean MDB request timeoutTransaction timeout Change WLM timeout to wlmtimeoutSetting the values Reconciliations IBM Tivoli Identity Manager applicationRecycle bin ThreadsMaximum duration Limiting attributes returned from the adapterLimiting the attributes evaluated Select ReconciliationSet the Max Duration to maxduration IBM Tivoli Identity Manager adapters Microsoft Active DirectoryBuffer pools Idle thread timeoutAPARs Determining the values JCL location DescriptionLocks per user limit Active log duplexingReorg and Runstats Default value Recommended value Additional ZparmsMax connections IBM Ldap ServerCache sizes Indexing Changelog limitsRow locking on Searchts RunstatsBest practices Regular maintenance Other resources

4.6 specifications

IBM 4.6, known for its robust and versatile capabilities, represents a significant evolution in the realm of enterprise software solutions. This version is primarily associated with IBM's middleware offerings, notably IBM WebSphere Application Server. It is engineered to support the development, deployment, and management of web applications with a focus on scalability, reliability, and security.

One of the standout features of IBM 4.6 is its enhanced performance optimizations. The platform employs advanced caching strategies and efficient resource management to improve application response times and throughput. This means that businesses can handle heavier loads with fewer resources, making it an economical choice for enterprises of all sizes.

Another notable characteristic is its support for a wide range of programming models and standards, including Java EE. This allows developers to build applications using familiar tools and frameworks, accelerating development timelines and improving productivity. Additionally, IBM 4.6 offers robust integration capabilities with existing enterprise systems through its support for web services and messaging protocols.

IBM 4.6 also emphasizes security. It includes features such as role-based access control, data encryption, and comprehensive auditing capabilities. These measures help organizations safeguard sensitive information and comply with various regulatory requirements.

The compatibility with multiple platforms, including cloud environments, is another significant advantage. IBM 4.6 simplifies deployment across diverse infrastructures, enabling businesses to operate in hybrid environments seamlessly. This flexibility is particularly beneficial as organizations increasingly adopt cloud migration strategies.

Furthermore, IBM 4.6 is equipped with a range of monitoring and management tools. These tools provide insights into application performance and health, allowing IT teams to proactively identify and address potential issues before they impact users. This capability is critical in maintaining high availability and reliability of services.

In summary, IBM 4.6 stands out as a comprehensive solution for enterprise application development and management. Its key features, such as enhanced performance, support for industry standards, strong security measures, platform compatibility, and monitoring tools, make it a compelling choice for organizations seeking to modernize their IT infrastructure. Implementing IBM 4.6 can empower businesses to innovate faster while ensuring their applications remain secure and efficient in a rapidly evolving digital landscape.