System Administration

Caution

If you installed MVS-TK5 per the instructions, The System should be up and running in daemon_mode.

A lot of the tasks done by the System Administrator will need to use the Hercules/MVS console which is not available in daemon_mode.

I have no doubt that there are real System Administrators and/or System Programmers who will read through this tutorial and think, “What… Why do you keep shutting down and re-IPLing the system?”

My goal is to get a System running in a “state more similar” to a “real world system” for an “Application Programmer”.

An “Application Programmer” doesn’t need access to the Hercules/MVS console.

They just use a 3270 Terminal or one of the newer methods of creating and running programs (VSCode + Zowe, use ncat or rje80 or IND$FILE, etc.) to access the System.

Once all the tasks are done, running the System in daemon_mode will be the norm.

So, this presents a problem.

To perform these tasks:

• Read the entire task to see if:

  • The console is not required and/or
  • changes need to/can be made while the System is running.

  If so,

  • Need to login to MVS-TK5 as HERC01 as this userid has permissions to do anything.
  • Make the changes.

  Else:

  • Shutdown the MVS-TK5 system.
  • Run the set_console_mode script.
  • Make any changes that need to/can be made while the system is not running.
  • Manually IPL the system.
  • Need to login to MVS-TK5 as HERC01 as this userid has permissions to do anything.

Also remember: When done updating and changing things:

• Shutdown the MVS-TK5 system.
• Run the set_daemon_mode script.
• Re-boot the RPi so the systemctl mvs.service starts up the MVS-TK5 system.