Application server custom properties for z/OS

Specifies options that you need to pass directly to the Java virtual machine (JVM) launch in the adjunct. This property is typically used for JVM options that the JVM cannot read from the options file that is specified as the value of the control_region_jvm_properties_file property. For example, the JVM cannot read the value that is specified for the -memorycheck option in the options file.

If you specify multiple options, use a semicolon to separate the options.

You can use the servant_jvm_direct_options and control_jvm_direct_options custom properties to specify options that you need to pass directly to the JVM launch in the servant and controller.

Specifies what action takes place when a critical messaging engine takes too long to start.

If you set this property to 0, warning message BBOO0418W is issued.

If you set this property to 1, the entire application server abnormally terminates.

Specifies how many seconds the server start process waits for a critical messaging engine to become active.

This variable applies only if the adjunct_region_start_synchronized environment variable is set to 1. This property controls how long the start process waits for both the adjunct region and the critical messaging engine to start. A value of 0 disables the timeout, and the start process waits indefinitely for the adjunct region and the critical messaging engine to start.

Specifies whether the startup process waits for all critical messaging engines to start before opening for e-business.

If you set this property to 1, the startup process waits for all critical messaging engines to start before starting to process e-business applications.

If you set this property to 0, the startup process does not wait for the critical messaging engines to start.

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 that is 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.

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 delivered again.

Specifies whether to condense Java trace or to show it in the old style which includes category information. The default is to condense the trace.

When this property is set to 1, java trace is condensed.

When this property is set to 0, java trace is expanded.

Specifies whether requests are dispatched to servants after 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 server 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.

Specifies whether the controller rejects requests for dispatch within a servant when it detects that no servants are available to process requests.

When this property is set to 1, if the controller detects that there are no servants available to process requests, it rejects requests for dispatch within the servants. It also removes the application server from the registry of servers that workload management (WLM) uses to assign work, and stops the HTTP and message-driven bean (MDB) listeners. If this property is set to 0, then the function is disabled.

When the minimum number of servants become available, the controller registers the application server with WLM again, starts the HTTP and MDB listeners, and allows requests to be dispatched to the servants.

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 occurred.

The queue_timeout_percent request-level Reliability Availability and Serviceability (RAS) attribute overrides the control_region_http_queue_timeout_percent custom property for HTTP requests. You define the request-level RAS attributes in the workload classification file.

Specifies the percentage of the HTTPS dispatch time limit that is used as the maximum amount of time that an HTTPS 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 HTTPS request can spend on the queue and in dispatch before an error message is issued, which indicates that an HTTPS dispatch timeout occurred.

The queue_timeout_percent request-level RAS attribute overrides the control_region_https_queue_timeout_percent custom property for HTTPS requests. You define the request-level RAS attributes in the workload classification file.

This property applies only to a Websphere Application Server configured with a servant. This property specifies whether HTTP requests on the WLM Queue can be requeued to any available servant.

When this property is set to 1, HTTP requests waiting on the WLM queue with an affinity to a servant that is marked for termination can be requeued to any available servant when the servant with affinity terminates.

When this property is set to 0 (zero), the server fails any HTTP requests on the WLM queue with an affinity to a servant that is marked for termination immediately. Also, the server fails any new HTTP request with affinity to the unhealthy servant.

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.

This property applies only to the time that the request spends on the WLM queue. Use the control_region_wlm_dispatch_timeout custom property if you want to limit the amount of time that the request spends on both the WLM queue and in dispatch,

The queue_timeout_percent request-level RAS attribute overrides the control_region_iiop_queue_timeout_percent custom property for IIOP requests. You define the request-level RAS attributes in the workload classification file.

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.

This property applies only to the time that the request spends on the WLM queue. Use the control_region_mdb_request_timeout custom property if you want to limit the amount of time that the request spends on both the WLM queue and in dispatch,

The queue_timeout_percent request-level RAS attribute overrides the control_region_mdb_queue_timeout_percent custom property for MDB requests. You define the request-level RAS attributes in the workload classification file.

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, and issues an error message that indicates that an MDB dispatch timeout occurred.

The request_timeout request-level RAS attribute overrides the control_region_mdb_request_timeout custom property for MDB requests. You define the request-level RAS attributes in the workload classification file.

Set this value to 0 to disable the function.

Specifies the number seconds the controller waits before it checks for servants with hung threads that need to be abended.

When this property is set to the default of 0, servants with hung threads are not abended. For any value other than 0, the controller waits a number of seconds that is equal to the value before it checks for servants with hung threads that need to be abended. The abend code that is issued is EC3 with reason code 042B0001.

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.

