From "VisC++", I take it that your program is running on a
PC. Is this true? If so, look at the Programmer's Toolkit
which comes with iSeries Acess. It provides functions to
send and receive data queue entries.
HTH.
Terry.
Available for contract programming.
Hi Terry,
i know this examples but they use CA express Classes and so you must install
CA to run your program. I want to use nativ AS/400 API's.
Willy
Alas, I do not have a good suggestion. The best I can think
of is to wrap QRCVDTAQ within an AS/400 program which sends
the results to the PC. Not necessarily a terribly big deal,
but still a nuisance.
Can somebody here give us a more direct suggestion?
Terry.
I thought you were writing this in Visual C++? Since Visual C++ isn't
able to create programs which run natively on the iSeries, they can't
call native iSeries APIs!
Personally, I think you're going about this the wrong way... if you
want to communicate between an iSeries and a PC, use sockets!
Unlike data queues, sockets are available for every operating system,
and are built into the networking layer. That means you won't have to
install some extra software like Client Access, ever.
That just my opinion, of course.
----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---
By definition, you are asking about doing client/server remote program
calls. As far as I know there is no reasonable tooling to do this.
Operations Navigator (aka iSeries Navigator) performs remote API calls
using both Visual C++ and Java.
In Op Nav for C++ there is a fair amount of code infratructure to
establish socket connections with the remote command server (one of the
Host Servers) to perform the calls. Unfortunately, none of this
infrastructure is published by IBM (e.g. as a publicly accessible C++
class library). On the Java side, all the remote program calls are
performed with the Toolbox for Java. In this case the Toolbox is doing
all the same infrastructure that the C++ code does with the benefit that
IBM provides the toolbox as a supported class library for Java developers.
One possibility is to define the needed APIs as DB stored procedures and
call them using ODBC. I say "possbility" because I have never done this,
and I suspect there may be a good many APIs that for one reason or
another would be difficult or impossible to implement as stored procedures.