It's been a while since I encountered a 9x error, so my memory isn't
100%. Basically, if you get a 9x type error from a COBOL program, the
value of the x character refers to a specific FSERROR number. You need
to look at the ASCII character set table (in the COBOL manual, among
others) and the number in the decimal column matching the x character is
the FSERR number. Take it from there!

In case I haven't got that entirely correct, look up FILE-STATUS values
in the COBOL manual. That should confirm or correct what I have just
said.

    Good Hunting



                 Peter

P.S. Any Contract vacancies (HP3000 COBOL and/or Powerhouse) coming up
at Virgin Express. I am available now!



In article <[log in to unmask]>, Richard Barker
<[log in to unmask]> writes
>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.
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

--
Peter O'Donoghue

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