This property applies only to the time that the request spends on the WLM queue. Use the protocol_sip_timeout_output custom property if you want to limit the amount of time that the request spends on both the WLM queue and in dispatch.

The queue_timeout_percent request-level RAS attribute overrides the control_region_sip_queue_timeout_percent custom property for MDB requests. You define the request-level RAS attributes in the workload classification file.

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.

This property applies only to the time that the request spends on the WLM queue. Use the protocol_sips_timeout_output custom property if you want to limit the amount of time that the request spends on both the WLM queue and in dispatch.

The queue_timeout_percent request-level RAS attribute overrides the control_region_sips_queue_timeout_percent custom property for MDB requests. You define the request-level RAS attributes in the workload classification file.

Specifies the maximum number of threads that the controller region worker thread pool can grow to.

The pool starts at control_region_thread_pool_size and grows to control_region_thread_pool_maximum_size. When control_region_thread_pool_maximum_size is set to 0, the maximum number of worker threads are calculated based on the number of servants and the number of threads in each servant.

If the calculated value is less than control_region_thread_pool_size, then control_region_thread_pool_size is used as the maximum. If the calculated value is greater than 100, then 100 is used as the maximum. When specifying a maximum, ensure that there are enough resources available to support the specified maximum. An example of a resource to consider is the JVM heap size.

Specifies the number of seconds a controller waits after detecting a timeout before it terminates the servant. This time delay gives work that is 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.

Specifies the type of dump that is taken whenever a timeout occurs for work that is dispatched to a servant. This property applies only applies if the control_region_timeout_delay custom property is set to a non-zero value.

Valid values for this property are SVCDUMP, JAVACORE, HEAPDUMP, TRACEBACK, JAVATDUMP, and NONE. JAVACORE generates a Java core dump. SVCDUMP generates an SVC dump. JAVATDUMP generates a JVM-initiated TDUMP.

Specifies the type of dump that is taken whenever a timeout occurs for an HTTP, HTTPS, SIP, or SIPS request that is dispatched to a servant.

This property applies only if the following corresponding variable is set to SESSION:

• protocol_http_timeout_output_recovery
• protocol_https_timeout_output_recovery
• protocol_sip_timeout_output_recovery
• protocol_sips_timeout_output_recovery

Valid values for this property are SVCDUMP, JAVACORE, HEAPDUMP, TRACEBACK, JAVATDUMP, and NONE. JAVACORE generates a Java core dump. SVCDUMP generates an SVC dump. JAVATDUMP generates a JVM-initiated TDUMP.

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.

Specifies options that you need to pass directly to the JVM launch in the controller. This property is typically used for JVM options that the JVM cannot read from the options file that is specified as the value of the control_region_jvm_properties_file property. For example, the JVM cannot read the value that is specified for the -memorycheck option in the options file.

If you specify multiple options, use a semicolon to separate the options.

You can use the servant_jvm_direct_options to specify options that you need to pass directly to the JVM launch in the servant. You can use the adjunct_jvm_direct_options custom properties to specify options that you need to pass directly to the JVM launch in the adjunct.

Specifies the identity 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 the specified PARMLIB member is not found, then tracing is defined to CTRACE, but no connection is available to a CTRACE external writer.

Specifies the default transaction class for internally processed work within the server.

If an internal classification element is not listed in the wlm_classification_file, or if the wlm_classification_file is not specified, then the default_internal_work_transaction_class setting is used. If a value is specified for internal classification setting listed in the wlm_classification_file, the value that is specified for the default_internal_work_transaction_class custom property is ignored.

Specifies that value that you want passed to the z/OS Workload Manager (WLM) as the SELECT_POLICY parameter of the IWMAEDEF service.

The IWMAEDEF service is used to create the dynamic application environment for the selection of work from the WLM queue. For more information about this service, see the z/OS WLM documentation for your version of the z/OS operating system.

Specifies, in megabytes, the maximum size for IIOP requests. For example, if you set the property to 35, then any requests over 35 MB are rejected. The minimum value for this property is 10, and the maximum value is 2048. Set the value to 0 or omit this property if you do not want to limit the size of IIOP requests.

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.

Specifies the number of threads available for the servant region internal work thread pool. Set this property to the number of threads you would like available for the servant region internal work thread pool.

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 MB are rejected. The minimum value for this property is 10 and the maximum value is 2048. Set the value to 0 or omit this property if you do not want to limit the size of locally connected communications requests.

