Hi Eric,

This one has a simple answer. CPYBRAP and CPYBLAP are both OMI-only
instructions and they can't be used from an ILE program. The mystifying
thing is the fact that the QSYSINC/MIH.CPYBLAP header file exists...


Aaron Albertson

c400-l-bounces+albertaa=us.ibm.com@xxxxxxxxxxxx wrote on 03/30/2011
03:58:16 PM:

From: Erik Olsson <erik.eo.olsson@xxxxxxxxx>
To: "C programming iSeries / AS400" <c400-l@xxxxxxxxxxxx>
Date: 03/30/2011 03:59 PM
Subject: [C400-L] Fwd: Prototype CPYBRAP instruction
Sent by: c400-l-bounces+albertaa=us.ibm.com@xxxxxxxxxxxx

Sorry, I'm still interested in the CPYBRAP prototype but to solve my
immediate business need I'm going with the good old trusted cpynv (if
anyone was going to suggest that).


---------- Forwarded message ----------
From: Erik Olsson <erik.eo.olsson@xxxxxxxxx>
Date: 2011/3/30
Subject: Prototype CPYBRAP instruction
To: C programming iSeries / AS400 <c400-l@xxxxxxxxxxxx>

Has anyone managed to prototype the CPYBRAP MI instruction? I have
tried a number of different approaches, even using the similar CPYBLAP
file from QSYSINC but so far no success.
(For the record, I have to populate a zoned decimal field that's 13, 0
so I can't use QXXITOZ as it only takes ints, ie not long long int and
I was thinking that CPYBRAP would be neater than a snprintf).

Best wishes,
This is the C programming iSeries / AS400 (C400-L) mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/c400-l.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].