On Feb 15,  1:23pm, Chris Bartram wrote:
> Subject: One more for the X.50 (5.0 Pull) list of quirks...
> Dunno how this happened, but...
>
> :listuser mgr.<ouraccount>
> ********************
> USER: MGR.<ouraccount>
>
> HOME GROUP: PUB                 PASSWORD: **
> MAX PRI   : 150                 LOC ATTR: $00000000
> LOGON CNT : -17
> CAP: SM,AM,AL,GL,ND,SF,BA,IA,PM,MR,DS,PH
> :
>
>   Interesting logon count huh?
>
>                          -Chris Bartram
>
>
> ______________________/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
>    ______              Sales (US):   800 Net-Mail    Fax:+1 916 622-0738
>   /__ |  \__________   -or-       +1 916 622-0630 E-Mail: [log in to unmask]
>  /  / | / ________     Sales (Europe):+44(0480)414131 Fax:+44(0480)414134
> |  /_ |<  ______       Tech Support:+1 703 569-9189  Fax:+1 703 451-3720
>  \ __)| \ ___          E-mail: [log in to unmask]   Personal(me): [log in to unmask]
>   \______/ Associates  6901 Old Keene Mill Rd Suite 205 Springfield VA 22150
> ______________________/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
> Gopher: gopher.3k.com   Anon-FTP: ftp.3k.com  WWW: http://www.3k.com/
>-- End of excerpt from Chris Bartram
 
Chris,
There is an SR for this problem SR 4701-216994. The incorrect logon counts
result when a program issues an AIFCHANGELOGON to a new identity with
the global option set and does not AIFCHANGELOGON back to the original
identity. The documentation warns "Any program which has called
AIFCHANGELOGON and has used the options parameter to change the global
logon environment must call AIFCHANGELOGON again to restore the logon
environment to its original state before terminating." Since jobs
or sessions can abnormally terminate the applications may not be
able to return to the original logon identity. There is no fix
available at this time. I agree the fix will make AIFCHANGELOGON more
resilient.
 
To correct the invalid logon count a reboot is required. The logon
counts get reset for the user the first time they logon after a reboot.
I filed SR 4701-284232 to request the logon count reflect correct information
when the user entry is read. The listuser command should display
correct information even if the user has not yet logged on.
I wanted to post this information on the net since this is a
known problem.
Best Regards,
Gail Duro
AIF engineer