PQ56452: 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/390.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ56452 addresses various problems * * in WebSphere Application Server V4.0.1 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ56452 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390: (MD12523) When refreshing the list of conversations in the System Management User Interface (SM EUI) a system exception "invalid object reference" occurs. The SM EUI caches some of the remote objects on the SM Server, in this case a conversation object. In case the very first conversation that got loaded during startup is deleted, this leads to a system exception after selection the refresh action. (MD12553) Error message BBON0111E appears in the System Management User Interface (SM EUI) message log for a key text.environmentEditing.OK with reason java.util.MissingResourceException. A button in the SMEditVariableDialog was previously renamed from DONE to OK. The corresponding NLS files were not changed but since English is the default, OK shows up on the button anyhow. (MD12564) The SMF properties in the SM Scripting API are not implemented for the J2EE server. They can not be speciefied in a script cause they are not included in the default XML files.Problem conclusion APAR PQ56452 provides the following problem resolution: (MD12523) The System Management User Interface (SM EUI) has been modified such that the cash of remote objects is flushed when the refresh action is selected. (MD12553) The System Management User Interface (SM EUI) has been changed such that the NLS files now have the corresponding changes for the renamed button. (MD12564) The properties are implemented in the SM Scripting API for the syntax check and they are added to the default XML files. ________________________________________________________________ The following publication was revised as a result of APAR PQ56452: ________________________________________________________________ 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. 64 (added section) Action exportserver This action causes a new server to be exported from an HFS file that was previously created by using the exportserver action. Syntax rc = CB390CFG ("-action 'exportserver' -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 "inputexportserver.xml" is listed in section inputexportserver.xml on page 224. 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 "inputexportserver.xml". Otherwise specify the complete location to the default xml file by setting this parameter to "/usr/lpp/WebSphere/samples/smapi/inputexportserver.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 inputexportserver.xml on page 224. ---------------------------------------------------------------- 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 server should be | |exported. The export function | |will automatically create a | |subdirectory here named after | |the exported server. A file | |named "server.xml" is created | |in that subdirectory that | |contains the complete server | |definition. | ---------------------------------------------------------------- oldservername |The original name of the server | x |that was once exported and is | |now to be exported. | ---------------------------------------------------------------- servername |The name of the 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 ="servername" val.=0 val.1 ="SM API Test" val.2 ="/u/smapi/test" val.3 ="BBOASR1" 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 exportserver failed while XMLGEN" exit end i =i+1 end; /*Call function exportserver */ rc =CB390CFG("-action 'exportserver'-xmlinput 'inputexportserver.xml'-input ') if (rc ==4)then do say "Test exportserver failed" rc =XMLPARSE("FCTEX""ALL") exit end /*Parsing the result */ rc =XMLPARSE("FCTEX""ALL") if (rc ==4)then do say "Test exportserver failed while XMLPARSE" exit end say "Test exportserver completed" exit error: say "Error in Test exportserver"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 SM API Test dcekeytabfile.1 dcequalityofprotection.1 No_Protection debuggerallowed.1 Y garbagecollectioninterval.1 50000 identityofthecontrolregion.1 IBMUSER identityoftheserverregion.1 IBMUSER isolationpolicy.1 One_Transaction_Per_Server_Region localidentity.1 CBGUEST logstreamname.1 olthostname.1 oltport.1 5000 procname.1 BBOASR1 productionserver.1 Y remoteidentity.1 CBGUEST replicationpolicy.1 Replicate_As_Needed sendassertedid.1 N serverdescription.1 My bboasr1 server servername.1 BBOASR1 serverregionjvmname.1 serverregionrequiresjvm.1 N serverregionstacksize.1 0 smfintervallength.1 3600 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 N useridpassticket.1 N security.1 ISM_UserID_Password status 0 message.1 OK count 1 ________________________________________________________________ Chapter 4, pg. 64 (changed section) Server These functions are for the modifications of a J2EE server. Syntax rc = ... create- j2eeserver ... delete- change- list- import- export- ________________________________________________________________ Chapter 4, pg. 66 (changed section) acceptassertedid.1 Y|N administratorname.1 AdministratorName allowkerberos.1 Y|N allownonauthenticatedclients.1 Y|N allowserverregiongarbagecollection.1 Y|N allowssl.1 Y|N allowsslclientcerts.1 Y|N allowuseridpasswd.1 Y|N conversationname.1 ConversationName dcekeytabfile.1 DCEKeyTabFile dcequalityofprotection.1 DCEQualityOfProtectionState debuggerallowed.1 Y|N enablerunasidentity.1 Y|N garbagecollectioninterval.1 Number(0-2G) identityofthecontrolregion.1 IdentityOfTheControlRegion identityoftheserverregion.1 IdentityOfTheServerRegion isolationpolicy.1 IsolationPolicyState j2eeserverdescription.1 ServerDescription j2eeservername.1 ServerName localidentity.1 LocalIdentity logstreamname.1 LogStreamName olthostname.1 ObjectLevelTraceHostName oltport.1 Number(0-65535) procname.1 ProcName productionserver.1 Y|N remoteidentity.1 RemoteIdentity replicationpolicy.1 ReplicationPolicyState sendassertedid.1 Y|N serverregionjvmname.1 ServerRegionJVMName serverregionrequiresjvm.1 Y|N serverregionstacksize.1 Number(0-100000) smfintervallength.1 Number(0,15-86400) smfwrcontaineractivity.1 Y|N smfwrcontainerinterval.1 Y|N smfwrserveractivity.1 Y|N smfwrserverinterval.1 Y|N sslracfkeyring.1 SSL_RACF_Keyring sslv2timeout.1 SSL_V2Timeout sslv3timeout.1 SSL_V3Timeout sysplexname.1 SysplexName transactionfactory.1 Y|N usedce.1 Y|N useibmconfidential.1 Y|N useridpassticket.1 Y|N security.1 Security environment.1 Environment status 0|4 message.1 OK|ErrorMessage count NumberOfListedServers ________________________________________________________________ Chapter 4, pg. 66 (changed section) action createj2eeserver ... ... importj2eeserver Causes the J2EE server to be imported into HFS files. exportj2eeserver Causes a new J2EE server to be exported from HFS files. ________________________________________________________________ Chapter 4, pg. 67 (changed section) 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 and can be overwritten by the XMLGEN ("Chapter 5. XMLGEN" on page 195), script. The default xml file is listed in section "inputcreatej2eeserver.xml" on page 227. ________________________________________________________________ Chapter 4, pg. 67 (changed section) ---------------------------------------------------------------- Parameter name |Values |Required ---------------------------------------------------------------- conversationname |Name of the conversation | x ---------------------------------------------------------------- j2eeservername |Name of the J2EE server | x ---------------------------------------------------------------- j2eeserverdescription |Description of the J2EE | |server | ---------------------------------------------------------------- ... |... |... ---------------------------------------------------------------- oltport |Character value between 1 | x |and 65535 | ---------------------------------------------------------------- ... |... |... ---------------------------------------------------------------- ________________________________________________________________ APAR PQ56452 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 #: PQ56452
IBM Group: Software Group
Modified date: Feb 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.