Re: Bindable APIs Vs Non-Bindable APIs

Perhaps a trap, but at least one that is documented.  If you look at the
help text for PARM, and specifically the description of Character string
constants, it covers the case of "*OMIT" cannot be specified as a constant
value -- that a null pointer will be passed instead to the called
procedure.




                                                                           
             Simon Coulter                                                 
             <shc@xxxxxxxxxxxx                                             
             om.au>                                                     To 
             Sent by:                  Midrange Systems Technical          
             midrange-l-bounce         Discussion                          
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
                                                                           
             02/19/2004 02:11                                      Subject 
             AM                        Re: Bindable APIs Vs Non-Bindable   
                                       APIs                                
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
                                                                           
                                                                           





On Thursday, February 19, 2004, at 09:51  AM, Barbara Morris wrote:

> Thanks, that's good to know.  I prompted on the PARM part of the
> CALLPRC
> command, and didn't see *OMIT there.  Now I see that the help does
> mention *OMIT.

That made me curious. I would have expected *OMIT to be a special value
but I discovered the SPCVAL keyword is not allowed with parameter type
*X (unrestricted). So *OMIT must be handled by the CL compiler as a
special case because the CPP for CALLPROC is a dummy program like DO,
IF, ENDDO, and other program-only commands.

Then I thought what if I want to pass the character string '*OMIT' to
the called procedure? That might be an odd case but is reasonable. I
enclosed it in apostrophes. Nope. Don't work. It is still interpreted
as the *OMIT special value. With normal commands you can force the
character value to bypass special value processing by enclosing it in
apostrophes and including an extra space ('*OMIT ') but that doesn't
work on CALLPRC.

Hmm? Trap for young players ... probably not a big deal.

Regards,
Simon Coulter.
--------------------------------------------------------------------
    FlyByNight Software         AS/400 Technical Specialists

    http://www.flybynight.com.au/
    Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
    Fax:   +61 3 9419 0175                                   \ /
                                                              X
                  ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------


_______________________________________________
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.