Re: FTP unable to close file. Error Code CPE3006

What makes the given situation especially confusing, is that there are two [or more; depending on perspective] "close errors" being diagnosed. The first close error is for a database file QAOSSI12 as implementation object. That "database close" error just happens to occur during the "DLO close" processing, which sensibly is manifest as an error in closing the STMF in the /QDLS. That the STMF was accessed via the generic IFS access methods by\in the FTP session, versus by the DLO-specific access methods, the FTP failures are manifest as the more generic IFS close errors. And even that errno is just replacement text as part of the FTP-specific error message for its "close" processing.

Since the error was during close processing [of the file target of the GET (REPLACE], then as long as no records were lost [e.g. for buffered records not written as part of the close; or perhaps just records unavailable to other threads as with row locking], the /logical condition/ of the file being left "open" could easily be innocuous. Thus that the GET would seem to have been effected sufficiently to be considered successful is not so strange.

However the failure to close could still become a problem, while the open as a logical condition remains, for presenting a conflict with _other_ operations that might be attempted later. For example a failed close which leaves a file "open" would often preclude operations such as delete of the file object. Since the FTP is record transport and thus the (REPLACE of the GET applies to the data versus the object, all of the data could be replaced successfully so the failure to close could remain a non-issue. Unfortunately a failed open of the DLO could obfuscate the error with the implementation object, since for example a DLTDLO might be manifest as an allocation error [per "not closed"] irrespective of the origin of the error(s) with the implementation object [which although since determined to be an allocation error, could have been any error during the fclose()].

Regards, Chuck

brad_bird wrote:

Our backups finished and we still got the error. We had
to initiate a second process to get the upload files and
it worked fine; even though this error job was still
reporting errors. Strange.

Jack Kingsley wrote:

Brad, not hitting a lib/file/member that is in use and or
locked via maybe off hours backup.

On Tue, Nov 17, 2009 at 11:52 AM, brad_bird wrote:

During our nightly polling, we starting getting a "Unable to
close file. Error code CPE3006" on upload but yet all download
files were sent successfully. This is a portion of the FTP
output log and program log for the error. Anyone have any idea
on the cause?

get FIN.DSS (REPLACE
227 Entering Passive Mode (<ip-address-removed>).
125 Data connection already open; Transfer starting.
Unable to close file. Error code CPE3006.
226 Transfer complete.
225 ABOR command successful.
<<SNIP>>