Re: File left open in QZRCSRVS job

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On 05/05/2008, at 6:24 PM, Jevgeni Astanovski wrote:

> 2. From what was advised, trying to capture an error and then  
> forced file close before exit seemed pretty simple. But it assumed,  
> that I know what exception to capture. Because capturing the  
> exception "File cannot be cleared as it is held" gives me nothing,  
> as it is already late. To find this exception I've placed several  
> "printf" into the program to trace it somehow. But :-((( it never  
> crashed since that time. Before that it crashed almost every day...

If you mean that your program has been recompiled with additional  
printf statements and now the failure doesn't occur then that  
suggests the real cause is a storage management issue.

While this can happen with other programming languages it is more  
prevalent with C because of its peculiar views on storage (no fixed- 
length variables, no compiler support for bounds checking, strings  
are arrays and arrays are just pointers, etc.)

In general, if your C code is failing and then starts working once  
you put printf (or other) statements in the code you probably have an  
issue with storage corruption. By adding the additional statements  
you've just moved the corruption to a less sensitive area of storage.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------