> The tech writers have lost their way. A Reference manual should specify syntax: how to code a command legally; and semantics: what that command does as coded. A Use's Gide should be task oriented: what command described in the <
I've been on both sides of the fence writing and as an end user. The perfect solution would be to have a link to "usage" from the command reference and vice versa. This is hard in PDF. It would tend to say "go and look in the usage book" (See below) With the knowledge centre conceptually there are no "books", so the cross linking should be easy. The table of contents is book based. I think MQ pubs are only KC, and you cannot easily get PDF documents. I doubt if there is the resource to put all the links in, but from the usage statistics per page in the KC, they should be able to find the hot pages and put links in there. An example from the KC *Note: This document provides some examples of how you can use BPXBATCH. For more detailed information about BPXBATCH, see the description of the BPXBATCH utility and the detailed discussion on using BPXBATCH to run executable files under MVS™ environments in z/OS UNIX System Services Command Reference <https://www.ibm.com/docs/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.bpxa500/toc.htm>.* This just gets me to *Table of Contents (exploded view) *in the command reference section rather than to the BPXBATCH command itself which would be easy to do. Both PDF and online KC have their good and bad points. Is there another option I have missed? Colin ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
