Save Library - time varies significantly

[Guest.Visitor]

I am researching something very strange. One of our data libraries takes extra time to save on Sunday nights. I am on 4.4 and use a 3590-B11. We save all libraries fully each and every night. Each night one of our data libraries takes approximately 15 minutes to save; however, Sunday night it takes one full hour. Has anyone else noticed this before? We aren't sure if this just started recently or not. The only difference between the days is that our batch processing occurs on Sunday. Is it possible for the system to have to reorganize something during a backup that would cause this big of a time lag? I checked SST for magnetic media errors and found none. I am about to call IBM. Thanks, Scott

[cwscholbe@dstsystems.com]

<pre> Is the data library also being used in your batch processing? If so, are you using *synclib in your SAVLIB parms? Is the backup on Sunday competing for resources only on Sunday? ie. are "other" jobs running during the weekday backups? Run the Sunday backup at a higher priority? In a different subsystem? What else is different about the "daily" backup and the one on Sunday? </pre>