Specifies permission for CICS application level identities to be used for authentication when the registration request is made.

When an application requests an optimized local adapter registration, the programmer can use two security-related bits in the registration flags structure to control identity propagation. For transactions that are inbound from CICS to WebSphere Application Server, bit 29 (x'00',x'00',x'00',x'04') controls how the identity is determined. When this property is turned on, the CICS application identity is used in WebSphere server authentication. When this property is turned off , the CICS region identity is used.

WebSphere Application Server administrators must set the environment variable to permit CICS application level identities to be used for authentication when the registration request is made. Set the value of to 1 to allow the use of CICS task level identity. If it is undefined or set to 0 (zero), registration requests can request only CICS region level authentication, otherwise if registration flag bit 29 is set to 1, the BBOA1REG registration request fails with a return code 8 and reason code 21. Bit 21 (x'00',x'00',x'00',x'01') controls outbound transaction security propagation. See outbound transactions for information.

Specifies whether to pause and resume the Activation Specification listeners when the MODIFY commands, PAUSELISTENERS and RESUMELISTENERS, are invoked.

This inclusion applies to other means of pausing listeners as well, such as autopause. The default is not to include the Activation Specification listeners when pausing listeners.

When this property is set to 1, the Activation Specification listeners are included among the paused listeners.

When this property is set to 0, the Activation Specification listeners are not included among the paused listeners.

Specifies whether the application server waits until a minimum number of servants are 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 are 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 Servers > Server Types > WebSphere application servers > server_name > 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.

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.

Specifies that if the BBOO0168W message is issued, then the failure that is detected when it attempts 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 the routing information that identifies the client.

Specifies that if the BBOO0169W message is issued, 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 the routing information that identifies the client.

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) that are exported from this server use the GIOP level indicated.

You might need to change the setting of this property from the default value if you use a client ORB that is not shipped as part of the product, and that supports a previous 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 a client ORB that supports the 1.1 CORBA standard instead of the 1.2 CORBA standard.

Specifies the maximum length for the queue of pending connections using HTTP. The value that you specify can be limited by the specification of the SOMAXCONN statement in the TCP/IP profile.

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 MB are rejected. Specify 0 to reject any requests that are larger than 10 MB.

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, any HTTP requests over 35 MB are rejected. Specify 0 for this property if you do not want to limit the size of unchunked HTTP requests.

Specifies, in bytes, the maximum length of the response buffer that is 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.

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 HTTP 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.

Specifies the recovery action that is taken when an HTTP request does not complete within a designated length of time. Setting this property to SERVANT allows servants to terminate when a timeout occurs. If an HTTP request is under dispatch in a servant when its timeout value is reached, the servant terminates with an ABEND EC3 RSN=04130007. The HTTP request and socket are then cleaned up. If this property is set to SESSION, no attempt is made to disrupt the processing of a dispatched HTTP request within a servant. However, the HTTP request and socket are still cleaned up. Using the SESSION setting might result in a loss of resources if the dispatched HTTP request loops or becomes inactive.

The timeout_recovery request-level RAS attribute overrides the protocol_http_timeout_output_recovery custom property for HTTP requests. You define the request-level RAS attributes in the workload classification file.

Specifies the maximum length for the queue of pending connections using HTTPS. The value that you specify can be limited by the specification of the SOMAXCONN statement in the TCP/IP Profile.

Specifies the name of a file with 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.

Specifies the label of the server certificate that the application server uses to establish 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 the recovery action that is taken when an HTTPS request does not complete within a designated length of time. Setting this property to SERVANT allows servants to terminate when a timeout occurs. If an HTTPS request is under dispatch in a servant when its timeout value is reached, the servant terminates with an ABEND EC3 RSN=04130007. The HTTPS request and socket are then cleaned up. If this property is set to SESSION, no attempt is made to disrupt the processing of a dispatched HTTPS request within a servant. However, the HTTPS request and socket are still cleaned up. Using the SESSION setting might result in a loss of resources if the dispatched HTTPS request loops or becomes inactive.

The timeout_recovery request-level RAS attribute overrides the protocol_https_timeout_output_recovery custom property for HTTPS requests. You define the request-level RAS attributes in the workload classification file.

Specifies the maximum length for the queue of pending connections using the CORBA Internet Inter-ORB Protocol (IIOP). The value that you specify might be limited by the specification of the SOMAXCONN statement in the TCP/IP profile.

