Cool. With SEQUEL, however, there is no CL necessary. It's done with a
script, which allows for run time variables to be passed to the SEQUEL
statements. If you're going to output data, the EXECUTE statement has all
kinds of formats built in.
It all boils down to make a hammer or buy a hammer. One can dig a huge hole
with either lots of laborers, shovels and wheelbarrows, or with a backhoe
and one operator. Cost effectivity is the message I try to deliver to my
clients.
Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx
[mailto:midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx] On Behalf Of
Nathan Andelin
Sent: Thursday, August 09, 2007 11:40 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL views
Paul N. wrote:
The whole project took me about 90 minutes. Try doing the same
thing in the same time frame with the "native" tools.
Good example. And one that demonstrates the value of tools like SEQUEL.
For what it's worth, I wrote a command named SQL2STMF that outputs the
results of any SQL select statement to a stream file in various ASCII text
formats (one of which is CSV format) and it would be pretty easy to create a
CL wrapper around it to prompt for "from" and "to" date parameters and send
the resulting stream file from the IFS to a third party via FTP. Keeps all
the processing on the server - requires no extra software on the client.
Nathan.
As an Amazon Associate we earn from qualifying purchases.