John,

Well, I can tell you that the standard call to NSINFO does not work. I got
this code from VTVERIFY thanks to
Duane Percox. I can also tell you that the data is available via
SOCKINFO.NET.SYS. You have to drill down to
the process and then do an 'A' command. This will dump much more than the
Destination address, but if anyone can figure a more direct route I would
also be very interested.

MOVE "$BACK"                     TO NI-ENV-ID.
MOVE 5                           TO NI-ENV-LEN.
MOVE ZERO                        TO NI-ENV-NUM.
MOVE 38                          TO NI-ITEM-IP.

CALL INTRINSIC "NSINFO" USING    NI-ENV-ID,
                                 NI-ENV-LEN,
                                 NI-ENV-NUM,
                                 NI-ERROR,
                                 NI-ITEM-IP,
                                 NI-IP-ADDRESS.

Mike Hornsby
[log in to unmask]
 (513) 922-0509 - Fax (513) 347-2834
Disclaimers: This communication is intended for the general use "AS IS",
with no written or implied warranty. It does not represent any corporate
views or disclose any private data or information. The sender has made every
effort to attribute authors of any included materials. Reference to any
commercial products, process, or service does not necessarily constitute or
imply its endorsement or recommendation. This communication and the
obligations of the parties hereunder shall be interpreted, construed, and
enforced in accordance with the laws of the State of Ohio, excluding
principals of conflict of laws.


-----Original Message-----
From: John Korb <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Thursday, November 13, 1997 9:30 AM
Subject: Telnet/iX: Need to find my sessions IP addr programmatically


>Here is one for the networking experts.
>
>The Navy has a requirement that they log information as to the source of
>each session (LDEV number on Classic systems, IP address for VT sessions)
>for audit purposes.
>
>A "showvar" (on 5.5) from an NSVT session shows a variety of information
>regarding the session, including the IP address, node name, and TCP port
>number.
>
>Telnet sessions (coming in through the inetd job) do not display IP
>address, node, or TCP port information -- they only display an LDEV number.
>
>Question:  Does anyone know how a COBOL program can find out that the
>session is a telnet session, and also find out the IP address, node name,
>and TCP port of the session?  We have been told that we must modify our
>applications to collect this information and log it instead of the LDEV
>number that was logged on the Classic systems.
>
>Thanks!
>
>John
>--------------------------------------------------------------
>John Korb                            email: [log in to unmask]
>Innovative Software Solutions, Inc.
>
>The thoughts, comments, and opinions expressed herein are mine
>and do not reflect those of my employer(s), or anyone else.
>
>