× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



With regard to *START/*END the restriction to use the file name is silly. We don't have that restriction when using a key or RRN, so why do we have it with *START/*END?

Or, if we absolutely must use a file name, then WHY OH WHY can't it give us a clear error message that says "hey dummy, you need to use a file name with *START/*END" instead of the really confusing and unclear RNF5319?



On 2/28/2011 5:00 PM, Barbara Morris wrote:
I don't think it would be good to simply say that a file name is
synonymous with its record format name if there is only one format. At
least, it doesn't make sense to me to allow say using a format name on
an OPEN opcode.

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-2024 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.