I think Chapter 5 should include DIRMAINT even though is not strictly a part of z/VM. It is common enough that it should at least be introduced as z/VM tools/components. PERFTK should be included in the Performance chapter. RACF should be introduced in the ESM discussion. Extended How-to/Best_Practices discussions can be in separate chapters/volumes. PROP and WAKEUP need to be in Chapter 6. Use of PERFTK as OPERATOR console processor can be added here too if there is anyone who has done more than the minimum configuration of it.RXSERVER as a VMUTIL server should be added to Chapter 11 as a must/should have tool.
/Tom Kern --- David Boyes <[EMAIL PROTECTED]> wrote: > As promised, I've posted my take on a book outline for new z/VM system > programmers. I'd appreciate comments and extensions to the topics (and > if people see sections they'd volunteer to write, I'd be thrilled). I > think a lot of the material will be reading the IBM stuff and casting it > into our own words, but we can also improve on same...8-) > > Note that the document is marked copyrighted by the VM Community Trust > -- this is simply to avoid one of the commercial publishers picking it > up and misusing it. I would intend this document to be owned by the VM > community and maintained by same (in the same vein as Melinda Varian's > classic "What Mother Never Told You About VM Service"). If we get > further with this, I'll set up a non-profit to hold the copyrights so > that it remains in the public trust. This was very successful for some > items on Usenet. > > The proposed outline is available at: > http://www.sinenomine.net/node/559. > > Comments are welcome, and should be posted to me and to the list. > > -- db > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
