×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi, David:
Also, CHGVAR, DCLF, DO, ENDDO, IF, RCVF, RETURN, SNDF, SNDRCVF, among
others. (Also, all of the command definition language commands and
binder language commands.)
Issue a DSPCMD for these, versus ones you know can run anywhere, to see
what is different about their definitions. For example:
DSPCMD IF
shows:
Where allowed to run . . : *BPGM *IPGM
while:
DSPCMD DSPCMD
shows:
Where allowed to run . . : *IMOD *BMOD *IREXX
*BREXX *BPGM *IPGM
*EXEC *INTERACT *BATCH
I think this is as close as you can get, by just examining the
attributes of the *CMD object itself.
The definitive way to find out is to create an OPM CL *PGM and compile
it with GENOPT(*LIST) and examine the generated MI assembly language
instruction listing. The "compile time only" CL commands generate
"in-line" code to perform data movement, comparison, arithmetic, and
conditional branching, etc., and only sometimes call a runtime
routine. All the others generate:
CALLX ?WWLISEPT(00277),?WCLCAARG,*; /* call QCAPARSE */
to parse and process the command.
HTH,
Mark S. Waterbury
On 1/11/2011 11:19 AM, David Gibbs wrote:
Folks:
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,& DCL are programming only commands.
RTVJOBA, CRTPGM, DLTF are executable commands.
Thanks!
david
midrange.com
