PQ56455: 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 PQ56455 addresses various problems * * in WebSphere Application Server V4.0.1 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ56455 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390: ( PQ54078) In the System Management User Interface (SM EUI)it is not possible to create environment variables which start with an underscore '_' or other non numeric and non alpha characters. Customer will see this error message: BBON0867E Environment variable list name 9 contains invalid dataProblem conclusion APAR PQ56455 provides the following problem resolution: ( PQ54078) In the System Management User Interface, methods that check evironment variable names have been modified such that they now accept all characters except numeric characters. ________________________________________________________________ The following publication was revised as a result of APAR PQ56455: ________________________________________________________________ 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. 82 (changed section) Values of default xml file The table below includes all of the attributes that are known for this J2EE 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 "inputlistj2eeserver.xml" on page 232. ________________________________________________________________ Chapter 4, pg. 82 (changed section) ---------------------------------------------------------------- Parameter name |Values |Required ---------------------------------------------------------------- conversationname |Name of the conversation | x ---------------------------------------------------------------- j2eeservername |"*" to list all J2EE servers | x |in the conversation | ---------------------------------------------------------------- ________________________________________________________________ Chapter 4, pg. 84 (added section) Action importj2eeserver This action causes a new server to be imported from an HFS file that was previously created by using the exportserver action. Syntax rc = CB390CFG ("-action 'importj2eeserver' -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 "inputimportj2eeserver.xml" is listed in section inputimportj2eeserver.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 "inputimportj2eeserver.xml". Otherwise specify the complete location to the default xml file by setting this parameter to "/usr/lpp/WebSphere/samples/smapi/inputimportj2eeserver.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 inputimportj2eeserver.xml on page 233. ---------------------------------------------------------------- Parameter name |Values |Required ---------------------------------------------------------------- conversationname |Name of a conversation in state | x |modifiable. | ---------------------------------------------------------------- inputdirectory |Name of the HFS directory to | x |which a server had been | |previously exported. The | |import function will look in | |this directory for a file named | |server.xml. If the file cannot be | |found in the given directory, it | |is also searched for in a | |subdirectory named after the | |exported server (see parameter | |"oldj2eeservername"). | ---------------------------------------------------------------- oldj2eeservername|The original name of the server | x |that was once exported and is | |now to be imported. | ---------------------------------------------------------------- j2eeservername |The new name under which the | x |imported server should be created.| |It is highly recommended to set | |this parameter to the same value | | as "oldj2eeservername". | ---------------------------------------------------------------- Example script Here is an example script: /*REXX function */ call syscalls 'ON' signal on error name.=0 name.1 ="conversationname" name.2 ="inputdirectory" name.3 ="oldj2eeservername" name.4 ="j2eeservername" val.=0 val.1 ="SM API Test" val.2 ="/u/smapi/test" val.3 ="BBOASR2" val.4 ="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 "importj2eeserver failed while XMLGEN" exit end i =i+1 end; /*Call function importserver */ rc =CB390CFG("-action 'importj2eeserver'-xmlinput 'inputimportj2eeserver.xml'-input) if (rc ==4)then do say "Test importj2eeserver failed" rc =XMLPARSE("FCTIM""ALL") exit end /*Parsing the result */ rc =XMLPARSE("FCTIM""ALL") if (rc ==4)then do say "Test importj2eeserver failed while XMLPARSE" exit end say "Test importj2eeserver completed" exit error: say "Error in Test importj2eeserver"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 ________________________________________________________________ APAR PQ56455 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 #: PQ56455
IBM Group: Software Group
Modified date: Feb 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.