|
SAVSECDTA and SAVCFG can be run while the system is up. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Ingvaldson, Scott" <SIngvaldson@guid To eone.com> "Midrange Systems Technical Sent by: Discussion" midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s@xxxxxxxxxxxx cc Subject 03/27/2007 09:55 RE: Longer Savsys? AM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> 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. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. ----------------------------------------- DISCLAIMER: This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.