×
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.
We are obliged to code all our exported subprocedures with 2 data structures as parameters. One for input, the other for output. The "parameters" are actually the DS subfields. This idea was a work around to avoid changing modules when one needed to add a parameter. Therefore, no keyword can be coded on one parameter only. The keyword would go on the DS and thus apply to all the "parameters".
Today, we find ourselves having to add the keyword EXTPROC(*CL) to the prototype. Would it be reasonable to assume that we would never have to add a keyword to a parameter, at a later release?
Thanks
As an Amazon Associate we earn from qualifying purchases.
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
