At a former job I created a logon udc that executed a command file.  This
command file would look for unigue file names and if found would lock out users
by account (except those who logged on as mgr.)
I could even lock down the entire box with the exception of those loggin on as
manager.sys or mgr.telesup.  You could even tighten it up by including the
jobname variable.

If you would like a copy let me know (I have it at home)



"Girard, Frank" wrote:

> We are looking for a way to restrict user access by account, rather than
> globally using limit 1,1.  Telling the users about hipri is not an options
> as this defeats the purpose, as well as being a security issue.  I am
> looking to restrict all users except 1, the manager of the account.
>
> We are fast coming up on a situation where we need to apply updates to an
> account, but in the update instructions it has us set the limits to 1,1.
> This cause all the users to get kicked out when they try to log onto an
> account that is not involved in an update.  Here is the information:
>
> We are running MACS from Smith Gardner, this is a MAil order and Catalog
> Supply software package.  This software is set up in 3 major accounts, 1
> account for each company that uses it.  The companies / accounts are WNG, BT
> and MP4.  The problem is that while I am applying an update to WNG, with the
> limits set to 1,1, the order processors who are logging into BT and MP4
> can't log in because the limits are set to 1.1 even though the update does
> not involve them.  Here's another example, WNG is doing a month and a year
> close this Saturday.  We are testing in BT and MP4.  The limits are set to
> 1.1 we cannot do any testing in these accounts, even though nothing in
> theses accounts affects WNG.
>
> Thanks in advance for your input and help.
>
> Frank Girard
> [log in to unmask]
> 781-828-9300 X2738

--
Larry Barnes
Director of MIS
Mitek Corp.
4545 E. Baseline Rd.
Phoenix, AZ 85040
[log in to unmask]