[daip] TACOP bogus message causing more user confusion.

[Jim Ulvestad]

Hi all,

Here's another one.  I accidentally deleted SN 1 from a uv data set, when
I have higher-numbered SN tables.  Being at least somewhat clever, I had
saved my tables with TASAV.  Thus, I used TACOP to copy SN table 1
back from the TASAV file to the original uv data file.

The message window tells me

coyote> TACOP1: Task TACOP  (release of 31DEC05) begins
coyote> TACOP1: Copied SN file from vol/cno/vers  2   50   1 to  2   18   1
coyote> TACOP1: OUTPUT EXTENSION FILE ALREADY EXISTS
coyote> TACOP1: Purports to die of UNNATURAL causes
coyote> TACOP1: coyote       31DEC05 TST: Cpu=       0.0  Real=       0

When I ran EXTLIST before the TACOP,
I was told that I had SN files 2 through 6.  When I ran EXTLIST after
TACOP, it listed SN files 1 through 6.  I tried plotting SN 1, and it looks
just fine.  So apparently the TACOP worked fine, but got confused because
there were higher-numbered SN files in existence, thus giving me an error
message.  My conclusion is that I should believe the line saying
"Copied SN file ..." and not believe the message about the output file
already existing and the death by unnatural causes.

ju