"Richard Barker" <[log in to unmask]> wrote in message
news:a628iu026c6@enews1.newsguy.com...
> Hi
>
> We have an old huge Cobol program here that produces Invoices.  It also
> produces files to be sent to another application.  Now someone made an
> unrelated change to the program and now we get this:
>
> R1320-WRITE-CPTJO-RECORD.
> R1320-WRITE-CPTJO-RECORD.
> R1320-WRITE-CPTJO-RECORD.
> R1300-WRITE-ERUCA-FILE.
> R1310-WRITE-ERUCA-RECORD.
> R1320-WRITE-CPTJO-RECORD.
> R1300-WRITE-ERUCA-FILE.
> R1310-WRITE-ERUCA-RECORD.
> R1320-WRITE-CPTJO-RECORD.
> R1320-WRITE-CPTJO-RECORD.
> Unable to open CPTJO - Status : 9G
> Filename: AGBILL
> File status is 9d
> Unable to CLOSE file, See File System error [9x] (COBERR 633)
> Program file: BILLING.EXE.VIRDEV
>
> We open and close the file numerous times, why is it suddenly getting this
> 9G error.  I realise I'm not giving you much information, but has anyone
> come accross 9G error before.  Nothing else is access the file.

9x errors are 'Implementation-defined' COBOL file status errors.

The G is the FSERR number expressed in the ASCII collating sequence, or in
other bytes, 71.

This is: TOO MANY FILES OPEN (FSERR 71)

Likewise, the 9d decodes to: DUPLICATE PERMANENT FILE NAME (FSERR 100)

My guess? You've recompiled this from ANSI-74 to ANSI-85, and fallen foul of
some of the file-handling subtleties that are different (e.g. OPEN or OPEN
EXTEND on 74 will build a file that does not exist at the time; 85 needs an
OPTIONAL clause not to error on this).

Or if not, that the 'unrelated change' is not so unrelated as you think, and
has broken the existing processing..... :-(

--
Roy Brown

Fixing COBOL for a living...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *