| Hello Mike.
seasons greetings to you.
>>What I would like to do is have a default template account for the
>>VMS process privs, but use the UAR entry form as another template.
>>This UAR entry form has, rights ids, last login info, disk and
>>directory info, DDS info and ALL-IN-1 user specific information.
>>In other words I need to define a customized template for account
>>creation, it would however be unique to each user I am maintaining.
>>Possible?
-----
I don't see any reason why we couldn't make this work with a bit of
hacking ;-) One thing though, the reason we call them templates is
because they are fixed, relatively unchanging sets of data that can be
applied to many account creations. By definition, then, your forms will
not be 'templates' because they change for each account created.
We have had a (sort of) request like this before, and I have played
with 'on-the-fly' editing of the templates, while in the normal CU
process (e.g. GOLD EXPAND on the template field).
But another way to do it, would simply be to call your UAR form(s) at
the end of form SM$CREATE. The question then becomes "how interactive
do you want you customization of Create User to be?"
Do you want to do away with the batch job that runs now, and run the
creation in real time? If (and I hope this is the case) you do not,
then we are faced with the problem of transferring the interactive data
input by yourself to the batch job that runs under the manager account.
This should not be very difficult, (in fact Global edit, which I have
been re-aquainted with recently, does something similar). Then I think
that MUA_COPY_TPL called from sm_cr_user_details would be the place to
look to start fitting in the additional interactive account details.
UAI$ and RIGHTS$ could help us a lot here.
If you want to publish a location where I can look through the UAR
forms/scripts/coms etc. then I'd be happy to do so.
One last thing, I see that you are 'migrating to V3.0' - are you
upgrading from V2.4 to V3.0? (there are profile changes/conversions at
this time, so it would be a good time to build in the new CU).
Cheers
DaveT
|
| <<< hacking ;-) One thing though, the reason we call them templates is
<<< because they are fixed, relatively unchanging sets of data
Yes a hack it is indeed. Templates would not be the word here. I would
have approx 2k "templates to deal with".
I want to get them as close to vanilla as possible. I have managed to
clean up tons of coding, however the new DSABS and the general
structural changes in the FILECAB and PARTITION leave me to believe
that vanilla is the ONLY option.
Basically the UAR entry form has relevant account data. An
administrator types in new data (add, change, delete) some validation
is made on who the person is, department, disks, rights IDs and DDS
registration.
The system manager then accesses the same entry form, but of course
gets more (technical data). The validation of data occurs here.
Changes can be made here, i.e. disk, rights IDs, etc. etc. Once the
form is complete we are off to VMS land (account creation) and then
ALL-IN-1 land (profile creation) etc. etc.
Since I have most of the data in the UAR entry form already I could
munge the ALL-IN-1 vanilla template with this, throwing out of course
any ALL-IN-1 vanilla template data. The killers here are:
Template data restricts to six disks
Template data has no knowledge of rights IDs
Template data has no knowledge of VMS account flags.
So I would have to customize both the Templates and the command,
script files, as well as the UAR system.
<<< But another way to do it, would simply be to call your UAR form(s)
<<< the end of form SM$CREATE.
Great idea!! I had them (UAR forms) feeding the SM$CREATE
forms......Can you hear the saws...hack.. hack... Way too much coding.
<<< Do you want to do away with the batch job that runs now, and run
<<< creation in real time?
No. The error reporting and general feel of the system management
sub-system is excellent work. I want to use as much as possible.
<<< One last thing, I see that you are 'migrating to V3.0' - are you
<<< upgrading from V2.4 to V3.0? (there are profile changes/conversions
<<< at this time, so it would be a good time to build in the new CU).
Yes, April is set for these systems. So I have plenty of play time.
Thanks for the input, I will examine the Templates and the extracting
of data from them more carefully.
Happy holidays! Best wishes in the New Year.
-Mike Z.
|
| Good! This lot is nooooo problem:
> Template data restricts to six disks
> Template data has no knowledge of rights IDs
> Template data has no knowledge of VMS account flags.
----
At present guess I would say write this lot away into a temporary file
created off UAR forms, off Create User. Open up the temp file in
sm_cr_user_details, and read in the VMS specifics you want during the
creation of the VMS account.
There would, of course be lots of tidying up around this, for which you
would charge buckets of $$s!!
Let me know how your ideas progress, and then you can help me test
Multiple Create User ;-)
Have a nice vacation
davet
|