IDDU, S36 & AS/400 SQL & RPG

[John Carr <74711.77@xxxxxxxxxxxxxx>]

RE:     IDDU, S36 & AS/400 SQL & RPG

>Greets from a longtime lurker!
>I've gotten some great knowledge from many of you in the past, and now it's
>time to ask a question that's been troubling me.
>I've got an F-20 running V3R1.  My main application is a S36 app that we
>bought from a vendor.  It's my job to extend that application at times.
>What I've been doing is (re)describing the data files in my RPG programs,
>and wrapping the RPG in a CL program that does an OVRDBF command.  Also, I'm
>using Query/400 a lot, and would like to see if SQL would have any
>performance benefits, but SQL won't access the files. 
>They are described with IDDU and Query/400 doesn't need to use any overrides
>to get at them, so I'm wondering if there's any way to make RPG (400 or ILE
>IV) and/or SQL use these descriptions ( to make the files External in RPG
>for example instead of program described) ?
>If I've left any thing out that would help you give me an answer, just let
>me know and I'll add to the picture.
>TIA Shawn Althouse  MIS Director  Monmouth County Correctional Institution 
>

Welcome long time lurker;

Shawn 
The major point is that it's a 3rd party package.  I don't know how much
you are authorized to change their stuff.   The easiest way to have your
cake and eat it too(without rebaking it) is to create logicals over the 
physical files that do not have DDS.  What the system currently sees of
your PF's is one big field(record length).    You can create logicals 
and use the substring function in the LF DDS to parse out the fields. 
Now you have DDS and leaving the system alone at the same time.

You can make indexes over the LF's.  Now you can use OPNQRYF, SQL and 
native RPG(externally defined inside the pgm)

This is the first thought off the top of my head.

There may be other ways that you will hear in the comming days.

John Carr
EdgeTech
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---