Service Level Build Level CF

Transcription

1 Service Level Build Level CF HOLD(UK31229) SYS FMID(JIWO610) REASON(ACTION) DATE(09061) Pack for WebServices on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for WebServices on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes ++ HOLD(UK33849) SYS FMID(JIWO610) REASON(ACTION) DATE(09061) Pack for Web Services on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for Web Services on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes ++ HOLD(UK36764) SYS FMID(JIWO610) REASON(ACTION) DATE(09061) Pack for Web Services on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for Web Services on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes

2 tables). **************************************************************** Problem description: Some directories created during the feature pack augmentation process are not group-writeable. Solution: Customers who have augmented an existing WebSphere Application Server profile on z/os with a feature pack should issue the following OMVS shell commands for each augmented profile's WAS_HOME directory before restarting at a new Feature Pack (service level): cd WAS_HOME chmod -Rh g+w * This will ensure that the post-installer can correctly update files in the profile configuration. This step only needs to be performed once per WAS_HOME - unless an additional augmentation is performed, in which case these commands must be reissued before restarting at a newer Fix Pack (service level).). ++ HOLD(UK39238) SYS FMID(JIWO610) REASON(ACTION) DATE(09061) Pack for Web Services on z/os at Fix Pack Level must be Level HOLD(UK41539) SYS FMID(JIWO610) REASON(ACTION) DATE(09061) Pack for Web Services on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for Web Services on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes

3 ++ HOLD(UK44286) SYS FMID(JIWO610) REASON(ACTION) DATE(09061) Pack for Web Services on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for Web Services on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes ++ HOLD(UK31495) SYS FMID(JIWO610) REASON(ACTION) DATE(09072) (The installation support for the IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0 on z/os is contained in APAR PK56637 (PTF UK31382). The sample jobs provided in PTF UK31382 must be run before applying this PTF. Additional resource requirements for IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0: The AIWOINC data set requires at least 2400 tracks (3390) of free space and 5 free directory blocks for the complete installation of Feature Pack for EJB 3.0. **************************************************************** Customers running IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0 on z/os PTF UK31495 must be running WebSphere Application Server for z/os V6.1 at Fix Pack Level IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0 on z/os PTF UK31495 will also allow customers to run with WebSphere Application Server for z/os V6.1 at Fix Pack Level when it becomes

4 ++ HOLD(UK33835) SYS FMID(JIWO610) REASON(ACTION) DATE(09072) Pack for EJB 3.0 on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0 on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes ++ HOLD(UK36856) SYS FMID(JIWO610) REASON(ACTION) DATE(09072) Pack for EJB 3.0 on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0 on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes tables). **************************************************************** Problem description: Some directories created during the feature pack augmentation process are not group-writeable. Solution: Customers who have augmented an existing WebSphere Application Server profile on z/os with a feature pack should issue the following OMVS shell commands for each augmented profile's WAS_HOME directory before restarting at a new Feature Pack (service level): cd WAS_HOME chmod -Rh g+w *

5 This will ensure that the post-installer can correctly update files in the profile configuration. This step only needs to be performed once per WAS_HOME - unless an additional augmentation is performed, in which case these commands must be reissued before restarting at a newer Fix Pack (service level).). ++ HOLD(UK39240) SYS FMID(JIWO610) REASON(ACTION) DATE(09072) Pack for EJB 3.0 on z/os at Fix Pack Level must be Level tables). Customers who augmented a stand-alone application server or deployment manager with Feature Pack for EJB 3.0 at the Fix Pack levels need to correct certain file permissions in WAS_HOME/deploytool/itp/plugins before starting those application servers or deployment managers at Fix Pack level or above. For each application server or deployment manager node which was augmented with Feature Pack for EJB 3.0, issue the following commands, where "WAS_HOME" is replaced with the home directory for the node: cd WAS_HOME/deploytool/itp/plugins chmod -Rh g+w * Nodes which were initially created with Feature Pack for EJB 3.0 already enabled do not require these actions; only nodes which were augmented with the feature pack after initial creation are affected. If the file permissions are not corrected, failures may occur during postinstaller execution at Fix Pack level or above.). ++ HOLD(UK41556) SYS FMID(JIWO610) REASON(ACTION) DATE(09072) Pack for EJB 3.0 on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0 on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes

6 ++ HOLD(UK44298) SYS FMID(JIWO610) REASON(ACTION) DATE(09072) Pack for EJB 3.0 on z/os at Fix Pack Level must be Level IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0 on z/os at Fix Pack Level will for z/os V6.1 at Fix Pack Level when it becomes ++ HOLD(UK45466) SYS FMID(H28W610) REASON(ACTION) DATE(09093) (Applying the appropriate fixpack will not automatically result in the new behavior. You must turn the behavior on by creating a custom propery on the deployment manager. To do this through the administrative console: -Navigate to System administration > Deployment manager -Expand Java and Process Management and click on Process definition -Click on Java Virtual Machine -Click Custom properties and click New. -Type 'com.ibm.console.core.verifyjndiname" for the name. -Type 'OnlyOnChange' for the value. -Save the changes and restart the deployment manager.). ++ HOLD(UK45466) SYS FMID(H28W610) REASON(DOC) DATE(09093) (APAR PK81617 requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: Changes to the WebSphere Application Server Version 6.1 Information Center will be made available in April, The following description of the new JVM custom property will be added to the topic "Java virtual machine custom properties:" com.ibm.console.core.verifyjndiname Use this property to indicate whether the JNDI name needs to be validated when a change is made to a resource that does not include a change to the JNDI name

7 for that resource. When this property is set to OnlyOnChange, the JNDI name does not need to be validated when a change is made to a resource that does not include a change to JNDI name for that resource. The JNDI validation check is still performed if the JNDI name is modified. By default, a value is not specified for this property, Therefore you must set the property to OnlyOnChange for JNDI name validation not to occur when the JNDI name does not change. This property can be specified for the deployment manager on a server-wide scope.).