Processing Time - Consecutive versus Simultaneous Jobs

[Cynthia.Rogers@xxxxxxxxxxx]

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