PQ77011: SM API ACTIVATE CONVERSATION FAILS ON RETRY WITH BBON3199E METHOD COMMITCONVERSATION FAILED.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
SM API activate conversation fails on retry with message
'BBON3199E Method commitconversation failed.'  The SMEUI works
differently in that with the SMEUI a test is performed to verify
if a commit has been done and if so, the logic goes to do the
activate.  In the SMAPI, if the commit has been done, no test is
performed to determine this, so the commit is attempted and
fails.  Customer would expect SMAPI to work similarly to the
SMEUI.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 version 4.0.1 for z/OS and OS/390            *
****************************************************************
* PROBLEM DESCRIPTION: Conversations which do not completely   *
*                      Activate can not be subsequently        *
*                      activated by the SM API.  The SM EUI    *
*                      can successfully activate a             *
*                      converstation in this state.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If an Activate conversation does not completely finish, leaving
the conversation in an Activate Pending condition, the SM API
can not be used to complete the Activation.  The SM API will
return the following on the commitconversation call:
status 4
message.1 BBON3199E Method commitconversation failed.
message.2 BBON3135E Conversation CV is the active conversation.
count 0.

Although the error message indicates that the conversation is
Activated, it is not. The lightning strike is not applied to
conversation when looked at through the SM EUI (the status will
show as Activate Pending).   The SM EUI can be used to complete
the Activation, but the SM API can not.
Problem conclusion
The SM API does the Commit and Activate (Complete) all in one
API call (commitconversation).  In this processing, when the
conversation object is obtained, a check is made to prevent the
Active conversation from being Activated again.

The code was modified to allow an Active conversation to be
Activated (Completed), only if it is in this Active Pending
state.  If such a case, the commit is bypassed since it must
have already been done.   The Activate (Complete) processing
has existing logic to continue the Activate/Complete processing
from where it previously had stopped.

APAR PQ77011 is associated with SERVICE LEVEL W401600 of
WebSphere Application Server version 4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ77011
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-07-31
Closed date 2003-08-27
Last modified date 2003-10-03

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 UQ79824    UP03/09/17 P F309

  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 #: PQ77011
IBM Group: Software Group
Modified date: Oct 3, 2003