SAVSYS objects do NOT have their object updated with date of last save.
SAVSYS objects do not have any user authorities.
The rest of the save, after the SAVSYS, both of the above do apply.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Musselman, Paul
Sent: Tuesday, July 03, 2018 3:01 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS SAVSYS performance differences
Memory could affect the timing as well. Saves are 'disk' and memory intensive! Each object that is saved gets updated with 'date of last save.'
As others have mentioned, authority not at the object or Authorization List level must be saved separately.
Paul E Musselman
PaulMmn@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Tuesday, July 03, 2018 10:49 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: BRMS SAVSYS performance differences
V7R3 - latest CUM and groups.
P7 8205-E6C
Product LPAR BRMS SAVSYS - 4 minutes
CPU 1+ cores, 155 gb mem
100% SSD
Ultrium 7 - 4 drives
R&D LPAR BRMS SAVSYS - 23 minutes
CPU 1+ cores, 80 gb mem
10k spinny ASP01, SSD drives from other host ASP02.
Ultrium 7 - 4 drives
What would cause such a large difference from one LPAR to another?
On the R&D LPAR, when watching the SAVSYS via the TS3200 GUI monitor, the tape drives were basically idle for the majority of the 23 minutes.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
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.