I create PDSE files under the HLQ.XXX.XXX... of the product and document there. If you want to play in Grok land...enjoy.
Daniel McLaughlin Z-Series Systems Programmer Information & Communications Technology Crawford & Company 4680 N. Royal Atlanta Tucker GA 30084 phone: 770-621-3256 fax: 770-621-3237 email: [EMAIL PROTECTED] web: www.crawfordandcompany.com IBM Mainframe Discussion List <[email protected]> wrote on 05/14/2008 09:35:10 AM: > "McKown, John" <[EMAIL PROTECTED]> > Sent by: IBM Mainframe Discussion List <[email protected]> > > 05/14/2008 09:35 AM > > Please respond to > IBM Mainframe Discussion List <[email protected]> > > To > > [email protected] > > cc > > Subject > > crazy thoughts - keeping product installation infomation > > ---------------------- Information from the mail header > ----------------------- > Sender: IBM Mainframe Discussion List <[email protected]> > Poster: "McKown, John" <[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 > > Best Overall Third-Party Claims Administrator - 2007 "Business Insurance" Readers Choice Awards Consider the environment before printing this message. This transmission is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is confidential, proprietary, privileged or otherwise exempt from disclosure. If you are not the named addressee, you are NOT authorized to read, print, retain, copy or disseminate this communication, its attachments or any part of them. If you have received this communication in error, please notify the sender immediately and delete this communication from all computers. This communication does not form any contractual obligation on behalf of the sender, the sender's employer, or the employer's parent company, affiliates or subsidiaries. ---------------------------------------------------------------------- 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
