RE: QINACTITV does not appear to be working

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Ya know, I was just getting ready to ask that question.  End QINTER, but
still allow me access to sign on.

Evan, could you detail both the subsystem and jobqueue you use for
backup, as well as second subsystem with the "workstation entries" (?)
and "routing entry" (?).  This appears to be exactly what I need/want to
do in our situation.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com

> -----Original Message-----
> From: Evan Harris [SMTP:spanner@ihug.co.nz]
> Sent: Thursday, August 30, 2001 2:18 PM
> To:   security400@midrange.com
> Subject:      Re: [Security400] QINACTITV does not appear to be
> working
>
> We do the same here. I run the backup jobs in batch through a specific
> dedicated subsystem and jobqueue so there is no possibility of a job
> clash
> (well, OK a much reduced possibility :)
>
> To enable access to particular individuals during the backup I starts
> a
> second subsystem that has workstation entries included in it and only
> allow
> people with a particular routing entry to sign on.
>
> Hope this helps
>
> >Dan,
> >
> >We only have one system here and I notice that some devices get
> knocked of
> >(we use 90)
> >and yet others, which have had no activity for HOURS are still on.
> The
> >common thread
> >seems to be they are PC's connected via TCP/IP and not the dumb
> terminals (?).
> >
> >We DEFINITELY end QINTER for backups and the backup job runs in
> QBATCH so
> >no user
> >submitted jobs can run against it...
> >
> >Chuck
> >
> >"Bale, Dan" wrote:
> >
> > > System value QINACTITV is set to 60 minutes on all of our
> production
> > > systems.  However, the system seems to recognize this setting on
> only
> > > two of these five boxes.  One one system, it takes up to six hours
> for
> > > the system to finally boot me off.  Another system takes about
> three
> > > hours.
> > >
> > > Yesterday, our backup failed because one user's workstation had
> not been
> > > signed off, objects were locked, and the backup "failed".  This
> was
> > > quickly elevated to "resolve this now" by our auditing team.