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



Charles,

Under what circumstances would you do this? I can see some (rare, I'd think)
cases where you'd need both (where you a number of optional parameters and
you might want to pass one or more of the later parameters (e.g. an error
parameter like QUSEC)) but not the earlier ones, but if that's the case, I'd
think you'd be better off redoing the parameter order.

I can only think of two instances where I've needed to use both *OMIT and
*NOPASS for a parameter. Although this could just mean that my procedures
are simple compared to your :-)

Rory

On 11/1/06, Wilt, Charles <CWilt@xxxxxxxxxxxx> wrote:


I often code parameters as options(*NOPASS:*OMIT).

Charles Wilt


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.