PQ56457: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V4.0.1 for z/OS and OS/390Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ56457 addresses various problems * * in WebSphere Application Server V4.0.1 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ56457 addresses the following problem in WebSphere Application Server V4.0.1 for z/OS and OS/390: ( PQ54184) When the System Management User Interface (SM EUI) is invoked to prepare the active conversation for a coldstart a dialog appears that tell the administrator about the consequences and offers him the facility to change the daemon ip name already in the configuration data. This is offered in form of a checkbox, and was this is checked, an entry field is displayed where the new daemon ip name can be entered. When this entryfield is made visible, the buttons at the bottom of the dialog are pushed out of the visible area of the dialog and cannot be accessed without resizing the dialog.Problem conclusion APAR PQ56457 provides the following problem resolution: ( PQ54184) The problem is that the JFC layout manager that's used for arranging the controls in the dialog has changed it's behaviour between the JDK level that was used when it was developed (1.1.8) and the actual JDK 1.3. Previously there was also some space reserved in a dialog for invisible components, like in this case the entryfield for the daemon ip name. Now this is no longer the case and this is why the dialog is now too small when the entryfield is made visible. To fix this the code was changed to expicitely reserve some space for the entryfield after it is made invisible. ________________________________________________________________ The following publication was revised as a result of APAR PQ56457: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 System Management Scripting API SA22-7839-02 ________________________________________________________________ This APAR 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: http://www.ibm.com/software/webservers/appserv/ ________________________________________________________________ ________________________________________________________________ Chapter 4, pg. 84 (added section) Action exportj2eeserver This action causes a new server to be exported from an HFS file that was previously created by using the exportj2eeserver action. Syntax rc = CB390CFG ("-action 'exportj2eeserver' -xmlinput 'defaultxmlfilename' -input 'inputfilename' -output 'outputfilename'") Syntax details rc The return code (rc) is "0" if no errors were detected. If rc is "4", an error has occurred while processing the action. defaultxmlfilename This is the default xml file. The file has to contain a document type definition (DTD) and all of the required parameters. Only the optional attributes can be left out. The default xml file for listserver "inputexportj2eeserver.xml" is listed in section inputexportj2eeserver.xml on page 233. This file is present in the /usr/lpp/WebSphere/samples/smapi directory. If the environment variable DEFAULT_CLIENT_XML_PATH locates to this directory you only need to type the filename "inputexportj2eeserver.xml". Otherwise specify the complete location to the default xml file by setting this parameter to "/usr/lpp/WebSphere/samples/smapi/inputexportj2eeserver.xml".If you want to use your own default xml file, you must specify the complete directory of the file or you must set the DEFAULT_CLIENT_XML_PATH to this directory. inputfilename This parameter is optional. It specifies a file that contains only name value pairs. Using XMLGEN (Chapter 5. XMLGEN on page 211), you can set the values of the default xml file to these new specified values. An example below show how this works. If it is not present, the default xmlinput file must contain all of the required parameters. outputfilename This parameter specifies the name of the output file. It will be written into the /tmp directory. Values of default xml file The table below includes all of the attributes that are known for this server action. The required ones must be defined in the default xml file or can be defined by the XMLGEN (Chapter 5. XMLGEN on page 211), script. The default xml file is listed in section inputexportj2eeserver.xml on page 233. ---------------------------------------------------------------- Parameter name |Values |Required ---------------------------------------------------------------- conversationname |Name of a conversation in state | x |"activated" or "replaced". | ---------------------------------------------------------------- outputdirectory |Name of the HFS directory to | x |which the j2ee server should be | |exported. The export function | |will automatically create a | |subdirectory here named after | |the exported j2ee server. A file | |named "server.xml" is created | |in that subdirectory that | |contains the complete j2ee server | |definition. Next to this file a | |set of files named with UUIDs are | |created that contain the | | plications and resources of | | is server. | ------------------ -------------------------------------------- j2eeservername |The name of the j2ee server to be | x |exported. | ---------------------------------------------------------------- Example script Here is an example script: /*REXX function */ call syscalls 'ON' signal on error name.=0 name.1 ="conversationname" name.2 ="outputdirectory" name.3 ="j2eeservername" val.=0 val.1 ="SM API Test" val.2 ="/u/smapi/test" val.3 ="BBOASR2" rc =4 i =1 /*Generate XML Input */ do while(name.i <>'0') rc =XMLGEN("tempin"name.i val.i) if (rc ==4)then do say "Test exportj2eeserver failed while XMLGEN" exit end i =i+1 end; /*Call function exportj2eeserver */ rc =CB390CFG("-action 'exportj2eeserver'-xmlinput 'inputexportj2eeserver.xml') if (rc ==4)then do say "Test exportj2eeserver failed" rc =XMLPARSE("FCTEX""ALL") exit end /*Parsing the result */ rc =XMLPARSE("FCTEX""ALL") if (rc ==4)then do say "Test exportj2eeserver failed while XMLPARSE" exit end say "Test exportj2eeserver completed" exit error: say "Error in Test exportj2eeserver"rc "at line"sigl say sourceline(sigl) exit Example output file The output file may look like this: acceptassertedid.1 N administratorname.1 IBMUSER allowkerberos.1 N allownonauthenticatedclients.1 Y allowserverregiongarbagecollection.1 Y allowssl.1 N allowsslclientcerts.1 N allowuseridpasswd.1 Y conversationname.1 test new j2ee resources dcekeytabfile.1 dcequalityofprotection.1 No_Protection debuggerallowed.1 Y enablerunasidentity.1 N garbagecollectioninterval.1 50000 identityofthecontrolregion.1 IBMUSER identityoftheserverregion.1 IBMUSER isolationpolicy.1 One_Transaction_Per_Server_Region j2eeserverdescription.1 My bboasr2 server j2eeservername.1 BBOASR2 localidentity.1 CBGUEST logstreamname.1 olthostname.1 oltport.1 5000 procname.1 BBOASR2 productionserver.1 Y remoteidentity.1 CBGUEST replicationpolicy.1 Replicate_As_Needed sendassertedid.1 N serverregionjvmname.1 serverregionrequiresjvm.1 N serverregionstacksize.1 0 sslracfkeyring.1 CBKeyring sslv2timeout.1 100 sslv3timeout.1 600 sysplexname.1 PLEX1 transactionfactory.1 N usedce.1 N useibmconfidential.1 N useridpassticket.1 Y security.1 ISM_UserID_Password ISM_Pass_Ticket environment.1 DB2_STATEFUL_STORE ='1'JDBC_URL ='jdbc:db2os390:loc1' status 0 message.1 OK count 1 ________________________________________________________________ Chapter 4, pg. 84 (new section) Example output file The output file may look like this: acceptassertedid.1 Y administratorname.1 CBADMIN allowkerberos.1 Y allownonauthenticatedclients.1 Y allowserverregiongarbagecollection.1 Y allowssl.1 N allowsslclientcerts.1 Y allowuseridpasswd.1 Y conversationname.1 API Functiontest dcekeytabfile.1 dcequalityofprotection.1 No_Protection debuggerallowed.1 N enablerunasidentity.1 Y garbagecollectioninterval.1 50000 identityofthecontrolregion.1 IBMUSER identityoftheserverregion.1 IBMUSER isolationpolicy.1 Multiple_Transactions_Per_Server_Region j2eeserverdescription.1 APIFCT Description j2eeservername.1 J2EESRV localidentity.1 CBGUEST logstreamname.1 olthostname.1 oltport.1 7000 procname.1 BBOASR1 productionserver.1 Y remoteidentity.1 CBGUEST replicationpolicy.1 One_Per_Server sendassertedid.1 Y serverregionjvmname.1 serverregionrequiresjvm.1 N serverregionstacksize.1 0 smfintervallength.1 0 smfwrcontaineractivity.1 N smfwrcontainerinterval.1 N smfwrserveractivity.1 N smfwrserverinterval.1 N sslracfkeyring.1 CBKeyring sslv2timeout.1 100 sslv3timeout.1 600 sysplexname.1 PLEX1 transactionfactory.1 N usedce.1 N useibmconfidential.1 Y useridpassticket.1 N security.1 ISM_UserID_Password environment.1 CLASSPATH = 'Demo:test1' PATH = 'test2' DEFAULT_CLIENT_XML_PATH = '/sm/xml' status 0 message.1 OK count 1 ________________________________________________________________ Chapter 9, pg. 224 (added section) importserver.xml <?xml version='1.0'?> <!--=========================================================--> <!-- File name: inputimportserver.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 = H28W401 --> <!-- --> <!-- Change history: --> <!--$L0=MD12514, H28W401, 20011018, PDRK: Created. --> <!-- --> <!--=========================================================--> <!-- internal DTD --> <!DOCTYPE inputimportserver <!ELEMENT inputimportserver EMPTY> <!ATTLIST inputimportserver conversationname CDATA #REQUIRED inputdirectory CDATA #REQUIRED oldservername CDATA #REQUIRED servername CDATA #REQUIRED > > <!--begin of default values--> <inputimportserver conversationname = '' inputdirectory = '' oldservername = '' servername = '' > </inputimportserver> ________________________________________________________________ APAR PQ56457 is associated with SERVICE LEVEL W401013 of WebSphere Application Server V4.0.1 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: 401
Software edition:
Reference #: PQ56457
IBM Group: Software Group
Modified date: Feb 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.