PMD is the Postmortem Dump task. When a task aborts, PMD generates a dump of its header and address space to aid in debugging. You can make a task eligible for a Postmortem Dump in any of three ways: o task build the task with the /PM switch on the task image file or DCL LINK/POSTMORTEM command o install the task with the /PMD=YES switch, or DCL INSTALL/POSTMORTEM command o abort the task with the /PMD switch or DCL ABORT/POSTMORTEM Postmortem dumps are put on the system disk under UFD [1,4] in the file taskname.PMD and are automatically spooled by PMD. NOTE The print spooler automatically deletes all files with the type .PMD after printing them. PMD also produces Snapshot Dumps of running tasks. See HELP PMD SNAPSHOT See Appendix D of the RSX-11M/M-PLUS Task Builder Manual for more information on PMD. 2 SNAPSHOT A running task can issue a macro call to generate a dump of its header and address space to aid in debugging. To generate a Snapshot Dump you must issue two macro calls in your program. The SNPBK$ macro must be specified in a data area to define the Snapshot Dump Control Block, and the SNAP$ macro must be specified at each place in the code where a Snapshot Dump is desired. SNPBK$ dev,unit,ctl,efn,id,L1,H1,L2,H2,L3,H3,L4,H4 SNAP$ ctl,efn,id,L1,H1,L2,H2,L3,H3,L4,H4 dev, device and unit efn event flag to use unit for dump file id number to identify ctl what to dump: a particular SNAP$ SC.HDR header SC.LUN LUN table L1,H1 memory limits for SC.OVL overlay segments L2,H2 dumping up to four SC.STK stack L3,H3 separate blocks of SC.WRD memory in words/RAD50 L4,H4 memory SC.BYT memory in bytes/ASCII Snapshot dumps are put on the specified device under the task's UFD in the file taskname.PMD and are automatically spooled. NOTE The print spooler automatically deletes all files with the type .PMD after printing them. See Appendix D of the RSX-11M/M-PLUS Task Builder Manual for more information on Snapshot Dumps.