Transaction dump is a service used to request an unformatted dump of virtual storage to a data set, similar to a SYSMDUMP. It is invoked with the IEATDUMP assembler macro which issues SVC 51. You can either request that the dump be written to a preallocated data set or to automatically allocated data sets. To request a preallocated data set, specify the DDNAME parameter that identifies a data set that contains sufficient space in one or more extents for the entire dump to be written. If you don't provide a large enough data set, you will receive a partial dump. To request automatic allocation, specify the DSN and DSNAD parameters, which ensure a dump will not be truncated due to data set space constraints. Automatic allocation is done to SYSALLDA. When using DSN or DSNAD, the maximum size is 2 GB, unless the dump is split among several data sets, in which case there is no restriction. DDNAME also does not have the 2 GB size restriction.
When a Transaction dump is written, a dump directory record describing the dump may be written. Specify the dump directory to be used with the IDX keyword on the dump request. If you do not specify a dump directory, the directory allocated to IPCSDDIR in the current job step will be used. If no dump directory is specified and IPCSDDIR is not allocated, no record describing the dump will be written.
Dump suppression occurs using symptoms available in the current SDWA or a symptom string may be provided (via the SYMREC keyword). If you provide a symptom string, and an SDWA exists, the symptom string is used for suppression purposes. Statistics for dump suppression are contained in the DAE data set and are not differentiated from SYSMDUMPs.
Authorized users may specify the REMOTE keyword on the IEATDUMP macro to request other address spaces on the current or other MVS™ images (in the same sysplex) be dumped. When you request remote dumps, automatic allocation must also be used.
Transaction dump uses an incident token to associate this dump with other diagnostic information. Automatic allocation also uses this incident token for symbol substitution in the data set name pattern. You can generate an incident token using the IEAINTKN macro and providing the INTOKEN keyword on the dump request. If you do not provide an incident token, one will be generated and used internally. While an incident token may always be specified, it may be especially important when remote dumps are requested.