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



I would suggest if you are doing a scheduled reload, take the time to
save the access paths.  Whenever we have scheduled reloads we save the
access paths to return the system sooner than later or decrease
performance.
The rebuild can take days as you said and in BPCS, I don't want to be
the first person to access a file if the access paths were not saved.

Bruce Barrett


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, April 22, 2004 9:29 AM
To: midrange-l@xxxxxxxxxxxx
Subject: 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

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


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.