23Dec2011
A not existing home terminal of a process no longer causes WHOIS to enter DEBUG.

19Dec2011
A specified process (by name, or PIN) now gets a possibly attached LIB displayed.

05Jun2008
Code lifting.

21Apr2008
In case a library is attached to a program file, it is displayed.

20Apr2008
Code streamlined, and performance dramatically enhanced.

12Jan2007
Support of code 800 type object.

06Sep2006
Full support of Gemini Telnet features, including:
- Client port number
- Tandem IP address
- Tandem port number
Requires STN54 or better.

30Aug2006
GHSLIB enhanced with the ability to talk to the Gemini Telnet process.
In case there is a Gemini Telnet, we can NOT retrieve the clients IP port, and the Tandem IP address and port.

05Jul2006
The Process creation time as well as the process age is now displayed.

13May2005
In case WhoIs is started from a Win6530 type emulator, it now uses a new interface to directly communicate with the emulator.

06Dec2004
Support for Subtype 30 Processes added; enhanced error handling.


Starting with GUARDIAN D30, Alias users are introduced to the system, and co-exist beside GUARDIAN users. An Alias user has its own name (which is case sensitive), an individual password, and DEFAULT values (GUARDIAN security, DEFAULT volume, SAFEGUARD default ACL).

This is the good news.

The bad news is, that an Alias is mapped to a GUARDIAN-ID when he successfully has passed the authentication procedure. This means, that the ID of a running process does NOT show the real user behind it, which might be an Alias user. It is even worde, when several different Alias users are mapped into one GUARDIAN-ID.

WhoIs is the solution: It displays the real ID behind a GUARDIAN ID when there is one.
WhoIs displays the following user information:

    * Alias Name (if the user has logged on with an Alias name, e.g. Weber_Carl)
    * GUARDIAN name (group.name, e.g. GHS.CARL)
    * GUARDIAN ID (groupID,userID, e.g. 100,5)
    * home terminal
    * window address of home terminal (IP or X.25 DTE address)