|
Actually what he says about the subsystem descriptions may, or may not, be true. Here's the catch: If you do what I used to do, which is copy over qbatch subsystem description from a backup library prior to the upgrade after every upgrade then you'll notice you have to keep doing this because you lost your change. Why? Because somewhere in the internals of the subsystem description is it's release level and if it's really old (V2 I think) it cannot upgrade it during the OS upgrade so it replaces it. I have thousands of job queue entries in QBATCH. Finally called IBM on this and the workaround is to recreate my subsystem description from scratch (or manually add the thousands of job descriptions to the new qbatch). I wrote a program to retrieve the attributes of the backup qbatch and create a new qbatch. Now IBM updates it fine and I don't lose my job queue entries. Again, I only had to run the program once and every os upgrade since then has been fine.
Perhaps if you are one of those shops that tried something clever and restored a machine onto another machine because you were more than n-2 levels behind or just would rather spend a month cleaning up problems than a day doing two upgrades to get there the official way, then you may have also fell into this trap.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.