Actually, as soon as the open output statement is called the program aborts
with the error message I posted.  I have a display statement right after the
open that is not displayed.

-----Original Message-----
From: [log in to unmask]
[mailto:[log in to unmask]]
Sent: Wednesday, February 28, 2001 3:12 PM
To: Keith Bordovsky
Cc: [log in to unmask]
Subject: Re: [HP3000-L] temporary file cannot be opened




Did you close it after you finished writing? and then OPEN file INPUT?
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431







Keith Bordovsky <[log in to unmask]> on 02/28/2001 03:52:52
PM

Please respond to Keith Bordovsky <[log in to unmask]>











 To:      [log in to unmask]

 cc:      (bcc: Leonard Berkowitz/CORP/HPHC)



 Subject: [HP3000-L] temporary file cannot be opened








Hello all, I have a dilemma I'm in.  I have a COBOL program that I would
like it to create a unique temporary file and write to it on the fly.  The
snippet of code is as follows:

SELECT PRT-FILE ASSIGN USING TF-FMP-PFILE.

FILE SECTION.
FD  PRT-FILE.
01  PRT-REC                      PIC X(80).

WORKING-STORAGE SECTION.
     03  TF-FMP-PFILE.
       05  TF-PIN-PREFIX          PIC X(3) VALUE "TIF".
       05  TF-PIN-FMP             PIC X(5) VALUE SPACES.

This is a COBOL sub-program that is called from an XL.  I load up the
TF-PIN-FMP variable with the pin number of the process I am running.  Then I
attempt to open the file as output using:
        OPEN OUTPUT PRT-FILE
This is the result:
        Filename: FMP00290
        File status is 37
        File/Org/Device does not support OPEN mode [37] ACCESS (COBERR 659)
        Program file: MICFMP.PRG.DCALLS
        OPERATION INCONSISTENT WITH ACCESS TYPE  (FSERR 40)

        +-F-I-L-E---I-N-F-O-R-M-A-T-I-O-N---D-I-S-P-L-A-Y+
        !  ERROR NUMBER: 0           RESIDUE: 0          !
        +------------------------------------------------+
        **** COB_QUIT 659 ****

A similar program I have that is using basically the same logic works like a
charm.  I can't figure out why the COBOL program will not create the
temporary file.  There are no file equations, permanent files, or temporary
file with the same name that this process will attempt to use.  Any help
will be appreciated.
Thanks,
Keith Bordovsky