×
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.
On 08 May 2013 11:44, Sergey Kashyrin wrote:
Thanks, I've also figured out that my test is incorrect - just
messed playing with 3-5 parms on many platforms, so I'm getting MCH
on COBOL call COBOL also if I use 5 parms.
For now I see the only way to avoid this issue (which does not exist
on the platforms other than AS400) is to do the call to
QCLRPGMI(&info, ...
and figure out the expected number of parameters
(info.Max_Parameters) and then code a huge switch with calls :-)))
I am obviously unaware of the details... But IMO a more obvious
resolution to avoid any logic in the CALLER, would be to code the CALLEE
to accept the additional two parameters regardless they are unused.
Of course I generally prefer having the caller use a distinct
invocation for each different parameter-style, so which type of
invocation has failed is very conspicuous; i.e. if there is just one
generic CALL PGMX (&Addr_of_Parm_List), then every variation of the CALL
that fails on the same HLL statement, and therefore only by debug or
good logging will I learn which variation of the invocation had been
established.
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.