Re: Duplicate Files in QUSRSYS

On 20-Jan-2012 14:46 , Victor Hunt wrote:

We recently upgraded our system from V5R4 to V7R1. Prior to the
upgrade while deleting unneeded licensed programs we ran into a
problem. While resolving that problem we discovered we have several
(just over 300) duplicate files in QUSRSYS (and perhaps elsewhere).
These are files that end in a number such as 0001, 0002, etc.

Many of these files date from 2005, which was when we upgraded to
new hardware. It most likely happened when we restored saved data
from our old system. Every file name starts with a Q, so they are not
files we created (at least knowingly, they could have come from
configuring various system functions such as TCP, SMTP, etc.)

Has anyone else run into this issue? If so, how did you clean them
up? I’ve been led to believe by IBM support that I cannot just delete
them, but they seem reluctant to give me any methods for removing
them. On the other hand, they don’t seem to be causing any problems,
but I would like to clean them up.

Thanks for any help or suggestions.

The response was correct, do *not* "just delete them." But that no
problems have been noticed does not mean the incorrect database files
and incorrect database relations have not already caused nor will cause
future problems [with the data and\or] with the features that depend on
them.

I have recovered several dozen improperly installed QUSRSYS. Beware
those who fail also to address "Old member name", in addition to the
"Old file name". While I can do so myself the easiest, interactively
while in PDM, I can probably provide some somewhat simplified steps; I
may have done so already in the past, in some message available on the
web, but I have not yet searched; just sending a quick reply presently.

Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.