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



I've seen something very loosely related. Back in the early days of
OS/400 I got into the habit of saving my QBATCH subsystem description
because the upgrade would lose all several hundred job queue entries and I
detested rekeying them. Then someone told me that I didn't have to do
that anymore because the upgrade would automatically fix my QBATCH
subsystem description. However, since I've always been doing the save of
it to a save file, and restoring it immediately after the upgrade it
couldn't fix my particular QBATCH subsystem description. I figured, no
problem, I'll do the save this next upgrade (just in case) and see what
happens during the upgrade.

Here's where it starts to get relevant...
The upgrade could not modify my QBATCH subsystem description because it
had been saved and restored since prior to V2R1 and had never been through
the upgrade process earlier. Thus the upgrade process could not fix it.
This was nothing to do with CISC-to-RISC or anything. I ended up having
to delve into subsystem description APIs and rebuilding it from scratch so
that it was no longer flagged somewhere in the DSPOBJD with V2R1.

You know, this is probably another reason to not skip upgrades and just
save all your crud from an old release and restore it on a machine that is
running a newer release.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.