RE: Disable Login

Chris -

I haven't seen this solution posted so I'll add it:

Create a data area as a flag to availability.  Then set the initial menu to
*SIGNOFF and the initial program in the user profile to check the data area
first when users sign on.  

<INLPGM>
PGM                                                   
DCL VAR(&ACT) TYPE(*CHAR) LEN(3)                      
RTVDTAARA DTAARA(QUSRSYS/PSIAPP) RTNVAR(&ACT)         
IF COND(&ACT *EQ 'yes') THEN(GO MENU(PSICMAIN)) 
ENDPGM
</INLPGM>

This allows you to disable a group of users with a command [CHGDTAARA
DTAARA(QUSRSYS/PSIAPP) VALUE('no')] without affecting other users who need
to continue working.  If the data area is 'yes' thet pass through to their
menu, if the data area is 'no' they get signed off.

Regards,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group 

-----Original Message-----
Date: Tue, 13 May 2003 11:10:28 -0700
From: "Chris Devous" <cdevous@xxxxxxxxxxx>
Subject: Re: Disable Login

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