Specifies the server workload profile, which can be ISOLATE, IOBOUND,
CPUBOUND, or LONGWAIT
The workload profile controls workload-pertinent decisions that are made
by the WebSphere Application Server for z/OS run time, such as the number
of threads used in the servant. The default value is IOBOUND, which is the
appropriate value for most applications. Use one of the other values when
your application requires more threads.
Workload profile |
Number of Threads |
Description |
ISOLATE |
1 |
Specifies that the servants are restricted to a single application
thread. Use ISOLATE to ensure that concurrently dispatched applications do
not run in the same servant. Two requests processed in the same servant can
cause one request to corrupt another. |
IOBOUND |
MIN(30, MAX(5,(Number of CPUs*3))) |
Specifies more threads in applications that perform I/O-intensive
processing on the z/OS operating system. The calculation of the thread number
is based on the number of CPUs. IOBOUND is used by most applications that
have a balance of CPU intensive and remote operation calls. A gateway or protocol
converter are two examples of applications that use the IOBOUND profile. |
CPUBOUND |
MAX((Number of CPUs-1),3) |
Specifies that the application performs processor-intensive operations
on the z/OS operating system, and therefore would not benefit from more threads
than the number of CPUs. The calculation of the thread number is based on
the number of CPUs. Use the CPUBOUND profile setting in CPU intensive applications,
like XML parsing and XML document construction, where the vast majority of
the application response time is spent using the CPU. |
LONGWAIT |
40 |
Specifies more threads than IOBOUND for application processing. LONGWAIT
spends most of its time waiting for network or remote operations to complete.
Use this setting when the application makes frequent calls to another application
system, like Customer Information Control System (CICS) screen scraper applications,
but does not do much of its own processing. |
Note: Number of CPUs is the number of CPUs online when the controller
comes up.
You can look at message BBOO0234I in the controller job log to check the
number of worker threads.