I totally understand the desire for Remedy to create products that encourage us
to buy more licenses.
>... They are given a floating READ license at
>login, but take a floating WRITE license when they do ANY OTHER ACTION.
Yes, This is what I've always thought. I would expect a floating read first.
But that did not happen.
In answer to other questions. The dialog has no active links, no menus, we open
the display-only form in Submit mode. We even tried submitter mode locked and
there was no difference.
Here's the actual user.log
<USER> <TID: 3007155120> <RPC ID: 0000001152> <Queue: List > <Client-RPC:
390620 > <USER: Test
> /* Fri Aug 25 2006 10:25:20.9211 */ FLOAT GRANT WRITE Test (1
of 5 write)
<USER> <TID: 3014532016> <RPC ID: 0000001153> <Queue: Fast > <Client-RPC:
390620 > <USER: MidTier Service
> /* Fri Aug 25 2006 10:25:20.9312 */ FIXED GRANT WRITE MidTier
Service
<USER> <TID: 3008215984> <RPC ID: 0000001189> <Queue: List > <Client-RPC:
390620 > <USER: Test1
> /* Fri Aug 25 2006 10:25:40.0814 */ FLOAT GRANT WRITE Test1 (2
of 5 write)
<USER> <TID: 3007155120> <RPC ID: 0000001199> <Queue: List > <Client-RPC:
390620 > <USER: Test2
> /* Fri Aug 25 2006 10:25:51.5725 */ FLOAT GRANT WRITE Test2 (3
of 5 write)
<USER> <TID: 3008215984> <RPC ID: 0000001212> <Queue: List > <Client-RPC:
390620 > <USER: Test3
> /* Fri Aug 25 2006 10:26:08.0219 */ FLOAT GRANT WRITE Test3 (4
of 5 write)
<USER> <TID: 3007155120> <RPC ID: 0000001222> <Queue: List > <Client-RPC:
390620 > <USER: Test4
> /* Fri Aug 25 2006 10:26:20.0821 */ FLOAT GRANT WRITE Test4 (5
of 5 write)
<USER> <TID: 3010321328> <RPC ID: 0000001232> <Queue: List > <Client-RPC:
390620 > <USER: Test5
> /* Fri Aug 25 2006 10:26:31.8456 */ FLOAT NO WRITE FREE Test5
(all 5 write in use)
I'm checking into whether the Preference server is affecting it.
Thanks,
-Geoff
-----Original Message-----
>From: Aaron Keller <[EMAIL PROTECTED]>
>Sent: Aug 25, 2006 4:40 PM
>To: [email protected]
>Subject: Re: After all these years (10) confused about Licensing
>
>>> My understanding is that user would be issued a floating read license
>at the time of login and then would be issued a floating license until
>they modify a form entry.
>
>You are partially correct. They are given a floating READ license at
>login, but take a floating WRITE license when they do ANY OTHER ACTION.
>
>
>The way it was explained to me is: the server pulls the write token when
>the screen is opened (instead of when a modify is initiated) so that it
>is ready to use if needed. Personally, I don't believe that
>explanation.
>
>Personally, I think it's done that way to encourage users to buy more
>licenses.
>
>-Aaron
>
>* Email: [EMAIL PROTECTED]
>
>
>-----Original Message-----
>From: Action Request System discussion list(ARSList)
>[mailto:[EMAIL PROTECTED] On Behalf Of Geoff Endresen
>Sent: Friday, August 25, 2006 3:57 PM
>To: [email protected]
>Subject: After all these years (10) confused about Licensing
>
>Riddle me this Batman or Wonder Woman,
>
>Why does the Remedy Server issue a floating write license when a user
>logs into the server and opens a dialog form.
>
>My understanding is that user would be issued a floating read license at
>the time of login and then would be issued a floating license until they
>modify a form entry.
>
>We have tested this via the User Tool and via the Mid-Tier and we have
>similar results.
>
>AR System 6.3 Patch 017
>Oracle 10g with UTF-8
>Red Hat Enterprise Linux release 3 (RHEL-3)
>
>Thanks,
>-Geoff Endresen
>Amazon.com
>
>________________________________________________________________________
>_______
>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
>
>SunCom is the wireless company that's committed to doing things differently.
>
>Things we want you to know.
>
>This e-mail and any files transmitted with it are confidential and are
>intended solely for the use of the individual or entity to whom they are
>addressed. This communication may contain material protected by the
>attorney-client privilege. If you are not the intended recipient or the person
>responsible for delivering the e-mail to the intended recipient, be advised
>that you have received this e-mail in error and that any use, dissemination,
>forwarding, printing or copying of this e-mail is strictly prohibited.
>
>_______________________________________________________________________________
>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
