Service Level Build Level cf

Transcription

1 Service Level Build Level cf HOLD(UK24627) SYS FMID(H28W610) REASON(ACTION) DATE(07173) COMMENT (For the initial configurations, the logic which creates the directories and symbolic links will be updated to create the etc directory as a real directory instead of a symbolic link. Future products which are installed alongside or on top of WebSphere Application Server for z/os may require that cells which were configured prior to Fix Pack be updated so that WAS_HOME/etc is a real directory instead of a symbolic link. Any future product with this requirement will note the requirement in its documentation. In the meantime, customers who wish to modify their existing pre cells to make WAS_HOME/etc a real directory instead of a symbolic link can follow the instructions found below in this action hold. NOTE: Following the instructions below is recommended for consistency, but is NOT required at this time. The following steps will adjust symbolic links in an existing WebSphere Application Server for z/os Version 6.1 node to match the current initial symbolic link configuration: 1. After applying Service Level (Fix Pack) or above, access the OMVS shell with a user ID that has file update authority (as defined in the customization instructions). 2. Change directories to <SMPE_INSTALL_ROOT>/bin 3. For each V6.1 application server or deployment manager node to be updated, run the following shell command (this is all one command; it is split here for space constraints): fixsymboliclinks.sh <SMPE_INSTALL_ROOT> <TARGET WAS_HOME> <file system owner> <configuration group> For example, if an application server was created with the default names prior to , the following commands would be used to update it: cd /usr/lpp/zwebsphere/v6r1/bin fixsymboliclinks.sh /usr/lpp/zwebsphere/v6r1 /WebSphere/V6R1/AppServer WSOWNER WSCFG1). ++ HOLD(UK25977) SYS FMID(H28W610) REASON(ACTION) DATE(07173) COMMENT (WebSphere Application Server V6.1.0 for z/os Service Level (Fix Pack) Post-Install support requires that before the Post-Installer is invoked (i.e. by starting the server), an OMVS 'chmod' command must be issued to update file permissions for the target node. For each WebSphere Application Server node, issue the following commands from a user ID with the proper authority, that is a user that is the owner of the directories shown below or has either uid=0 or READ access to the UNIXPRIV class SUPERUSER.FILESYS.CHANGEPERMS. Issue the following commands: cd <WAS_HOME>/optionalLibraries chmod -R 775 * Where <WAS_HOME> is the target WebSphere Application Server node's home directory (such as /WebSphere/V6R1/AppServer).

2 This must be done against each WebSphere Application Server node BEFORE the node is started at WebSphere Application Server V6.1.0 for z/os Service Level (Fix Pack) The following is an example of running the commands from OMVS and shows the target directories of the chmod: /:> cd /WebSphere/V6R1/AppServer/optionalLibraries /WebSphere/V6R1/AppServer/optionalLibraries:>chmod -R 775 * /WebSphere/V6R1/AppServer/optionalLibraries:>ls -l total 48 drwxrwxr-x 3 WSADMIN CBCFG Mar 27 14:10 Apache drwxrwxr-x 4 WSADMIN CBCFG Mar 27 14:10 IBM drwxrwxr-x 3 WSADMIN CBCFG Mar 27 14:10 jython In chapter 5 Section 2.3 of the Program Directory for WebSphere Application Server for z/os V6.1.0 (GI ), page 23, Figure 16 (page 2 of 2). Storage Requirements for WebSphere Application Server for z/os V6.1.0 Distribution Libraries. IBM recommends the following storage requirements for WebSphere Application Server V6.1.0 for z/os in regards to the ABBOINC Data Set: Library TYPE ORG RECFM LRECL No. of No. of DDNAME 3390 Trks DIR Blks ABBOINC U PDS VB With the application of this PTF, IBM now recommends the the installation updates the storage requirements for the ABBOINC Data Set as follows: Library TYPE ORG RECFM LRECL No. of No. of DDNAME 3390 Trks DIR Blks ABBOINC U PDS VB ). ++ HOLD(UK24627) SYS FMID(H28W610) REASON(DOC) DATE(07173) COMMENT (APAR PK41492 requires changes to documentation. The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be made available in June, The following changes will be made to the About this task section of the topic "Setting a time limit for the completion of RMI/IIOP enterprise bean requests". The paragraph: BBOO0325W An IIOP request for Class Name 'com.ejb.test. hello.second.ejsremotestatelesssayhellosecond_686a0ff2' and Method Name 'sayhellotwo', to 'jobname=bbos002 asid=0031', has timed out. will be changed to: BBOO0325W An IIOP request for Class Name 'com.ejb.test. hello.second.ejsremotestatelesssayhellosecond_686a0ff2' and Method Name 'sayhellotwo', to 'jobname=bbos002 asid=0031', has timed out. SessionHandle= D9F A008004FF, Request ID= The following paragraphs:

3 When this message is issued, a corresponding exception trace is generated that includes an entry similar to the following entry: /bbooejsb.cpp BBOO0011W The function ORBEJSBridge::invoke_request(JNIEnv *, bboojorb *, char *, CORBA::Boolean, CORBA::Request *&, void *)+3395 received CORBA system exception CORBA::COMM_FAILURE. Error code is C9C20D9B The minor code C9C20D9B in this trace entry indicates that the wait time for the RMI/IIOP outbound timer has ended. will be changed to: When this message is issued, a corresponding exception trace is generated that includes an entry similar to the following entry: /bbooejsb.cpp BBOO0011W The function ORBEJSBridge::invoke_request(JNIEnv *, bboojorb *, char *, CORBA::Boolean, CORBA::Request *&, void *)+3395 received CORBA system exception CORBA::COMM_FAILURE. Error code is C9C26A48 The minor code C9C26A48 in this trace entry indicates that the wait time for the RMI/IIOP outbound timer has ended. The following paragraphs will be added: If a response to the request is received after the request times out and is no longer on the queue, the following message is issued: BBOO0328I: No Request found for inbound GIOP Response, SessionHandle=<hstring>, RequestID=<hstring>. A Request/Reply is uniquely identified by the SessionHandle and Request ID and can be used to determine if an earlier BBOO0325W message was received for this request. The administrative console navigation path for performing this task will also be changed from: In the administrative console, click Servers > Application Servers > server_name > ORB Service. to: In the administrative console, click Servers > Application Servers > server_name > Container Services > ORB Service. The following new messages will be added to the BBOO messages: BBOO0325W An IIOP request for Class Name <string> and Method Name <string>, to <string>, has timed out. SessionHandle=<hstring>, Request ID=<hstring>. Explanation: An outbound IIOP request or locate from a servant process has timed out. The "to" string identifies the target server for the request. For servers using TCP/IP the host name and port number will appear in the message. For a local server, this field contains the the jobname and ASID of the server address space. A Request/Reply are uniquely identified by the SessionHandle and Request ID. User response: Examine the target server for possible errors which may have lead to delays. BBOO0328I: No Request found for inbound GIOP Response, SessionHandle=<hstring>, RequestID=<hstring>. Explanation: GIOP reply message was received, but no corresponding request could be found. User response: Look for other messages, errors and dumps to help determine the cause of this message. This may be a "normal" event if a BBOO0325W message is found with a matching SessionHandle and Request ID. A Request/Reply

4 is uniquely identified by the SessionHandle and Request ID. The following new error codes will be added to the Error (minor) codes" topic: C9C26A48 Explanation: An outbound Request or locate from a Servant was successfully sent, but its response was not received in a reasonable amount of time. User Response: Make sure that the target server is not experiencing unexpected delays. The target server will be identified by an associated BBOO0325 message. Additionally, check that the time out value is of sufficient length. See the instructions for setting the "Request timeout" in the WebSphere Application Server Information Center. C9C20D9D C9C20D9E C9C25809 C9C2580A APAR PK38507 requires changes to documentation. A change to the z/os version of the WebSphere Application Server Version 6.1 Information Center will be made. new minor code C9C213DE Explanation: An outbound request originating from the local Servant attempted to drive remotely to a target object that also exists in the local Servant. If we allowed the request to continue, the obscure local flow would cause

5 ORB_Request SMD areas to become corrupted, as the response would be processed at the SAME TIME as the request. We should have caught this exception in ClientDelegate.invoke(), then performed an ORB.lookupLocalObject to find the target servant in the local JVM. If the target servant could not be found, then we propagate the exception to the user code. In this event, something really bad happened, therefore this exception is marked "IBM Internal Only". User Response: "IBM Internal Only" APAR PK37706 requires changes to documentation. The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be made available. The following descriptions of the three new z/os application server custom properties will be added to the "Application server z/os custom properties" topic: iiop_max_msg_megsize Specifies, in megabytes, the maximum size for IIOP requests. For example, if you set the property to 35, any requests over 35 megabytes are rejected. The minimum value for this property is 10 and the maximum value is Omit this property if you do not want to limit the size of IIOP requests. Important: This custom property only applies for systems that are running in 64-bit mode. The maximum size for IIOP requests on systems that are running in 31-bit mode is 10 megabytes. Data Type Integer Default 0 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click Application servers > server > Server infrastructure > Administration > Custom Properties. local_comm_max_msg_megsize Specifies, in megabytes, the maximum size of locally connected communications requests. For example, if you set the property to 35, any requests over 35 megabytes are rejected. The minimum value for this property is 10 and the maximum value is Omit this property if you do not want to limit the size of locally connected communications requests. Important: This custom property only applies for systems that are running in 64-bit mode. The maximum size for IIOP requests on systems that are running in 31-bit mode is 10 megabytes. Data Type Integer Default 0 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click Application servers > server > Server infrastructure >

6 Administration > Custom Properties. protocol_http_large_data_inbound_buffer_64bit Specifies, in megabytes, the size limit for incoming HTTP requests when inbound HTTP chunking is disabled. For example, if you set the property to 35 megabytes, any HTTP requests over 35 megabytes are rejected. Specify 0 (zero) for this property if you do not want to limit the size of unchunked HTTP requests. Important: This custom property should only be used if your system is running in 64-bit mode. If your system is running in 31-bit mode, you should use the protocol_http_large_data_inbound_buffer custom property to set a limit for this inbound buffer. Data Type Integer Default 0 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click Application servers > server > Server infrastructure > Administration > Custom Properties. Also, the following note will be added to the description of the protocol_http_large_data_inbound_buffer custom property that is contained in this same topic: Important: This custom property should only be used if your system is running in 31-bit mode. If your system is running in 64-bit mode, use the protocol_http_large_data_inbound_buffer_64bit custom property to set a limit for this inbound buffer. APAR PK36998 requires changes to documentation. The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be made available. The following step will be added to the "Fine tuning the LE heap" topic: 9. If your Linkage Editor (LE) storage is being exhausted before the Java Virtual Machine (JVM) runs a garbage collection cycle, you can use a JVM generic argument to indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed. The direct byte buffers, that the JVM creates to handle request data, are allocated in the LE heap instead of in the JVM heap. However, even if the direct byte buffers are no longer needed, the JVM does not release this native LE storage until the next garbage collection occurs. If the server is handling large requests, LE storage might become exhausted before the JVM runs a garbage collection cycle, causing the server to abnormally terminate (abend). To indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed: 1. In the administrative console, click Application servers > server > Java and Process Management > Process Definition. 2. Select Control, and then click Java Virtual Machine.

7 3. Enter the following the following value in the Generic JVM arguments field. com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl 4. Repeat the preceding substeps, selecting Servant instead of Control. The description of the Maximum open connections custom property, that is contained in the "TCP transport channel settings" topic, will be changed to the following: Maximum open connections Specifies the maximum number of connections that can be open at one time. Data type Integer between 1 and 128,000 inclusive Default 20,000 The description of the Generic JVM arguments field, that is contained in the "Java virtual machine settings" topic, will be updated to include the following description of the new command line argument: You can use the argument to indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed. The only supported value for this argument is The direct byte buffers, that the JVM creates to handle request data, are allocated in the LE heap instead of in the JVM heap. Normally, even if the direct byte buffers are no longer needed, the JVM does not release this native LE storage until the next garbage collection occurs. If the server is handling large requests, LE storage might become exhausted before the JVM runs a garbage collection cycle, causing the server to abnormally terminate (abend). Configuring the JVM with the com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl argument prevents these abends from occurring. You also need to specify this argument if you are using the zaiofreeinitialbuffers custom property for a TCP channel to indicate that the channel should release the initial read buffers used on new connections as soon as these buffers are no longer needed for the connection. The topic "TCP transport channel custom properties" will be updated to include the following description of the new zaiofreeinitialbuffers custom property: zaiofreeinitialbuffers Use the zaiofreeinitialbuffers property to indicate that the TCP channel should release the initial read buffers used on new connections as soon as these buffers are no longer needed for the connection. By default, this initial read buffer is cached for each connection. When a connection is closed, the read buffer is reused to avoid a memory allocation. This process works well for non-persistent connections, where there is one request per connection. However, for highly persistent connections, the buffer might be held for a considerable amount of time even though it is not being used. For workloads that require a large number of connected clients, this situation can cause a shortage of Linkage Editor (LE) heap space. Unless your workload

8 consists mainly of non-persistent connections, you should set this custom property to true to enable the release of the initial read buffers. If you set this property to true, you must also add the following argument to the JVM generic arguments that are configured for the application server that is using this TCP channel: com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl Data type String Default false). ++ HOLD(UK25977) SYS FMID(H28W610) REASON(DOC) DATE(07173) COMMENT (APAR PK39388 requires changes to documentation. The following changes to the WebSphere Application Server Version 6.1.x Information Centers for the Distributed and z/os platforms will be made available. The topic "Security custom properties" will be updated to include the following descriptions of the three new security custom properties: com.ibm.csi.rmiinboundmappingconfig This property defines the system JAAS login configuration that will be used to perform application specific principal mapping. Default: None com.ibm.csi.rmiinboundmappingenabled This property, when set to true, enables the application specific principal mapping capability. Default: false com.ibm.csi.rmioutboundmappingenabled This property, when set to true, enables the original caller subject embedded in the WSSubjectWrapper object to be restored. Default: false APAR PK30496 requires changes WebSphere Application Server for z/os V6.1.0 documentation. The V6.1.0 WebSphere Application Server for z/os Information Center article "Local operating system settings" will be updated to include the following descriptions of the new custom property: force.credential.creation.for.validation property. Setting this property will force the creation of an access control environment elements (ACEE) or find the ACEE of the user from the cache during ID assertion login to prevent obtaining information for users that have been revoked. Forcing the creation of credentials all the time will cause a decrease in performance. APAR PK30495 requires changes to WebSphere Application Server

9 for z/os V6.1.0 documentation. The V6.1.0 WebSphere Application Server for z/os Information Center article "Local operating system settings" will be updated to include the following descriptions of the new custom property: Under the Custom properties link, you can add a value for the disable.principal.case.preservation property. Setting this property will force the principal returned by getremoteuser() and getuserprincipal() calls to be uppercased. If this property is not set, the case that was presented will be preserved.). ++ HOLD(UK24627) SYS FMID(H28W610) REASON(ACTION) DATE(07173) COMMENT (For the initial configurations, the logic which creates the directories and symbolic links will be updated to create the etc directory as a real directory instead of a symbolic link. Future products which are installed alongside or on top of WebSphere Application Server for z/os may require that cells which were configured prior to Fix Pack be updated so that WAS_HOME/etc is a real directory instead of a symbolic link. Any future product with this requirement will note the requirement in its documentation. In the meantime, customers who wish to modify their existing pre cells to make WAS_HOME/etc a real directory instead of a symbolic link can follow the instructions found below in this action hold. NOTE: Following the instructions below is recommended for consistency, but is NOT required at this time. The following steps will adjust symbolic links in an existing WebSphere Application Server for z/os Version 6.1 node to match the current initial symbolic link configuration: 1. After applying Service Level (Fix Pack) or above, access the OMVS shell with a user ID that has file update authority (as defined in the customization instructions). 2. Change directories to <SMPE_INSTALL_ROOT>/bin 3. For each V6.1 application server or deployment manager node to be updated, run the following shell command (this is all one command; it is split here for space constraints): fixsymboliclinks.sh <SMPE_INSTALL_ROOT> <TARGET WAS_HOME> <file system owner> <configuration group> For example, if an application server was created with the default names prior to , the following commands would be used to update it: cd /usr/lpp/zwebsphere/v6r1/bin fixsymboliclinks.sh /usr/lpp/zwebsphere/v6r1 /WebSphere/V6R1/AppServer WSOWNER WSCFG1). ++ HOLD(UK24627) SYS FMID(H28W610) REASON(DOC) DATE(07173) COMMENT (APAR PK41492 requires changes to documentation.

10 The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be made available in June, The following changes will be made to the About this task section of the topic "Setting a time limit for the completion of RMI/IIOP enterprise bean requests". The paragraph: BBOO0325W An IIOP request for Class Name 'com.ejb.test. hello.second.ejsremotestatelesssayhellosecond_686a0ff2' and Method Name 'sayhellotwo', to 'jobname=bbos002 asid=0031', has timed out. will be changed to: BBOO0325W An IIOP request for Class Name 'com.ejb.test. hello.second.ejsremotestatelesssayhellosecond_686a0ff2' and Method Name 'sayhellotwo', to 'jobname=bbos002 asid=0031', has timed out. SessionHandle= D9F A008004FF, Request ID= The following paragraphs: When this message is issued, a corresponding exception trace is generated that includes an entry similar to the following entry: /bbooejsb.cpp BBOO0011W The function ORBEJSBridge::invoke_request(JNIEnv *, bboojorb *, char *, CORBA::Boolean, CORBA::Request *&, void *)+3395 received CORBA system exception CORBA::COMM_FAILURE. Error code is C9C20D9B The minor code C9C20D9B in this trace entry indicates that the wait time for the RMI/IIOP outbound timer has ended. will be changed to: When this message is issued, a corresponding exception trace is generated that includes an entry similar to the following entry: /bbooejsb.cpp BBOO0011W The function ORBEJSBridge::invoke_request(JNIEnv *, bboojorb *, char *, CORBA::Boolean, CORBA::Request *&, void *)+3395 received CORBA system exception CORBA::COMM_FAILURE. Error code is C9C26A48 The minor code C9C26A48 in this trace entry indicates that the wait time for the RMI/IIOP outbound timer has ended. The following paragraphs will be added: If a response to the request is received after the request times out and is no longer on the queue, the following message is issued: BBOO0328I: No Request found for inbound GIOP Response, SessionHandle=<hstring>, RequestID=<hstring>. A Request/Reply is uniquely identified by the SessionHandle and Request ID and can be used to determine if an earlier BBOO0325W message was received for this request. The administrative console navigation path for performing this task will also be changed from: In the administrative console, click Servers > Application Servers > server_name > ORB Service. to: In the administrative console, click Servers > Application

11 Servers > server_name > Container Services > ORB Service. The following new messages will be added to the BBOO messages: BBOO0325W An IIOP request for Class Name <string> and Method Name <string>, to <string>, has timed out. SessionHandle=<hstring>, Request ID=<hstring>. Explanation: An outbound IIOP request or locate from a servant process has timed out. The "to" string identifies the target server for the request. For servers using TCP/IP the host name and port number will appear in the message. For a local server, this field contains the the jobname and ASID of the server address space. A Request/Reply are uniquely identified by the SessionHandle and Request ID. User response: Examine the target server for possible errors which may have lead to delays. BBOO0328I: No Request found for inbound GIOP Response, SessionHandle=<hstring>, RequestID=<hstring>. Explanation: GIOP reply message was received, but no corresponding request could be found. User response: Look for other messages, errors and dumps to help determine the cause of this message. This may be a "normal" event if a BBOO0325W message is found with a matching SessionHandle and Request ID. A Request/Reply is uniquely identified by the SessionHandle and Request ID. The following new error codes will be added to the Error (minor) codes" topic: C9C26A48 Explanation: An outbound Request or locate from a Servant was successfully sent, but its response was not received in a reasonable amount of time. User Response: Make sure that the target server is not experiencing unexpected delays. The target server will be identified by an associated BBOO0325 message. Additionally, check that the time out value is of sufficient length. See the instructions for setting the "Request timeout" in the WebSphere Application Server Information Center. C9C20D9D C9C20D9E C9C25809

12 C9C2580A APAR PK38507 requires changes to documentation. A change to the z/os version of the WebSphere Application Server Version 6.1 Information Center will be made. new minor code C9C213DE Explanation: An outbound request originating from the local Servant attempted to drive remotely to a target object that also exists in the local Servant. If we allowed the request to continue, the obscure local flow would cause ORB_Request SMD areas to become corrupted, as the response would be processed at the SAME TIME as the request. We should have caught this exception in ClientDelegate.invoke(), then performed an ORB.lookupLocalObject to find the target servant in the local JVM. If the target servant could not be found, then we propagate the exception to the user code. In this event, something really bad happened, therefore this exception is marked "IBM Internal Only". User Response: "IBM Internal Only" APAR PK37706 requires changes to documentation. The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be made available. The following descriptions of the three new z/os application server custom properties will be added to the "Application server z/os custom properties" topic: iiop_max_msg_megsize Specifies, in megabytes, the maximum size for IIOP requests. For example, if you set the property to 35, any requests over 35 megabytes are rejected. The minimum value for this property is 10 and the maximum value is Omit this property if you do not want to limit the size of IIOP requests. Important: This custom property only applies for systems that are running in 64-bit mode. The maximum size for IIOP requests on systems that are running in 31-bit mode is 10 megabytes. Data Type Integer Default 0

13 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click Application servers > server > Server infrastructure > Administration > Custom Properties. local_comm_max_msg_megsize Specifies, in megabytes, the maximum size of locally connected communications requests. For example, if you set the property to 35, any requests over 35 megabytes are rejected. The minimum value for this property is 10 and the maximum value is Omit this property if you do not want to limit the size of locally connected communications requests. Important: This custom property only applies for systems that are running in 64-bit mode. The maximum size for IIOP requests on systems that are running in 31-bit mode is 10 megabytes. Data Type Integer Default 0 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click Application servers > server > Server infrastructure > Administration > Custom Properties. protocol_http_large_data_inbound_buffer_64bit Specifies, in megabytes, the size limit for incoming HTTP requests when inbound HTTP chunking is disabled. For example, if you set the property to 35 megabytes, any HTTP requests over 35 megabytes are rejected. Specify 0 (zero) for this property if you do not want to limit the size of unchunked HTTP requests. Important: This custom property should only be used if your system is running in 64-bit mode. If your system is running in 31-bit mode, you should use the protocol_http_large_data_inbound_buffer custom property to set a limit for this inbound buffer. Data Type Integer Default 0 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click Application servers > server > Server infrastructure > Administration > Custom Properties. Also, the following note will be added to the description of the protocol_http_large_data_inbound_buffer custom property that is contained in this same topic: Important: This custom property should only be used if your system is running in 31-bit mode. If your system is running in 64-bit mode, use the protocol_http_large_data_inbound_buffer_64bit custom property to set a limit for this inbound buffer. APAR PK36998 requires changes to documentation. The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be

14 made available. The following step will be added to the "Fine tuning the LE heap" topic: 9. If your Linkage Editor (LE) storage is being exhausted before the Java Virtual Machine (JVM) runs a garbage collection cycle, you can use a JVM generic argument to indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed. The direct byte buffers, that the JVM creates to handle request data, are allocated in the LE heap instead of in the JVM heap. However, even if the direct byte buffers are no longer needed, the JVM does not release this native LE storage until the next garbage collection occurs. If the server is handling large requests, LE storage might become exhausted before the JVM runs a garbage collection cycle, causing the server to abnormally terminate (abend). To indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed: 1. In the administrative console, click Application servers > server > Java and Process Management > Process Definition. 2. Select Control, and then click Java Virtual Machine. 3. Enter the following the following value in the Generic JVM arguments field. com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl 4. Repeat the preceding substeps, selecting Servant instead of Control. The description of the Maximum open connections custom property, that is contained in the "TCP transport channel settings" topic, will be changed to the following: Maximum open connections Specifies the maximum number of connections that can be open at one time. Data type Integer between 1 and 128,000 inclusive Default 20,000 The description of the Generic JVM arguments field, that is contained in the "Java virtual machine settings" topic, will be updated to include the following description of the new command line argument: You can use the argument to indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed. The only supported value for this argument is The direct byte buffers, that the JVM creates to handle request data, are allocated in the LE heap instead of in the JVM heap. Normally, even if the direct byte buffers are no longer needed, the JVM does not release this native LE storage until the next garbage collection occurs. If the server is handling large requests, LE storage might become exhausted before the JVM runs a garbage collection cycle, causing the server to abnormally terminate (abend). Configuring the JVM with the com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl

15 argument prevents these abends from occurring. You also need to specify this argument if you are using the zaiofreeinitialbuffers custom property for a TCP channel to indicate that the channel should release the initial read buffers used on new connections as soon as these buffers are no longer needed for the connection. The topic "TCP transport channel custom properties" will be updated to include the following description of the new zaiofreeinitialbuffers custom property: zaiofreeinitialbuffers Use the zaiofreeinitialbuffers property to indicate that the TCP channel should release the initial read buffers used on new connections as soon as these buffers are no longer needed for the connection. By default, this initial read buffer is cached for each connection. When a connection is closed, the read buffer is reused to avoid a memory allocation. This process works well for non-persistent connections, where there is one request per connection. However, for highly persistent connections, the buffer might be held for a considerable amount of time even though it is not being used. For workloads that require a large number of connected clients, this situation can cause a shortage of Linkage Editor (LE) heap space. Unless your workload consists mainly of non-persistent connections, you should set this custom property to true to enable the release of the initial read buffers. If you set this property to true, you must also add the following argument to the JVM generic arguments that are configured for the application server that is using this TCP channel: com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl Data type String Default false). ++ HOLD(UK24627) SYS FMID(H28W610) REASON(ACTION) DATE(07173) COMMENT (For the initial configurations, the logic which creates the directories and symbolic links will be updated to create the etc directory as a real directory instead of a symbolic link. Future products which are installed alongside or on top of WebSphere Application Server for z/os may require that cells which were configured prior to Fix Pack be updated so that WAS_HOME/etc is a real directory instead of a symbolic link. Any future product with this requirement will note the requirement in its documentation. In the meantime, customers who wish to modify their existing pre cells to make WAS_HOME/etc a real directory instead of a symbolic link can follow the instructions found below in this action hold. NOTE: Following the instructions below is recommended for consistency, but is NOT required at this time. The following steps will adjust symbolic links in an existing WebSphere Application Server for z/os Version 6.1 node to match the current initial symbolic link configuration: 1. After applying Service Level (Fix Pack) or above, access the OMVS shell with a user ID that has file update authority (as defined in the customization instructions).

16 2. Change directories to <SMPE_INSTALL_ROOT>/bin 3. For each V6.1 application server or deployment manager node to be updated, run the following shell command (this is all one command; it is split here for space constraints): fixsymboliclinks.sh <SMPE_INSTALL_ROOT> <TARGET WAS_HOME> <file system owner> <configuration group> For example, if an application server was created with the default names prior to , the following commands would be used to update it: cd /usr/lpp/zwebsphere/v6r1/bin fixsymboliclinks.sh /usr/lpp/zwebsphere/v6r1 /WebSphere/V6R1/AppServer WSOWNER WSCFG1). ++ HOLD(UK24627) SYS FMID(H28W610) REASON(DOC) DATE(07173) COMMENT (APAR PK41492 requires changes to documentation. The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be made available in June, The following changes will be made to the About this task section of the topic "Setting a time limit for the completion of RMI/IIOP enterprise bean requests". The paragraph: BBOO0325W An IIOP request for Class Name 'com.ejb.test. hello.second.ejsremotestatelesssayhellosecond_686a0ff2' and Method Name 'sayhellotwo', to 'jobname=bbos002 asid=0031', has timed out. will be changed to: BBOO0325W An IIOP request for Class Name 'com.ejb.test. hello.second.ejsremotestatelesssayhellosecond_686a0ff2' and Method Name 'sayhellotwo', to 'jobname=bbos002 asid=0031', has timed out. SessionHandle= D9F A008004FF, Request ID= The following paragraphs: When this message is issued, a corresponding exception trace is generated that includes an entry similar to the following entry: /bbooejsb.cpp BBOO0011W The function ORBEJSBridge::invoke_request(JNIEnv *, bboojorb *, char *, CORBA::Boolean, CORBA::Request *&, void *)+3395 received CORBA system exception CORBA::COMM_FAILURE. Error code is C9C20D9B The minor code C9C20D9B in this trace entry indicates that the wait time for the RMI/IIOP outbound timer has ended. will be changed to: When this message is issued, a corresponding exception trace is generated that includes an entry similar to the following entry: /bbooejsb.cpp BBOO0011W The function ORBEJSBridge::invoke_request(JNIEnv *, bboojorb *, char *, CORBA::Boolean, CORBA::Request *&, void *)+3395 received CORBA system exception CORBA::COMM_FAILURE.

17 Error code is C9C26A48 The minor code C9C26A48 in this trace entry indicates that the wait time for the RMI/IIOP outbound timer has ended. The following paragraphs will be added: If a response to the request is received after the request times out and is no longer on the queue, the following message is issued: BBOO0328I: No Request found for inbound GIOP Response, SessionHandle=<hstring>, RequestID=<hstring>. A Request/Reply is uniquely identified by the SessionHandle and Request ID and can be used to determine if an earlier BBOO0325W message was received for this request. The administrative console navigation path for performing this task will also be changed from: In the administrative console, click Servers > Application Servers > server_name > ORB Service. to: In the administrative console, click Servers > Application Servers > server_name > Container Services > ORB Service. The following new messages will be added to the BBOO messages: BBOO0325W An IIOP request for Class Name <string> and Method Name <string>, to <string>, has timed out. SessionHandle=<hstring>, Request ID=<hstring>. Explanation: An outbound IIOP request or locate from a servant process has timed out. The "to" string identifies the target server for the request. For servers using TCP/IP the host name and port number will appear in the message. For a local server, this field contains the the jobname and ASID of the server address space. A Request/Reply are uniquely identified by the SessionHandle and Request ID. User response: Examine the target server for possible errors which may have lead to delays. BBOO0328I: No Request found for inbound GIOP Response, SessionHandle=<hstring>, RequestID=<hstring>. Explanation: GIOP reply message was received, but no corresponding request could be found. User response: Look for other messages, errors and dumps to help determine the cause of this message. This may be a "normal" event if a BBOO0325W message is found with a matching SessionHandle and Request ID. A Request/Reply is uniquely identified by the SessionHandle and Request ID. The following new error codes will be added to the Error (minor) codes" topic: C9C26A48 Explanation: An outbound Request or locate from a Servant was successfully sent, but its response was not received in a reasonable amount of time. User Response: Make sure that the target server is not experiencing unexpected delays. The target server will be identified by an associated BBOO0325 message. Additionally, check that the time out value is of sufficient length. See the instructions for setting the "Request timeout" in the WebSphere Application Server Information Center. C9C20D9D

18 C9C20D9E C9C25809 C9C2580A APAR PK38507 requires changes to documentation. A change to the z/os version of the WebSphere Application Server Version 6.1 Information Center will be made. new minor code C9C213DE Explanation: An outbound request originating from the local Servant attempted to drive remotely to a target object that also exists in the local Servant. If we allowed the request to continue, the obscure local flow would cause ORB_Request SMD areas to become corrupted, as the response would be processed at the SAME TIME as the request. We should have caught this exception in ClientDelegate.invoke(), then performed an ORB.lookupLocalObject to find the target servant in the local JVM. If the target servant could not be found, then we propagate the exception to the user code. In this event, something really bad happened, therefore this exception is marked "IBM Internal Only". User Response: "IBM Internal Only" APAR PK37706 requires changes to documentation. The following changes to the z/os version of the WebSphere

19 Application Server Version 6.1.x Information Center will be made available. The following descriptions of the three new z/os application server custom properties will be added to the "Application server z/os custom properties" topic: iiop_max_msg_megsize Specifies, in megabytes, the maximum size for IIOP requests. For example, if you set the property to 35, any requests over 35 megabytes are rejected. The minimum value for this property is 10 and the maximum value is Omit this property if you do not want to limit the size of IIOP requests. Important: This custom property only applies for systems that are running in 64-bit mode. The maximum size for IIOP requests on systems that are running in 31-bit mode is 10 megabytes. Data Type Integer Default 0 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click Application servers > server > Server infrastructure > Administration > Custom Properties. local_comm_max_msg_megsize Specifies, in megabytes, the maximum size of locally connected communications requests. For example, if you set the property to 35, any requests over 35 megabytes are rejected. The minimum value for this property is 10 and the maximum value is Omit this property if you do not want to limit the size of locally connected communications requests. Important: This custom property only applies for systems that are running in 64-bit mode. The maximum size for IIOP requests on systems that are running in 31-bit mode is 10 megabytes. Data Type Integer Default 0 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click Application servers > server > Server infrastructure > Administration > Custom Properties. protocol_http_large_data_inbound_buffer_64bit Specifies, in megabytes, the size limit for incoming HTTP requests when inbound HTTP chunking is disabled. For example, if you set the property to 35 megabytes, any HTTP requests over 35 megabytes are rejected. Specify 0 (zero) for this property if you do not want to limit the size of unchunked HTTP requests. Important: This custom property should only be used if your system is running in 64-bit mode. If your system is running in 31-bit mode, you should use the protocol_http_large_data_inbound_buffer custom property to set a limit for this inbound buffer. Data Type Integer Default 0 Used by Daemon No To specify a value for this custom property for an application server, in the administrative console, click

20 Application servers > server > Server infrastructure > Administration > Custom Properties. Also, the following note will be added to the description of the protocol_http_large_data_inbound_buffer custom property that is contained in this same topic: Important: This custom property should only be used if your system is running in 31-bit mode. If your system is running in 64-bit mode, use the protocol_http_large_data_inbound_buffer_64bit custom property to set a limit for this inbound buffer. APAR PK36998 requires changes to documentation. The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be made available. The following step will be added to the "Fine tuning the LE heap" topic: 9. If your Linkage Editor (LE) storage is being exhausted before the Java Virtual Machine (JVM) runs a garbage collection cycle, you can use a JVM generic argument to indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed. The direct byte buffers, that the JVM creates to handle request data, are allocated in the LE heap instead of in the JVM heap. However, even if the direct byte buffers are no longer needed, the JVM does not release this native LE storage until the next garbage collection occurs. If the server is handling large requests, LE storage might become exhausted before the JVM runs a garbage collection cycle, causing the server to abnormally terminate (abend). To indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed: 1. In the administrative console, click Application servers > server > Java and Process Management > Process Definition. 2. Select Control, and then click Java Virtual Machine. 3. Enter the following the following value in the Generic JVM arguments field. com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl 4. Repeat the preceding substeps, selecting Servant instead of Control. The description of the Maximum open connections custom property, that is contained in the "TCP transport channel settings" topic, will be changed to the following: Maximum open connections Specifies the maximum number of connections that can be open at one time. Data type Integer between 1 and 128,000 inclusive Default 20,000 The description of the Generic JVM arguments field, that is contained in the "Java virtual machine settings" topic, will be updated to include the following description of the new

21 command line argument: You can use the argument to indicate that storage for individual direct byte buffers should be released as soon as the buffer is no longer needed. The only supported value for this argument is The direct byte buffers, that the JVM creates to handle request data, are allocated in the LE heap instead of in the JVM heap. Normally, even if the direct byte buffers are no longer needed, the JVM does not release this native LE storage until the next garbage collection occurs. If the server is handling large requests, LE storage might become exhausted before the JVM runs a garbage collection cycle, causing the server to abnormally terminate (abend). Configuring the JVM with the com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl argument prevents these abends from occurring. You also need to specify this argument if you are using the zaiofreeinitialbuffers custom property for a TCP channel to indicate that the channel should release the initial read buffers used on new connections as soon as these buffers are no longer needed for the connection. The topic "TCP transport channel custom properties" will be updated to include the following description of the new zaiofreeinitialbuffers custom property: zaiofreeinitialbuffers Use the zaiofreeinitialbuffers property to indicate that the TCP channel should release the initial read buffers used on new connections as soon as these buffers are no longer needed for the connection. By default, this initial read buffer is cached for each connection. When a connection is closed, the read buffer is reused to avoid a memory allocation. This process works well for non-persistent connections, where there is one request per connection. However, for highly persistent connections, the buffer might be held for a considerable amount of time even though it is not being used. For workloads that require a large number of connected clients, this situation can cause a shortage of Linkage Editor (LE) heap space. Unless your workload consists mainly of non-persistent connections, you should set this custom property to true to enable the release of the initial read buffers. If you set this property to true, you must also add the following argument to the JVM generic arguments that are configured for the application server that is using this TCP channel: com.ibm.ws.buffermgmt.impl.zoswsbytebufferpoolmanagerimpl Data type String Default false). ++ HOLD(UK24627) SYS FMID(H28W610) REASON(ACTION) DATE(07173) COMMENT (For the initial configurations, the logic which creates the directories and symbolic links will be updated to create the etc directory as a real directory instead

22 of a symbolic link. Future products which are installed alongside or on top of WebSphere Application Server for z/os may require that cells which were configured prior to Fix Pack be updated so that WAS_HOME/etc is a real directory instead of a symbolic link. Any future product with this requirement will note the requirement in its documentation. In the meantime, customers who wish to modify their existing pre cells to make WAS_HOME/etc a real directory instead of a symbolic link can follow the instructions found below in this action hold. NOTE: Following the instructions below is recommended for consistency, but is NOT required at this time. The following steps will adjust symbolic links in an existing WebSphere Application Server for z/os Version 6.1 node to match the current initial symbolic link configuration: 1. After applying Service Level (Fix Pack) or above, access the OMVS shell with a user ID that has file update authority (as defined in the customization instructions). 2. Change directories to <SMPE_INSTALL_ROOT>/bin 3. For each V6.1 application server or deployment manager node to be updated, run the following shell command (this is all one command; it is split here for space constraints): fixsymboliclinks.sh <SMPE_INSTALL_ROOT> <TARGET WAS_HOME> <file system owner> <configuration group> For example, if an application server was created with the default names prior to , the following commands would be used to update it: cd /usr/lpp/zwebsphere/v6r1/bin fixsymboliclinks.sh /usr/lpp/zwebsphere/v6r1 /WebSphere/V6R1/AppServer WSOWNER WSCFG1). ++ HOLD(UK26009) SYS FMID(H28W610) REASON(DELETE) DATE(07173) COMMENT (Delete parts.). ++ HOLD(UK24627) SYS FMID(H28W610) REASON(DOC) DATE(07173) COMMENT (APAR PK41492 requires changes to documentation. The following changes to the z/os version of the WebSphere Application Server Version 6.1.x Information Center will be made available in June, The following changes will be made to the About this task section of the topic "Setting a time limit for the completion of RMI/IIOP enterprise bean requests". The paragraph: BBOO0325W An IIOP request for Class Name 'com.ejb.test. hello.second.ejsremotestatelesssayhellosecond_686a0ff2' and Method Name 'sayhellotwo', to 'jobname=bbos002 asid=0031', has timed out. will be changed to: BBOO0325W An IIOP request for Class Name 'com.ejb.test. hello.second.ejsremotestatelesssayhellosecond_686a0ff2'