[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

3644.0. "Use DSAB to set VMS account CAPTIVE .." by TAV02::CHAIM (Semper ubi Sub ubi .....) Wed Dec 08 1993 09:18

Does the DSAB for accessing the SYSUAF file contain a field for modifying any
of the flags?

A customer wants to modify the create user so that any VMS account created will
be CAPTIVE. I took a look in the script file which does the create details for
the VMS account. At the very end it also issues a DCL command to invoke
authorize (not very elegant). So, I suggested that we just add /flags=captive
at this point.

However, I would much rather use the DSAB mechanism if avaiable to set this
flag.

Thanks,

Cb.
T.RTitleUserPersonal
Name
DateLines
3644.1use the dsabIOSG::TYLDESLEYWed Dec 08 1993 10:0717
    Cb.
    >>> ..the script file which does the create details for the VMS  
    >>> account. At the very end it also issues a DCL command to invoke
    >>> authorize (not very elegant).
    ----
    This is the only way it could be done, because of the way the UAI$
    works. Scott, who wrote UAI$ will explain in more detail. I've
    forgotten right now.
    
    You do not need to use this 'inelegant' mechanism and the /flags
    qualifier, because you can: 
    <write change UAI$ username=#username, captive = "1"
    See Application Programming Ref Vol 1, page 7-123.
    
    Cheers
    DaveT
                               
3644.2I'm embarrased ...TAV02::CHAIMSemper ubi Sub ubi .....Wed Dec 08 1993 10:3314
>    
>    You do not need to use this 'inelegant' mechanism and the /flags
>    qualifier, because you can: 
>    <write change UAI$ username=#username, captive = "1"
>    See Application Programming Ref Vol 1, page 7-123.

I'm embarrased, and I guess I was a little lazy.

BTW, why does the sm_create_user_details script issua a dcl AUTHORIZE at the
end to set /PWDEXPIRED. Couldn't this have been doen via the DSAB as well.

Thanks,

Cb.
3644.3will doIOSG::TYLDESLEYWed Dec 08 1993 10:5912
    Hi Cb.
    No need to be embarassed - UAI$ docn. is a little hidden ;-)
    
    re sm_cr_user_details. At the time that this was converted to use UAI$,
    UAI$ did not support setting the password expired. This was added at a 
    later date and since that time we have not had the resource to make and
    test the change to use the dsab. (it's not a big fix, but it consumes 
    testers, PA etc.) I agree it would be nice to do, and will add it to my
    list of nice-to-do's... (need a new whiteboard!).
    
    Thanks for the reminder.
    DaveT
3644.4CAPTIVE works?BIGMAC::KARPELThu Jan 06 1994 19:034
    I thought I recalled a problem with the CAPTIVE flag and ALL-IN-1
    printing.  Don't you have to use RESTRICTED?
    
    TK
3644.5STARS says....AIMTEC::WICKS_AAtlanta&#039;s Most (In)famous WelshmanThu Jan 06 1994 19:238
    CAPTIVE v RESTRICTED last discussed in note 2151 of the previous
    version of the conference.
    
    That note interestingly was posted by one Chaim Budnick!
    
    regards,
    
    Andrew.D.wicks