RE: Performance issue - CLRLIB vs RNMOBJ vs DLTLIB / Timeslice

Steve,

First a comment about timeslice...  It doesn't work the way it used to, so I
doubt it really helps much.  

Now a few questions:

Are there many access paths that are being rebuilt?  This is probably where
most of the copy time is spent.....  Perhaps you could save to tape (with
access paths) overnight, then restore to the test lib?  Otherwise, see if
you can reduce the number of access paths that need to be rebuilt.  

Do you really need the entire library copied?  There are tools that help
build testing libraries by only copying subsets of the production database.
Reducing the number of rows would save you much time...

What model iSeries are you running?  Tape drive?  

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Steve Johnson [mailto:sjohnson@xxxxxxxx]
Sent: Tuesday, January 20, 2004 4:07 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Performance issue - CLRLIB vs RNMOBJ vs DLTLIB / Timeslice


We currently submit a job to copy data libraries from our prod environment
to a test environment.  The libraries are very large, and we are currently
doing a CLRLIB of the to-library followed by a CPYLIB from the prod library
to populate the cleared test library with production data.  The job takes
longer than we would like for it to complete, about 2 hours.

With large libraries might another approach perform better?  We thought that
RNMOBJ/CRTLIB/CPYLIB might help the main process complete faster, allowing
the DLTLIB of the unneeded RNMOBJ library to be handled later, but we didn't
notice the job completing any faster.  I would think that a
DLTLIB/CRTLIB/CPYLIB combination might be even slower in completing.

Have you been there done that?   

One of the first steps in the CLP is a CHGJOB to set the timeslice to
6,000,000.  Someone once stated that too high of a timeslice will work
against your own job performance-wise.  Any comments, suggestions?

Thanks,
Steve

_______________________________________________
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.