Re: Permissions of IFS file created with QZRUCLSP

Dennis <iseries-HF96MFG82JhWk0Htik3J/[email protected]> Fri, 18 Mar 2011 13:36:06 -0400
Newsgroups gmane.comp.lang.as400.mi
Message-ID <[email protected]>
Yipes!  That is, of course, argopt.

"Dennis" <iseries-HF96MFG82JhWk0Htik3J/[email protected]> wrote:

>Oh, I see.  So I infer that it would be (would have been?) possible to
>design QZRUCLSP to properly handle optionally-passed parameters by
>careful placement of those parms presented to the procedure.  But it
>would likely not be possible to influence a program without such design
>in such a way that the stars line up for that call.
>
>Finally the documentation line makes sense: "The API does not support
>calling procedures that have been defined using #pragma artopt"
>
>So no defect at all.  Thanks everyone.  This is what I had missed.
>
>"Barbara Morris" <[email protected]> wrote:
>
>>On 3/18/2011 9:38 AM, Dennis wrote:
>>> Ah, that sheds some light!  Since we have no (apparent) means of
>>> telling QZRUCLSP that certain parameters are optional but passed, it
>>> seems unlikely that it would be capable of guessing the correct
>means
>>> of passing same.
>>>
>>> Probably a moot point, but is the "differently" part of your message
>>> a trade/business/compiler secret?
>>
>>It's more that I don't know all the details since it's mostly 
>>transparent to the compilers.  The compilers just tell the
>optimizating
>>
>>translator that the called function has optional parameters.
>>
>>I do know that for a "..." C function, the function would use the 
>>va_list mechanism to access optional parameters.  This requires that
>>the 
>>optional parameters be contiguous in storage, so parameter 3 follows 
>>parameter 2 in storage, at a fixed offset away.  When there are no 
>>optional parameters, the system can pass the parameters in whatever
>way
>>
>>makes the most sense.  So the location of parameter 3 can't be
>>predicted 
>>from the location of parameter 2.
>>_______________________________________________
>>This is the MI Programming on the AS400 / iSeries (MI400) mailing list
>>To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
>>To subscribe, unsubscribe, or change list options,
>>visit: http://lists.midrange.com/mailman/listinfo/mi400
>>or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
>>Before posting, please take a moment to review the archives
>>at http://archive.midrange.com/mi400.
>
>--  
>Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my
>brevity.
>_______________________________________________
>This is the MI Programming on the AS400 / iSeries (MI400) mailing list
>To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/mi400
>or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/mi400.

--  
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.
_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.