• Subject: Re: PGM assist?
  • From: rbbaird@xxxxxxxxxxx (Rick Baird)
  • Date: Fri, 10 Oct 1997 07:18:07 -0500
  • Organization: Premium Systems, Inc.

Tim Truax wrote:
> In order to get this program to compile I had to CRTDUPOBJ DUPDATA(*NO)
> the USSRCHM file into my library as UXSRCHM, then place an OVRDBF for
> UXSRCHM to point to actual USSRCHM file.  Is creating an empty file
> object considered proper to getting the program to compile?

you shouldn't have had to do do both the CRTDUP and the override to
compile the pgm.  One or the other should have done the trick.

It is not uncommon to have a "temporary files" library to store the odd
work files etc. (qtemp objects and such) for developers.  to avoid
conflict, the library wouldn't be in the libl for users or for
developers when testing, just for compiling.   If you have to do an
override every time you compile a program, it gets to be a pain, but if
the real file gets changed, you have to remember to replace the copy.

one alternative would be to create a logical over the file, same key
(with no members, so there would be no maintenance overhead) in your
temporary library so that if the physical gets changed, you will know to
change the logical.

Or you could change your program to do it with one "UF" file, READ it in
a loop with the operational extender "N" and when you get a record you
want to update, just chain to the same record/file without the "N",
update the record and then continue reading (assuming you are reading by


| 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 MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| 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].