The select is as you suggest.  I haven't tried changing the OPEN to use I-O mode.  That would certainly remove the problem.

I'm beginning to suspect that the JCL is incorrect.  It looks like this:

!JOB  COMRPTSJ, BATCHOPS/JOBS.SUPPLY;OUTCLASS=205,1,1
!CALC FINFO("ECFDAT.TEMP.SUPPLY","EOF")*20
!SETVAR COMRPTS_FS HPRESULT
!PURGE ECFDAT.TEMP.SUPPLY
!FILE ECFDAT=ECFDAT.TEMP.SUPPLY,NEW;DISC=!COMRPTS_FS;SAVE
!FILE OPDB=OPDB.FLS.SUPPLY
!RUN COMRPTS.TEMP.MIS;PARM=3
?(FISPER2K)
!DELETEVAR COMRPTS_@
!EOJ

I'm pretty sure that file equation is causing my problem.

If the OPEN routines detect a problem, they report it and STOP RUN.

Yes, the WS-ECF-IO-?? items are not part of the FILE STATUS data item.

Thanks for your help.  I suspect that just changing to an OPEN I-O, would be the simplest solution.

>>> Bruce Hobbs <[log in to unmask]> 10/25/99 05:05PM >>>
At 4:09 PM -0400 10/25/99, Boris Kortiak wrote:

>Back to the program from before.  I made a change last Friday to a program which originally only created a KSAM file.  The change was to simply continue processing to generate a report.  The original program OPENs the KSAM file OUTPUT.  I added logic after the CLOSE to reOPEN the file INPUT, MOVE LOW-VALUES to one of the keys and do a START on that key; see sample below.
>
Wouldn't you simply want to SELECT ... ACCESS DYNAMIC and OPEN I-O to begin with? What does your SELECT statement look like anyway? Are there any file equates in effect?

>The start generates a FILE STATUS of '23' indicating that it can't find a key based on the START statement.
>
Although it's probably not important here, I believe you can also get a "23" when it appears that you're using START with a missing optional file.

>Please take a look and let me know if you see anything obvious.
>
>The other strangeness is that since no processing is done the program attempts to CLOSE the KSAM file again after the failed START and gets the FILE STATUS indicating that it is attempting to create an already existing file.
>
Since you're getting "DUPLICATE PERMANENT FILE" it certainly "feels" like the file was re-opened OUTPUT (which I think would lead to that error on the second CLOSE).
>
<snip>
These 88-levels do apply to something other than the FILE STATUS variable, right?

>Is it unacceptable to OPEN a file in INPUT mode after having created it in OUTPUT mode in the same program?
>
Not that I'm aware of, but since you can use OPEN I-O it isn't immediately clear to me why you'd want to do that
=======================================================================
Bruce Hobbs, CCP, CDP   856 N Monterey St         Phone: (626) 570-8028
Partner                 Alhambra, CA 91801-1574   FAX:   (626) 570-9850
Engineered Software     E-mail: [log in to unmask]