Improvement on FFDC for z/OS & VTS mount state discrepencies

We have had many instances over the years of mismatches between the VTS device mount state in the VTS and z/OS. The latest of these was being pursued through PMR 15331,122,000. In almost all of these instances we get some notification through a z/OS message or business partner call about VTS mount issues. Most of these are resolved somewhat simply through the issuance of an unload command or involvement of IBM CE. However, prior to that there is a lot of work on ensuring that the tape is not really being used and identifying the correct cluster.

While it is a step in the right direction to get the notification of the mismatch we are still left with the task of document collection during a recreate scenario. While setting this documentation request on one system isn't a large effort setting this for 250+ LPAR's requires a lot of manual labor. This is all for a chance to trap the information if the situation were to happen again.

We would like better diagnostics so that the first occurrence of these situations would cause enough document collection to take place to identify root cause. I presume that this would mean that z/OS would invoke a function in the VTS (state save type of request) to collect the documentation for that drive when z/OS identifies that the mount states are out of sync for a particular logical drive.