HP3000-L Archives

November 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Thu, 13 Nov 1997 14:05:03 PST8
Content-Type:
text/plain
Parts/Attachments:
text/plain (63 lines)
John,

Some time ago Eero Lauria (sp?), working for CSY (I think), submitted a
couple of command files that can be used to show connections on the HP3K and
also to abort them if need be, 'SHOWCONN' and 'ABORTCON'.  I think these
command files have been 'bundled' in the FOS and should be available on your
system.  Executing the 'showconn' command on a 'VT' session I get the
following:


SHOWCONN #!HPJOBTYPE!HPJOBNUM

JOBNUM  INTRO DATE AND TIME    LDEV   USERNAME
 REMOTE ADDRESS  RPORT  LPORT  FLAGS   PIN(PROGRAM)
#S5845  THU NOV 13 1997 13:53   155   MANAGER.SYS,PUB
       127.0.0.1 35446  vt     utcind  344(VTSERVER.NET.SYS)

Total processes checked:    4
Processes with sockets :    1
Total sockets open     :    1

Perhaps the information that you need is there...

Regards

Paul H. Christidis


______________________________ Reply Separator _________________________________
Subject: Telnet/iX: Need to find my sessions IP addr programmatically
Author:  John Korb <[log in to unmask]> at CCGATE
Date:    11/13/97 11:22


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.

ATOM RSS1 RSS2