|
Anyone think there is an IBM requirement buried in here?wrote:
Phil
On May 11, 2012, at 12:41 PM, "Gary Thompson"<gthompson@xxxxxxxxxxx>
one CL with the RUNSQLSTM command.
Got me!
-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Friday, May 11, 2012 1:37 PM
To: Midrange Systems Technical Discussion
Subject: RE: easier SQL statements in CL
My point exactly.
Gary Monnier
-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Friday, May 11, 2012 12:33 PM
To: Midrange Systems Technical Discussion
Subject: RE: easier SQL statements in CL
SQLCLLE ??? - does not appear as an option on our V7R1 box...
-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Friday, May 11, 2012 1:28 PM
To: Midrange Systems Technical Discussion
Subject: RE: easier SQL statements in CL
Have you ever heard of an SQLCLLE source type?
Gary Monnier
-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Friday, May 11, 2012 12:21 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: easier SQL statements in CL
None of these suggestions let me keep the SQL statements WITHIN the
my OP) into a qtemp source member and use RUNSQLSTM to run that?
Is there a way to do this?
Is it possible to copy data records from within the CL member (as in
messagenews:0B57EB3973113A47A96A7FD995D2B6E025A35895@xxxxxxxxxxxxxxxxxxxxx..
-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Loek Maartens
Sent: Friday, May 11, 2012 2:06 PM To:midrange-l@xxxxxxxxxxxx
Subject: Re: easier SQL statements in CL
Hi Joel,
Maybe you mean like in RUNSQLSTM ?
Kind regards,
Loek Maartens.
"Stone, Joel"<Joel.Stone@xxxxxxxxxx> wrote in
mess.There MUST be a better method of coding SQL in a CL source member.
Here is what an SQL stmt might look like that I created today:
PGM
DCL&SQLCMD type(*CHAR) len(1000)
chgvar&sqlCmd ('create table qtemp/sqltemp1' +
*tcat ' (fld1 char(1),' +
*tcat ' fld2 char(1),' +
*tcat ' fld3 char(1),' +
*tcat ' clientN numeric(6,0))')
RUNSQL(&SQLCMD)
I recall that others like to create a string with the MSG commands.
Is it possible to code the straight SQL statements with no
tricks in a CL source member (like in the old punch-card days to
suck in a few data
records?):)
Any method would be great if I can skip all the *tcats, and quotes
would
In the example below, is there a simple way to copy everything
between the "/*" to a source member and run that?
Or any other method to keep the CL together with the SQL
commands in the same member - without using quotes or tcat's.
Something like:
PGM
DCL&SQLCMD type(*CHAR) len(1000)
//start SQL
/*
create table qtemp/sqltemp1 (fld1 char(1) ---
fld2 char(1) |
fld2 char(1) |----
tcat'slike to run this nice readable SQL command in CL without quotes and
--client numeric(6,0)) ___|
/*
RUNSQL
Thanks!
As an Amazon Associate we earn from qualifying purchases.
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.