We generally create a dataset with the low level qualifier of "OUTPUT" and keep all of the job output from a product's installation in that PDS, and we try to name the members something meaningful (like the install doc name of the job submitted). We also have CA-View, and I also keep the output there for at least a year for product installs - and in some cases much longer for rarely updated products.
As for the PDF's, we do use Unix for that, and I have a web server on the mainframe so we can get to a web page that contains all of our doc. But I do tend to go to the product web page to pull PDF's when I need to look something up, because the vendor pages tend to be more up-to-date (in most cases). C. Todd Burrell Senior z/OS Systems Programmer ITSO (770) 917-8081 (home) (404) 723-2017 (cell) Please visit the ITSO Customer Satisfaction Survey and tell us about your recent experiences with ITSO. This survey is for internal CDC use only and the results will be used to improve business services. Anyone working for CDC in any capacity is invited to participate in our survey. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, May 14, 2008 9:35 AM To: [email protected] Subject: crazy thoughts - keeping product installation infomation OK, I admit to not having had enough sleep. But the following insanity came to me today. So I thought that I'd ask some, hopefully, sane people about it. I always seem to have problems finding documentation on how a product was installed. That is, what jobs were run, where were they submitted from, what did they do, where is there output, and so on. There is also the "problem" of where to keep the documentation, especially PDF files. So I got this weird idea. Why not keep all this stuff in the UNIX filesystem on the z/OS system itself? Something along the lines of: The base directory for &version of &product-name from vendor &vendor would all be kept below the subdirectory: /products/&vendor/&product-name/&version For each such "base directory", there would be a set of directory along the lines of: ./vendor-documentation (for vendor supplied doc, TEXT files, PDFs, etc) ./user-documentation (for things that the shop wants to document like FAQs, installation notes, etc) This would also document any customization done to the product, such as exits. ./install-job-output (a separate file for each job run, something like:) ./install-job-output/install.dsn.member.run.1 the .1 would be incremented so that if a job is run multiple times, you can see the output from each successive job. So, do I need another vacation? -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
