Skip to main content

Hi All,

 

I'm just wanting a fresh perspective on an issue I'm having!

 

I'm randomly getting a file status 9/57 on one particular file (which is IDX"8" format)  on a rewrite. The file in question is only 40MB, but at various points within the program when a rewrite on the file happens, it will randomly report this error!

 

This happens on a 32bit machine running Red Hat Enterprise 5.5, the development machine is 64 bit - but compiling to 32 bit.

 

Any suggestions will be greatfully received, as I'm starting to tear out (what remains of) my hair!

 

Mike.

Hi All,

 

I'm just wanting a fresh perspective on an issue I'm having!

 

I'm randomly getting a file status 9/57 on one particular file (which is IDX"8" format)  on a rewrite. The file in question is only 40MB, but at various points within the program when a rewrite on the file happens, it will randomly report this error!

 

This happens on a 32bit machine running Red Hat Enterprise 5.5, the development machine is 64 bit - but compiling to 32 bit.

 

Any suggestions will be greatfully received, as I'm starting to tear out (what remains of) my hair!

 

Mike.

What version of SX are you using?
9/57 is not a valid file status code if you are running in default Micro Focus dialect mode of operation. I did find a reference to this status being returned if you are turning on the RM directive within your application. In RM COBOL the 57 means that a record is locked within the file.

Are you specifying the RM directive?
Is this file being shared amongst multiple processes?
Is this file in question defined with a LOCK MODE clause in its SELECT statement? (LOCK MODE MANUAL/AUTOMATIC)

Hi All,

 

I'm just wanting a fresh perspective on an issue I'm having!

 

I'm randomly getting a file status 9/57 on one particular file (which is IDX"8" format)  on a rewrite. The file in question is only 40MB, but at various points within the program when a rewrite on the file happens, it will randomly report this error!

 

This happens on a 32bit machine running Red Hat Enterprise 5.5, the development machine is 64 bit - but compiling to 32 bit.

 

Any suggestions will be greatfully received, as I'm starting to tear out (what remains of) my hair!

 

Mike.

We're using server express 5.1 and it is using the RM directive along with OSVS

There isn't a LOCK MODE specified in the SELECT statement. The file in question is being used by multiple processes as it is the orders file for an SOP application, although only one process can access a particular order at any one time .So it might be worth looking at DECLARATIVES to trap and wait should this keep happening.

One thing I have discovered is that a duplicate REWRITE statement found it's way into the file handling copybook, I think a developer got a 'yyp' happy in vi - so i've removed that, recompiled and sent to site to see if that resolves the issue.

Thanks for all your help

Hi All,

 

I'm just wanting a fresh perspective on an issue I'm having!

 

I'm randomly getting a file status 9/57 on one particular file (which is IDX"8" format)  on a rewrite. The file in question is only 40MB, but at various points within the program when a rewrite on the file happens, it will randomly report this error!

 

This happens on a 32bit machine running Red Hat Enterprise 5.5, the development machine is 64 bit - but compiling to 32 bit.

 

Any suggestions will be greatfully received, as I'm starting to tear out (what remains of) my hair!

 

Mike.

We're using server express 5.1 and it is using the RM directive along with OSVS

There isn't a LOCK MODE specified in the SELECT statement. The file in question is being used by multiple processes as it is the orders file for an SOP application, although only one process can access a particular order at any one time .So it might be worth looking at DECLARATIVES to trap and wait should this keep happening.

One thing I have discovered is that a duplicate REWRITE statement found it's way into the file handling copybook, I think a developer got a 'yyp' happy in vi - so i've removed that, recompiled and sent to site to see if that resolves the issue.

Thanks for all your help
Terms & ConditionsAccessibility statement