TFNRegistry Reporting: Logonid History Table (RHDB_LOGONID_HISTORY) – Somos

The Logonid History table stores information for all current and past interfaces; therefore, interfaces that are no longer available, such as 3270, may still appear in this table as it was still available at the time a user last accessed it.

This table is available via the SMSADM universe in Reporting. The data is viewable only by Help Desk and Administrators via Reporting (see Table 128 RHDB_LOGONID_HISTORY).

Table 128 RHDB_LOGONID_HISTORY

RHDB_LOGONID_HISTORY
Field	Characters	Description
ActivityDateTime	Timestamp	Date/time of the logonid_history record activity.
user_logon	char (8)	The Login ID of the activity.
Logon_system	char (4)	The SMS/800 TFN Registry that the Login ID is created for. Valid values: S1 - 3270/WBA interfaces Login ID MGI - MGI interface Login ID BOJ – WRS Business Objects Interface Login ID RHO -RHDB SQL*Net interface Login ID RHU - RHDB SFTP interface Login ID
user_control_resporg	char (5)	Indicates the controlling Resp Org of the Login ID.
Status	char (1)	Indicates the status of the Login ID. Valid values: L - Locked U - Unlocked
Exempt	char (1)	Indicates the "exempt" status of the Login ID. Valid values: Y - It’s exempt from being automatically locked by the SMS/800 TFN Registry due to in activity defined on the UAA page N - It is not exempt
interface_ind	char (4)	Indicates the interface the action is performed. Valid values: BACH - locking/unlocking S1/MGI IDs due to inactivity or via manual tool WBA - locking/unlocking S1/MGI IDs via (UAA/SUD/ GSA WBA) pages 3270 - locking/unlocking S1/MGI IDs via SUD/ GSA 3270 pages WRSA - locking/unlocking RHDB SFTP and SQL IDs due to inactivity WRSM - locking/unlocking RHDB SFTP and SQL IDs via manual tool or the UAA page BOJA - locking/unlocking WRS Business Objects IDs due to inactivity BOJM - locking/unlocking BO IDs via the UAA page Please Note: MGI does not allow a user to lock/unlock/exempt/unexempt any Login IDs. MGI IDs can be locked, etc. via WBA/3270/BACH.
processName	char (30)	Indicates the process name/page via which the action is performed. Examples: GSA, LOGON, UAA, MANUAL BATCH JOB, smrhd_acc_usrlock, smrh_acc_usrunlock, SUD.
Processed	char (10)	Indicates the process/Login ID that performed the action. Examples: SMSADM
extractDate	Date	The date when the record was sent to the RHDB database.

Please Note: This table includes references to all the older Somos interfaces and older page names to maintain the historical data.