Steve Miller at Beechglen solved this. The parentheses around the target
file name imply a new file. If the file already exists, there should be no
parentheses around the target file name.

I was misled by the example in the section titled "Recovering from Index
Corruption" in the online KSAM/XL manual. See
http://docs.hp.com/mpeix/onlinedocs/32650-90886/32650-90886.html

At 03:52 PM 1/28/2004, [log in to unmask] wrote:
>I have created a job which runs FCOPY to copy records from one KSAM/XL
>file to another. The job builds the target before it runs FCOPY. However,
>even though I *do not* specify the ;NEW option on the command line, FCOPY
>blows up claiming that the NEW option was specified and the target file
>already exists. I can't figure why on Earth it thinks the ;NEW option was
>specified. Here's the relevant part of the $STDLIST.
>
>:if finfo("ITESFXT.ORIDATA","EXISTS") THEN
>  *** EXPRESSION FALSE: COMMANDS IGNORED UNTIL MATCHING ELSEIF/ELSE
>  /ENDIF
>  :  tell !HPSTREAMEDBY !HPJOBNAME found duplicate ITESFX temp file. Aborting.
>  :else
>  *** RESUME EXECUTION OF COMMANDS
>  :  build itesfxt.oridata;rec=-121,,f,ascii;disc=6000;ksamxl;&
>  :  key=(b,1,6,dup;b,7,18);firstrec=0;noreuse;defblk
>  :endif
>  :
>  :FCOPY FROM=ITESFX.ORIDATA;TO=(ITESFXT.ORIDATA);KEY=0
>
>  HEWLETT-PACKARD 31900A.05.04 FILE COPIER  WED, JAN 28, 2004,  3:42 PM
>  (C) HEWLETT-PACKARD CO. 1999
>  *144*
>  NEW OPTION: FILE ALREADY EXISTS
>  0 RECORDS PROCESSED *** 1 ERROR
>
>  Program terminated in an error state. (CIERR 976)
>  REMAINDER OF JOB FLUSHED.
>
>
>Any ideas are greatly appreciated.

--
Tom Brandt
Northtech Systems, Inc.
130 S. 1st Street, Suite 220
Ann Arbor, MI 48104-1343
http://www.northtech.com/

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