RE: Securing interactive work during backups (was: QINACTITV does notappear to be working)

My last company, all user profiles had an initial program they called
in one of our libraries, something like STRCONEX.  When I wanted to
keep people out of the system I would allocate the program exclusively.

Very effective, people would try to log in and get an error screen and
be dumped back to the log in screen.

Of course, there was a hack around it if I then needed to sign in
somewhere.  I would simply specify the Program/Procedure on the login
screen as *NONE, which would bypass the initial program and let me in.

It wasn't' really a security thing but just a way to keep people out
while I was doing things where I didn't want to have to bring the system
to a restricted state, but wanted to make sure users didn't open files
I was using (used it primarily for the bi-monthly data history archival
program that was run during a lunch hour).


Regards,

Jim Langston
Programmer/Analyst
Cels Enterprises, Inc.