weblogs/oldcomputernerd.com
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

improve documentation for turnkey

Browse Source
This commit is contained in:
Greg Gauthier 2025-01-19 00:41:32 +00:00
parent 313029f51d
commit cfd2a671bc
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
md/MVS/entries/tk5-setup.md
View File

@ -349,8 +349,9 @@ I'm not going to go over the entire output. For that, you'll have to refer to th
4. The first 'system' entry is called `JES2`. That is your Job Entry System. It will ALWAYS be the very first task on a normal MVS system, because it controls the submission of ALL other work on the system. 4. The first 'system' entry is called `JES2`. That is your Job Entry System. It will ALWAYS be the very first task on a normal MVS system, because it controls the submission of ALL other work on the system.
5. `NET` is the task that provides MVS networking capabilities. This includes both SNA and TCPIP architectures. 5. `NET` is the task that provides MVS networking capabilities. This includes both SNA and TCPIP architectures.
6. I've forgotten what `TP` is, but `MF1` is the "Monitoring Facility". This task keeps track of all the the run statistics of both your base system, and of your "metered" jobs. Technically, you don't need to run this on the Turnkey system, since there's no real need to monitor run statistics, which would normally have been parsed up and sent in batches to IBM, and your accounting department. IBM would get the base statistics for the system. Your accounting department would figure up a cost for each department that matched it's usage of the system, and that cost would be billed to clients. 6. I've forgotten what `TP` is, but `MF1` is the "Monitoring Facility". This task keeps track of all the the run statistics of both your base system, and of your "metered" jobs. Technically, you don't need to run this on the Turnkey system, since there's no real need to monitor run statistics, which would normally have been parsed up and sent in batches to IBM, and your accounting department. IBM would get the base statistics for the system. Your accounting department would figure up a cost for each department that matched it's usage of the system, and that cost would be billed to clients.
7. `SNASOL` is shorthand for "System Network Architecture Solicitor". In short, it is a task that does nothing more than listen for terminals trying to connect to the system throught `NET`, intercept those connections, and present the terminal display with a logon splash screen, and user entry fields. 7. `TSO` is shorthand for "Time Sharing Option". TSO is essentially a "virtualization" environment that facilitates multi-tasking across many terminal sessions. The way it works, it gives the human users the "impression" of being on an interactive system, like PC DOS. Behind the curtains it doesn't really work that way, though. Suffice to say, this is where you will do most of your work, only not from the console, but from a terminal emulator.
8. I can't remember what `JRP` is. 8. `SNASOL` is shorthand for "System Network Architecture Solicitor". In short, it is a task that does nothing more than listen for terminals trying to connect to the system throught `NET`, intercept those connections, and present the terminal display with a logon splash screen, and user entry fields.
9. I can't remember what `JRP` is.
**JES2 Jobs** **JES2 Jobs**