PQ77018: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V5.0 for z/OS.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ77018 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ77018 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD15371) Entering the maximum length value of certain fields results in a generate error like the following: Output overflow Line to be written greater than data set LRECL 80 Enter HELP command for further information regarding this error. Press ENTER key to terminate the dialog. (MD15507) ABEND 0xDC3 with minor code C9C2186C in module BBOTOTS. The transaction service received the return code ATR_CONTEXT_TOKEN_INV from RRS when calling the service ATREINT1. RRS is reporting that the context token supplied on the call is invalid or incorrect. The context token could be invalid because it was abnormally terminated in the servant region before we called the ATREINT1 service in the controller. This can occur when a transaction times out and the servant region is abtermed, while at the same time, a new global transaction is started on another thread in that same servant region. (MD16175) SQL Locking behaviour for CustomFinders and load for update findByPK methods not present causing deadlocks and data integrity problems. In order to allow custom finder methods and findByPrimaryKey methods that were definded as 'forUpdate' to hold the neccessary DB/2 locks, the SQL that backs these methods needs to be ammended at runtime to append the correct SQL locking syntax. This SQL ammending is not occuring and therefore the correct locking behaviour is not possible leading to multiple data integrity problems. (MD16972) Client hang can occur when running a WebSphere AE client against WebSphere V5.0 for z/OS. Invalid service contexts returned by the daemon caused incorrect interpretation of response, and invalid handling of forwarding IORs. (MD16974) A javax.resource.ResourceException is thrown when the Application server attempts to initialize J2C connector. The Application server's error log also shows a java.lang.UnsatisfiedLinkError for one or more DLLs(*.so files) belonging to the connector. Note this problem occurs in a Network Deployment Environment only. During connector installation, the chmod API is called to turn on the execute permission flag(for owner,group,other) on any DLLs (.so files) the connector may have. The connector archive was unpacked by the nodeagent, but the chmod was erroneously executed in the deployment manager. The chmod must be performed in the same process (address space) that unpacks the archive. Otherwise, the chmod API will fail with errno = 139 (permission denied). (MD16999) AccessController.doPrivileged method is called without first checking to see if security is enabled or not. In the case of the latter, the call is an unneccessary waste of CPU cycles. (MD17035) Container managed transactions that time out during method execution may not result in an exception being reported to the client. (MD17109) Dialog overlays the CTRACE PARMLIB member for WebSphere V4.0.1. It unconditionally copies from BBOCTI00 to CTIBBO00, which is the same member used for WebSphere V4.0.1. The dialog should use a different parmlib for WebSphere V5.0. (MD17146) Daemon SSL support needs to be provided. Customers are not able to use a SSL connection between client programs and the daemon. (MD17153) When starting/stopping the MDB Listener Ports the Status Icon does not reflect the status of the Listener Port. The problem is being caused by different behavior of the RuntimeCollaborator (used by the MBean proxy in the controller) verses the DefaultRuntimeCollaborator (used by the MBean in the servant). The DefaultRuntimeCollaborator sets the name value within the MBean object name whereas RuntimeCollaborator does not. Hence, on the controller, the MBean name value defaults to the configId which is the mbeanidentifier value (the real long string value). This means that the object name of the MBean proxy does not match the object name of the servant MBean. (MD17161) Running the BasicCalculator Client Fails with the message: WSCL0202E: The manifest . file for the Application Client jar file . BasicCalculator Client.jar located in the Enterprise Archive file ../samples/lib/TechnologySamples/TechnologySamples.ear does not contain a Main-Class entry for the client application main class. The MANIFEST.MF file does not have key path information needed by the basic calculator client. (MD17187) When daemon goes down, common storage pointed to by bbodbgvt_daemon_ior and bbodbgvt_daemon_ior_ascii does not get freed. If daemon comes up again, new storage is allocated for these IORs. (MD17210) In the administrative console, if you navigate to Security > Authentication Protocol > zSAS Transport panel, the following 3 fields are not related to zSAS and should not be in the zSAS Transport Detail View: remote identity local identity synch to os thread (MD17230) A NullPointerException can occur during node agent initialization. AdminImpl is attempting to initialize a non-existant ZServantListener object and this is causing the NullPointerException. The NotificationService does not create a ZServantListener instance for node agents (because node agents do not have any servants and hence there is nothing to listen for). So, AdminImpl cannot attempt to invoke any methods on the ZServantListener instance when running within a node agent.Problem conclusion APAR PQ77018 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD15371) Dialog files will be updated so that a given line with the substituted string will not be greater than the LRECL. (MD15507) Code was added to handle the ATR_CONTEXT_TOKEN_INV return code from ATREINT1. If this code is returned, and the servant which started the transaction is not active, the transaction is marked rollback_only. If the servant is active, a dump is collected which can aid in determining what may be the cause of this condition. Defect fix MD15507, shipped in APAR PQ77018 requiries a change to WebSphere V5.0 for z/OS documentation. Changes to the WebSphere Application Server Version 5 InfoCenter will be available in the next refresh of the documentation. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library/ The changes will read as follows: C9C21948 Explanation: The RRS service ATREINT1 returned the value ATR_CONTEXT_TOKEN_INV. The transaction will be marked rollback- only. User Response: Check for an application error. ---------------------------------------------------------------- | Abend | Abend | Explanation | Suggested Action | | Code | Reason | | | ---------------------------------------------------------------- | DC3 | 000E0001 | The caller is | Verify that the | | | | not authorized | application is using | | | | to invoke the | standard interfaces. If | | | | requested | the problem persists, | | | | function. The | contact the IBM Support | | | | caller of the | Center. | | | | service is not | | | | | valid. | | ---------------------------------------------------------------- (MD16175) Code added to allow the metadata related to the 'forUpdate' nature of a custom finder and/or a findByPrimaryKey to trigger the correct ammending of SQL statements that back these methods. The interpretation of the metadata and the ammending of the SQL now occur in the in both the EJB 1.1 and EJB 2.0 persistence legs of the container. (MD16972) ServiceContext marshalling has been corrected to ensure invalid contexts are not included in marshalled response. (MD16974) Connector install processing will be updated to ensure the chmod function is executed by the process that unpacks the archive. (MD16999) A WebSphere for z/OS version of the AccessController class has been created to be called by doPrivileged calls first. That class then checks to see if security is enabled. If security is enabled, it passes the call to the original AccessController class, else it returns. (MD17035) The transaction strategy has been updated to throw a TransactionRolledBackException when a CMT method transaction times out. (MD17109) The dialog will prompt the ctrace parmlib suffix on the panel to allow the user to use a different suffix other than "00". The default for the suffix will be "50". As a result, the WebSphere V4.0.1 CTRACE PARMLIB member will not be overlayed by the WebSphere V5.0 CTRACE PARMLIB member. (MD17146) Support was modified such that the following variables are transformed from the security.xml SSL Repertoire that matches the one stated in the cell level variables.xml by the variable: WAS_DAEMON_ONLY_protocol_iiop_daemon_ssl_repertoire com_ibm_DAEMON_claimClientAuthentication com_ibm_DAEMON_claimSecurityLevel com_ibm_DAEMON_claimSecurityCipherSuiteList com_ibm_DAEMON_claimKeyringName com_ibm_DAEMON_claim_ssl_sys_v3_timeout (MD17153) Support has been modified to ensure that the MBeanFactoryImpl on the controller will always have the servant value of the name key (within the object name), which should eliminate mismatches in the object name. (MD17161) A MANIFEST.MF with the path information has been provided. (MD17187) Code has been modified such that when a daemon come up it first checks if bbodbgvt_daemon_ior and bbodbgvt_daemon_ior_ascii already point to valid storage. if they do, they get deleted to prevent the storage leaking. (MD17210) In the administrative console, the 3 fields: "remote identity", "local identity", and "synch to os thread" are removed from the Security > Authentication Protocol > zSAS Transport panel. A new panel named z/OS Global Security Options view to configure these 3 fields is provided. This new view can be reached via the following 2 navigations: Security > Global Security > z/OS Security Options, and Servers > Application Servers > <server-name> > Server Security > Server Level Security > z/OS Security Options. (MD17230) Method AdminImpl has been modified to determine if the ZServantListener.getInstance method returned a non-null value before attempting to invoke a method on the ZServantListener instance. APAR PQ77108 is associated with SERVICE LEVEL W500103 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ79131 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ77018.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ77018
IBM Group: Software Group
Modified date: Sep 9, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.