Specifies the maximum length for the queue of pending connections using IIOP Secure Sockets Layer (SSL). The value that you specify can be limited by the specification of the SOMAXCONN statement in the TCP/IP profile.

Specifies whether WebSphere Application Server should enable the process that allows it to receive input from the Workload Manager (WLM) to make IIOP routing decisions.

When this property is enabled, WLM sends WebSphere Application Server input that WebSphere Application Server uses to make IIOP routing decisions.

BBOO0037E Function IWMSRCRR failed with RC=8, REASON=00000868

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 interaddress space communication protocols.

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 o, 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.

Specifies whether, if possible, the application server resolves the object URLs to a server that is local to the LPAR. By default, the object URL is processed in order and the first server that can be reached is chosen. When this property is set to 1, any servers local to the LPAR are checked first and only if none of those servers are reachable is a resolution attempted to a remote server.

Specifies the number of messages that can reside on the JFAP protocol message queue that is associated with a servant process. This queue is used to hold pending messages that are being sent between the servant process and the controller.

You can specify any positive integer as the value for this property. However, whenever possible, use the default value 0. A value of 0 indicates that the number of messages that can reside in the JFAP protocol message queue is four times the number of dispatch threads in the servant. Therefore, this value provides a calculated limit based on workload, and removes the arbitrary restraints imposed by specifying a specific value for this property.

The number of dispatch threads in the servant is controlled by the ORB services Workload profile setting. See the topic ORB services advanced settings on the z/OS platform for more information about this setting.

Review the topic Configuring MDB throttling for the default messaging provider for a description of how to tune message-driven beans.

Specifies the recovery action that is taken when a SIP request does not complete within a designated length of time. Setting this property to SERVANT allows servants to terminate when a timeout occurs. If a SIP request is under dispatch in a servant when its timeout value is reached, the servant terminates with an ABEND EC3 RSN=04130007. The SIP request and socket are then cleaned up. If this property is set to SESSION, no attempt is made to disrupt the processing of a dispatched SIP request within a servant. However, the SIP request and socket are still cleaned up. Using the SESSION setting might result in a loss of resources if the dispatched SIP request loops or becomes inactive.

The timeout_recovery request-level RAS attribute overrides the protocol_sip_timeout_output_recovery custom property for SIP requests. You define the request-level RAS attributes in the workload classification file.

Specifies the recovery action that is taken when a SIPS request does not complete within a designated length of time. Setting this property to SERVANT allows servants to terminate when a timeout occurs. If a SIPS request is under dispatch in a servant when its timeout value is reached, the servant terminates with an ABEND EC3 RSN=04130007. The SIPS request and socket are then cleaned up. If this property is set to SESSION, no attempt is made to disrupt the processing of a dispatched SIPS request within a servant. However, the SIPS request and socket are still cleaned up. Using the SESSION setting might result in a loss of resources if the dispatched SIPS request loops or becomes inactive.

The timeout_recovery request-level RAS attribute overrides the protocol_sips_timeout_output_recovery custom property for SIPS requests. You define the request-level RAS attributes in the workload classification file.

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.

Specifies whether to redirect write-to-operator (WTO) messages that use the default routing to SYSPRINT. These messages are redirected to the location identified through the DD card on the JCL start procedure for the server. These WTO messages are typically issued during initialization.

Specifies the default dump that is used by the signal handler. Do not change this property unless directed to do so by IBM Support personnel.

Specifies the dump options to 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 to do so by IBM service personnel.

Specifies whether FFDC logs should be generated when a trace is truncated because its size exceeds the length of internal buffers producing the trace.

Truncated trace entries in the logs show a BUFFER_OVERFLOW message at the end of the trace. By default, when truncated traces are written, corresponding FFDC logs are generated to provide a way to access all the information in the trace.

Set the value to 0 to disable to creation of FFDC logs.

Specifies the level of diagnostic information that the application server collects. Reducing the value of this property increases the performance of the application server. However, less data is available to IBM Support personnel when diagnosing a problem. The opposite is true when increasing the value of this property. The default value of 5 provides a balance of performance and diagnostic information.

Specifies the version of trace log to display. Valid values are 1 through 3. Version 3 displays a message tag that is defined in the classification file if an application request is associated with the current thread at the time the error occurs, in addition to previous version information. Version 2 displays the server name, cluster name, and cell name, in addition to the base information. For example, ras_error_log_version=2.

Specifies to redirect write-to-operator (WTO) messages that are routed to hardcopy. 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 that are issued from Java code during initialization.

Specifies the type of diagnostic action that is performed when a Java virtual machine out-of-memory condition occurs.

