> > Such new statements also > require delegation in DIRMAINT.
Both DIRMAINT and VM:Secure cater for MINIOPT. Why not expand on that? Another approach we've used in the past is a common file on each > system disk that lists the purpose and change history (e.g. @WHATSON > THISDISK). But if you format that disk, you lose @WHATWASON THISDISK as well! :-) As anything else it requires discipline to keep it valid. > Or if you want, one single disk in the system that has one file per > system disk, named with userid and CUU. > If you have the information in a file or multiple files, it is very > easy to use a lookup stage to annotate some output with this (I do > this also for SFS directories, for example - how about adding comments > there as well). I actually have a MDISKMAP COMMENTS file that contains userid, address and comments for critical minidisks. That file is then used by my MDISKMAP EXEC which can then display comments in the right-most column of the 132-column listing. And it uses PIPEs and LOOKUPs extensively. </plug-in> MDISKMAP reads multiple source directories, cross-references them (DASD sharing), displays overlaps and cross-system overlaps, can display all links (and links to links...) to minidisks, limit the display to certain userids... It also checks for online/offline DASD, can integrate VSE VTOC listings and VSE/VSAM catalog listings with exact cyl/track positioning for each VSAM file extent, graphically display disk usage... Available for free to interested parties. Contact me offline if you want it. </end plug-in> Ivica Brodaric
