Re: Securing a command from command line.

You're probably right with the CLP.  Although that's dragging me kicking 
and screaming from my tendency to move away from cl and imbed all commands 
into a hll program instead.  That, and now I would have to look at all hll 
code to find any possible uses of that command and change those 
accordingly from qcmdexc to a cl call.

I think that moving the IBM supplied command to a library that's not in 
any user library list would involve changing all code that uses it to 
hardcode the library name.  Just about as ugly as changing all code from 
QCMDEXC to a CL call.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





MWalter@xxxxxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/10/2005 02:37 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Securing a command from command line.






You could wrap it with a CLP, but that's sort of a half-baked fix, isn't
it? Could you move the command to a library that's not in a users' default
library list?

Thanks,

Mark

Mark D. Walter
Senior Programmer/Analyst
CCX, Inc.
mwalter@xxxxxxxxxx
http://www.ccxinc.com


 
             rob@xxxxxxxxx 
             Sent by: 
             midrange-l-bounce                                          To 

             s@xxxxxxxxxxxx            midrange-l@xxxxxxxxxxxx 
                                                                        cc 

 
             03/10/2005 02:34                                      Subject 

             PM                        Securing a command from command 
                                       line. 
 
             Please respond to 
             Midrange Systems 
                 Technical 
                Discussion 
             <midrange-l@midra 
                 nge.com> 
 
 




I want people to not use a certain command from the command line but using
it in a program is ok.  I even want to restrict QSECOFR so LMTCPB is not
the option.  First thought was CHGCMD and take away *INTERACT.  However,
that killed the use in a program.  I thought *IPGM was all I needed.
However *IPGM is pretty insistent that the program be a CLP.  Trying the
command with QCMDEXC in RPGLE blows up after you remove *INTERACT.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.