Re: More CPYFRMIMPF question - Monitor for bad path...

see inline, marked with >@>@>

---original message----
Simon sez:

>Member MYFILE file MYFILE in MYLIB cleared.
>File QACP296636 created in library QRECOVERY.
>Member QACP296636 added to file QACP296636 in QRECOVERY.
>File QACP296636 in library QRECOVERY was created.

The above stuff is indicating that a copy of the file was created so the
command can recover in case of errors.  Oops, it cleared the target file
before it copied it to QRECOVERY.  APAR!

>@>@>Due to the nature of the command (CPYFRMIMPF) - it must be creating
>@>@>intermediate files for doing the conversion from delimited to native
PF
>@>@>formats.    I would think they are used for conversion rather than
>@>@>recovery - although QTEMP would be a better place for these workfiles.

>Object not found.

This is the error that indicates the stream file was not found.
<snip>
The copy of zero records is the flawed recovery code.  APAR!

>@>@>that's what I thought.  It should have quit at the 'object not found'
>@>@>which it should have checked that before creating/changing qrecovery
and
>@>@>qtemp objects, and DEFINATELY before clearing the file.

>I also tried to monitor for 'Object not found' (CPFA0A9) but it is a
>diagnostic, not an escape message.

Exactly.  See above for how this is supposed to work.  It should be
verifying ALL parameters before it starts the copy.  Losing your data due
to a missing file is inexcusable!

>@>@>agreed.  As it happens, at this point in MY job, losing the data is
not a
>@>@>big deal.  but still, I should be able to monitor for the failure.

>you would think an invalid path would make the command bomb, whouldn't
>you?

It does.  Just not how it should bomb. APAR!

>@>@>The rallying cry of the iseries disenfranchised!  APAR!


---in another message-----
Al sez:
I don't perceive that IBM considers QDLS strategic enough for further
significant investment.  I am open for anyone to disagree with me.

>@>@>But it's not in QDLS.  I'm copying right out of the plain old root
IFS.

>@>@>Anyway, I'm not going to hold my breath for a PTF.   Thanks to all for
>@>@>the help.

>>>>Rick