|
Here is the reply I sent Patrick in response to his question about a slow SAVSYS: Thanx for all your help Rob and Al .... Patrick .... The SAVSYS process does several things. 1.) Saves all user profiles 2.) Saves License Internal Code 3.) Saves private authorities 4.) Saves configuration objects 5.) Saves objects from library QSYS Your process could be running longer if any of those items significantly changed in size after your upgrade. I ran this issue by several other people "in the know" too. Here are some things they suggest you check: 1.) See how many QHST file are in library QHST. Delete any you don't need. 2.) Make sure PTF SI02913 is on your system. This PTF fixes some known performance problems with SAVSYS. It is part of V5R1 Cume C3007510. 3.) Consider running SAVSYS as follows: SAVSYS DEV(TAPXX) OMIT(*CFG *SECDTA) This will omit the SAVCFG and SAVSECDTA processes of the SAVSYS. These two processes should be run with your daily backup and they don't require that your system be in a restrictive state either. I hope this helps you out. Let me know if any of these ideas made a difference. Good luck, Kenneth -----Original Message----- From: Graap, Ken [mailto:keg@xxxxxxxxxxxxx] Sent: Tuesday, May 27, 2003 9:13 AM To: 'Midrange' Subject: SAVSYS Someone is telling me that their SAVSYS is running 4 or 5 times longer since upgrading to V5R1. They aren't using any special BU products, just the native SAVSYS command. In your experience, what usually affects how long SAVSYS runs? Here is what I think.... 1.) Number of profiles 2.) Number of private authorities. 3.) Number of configuration objects on the system .... If there were no significant changes in these three items, what possibly could be happening.... Hmmmm, a mystery... Kenneth **************************************** Kenneth E. Graap IBM Certified Specialist AS/400e Professional System Administrator NW Natural (Gas Services) keg@xxxxxxxxxxxxx Phone: 503-226-4211 x5537 FAX: 603-849-0591 **************************************** _______________________________________________ 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-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.