[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

3902.0. "What's wrong with SM_USED_UIC.DAT" by HTSC12::MICKWIDLAM (DECwalker for OpenLIFE, V1.0) Mon Feb 21 1994 09:48

I have a customer using V2.3 got a problem.

There are some users created thru. A1 got the same UIC. The basic reason is that
the job for creating a user is put on a batch queue which allow several job to
be executed at the same time. When the jobs check the UICs together, they may
generate a same UIC at the same time (as the jobs checked the UIC is not
existed). This cause the major problem. I asked him to set the batch queue to
allow only one job for execution so that the UIC is added to UAF before the next
job read the UAF file and rebuild the UAF file. This may primarily solve the
problem.

But when the user look deep into the command procedure MUA_CREATE.COM, he
reported that the file SM_USED_UIC.DAT is not written during accout creation.
Then what is the use of this file? This file is supposed to be the file stores
the used UIC. Each time a new UIC is created, the UIC should put into the file.
But it is not done in their version (their file got only one UIC entry:
[000200,000200]). What wrong?


Regards,
Mickwid, HK MCS.
T.RTitleUserPersonal
Name		DateLines
3902.1not writtenIOSG::TYLDESLEYMon Feb 21 1994 10:2622
    Hello Mickwid.
    Your analysis of the situation seems to be correct. I can't find any
    evidence of a write to this data file in the V2.3 mua_create. It would
    be quite easy for your customer to customize mua_create in oa$lib: to
    write away the uic group and member number chosen, in the correct
    format (vms_uic = "[" + exp_uic_group + "," + octal_mem + "]") for the
    search that is done. I don't have a V2.3 system here to try this out,
    sorry.
    
    I'd be very suprised if this hasn't been noted before, and one of the
    other Support readers of this conference could perhaps point you to a
    Stars article that gives a fix for this. A reason that it may not have
    caused much trouble, is that a 'random' member number is chosen on this
    method, so there may have been few clashes.
    
    In later versions (V2.4 onwards) a completely different method of
    choosing unused UICs was adopted, so this problem would have gone away
    very quickly. Thanks for your help.
    Regards,
    DaveT
3902.2v2.3 too old even for the DPC?AIMTEC::WICKS_AAtlanta's Most (In)famous WelshmanMon Feb 21 1994 13:169
    since this note was posted twice 3901 and 3902 i've deleted 3901
    
    please also note that v2.3 is unsupported in most of the civilised
    world (except for the u.S) and you should upgrade to a supported
    version e.g v3.0 as soon as possible.
    
    regards,
    
    Andrew.D.Wicks
3902.3can't upgradeHTSC12::MICKWIDLAMDECwalker for OpenLIFE, V1.0Tue Feb 22 1994 01:3612
Thanks for your help.

I've also asked the customer to do upgrade. But they refused to do so as they
have some customized feature to make them can't upgrade. May be I should modify
the MUA_CREATE.COM to fix this problem.

If there is any STAR article contains the fix for related problem, please help
me to locate.


Thanks,
Mickwid.
3902.4we even have "Customization Management"IOSG::TYLDESLEYTue Feb 22 1994 09:159
    Mickwid.
    >>> I've also asked the customer to do upgrade. But they refused to do
    >>> so as they have some customized feature to make them can't upgrade.
    
    I'm a bit worried about this. ALL-IN-1 is designed to upgrade AND
    preserve customizations. In fact, it's rather good at it! Can you supply 
    more details of their customization?
    Best regards
    DaveT