This will facilitate employee contributions during the writing process and allow easy access to information once the manual is in circulation.Include a table of contents that lists subsections.The harsher side to this reality is that the aren’t just retiring, they are expiring.(Short prayer for Jim Stanicki and John Stalher who were two exemplary mainframe developer friends of mine that died in the last few years.) Shouldn’t those old mainframe applications just be rewritten? Yeah, I know, you’ve heard about rewrites for years.A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. We take Uber, browse Pinterest, send tweets, and update Facebook.
Worse that that, many of those programs were written before modular programming techniques became available.
But the reason why most of those Visual Basic, d Base III, and PHP apps (that’s right, I’m saying they weren’t mainframe apps) were rewritten every 5 years is because they weren't written that well to begin with.
Meanwhile, the mainframe apps have been running well for decades. Rewrites are never easy and, for huge applications, they are often failures.
Have authors create the document using the same word-processing software.
Common software will not only make it easier to construct the manual now but it should also ensure the document can be easily modified in the future.