Hi
Sorry to bother the list with this again, but I'm getting desperate. I'm
far from a Cobol expert and will replace this 7000 lines of Cobol with a 300
line Powerhouse one, as soon as possible, but until that happens this has to
work.
I thought that Roy had solved my problem, but it appears I was a bit
premature. I am still getting this '9G' error, which as Roy correctly
points out is 'too many files open'. Now sometimes this program runs
through without a problem and other times (mostly) I get this 9G error. No
one else is accessing the same file, the files are always closed, before
being opened again, so this doesn't make any sense to me.
The latest example is where a file is built and then file equated to,
opened, records are written and then it is closed.
build
/TRANSFER/HP/billing/cptjo/CPTJOERU2002021620020228;rec=-98,2,F,ASCII;DISC
=25000
.
.
.
FILE cptjo=/TRANSFER/HP/billing/cptjo/CPTJOERU2002021620020228
open extend cptjo-file.
write cptjo-record.
close cptjo-file.
FILE cptjo=/TRANSFER/HP/billing/cptjo/CPTJOERU2002021620020228
open extend cptjo-file.
write cptjo-record.
close cptjo-file.
open extend cptjo-file.
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
DUPLICATE PERMANENT FILE NAME (FSERR 100)
+-F-I-L-E---I-N-F-O-R-M-A-T-I-O-N---D-I-S-P-L-A-Y+
! FILE NAME IS AG1178.TEMP.VIRGIN !
! FOPTIONS: NEW,ASCII,FORMAL,F,NOCCTL,FEQ !
! NOLABEL !
! AOPTIONS: OUTPUT,NOMR,NOLOCK,DEF,BUF,NOMULTI !
! WAIT,NOCOPY !
! DEVICE TYPE: 3 DEVICE SUBTYPE: 8 !
! LDEV: 35 DRT: 8 UNIT: 0 !
! RECORD SIZE: 184 BLOCK SIZE: 184 (BYTES) !
! EXTENT SIZE: 31250 MAX EXTENTS: 32 !
! RECPTR: 18 RECLIMIT: 999999 !
! LOGCOUNT: 18 PHYSCOUNT: 18 !
! EOF AT: 18 LABEL ADDR: %00000000000 !
! FILE CODE: 0 ULABELS: 0 !
! FILE OWNER: MGR.VIRGIN !
! PHYSICAL STATUS: 0000000000000000 !
! ERROR NUMBER: 100 RESIDUE: 184 (BYTES) !
! BLOCK NUMBER: 18 NUMREC: 1 !
+------------------------------------------------+
**** COB_QUIT 633 ****
ABORT: BILLING.EXE.VIRDEV
NM SYS a.01004770 dbg_abort_trace+$28
NM USER 11b.0025d398 COB_QUIT+$b8
NM PROG 4b1.0029d158 ybilling+$1a68
Help
-----Original Message-----
From: Richard Barker
Sent: Tuesday 05 March 2002 14:27
To: 'Roy Brown'; [log in to unmask]
Subject: RE: [HP3000-L] Cobol help
Excellent Roy.
I fairly sure this is the problem as I just logged on again, ran the report
and got the error again. I ran it once more, with exactly the same options
and it worked. I'm using Cobol85 and indeed am using OPEN EXTENDS, example:
move 88888888 to nb-account-no.
R1330 - open extend navbil-file.
R1330 - write navbil-record.
R1330 - close navbil-file.
R1330-FINAL-CPTJO-RECORD.
R1330 - open extend cptjo-file.
R1330 - write cptjo-record.
R1330 - close cptjo-file.
move 88888888 to nb-account-no.
R1330 - open extend navbil-file.
R1330 - write navbil-record.
R1330 - close navbil-file.
Total PNR-DETAILS Read: 000487719
END OF PROGRAM
So, OPTIONAL then, I'll get the manual.
Thanks
-----Original Message-----
From: Roy Brown [mailto:[log in to unmask]]
Sent: Tuesday, March 05, 2002 2:02 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Cobol help
"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 *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