Specifies, in seconds, the length of time during which the diagnostic action specified by the ras_java_oom_action environment variable is not repeated. This property helps to limit the number of diagnostic actions that occur for related out-of-memory conditions.

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, the product uses the SYSOUT stream.

Specifies the buffer size to be used for trace processing. The buffer size default value of 16384 is also the minimum allowed buffer size. If the trace is larger than the set value, a BUFFER_OVERFLOW message is printed at the end of the truncated trace.

Specifies a comma-delimited list of WebSphere Application Server message IDs to be rerouted to the operator console (route code 2). Each message displays in the operator console, instead of in the default location.

Specifies a comma-delimited list of WebSphere Application Server message IDs to be copied to the operator console. Each message displays in both the operator console and the default location.

Specifies a comma-delimited list of WebSphere Application Server message IDs to be copied to the errorlog. Each message displays in both the errorlog and the default location.

Specifies a comma delimited list of WebSphere message IDs to be rerouted to hardcopy (route code 11). Each message shows up in the hardcopy as well as in its default location.

Specifies a comma-delimited list of WebSphere Application Server message IDs to be rerouted to the error log. Each message displays in the error log, rather than its default location.

Specifies a comma delimited list of WebSphere message IDs to be rerouted to hardcopy (route code 11). Each message shows up in the hardcopy instead of in its default location.

Specifies a comma-delimited list of WebSphere Application Server message IDs to be ignored. Each message is hidden from one or more normal output locations.

Specifies the default behavior for gathering documentation about system exception minor codes.

You can also specify the following values.

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.

Specifies the number of lines of output that is written between the writing of form-feed characters to standard error (SYSOUT).

Because of uncontrollable factors, such as line wrapping, the product can only approximate the number of lines of output it has written. Therefore the actual number of lines written between the writing of form-feed characters might be plus or minus 5 percent of the value specified for the property.

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.

