RE: Join & Update

You don't have to go through your programs to make them use the format
selector program.  It's specified on the CRTLF command.  

When we moved to the AS400 I converted a 17 format file to 17 physical files
with a multiformat logical using a format selector program.  It worked great
and we ended up with a much more manageable database.  The IBM docs to do it
were pretty clear but I don't remember which book it was in.  We named the
new logical with the same name as the old physical file so we did not have
to change any of our programs.


Larry Paque
Echo Service Company
larry@scjins.com

-----Original Message-----
From: Jim Langston [mailto:jlangston@conexfreight.com]
Sent: Monday, October 18, 1999 2:17 PM
To: RPG400-L@midrange.com
Subject: Re: Join & Update


Well, the problem with this is I would still have to go though every program
and use the "record format selector program" and if I'm going to do that I
might as well break them up into two separate files anyway.

I don't want to have to go through every program and change the code, since
I just don't have the time to do it (notice the use of the word "I" here,
and not

"we").

Regards,

Jim Langston

Scott Klement wrote:

> Jim,
>
> It seems to me that you probably want a multi-format logical, rather
> than a join logical....   With a multi-format logical, (and perhaps
> the help of a record format selector program -- at least temporarily)
> you should be able to do what you're looking for...
>
> At least, if I understand what you're saying :)
>
> Jim Langston <jlangston@conexfreight.com> wrote:
> > Updateable joins would make my life *SO*  much simpler.  I have one
> >  file
> > on my system (thank goodness it is only one) that uses a dual format
> > Unfortunately,
> > this is our AR file and is used in something like 1/4 of our program
> >   All the
> > other files have been converted to DDS no problem.  But, this one is
> >  the problem.
> >
> > For this one we are still internally describing it, our only other
> >  option is to
> > break it
> > into two files then go through every single program and change them
> >  use one,
> > the other, or both files.  Something we just haven't had the time to
> >  invest into.
> >
> > An Updateable join would work perfectly, and we wouldn't have to do
> >  this.
> > We could just break it up into two files (which we already have
> >  created, by the
> > way, but can't really use) and then do an Updateable join logical on
> >  them, and
> > all our
> > programs would still work as written, and then we could change the
> >  programs to
> > use externally described files.
> >
> > This limitation, to me, has always been the one major drawback to
> >  logical joins,
> > and is the only reason we would want to use one anyway.
> >
> > Anomalies, smomalies, as long as it works <g>
> >
> > Regards,
> >
> > Jim Langston
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---