Table of Contents
Compiling The Nucleus Of AVM 3370 Mainframe
| Field | Systems programming |
| Went Obsolete | 1994 |
| Made Obsolete By | VM/ESA 2.x |
| Knowledge Assumed | Systems programming training |
| When useful | Fixing CP bugs, Dealing with odd configurations |
VM/370 required that the description of the system be entered in various systems definition files (DMKRIO for the I/O devices, DMKSYS for system memory and features, DMKSNT for shared segment (like shared libraries), DMKBOX for the logo being displayed before logging in), assembled and linked into a new nucleus (kernel).
Modern versions of VM use various mechanisms to automatically detect the configuration. Furthermore, the VM hypevisor (CP) can now read other non dynamic configuration items off of flat text disk files.
Re-linking the nucleus is STILL necessary when
- Fixing a bug in the code for the portions where source code is available
- When dealing with odd devices (those that do not report what type of devices they are)