Specifies the interval of time, in minutes, between the writing of a form-feed character to standard output(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.

Specifies the number of lines of output between the writing of form-feed characters to standard output (SYSPRINT).

Because of uncontrollable factors, such as line wrapping, the product can only approximate the number of lines of output it has written. Therefore the actual number of lines written between the writing of form-feed characters might be plus or minus 5 percent of the value specified for the property.

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.

Specifies whether messages that are written to the operator console are tagged, if appropriate. Valid values are 0 and 1. For example, ras_tag_wto_messages=0.

Specifies whether time stamps in the error log display are in local time or Greenwich Mean Time (GMT). The time stamp is in GMT if this property is set to false.

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 to do so by IBM service personnel.

Specifies the number of trace buffers to allocate.

Specifies, in bytes, the size of a single trace buffer. You can use the letters K, for kilobytes, or M, for megabytes.

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.

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 to do so by IBM Support personnel.

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 to do so 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 quotation marks.

Specifies the version of trace log to display. Valid values are 1 and 2. Version 2 displays a message tag that is defined in the classification file if an application request is associated with the current thread at the time the trace is issued. For example, ras_trace_log_version=1.

Specifies where to send trace records. You can specify:

For servers, you can specify one or more values, separated by a space.

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 quotation marks. Do not use this property unless directed to do so by IBM Support personnel.

Specifies the output directory on the Unix Systems Services (USS) file system to which redirected servant output files are to be written. Only the SYSPRINT and SYSOUT DD cards are redirected.

This value must be an absolute path to an existing directory with appropriate write permissions. If a valid value is not specified for this variable, by default, output is redirected to DD cards.

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.

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.

Specifies options that you need to pass directly to the JVM launch in the servant. This property is typically used for Java virtual machine (JVM) options that the JVM cannot read from the options file that is specified as the value of the control_region_jvm_properties_file property. For example, the JVM cannot read the value that is specified for the -memorycheck option in the options file.

If you specify multiple options, use a semicolon to separate the options.

You can use the controller_jvm_direct_options and adjunct_jvm_direct_options custom properties to specify options that you need to pass directly to the JVM launch in the controller and adjunct.

Specifies the number of application threads that are used in each of the servants that are running in an application server.

If you specify a value for this custom property, you must set the Workload profile property on the ORB services z/OS additional settings page in the administrative console to CUSTOM before this setting becomes effective. To navigate to this page, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Container services > ORB service > z/OS additional settings.

Specifies whether product DLLs are loaded from the Hierarchical File System (HFS) or from the STEPLIB, LPA, or link list.

Setting this property to 1 (the default) indicates that the DLLs are loaded from the HFS. Setting this property to 0 indicates that the DLLs are put into the STEPLIB, LPA, or link list.

Specifies whether the servant connects to Workload Manager (WLM) at the beginning or the end of servant initialization.

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 all start almost concurrently. Concurrent initialization of multiple servants might cause high CPU usage that needs to be considered.

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.

Specifies the dump action that the server takes when requests exceed their CPU timeout specified on the server_region_request_cputimeused_limit custom property.

The cputimeused_dump_action request-level RAS attribute overrides the server_region_cputimeused_dump_action custom property for HTTP, IIOP, SIP, MDB, and optimized local adapter requests. You define the request-level RAS attributes in the workload classification file.

Specifies the type of dump that is taken when the dispatch progress monitor (DPM) interval has expired for a request. After the dump is taken the DPM interval is reset.

The dpm_dump_action request-level RAS attribute overrides the server_region_dpm_dump_action custom property. You define the request-level RAS attributes in the workload classification file.

Specifies the type of dump that is taken when a request is considered unresponsive. After the dump is taken the controller is notified of the unresponsive request. The controller might then terminate the servant based on the values specified for other custom properties, such as server_region_stalled_thread_threshold_percent, control_region_timeout_delay, and control_region_timeout_save_last_servant.

The stalled_thread_dump_action request-level RAS attribute overrides the server_region_http_stalled_thread_dump_action custom property. You define the request-level RAS attributes in the workload classification file.

Specifies the type of dump that is taken when a request is considered unresponsive. After the dump is taken the controller is notified of the unresponsive request. The controller might then terminate the servant based on the values specified for other custom properties, such as server_region_stalled_thread_threshold_percent, control_region_timeout_delay, and control_region_timeout_save_last_servant.

The stalled_thread_dump_action request-level RAS attribute overrides the server_region_ https_stalled_thread_dump_action custom property. You define the request-level RAS attributes in the workload classification file.

Specifies the type of dump that is taken when a request is considered unresponsive. After the dump is taken the controller is notified of the unresponsive request. The controller might then terminate the servant based on the values specified for other custom properties, such as server_region_stalled_thread_threshold_percent, control_region_timeout_delay, and control_region_timeout_save_last_servant.

The stalled_thread_dump_action request-level RAS attribute overrides the server_region_ iiop_stalled_thread_dump_action custom property. You define the request-level RAS attributes in the workload classification file.

Do not use this property unless directed to do so by IBM Support personnel.

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.

Specifies the type of dump that is taken when a request is considered unresponsive. After the dump is taken the controller is notified of the unresponsive request. The controller might then terminate the servant based on the values specified for other custom properties, such as server_region_stalled_thread_threshold_percent, control_region_timeout_delay, and control_region_timeout_save_last_servant.

The stalled_thread_dump_action request-level RAS attribute overrides the server_region_mdb_stalled_thread_dump_action custom property for MDB requests. You define the request-level RAS attributes in the workload classification file.

Specifies the number of transactions that are processed by a servant process after which the servant process is recycled. Workload management (WLM) ends the servant after all affinity requirements are met. Specify a nonzero value to enable recycling.

You might want to enable recycling if, after running for an extended period, your application is experiencing out-of-memory exceptions. Out-of-memory exceptions can result from memory leakage by your application.

Specifies, in milliseconds, the amount of CPU time that an application request can consume.

The server_region_request_cputimeused_limit custom property helps you to prevent a single application request from monopolizing the available CPU time because it allows you to limit the amount of CPU time that a single request can use. A CPU monitor is invoked when a request is dispatched. If the request exceeds the specified amount of CPU time, the controller considers the request unresponsive. The controller then issues message BBOO0327 to let the requesting application know that the request was unresponsive.

The monitor that monitors the amount of CPU time that a request is using typically sends a signal to the dispatched thread when the amount of CPU time used exceeds the specified amount. However, there are situations when this signal cannot be delivered, and the request remains pending. For example, if the thread goes native and invokes a PC routine, the signal remains pending until the PC routine returns.

The cputimeused_limit request-level RAS attribute overrides the server_region_request_cputimeused_limit custom property for HTTP, IIOP, SIP, MDB, and optimized local adapter requests. You define the request-level RAS attributes in the workload classification file.

Specifies the type of dump that is taken when a request is considered unresponsive. After the dump is taken the controller is notified of the unresponsive request. The controller might then terminate the servant based on the values specified for other custom properties, such as server_region_stalled_thread_threshold_percent, control_region_timeout_delay, and control_region_timeout_save_last_servant.

The stalled_thread_dump_action request-level RAS attribute overrides the server_region_sip_stalled_thread_dump_action custom property. You define the request-level RAS attributes in the workload classification file.

Specifies the type of dump that is taken when a request is considered unresponsive. After the dump is taken the controller is notified of the unresponsive request. The controller might then terminate the servant based on the values specified for other custom properties, such as server_region_stalled_thread_threshold_percent, control_region_timeout_delay, and control_region_timeout_save_last_servant.

The stalled_thread_dump_action request-level RAS attribute overrides the server_region_sips_stalled_thread_dump_action custom property. You define the request-level RAS attributes in the workload classification file.

Specifies the percentage of threads that can become unresponsive before the controller terminates the servant.

If 0 is specified, the controller terminates the servant as soon as the controller determines that at least one thread has become unresponsive.

Specifies whether you want a z/OS System Management Facility (SMF) 120 Subtype 10 record created for WebSphere Optimized Local Adapter outbound requests.

If you specify 1 for this property, an SMF 120 Subtype 10 record is created.

Collecting the data for this record might impact performance; do not enable this property unless you have a specific reason for collecting the data that is included in this record.

Specifies whether you want the asynchronous data section included in SMF 120 Subtype 9 records that are created.

If this property is set to true, the asynchronous data section is included in any SMF 120 Subtype 9 record that is created during asynchronous work.

The setting for this property is ignored if the server_SMF_request_activity_enabled property is set to false.

Specifies whether you want the CPU usage breakdown section included in any SMF 120 Subtype 9 record that is created.

If this property is set to true, the CPU usage breakdown section is included in any SMF 120 Subtype 9 record that is created.

The setting for this property is ignored if the server_SMF_request_activity_enabled property is set to false.

The SMF_request_activity_CPU_detail request-level RAS attribute overrides the server_SMF_request_activity_CPU_detail custom property for HTTP requests and IIOP requests. You define the request-level RAS attributes in the workload classification file.

Specifies whether you want the z/OS System Management Facility (SMF) to create an SMF 120 Subtype 9 record.

If you specify true for this property, an SMF 120 Subtype 9 record is created. Because the record is a relatively large, and collecting the data for this record could have an impact on performance, do not enable this property unless you have a specific reason for collecting the data that is included in this record.

The SMF_request_activity_enabled request-level RAS attribute overrides the server_SMF_request_activity_enabled custom property for HTTP requests and IIOP requests. You define the request-level RAS attributes in the workload classification file.

Specifies whether you want the Security data section included in any SMF 120 Subtype 9 record that is created.

If this property is set to true, the Security data section is included in any SMF 120 Subtype 9 record that is created.

The setting for this property is ignored if the server_SMF_request_activity_enabled property is set to false.

The SMF_request_activity_security request-level RAS attribute overrides the server_SMF_request_activity_security custom property for HTTP requests and IIOP requests. You define the request-level RAS attributes in the workload classification file.

Specifies whether you want the z/OS formatted timestamps section included in any SMF 120 Subtype 9 record that is created.

If this property is set to true, the z/OS formatted timestamps section is included in any SMF 120 Subtype 9 record that is created.

The setting for this property is ignored if the server_SMF_request_activity_enabled property is set to false.

The SMF_request_activity_timestamps request-level RAS attribute overrides the server_SMF_request_activity_timestamps custom property for HTTP requests and IIOP requests. You define the request-level RAS attributes in the workload classification file.

Specifies how long the startServer.sh command processing waits for the product initialization process to complete. By default, startServer.sh command processing waits indefinitely until initialization is complete.

Specifies whether WLM 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 (EJB) 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 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 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 the creation of long-term affinities and is the best technique for achieving a balanced utilization of system resources in this type of environment. 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 prefer, you can use the round-robin capability that WLM provides, instead of the previously described product round-robin capability. 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, 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.

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.

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.

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 shutdown process. If you set this property to 1, the application server does not abend the address space for this reason.

Controls whether a dump is taken when an ABENDDC3 or an ABENDSDC3 occurs because a hung thread did not terminate 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. Setting this property to 1 prevents a dump from being taken if this abend occurs.

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 complete one of the following options:

• Continue the recovery process.
• Stop trying to resolve all restart transactions.
• Write transaction-related information to the job log or hard copy log.
• Terminate.

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.

Specifies the maximum number of connections supported for a daemon group. A connection is defined as a local communication connection between a client address space and a server within the daemon group.

As client address spaces register with the optimized local adapter APIs, the number of physical connections that the client address spaces want to make with the WebSphere address space is defined. To prevent the connectors from over-running the WebSphere Application Server with requests, the number of connections across the entire daemon group can be set to a maximum number by specifying the adapter_max_conn variable.

If a subsystem connects to the WebSphere server and requests a number of connections that is the maximum for the daemon group, the register request fails with a reason code that indicates that the maximum number of connections has been reached.

The maximum number of physical connections between the WebSphere Application Server and external address spaces is set on the connection factory.

Specifies support for an optimized local adapter. Support is enabled when this variable is used to start the daemon.

The WebSphere daemon needs to know whether this daemon group is going to support the optimized local adapters, since it manages the shared storage used by the WebSphere server and the associated address spaces. All daemon configuration exists in the was.env file for the daemon. The daemon does not have a JVM. Therefore it does not have access to the WCCM model.

This variable sets the maximum number of adapter outbound services that can be active for a single registration. When the value is not specified, it defaults to 100.

Specifies support for an optimized local adapter. Support is enabled when this variable is used to start the daemon.

The WebSphere daemon needs to know whether this daemon group is going to support the optimized local adapters, since it manages the shared storage used by the WebSphere server and the associated address spaces. All daemon configuration exists in the was.env file for the daemon. The daemon does not have a JVM, therefore it does not have access to the WCCM model.

This variable sets the maximum size of the adapters shared 64-bit memory for adapters control structures for the daemon group. When this value is not specified, it defaults to 32 M (33554432).

Specifies support for an optimized local adapter. Support is enabled when this variable is used to start the daemon.

The WebSphere daemon needs to know whether or not this daemon group is going to support the optimized local adapters, since it manages the shared storage used by the WebSphere server and the associated address spaces. All daemon configuration exists in the was.env file for the daemon. The daemon does not have a JVM, therefore it does not have access to the WCCM model.

Set this property to true if you want to start the daemon with this variable and enable support for the optimized local adapters. Set this property to false if you do not want to start the daemon with this variable and enable support for the optimized local adapters.

Specifies the setting of the AE_SPREADMIN parameter on the IWM4SLIP service, which you use for servant address spaces. The IWM4SLIP service is the application environment limit service for workload management (WLM) on the z/OS system. The AE_SPREADMIN parameter indicates how WLM distributes the minimum number of servants across the service classes being used to process work requests.

• If you specify 1 for this property, the application server sets the AE_SPREADMIN parameter to YES. WLM distributes the number of servants specified on the Minimum Number of Instances field as evenly as possible to all service classes being used to run work requests.
• If you specify 0 for this property, the application server sets the AE_SPREADMIN parameter to NO. WLM distributes the number of servants specified on the Minimum Number of Instances to service classes as needed in order to meet goals.

Read the topic on controlling the minimum and maximum number of servants for more information about setting the Minimum Number of Instances field.

Specifies 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.

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 documentation 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.

Specifies the increment amount provided to the z/OS Workload Managers Health API (IWM4HLTH) at the interval specified for the wlm_health_interval custom property.

If the value specified for the wlm_health_interval custom property is 0, a value of 100 is used for the wlm_health_increment custom property.

Specifies the amount of time, in seconds, between calls to the z/OS Workload Managers Health API (IWM4HLTH).

The health value provided increments for each call to the WLM health API by the value specified for the wlm_health_increment custom property. If the value for the wlm_health_interval custom property is 0, an increment value of 100 is used when updating the servers health value. The initial health value of the server is set to 0 during initialization. The servers health value is updated at the intervals defined by the value specified for the wlm_health_interval custom property. The first interval starts when the deferred listeners for the server are started. See the description of the protocol_accept_http_work_after_min_srs custom property for additional information.

Specifies how a server that is configured to start more than one servant address space starts these address spaces.

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.

Specifies whether a Java heap dump is generated, in addition to a Java core dump when you issue the wsadmin dumpThreads command.

Set this property to 1 if you want a Java heap dump generated when you issue the wsadmin dumpThreads command. Set this property to 0 if you do not want a Java heap dump generated when you issue the wsadmin dumpThreads command.

Specifies whether a system TDUMP is generated, in addition to a Java core dump when you issue the wsadmin dumpThreads command.

Set this property to 1 if you want a system TDUMP generated when you issue the wsadmin dumpThreads command. Set this property to 0 if you do not want a system TDUMP generated when you issue the wsadmin dumpThreads command.