Re: Executable commands vs. programming commands

I have created commands with the "where allowed to run" value of *IPGM *BPGM
*IREXX *BREXX (even though I don't use REXX). These are RTVxxx type
commands that return a value.

I could just as easily restrict those commands to *IPGM *BPGM. Wouldn't
those commands then appear to be programming only commands? If you DSPCMD
RTVJOBA, it shows as where allowed *IPGM *BPGM *IREXX *BREXX which would
indicate it's a programming only command.



On Tue, Jan 11, 2011 at 11:54 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 1/11/11 8:19 AM, David Gibbs wrote:

Does anyone know if there is an easy way to identify commands, based
on attributes, that actually execute programs vs. those that are
just used for CL programs?

Example:

PGM, ENDPGM, and DCL are programming only commands.
RTVJOBA, CRTPGM, DLTF are executable commands.

That a command is limited to only program-flow\statement versus at a
command line is determined by the "Where allowed to run" values of the
command; i.e. those with either or both, *IPGM and\or *BPGM, but with no
other allowed modes.

The CMDI0100 Format of the Retrieve Command Information (QCDRCMDI)
API returns the "Where allowed to run" information of a *CMD object.

To distinguish probably if an OS or LPP command, the CPP library
would be the QSYS or a product (option) library; the object "Licensed
program" information of the *CMD object could be used instead, or just
to corroborate the inference.

Regards, Chuck
--
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.