|
On Aug 10, 2020, at 8:26 AM, Brad Stone <bvstone@xxxxxxxxx> wrote:
Hey, John.
No Varchars and no prototypes. It's a straight call. But I'm thinking of
making an ILE interface for the program so that it would be available from
any ILE language.
I'll dig into it. Shouldn't be terrible. I had one person suggest
creating a PF and using that as an external DS. But there are arrays in
the data structure/parameter list so that may not work either. But I'm
sure there are "tricks" lol.
On Sun, Aug 9, 2020 at 2:28 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
No docs that I know of Brad but I have done it for a few people in the--
past.
A bigger issue is often that with RPG we can rely on the prototypes to
help and also have support for varchar - neither of which exist in COBOL.
If you want to send me a couple of samples (including the protos so I know
how the calls should be) I would be more than happy to convert them for you
to give you an idea.
On Aug 9, 2020, at 2:05 PM, Brad Stone <bvstone@xxxxxxxxx> wrote:but
This may seem like an odd question, but are there any materials that show
how you can convert a data structure and field definitions from RPG to
COBOL for the IBM i?
I only ask because I have someone who wants to call one of my programs
the /copy book for the parameters and fields is RPG and they are COBOLonly
shop. I would think once that is converted that calling an RPG programuse
from COBOL (not a subprocedure, just a straight CALL) should be simple.
I haven't touched COBOL since the 90s. :)
Thanks!
Bradley V. Stone
www.bvstools.com
GreenTools for # Slack # <https://www.bvstools.com/g4slk.html>: Easy to
interfaces for sending and receiving messages on Slack!list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated questions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
link: https://amazon.midrange.com
Help support midrange.com by shopping at amazon.com with our affiliate
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.