PQ55487: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V4.0 for z/OS and OS/390.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ55487 addresses various problems * * in WebSphere Application Server V4.0 fo * * z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ55487 addresses the following problems in WebSphere Application Server V4.0 for z/OS and OS/390: (MD11011) The EAR file processor deletes the EAR file it got as input. While this is OK for the "Install J2EE app" action on the WebSphere for z/OS Administration Application (SM EUI), it is not correct for the "Import server" action. (MD11132) When using the System Management(SM) Scripting API "removeApplicationFamily" and specifying a non-existing server, the following messages are shown: BBON3199E Method removeApplicationFamily failed. BBON1000E The Application Family object, <family-name>, could not be found. These error messages are incorrect for the problem. The correct error messages for this situation are: BBON3199E Method removeApplicationFamily failed. BBON1000E The Server object, <server-name>, could not be found. (MD11133) For the System Management(SM) Scripting API function "disassociatelrmfromcontainer" when LRM and container are not associated an error message BBON3155E should be issued. This error message is not issued. (MD11237) When importing application families using the WebSphere for z/OS Administration Application (SM EUI), the family name is not required (can't even be specified). When importing application families using a System Management(SM) Scripting API script, the family name is required. The family name should be an optional parameter. (MD11614) Need more RAS to identify GIOP message response problems. The additional RAS should log a message with specific content under specific circumstances. The first circumstance is that the server has received and processed a request from a client and are unable to send the response (ex. communication failure). A second circumstance is that a response to client request is SystemException (MD12008) Minor code C9C2113B is recieved when starting a Systems Management control region with HEAPPOOLS(OFF) in the proc. This situation results because OTS makes a decision on how to build an ior based on m_StartAllListeningComplete. It is incorrectly ON because of the object storage being dirty. The following messages are recieved: BBOU0011W The function base_build_An_IOR(char*,char*, char*,char*,SEQUENCE_octet*,CORBA::Boolean,IORType, CORBA::Boolean,CORBA::Boolean,CORBA::Boolean) +4012 raised CORBA system exception CORBA::INTERNAL. Error code is C9C2113B. BBOU0003E CB SERIES CONTROL REGION SYSMGT01 ENDED ABNORMALLY, REASON=C9C2113B. (MD12092) When defining a J2EE server, a working directory <CBCONFIG>/working/<SRVNAME> is created for the web container. This directory is not created in case of ImportJ2EEServer. This does not lead to problems, as the web container code seems to create the directory in case it is not there. However, it is created with the app server server region ID. For consistency, it should be created. (MD12139) J2EE resource instances created by System Management (SM) Scripting API support do not have the default values set that are defined in the resource template XML. ( PQ54064) When running with different levels of the client and server JDK ORB, a customer may receive CORBA::MARSHAL exceptions with a minor code of zero (or 4942F000). Different service levels of the marshalling code may result in incompatabilities as data is marshalled in a lower service level and demarshalled by a newer service level of marshal code, or vice versa. These problems surface as a CORBA::MARSHAL exception, usually with a zero or 4942F000 minor code.Problem conclusion APAR PQ55487 provides the following problem resolution: (MD11011) Support has been added to prevent the EAR file processor from deleting an EAR file by providing a symbolic link to it as input for the "Import server" action. (MD11132) For the System Management(SM) Scripting API support, the code for removing an application family was modified to check for server existance and writing the appropriate error message: BBON3199E Method removeApplicationFamily failed. BBON1000E The Server object, <server-name>, could not be found. (MD11133) In the System Management(SM) Scripting API support the code for dis-associating LRM and container was modified to check whether they are currently associated. If they are not associated, the following error message is now written: BBON3155E LRM <lrmname> is not associated with container <containername>. (MD11614) Support has been added to issue messages to the error log in the event of either failing to send a response to a client (new message BBOU0733W); and/or sending a response which contains an SystemException (new message BBOU0734W). The issuance of these messages are controlled with the following 2 new environment variables: BBOC_LOG_RESPONSE_FAILURE=YES -- Issue message BBOU0733W to record a failure detected when attempting to send a response to a client. The message text will contain the request method name, the reply status, and routing information identifying the client. BBOC_LOG_RETURN_EXCEPTION=YES -- Issue message BBOU0734W to record a response that contains an SystemException. The message text will contain the exception id and minor code, the request method name, and routing information identifying the client. (MD11237) The System Management(SM) Scripting API code for importing application families has been modified to make the family name parameter optional. (MD12008) SessionManager constructor in module bbocsmgr.cpp has been modified to initialize m_StartAllListeningComplete to zero, thus fixing the error condition resulting in minor code C9C2113B being issued. (MD12092) For the ImportJ2EEServer function a working directory is now created. (MD12139) In System Management(SM) Scripting API support the code for creating a J2EE resource instance was modified to read and use the resource's default attribute values defined in the template XML. ( PQ54064) To handle imcompatabilities between marshalling code, the JDK ORB implemented the Partner Version service context. WebSphere Application Server V4.0 for z/OS uses the JDK ORB, but did not exploit this service context. Code has been added to exploit this service context thus allowing different levels to co-exist. The following publication was revised as a result of APAR PQ55487: ________________________________________________________________ WebSphere Application Server V4.0 for z/OS and OS/390 Installation and Customization GA22-7834-01 ________________________________________________________________ On page 372, add the following environment variables to table 58: o BBOC_LOG_RESPONSE_FAILURE=NO. Optional for each server. o BBOC_LOG_RETURN_EXCEPTION=NO. Optional for each server. On page 378, add the following environment variable descriptions: BBOC_LOG_RESPONSE_FAILURE= YES|NO Determines whether message BBOU0733W is issued to record a failure detected when attempting to send a response to a client. The message is sent to the error log. YES causes the message to be issued. The default is NO. The message text will contain the request method name, the reply status, and routing information identifying the client. EXAMPLE: BBOC_LOG_RESPONSE_FAILURE=YES BBOC_LOG_RETURN_EXCEPTION= YES|NO Determines whether message BBOU0734W is issued to record a response that contains an SystemException. The message is sent to the error log. YES causes the message to be issued. The default is NO. The message text will contain the exception identifier and minor code, the request method name, and routing information identifying the client. EXAMPLE: BBOC_LOG_RETURN_EXCEPTION=YES ________________________________________________________________ The following publication was revised as a result of APAR PQ55487: ________________________________________________________________ WebSphere Application Server V4.0 for z/OS and OS/390 System Management Scripting API SA22-7839-01 ________________________________________________________________ Chapter 4, pg. 162 (changed section) Parameter name Values Required conversationname Name of the conversation x servername Name of the server x applicationfamilyname Name of the application family ddlfilename Name of the dll file dataset x outputfilename Name of the output dataset x Note: The parameter applicationfamilyname is optional. The actual name of the family being imported is taken from the ddlfilename. The parameter was kept in order to avoid breaking any existing scripts. If an application family name is specified, the API will attempt to list that family after importing from ddlfilename. The supplied family name may be the name of the family imported with ddlfilename or some other application family already defined for the server. In any case, the return code reflects the result of the import operation only. Example script Here is an example script: <?xml version='1.0'?> <!--=========================================================--> <!-- File name: inputimportApplicationfamily.xml --> <!-- --> <!-- Descriptive name: ... --> <!-- --> <!-- Proprietary statement: --> <!-- --> <!-- Licensed Material - Property of IBM --> <!-- --> <!-- 5655-F31 (C) Copyright IBM Corp. 2000, 2001 --> <!-- All Rights Reserved. --> <!-- U.S. Government users - RESTRICTED RIGHTS - Use, --> <!-- Duplication, or Disclosure restricted by GSA-ADP --> <!-- schedule contract with IBM Corp. --> <!-- Status = H28W400 --> <!-- --> <!-- Change history: --> <!--$L0= OW44455, H28K510, 20000721, PDCG: Created. --> <!--$P1=MD11237, H28W400, 20010930, PDJH: import application --> <!--family: make family name optional --> <!-- --> <!--=========================================================--> <!-- internal DTD --> <!DOCTYPE inputimportapplicationfamily <!ELEMENT inputimportApplicationFamily EMPTY> <!ATTLIST inputimportApplicationFamily conversationname CDATA #REQUIRED servername CDATA #REQUIRED applicationfamilyname CDATA #IMPLIED ddlfilename CDATA #REQUIRED outputfilename CDATA #REQUIRED > > <!--begin of default values--> <inputimportApplicationFamily conversationname = '' servername = '' applicationfamilyname = '' ddlfilename = '' outputfilename = '' /> ________________________________________________________________ APAR PQ55487 is associated with SERVICE LEVEL W400051 of WebSphere Application Server V4.0 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ55487
IBM Group: Software Group
Modified date: Jan 3, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.