Whether or not to save access paths when doing an unload/reload

Normally we don't save access paths.  However we flipped a little switch 
to start saving access paths.  And we really didn't notice a significant 
change in time.  However we do omit a large number of libraries.

I have an unload/reload scheduled shortly for this machine.  Last time I 
did an unload/reload, and didn't save access paths, it took DAYS for all 
of the access paths to rebuild.  But that was an earlier model, and many 
versions of OS ago.  I am thinking that when we run the save that we 
should save access paths.

What y'all think?


What get's run on a nightly basis (along with SAVDLO, SAV, etc), and 
didn't really very much when we changed &ACCPTH:
             SAVLIB     LIB(*ALLUSR) DEV(&TAPEDRIVE) EXPDATE(&EXPDT) +
                          ENDOPT(*LEAVE) DTACPR(*DEV) OMITLIB( +
                          ACC* ASSET* ATJ* ATS* BAD* +
                          BPCSUSR* BPCSS4* +
                          BPCSS2* BPCSS3* BPCSS6* BPCSPTF* +
                          BPCSF602 BPCSO602 +
                          BPCS405CDO BPCS405CDS +
                          DCU* DATDIVF DHTDIVF +
                          EMR* LYLDIVF LXI* +
                          MGRA* MGRC* MGRD* MGRF* MGRG* MGRH* +
                          MGRIN5* MGRP* MGRR* MGRSI* MGRTPF* MGR1* +
                          PAIAVIF PAILIMF PAIPAMF PAIRMCF PPIARDF +
                          PPIASHF PPICORF PPIELKF PPIFABF PPIHAMF +
                          PPIPEPF +
                          QA* QB* QC* QD* +
                          QE* QFIX QFNTCPL QG* QH* QI* QM* QO* QP* +
                          QPW* QPFRDATA QQ* QR* QS* QT* QU* QYPINT +
                          QZRDPACK RCS* REL* RSC* SBSV* SCSERVER +
                          SEQ* SSA* XM* +
                          ) OUTPUT(*PRINT) ACCPTH(&ACCPTH)

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com