FWiW. The generic I/O error [3006] for the FTP GET was a side effect of the QODCLOSE error; i.e. the error referred to as the /previous message/ in the /Recovery/ text for the CPE3006. The QODCLOSE error is a side effect of yet another previous error message, the CPF5129 "interface error" condition. That interface error arose from yet another prior error [albeit not visible in the joblog] in processing the document details for the DLO that was having its data replaced by the GET (REPLACE request. So...

A RCLSTG would probably be excessive. To be sure, that function is not listed in\as the /Recovery/ of the logged messages; the reclaim storage feature should be required almost exclusively for conditions diagnosed by error messages, where stated specifically as recovery action. Also for apparently being in /QDLS, there is the less excessive RCLDLO reclaim feature. However neither is that command listed in any of the messages as recommended recovery actions. That is because the original database I/O error for the QAOS* files [as implementation objects], would generally not be recoverable by the RCLDLO feature, since the database of document details must be functional in order to be properly updated by the reclaim DLO request.

Regards, Chuck

Scott Klement wrote:

This seems to imply a disk error of some sort. Possibly a
corrupt file on disk? (Presumably, the file on the client's side
of the connection.) Have you tried RCLSTG?

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?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.