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



"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 03/16/2018
05:34:37 PM:
On 2018-03-16 1:43 PM, dlclark@xxxxxxxxxxxxxxxx wrote:
They are analogous in that they are both used to call
procedures.
It just so happens that CALLP can also call external programs through
a
prototype (CALLP doesn't always require a prototype so perhaps it is
mis-titled, now). Anyway, I'm just asking that CALLPRC also have the
ability to call external programs, but via a new parameter on the
command -- rather than having to make a much more extensive
modification to support full prototypes.

If the purpose of modifying CALLPRC is so you can use *OMIT for program
calls, it seems like it would be more straightforward to ask to use
*OMIT with the CALL command. I think it would be nicer to code
CALL PGM ('x' *OMIT 'y')
than
CALLPRC pgm ('x' *OMIT 'y') EXTPGM(*YES)


I would be in favor of either approach. I have added that as a
comment to the RFE. Thanks.

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=117746


Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.