A multi-format file is created to handle different record types in one
file that are allowed on the System 36. Thanks to the great folks on the
list, I was made aware of it as a solution and it works like a champ for
legacy code! Anyway, the message from the subfile program was "The
arrival sequence was requested on an open of logical file member CORRUN.
Member CORRUN is based on more than one physical file member and must be
processed in a keyed sequence." The file spec is

CORRUN  UF      E                DISK                      A       

The program wouldn't compile with a "K" in pos 31. I'm not sure what
else to try other than working with the individual physical files.

Darlene Brengle
Norsoft, Inc.

Date: Wed, 13 May 98 20:24:20 -0400
From: boothm@ibm.net
Subject: Re: Subfile processing with duplicate keys

What is a multiformat logical file?  I don't understand why the RRN
unique and therefore suitable...?  (I don't question you, I just don't
understand it.  If its what I think it is, this must just one of many
problems you have to overcome.)

In <355A390A.2A2D@blazenet.net>, on 05/13/98 
   at 05:21 PM, Tim-Bar <timbar@blazenet.net> said:

>We have a multiformat logical file that has duplicate keys that needs to
>be updated in a subfile program. You select the record you want to update
>and it is displayed on the screen. Because of the duplicate keys, you
>don't get the record you want. You can't use relative record number with
>a multiformat logial file. Anybody got any ideas? 


>Darlene Brengle
>Norsoft, Inc.
| 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

This thread ...

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

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