× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Chances are that running 7 saves concurrently is hammering your disks.
Analyzing performance data would confirm it but that's my guess.

I have 2 suggestions:
1. Add DTACPR(*MEDIUM) to your save commands. This enables a level of
compression (similar to a ZIP file) that takes little CPU overhead but can
reduce disk writes during save operations (it works especially well on
databases). As a side benefit, the resulting save files should take less
space on both disk & tape and the save to tape will likely take less time.
2. Don't run 7 saves concurrently; do 2, no more than 3, at a time. You
might create a job queue that can run 2 concurrent jobs and submit the
saves to that queue. I would consider submitting them in reverse size
order; i.e. the save for the largest library first all the way down to the
smallest. That should result in a reasonable optimal use of your time.
Your goal should be to drive disk busy to 30-35% (over a 5+ minute
interval) but not beyond as much over 40% and the disks are so busy
servicing requests that the system gets stuck waiting on them, causing run
times to go longer than expected.
On Fri, Jun 14, 2013 at 2:47 PM, <Cynthia.Rogers@xxxxxxxxxxx> wrote:

We end QINTER and do a SAVLIB to *SAVF (in QBATCH) for our top seven high
availability libraries before restarting QINTER and allowing users back on
the system while the remaining libraries are backed up to tape.

We were running the SAVLIB commands consecutively, one after another, in
QBATCH. This job started running over into our dayend processing, so we
decided to submit these SAVLIB jobs separately to QBATCH so they could all
run at the same time.

We expected each of these submitted jobs to take about the same time as
they were taking when they were run one after another. That, however, is
not what happened. Our results were as follows:

Run Date 6/13/13 Run
Date 6/14/13
Running Consecutively Running
Concurrently
Library Start End Start End

PWRDTA 3:00 a.m. 3:36 a.m. 3:00 a.m. 4:23
a.m.
BLDDTA 3:36 a.m. 4:00 a.m. 3:00 a.m. 4:10
a.m.
PWRFOR 4:00 a.m. 4:02 a.m. 3:00 a.m. 3:09
a.m.
BLDFOR 4:02 a.m. 4:03 a.m. 3:00 a.m. 3:04
a.m.
IPWCSPRDF 4:03 a.m. 4:03 a.m. 3:00 a.m.
3:00 a.m.
IPWBLPRDF 4:03 a.m. 4:03 a.m. 3:00 a.m.
3:00 a.m.
IPWBSPRDF 4:03 a.m. 4:24 a.m. 3:00 a.m.
4:02 a.m.

Our SAVLIB commands are: SAVLIB LIB(library name) DEV(*SAVF)
SAVF(HALIB/library name) PVTAUT(*YES)

What am I missing? Is there anything I can do to speed this process up?

Thanks.

Cindy Rogers
Blue Line Foodservice Distribution
248/478-4213
--
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.