  Debugging LIB$SPAWN? 
 The Question is:
 
This error just started happening.  We have not changed the code since June
 2001.  The executable was running fine and then this problem began.  What
 could cause this to happen?
 
 The Answer is :
 
  The OpenVMS Wizard has seen bugs latent in OpenVMS itself for
  over twenty years, and thus takes little stock in statements
  such as "We have not changed  the code since June 2001."
 
  To confirm, the DCL command that you are spawning is:
 
    copy FPRS$INPUT:faa055844 FPRS$PET_HISTORY:593749.dat
 
  The error messages shown are not those normally from COPY, which
  would imply that another image is activating.
 
  Do you have a DCL symbol COPY around?
 
  Do you have a COPY logical name defined?
 
  This appears to be an application or site-specific bug or (as was
  mentioned) some application activated via an errant COPY symbol
  or errant COPY logical name; please contact the vendor of the
  particular application involved in generating the command error.
 
  The callable convert (conv$) routines are an easy way to copy files
  more directly.
 
 Answer written or last revised on  22-MAY-2002 
