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

(MD12405) The SM Scripting API does not show the state of a
conversation when a action on a conversation is performed
(create-, list-, commit-, delete- conversation). Therefore we
need the SM Scripting API server side to return a property
which indicates the state of a conversation.

(MD12451) The 'deletej2eeapplication' returns always that the
xml output returned from the server side of SM Scripting API is
not valid. This always happens if the application specified for
this action is not found on the specified server.

(MD12514) The SM Scripting API does not support the functions
for importing and exporting (j2ee) servers. The APIs for
importing and exporting servers were initially omitted from the
SM Scripting API by intention, since they are just a convenient
way for an online user to avoid redoing all those manual
definitions over and over again. But if those server objects
would have been defined through the SM Scripting API, rather
than exporting and importing all definitions at once, the
orignal scripts could be run again against the new application
environment to gain the same result. Since more and more
customers are asking for these APIs and the doc states that SM
User Interface and SM Scripting API are functionally equivalent,
this support now needs to be added.
Problem conclusion
APAR PQ56451 provides the following problem resolution:

(MD12405) The server side of the SM Scripting API now returns
an additional propertry which indicates the state of a
conversation.

(MD12451) The conclusion is that the script now returns a valid
xml document which includes in the error case (the j2ee
application was not found on the server) an message which
indicates that the application is not found on the system.

(MD12514) The SM Scripting API is extended to support the
following new functions:
- importserver
- exportserver
- importj2eeserver
- exportj2eeserver
________________________________________________________________
The following publication was revised as a result
of APAR PQ56451:
________________________________________________________________
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 importserver
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 'importserver'
-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 "inputimportserver.xml" is listed in section
inputimportserver.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
"inputimportserver.xml". Otherwise specify the complete location
to the default xml file by setting this parameter to
"/usr/lpp/WebSphere/samples/smapi/inputimportserver.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 inputimportserver.xml on page 224.

----------------------------------------------------------------
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|
                 |directory, it is also searched |
                 |for in a subdirectory named    |
                 |after the exported server (see |
                 |parameter "oldservername").    |
----------------------------------------------------------------
oldservername    |The original name of the server|    x
                 |that was once exported and is  |
                 |now to be imported.            |
----------------------------------------------------------------
servername       |The new name under which the   |      x
                 |imported server should be      |
                 |created.                       |
----------------------------------------------------------------

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 ="oldservername"
name.4 ="servername"
val.=0
val.1 ="SM API Test"
val.2 ="/u/smapi/test"
val.3 ="BBOASR1"
val.4 ="SMAPI1"
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 "importserver failed while XMLGEN"
exit
end
i =i+1
end;
/*Call function importserver */
rc =CB390CFG("-action 'importserver'-xmlinput
     'inputimportserver.xml'-input ')
if (rc ==4)then do
say "Test importserver failed"
rc =XMLPARSE("FCTIM""ALL")
exit
end
/*Parsing the result */
rc =XMLPARSE("FCTIM""ALL")
if (rc ==4)then do
say "Test importserver failed while XMLPARSE"
exit
end
say "Test importserver completed"
exit
error:
say "Error in Test importserver"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 SMAPI1
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
________________________________________________________________
APAR PQ56451 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 PQ56451
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-05-14

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 #: PQ56451
IBM Group: Software Group
Modified date: May 14, 2002