PQ77613: SMEUI DOES NOT INFORM THE USER THAT A CONVERSATION IS NOT BASED ON THE CURRENT ACTIVE ONE UNITL THE CONV IS BEING ACTIVATED. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description The way SMEUI works right now: User1 and User2 have SMEUI started with Conv1 as an active conversation. User1 creates a new conversation Conv2 and activates it. So Conv2 is now the active conversation. However, User2 does not hit the Refresh button, so he doesn't know about it, and not until he creates his own conversation Conv3, does modification, and then tries to Commit it, he sees the following error: BON1053E Base conversation of conversation <conversation Name> is not the current active conversation. . At this point the view is refreshed and Conv2 is showed as active. . With the fix, User2 would be notified about the problem when he attempts to create his Conv3, not when he is trying to Commit it. We will also refresh the view at the time of the error so next time User2 tries to activate the conversation, it will be based on the actual active conversation. . This still leaves an open window. If User1 creates a conversation and User2 creates another one shortly after that and quickly activates it, User1 will not know about the problem until the time he tries to Commit the conversation.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: SM EUI does not inform the user that a * * conversation is not based on the * * currently active one until the conv is * * being activated. Thus, the user may * * spend a lot of time modifying a newly * * created conversation and then find * * that the changes cannot be committed. * **************************************************************** * RECOMMENDATION: * **************************************************************** Situation arose at customer where two administrators were simultaneously using separate SMEUI applications to administer WebSphere. UserA added a new conversation and activated it. UserB, without refreshing the SMEUI view, added a new conversation based on what he thought was the active conversation, but was really the previously active conversation. UserB spent a considerable amount of time modifying his new conversation, then tried to commit it, at which time SM notified him that the new conversation could not be committed because it was not based on the currently active conversation. Customer would like to be notified sooner, before spending a lot of time doing work that cannot be committed.Problem conclusion Code was added to a method invoked at Add-Conversation time. It checkes to see if the new conversation is to be based on the currently active conversation, and, if not, throws an InvalidBase exception, resulting in the following message at the SMEUI console: BBON0468E Unable to create conversation convname. The message log will contain the following additional message: BBON1053E Base conversation of conversation convname is not the current active conversation. APAR PQ77613 is associated with SERVICE LEVEL W401602 of WebSphere Application Server version 4.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: UQ80473 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 #: PQ77613
IBM Group: Software Group
Modified date: Oct 3, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.