Funny you should say this. I tried to elicit some of these gotchas, if
you will, in a previous post, To fall from heaven. This came from the
data center wanting to take away my SM id. Since I am the only one here
with this ability, what I run into is the inability of others developers
to see things in other accounts from their sign on. I try to stick with
AM sign-ons regardless, using SM only as needed. I would still welcome
feedback on the gotchas that Leonard mentions... So far, I have:
resetting expired account passwords
>comparing files between accounts under our current configuration (I know that
>we could change the Read access, or copy files to an open group in one
>account, then sign on to the other account),
>REPORT on multiple accounts on a volume set (again, we could sign on to each
>one in turn),
>and under SECURITY/3000, "setup users with inheritance from other accounts".
And of course, setting up new accounts.

>----------
>From:  Leonard S. Berkowitz[SMTP:[log in to unmask]]
>Sent:  Thursday, November 06, 1997 8:45 AM
>To:    [log in to unmask]
>Subject:       [HP3000-L] Open Letter to Andreas Schmidt <g>
>
<snip>
>Just as a test, if you are accustomed to working on the HP3000 with SM + OP
>or
>AM + OP capability, switch to a logon with none of those and just try to
>figure out what things you can no longer perform. I guarantee that you will
>encounter many gottchas.
<snip>