Re: QINACTITV does not appear to be working

We have one 400 that just does the QINTER thingy.  It's offsite.  When the
backup blows up leaving QINTER down I use FTP commands to start QINTER
QUOTE RCMD STRSBS QINTER
Oh, there's always a way to hack.

Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.



                    Evan Harris
                    <spanner@ihug.co.nz>       To:     security400@midrange.com
                    Sent by:                   cc:
                    security400-admin@mi       Subject:     Re: [Security400] 
QINACTITV does not appear to be working
                    drange.com


                    08/30/2001 01:18 PM
                    Please respond to
                    security400






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.

_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400)
mailing list
To post a message email: Security400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/security400
or email: Security400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.