Re: File system error occurred. Error number 3029.

[Gary Thompson <GThompson@xxxxxxxxxxx>]

Scott wrote:

> But...  I don't understand why your process doesn't abort when it gets 
> the EBUSY error?  If step 1 fails, why does your program continue on to 
> step 2?  Perhaps that's a bug.

The move is by design: processed files move to a "no error" folder
        and unprocessed files move to an "error" folder that is reviewed,
        with the intention of re-processing such files successfully.

        These are financial transactions and are audited daily and montly. 


Scott also wrote:

> When you open a file with the open() API, you can specify O_SHARE_NONE, 
> O_SHARE_RDONLY, O_SHARE_WRONLY, or O_SHARE_RDWR.

Thank you for the suggestion.

This could solve a problem where, usually, an inexperienced operator 
performs the initial, 
        manual file handling and fogets to close the MS Excel document 
from where the IFS
        file was saved: leaving the IFS file locked.

        We are currently reviewing our process, system design and 
documentation.