×
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.
On 23-Jan-2012 05:59 , Victor Hunt wrote:
They don't appear to be PTF save files. Here are some examples:
QAALAL0001
<<SNIP several AL Alert-related ; GO CMDALR>>
QAEABK0001
<<SNIP two more EA Education-related ; GO CMDEDU>>
The are database files following the naming convention: Q="Operating
System", A="Database", xx=Component_Id, ..., ####="renamed by database
restore feature during an ALWOBJDIF(*ALL) restore, to protect from
data-loss"
I suppose if the system does not depend on "alerts" and nobody uses
the "Education" [STREDU] feature, then those sets of files could
probably be ignored indefinitely.
However I am not so sure knowing whether alerts might be used by the
OS or products is completely obvious. If there is no data in any of the
members of any of the physical files, then effectively those members can
be deleted; any pertinent data might reside in alternate copies [of the
members or the files], and the database relations may still need
recovery. Reviewing each member list, the data, and the relations; why
access to the system to actively process the members and files is
easiest for someone to effect recovery.
They don't have a description other than "Old name XXXXXXXXXX is
QUSRSYS owned by QSYS." As I mentioned, there are over 300 of them.
Every file with #### suffix *has* effective TEXT('Old name ...')
That is what restore [for install] would have done when either an
improper restore [or an improper install] was done; i.e. not having
followed the proper migration instructions\steps to effect a proper
restore\upgrade.
Regards, Chuck
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.
midrange.com
