(ZOS) Tune on z/OS

Learn about tips to tune your z/OS operating system to optimize WebSphere Application Server performance.

One of the goals of the WAS for z/OS programming model and runtime environment is to significantly simplify the work required for application developers to write and deploy applications. WAS for z/OS can help to relieve the application programmer of many of the plumbing tasks involved in developing applications. For example, application code in WAS for z/OS does not concern itself directly with remote communication, it locates objects which might be local or remote, and drives methods. As a result, there is no direct use of socket calls or TCP/IP programming in a WAS for z/OS application.

Separating application development tasks from determining where to run the application is one aspect of relieving plumbing tasks. Other aspects to consider include assistance with data calls for multiple types of beans, assistance with user authentication, and threading.

Removing tuning work from the application programmer does not mean that the work is complete. There might also be tuning work for database administrators, network administrators, security administrators, and performance analysts.

Use the following topics to tune your z/OS operating system to optimize WAS performance.

Tasks

• Tune the z/OS operating system
• Tune the WAS for z/OS runtime
• Tune the message-driven bean processing on z/OS using IBM MQ as the messaging provider in ASF mode

What to do next

For more information about tuning applications, see the using application clients information.

Subtopics

• Tune the z/OS operating system
  Use these steps to tune your z/OS operating system to optimize WAS performance.

• Tune the WAS for z/OS runtime
  To optimize performance, review the following steps involved in tuning the WAS for z/OS runtime.

• Tune message-driven bean processing on z/OS using IBM MQ as the messaging provider in ASF mode
  We can tune message-driven beans processing when we are running WAS on the z/OS platform, where IBM MQ is the messaging provider, and the message-driven bean has been deployed in Application Server Facilities (ASF) mode.

Use application clients