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



Hi Steve,

When you say "probably
unnecessary" I was confused. Wouldn't you have to create a new current
signature so the new programs could use the new parameter, while leaving
existing programs to use *PRV?

I was obliquely referring to the fact that I could simply make all my signatures the same, like 'company_name' instead of something that makes sense. Then the signature stays the same at all times, there is no *PRV and all new procedures go at the bottom of the binder source.

Or can a *NOPASS parameter be added to a PI and existing programs not
using this parm will run fine as long as the procedure doesn't reference
the new parm?

Yes, existing programs that consume the procedure will run just fine. But there's no point adding a new parameter to a subprocedure that isn't used anywhere. You can add the new parameter safely as long as you don't refer to it unless it's been passed by the caller.
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.