• Subject: Re: Problem with two Pfiles in a logical ?
  • From: Carel Teijgeler <teygeler@xxxxxxx>
  • Date: Tue, 07 Nov 2000 20:48:49 +0100

"Bankston, Jeff" wrote:

> I'm having a problem with a logical file created over two physical
> files.  We've archived old records from a production file into a
> different library and removed them from production.  Now I need to
> combine the records from both files back into a single file for
> special monthly processing.  I built a logical file and named both
> files on the PFILE keyword.
> A          R ALRTCAR                   PFILE(SISDTA250/ALRTCA +
> A                                             SISDTAARCT/ALRTCA)
> A          K CAREFN    R
> A          K CAUNIT     R
> A          K CASSEQ    R
> Two problems.
> 1) We I run a RPG-ILE program using the new logical the program blows
> with an error stating that the record format was used more than once.
> 2) The logical file is not visible when trying to connect with ODBC
> from M$ Access nor is it visible from inside Operations Navigator
> either.
> Thanks,
> Jeff Bankston


You have two options:
1) Create a multiple record format LF, each record format referencing
one PF and list the fields and key fields you want to use on those PF's.

2) Create a join LF on the two PF's, listing the fields from both PF's
and the key fields you want to use.

I hope I put you in some direction.

Carel Teijgeler

| 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

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].