Archives of the TeradataForum
Message Posted: Thu, 04 Mar 2004 @ 10:59:03 GMT
| Subj: || || Re: DBC login authorization |
| From: || || John Hall |
Managing the attempted logons to DBC is one approach, but given the security risk they represent, wouldn't it be better to manage the people
who are attempting the logons?
Assuming that the logon attempts are coming from the network (a different query would be necessary for MVS), the following SQL should give you
a list of the IP addresses for those people who unsuccessfully tried to logon to DBC:
sel datefld (named Log_Date)
, timefld (named Log_Time)
, substr(logonsource,15,15) (named IP_Addr)
where username = 'dbc'
and event = 'bad password'
and logonsource like '(tcp/ip%'
order by 1,2,3;
Once you have the list of IP addresses, you should be able to work with your network people to determine the actual culprit(s).