T.R | Title | User | Personal Name | Date | Lines |
---|
2121.1 | I think we've done this one before | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Tue Jan 19 1993 15:07 | 8 |
| I think this is a "known problem" that has been discussed elsewhere in
this conference.
There are several possible workarounds. You could customise the form
to add a /OPTIONAL qualifier to the field, for example. Directly using
WRITE CHANGE PROFIL USER="bloggs",VMSUSR="" would work, etc.
Scott
|
2121.2 | How to leave the field empty ... | BRUMMY::MARTIN::BELL | Martin Bell, TCC, Birmingham UK | Tue Jan 19 1993 15:08 | 10 |
| Jason,
if you want to "get around" this validation, when you are on
the VMS account name field, type GOLD KP7 followed by OA$VAL_SET_VALID
which will convince ALL-IN-1 that you have filled the form in correctly.
It may b*gger something else up along the way however, 'cos ALL-IN-1
does make a big use of ACLs and the like these days!
mb
|
2121.3 | Don't | IOSG::TALLETT | Gimmee an Alpha colour notebook... | Wed Jan 20 1993 10:11 | 9 |
| >I have a customer who is trying to set up an ALL-IN-1 account that can be
>accessed by several VMS accounts.
We don't recommend this, which is why the validation disallows it.
Why not have an ALL-IN-1 account for each user or a guest account
for them all to use?
Regards,
Paul
|
2121.4 | Don't believe everything you read... | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Wed Jan 20 1993 11:46 | 9 |
| re .3 >> we don't recommend this
I was going to say that, but according to .0, the management guide
tells you how to do it, so obviously we are recommending it!
If we aren't supposed to be recommending it, then we should get the
books fixed... SPR time, methinks.
Scott
|