Re: easier SQL statements in CL

Anyone think there is an IBM requirement buried in here?

Phil

On May 11, 2012, at 12:41 PM, "Gary Thompson" <gthompson@xxxxxxxxxxx> wrote:

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 one CL with the RUNSQLSTM command.

Is there a way to do this?

Is it possible to copy data records from within the CL member (as in my OP) into a qtemp source member and use RUNSQLSTM to run that?



-----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 message news:0B57EB3973113A47A96A7FD995D2B6E025A35895@xxxxxxxxxxxxxxxxxxxxx...

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

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) |---- would
like to run this nice readable SQL command in CL without quotes and tcat's
client numeric(6,0)) ___|

/*

RUNSQL




Thanks!

______________________________________________________________________
This outbound email has been scanned for all viruses by the
MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
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.

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


________________________________________________________________________
This inbound email has been scanned for all viruses by the MessageLabs SkyScan service.
________________________________________________________________________

______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________
--
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.

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



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

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



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