×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Duane,

The V5R3 info center has some of the information you are asking for
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/index.htm

Look under: Programming, APIs, MI programming, Machine interface
instructions.

ILE built-ins are a subset of MI instructions.  Of the MI instructions
listed, the ones that are available as built-ins are documented as having a
"built-in number" along with the interface for "bound program access".

Looking up MEMCPY it describes the "bound program access" as

Built-in number for MEMCPY is 15.
MEMCPY (
        target_string   : address of aggregate(*)
        source_string   : address of aggregate(*)
        copy_length     : unsigned binary(4) value which specifies the
                          number of bytes to copy
) :   space pointer(16) to the target string


The interface happens to be the same as the C library version of memcpy.  If
you don't have a RPG prototype, this will work.

d memcpy          pr              *   extproc('__memcpy')
d target                          *   value
d source                          *   value
d length                        10u 0 value


The missing piece of information is determing the actual builtin name to use
(ie. "__memcpy").



Keith






> Bob,
>
> Earlier this week, or last week, you mentioned using the builtin for
memcpy
> (__memcpy) rather than the C library function. I could find no
description,
> in the C/C++ Run-time Functions manual, of which functions are builtin,
and
> looking through the info-center search did'nt help much either. Is there a
> list of builtins somewhere or is there a rule of thumb in defining them?
>
>
> Thanks
>
> Duane Christen


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