Re: new IBM RUNSQL command

Or the MegaMillions numbers.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Friday, March 30, 2012 12:14 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: new IBM RUNSQL command

Wow - please suggest some stocks to buy (or sell) :)


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Friday, March 30, 2012 11:12 AM
To: Midrange Systems Technical Discussion
Subject: Re: new IBM RUNSQL command

I hear you.

Many years ago when I got a RUNSQL command from a magazine, I
*deliberately* changed it to ADHOCSQL in case this issue ever came up.

Finally, I look prescient.

:)


On Fri, Mar 30, 2012 at 11:15 AM, Stone, Joel <Joel.Stone@xxxxxxxxxx>
wrote:

http://www.mcpressonline.com/cl/the-cl-corner-introducing-the-new-run-
sql-command.html

Thanks for the great article Bruce!

One question - hundreds of custom RUNSQL type commands have been
custom-built at hundreds of iseries shops over the years.

These commands are used in production.

How can shops ensure old CL runs will continue to call their
home-grown RUNSQL command (instead of the new IBM RUNSQL command?)

This will surely cause havoc in many shop, as parm names will not
match and abends will occur in production jobs, some without source
(for packages, etc).



Many Iseries articles have been published over the years for a
home-grown CL SQL command, and most have used "RUNSQL" as the command

name.

Shouldn't IBM pick another name, so as not to cause hardship with so
many users?

I know other vendors were smart enough to name their SQL commands
something different than "RUNSQL", probably to avoid just this scenario.

If IBM introduced this command in the last century like other vendors,
I can understand them grabbing the obvious command name.

But decades late to the party, shouldn't they be cognizant of
identical command names in the iseries user community and name it

something else?

EXECSQL, CALLSQL, DOSQL, RUNIBMSQL, INVOKESQL, RUNSQLI, or million
other variations.

Tell me why this is not a concern, please, and I will go "oops". But
I have introduced this command in shops code and don't want stuff to
be croaking because parm names don't match up.



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

--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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.