Editing Core dump (section)

=== {{Anchor|VMCORE}}Naming ===
==== OS/360 and successors ====
In [[OS/360 and successors]], a job may assign arbitrary data set names (dsnames) to the ddnames <code>SYSABEND</code> and <code>SYSUDUMP</code> for a formatted ABEND dump and to arbitrary ddnames for SNAP dumps, or define those ddnames as SYSOUT.{{efn|SYStem OUTput files (SYSOUT) files are temporary files owned by the [[Spooling|SPOOL]] software.}} The Damage Assessment and Repair (DAR) facility added an automatic unformatted{{efn|IBM provided tools for extracting and formatting data from an unformatted dump; those tools{{efn|Initially the batch utility IMDPRDMP; currently the TSO command and [[ISPF]] panel repertoire for Interactive Problem Control System (IPCS).}} often made it easier to deal with an unformatted dump than a formatted dump.}} storage dump to the dataset <code>SYS1.DUMP</code>{{efn|Since then, IBM added the ability to have up to a hundred dump datasets named <code>SYS1.DUMPnn</code> (nn from 00 to 99). [[z/OS]] supports multiple system dump data sets with arbitrary dsname patterns under installation and operator<ref>{{cite manual
 | title       = z/OS 2.5 MVS System Commands
 | id          = SA38-0666-50
 | date        = March 25, 2022
 | pages       = 474–475
 | section     = Setting the name-pattern for dump data sets
 | section-url = https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa380666/$file/ieag100_v2r5.pdf#page=506
 | url         = https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa380666/$file/ieag100_v2r5.pdf
 | access-date = April 6, 2022
 }}
</ref> control.}} at the time of failure as well as a console dump requested by the operator. A job may assign an arbitrary dsname to the ddname <code>SYSMDUMP</code> for an unformatted ABEND dump, or define that ddname as SYSOUT.{{efn|If SYSMDUMP is allocated, then no formatted dump is written to SYSABEND or SYSUDUMP.}} The newer transaction dump is very similar to the older SVC dump. The ''Interactive Problem Control System'' (IPCS), added to OS/VS2 by ''Selectable Unit'' (SU) 57<ref>{{cite manual
 | title       = OS/VS2 MVS Interactive Problem Control System (IPCS) System Information - SUID 5752-857
 | id          = GC34-2004-0
 | date        = March 1978
 | edition     = First
 | url         = http://bitsavers.org/pdf/ibm/370/OS_VS2/GC34-2004-0_OS_VS2_MVS_Interactive_Problem_Control_System_IPCS_System_Information_197803.pdf
 | publisher   = [[IBM]]
 | access-date = June 29, 2023
 }}
</ref><ref>{{cite manual
 | title       = OS/VS2 MVS Interactive Problem Control System User's Guide and Reference - SUID 5752-857
 | id          = GC34-2006-1
 | date        = October 1979
 | edition     = Second
 | url         = http://bitsavers.org/pdf/ibm/370/OS_VS2/GC34-2006-1_OSVS2_MVS_Interactive_Problem_Control_System_Users_Guide_and_Reference_2nd_ed_197910.pdf
 | publisher   = [[IBM]]
 | access-date = June 29, 2023
 }}
</ref> and part of every subsequent [[MVS]] release, can be used to interactively analyze storage dumps on [[DASD]]. IPCS understands the format and relationships of system control blocks, and can produce a formatted display for analysis. The current versions of IPCS allow inspection of active address spaces<ref>{{cite manual
 | title       = z/OS 2.5 - MVS Interactive Problem Control System (IPCS) Commands
 | id          = SA23-1382-50
 | date        = 2023-05-12
 | page        = [https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa231382/$file/ieac500_v2r5.pdf#page=259 239]
 | quote       = ACTIVE, MAIN, or STORAGE specifies the central storage for the address space in which IPCS is currently running and allows you to access that active storage as the dump source. You can access private storage and any common storage accessible by an unauthorized program.
 | section     = SETDEF subcommand - set defaults
 | section-url = https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa231382/$file/ieac500_v2r5.pdf#page=257
 | url         = https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa231382/$file/ieac500_v2r5.pdf
 | publisher   = [[IBM]]
 | access-date = April 6, 2022
 }}
</ref>{{efn|With read authority to facility class BLSACTV.ADDRSPAC, IPCS can view any address space.}} without first taking a storage dump and of unformaated dumps on SPOOL.

==== Unix-like ====
Since Solaris&nbsp;8, system utility <code>coreadm</code> allows the name and location of core files to be configured. Dumps of user processes are traditionally created as <code>core</code>. On Linux (since versions 2.4.21 and 2.6 of the [[Linux kernel mainline]]), a different name can be specified via [[procfs]] using the <code>/proc/sys/kernel/core_pattern</code> configuration file; the specified name can also be a template that contains tags substituted by, for example, the executable filename, the process ID, or the reason for the dump.<ref>{{cite web
 | url = http://man7.org/linux/man-pages/man5/core.5.html
 | title = core(5) – Linux manual page
 | date = 2015-12-05
 | access-date = 2016-04-17
 | website = man7.org
 | archive-date = 2013-09-20
 | archive-url = https://web.archive.org/web/20130920151607/http://man7.org/linux/man-pages/man5/core.5.html
 | url-status = live
 }}</ref> System-wide dumps on modern Unix-like systems often appear as <code>vmcore</code> or <code>vmcore.incomplete</code>.

==== Others ====
Systems such as [[Microsoft Windows]], which use [[filename extension]]s, may use extension <code>.dmp</code>; for example, core dumps may be named <code>memory.dmp</code> or <code>\Minidump\Mini051509-01.dmp</code>.