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



John,

You can use the RUNSQLSTM command. regarding what your CL would look like
depends on many things, including error monitoring and processing,
parameters, etc.
In its simple way it would be something like this:

PGM

RUNSQLSTM SRCFILE(MYLIB/SOURCEFILE) +
SRCMBR(SQLSRC) +
COMMIT(*NONE)

ENDPGM

Please be aware that, in this example, I set the COMMIT option to *NONE.
Your settings can be different... Also, you can run your RUNSQLSTM directly
from the entry of the job scheduler (although I, personally, prefer to
execute them from inside a CL)

HTH,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


On Tue, May 18, 2010 at 8:53 AM, John Candidi
<jacandidi@xxxxxxxxxxxxxxxxx>wrote:

Novice SQL. If I have an SQL SRC file and I want to call that with a
simple CL program to execute via job scheduler, what would the CL program
look like?

John A. Candidi
American European Insurance Group
IT Systems, Application and Support Manager
Cell (609-922-3108)
Office (856-779-2274)
jacandidi@xxxxxxxxxxxxxxxxx




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