Re: SQL vs DDS

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxx>]

Rob Berendt wrote:
> 
> I try to get away from this as much as possible, but I used to write 
>applications
> that contained CRTPF commands that used DDS.  I thought about the RUNSQLSTM
> command.  Thought this would be a neat area to keep my SQL source for my
> files.  However RUNSQLSTM doesn't work on the production machines.  Perhaps
> I could put the source into a Query Management Query.  While the prompter
> (STRQM) is only available on the development machine, it can be run,
> (STRQMQRY, CRTQMQRY, etc) on any machine.  In fact we use STRQMQRY in the
> RUNSQL command to give us a poor man's SQL on the production machines.
> 

Have you tried configuring a remote database? WRKRDBDIRE and name the
local and configure the remote.

Next, issue the CONNECT TO remote_system_name.

Now issue the commands. They happen on the remote, without the SQL
toolkit on the remote.

I have also used this to correct data in a V2R3 machine from a V4R2
machine. Just set up the remote database in the directory, establish the
connection (which at the time was a 2400 baud, through the ECS modems,
SDLC connection) and execute the connect, then execute the update and
delete commands. Worked like a charm. Saved the customer dozens of hours
of my time.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---