Re: Storing SQL script options -- MIDRANGE-L

Subject: Re: Storing SQL script options
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Wed, 27 Mar 2019 10:46:47 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I use REXX. It's a reasonable cross between SQL and CL.

https://www.mcpressonline.com/programming/sql/techtip-calling-sql-from-rexx

On 3/27/2019 8:50 AM, Jim Oberholtzer wrote:

In my view, rather than spend $0.10 on updating RUNSQLSTM I'd much rather IBM put an SQL precompiler into CLLE, (AKA like every other language has) so there is a CRTSQLCLE command.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Storing SQL script options , Rob Berendt

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.