Folks, There are a number of tools out there that can provide this capability. I have come across a number of them, including Docet from RES (www.res-it.com/en). For mainframe sites with DB2, it is an excellent tool for keeping documentation (among a plethora of other mainframe inventory and infrastructure information) at the fingertips of those who need it.
Regards, Mitch McCluhan, Legacy Modernization Consultant -----Original Message----- From: Duffy Nightingale, SSPI <[email protected]> To: IBM-MAIN <[email protected]> Sent: Wed, Feb 26, 2014 12:53 pm Subject: Re: Query for Destination z article -- identifying/overcoming mainframe challenges One thing I have run into at a couple of mainframe sites is they have had so uch turnover in tech support and no process for the ex person to train or eave the new person documentation that the current tech people (and same ith application folks) - seem to have no idea how things work! This robably applies to all mainframe staff positions. Sites need to have a rocess in place to save in documentation or spend a couple of weeks with he new person all the systemic information on apps, system software. uffy Nightingale ound Software Printing, Inc. [email protected] ww.soundsoftware.us hone: 360.385.3456 ax: 973.201.8921 The information in this e-mail, and any attachment therein, is onfidential and for use by the addressee only. If you are not the ntended recipient, please return the e-mail to the sender and delete t from your computer. Although Sound Software Printing, Inc. ttempts to sweep e-mail and attachments for viruses, it does not uarantee that either are virus-free and accepts no liability for any amage sustained as a result of viruses. -----Original Message----- rom: IBM Mainframe Discussion List [mailto:[email protected]] On ehalf Of Gabe Goldberg ent: Wednesday, February 26, 2014 7:44 AM o: [email protected] ubject: Query for Destination z article -- identifying/overcoming mainframe hallenges Challenges are everywhere -- doing more with fewer resources, maintaining ecurity, management/user sometimes willful ignorance of mainframe haracteristics and strengths, disrespect (different from gnorance!) for mainframe heritage and value, staffing (recruiting needed kills, generation-gap communication, needing to be Swiss-Army experts on iverse technologies/platforms), system maintenance, managing vendor ccounting and billing, capacity planning, performance analysis, etc. OK, that's enough -- and only part of the bad news. What other challenges re faced? And much more important, what's done (can be done, should be one) to overcome them all? As usual, be brief -- this will be a relatively short article. And please opy to me directly so replies aren't buried in digests. Thanks... -- abriel Goldberg, Computers and Publishing, Inc. [email protected] 401 Silver Maple Place, Falls Church, VA 22042 (703) 204-0433 inkedIn: http://www.linkedin.com/in/gabegold Twitter: GabeG0 ---------------------------------------------------------------------- or IBM-MAIN subscribe / signoff / archive access instructions, send email o [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- or IBM-MAIN subscribe / signoff / archive access instructions, end email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
