|
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.