×
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.
On 3/1/11 10:52 AM, M. Lazarus wrote:
At some point in the process of either compilation (in the case of a
MFLF) or runtime (in possibly some other cases), the RPG program
should be able to know where there is an ambiguity. Only in those
(rare?) cases should we be required to specify the format.
Are there any cases you can think of (for data files) that this would
be problematic?
If the decision could be made at run-time, then any hard enforcement
at compile-time might or might not be desirable. My mention of the
concept of RcdFmt=*ONLY meant to allude to the possibility that a
run-time operation might be able to recognize that the ODP is defined
for multi-format access, and thus issue an error for any request which
used a file-name versus a format-name to effect its request, for which a
format name was required. Under the assumption that the multiformat
scenario is rare, then always coding to the file name versus a format
name should rarely experience an error like the "record format name is
required" which CPD3104 does for OPNQRYF when defaulting to Record
Format = *ONLY; e.g the case presented by Joe "to allow file name for
all <RLA> opcodes".
Regards, Chuck
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.
midrange.com
