Re: V4R5 Frustration

Mike,

>Why do we need observability going from 4.4 to 4.5?

You do not need it when restoring a V4R4 object onto a V4R5 system.

>BTW, IBM expect you to move you 'old' box BACK to 4.4 AFTER you save your
>system to go to 4.5, see data migration on page 32 of the roadmap. They
must
>be joking!

I have not looked at the roadmap but I do not believe it. Either the
roadmap is wrong, or are interpreting it incorrectly, or it does not apply
your specific situation. (It is also possible that I am wrong but I do not
think so.)

>I should have clarified that the libaries restore OK from tape using
>*ALLUSR, it's just several thousand objects within them that don't
(because
>of lack of observability I think).

This is the key. Why do you think the problem is caused by a lack of
observability? The job log (or outfile created by RSTLIB) should have
provided a reason for each and every object not restored.  Please be a bit
more specific or provide related information (e.g. job log spooled file or
RSTLIB outfile) to your service provider. My guess is that there is some
other reason that the objects did not restore.  For example, the setting of
the QALWOBJRST (allow object to restore) system value can prevent system
state programs or programs that adopt their owners authority from being
restored.

Ed Fishel,
edfishel@US.IBM.COM


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---