Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!ENGVAX.UUCP!KVC
From: KVC@ENGVAX.UUCP.UUCP
Newsgroups: mod.computers.vax
Subject: Re: image dump
Message-ID: <8701310327.AA18593@ucbvax.Berkeley.EDU>
Date: Fri, 30-Jan-87 15:24:00 EST
Article-I.D.: ucbvax.8701310327.AA18593
Posted: Fri Jan 30 15:24:00 1987
Date-Received: Sat, 31-Jan-87 09:16:53 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23
Approved: info-vax@sri-kl.arpa

> Apparently, there is no way to tell $CREPRC to set the created process
> to /DUMP (it must be there somewhere, because RUN/DET/DUMP works, but
> it's not documented). A workaround is to let the created process do it:
>
>     Jan
 
According to the "VMS System Services Reference Manual" for VAX/VMS Version
4.4, on page SYS-87 under the description of the STSFLG parameter to SYS$CREPRC
there is a table of flag bits, including:
 
PRC$M_IMGDMP    Enable image dump facility.  If an image terminates
                due to an unhandled condition, the image dump facility
                writes the contents of the address space to a file in
                your current default directory, (sic)  The file name will be
                the same as the image name which terminated.  The
                file type will be DMP.
 
Also, the /DUMP qualifier to the RUN command is documented under the
topic "HELP RUN PROCESS /DUMP" as well as on page DCL-370 of the "VMS DCL
Dictionary".
 
        /Kevin Carosso                 kvc%engvax.uucp@usc-oberon.usc.edu
         Hughes Aircraft Co.