IBM 4.6 manual Locks per user limit, Active log duplexing

Page 15

Setting the values

1)Copy DSN.V8R1M0.NEW.SDSNSAMP(#02TIJUZ) to another dataset and/or member for updating.

2)Locate the line containing DSNTIZP and delete everything to the end of the file, including this line.

3)Locate the IDTHTOIN operand for the DSN6FAC macro.

4)Change the value to idle_thread_timeout as determined above, with care not to delete the continuations in column 72.

5)Locate the line containing SYSLMOD.

6)Update the DSN value on the following line to a data set where you have modification permissions (for example: DSN=DSN81.SDSNEXIT).

7)Submit the job and ensure it runs with a condition code zero.

Restart IBM DB2 subsystem for the change to take effect.

5.4Locks per user limit

During policy analysis, DB2 error 00C90096 may be seen in the trace.log file. This occurs when IBM Tivoli Identity Manager attempts to remove a large number of rows from a temporary table and the number of rows exceed the locks per user limit. This can be avoided by increasing the locks per user limit.

Determining the values

locks_per_user_limit – Total number of locks a user is allowed to hold at one time. Default value: 10000. Recommended value: 100000 or higher.

Setting the values

If implementing IBM DB2 for the first time, or creating a separate instance, this parameter can be increased by editing the LOCKS PER USER value.

To increase the limit for an existing installation:

1)Edit the existing DSNTIJUZ job.

2)Update NUMLKUS in the DSN6SPRM macro using the procedure described in the Idle thread timeout section.

3)Submit the job to rebuild the DB2 startup parameters.

Restart IBM DB2 subsystem for the change to take effect.

5.5Active log duplexing

Disabling the IBM DB2 active log duplexing has shown to increase account creation throughput by up to 62%. Changing this setting depends upon your installation’s procedures and conventions.

Determining the values

active_log_duplex – Enable active logging duplexing? Default value: YES. Recommended value: NO.

Setting the values

1)Edit the existing DSNTIJUZ job.

2)Update TWOACTV to active_log_duplex in the DSN6LOGP macro using the procedure described in the Idle thread timeout section.

3)Submit the job to rebuild the DB2 startup parameters.

Restart IBM DB2 subsystem for the change to take effect.

IBM Tivoli Identity Manager Performance Tuning Guide

Page 13

Image 15
Contents Issue Date Trademarks Copyright NoticeTable of contents Who should use this guide About this guideResource allocation Vital tuningsInitial tunings IntroductionMemory 2 CPUDisk space Workload management WLM timeout IBM WebSphere Application ServerJava virtual machine JVM size Change WLM timeout to wlmtimeout Message driven bean MDB request timeoutTransaction timeout Select Container Services Select ORB ServiceSetting the values Threads IBM Tivoli Identity Manager applicationRecycle bin ReconciliationsSelect Reconciliation Limiting attributes returned from the adapterLimiting the attributes evaluated Maximum durationSet the Max Duration to maxduration Microsoft Active Directory IBM Tivoli Identity Manager adaptersDetermining the values JCL location Description Idle thread timeoutAPARs Buffer poolsActive log duplexing Locks per user limitReorg and Runstats Additional Zparms Default value Recommended valueIBM Ldap Server Cache sizesMax connections Runstats Changelog limitsRow locking on Searchts IndexingBest 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.