Re: Executable commands vs. programming commands

On 1/11/11 9:24 AM, Jeff Crosby wrote:

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 wrote:

<<SNIP>>

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.

Thus the comment about verifying the library name of the Command Processing Program. AFaIK all program-flow command\statement objects would have only *IPGM and\or *BPGM [possibly additionally or only *IMOD and\or *BMOD for ILE CL], *and* a CPP from library QSYS [although I allude of possibility for a CPP coming from an LPP\option] with "license information" indicating the command supplied with the option. If the command is not from an OS or LPP command, then presumably the command would be user-created, just with similar limitations; whether\how the OP wants to count such a command is not clear to me. FWiW I believe most CL program-flow commands will also have the prefix QCL, and then the first several characters of the CL command name as the suffix; one exception for sure, is the CL command RETURN, but that is functional as a command outside of a pgm\mod.

Regards, Chuck