PQ56453: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390.

 A fix may be available

Obtain the fix for this APAR



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 PQ56453 addresses various problems *
*                      in WebSphere Application Server V4.0.1  *
*                      for z/OS and OS/390.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ56453 addresses the following problems in
WebSphere Application Server V4.0.1 for z/OS and OS/390:

(MD12600) Some customers have their System Management Interface
(SM EUI) operating from behind a firewall. The FTP protocol
needs to be set up in passive mode to be able to cross a
firewall. So far the SM EUI does not set up FTP accordingly,
and therefore a customer cannot install earfiles from behind a
firewall. The FTP transfer status dialog shows an error message
saying that the transfer failed.

(MD12616) The delete methods of server, j2eeserver and
serverinstance are displaying wrong environment variables.
The server side of the SM Scripting API recieves environment
triples. These triples must be parsed and be converted to
environment touples which then should be returned to the SM
Scripting API client.

(MD12619) OTS does not release the tx lock before driving
before_completion.  This prevents prevents us from
performing some transactional services.

(MD12637) Currently the System Management User Interface
(SM EUI) issues a BBON0889 warning message for any bean that is
being loaded which as an activation policy of once. Since the
wrapper EjbJar file for web applications (war files) has
actually set it's activation policy to once by default, the
warning message is issued for each and any J2EE application that
contains also a web application. So the check only needs to be
done for entity beans are stateful session beans, but never for
stateless session beans.

(MD12664) When the SM Scripting API server side generates an
XML output file which includes invalid characters
(e.g. a 'null') the returned XML file is not valid. The client
displays a message, but this message explains that the XML input
file is invalid. It should display that the XML output file is
invalid. The wrong/old messages are:

BBON3010E Getting xml parser reference for parsing xml input
          failed.
BBON3011E Xml input file is not valid.
BBON3012E Getting xml input document reference failed.
BBON3013E Getting root element of xml input document failed.

The new messages are:
BBON3050E Getting xml parser reference for parsing xml output
          failed.
BBON3051E Xml output file is not valid.
BBON3052E Getting xml output document reference failed.
BBON3053E Getting root element of xml output document failed.

Additionally, the CB390CFG part can display another message:
BBON3006E Getting xml output reference failed.
Problem conclusion
APAR PQ56453 provides the following problem resolution:

(MD12600) Support for passive FTP has been build into the
System Management User Interface (SM EUI).

(MD12616) SM Scripting API server side now parses the
environment triples for the delete methods as well as for the
list methods and converts them to name value touples.

(MD12619) The lock is released, we run before_completion,
and then re-acquire the lock, just as we do for MOFW.

(MD12637) The System Management User Interface (SM EUI) has been
modified such that the activation policy is  _NOT_ checked for
stateless session beans.

(MD12664) New messages has been added which indicates that the
XML output file is invalid. The new messages are:
BBON3050E, BBON3051E, BBON3052E and BBON3053E.
________________________________________________________________
The following publication was revised as a result
of APAR PQ56453:
________________________________________________________________
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. 70 (changed section)

Example script
Here is an example script:
/* REXX function */
call syscalls 'ON'
signal on error

say "FCT Test #createj2eeserver"

