Re: Securing a command from command line.

[Jonathan Mason <masonjo1@xxxxxxxxxxxxxxxx>]

Hi Rob

Does the command have a validity checking program associated with it?  If not 
you could create your own routine that checks the call stack to determine 
whether the command has been called from within an HLL program or not and act 
accordingly.

All the best

Jonathan

-----Original message-----
From: rob@xxxxxxxxx
Date: Thu, 10 Mar 2005 19:34:15 +0000
To: midrange-l@xxxxxxxxxxxx
Subject: Securing a command from command line.

> 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.
> 


Jonathan Mason
www.astradyne-uk.com