Q: Question:
The user wants to have an audit trail recording the user and
his terminal ID identifying the logged-in user's physical
location. Additionally, they want to direct print jobs to
remote printers based on the user's physical location, again
determined from his terminal ID.
The environment is an application running under CICS/6000
with LAN connected PC workstations running Windows, and Rumba
Office, Novix and Flashpoint for a GUI front-end. The PC is
only running Novell Netware and IPX to minimize memory loss
due to multiple protocol stacks.
Will the solution proposed in item CSQGS work in this
environment? Can this solution be implemented within the
CICS application? Would EPI be a simpler alternative?
---------- ---------- ---------- --------- ---------- ----------
R: Response:
When a user logs in to AIX or spawns a new window, the user
is assigned a terminal name by AIX. These terminal names
are known in UNIX as the "tty name" (tty is a legacy name
meaning "Terminal Tele tYpe").
You may determine your own "tty name" by executing a command
called "tty". This will return a string such as
"/dev/pts/13". The complete string is actually an AIX file
name pointing to a special file which when written to causes
output to be displayed on the terminal. When read,
keystrokes may be retrieved from the terminal.
There are two types of "tty" in AIX, real ttys and virtual
ttys.
A real tty, is an ASCII terminal which is electrically
attached to the RISC System/6000. These have "tty names"
which begin /dev/ttyx where "x" is a numeric. Each time a
user logs in on one of these terminals, the tty name will be
the same.
A virtual tty, is a tty assigned by the operating system
dynamically. AIXterm windows, telnet sessions and rlogin
sessions all result in the creation of a virtual tty. The
virtual tty has an almost random name assigned to it. If a
user runs telnet to login to a remote machine, the tty name
assigned may be different the next time the user runs the
same telnet command.
From AIX, it is thus virtually impossible to determine the
physical location of a user when they login. If the user is
not sitting at a real, directly attached ASCII terminal, the
tty name returned will have been generated by AIX.
The solution outlined in CSQGS allows the identification of
specific "telnet clients" which may have originated from a
PC workstation. The CICS/6000 telnet server does not use
ttys, the cicsterm ASCII terminal 3270 emulator does.
If you are planning on using tn3270 from PC workstations,
only the CICS/6000 telnet server (cicsteld) is appropriate.
Cicsterm is only usable for attached ASCII terminals.
The model of operation I am assuming, is as follows:
(1) (2) (3)
+----+ TCP/IP +----------+ DCE +-----------+
| PC | <------------------> | cicsteld | <-----> | CICS/6000 |
+----+ tn3270 +----------+ RPC +-----------+
Notes:
The machines running cicsteld (2) and the CICS/6000 region
(3) may be the same machine or may be separate, TCP/IP
connected machines.
It would be possible to map the TCP/IP address of the remote
PC (1) to a unique TERMID.
---------- ---------- ---------- --------- ---------- ----------
*====================================================*
| This entry has been edited for Library/INFO status.|
*====================================================*
NK ( upgrader: D73FA09
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q675093 FDVXC
Additional search words:
CICS CICS6000 DASYS DEC94 FDVXC LOCATING NK OZNEW TERMINAL TERMINALS
6000
WWQA: ITEM: RTA000051546 ITEM: RTA000051546
Dated: 12/1996 Category: KIX6000
This HTML file was generated 99/06/24~12:43:19
Comments or suggestions?
Contact us