The local attribute, IIRC, is something leftover from very long ago and is
basically unused by MPE, something like an appendix.  :-)

The local attribute can be easily changed with the ALTUSER command.  The
same goes for local attribute for accounts, also modifiable with ALTACCT.

Of course, NEWUSER and NEWACCT can be used to initially assign a value.

I seem to remember a program that actually checked the value for the user
and it had to be set properly for it to proceed.

You obviously have a program that does the same thing.

Denys

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Raymond Familar
Sent: Tuesday, December 06, 2005 9:13 AM
To: [log in to unmask]
Subject: [HP3000-L] MPE local attribute on userid

Hello.
I recently performed a failover test for an applicaiton that tracks some
userid information.  The local attribute (LOC ATTR) is tracked, so when a
user logs in on the DR system, if their LOC ATTR does not match, then they
cannot log in.  I do not recall this being much of an issue in past DR
tests, so I assume they matched during the last test (6-12 months ago). 
Under what circumstances would a userid LOC ATTR be changed.  We use Vesoft
Sec/3000 in our environment.

Thanks.
Ray

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *