TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
MF documentation can be extensive or it can be "not so much". I'm doing
a document set on a modest ISPF add-on productivity tool that has two
documents; Installation Guide (70pgs) and User's Guide and Reference
(235pgs). My plans are to add two more documents; Admin Maintenance and
Support, and a Command Guide.
OTOH, at the other end of the spectrum is the IBM document set, which
has a bazillion manuals.
I'd say that to estimate the number of documents, allocate 2-3 manuals
per tool (Install, User, Admin), plus a tech note, a What's New, and a
readme. I don't know if you use JCLs, but if so, maybe a document with
all the JCLs printed out.
Also, I don't know if an AS400 has different Oss. If your product is the
same on any AS400 OS, consider combining them. OTOH, if your product is
different (as ours is on two different Oss), keep them as individual
sets.
I recall a post to this list that delineated the document set
expected/desired in a mainframe environment. Various searches of the
Archives have failed to return this nugget of gold. Any advice?
