Hi,
There are tools that handle the user log quite well ;-)
The submitter-mode locked could definitely be an issue. If you are trying to
update a records, where the the users login name is in the Submitter-field, he
would get an error unless it is set. I don't know if the error is
field-by-field though... But I guess it will void any situation where you use
permission settings to allow Submitter to change a field.
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12):
* 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.
> Yes, among other things we are fetching the ordinal date and populating the
> home page. There are push fields on window open actions from the Home Page,
> though certainly not to all of the fields for which it is giving us errors.
>
> I did notice a discrepancy between the legacy server and the new server, old
> server had submitter mode = locked and the new one had submitter mode =
> changeable. When I have a chance to reboot I'll change it to locked, at least
> for consistency's sake. But I'm not sure whether it would make a difference
> in this case?
>
> Interesting note about the license allocation circa 7.6, because even when
> people don't get ARERR 331, they are acting like the float-read-warning is
> totally unfamiliar to them. But we have the same number of floating licenses,
> and users, that we always did.
>
> If I can get my mind "unwrapped around the wheel" I'll take a look through the
> user log file.
>
> Thanks,
>
> Joe
>
> On Mon, 8 Apr 2013 21:07:24 +0200, Misi Mladoniczky <[email protected]> wrote:
>
>>Hi,
>>
>>The FLOAT-WRITE is grabbed as soon as the user performs any activity.
>>
>>The FLOAT-READ-WARNING is not displayed until the user tries to save
>> something
>>requiring a FLOAT-WRITE. And it is only displayed the first time this
>> happens.
>>
>>If you get message as soon as you login, I bet that you have some code that
>>actually performs a write, such as a Push-Fields.
>>
>>BMC has "fixed bugs" in the license allocation, and this might cause license
>>usage to increase. I think the major thing happened in 7.6, but I am not
>>sure...
>>
>>Turn on your user log, and check your license usage. Is it correct?
>>
>> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
>>
>>Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12):
>>* 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.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
