  Debugging Run-time Executable Image Error? 
 The Question is:
 
What is the correct way to run an executable from a command procedure?
I am currently experiencing problems when trying to do it.  The program works
 fine when manually running the program but produces a stack dump (pas$rtl???)
 when ran from the command procedure.
Please help.
 
 
 The Answer is:
 
  The program likely contains a bug, probably either based on an
  (erroneous) assumption on the command input or potentially based
  on (if run in batch) differences in the process quotas.
 
  Use the traceback information (stackdump) from the error with the
  compiler listings and the LINKER map file to locate the specific
  error, and then work backwards from the error to locate the trigger.
 
  You can also use the DBG$DECW$DISPLAY logical name or various other
  redirections to bring up the application running under the OpenVMS
  debugger, and running within the command procedure environment.
  The debugger can then be used to determine the actual run-time
  operation of the application, and to compare this behaviour with
  the intended operation of the application.
 
  A list of some of the more common programming errors is located
  in topic (1661).
 