name. = 0
name.1 = "conversationname"
name.2 = "j2eeservername"
name.3 = "j2eeserverdescription"
name.4 = "identityofthecontrolregion"
name.5 = "identityoftheserverregion"
name.6 = "serverregionstacksize"
name.7 = "productionserver"
name.8 = "debuggerallowed"
name.9 = "olthostname"
name.10 = "oltport"
name.11 = "isolationpolicy"
name.12 = "replicationpolicy"
name.13 = "serverregionrequiresjvm"
name.14 = "serverregionjvmname"
name.15 = "localidentity"
name.16 = "remoteidentity"
name.17 = "transactionfactory"
name.18 = "allowserverregiongarbagecollection"
name.19 = "garbagecollectioninterval"
name.20 = "logstreamname"
name.21 = "procname"
name.22 = "enablerunasidentity"
name.23 = "allownonauthenticatedclients"
name.24 = "allowuseridpasswd"
name.25 = "useridpassticket"
name.26 = "usedce"
name.27 = "dcequalityofprotection"
name.28 = "dcekeytabfile"
name.29 = "allowssl"
name.30 = "allowsslclientcerts"
name.31 = "allowkerberos"
name.32 = "acceptassertedid"
name.33 = "sendassertedid"
name.34 = "useibmconfidential"
name.35 = "sslracfkeyring"
name.36 = "sslv2timeout"
name.37 = "sslv3timeout"
name.38 = "security"
name.39 = "smfwrserveractivity"
name.40 = "smfwrcontaineractivity"
name.41 = "smfwrserverinterval"
name.42 = "smfwrcontainerinterval"
name.43 = "smfintervallength"
name.44 = "environment"

val. = 0
val.1 = "API Functiontest"
val.2 = "J2EESRV"
val.3 = "APIFCT Description"
val.4 = "IBMUSER"
val.5 = "IBMUSER"
val.6 = "0"
val.7 = "Y"
val.8 = "N"
val.9 = ""
val.10 = "7000"
val.11 = "Multiple_Transactions_Per_Server_Region"
val.12 = "One_Per_Server"
val.13 = "N"
val.14 = ""
val.15 = "CBGUEST"
val.16 = "CBGUEST"
val.17 = "N"
val.18 = "Y"
val.19 = "50000"
val.20 = ""
val.21 = "BBOASR1"
val.22 = "Y"
val.23 = "Y"
val.24 = "Y"
val.25 = "N"
val.26 = "N"
val.27 = "No_Protection"
val.28 = ""
val.29 = "N"
val.30 = "Y"
val.31 = "Y"
val.32 = "Y"
val.33 = "Y"
val.34 = "Y"
val.35 = "CBKeyring"
val.36 = "100"
val.37 = "600"
val.38 = "ISM_UserID_Password"
val.39 = "N"
val.40 = "N"
val.41 = "N"
val.42 = "N"
val.43 = "0"
val.44 = "CLASSPATH='Demo:test1' PATH='test2'
     DEFAULT_CLIENT_XML_PATH='/sm/xml'"
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 "FCT Test #createj2eeserver failed while XMLGEN"
exit
end
i = i+1
end;
/* Call the function: createj2eeserver */
rc = CB390CFG("-action 'createj2eeserver' -xmlinput
     'inputcreatej2eeserver.xml' -input 'tempin' -output
     'createj2eeserver'")
if (rc == 4) then do
say "FCT Test #createj2eeserver failed"
exit
end
/* Parse the result */
rc = XMLPARSE("createj2eeserver" "ALL")
if (rc == 4) then do
say "FCT Test #createj2eeserver failed while XMLPARSE"
exit
end
say "FCT Test #createj2eeserver completed"
return 0
exit
error:
say "Error in FCT Test #createj2eeserver" rc "at line" sigl
say sourceline(sigl)
exit
________________________________________________________________
Chapter 4, pg. 72 (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 4, pg. 73 (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 "inputdeletej2eeserver.xml" on page 229.
________________________________________________________________
Chapter 4, pg. 74 (changed section)

----------------------------------------------------------------
Parameter name          |Values                       |Required
----------------------------------------------------------------
conversationname        |Name of the conversation     |   x
----------------------------------------------------------------
j2eeservername          |Name of the J2EE server      |   x
----------------------------------------------------------------
________________________________________________________________
APAR PQ56453 is associated with SERVICE LEVEL W401013 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ56453
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-01-08
Closed date 2002-01-08
Last modified date 2002-02-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ61730    UP02/01/17 P F201

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


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 #: PQ56453
IBM Group: Software Group
Modified date: Feb 2, 2002