z/VSE Standalone Dump priorities
Ingolf24 120000DRN3 Visits (1584)
If you have a system failure, e.g. hard- or softwait, you may take a standalone dump (SADUMP) to tape or disk. The standalone dump program dumps the system areas and the active partitions in a predefined order. If the dump of all data does not fit to the tape or disk, it does stop writing dump files. So it could be that important dump areas / partitions are not written.
Therefore you can define the SADUMP priority for each partition, data space or memory object. That is to give those areas a high priority, that are most important for your workload. So you can ensure a high probability, that those areas are included on the dump medium.
You can use the QUERY OPTION,<SYSLOG id> to display the SADUMP priority of a specific partition on the console. E.g. after you installed z/VSE: BG has a priority of 0, F1 and F2 have a priority of 5, which means that F1 and F2 are
most likely included, BG only, if there is enough space available - depends of the space on tape or disk.
The SADUMP priority can be defined with the VSE Job Control option // OPTION SADUMP= or // STDOPT SADUMP= for the partition address and data space and memory objects.
You can exclude shared memory objects via // STDOPT SADMPSMO=NO
The QUERY and OPTIONs commands are described in the z/VSE Job Control Statement. You can download this book from the z/VS
The z/VSE ASI procedure or dynamic partition profile may include an OPTION statement, e.g. $1JCL.PROC, $2JCL.PROC, includes // OPTION SADUMP=5. You may add or change the priority there, use the corresponding skeleton in ICCF library 59 or include the OPTION statement into your VSE job.