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



Slap me....  This is much better than calling the CPP directly...

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: Elvis Budimlic [mailto:ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, February 22, 2005 7:35 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Executing a command within RUNSQLSTM


Yes, by calling system command interpreter as SQL stored procedure.
Create a source member with a call like this:

CALL QSYS/QCMDEXC('DSPJOB OUTPUT(*PRINT)', 0000000021.00000);

and then execute it the way you normally do.  
In my case I used system naming scheme and no journaling so my call looked
like this:
RUNSQLSTM SRCFILE(ELVIS/H) SRCMBR(CALLCMD) COMMIT(*NONE) NAMING(*SYS)

HTH, 
Elvis

-----Original Message-----
Subject: Executing a command within RUNSQLSTM

Is there a way to execute a command within a RUNSQLSTM execution or do
I have to create a stored procedure?

Thanks,
Reeve


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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.