×
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.
David FOXWELL wrote:
I have asked around, and I'm informed that the callers are SUPPOSED
to issue a CLEAR InDS, then fill the subfields before calling the
procedure. The first line of the called procedure issues a CLEAR
OutDS.
That would solve the decimal data error. But you still can't make a
parameter optional using this technique. If a new parameter is added,
and everything recompiled, and everything issues the CLEAR properly
(which is a lot of IFs) then you'll get zeroes passed for any numeric
fields added, or blanks for any character fields added.
The subprocedure cannot distinguish between the caller passing a zero,
or the caller not providing the variable.
For example, I work in a sausage factory. We might add 'temperature' as
a parameter to a subprocedure (since monitoring the temperature of our
sausage is very important for quality assurance.) How could we know if
the caller simply didn't pass the parameter, or if the caller meant to
say the temperature was 0 degrees?
Anyway... no need to reply to this message. I don't think my arguments
against your methods will matter to your manager, and his arguments
certainly aren't going to make me change...
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
