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


  1.  Home
  2. MIDRANGE-L
  3. January 2011

Re: Executable commands vs. programming commands

David

The ones for which you got the CPF6250 are for use in CMD definitions only - they are not exactly CL commands - I know, they have the *CMD object type! I got that error when doing the DSPCMD on one of them.

Vern

On 1/11/2011 11:32 AM, David Gibbs wrote:
On Tue, Jan 11, 2011 at 11:19 AM, David Gibbs<david@xxxxxxxxxxxx> 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?
Thanks for the input folks ... I wrote a java program that spins through all the commands in QSYS and checks the *EXEC attribute.

Interestingly, I got a CPF6250 on these commands:

CMD
DEP
ELEM
ENDPGMEXP
EXPORT
PARM
PMTCTL
QUAL
STRPGMEXP

I'm just going to add those commands to the non-executable list.

If you're interested in the program that I'm using, check out http://midurl.com/v

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.