×
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.
On 25-Nov-2013 13:07 -0800, Steinmetz, Paul wrote:
I installed from a V7R1 combined OS and PTF DSLO image <<SNIP>>
I am not sure how easily I would be able to gain a better
understanding of the failures without more directly poring over the
actual spooled output from the install activity, and then reviewing the
system at the point of the freshly failed install [prior to any
recovery]. Lack of access to the revisions to the option and the OS,
either via the IBM software source code or sufficiently descriptive PTF
cover letters documenting them, makes understanding the origin that much
more difficult.
My first impression is that the DSLO image has down-level SQL catalog
[TABLE and VIEW] files in QSYS2 [XTND: extended base option-01 of the
OS], as compared with the code-level of the OS itself. That is, the
/recovery steps/ that were given for the failed installation, appear
might be what is required to be performed at the system from which the
DSLO image is taken. If so, the question would seem to be, how did the
application of maintenance to that DSLO-source system go wrong; i.e. how
came about, the inconsistency between OPTION(01) of the OS and the OS
code itself on the DSLO system? IIRC, and if the implementation used to
deliver the /upgrades/ to the catalog files remains unchanged, there are
a number of potential origins, and the effects may be subtle, hidden, or
essentially lost... unless the maintenance was applied using *IMMED
apply vs *DELAYED.
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.