[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

2972.0. "Non-priv'd user unable to SORT Sys Dist List - bug?" by MCIS2::BONVALLAT () Tue Jul 06 1993 21:54

We are running ALL-IN-1 V3.0 on several large timesharing systems.
I have just noticed that none of our non-privileged users are able
to SORT a System Distribution List even if they are an Editor
of the list (and they can successfully add/delete names from the SDL).
They either use the SO command or say "Y" to the question
"Do you want this list SORTED after editing ? [Y/N]" when they edit
the SDL - and in both cases - they get the messages "Sorting Distribution
List" and "Distribution List Sorted" BUT nothing sorts.

The ACL and protections look OK to me:

Directory DISK$ALLIN1:[ALLIN1.SYSTEM_LISTS]

ZUTFL3FLC.DIS;2           1   2-JUL-1993 14:47:39.04  [ALLIN1]              (RWE
D,RWED,RE,)
          (IDENTIFIER=OA$ADMIN,ACCESS=READ+WRITE+DELETE)
          (IDENTIFIER=[*,*],ACCESS=READ)

Is this a V3 bug?  feature?  problem on only our systems?   Thanks for any help.
T.RTitleUserPersonal
Name
DateLines
2972.1A customisation - use CM to see who!AIMTEC::WICKS_AU.S.A 2 England 0 - I was there!Tue Jul 06 1993 22:2817
    does it happen $allin1/nocustom? 
    
    you'll probably find that the Sorting of distribution lists is a
    customisation applied to your system - it isn't part of the base.
    
    given  that you either contact the author of the customisation or you
    switch trace on and see what that tells you.
    
    I wouldn't have thought it was a good idea to let non-priv'd users
    at System Distribution Lists anyway - surely you would only want
    System Administrators (people with the OA$ADMIN identifier) to do this
    and having more than a couple of those per system is definitely a case 
    of "too many cooks..."
    
    Regards,                                   
    
    Andrew.D.Wicks
2972.2Wrong Conference?SAHQ::WOLFEJohn Wolfe - (404)-924-6463Wed Jul 07 1993 14:2111
	This sounds like an "undocumented feature" in SYSUSER that was fixed
quite a while ago.  See Note 260.1 in ATLANA::A1-TOOLKIT.

	Andrew - Editors of individual SDLs need to be authorized by the
MANAGER in our customization so there is some control over who can get to 
the individual lists (many sites have hundreds of SDLs).

HTH

John