Hi,
It is too late for a change now, as they are charging us based on this
behavior.
If this was changed, we as customers would need fewer licenses, and BMC
would loose revenue.
The same thing applies to the minimum setting for floating timeouts, which
is 1 hour. If it was 5 minutes, your license needs would drop drastically.
In other words, this behavior is what you have payed for. A valid
complaint would be that it is not that clearly stated in the
documentation...
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
>
> BMC Remedy has so many options. I am a bit surprised that you can't set an
> option that says -- do not grab license.
>
> It is sold - that -- unless you are modifying somebody else's record --
> you don't need a license.
> (Clever wording -- you don't NEED a license -- but you USE one anyway)
>
>
> Thoughts???
>
>
> -John
>
>
> On Mar 25, 2011, at 7:58 AM, Walters, Mark wrote:
>
> **
> This is, and always has been, how it works I believe. A write license is
> assigned when a query is performed because there is an assumption that the
> user may then modify the record returned and try to save it. If the
> license was not assigned until this point you would run the risk of not
> being able to get a license and being unable to save your changes.
>
>
>
> Mark
>
>
>
> I work for BMC, I don’t speak for them.
>
>
>
> From: Action Request System discussion list(ARSList)
> [mailto:arslist@ARSLIST.ORG] On Behalf Of Conny Martin
> Sent: 25 March 2011 11:26
> To: arslist@ARSLIST.ORG
> Subject: Floating users get a floating write token on read operations
>
>
>
> **
>
> Hello All,
>
>
>
> I searched the list but found no answer.
>
>
>
> I have an issue where floating users are granted a write token on read
> operations. I verified this with driver to eliminate workflow that could
> trigger this behaviour. On the first GetListEntry the user is granted a
> write token, although this is not neccessary in my opinion. So every user
> who logs into the system only to check if there are tickets assigned to
> him is blocking a floating write token for at least one hour.
>
>
>
> Has anyone else experienced this behaviour?
>
>
>
> Kind Regards Conny
>
>
>
> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
>
> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
>
> --
> John Sundberg
>
> Kinetic Data, Inc.
> "Building a Better Service Experience"
> Recipient of:
> WWRUG10 Best Customer Service/Support Award
> WWRUG09 Innovator of the Year Award
>
> john.sundb...@kineticdata.com
> 651.556.0930 I www.kineticdata.com
>
>
>
>
>
>
>
>
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
