Some of the application server custom properties that are provided with the product can only be used with z/OS®. This topic describes how to use these properties.
To set one of these custom properties for either an application server or a deployment manager, in the administrative console, click
, select the appropriate node or cell from the list of available servers, nodes and cells, and then click .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, respectively.
Data Type | String |
Default | Empty string |
Used by Daemon | No |
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 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 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.
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 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 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.
This property only applies 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,
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.
This property only applies 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,
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, and issues an error message that indicates that an MDB dispatch timeout has occurred.
Set this value to 0 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.
This property only applies 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,
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.
This property only applies 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,
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, idle servant worker threads are paused waiting for WLM to assign new to them. 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.
Valid values for this property are JAVACORE, SVCDUMP, and JAVATDUMP. JAVACORE generates a Java core dump. SVCDUMP generates an SVC dump. JAVATDUMP generates a JVM-initiated TDUMP.
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:
Valid values for this property are JAVACORE, SVCDUMP, and JAVATDUMP. JAVACORE generates a Java core dump. SVCDUMP generates an SVC dump. JAVATDUMP generates a JVM-initiated TDUMP.
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 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 and adjunct_jvm_direct_options custom properties to specify options that you need to pass directly to the JVM launch in the servant and adjunct, respectively.
Data Type | String |
Default | Empty string |
Used by Daemon | No |
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 | Empty string |
Used by Daemon | Yes |
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 specified for the default_internal_work_transaction_class custom property is ignored.
Data Type | String |
Default | null (empty string) |
Used by Daemon | No |
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. Omit this property if you do not want to limit the size of IIOP requests.
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 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 only request 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.
Data Type | Integer |
Default | |
Used by Daemon |
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
server_name . To change the setting of this property for a deployment manager, in the administrative console, click .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 |
Specifies whether the application server waits for a minimum number of servants to be ready to accept work before the application server starts the IIOP transport channels. If this property is set to 1, when the minimum number of servants is ready for work, then the IIOP transport channels starts accepting work. If this property is set to 0, the IIOP 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 IIOP transport channels start. To change the setting of the Minimum number of instances property for an application server, in the administrative console, click
server_name . To change the setting of this property for a deployment manager, in the administrative console, click .Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
Specifies that if the BBOO0168W message is issued, then the failure that is 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 the routing information that identifies the client.
Data Type | Boolean |
Default | false |
Used by Daemon | Yes |
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.
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) 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.
Data Type | String |
Default | 1.2 |
Used by Daemon | Yes |
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.
Data Type | Integer |
Default | 10 |
Used by Daemon | No |
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.
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, 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.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
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.
Data Type | Integer |
Default | 104857600 |
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 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.
Data Type | Boolean |
Default | 0 |
Used by Daemon | Yes |
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.
Default | SERVANT |
Used by Daemon | No |
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.
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.
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 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.
Default | SERVANT |
Used by Daemon | No |
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.
Data Type | Integer |
Default | 10 |
Used by Daemon | Yes |
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.
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 interaddress 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 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.
Data Type | Boolean |
Default | 1 |
Used by Daemon | Yes |
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.
Default | SERVANT |
Used by Daemon | No |
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.
Default | SERVANT |
Used by Daemon | No |
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.
Data Type | String |
Default | Empty string |
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 the default dump that is used by the signal handler. Do not change this property unless directed to do so by IBM® Support 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, then separate each option with a blank space. Do not change this property unless directed to do so 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 that are 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, the product uses the SYSOUT 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 |
You can also specify the following values.
CEEDUMP | Captures callback and offsets. Taking a CEE dumps is a lengthy process, and transaction time outs can occur during this process. |
TRACEBACK | Captures Language Environment® and UNIX® traceback data for the z/OS operating system. |
SVCDUMP | Captures an MVS dump, but does not produce a dump in the client. |
Specifies the interval of time, in minutes, that the system waits before writing the next form-feed character to standard error (SYSOUT).
Data Type | Integer |
Default | 0 |
Used by Daemon | Yes |
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.
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(SYSPRINT).
Data Type | Integer |
Default | 0 |
Used by Daemon | Yes |
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.
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 to do so by IBM service personnel.
Data Type | String |
Default | 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, in bytes, the size of a single trace buffer. 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 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 to do so by IBM Support personnel.
Data Type | String |
Default | 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 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.
Data Type | String |
Default | Empty string |
Used by Daemon | Yes |
Specifies where to send trace records. You can specify:
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 quotation marks. Do not use this property unless directed to do so by IBM Support personnel.
Data Type | String |
Default | 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 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, respectively.
Data Type | String |
Default | Empty string |
Used by Daemon | No |
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 > Application servers > server_name > Container services > ORB service > z/OS additional settings.
Data Type | Integer |
Range | 1 - 100 |
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.
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.
Valid values | none, svcdump, javacore, heapdump, javatdump, and traceback |
Default | traceback |
Used by Daemon | No |
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.
Valid values | none, svcdump, javacore, heapdump, and traceback. |
Default | traceback |
Used by Daemon | No |
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.
Valid values | none, svcdump, javacore, heapdump, and traceback. |
Default | traceback |
Used by Daemon | No |
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.
Valid values | none, svcdump, javacore, heapdump, and traceback. |
Default | traceback |
Used by Daemon | No |
Do not use this property unless directed to do so 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 |
Used by Daemon | No |
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.
Valid values | none, svcdump, javacore, heapdump, and traceback. |
Default | traceback |
Used by Daemon | No |
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 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, in milliseconds, the amount of CPU time that an application request can consume.
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.
After the signal is delivered on the dispatch thread, the WLM enclave, that is associated with the dispatched request, is quiesced. This situation lowers the dispatch priority of this request, and this request should now only get CPU resources when the system is experiencing a light work load.
Data type | integer |
Default | 0 |
Used by Daemon | No |
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.
Valid values | none, svcdump, javacore, heapdump, and traceback. |
Default | traceback |
Used by Daemon | No |
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.
Valid values | none, svcdump, javacore, heapdump, and traceback. |
Default | traceback |
Used by Daemon | No |
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.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
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.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
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 this is a relatively large record, and collecting the data for this record could impact performance, do not enable this property unless you have a specific reason for collecting the data that is included in this record.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
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.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
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.
Data Type | Boolean |
Default | 0 |
Used by Daemon | No |
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.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
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™ (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 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 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 exploit 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.
0 | The z/OS WLM function is not used. |
1 | The z/OS WLM function 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 | The hot thread algorithm is used. When the hot thread algorithm is used, each new work request is assigned to the first servant that has a thread available to process the request. If none of the servants have an available thread, the request is queued into the global work queue that all of the servants share. The request is then selected from the global work queue when the next thread becomes available, regardless of which servant owns that thread. The goal of the hot thread algorithm is to route requests to the fewest number of servants possible. If the number of concurrent requests is not greater than the number of threads in a servant, all requests are processed by the same servant. |
1 | The round robin algorithm is used. When the round robin algorithm is used, new work requests are distributed evenly across all servants. If all of the servant threads are already processing other work requests, the new request is added to the request queue for a specific servant. The queued request is then selected when it becomes the top request in the queue and a thread becomes available in that servant. |
|
|
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 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.
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 complete one of the following options:
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 |
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 how a server, that is configured to start more than one servant address space, starts these address spaces.
Data Type | Boolean |
Default | 0 |
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 |
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.
Data Type | Boolean |
Default | 1 |
Used by Daemon | No |
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.
Data Type | Boolean |
Default | 1 |
Used by Daemon | No |
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.
Data Type | Integer |
Default | |
Used by Daemon | Yes |
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.
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.
Data Type | Integer |
Default | 100 |
Used by Daemon | Yes |
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.
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 32M (33554432).
Data Type | Integer |
Default | 32M |
Used by Daemon | Yes |
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.
Data Type | Boolean |
Default | true |
Used by Daemon | Yes |