Its funny that no one mentioned the most obvious place to keep documentation - printed in a 3 ring binder. Most of the procedures we need in operating our mainframe fit in one 2" binder. Certainly, any procedure that needs to be referenced when the system is down (IPL, SADump, Stand Alone Restore) should be available printed at the main operator station.
I like Ed's thoughts quoted below. Keep the documentation on the platform it belongs to. I know our programming department required all of their doc to be in Word. We keep all of our systems doc in PDSs in Script. I just realized I haven't posted for quite a while. It seems like traffic in general on IBM-Main has been a lot less in the last few months, although yesterday had more posts than usual as of late. Eric Bielefeld P&H Mining Equipment On Fri, 11 Nov 2005 00:37:58 -0800, Edward E. Jaffe <[EMAIL PROTECTED]> wrote: >How funny! Using this "reasoning", I should put all of my z/OS doc on >Windows and all of my Windows doc on z/OS. That way if either is down I >can use the other to read the doc (and hopefully get it back up). Do you >/really/ put your Windows doc on z/OS?? > >My Linux doc resides on Linux. My Windows doc resides on Windows. My Mac >OSX doc resides on Mac OSX. My OS/2 doc resides on OS/2. And -- believe >it or not -- my z/OS doc resides on z/OS. I consider the practice of >putting doc on an alternate platform to be inconvenient. And, in the >case of z/OS, I want to retain the option of reading the doc directly >from a TSO/E session. > >What do I do when my Windows desktop fails and I need to read the doc to >(for example) remember how to reboot into "Safe Mode"? I simply read the >doc from my laptop, also running Windows. And what do I do when (God >forbid) one of my z/OS images fails and I need to read the doc to (for >example) interpret a wait-state code or take a stand-alone dump? I >simply access the doc, either directly or through the Library Server for >z/OS web interface, via one of my *other* z/OS images in the same >parallel sysplex. After all, I'm allowed to have more than one. >Unplanned outages are precisely why we have concepts like >sysplex-enabled VIPA fail-over in the first place! Sheesh! > >.-----------------------------------------------------------------. >| Edward E. Jaffe | | >| Mgr, Research & Development | [EMAIL PROTECTED] | >| Phoenix Software International | Tel: (310) 338-0400 x318 | >| 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801 | >| Los Angeles, CA 90045 | http://www.phoenixsoftware.com | >'-----------------------------------------------------------------' > ---------------------------------------------------------------------- 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
