There are some application server custom properties that only apply to the z/OS platform. Use this page to configure these custom properties.
To set one of these custom properties for either an application server or a deployment manager, in the administrative console, click Environment > WebSphere Variables, select the appropriate server, node, or cell from the pull-down list of available servers, nodes and cells, and then click New.
Specifies that you want to allow the application server to do lookups on large SAF groups.
If you set this property to 1, the size of the buffer that is used to do lookups is tripled from 8192 bytes to 24576 bytes.
You can also set this property to a specific number off bytes up to and including 2147483647. If you specify an integer, other than 1, as the value for this property, the buffer size becomes that number of bytes. For example, if you specify allow_large_SAF_groups=21400000, the size of the buffer used to do lookups on SAF groups is 21400000 bytes.
If you do not specify a value for this property, or specify a value of 0, the buffer size is 8192 bytes.
Data Type | Integer |
Range | 1 - 2147483647 |
Default | 0 |
When a message arrives on the queue that a message-driven bean (MDB) is consuming from, the message is locked and passed to the MDB in the servant region. If the servant region is disabled, or if there is an error processing the message on the servant region, this property defines how long the messaging engine waits before unlocking the message so that it can be re-delivered.
Data Type | Integer |
Units | milliseconds |
Default | 300000 |
Range | A positive integer. The value 0 indicates that the message lock never expires and the messaging engine waits indefinitely for the servant region to process and unlock the message. |
Specifies whether the controller rejects requests for dispatch within a servant when it detects that there are no servants available to process requests.
When this property is set to 1, the controller detects that there are no servants available to process requests, the controller rejects requests for dispatch within the servants, de-registers the application server with Workload management (WLM), and stops the HTTP and message-driven bean (MDB) listeners. If this property is set to 0 (zero), then the function is disabled.
When a minimal number of servants become available again, the controller registers the application server with WLM again, starts the HTTP and MDB listeners, and allows requests to be dispatched to the servants.
Data Type | Integer |
Acceptable values | 0 or 1 |
Default | 0 |
When a message arrives on the queue that a message-driven bean (MDB) is consuming from, the message is locked and passed to the MDB in the servant region. If the servant region is disabled, or if there is an error processing the message on the servant region, this property defines how long the messaging engine waits before unlocking the message so that it can be re-delivered.
Data Type | Integer |
Units | milliseconds |
Default | 300000 |
Range | A positive integer. The value 0 indicates that the message lock never expires and the messaging engine waits indefinitely for the servant region to process and unlock the message. |
Specifies whether requests are dispatched to servants following the detection of a no-servants situation. This property is ignored if the control_region_dreg_on_no_srs custom property is set to 0.
When this property is set to 1, the controller does not dispatch requests to the servants until it receives a response to message BBOO0297A. This message is issued following a no-servant situation when the sever detects that the required minimal number of servants are available to process requests.
When this property is set to 0 (zero), the controller determines when to allow requests to be dispatched to the servants after a no-servant condition is detected.
Data Type | Integer |
Acceptable values | 0 or 1 |
Default | 0 |
Specifies the percentage of the HTTP dispatch time limit that is used as the maximum amount of time that an HTTP request can spend on the workload management (WLM) queue. The protocol_http_timeout_output custom property is used to specify the maximum amount of time that an HTTP request can spend on the queue and in dispatch before an error message is issued, which indicates that an HTTP dispatch timeout has occurred.
Data Type | Integer |
Range | 0 - 99 |
Default | 0 |
Specifies the percentage of the HTTPS dispatch time limit that is used as the maximum amount of time that an HTTP request can spend on the workload management (WLM) queue. The protocol_https_timeout_output custom property is used to specify the maximum amount of time that an HTTP request can spend on the queue and in dispatch before an error message is issued which indicates that an HTTP dispatch timeout has occurred.
Data Type | Integer |
Range | 0 - 99 |
Default | 0 |
Specifies the percentage of the IIOP dispatch time limit that is used as the maximum amount of time that an IIOP request can spend on the workload management (WLM) queue. The control_region_wlm_dispatch_timeout custom property is used to specify the maximum amount of time that an IIOP request can spend on the queue and in dispatch before an error message is issued which indicates that an IIOP dispatch timeout has occurred.
Data Type | Integer |
Range | 0 - 99 |
Default | 0 |
Specifies the percentage of the MDB dispatch time limit that is used as the maximum amount of time that an MDB request can spend on the workload management (WLM) queue. The control_region_mdb_request_timeout custom property is used to specify the maximum amount of time that an MDB request can spend on the queue and in dispatch before an error message is issued which indicates that an MDB dispatch timeout has occurred.
Data Type | Integer |
Range | 0 - 99 |
Default | 0 |
Specifies the time, in seconds, that the server waits for a message-driven bean (MDB) request to receive a response. If the response is not received within the specified amount of time, the server removes the MDB request.
This property only applies for application servers.
Set this value to 0 (zero) to disable the function.
Data Type | Integer |
Units | Seconds |
Default | 120 |
Specifies the percentage of the Session Initiation protocol (SIP) dispatch time limit that is used as the maximum amount of time that a SIP request can spend on the workload management (WLM) queue. The protocol_sip_timeout_output custom property is used to specify the maximum amount of time that a SIP request can spend on the queue and in dispatch before an error message is issued which indicates that a SIP dispatch timeout has occurred.
Data Type | Integer |
Range | 0 - 99 |
Default | 0 |
Specifies the percentage of the SIP Secure Sockets Layer (SSL) dispatch time limit that is used as the maximum amount of time that a SIP SSL request can spend on the workload management (WLM) queue. The protocol_sips_timeout_output custom property is used to specify the maximum amount of time that a SIPS request can spend on the queue and in dispatch before an error message is issued which indicates that a SIP dispatch timeout has occurred.
Data Type | Integer |
Range | 0 - 99 |
Default | 0 |
Specifies the number of seconds a controller waits after detecting a timeout before it terminates the servant. This time delay gives work that is currently running in the servant a chance to complete before the servant is terminated.
The specified length of time period starts when a timeout occurs. When a servant thread completes its current work item and determines that the servant is being terminated, the servant thread waits for the specified length of time instead of selecting a new work item.
When this field is set to 0 the controller terminates a servant as soon as the controller detects a timeout.
Data Type | Integer |
Units | Seconds |
Default | 0 |
Only one new request is processed because, when the timeout occurs, the idle servant worker thread are paused waiting for WLM to assign each of them a new requests. When WLM assigns new work to one of these threads, the thread becomes active, processes the work, and then acquiesces. Therefore, WLM cannot assign any additional work to this thread.
Specifies the type of dump that is taken whenever a timeout occurs for work that has been dispatched to a servant. This property only applies if the control_region_timeout_delay custom property is set to a non-zero value.
Set this property to either JAVACORE or javacore, if you want a Java core dump, or set the property to either SVCDUMP or svcdump if you want an SVC dump.
Data Type | String |
Default | None |
Specifies the type of dump that is taken whenever a timeout occurs for an HTTP, HTTPS, SIP, or SIPS request that has been dispatched to a servant.
This property only applies if the following corresponding variable is set to SESSION:
The value specified for this property determines whether a Java core dump or an SVC dump is taken. Set this property to either JAVACORE or javacore, if you want a Java core dump, or set the property to either SVCDUMP or svcdump if you want an SVC dump.
Data Type | String |
Default | None |
Specifies whether the controller terminates the last available servant when a timeout situation occurs. If the controller does not terminate the last available servant when a timeout situation occurs, other work continues to be processed until a new servant is initialized. However, not terminating the last available servant might cause the loss of system resources if the dispatched servant thread that encountered the timeout situation continues to loop or stops functioning. For example, if timeouts keep occurring, the system might consume a high percentage of the available servant threads.
Data Type | Boolean |
Default | 0 |
Specifies, in megabytes, the maximum size of locally connected communications requests. For example, if you set the property to 35, then any requests over 35 megabytes are rejected. The minimum value for this property is 10 and the maximum value is 2048. Omit this property if you do not want to limit the size of locally connected communications requests.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Specifies, in megabytes, the maximum amount of data that can be queued up to send asynchronously over a single IIOP connection. If the amount of data queued exceeds the specified value, future IIOP requests over this connection fail with a C9C26A4D minor code. The minimum value for this property is 0, which indicates that there is no limit to the amount of data that can be queued for sending. The maximum value is 2048.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Specifies, in megabytes, the maximum size of locally connected communications requests. For example, if you set the property to 35, then any requests over 35 megabytes are rejected. The minimum value for this property is 10 and the maximum value is 2048. Omit this property if you do not want to limit the size of locally connected communications requests.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Specifies whether the application server waits for a minimum number of servants to be ready to accept work before the application server starts the HTTP transport channels. If this property is set to true, then when the minimum number of servants is ready for work, the HTTP transport channels start accepting work. If this property is set to false, the HTTP transport channels start when the controller starts.
When this property is set to true, the value specified for the Minimum Number of Instances property determines the number of servants that must be ready before the HTTP transport channels start.
To change the setting of the Minimum Number of Instances property for an application server, in the administrative console, click Application servers > server > Java and Process Management > Server Instance.
To change the setting of this property for a deployment manager, in the administrative console, click System administration > Deployment manager > Java and Process Management > Server Instance.
The job output indicates protocol_accept_http_work_after_min_srs: 1 if this property is set to true, or protocol_accept_http_work_after_min_srs: 0 if this property is set to false.
Data Type | Boolean |
Default | true |
Used by Daemon | No |
Determines when the daemon starts to send requests to the IIOP transport channels. If this property is set to true, the daemon starts to send requests to the IIOP transport channels when the minimum number of servants, as specified for the Minimum Number of Instances property, are ready to accept work, If this property is set to false, the daemon starts to sent requests to the IIOP transport channels when the controller starts.
To change the setting of the Minimum Number of Instances property for an application server, in the administrative console, click Application servers > server > Java and Process Management > Server Instance.
To change the setting of this property for a deployment manager, in the administrative console, click System administration > Deployment manager > Java and Process Management > Server Instance.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
Specifies that if the BBOO0168W message is issued, then the failure detected when attempting to send a response to a client is recorded. The message is sent to the error log. The message text contains the request method name, the reply status, and routing information identifying the client.
Data Type | Boolean |
Default | false |
Used by Daemon | yes |
Used to indicate that if the BBOO0169W message is issued, then the response that contains the SystemException is recorded. The message is sent to the error log. The message text contains the exception identifier and minor code, the request method name, and routing information identifying the client.
Data Type | Boolean |
Default | false |
Used by Daemon | yes |
Specifies the CORBA General Inter-ORB Protocol (GIOP) protocol version level that is used by the application server object request broker (ORB). Valid values are 1.1 and 1.2. Interoperable object references (IORs) exported from this server use the GIOP level indicated.
You might need to change this property from the default if you use a non-WebSphere Application Server client ORB that supports a lower version of the CORBA standard. For example, you might need to change from the default protocol version level of 1.2 to 1.1 to support an older version, non-WebSphere Application Server client ORB.
Data Type | String |
Default | 1.2 |
Used by Daemon | Yes |
Specifies the maximum length for the queue of pending connections using HTTP. The value used can be limited by the specification of the SOMAXCONN statement in the TCP/IP profile.
Data Type | Integer |
Default | 10 |
Used by Daemon | No |
Specifies the name of a file containing entries that map IP addresses to server certificate labels. You can set this property at the cell, node, or server level.
When an HTTP SSL connection request is received, the application server checks the IP address against entries in the file specified for this property. If the application server finds a match, the certificate mapped to the IP address is used for the connection. If the application server does not find a match, it checks the protocol_https_default_cert_label property for the name of a certificate. If a certificate name is specified, the application server uses that certificate to establish the connection. If a certificate name is not specified, the default server certificate specified in the RACF SSL keyring, that is owned by the application server, is used to establish the HTTP SSL connection.
Following is the syntax for entries in a certificate mapping file:
SSLServerCert label ipaddress
where:
Examples:
SSLServerCert 'My Certificate Label' 9.57.4.29 SSLServerCert "My Co.'s Certificate" 9.57.4.30
Specifies the label of the server certificate that the application server uses when establishing HTTP SSL connections with the application server. You can set this property at the cell, node, or server level.
If the name of a certificate is note specified for this property, the default server certificate specified in the RACF SSL keyring, that is owned by the application server, is used to establish the HTTP SSL connection.
Specifies, in bytes, the limit of the size of incoming HTTP requests when inbound HTTP chunking is disabled. For example, if you set the property to 15728640, any requests over 15 megabytes are rejected. Specify 0 (zero) if you want to reject any requests that are larger than 10 megabytes.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Specifies, in megabytes, the size limit for incoming HTTP requests when inbound HTTP chunking is disabled. For example, if you set the property to 35 megabytes, any HTTP requests over 35 megabytes are rejected. Specify 0 (zero) for this property if you do not want to limit the size of unchunked HTTP requests.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Specifies, in bytes, the maximum length of the response buffer used for HTTP requests. Responses larger than this value are rejected. Specify a value of 0 if you do not need a large response buffer because all of your HTTP responses are less than 10 MB.
Data Type | Integer |
Default | 104857600 |
Used by Daemon | No |
Specifies the action for the timer expiration. Set the value to SESSION to send the client a message stating that the server timed out and let the server continue running.
Data Type | String |
Default | SERVANT |
Used by Daemon | No |
Specifies the maximum length for the queue of pending connections using HTTPS. The value used can be limited by the specification of the SOMAXCONN statement in the TCP/IP Profile.
Data Type | Integer |
Default | 10 |
Used by Daemon | No |
Specifies the maximum length for the queue of pending connections using the CORBA Internet Inter-ORB protocol (IIOP). The value used might be limited by the specification of the SOMAXCONN statement in the TCP/IP profile.
Data Type | Integer |
Default | 10 |
Used by Daemon | Yes |
Specifies specify the maximum length for the queue of pending connections using IIOP Secure Sockets Layer (SSL). The value used can be limited by the specification of the SOMAXCONN statement in the TCP/IP Profile.
Data Type | Integer |
Default | 10 |
Used by Daemon | Yes |
Specifies whether to propagate the workload management (WLM) enclave that is associated with the currently dispatched request on an outbound IIOP request that was made to another server on the same z/OS system over local inter-address space communication protocols.
Data Type | Boolean |
Default | 1 |
Used by Daemon | No |
Specifies whether to perform Domain Name Server (DNS) resolution of the IP address of a foreign client to a DNS registered host name for each established IIOP session. If this property is set to 1, then the DNS host name resolution is performed. If this property is set to 0, then the DNS host name resolution is not performed, and a textual representation of the IP address of the foreign client is used instead of the DNS host name.
Data Type | boolean |
Default | 1 |
Used by Daemon | Yes |
Specifies to use an external debugger tool with the application server for tracing and debugging client and server application components such as JavaServer Pages (JSP) files, servlets, and enterprise beans.
Data Type | Boolean |
Default | false |
Used by Daemon | Yes |
Specifies whether to redirect write-to-operator (WTO) messages that use the default routing to hard copy. These messages are redirected to the location identified through the DD card on the job control language (JCL) start procedure for the server. These write to operator (WTO) messages are usually issued during initialization.
Data Type | String |
Default | empty string |
Used by Daemon | Yes |
Specifies dump options use with a CEE3DMP dump. If you want more than one option, then separate each option with a blank space. Do not change this property unless directed by IBM service personnel.
0 | No dump is generated. |
1 | A ctrace dump is taken. |
2 | A cdump dump is taken. |
3 | A csnap dump is taken. |
4 | A CEE3DMP dump is taken. |
Data Type | Integer |
Default | 3 |
Used by Daemon | Yes |
Specifies the dump options to use with a CEE3DMP dump. If you want more than one option, separate each option with a blank space. Do not change this property unless directed by IBM service personnel.
Data Type | String |
Default | THREAD(ALL) BLOCKS |
Used by Daemon | Yes |
Specifies to redirect write to operator (WTO) messages that are routed to hard copy. These messages are redirected to the location that is identified through the DD card on the server JCL start procedure. These WTO messages are primarily audit messages issued from Java code during initialization.
Data Type | String |
Default | empty string |
Used by Daemon | Yes |
Specifies the log stream that the product uses for error information. If the specified log stream is not found or not accessible, a message is issued and errors are written to the server job log. If this variable is not specified, WebSphere Application Server for z/OS uses the STDERR stream.
Data Type | String |
Default | empty string |
Used by Daemon | Yes |
Specifies the default behavior for gathering documentation about system exception minor codes.
Data Type | String |
Default | NODIAGNOSTICDATA |
Used by Daemon | Yes |
Specifies the interval of time, in minutes, that the system waits before writing the next form-feed character to standard error (SYSOUT).
If you are running on z/OS® Version
1.13 or later, and using JES2, you can use JES2 DD keywords to segment
output using the periodic writing of form-feed characters to the output
streams.
If you are running on z/OS Version
1.12 or earlier, and using JES2, to segment the output, include the
SEGMENT= parameter, along with this environment setting, on the SYSPRINT
DD statement. The value of the SEGMENT= parameter is the number of
form-feeds required before the first segment is closed and a new segment
is allocated. The SEGMENT= parameter is not supported on JES3.
Data Type | Integer |
Default | 0 |
Used by Daemon | Yes |
Specifies the interval of time, in minutes, between the writing of a form-feed character to standard output, or SYSPRINT.
If you are running on z/OS Version
1.13 or later, and using JES2, you can use JES2 DD keywords to segment
output using the periodic writing of form-feed characters to the output
streams.
If you are running on z/OS Version
1.12 or earlier, and using JES2, to segment the output, include the
SEGMENT= parameter, along with this environment setting, on the SYSPRINT
DD statement. The value of the SEGMENT= parameter is the number of
form-feeds required before the first segment is closed and a new segment
is allocated. The SEGMENT= parameter is not supported on JES3.
Data Type | Integer |
Default | 0 |
Used by Daemon | Yes |
Specifies whether time stamps in the error log display is in local time or Greenwich Mean Time (GMT). The time stamp is in GMT if this property is set to false.
Data Type | Boolean |
Default | false |
Used by Daemon | Yes |
Specifies tracing overrides for particular product subcomponents. Subcomponents, specified by numbers, receive basic and exception traces. If you specify more than one subcomponent, use parentheses and separate the numbers with commas.Do not change this property unless directed by IBM service personnel.
Data Type | String |
Default | null (empty string) |
Used by Daemon | Yes |
Specifies the number of trace buffers to allocate.
Data Type | Integer |
Valid values | 4 through 8 |
Default | 4 |
Used by Daemon | Yes |
Specifies the size of a single trace buffer in bytes. You can use the letters K, for kilobytes, or M, for megabytes.
Data Type | String |
Valid values | 128K through 4M |
Default | 1M |
Used by Daemon | Yes |
Specifies the identify of the CTRACE PARMLIB member. The value can be either a two-character suffix, which is added to the CTIBBO string to form the name of the PARMLIB member, or the fully specified name of the PARMLIB member. For example, you can use the 01 suffix, which the system resolves to CTIBBO01. A fully specified name must conform to the naming requirements for a CTRACE PARMLIB member. For details, see z/OS MVS Diagnosis: Tools and Service Aids, GA22-7589.
If this property is specified and the PARMLIB member is not found, then the default PARMLIB member, CTIBBO00, is used. If neither the specified nor the default PARMLIB member is found, then tracing is defined to CTRACE, but no connection is available to a CTRACE external writer.
Data Type | String |
Default | null (empty string) |
Used by Daemon | Yes |
Specifies the default tracing level for the product. Use this variable with the ras_trace_basic and ras_trace_detail variables to set tracing levels for product subcomponents. Do not change this property unless directed by IBM Support personnel.
0 | No tracing |
1 | Exception tracing |
2 | Basic and exception tracing |
3 | Detailed tracing, including basic and exception tracing |
Data Type | Integer |
Default | 1 |
Used by Daemon | Yes |
Specifies tracing overrides for particular product subcomponents. Subcomponents, specified by numbers, receive detailed traces. If you specify more than one subcomponent, use parentheses and separate the numbers with commas. Do not change this property unless directed by IBM Support personnel.
Data Type | String |
Default | null (empty string) |
Used by Daemon | Yes |
Specifies product trace points to exclude from tracing activity.
Trace points are specified by 8-digit, hexadecimal numbers. Do not use this property unless directed by IBM service personnel. If IBM service personnel directs you to specify more than one trace point, use parentheses and separate the numbers with commas. You also can specify a variable name by enclosing the name in single quotes.
Data Type | String |
Default | null (empty string) |
Used by Daemon | Yes |
Specifies where to send trace records. You can send trace records to the following locations:
For servers, you can specify one or more values, separated by a space.
Data Type | String |
Default | SYSPRINT BUFFER |
Used by Daemon | Yes |
Specifies tracing overrides for specific product trace points. Trace points are indicated by 8-digit, hexadecimal numbers. To specify more than one trace point, use parentheses and separate the numbers with commas. You can also specify tracing on a specific environment variable by using the name enclosed in single quotes. Do not use this property unless directed by IBMSupport personnel.
Data Type | String |
Default | null (empty string) |
Used by Daemon | Yes |
Specifies whether you want z/OS to create SMF Type 89 Subtype 2 records, in addition to SMF Type 89 Subtype 1 records. In previous releases of the product, after the product registered with z/OS, z/OS created SMF Type 89 Subtype 2 records to collect product usage data.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
Specifies whether to record the first authenticated user under request dispatch in the SM120CRE field in the System Management Facility (SMF) server activity record.
If this property is set to 1, then the first authenticated user under request dispatch is written to the SM120CRE field. If this property is set to 0, then the ID of the user under which the server activity began is written to the SM120CRE field.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
Specifies whether the servant should connect to Workload Manager (WLM) at the beginning or the end of servant initialization.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
Setting this property to 1 enables the servant to connect to WLM at the beginning of servant initialization. After the servant connects to WLM, WLM is able to classify asynchronous work that is started during the remainder of the servant initialization process. A consequence of enabling the servant to connect to WLM at the beginning of servant initialization is that when there are multiple servants defined, the servants will all start almost concurrently. Concurrent initialization of multiple servants might cause high CPU usage that needs to be taken into consideration.
Setting this property to 0 prevents any asynchronous work that is started during servant initialization from being classified by WLM because the servant does not connect to WLM until the end of the servant initialization process.
Do not use this property unless directed by IBM Support personnel.
Data Type | Integer |
Default | 128 |
Used by Daemon | No |
Specifies the Hierarchical File System (HFS) file in which Java Native Interface (JNI) and class debug messages from the Java Virtual Machine (JVM) are logged. Use this variable only in a single-server environment. If you use this property in a multiple-server environment, then all of the servers write to the same file, and you might have difficulty using the file for diagnostic purposes.
Data Type | String (file name) |
Default | empty string (no file name) |
Used by Daemon | No |
Specifies the number of transactions processed by a servant process after which the servant process is recycled. Workload management (WLM) ends the servant after all affinity requirements have been met. Specify a nonzero value to enable recycling.
You might want to enable recycling if, after running for an extended period of time, your application is experiencing out-of-memory exceptions. Out-of-memory exceptions can result from memory leakage by your application.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Specifies how long the startServer.sh command processing waits for WebSphere Application Server initialization to complete. By default, startServer.sh command processing waits indefinitely until initialization is complete.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Specifies whether WLM for z/OS is used for workload queuing.
Set this property to 1 if you are using stateless application models. With these models, application objects, such as Enterprise JavaBeans (EJBs) and HTTP sessions, are only resident in memory for the life of an individual request. In this situation, you want WLM to dynamically balance individual requests. This configuration allows linear scalability and consistent, repeatable response times.
Set this property to 0 (zero) if you are using conversational application models. With these models, a client might hold, and periodically interact with, a reference to a stateful object which is pinned in the memory of one of the JVMs for a period of time that is greater than the duration of an individual request. For example, the client might be using HTTP sessions, stateful session beans or entity beans that are maintained in memory instead of being stored in a database or file system between requests, as is done in stateless application models.
Conversational application models prevent WLM from dynamically routing individual requests in a clustered environment because the client has affinity to a specific JVM. In this situation, a round robin algorithm is used to handle the initial request from the client . This algorithm evenly distributes creation of long term affinities and is the best technique for achieving a balanced utilization of system resources under these conditions.
If you set this property to 0 for conversational application models, you must also set the server_work_distribution_algorithm property to 1.
If you want to exploit the round robin capability that WLM provides, instead of the previously described product round robin capability, seeWorkload management (WLM) for z/OS . The differences between the round robin capability that WLM provides and the product round robin capability is explained in the following scenario.
When the server_use_wlm_to_queue_work property is set to 0 (zero), the wlm_minimumSRCount and wlm_maximumSRCount properties are set to the same value. Because the work is not going through WLM, WLM only starts the number of servants that are specified for the wlm_minimumSRCount property.
0 (zero) | WLM for z/OS is not used. |
1 | WLM for z/OS is used. |
Default | 1 |
Used by Daemon | No |
Specifies the type of work distribution algorithm that the application server uses for workload balancing. This property is only used if the server_use_wlm_to_queue_work property is set to 0. If the server_use_wlm_to_queue_work property is set to 1, then the value specified for this property is ignored.
0 (zero) | The hot thread algorithm is used. This option is not recommended. |
1 | The round robin algorithm is used. This value must be specified if the server_use_wlm_to_queue_work custom property is set to 0 for conversational application models. |
Default | 0 |
Used by Daemon | No |
Indicates whether the error message BBOO0384I ERROR OCCURRED WRITING TO {0} is written to the SYSLOG when an error occurs while writing to SYSPRINT or SYSOUT.
This property can be set to 0 or 1. When this property is set to 1, this error message is written to the SYSLOG. When this property is set to 0 no message is issued.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Controls whether an ABENDDC3 or an ABENDSDC3 code is issued when a hung thread is found during the server stop process. This property disables the detection of a hung thread.
When a STOP command is issued for a server, a hung thread might fail to terminate. By default, the application server issues an ABENDDC3 or ABENDSDC3 code with a 000C000B reason code when this condition is encountered to avoid any delays and to provide a diagnostic dump earlier in the shut down process. If you set this property to 1, the application server does not abend the address space for this reason.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
Controls whether a dump is taken when an ABENDDC3 or an ABENDSDC3 code is issued because a hung thread did not stop in response to a STOP command.
When a STOP command is issued for a server, a hung thread might fail to terminate, which causes an ABENDDC3 or an ABENDSDC3 to occur with reason code 000C000B. If you set this property to 1, the application server does not take a dump if this abend occurs.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
Specifies the time, in minutes, that this controller uses to attempt to complete all restarted transactions before issuing a write-to-operator-with-reply (WTOR) message to the console, requesting whether to:
If the operator replies to continue the recovery process, then the controller attempts recovery for the specified amount of time before reissuing the write-to-operator message. After all the transactions are resolved, the controller terminates. This variable applies only to controllers that are running in peer restart and recovery mode.
Data Type | Integer |
Default | 15 |
Used by Daemon | No |
You can use the wlm_classification_file property to specify the location of your workload classification document. You can set this property at the cell, node, or server level.
The workload classification document is a common XML file that classifies inbound HTTP, IIOP, and message-driven bean (MDB) work. Any rules that are defined in this XML file override the old format HTTP classification. The rules in the common XML file also override any rules that are in the MDB classification file defined by the endpoint_config_file property.
To set this property at the cell level, in the administrative console click Environment > WebSphere Variables > New and specify wlm_classification_file in the Name field and the location of your workload classification document in the Value field.
To set this property at the node level, in the administrative console click System administration > Nodes > node_name > Custom properties > New and specify wlm_classification_file in the Name field and the location of your workload classification document in the Value field.
To set this property at the server level, in the administrative console click Servers > Application servers > server_name > Web container settings > Web container > Custom properties > New and specify wlm_classification_file in the Name field and the location of your workload classification document in the Value field.
Specifies the value that you want used for the Workload Management Service EXSTARTDEFER parameter when you use the IWMECREA Workload Management Service to create an Enclave.
See the z/OS Information Center for the version of z/OS that is running on your system for more information about the IWMECREA Workload Management Service and the EXSTARTDEFER parameter.
Data Type | String |
Default | YES |
Used by Daemon | No |
Specifies whether round robin queuing of HTTP sessions is enabled among servants. You can set this property at the cell, node, or server level.
Set this property to true if you want round robin queuing of HTTP sessions enabled among servants. Set this property to false if you do not want round robin queuing of HTTP sessions enabled among servants.
See the use of the custom property, WLMStatefulSession, for more information on the effect of using wlm_stateful_session_placement_on.
Data Type | Boolean |
Default | true |
Used by Daemon | No |