Hercules/390

the New Users Documentation Effort.
Hercules S/370 and ESA/390 Emulator 
[ Join Now | Ring Hub | Random | << Prev | Next >> ] 

(c) 2000 - Cory Hamasaki, with these modifications. I grant the Hercules/390 project permission to include these pages in electronic and print distributions. The original authors retain the right to produce derivative works of their writings and the right to republish their works included in this documentation effort. Neither myself, Hercules/390, nor the original authors restrict each other's rights in any way. All other commercial use of these documents is prohibited.

Private use and usage covered under the Fair Use Doctrine is encouraged even if you receive compensation. An example is using the docs to teach a seminar or class and charging a fee. In this case, you must include an attribution to Hercules, the Hercules Documentation Project, and the individual authors (this table of contents is adequate attribution.)
 


The documentation project started July 2000.  (Authors, If you're not listed below, please drop me another note.  Like most mainframers, I'm working two or three jobs and misplace notes and my todo list.)

Update 1/4/2002 - Authors, if I haven't updated the link or if you have a suggestion, drop me a note, HHResCo@ATTGlobal.net

Anyone want to take a stab at writing a CGI or Spyder to collect the documentation into a consolidated file? Have at it.


1. Primary Topics:
2) Non Install Topics
3)  Advanced Topics
I'll write what I can on the areas that I have some knowledge but primarily, I'll collect the work of others as web pages. I have some storage on a fast server so I'll host some of the text and link to existing pages too.

This effort depends on contributions. Roger, Jay, Jan, and the others working on the code should not be expected to research and write dissertations on HASP II, printers, or whatever. Hopefully they will comment and provide feedback but this is a grass-roots project.

Writing Guide
for
the Hercules New User Documentation Effort
  1. You know how IBM writes? Don't do that.
  2. Don't worry if you're not *exactly* correct. Show how to do it.
  3. Don't attempt to be complete. Provide a starting point.
  4. Write as ASCII text for email. I envision using the <pre> and </pre>

    5. tags on the web version.
  5. If you're not an expert, write it anyway.
  6. Pass completed writing contributions through the list (until someone complains, then we'll split off as the Nubie sublist.) If you have a website, put the doc there and I'll link to it.
  7. If you wish to correct a contribution, email it to the original author for revision. Do this collaboration off the list.
  8. Pick a topic, announce your intention to the list (so that no one else will start work on the topic.)
  9. Aim for about 2 typewritten pages on a topic. Each needs about 200 pages for proper treatment but hey, we all have other duties.
  10. Have fun. When you complete your assignment, we'll have a virtual round of drinks in this cyber-saloon.
  11. The current target is MVT. This effort should build on Rick's MVT project, provide a Hercules spin.
  12. Some knowledge of software, programming, and systems is assumed but an intelligent person who is not an S/390 or Unix expert should be able to install, configure, IPL, and run a job on MVT.
  13. Let's add MVS topics!!!
  14. I'll maintain this page listing you as the author and your co-authors. I've written a copyright notice that gives Roger and the Hercules project reprint rights but reserves to you non-exclusive rights to publish your material for a fee. If you want to sell your chapter to naSPA (which I doubt will happen) you can. If Roger or the Hercules project wants to include your text in a future CD distribution, they can, as long as they credit you.
  15. Anyone who doesn't like these rules is sentenced to write *two* chapters.
Who's with me? I'd like volunteers in two weeks and completed assignments in two months. -Snap- sound of whip cracking.

As an author, you're now a NUDE'ist.