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

(MD11094) Createsystem fails with a CEEDUMP signal=SIGSEGV
sicode=SERV_PROTECT. Also follwing message will be received:

BBON3045E Call createsystem failed.
          Invocation target is invalid.

Creating a new system with scripting API fails due to a too
small defined properties array.

(MD11850) A change is need to the System Management User
Interface (SM EUI) such that deleted subtrees are no longer
shown and expandable.

(MD12059) Client gets a CORBA::NO_PERMISSION exception and a
Minor Code=0. The problem occurs when a caller tries to access a
method for the first time, without the proper authorization.
Instead of throwing a CSIAccessExeption we throw instead a
com.ibm.websphere.csi.NoMethodPermissionException, which
translates to NO_PERMISSION, but it sends a minor code of 0.

(MD12073) The fonts that are used when running the System
Management (SM EUI) in Japanese appear difficult to read and
are causing a usability issue.

(MD12143) Attribute values are not checked against the choices
allowed by the template XML for J2EE resource instances with
instance attributes of type combobox.
Problem conclusion
APAR PQ56289 provides the following problem resolution:

(MD11094)Createsystem failure was resolved by resizing the too
small defined Properties array.

(MD11850) The System Management User Interface (SM EUI) has
been modified to not show deleted subtrees any more and to
make sure they are no longer expandable.

(MD12059) Support was added to change the exception name from
NoMethodPermissionException to CSIAccessException. In addition,
a new minor code, C9C240E6 was added. This new minor code is
sent back the client, to aid in providing more detailed
information to better diagnose the problem.

(MD12073) All visual elements have been equipped with code that
changes their font setting according to the locale the System
Management User Interface (SM EUI) runs in.

(MD12143) The code for processing J2EE resource attributes of
type combobox was modified to check attribute values against
the list of valid values specified in the template XML.
_______________________________________________________________
The following publication was revised as a result
of APAR PQ56289:
________________________________________________________________
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. 21 - createconversation (changed section)

Example output file
The output file may look like this:
administratorname.1  =  CBADMIN
conversationdescription.1  =  This conversation is for testing
conversationname.1  =  Testconversation
conversationstatus.1  =  Modifiable
status  =  0
message.1  =  OK
count  =  1

This method on a conversation returns one of the following
states of a conversation:
 1: No status
 2: Modifiable
 3: Commit in progress
 4: Committed
 5: Ready for activate
 6: Activate in progress
 7: Activated
 8: Replaced
 9: Replace pending
10: Prepared for cold start
11: Deleted
________________________________________________________________
Chapter 4, pg. 23 - deleteconversation (changed section)

Example output file
The output file may look like this:
administratorname.1  =  CBADMIN
conversationdescription.1  =  This conversation is for testing
conversationname.1  =  Testconversation
conversationstatus.1  =  Deleted
status  =  0
message.1  =  OK
count  =  1

This method on a conversation returns one of the following
states of a conversation:
 1: Deleted
________________________________________________________________
Chapter 4, pg. 25 - commitconversation (changed section)

Example output file
The output file may look like this:
administratorname.1  =  CBADMIN
conversationdescription.1  =  This conversation is for testing
conversationname.1  =  Testconversation
conversationstatus.1  =  Activated
status  =  0
message.1  =  OK
count  =  1

This method on a conversation returns one of the following
states of a conversation:
 1: No status
 2: Modifiable
 3: Commit in progress
 4: Committed
 5: Ready for activate
 6: Activate in progress
 7: Activated
 8: Replaced
 9: Replace pending
10: Prepared for cold start
11: Deleted
________________________________________________________________
Chapter 4, pg. 26 - listconversation (changed section)

Example output file
administratorname.1  =  CBADMIN
conversationdescription.1  =  This conversation is for testing
conversationname.1  =  Testconversation
conversationstatus.1  =  Modifiable
status  =  0
message.1  =  OK
count  =  1

This method on a conversation returns one of the following
states of a conversation:
 1: No status
 2: Modifiable
 3: Commit in progress
 4: Committed
 5: Ready for activate
 6: Activate in progress
 7: Activated
 8: Replaced
 9: Replace pending
10: Prepared for cold start
11: Deleted.*
________________________________________________________________
Chapter 4, pg. 37 (new section)

Example output file
The output file may look like this:
administratorname.1 CBADMIN
conversationname.1 API Functiontest
sysplexname.1 PLEX1
systemdescription.1
systemname.1 SY2
status 0
message.1 OK
count 1
________________________________________________________________
Chapter 4, pg. 39 (new section)

Example output file
The output file may look like this:
administratorname.1 CBADMIN
conversationname.1 API Functiontest
sysplexname.1 PLEX1
systemdescription.1 New description
systemname.1 SY2
status 0
message.1 OK
count 1
________________________________________________________________

Chapter 4, pg. 41 (new section)

Example output file
The output file may look like this:
administratorname.1 CBADMIN
conversationname.1 API Functiontest
sysplexname.1 PLEX1
systemdescription.1 New description
systemname.1 SY2
status 0
message.1 OK
count 1
________________________________________________________________
Chapter 4, pg. 44 (new section)

Example output file
The output file may look like this:
administratorname.1 CBADMIN
conversationname.1 API Functiontest
sysplexname.1 PLEX1
systemdescription.1 IBM OS/390 Component Broker base System
systemname.1 SY1
administratorname.2 CBADMIN
conversationname.2 API Functiontest
sysplexname.2 PLEX1
systemdescription.2
systemname.2 SY2
status 0
message.1 OK
count 2
________________________________________________________________
Chapter 4, pg. 44 (changed section)

Server
These functions are for the modifications of a server.
Syntax
rc =  ... create- server ...
  delete-
  change-
  list-
  import-
  export-

________________________________________________________________
Chapter 4, pg. 45 (changed section)

action
createserver ...
...
importserver Causes the server to be imported into HFS
    files.
exportserver Causes a new server to be exported from HFS
    files.
________________________________________________________________
APAR PQ56289 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 PQ56289
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-01-03
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:
UQ61730

Modules/Macros
BBOOOPIP BBOOOPIX BBOOORBP BBOOORBX BBOOOUTP BBOOPCCR
BBOORCTX BBOORDTA BBOOTTIP BBOOTTIX BBOROBML BBOROBMS
BBOROMDL BBOROOPI BBOROSMD BBORRMGR BBORTRCD BBOSSDB2
BBOSSESS BBOSSEXT BBOSSITU BBOSSMET BBOSSRPW BBOSSRUN
BBOSSRVA BBOTTCR BBOTTSR BBOUBINF BBOUENUS BBOZ0688
BBOZ0689 BBOZ0733 BBOZ0739 BBOZ0740 BBOZ0742 BBOZ0745
BBOZ0749 BBOZ0751 BBOZ0752 BBOZ0786 BBOZ0801 BBOZ0804
BBOZ0812 BBOZ0813 BBOZ0814 BBOZ0978 BBOZ0979 BBOZ0980
BBOZ0981 BBO3BEGC BBO3CTXP BBO3CTXX BBO3ENDC BBO3SWCH

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