Donna,

   Not an answer to your original question, but a recommendation.....

   Consider creating a group in another account instead of SYS.  (I'm using
one named SYSTEM.)  It makes it easier to see what is HP provided, and
makes it easier to locate and move to a new system if you ever upgrade.

David N. Lukenbill
Computer Sciences Corporation




Please respond to Donna Garverick <[log in to unmask]>

To:   [log in to unmask]
cc:    (bcc: David N Lukenbill/LOU/Raytheon/US)

Subject:  sys command group?



hi all!

here's an interesting question (i hope :-)....

i'm wanting to setup a group (in the sys account) that only
'op' and 'sm' users have 'x'ecute access to but only 'sm'
users have all the other accesses to (particularily write).
i'm going to place command files in this group that are
meant for 'op' and 'sm' users only.  (wish i could control
listfile too <sigh>)  my intent is to 'unbundle' as many
(annoying) udc's as i can from the operator's udc file.
(ignoring the eight-character file limit <sigh>)  whatever
this group is, it would be added to 'op' and 'sm' users
hppath.

while i could front-end each command file with a hpusercapf
test, that creates a long-term maintenance issue....  if i
could invent my own capability (like (gee what letter
combinations are left?) 'zz'), i could give operator.sys and
manager.sys (and a few others...) 'zz' capability and set
all the group's access permission accordingly.

i guess acd's would work....but again there's that long term
maintenance issue....

any other ideas?             - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<