×

Good News Everybody!

The new search engine is LIVE!

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




Of course the question comes to mind why are you coding QDBRTVFD in CL. You
just like pain?

But assuming you have a reason, why not just create a RPG module with a
procedure, pass the value, convert and return to CL. Bind the CL module to
the RPG to form a program.


On Mon, Dec 19, 2016 at 6:21 PM, Mark S Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Hi, Dave:

If you use ILE CL (CLLE) vs. OPM CL (CLP), then you can use many MI
instructions directly "in-line" as built-in functions. This includes the
MI instructions for testing and setting individual bits, etc.

Hope that helps,

Mark S. Waterbury

On 12/19/2016 2:22 PM, dlclark@xxxxxxxxxxxxxxxx wrote:

I was about to call the QDBRTVFD API from a CL program but
noticed
that the information I wanted was bit-encoded in byte 9 of the receiver
variable output. I know how to take the long (mathematical) approach to
determining bit settings (because I did it in COBOL back in the day), but
I was wondering if there was a more direct method available to CL
programs? Thanks.

Sincerely,

Dave Clark



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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.