| Hi Marcia.
>>> I have a customer who is running ALL-IN-1 version 3.0. We have just
>>> upgraded ALL-IN-1 and he has a lot of account templates created in version
>>> 2.3.
======
I'm pleased to hear that the 2.3 -> 3.0 sm_account_types.dat conversion
went OK. ;-)
>>> The problem is that most of these templates had an "*" in the field
>>> Group Uic and some didn't have anything.
======
Yes. It is possible to store a "*" in the sm_account_types data file. I have
just inserted one in a template record here, in the field UIC_GROUP.
Obviously, creating new accounts from scratch fails with this. The manager
gets the message 'Failed to create new SYSUAF entry' and examination of the
Create Log reveals:
"If not re-using a VMS account, creating the VMS account ...
UIC member number from UIC allocation file = 1
The value entered is not a valid identifier
Status returned from Make_UIC = 0"
If, however, as is the case with your customer, the VMS account already
exists, then this part of sm_cr_user_details.scp would be skipped, and the
new ALL-IN-1 account should be happily created on top of the existing VMS
account. So, there is a danger in having the * in the template, but only
when creating completely fresh accounts (i.e. ALL-IN-1 + VMS).
So, it would be advisable for them to get the "*"s out of the template file
(blank values would fail in the same way). So, that brings us to your
requirement to edit the templates:
>>> Now when I try to edit this field , version 3.0 wants me to fill it out
>>> with a valid uic group.
========
Yes. There is some quite comprehensive validation of the UIC Group number
done by oa$sm_dtc_validate_uic.com, which hangs off the UIC_GROUP field.
You have a number of alternatives at this point:
a) Go into SM to edit the field concerned:
MGT DTC {SELect template} E
Tab to the field UIC group number, ensure it contains something (e.g.
a "*") and then do GOLD KP7
Enter Command:OA$VAL_SET_VALID {RETURN}
You should then be able to TAB on down through the fields, and close the
form, save the edits, etc. This will leave you with a template, in V3.0
with * in the Group UIC field
b) you can write change direct to the field in the file, e.g. in a small
script, which loops round all your templates with a FOR loop:
<write change smtemplate template="PRIV_USER", uic_group="100"
This wouldn't take much to write, and would improve your customer's
set of templates.
c) How many templates do they have exactly? Most sites run with only about
max 10/12. Surely editing these is not too difficult? Perhaps they could
use Template Global Edit? (MGT DTC I {build index} GE)
>>> This customer creates the Vms accounts before creating the a1 account,
>>> that's why they don't have this field filled out or they put an
>>> asterisk. But now ,they are complaining of having to change this in all
>>> the templates they have.
=======
Well here they need a careful talking to! I know that they are always right,
but V3.0 does like to have its VMS accounts set up by ALL-IN-1. Obviously,
it's not mandatory, but it does help to get things like identifiers,quotas,
protections, directories etc. set up correctly, which is good for the shared
file cabinet, amongst other things. Besides which, it is a lot easier to
create VMS accounts from within ALL-IN-1 than from VMS ;-). So, perhaps in
future, you might encourage them to do it this way.
>>> It seems that ALL-IN-1 3.0 does a validation in this field and this
>>> didn't happen in the old 2.3 version.
======
Correct. See above.
>>> I would like to confirm if this is the correct way in 3.0 or am
>>> I missing something ?
======
No you are not missing anything (except perhaps Template Global Edit).
Hope this helps.
Regards,
DaveT
p.s. some rude colleagues of mine might chastise you for your spelling
of ALL-IN-1
|