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



First, we're on V5R1. So this may be (oh, heck, IS) an issue.



Every night I save a copy of our data library to a test library, which I can
use for testing (no partitions). The test library is then saved to a save
file. I can restore the test library from the save file, if my tests, well,
screw up.



I don't often have to restore it in the middle of the day, but it does
happen. In fact, today I've done it twice (bad day). Obviously things go a
little slow (to put it mildly) during the restore. But even after my
command returns to the menu, there are still jobs running that are building
indices. WRKACTJOB shows:



Subsystem/Job User Type CPU % Function Status

QDBSRV05 QSYS SYS 46.8 IDX-A.HISLA1 RUN

QDBSRV04 QSYS SYS 43.3 IDX-D.LYMDRL01 RUN



The restore is done by, first, clearing the library. Then doing a RSTOBJ to
the test library. Is there a better, quicker way to do this? I never
noticed this before (i.e., on other systems on which I have worked using the
same technique), but I would have thought (erroneously it seems) that the
indices would have simply been restored from the save file, instead of
under-going a complete rebuild. The LFs are in the save file. The disks
are mirrored.



Jerry C. Adams

IBM i Programmer/Analyst

You'll never make it - four groups are out. Go back to Liverpool. - Decca
Records executive to the Beatles (1962)

--

A&K Wholesale

Murfreesboro, TN

615-867-5070




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.