• Subject: Re: Non-Join Multi PF Logical File Format
  • From: "David Shea" <dshea@xxxxxxxxxxxx>
  • Date: Wed, 24 May 2000 11:24:39 -0400

In RPG you would do your example as follows:
     A          R AREC                      PFILE(A)
     A          K FLD1                                
     A          R BREC                      PFILE(B)
     A          K FLD1                                
 
This sorts the records properly, but returns different record formats.
 
I'll be _very_ curious to know if Cobol can actually do what I _wish_ RPG could.
 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Time share a current model AS/400 over the internet!
Individual developers, company development and testing, or full outsourcing.
Get access to RPG, Cobol, C, SQL, Java and more for a low monthly fee.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
----- Original Message -----
From: David Keck
Sent: Wednesday, May 24, 2000 12:06 PM
Subject: Non-Join Multi PF Logical File Format

Can a COBOL program work with a non-join logical file record format which references more than one PF (more than one PF in the DDS PFILE entry) ?  I know RPG programs can NOT compile if they reference such a file.  For example ...
 
Physical File named "A"
     A          R AREC              
     A            FLD1           1A 
Physical File named "B"  (In this case the entire record format for file AA is identical to that of file A)
     A          R BREC             
     A            FLD1           1A 
Logical File named ABLF
Non-Join Multi-PF Logical File Format (in this case the only format in the LF)
     A          R AREC                      PFILE(A B)
     A          K FLD1                                

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.