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



As I recall, we got hosed up when we migrated a V2R3 (using save tapes) to a new host at V3R1. When re restored *ALLUSR, it laid down old version of IBM objects that reside in QGPL, which effectively made all of our LPPs backlevel.... Something like that.... Had to reload everything....

I have not heard of user objects being removed though.

Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of albartell
Sent: Wednesday, August 08, 2007 4:36 PM
To: 'Midrange Systems Technical Discussion'
Subject: non-IBM objects in QGPL removed during OS upgrade


I was talking with a customer today that said they have experienced non-IBM
objects being removed/replaced in QGPL during an OS upgrade. It happened
some time ago and they couldn't remember the details of it but was fairly
certain it was because of an OS upgrade. This has caused them to adopt a
shop standard to never use QGPL for anything. I have never experienced this
behavior and would guess that it was possibly something else that caused the
objects to be removed (e.g. some library mirroring software possibly).

Does anybody know if there is precedence, in documentation or experience,
that non-IBM objects in QGPL are replaced/removed during an OS upgrade?

TIA,
Aaron Bartell
http://mowyourlawn.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.