These application server custom properties are specific environment variables for optimized local adapters for z/OS®.
To set one of these environment variables 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 click .Specifies the amount of time, in seconds, that a CICS® link server waits for the next method in a transaction to arrive before unilaterally backing out the transaction.
This feature protects the link server from keeping transactional resources when the client does not return to complete a transaction, or encounters an unexpected delay when executing its business logic.
After the specified number of seconds elapses, the link server stops any transactional work done by the transaction. Future client methods driven into the backed out transaction receive an exception.
For example, if a Java 2 Enterprise Edition (J2EE) application component starts a global transaction and obtains an optimized local adapter connection, the connection is enlisted in the global transaction. The application sends a request to a CICS link server on the connection, and receives a response. If more than the number of seconds specified by this variable elapses before the next method is driven on the optimized local adapter connection, or before a backout or commit request is issued by the application server, the link server stops any work done by this connection. Transactional resources that were used by this connection are freed.
The timeout value applies to all link servers that are connected to any WebSphere® Application Server to which the variable is scoped. If the variable is set at the server scope, it applies to any link server connected to this WebSphere Application Server for z/OS instance.
Data Type | Integer |
Default | 120 |
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 Customer Information Control System (CICS) to WebSphere Application Server, the reg_flag_C2Wprop registration flag controls how the identity is determined. When this bit is turned on, the CICS application identity is used in WebSphere server authentication. When this bit 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 the variable to 1 to allow applications to use CICS task level identity. If it is undefined or set to 0 (zero), connection registrations can only request CICS region level authentication, otherwise if the reg_flag_C2Wprop registration flag is set to 1, the BBOA1REG registration request fails with a return code 8 and reason code 21. The reg_flag_W2Cprop registration flag controls WebSphere Application Server to CICS outbound transaction security propagation.
Data Type | Integer |
Default | 0 |
Used by Daemon | No |
Specifies the maximum number of connections supported for a single registration with a server in the daemon group. A connection is defined as a local communication connection between a client address space and a server within the daemon group.
When client address spaces register using the optimized local adapter Register API, the number of physical connections that the client address spaces want to make with the WebSphere Application Server address space is defined with the minimum and maximum connections parameter. To prevent any one registration request from over-running the target WebSphere Application Server with connections, the number of maximum connections for a single registration can be limited by specifying the adapter_max_conn variable.
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 must 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.
Set this to true if you want to start the daemon with this variable and enable support for the optimized local adapters. Set this 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 | False |
Used by Daemon | Yes |
Specifies 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 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 a fully qualified path and file name of an optimized local adapter trace properties file.
WebSphere Application Server reads this file during daemon initialization and in response to the F daemon,SETOLATRACEPROPS operator command. In both cases the server reads and saves the file records in the OLA Trace Properties table. When optimized local adapter registration is called, the server searches the table for an entry that matches the new registration name. If a match is found, the registration trace level is set to what is specified in the properties table entry.
Like all WebSphere Application Server environment variables, the daemon must be restarted for any changes to take effect. You can preset this to a default value of a non-existent file without negative impact to daemon initialization. When you want to set trace properties, you can then create the file and issue the modify command shown above. For details on using optimized local adapter tracing and the trace properties file see the topic, Using tracing on optimized local adapters.