Well, the Script plumbing allowed you to write a document that you could format differently for different contexts and audiences. I found it a great time saver.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf of Ian Worthington [00000c9b78d54aea-dmarc-requ...@listserv.uga.edu] Sent: Monday, November 15, 2021 10:38 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: z/Architecture Principles of Operation pdf I loved bookmaster back in the day (though the script underpinnings, not so much), never really found an adequate tool to replace it. Tried lyx for a bit and was finally persuaded to use latex, but it's still not as productive as bm was. Anyone know what IBM uses these days? Best wishes, Ian ... On Monday, November 15, 2021, 07:21:08 AM GMT-5, Seymour J Metz <sme...@gmu.edu> wrote: Back when IBM used BookMaster and BookManager BUILD (MVS or VM), it was trivial to write a manual that could be printed for different envirenments with message ids, etc., automatically tailored for the selected environment. I wish that they hadn't switched to WYSIAYG. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf of Paul Gilmartin [00000014e0e4a59b-dmarc-requ...@listserv.uga.edu] Sent: Sunday, November 14, 2021 6:02 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: z/Architecture Principles of Operation pdf On Nov 14, 2021, at 14:52:12, Charles Mills wrote: > > Well, not sure it's sensible but "z Architecture" is not a "feature of z/OS." > Yes, but still a hyperlink would be useful. > Yes, yes, of course, not very sensible. z/OS only runs on one type of > hardware, and any assembler developer interested in z/OS is interested in how > the hardware works. > Even less sensible is that SuperC comes with either ISPF or HLASM TK with separate manuals. The M&C differ largely in messages prefixes and degree of obsolescence. When I suggested in these lists that SuperC be made a single dependent FMID, applicable to either product, with a uniform component prefix, an IBM representative replied that Would be contrary to Company Policy.
