Re: Disable Login

["Chris Devous" <cdevous@xxxxxxxxxxx>]

Man, have I gotten a lot of great responses from the list!  Thanks everybody 
for all 
the great suggestions!

What I was hoping to do was restrict access to BPCS data files so that we can 
run 
some of the reorgs (we do some of these nightly).  The specific issue is that 
we have 
placed a trigger over RCM to audit any activity that takes the open order 
amount to 
zero or negative.  I like to remove this trigger, run ORD992 which resets open 
order 
amounts, then replace the trigger.  

What is happening is that I have a user coming in at 4:30 to service the east 
cost.  
He logs right on, which locks RCM, and the rest is history.  I don't really 
have a 
specific issue with ODBC and my nightly batch, because this all happens right 
after 
an IPL, but I'd sure like to know what you have in mind.

I have the CL doing an ALCOBJ on RCM to make sure the trigger can be removed 
before the actually attempting to do it, but of course if I can't remove the 
trigger I skip 
the reset, and I do want to run the reset.

On Netware consoles you can actually type "DISABLE LOGIN" which leaves 
everything running but actually prevents users from logging in.  I was hoping 
the 400 
has something similar.  What I think I'll do is disable the appropriate user 
profiles 
during the nightly batch, which should take care of the ODBC issues as well.

Thanks,

--Chris

On 13 May 2003 at 10:54, rob@xxxxxxxxx wrote:

> Were you also hoping to stop file access from these users via file
> transfers, odbc requests, etc, or is the minimal work done by simply
> restricting 5250 acceptable?
> 
> Rob Berendt