HP3000-L Archives

November 2003, Week 4

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:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Tue, 25 Nov 2003 10:27:33 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Re:
> Perhaps this would work for you:
>
> nslookup.hpdce !HPLOCIPADDR
>
> > How do I retrieve the Local node name programmatically?

Sorry, but this won't work (I was led down the same path :)

HPLOCIPADDR, strangely (?) documented as:
     A global variable used by the CI that shows the IP
     address of a remote client; initial value is null
     string.  Type= R S

(If you think of the remote user (at, say, a PC running Reflection),
accessing a client (the 3000), then the phrase "remote client" almost
makes sense.  However, "address of this HP 3000" would make more sense,
I think.)

Despite that, HPLOCIPADDR is an empty string for batch jobs,
and for non-network sessions (e.g., console, serial).  Thus, you
can't count on it in all cases.

However, it is useful if you only need it for sessions coming in
over telet or NS-VT.

Stan

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2