Ken, I appreciate the extra detail.
I had seen Rob's follow-up "We were all wrong." but
I was not sure what he meant, so I thought I would
Somewhere (maybe in John Yeung's second e-mail or
Midrange archives) I got the following link which
mentions ILE CL procedutes with variable length
at any rate, I can't work on this for a while,
but do intend to attempt CLLE with "optional parameter(s)"
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Sims
Sent: Tuesday, January 21, 2014 2:26 PM
Subject: Re: optional parm in CLLE
Hi Gary -
On Tue, 21 Jan 2014 20:09:15 +0000, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:
I am looking at changing a local program used for FTP.
Are optional parameters possible in CLLE ?
The idea is existing programs calling this changed program will not
pass the new parameter and will not need changing.
Note that all of the responses about trying to use the parameter and monitoring for an invalid/null pointer are NOT correct for not passing a pointer at all (unless CLLE does something under the covers for checking the number of parameters passed versus the field being accessed).
If a pointer is not passed (valid or null), then there could be a valid pointer in the memory location where that pointer would be if it had been passed.
You need the equivalent of the RPGLE %PARMS BIF. I suspect that you will need to use one of the CEE APIs to do that, but I don't know. I have many RPGLE programs that can handle varying numbers of parameters, but I've never done that in CLLE.
Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l