×
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.
David Gibbs wrote:
Kirk Goins wrote:
Couple questions come to mind #1 were Access paths saved? Where is
the 2749 in relation to a disk controller? On the Same BUS or IOP?
( this last item can kill tape performance )
Our IT guy replies ...
The save was done with a Go backup option 11 which is the same as a
Go save. By default the access paths are saved. I'm talking with IBM
now and they said they have seen instances where the access paths
were backed up and they were still rebuilt during the restore.
However the only way to confirm that is with a command line which we
don't have since the restore is still running. They are not on the
same bus or IOP.
To suggest that "they have seen" is a daft comment; in the least,
because it seems to imply that there is some unknown defect for which
that sometimes is the effect. While indeed there are some defects for
which that might transpire, it is best stated that access path rebuilds
during restore, regardless that ACCPTH(*YES) was specified, is perfectly
valid and normal for some restores. Specifically for when the DR
strategy did not properly account for what saving access paths can
actually effect; i.e. data in different library than the logical file
that defines the access path, vitiates the intent of the request to save
access paths, since it is not possible to ensure the data and index are
consistent\unchanged so the index objects must be rebuilt for the data
to ensure integrity of the data.
FWiW: Before that restore, I always adjust the message which defines
the SysRqs options, to effect WRKJOB instead of the shipped default of
DSPJOB, in order to enable a command line. In that manner I can issue
WRKACTJOB [JOB(*SYS)], WRKSYSACT [to look for LD tasks], and EDTRBDAP as
necessary, from the SysRqs-3 menu option.
The RSTLIB of *NONSYS can be restarted, thus SysRqs-2 to effect
ENDRQS would enable command line access. However I would perform
several SysRqs-3 OUTPUT(*PRINT) over several minutes to record the
program stack and job locks, for possible later review for any [lack of]
changes.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
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.