|
Nope,
the job is not submitted, it's a client-server sort of kind of stuff
thingy.
But I meanwhile found a solution using the QtocLstNetCnn and QtocRtvNetCnnDta
API's, as you suggested in one of your previous mails.
Thanks goes to the makers of www.think400.dk for providing me with an API
example program that I have adapted to my needs.
Best regards,
Peter Colpaert
Application Developer
Massive - Kontich, Belgium
-----
Yoda of Borg are we. Futile is resistance, assimilated will you be.
-----
Vernon Hamberg <vhamberg@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/01/2005 14:47
Please respond to Midrange Systems Technical Discussion
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc:
Subject: Re: Retrieving remote IP address
Just had a thought - unusual for this early in the day - the batch job is
not the one that is connected, so it has no IP address associated with it.
The job with the IP address would probably be the one that submitted the
batch job. This information is available to the job itself. So one needs
to
determine the submitting job (RTVJOBA or an API, I think), then run that
submitting job info through a list of IP connection jobs. Eh?
Vern
At 07:32 AM 1/4/2005, you wrote:
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.