(TPFUG/Visa) Need a reliable means to identify all tapes associated with a given dump

If a dump spans more than one tape, you must include all tape numbers on the dump post processing request to obtain the complete dump. If you do not include all tape numbers, the post processing will complete with abend code 2999. 

Although a tape switch can occur during any dump, in general the more serious the dump, the greater the amount of data dumped and therefore the more likely it is that the dump will span more than one tape. The greater the amount of data there is to post process for a dump, the greater the delay if not all tapes are provided on the first request to post process the dump - the first post process request must fail for the mistake to be realized, the full list of tapes gathered, and then the dump must be resubmitted for post processing. Delays in obtaining a complete post processed dump can have critical consequences for business continuity, especially if the dump needs to be sent to the TPF lab as part of a Sev 1 or 2 problem case.

CPSE0156I provides the VSN of the first tape a dump is written to, but there is no messaging indicating when writing a dump to tape finishes. There is also no current support to automatically record any subsequent tapes associated with a given dump (e.g. ZDHST only includes the first VSN). 

PJ47194 updated CPSE0012I to include the VSN of the new dump tape, but tape switches while a dump is being written out do not always result in CPSE0012I messages.

We need a reliable mechanism to allow Operations/Coverage to immediately obtain a full list of all tapes associated with a dump once all the dump data has been written to tape. This mechanism cannot rely on a subsequent dump being taken in order to identify a time period during which to search the console for the various tape switch messages that are possible.

The type of mechanism we are looking for would allow Operations/Coverage to add automation around specific message prefixes or be provided via a Zentry display.