Re: Getting a 3029 when trying to open() an IFS file that was close() just a second before...

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

hi Bryce,

You say that you used "iNav to check it, and it's still busy".  The 
point behind iNav is to find out _what_ is using it...  using iNav won't 
stop it from being busy :-)

But, iNav can tell you who/what is using the file.  Then, you can look 
into ending the appropriate job, or fixing he appropriate process so 
that it's not busy anymore.

-SK



On 7/20/2012 9:12 AM, Bryce Martin wrote:
> I'm working on something right now where I need to convert a file from
> UTF-16 Little Endian to UTF-16 Big Endian... the file needs to retain
> its name and have its CCSID as 1200. So here is what I'm doing...
>
>
>
> 1)      Append a random number to the front of the filename (to retain
> uniqueness if multiple processes happening at one time) and do an IFS
> rename (via Qp01RenameKeep)
>
> 2)      Create the file via open()
>
> 3)      If it was successful I do a callp close(fd)
>
> 4)      Then I open the renamed file as read only - this works fine
> everytime.
>
> 5)      Then I try to open the just created file and I am getting an
> error of 3029 Resource Busy.
>
>
>
> I don't know why the resource would still be busy, I closed the file
> descriptor.  And it stays busy, even if I let the program hit an error
> and it finished with *inlr=*on.  I used iNav to check it and it still
> shows busy.  It even showed busy after I ended the 5250 session, which
> killed the job... Any thoughts as to what else could be keeping it busy?
>
>
>
>
>
>
> Thank You
>
> Bryce Martin
>
> National Ticket Company <http://www.nationalticket.com/>
>
> 570-672-2900 ext. 226