×
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 30 May 2013 06:59, tim.dclinc@xxxxxxxxx wrote:
I was able to figure out the issue.
it seems when the system does a "RENAME" it creates a temp file with
the description ("old file..."). I deleted all those files and it is
working fine now.
Still not sure why system is creating a file like that, but after
deleting it, it is fine..
I do not have an ability to disprove the claim, for lack of any
access to the S36EE [and trace and auditing], but I doubt that
interpretation of the problem and the resolution is accurate. Perhaps
if the text description is actually "old file..." vs "Old name..." as
claimed, but I doubt that is an accurate description either.
IIRC the "old name" TEXT() implementation [CPX8105 "Old name &1 in &2
owned by &5."; CPX8109 "Old member &2 file &3/&1."] is a side effect
only of restore activity. While the issue with the error may have been
resolved after the noted DLTF activity, I have doubts that the inference
about how\why that action resolved the issue is accurate; because of
course, I believe the assumption about the RENAME procedure utilizing
that same feature is incorrect.
As I had alluded on the RPG400-l in my reply to my reply to the OP, I
expect there were more than one member in the file being renamed. A
similar effect of RSTOBJ\RSTLIB for that TEXT() naming is, like is done
for database files, is also done for members within database files.
Thus if there were /files/ with "old name" text, there are also likely
to have been /members/ with "old name"
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
