|
We had a similar issue. We now use OMIT(*SECDTA) on the SAVSYS to reduce downtime and run a SAVSECDTA by itself weekly, during a timeframe when the system is active but not busy. Regards, Scott Ingvaldson System i Administrator GuideOne Mutual Insurance Company -----Original Message----- From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] Sent: Tuesday, March 27, 2007 7:45 AM To: Midrange Systems Technical Discussion Subject: Re: Longer Savsys? Our SAVSYS jumped from 4 minutes to 44 minutes solely on the basis of using "secondary groups". IBM dialed in and verified this by using PRTPVTAUT, etc. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com fbocch2595@xxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 03/24/2007 08:50 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Fax to Subject Longer Savsys? Hi, we run savsys weekly and it usually runs no more than 30 mins but today it ran 70 mins. What are the usual reasons why it's runtime gets extended? We've added a handful of ptf's since the last savsys, could that cause the longer runtime? Thanks, Frank p.s. There were no interruptions caused by tape or tape drive. ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.
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.