VM/370 - Environment Setup
This is a case study in setting up multiple VM/370 environments
The preferred system is the “SixPack” 1.3 Beta 3 Release. It has:
- Uploaded 19-Jun-2018
- Several update to RSCS and supporting programs added
- Node name in bottom of screen
- V310 of Diag 58 (327x Full Screen Support) and LDF
- Upgraded GNU-C compiler.
- WATFIV installed on “Y” disk. See the WATFIVUG LISTING U2 for usage.
- A new front end for Fortran G removing reference to a University system.
- Fortran H is now also available as “FortranH”
- See readme-1_3.txt for full details
Please refer to the information on G4UGM's Vintage Computer Pages for detailed information about the various VM/370 Pack offerings.
Also see New Users of Hercules Wanting a VM/CMS Environment by Greg Hartwig
Plan your working environment
This folder structure will encapsulate the isolated initial instance of the unloaded SixPack environment.
E:\EMULATION\VM370.6PACK.1.3.ORIG ├───batch ├───disks │ └───shadows ├───io └───WC3270 └───html
Next to the above structure - set up a working structure that defines a workspace in which new code can be developed and tested.
E:\EMULATION\OPERATIONS.WORKSPACE ├───Development ├───Documentation ├───Distributions ├───Reference ├───Tapes ├───Tapes.Export ├───VM.Tools └───_Sys.Utilities
Along with the distribution comes a “startup” batch file called
Because we will want to make modifications to, but retain original copies of the
configuration files - we need to instantiate a slightly improved working environment.
The “out of the box” setup looks like this:
Before doing anything else, read the following documents:
Read "What Mother Never Told You About VM Maintenance" by Melinda Varian is THE reference document, crucial to understanding why things work the way they do.
You may the proceed to Initial Startup