Files > SIGN-ON LOG

name
SIGN-ON LOG
number
3.081
location
^XUSEC(0,
description
This file records sign-on/sign-off times by user, device, job, UCI, and CPU. It is cross-referenced by user, device, and sign-off time.
applicationGroups
XU
Fields
#NameLocationTypeDetailsIndexDescription
.001date/time11This is the date/time that the user signed on. To allow more than one sign-on per second the time may have values that show hundredth of a second.
.01user(+)0;1POINTER200This is the user that signed on.
1device $i0;2FREE TEXTThis is the device $I that the user signed on to.
2job0;3NUMERICThis is the job number of the user's job.
3signoff time0;4DATE-TIMEThis is the time that the user signed-off through H^XUS.
4cpu0;5FREE TEXTThis is the name of the CPU the user signed on to.
5device0;7POINTER3.5This is a pointer to the Device file showing which device the user signed-on to. With network devices this is not a very useful field anymore. The 'ALDEV' X-ref is used to tell which user last sign-on to this device and the X-ref is not killed. At the most there would be one entry for each entry in the device file.
6uci0;8FREE TEXTThis field records the UCI account area where the user had signed on.
7task?0;6SET OF CODES1:TASK
This field is set to 1 for entries that are created by TaskMan. A field in the Kernel Site Parameters file can be used to make TaskMan "log sign-ons" for tasks. When that feature is active, TaskMan makes an entry in this file every time it runs a task.
9$zio (optional)0;9FREE TEXTOn a system with terminal servers this may be the port and server that the user is signed-on to. It can provide information not contained in $I.
10node name0;10FREE TEXTThe VAX/VMS cluster node name or system name on other systems. Comes from the GETENV^%ZOSV api.
11ipv4 address0;11FREE TEXTThis field holds the IPv4 address of the calling system. Note that under DHCP IP address are dynamically allocated so more that one client could have used the same IP address over some time period.
12workstation name0;12FREE TEXTThis field holds the workstation name if it has been provide by the underlaying OS or as part of a RPCBroker signon.
13auto signon handle0;13FREE TEXTThis field is used internally by the Kernel Auto Sign-on code to store the handle returned by the ClientAgent on the users system.
14remote station id0;14FREE TEXTThis field holds the station id (station #) of a remote site that did the user authentication. Having this field filled in implies that the user did not sign-on to the local system but was authenticated at some remote site that has requested data or services from this system. The Enterprise Single Sign-on, and the CPRS remote patient data projects use this field.
15remote user ien0;15NUMERICThis field holds the user IEN of a remote user that was authenticated at a remote site (field #14). Having this field filled in implies that the user did not sign-on to the local system but was authenticated at some remote site that has requested data or services from this system. The Enterprise Single Sign-on, and the CPRS remote patient data projects use this field.
16force close0;16BOOLEAN0:No
1:Yes
This field is a flag to indicate that the sign-on record was closed by some action other than a normal sign-off. IRM used the 'Release User' option. The nightly cleanup job closed the record because it was open to long.
17division0;17POINTER4This field holds the division that the user signed into. It is used to set the division if the user sign-on is thru AUTO SIGN-ON.
18remote app0;18POINTER8994.5If the user came into the system by a remote application like CAPRI or VistAWeb then this will point to the entry in the remote application file they used.
60cpu0;5FREE TEXTThis is the name of the CPU the user signed on to.
97elapsed time (seconds)COMPUTEDThis field calculates the number of seconds between sign-on time and sign-off time.
98locationCOMPUTEDThis is the location of the device which was used to sign on.
99elapsed time (minutes)COMPUTEDThis is the amount of time the user has been signed on.
100ipv6 address1;1FREE TEXTThis field holds the IPv6 address of the calling system. Note that under DHCP IP addresses are dynamically allocated so more than one client could have used the same IP address over some time period. Note also that under IPv6, each client could have more than one IP address. IPv4 addresses will be stored as IPv4-mapped IPv6 addresses, and all addresses will be stored in expanded IPv6 format.

Not Referenced