![[z/OS]](../images/ngzos.svg)
ORB services advanced settings on the z/OS platform
Use this topic to support Object Request Broker (ORB) service advanced settings. This support includes ORB listener keep alive, ORB Secure Sockets Layer (SSL) listener keep alive, control threads, and workload profile.
To view this administrative console page, click .
ORB listener keep alive
Defines the value in seconds provided to TCP/IP on the SOCK_TCP_KEEPALIVE option for the Internet Inter-ORB Protocol (IIOP) listener.
This option verifies that idle sessions are still valid by polling the client TCP/IP stack. If the client goes away without notifying the server, the session is still active on the server side. Use this property to clean up these unnecessary sessions. If the client does not respond, the session closes. The default is 0 (zero). If the property is not set, the TCP/IP option is not set. Setting the SOCK_TCP_KEEPALIVE option generates network traffic on idle sessions, which can cause problems.
| Information | Value |
|---|---|
| Data type | Integer |
| Range | 0 - 2147040 |
ORB SSL listener keep alive
This property defines the value in seconds provided to TCP/IP on the SOCK_TCP_KEEPALIVE option for the SSL IIOP listener.
This option verifies if idle sessions are still valid by polling the client TCP/IP stack. If the client goes away without notifying the server, the session is still active on the server side. Use this option to clean up these unnecessary sessions. If the client does not respond, the session closes. The default is 0 (zero). If the property is not set, the TCP/IP option is not set. Setting the SOCK_TCP_KEEPALIVE option generates network traffic on idle sessions, which can be undesirable.
| Information | Value |
|---|---|
| Data type | Integer |
| Range | 0 - 2147040 |
Workload manager timeout
Specifies the maximum time in seconds that IIOP requests are queued and dispatched to a servant process.
| Information | Value |
|---|---|
| Data type | Integer |
| Range | 0 - 2147040 |
| Default | 300 |
| Disable workload manager queue timeout | 0 |
Workload profile
Specifies the server workload profile, which can be ISOLATE, IOBOUND, CPUBOUND, LONGWAIT, or CUSTOM.
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. |
| CUSTOM | User defined | Specifies that the number of servant application threads is determined by the value that is
specified for the servant_region_custom_thread_count server custom property. The minimum number of
application threads that can be defined for this custom property is 1; the maximum number of
application threads that can be specified is 500. Best practice: Before you specify a value greater than 100 in a production environment, you should try the value
in a test environment to ensure you do not negatively affect performance.
|
You can look at message BBOO0234I in the controller job log to check the number of worker threads.