RE: [Bulk] QDCRDEVD API Not Working as Advertised (or is it just me?)

Jerry,

I wrote up a quick comparison program between the QUSRJOBI and QDCRDEVD
APIs. Here is what I did.

1. Build a screen like the one below.

IP Addresses for a Display Device




Device name: __________ Device user: __________ Device job number:
______


Job IP address . . . .:



Network protocol IP address:



Server network protocol IP address:



2. Write a program to use the APIs. The program for this screen uses
Retrieve Job Information (QUSRJOBI) API format JOBI0600 to retrieve Job
IP address and the Retrieve Device Description (QDCRDEVD) API format
DEVD0600 to retrieve Network Protocol IP address and Server network
protocol IP address.

The interesting part is Job IP address and Network protocol IP address
were the same while the Server network protocol IP address held the
system's IP address.

Network protocol IP address came from position 878 - 892 (Internet
Protocol (IP) internet address in dotted decimal form).

Server network protocol IP address came from position 958 - 972 (Server
Internet Protocol (IP) internet address in dotted decimal form).

If the IP address from the job or the NWP IP address are not what you
expect you can try using the Telnet exit point (QIBM_QTG_DEVINIT). You
can find the client IP address in the connection description
information.

If you happen to have an exit point package that allows supplemental
exit programs you can use the feature to interrogate the Telnet exit
point without having to end and restart Telnet.



Gary Monnier

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Thursday, March 24, 2011 4:53 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: [Bulk] QDCRDEVD API Not Working as Advertised (or is it
just me?)

The stores only have a PC, which connects to the System i sitting next
to me
using Client Access. I'm not really concerned about the IP address of a
session inside HQ's four walls. I just wanted to be able to identify
the
store calling in. Seems to work at the store level; none of them have
routers (or so I've been told - famous last words).

Jerry C. Adams
IBM i Programmer/Analyst
More people are kicked to death by donkeys than die in aircraft
accidents. -
Encyclopedia of Useless Information (Personally I don't find this
useless at
all; just another reason to avoid jackasses.)
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, March 22, 2011 3:11 PM
To: Midrange Systems Technical Discussion
Subject: RE: [Bulk] QDCRDEVD API Not Working as Advertised (or is it
just
me?)

Jerry,

Unless your stores have their own IBM i then I wouldn't think this
NATting
would make sense. The API retrieves the IP address from the device
description, which should be stored on the i.


Rob Berendt