Every shop I've been at did it slightly different. The ones I like best have a PDS with an index and a member for each product that has all the information you need (install dsns, SMP/E CSI, FMIDs, install date, STCs, start command, stop command, exits, etc.). hat doc can point to a network share (lan drive) we use for the stuff you would want to keep on z/OS Unix. You need a PC to open those PDF files anyway and mainframe dasd is more expensive.
That in combination with a HLQ for install files. SYSX, SYS3, TECH, INSTALL, whatever. In our case (and in other shops I've been at) we use an install hlq, + vendor + product + rel. For example insthlq.CA.MIM.R116.* I've seen this a lots of shops... some using a different HLQ for SMP/E data sets. Why, I don't know ... keeping everything under one HLQ makes it really easy to get rid of an obsolete release / product. Then we use a different HLQ for runtime and drop the version (so data set names don't change between releases). In recent years this stuff moved to be part of the sysres set and is indirectly cataloged so changes go in via rolling IPLs after cloning from a maintenance ISV sysres volume. Usually there is a hlq.vend.product.release.INSTALL or INSTLIB so even if you had no clue about the common DOC PDS, it is easy to find what you want. Is it Friday already? :-) Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
