Yeah, you've run into the object-based nature of the IBM i - you can call programs, you can't call commands. Unlike in DOS, where a .CMD and a .EXE are both executables, a *CMD and a *PGM are different creatures. A *CMD typically ends up being the thing that calls a *PGM - there are alternatives, such as a REXX procedure that can be a command-processing procedure - probably more than you wanted to know, eh? :)

Cheers
Vern

On 10/25/2015 9:17 PM, Justin Dearing wrote:
On Fri, Oct 23, 2015 at 5:26 PM Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Justin

There are documents that fully explain all this stuff - if you look only
at the command parameters, you can get lots of information, but it's not
going to give you a full picture.

Hint taken, its time to RTFM regarding journals.

As to QCMDEXC -- it is already something that can be called as a stored
procedure - no need to register it - this is true about every program on
the system.

I meant registering ADDPFM as a stored procedure, but it seems the one
exception to "everything can be a stored proc on the IBM i" is CL commands.
I'm a little concerned about the potential for SQL injection for a proc
that passes a string to QCMDEXEC, but yes I need to read up, and initially
I'm writing a stored procedure only I will call on a system where I have
QSECOFR.


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].