Generally what I do when I come across this type of situation is I EDTOBJAUT
on the given command and see how they are currently set up.  I see on our
system it is also set up:

 User        Group       Authority
 QSYS                    *ALL
 QSRV                    *USE
 QSRVBAS                 *USE
 QSYSOPR                 *USE
 QPGMR                   *USE
 *PUBLIC                 *EXCLUDE

which basically means the system, programmers and the security officer can
run the command.  If I wanted someone else to use this command I would add
them as *USE.

EDTOBJAUT is generally the first place I look when securing or unsecuring


Jim Langston
Cels Enterprises, Inc.

-----Original Message-----
[]On Behalf Of Bale, Dan
Sent: Monday, August 20, 2001 2:40 PM
Subject: [Security400] "Not authorized to command XXXXXXXX"

Am I correct that I can give the group profile for admins *USE authority
to the STRHOSTSVR command to solve our dilemna?  Or is there something
else that needs to be done?

Dan Bale

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.