Steps For Automating Linux Virtual Consoles - IBM ZVM - FOR LINUX V6 RELEASE 1 Getting Started

Important: Once the programmable operator is running, do not log onto
OPERATOR except when necessary. If you do log on to OPERATOR, before you
can issue commands other than those that control the programmable operator, you
must issue the STOP command.

Steps for automating Linux virtual consoles

This task shows you how to send Linux virtual console
programmable operator. Because your Linux virtual servers typically run
disconnected, you do not see virtual console messages and thus do not know if
problems are occurring in the Linux virtual machines. Through this task, you send
virtual console messages to the programmable operator for handling. By modifying
the routing table, you can record incoming messages or forward important
messages to the real operator. Figure 9 shows how automating Linux virtual
consoles works.
Figure 9. Automating Linux virtual consoles
In the figure, each Linux virtual machine has the command CP SET SECUSER
OPERATOR in its PROFILE EXEC. The command defines the OPERATOR user ID
as a secondary console, meaning all virtual console messages are sent to OPERATOR.
Because OPERATOR is running the programmable operator facility, you can filter
messages coming from the Linux virtual machines. You can log the insignificant
messages for later reference and forward messages requiring special handling to a
real operator at LGLOPR.
By using the secondary console, you can also send messages to the Linux virtual
servers to do certain actions, such as attach a network interface (COUPLE
command), should a Linux failure be detected.
5. For a description of virtual consoles, see "Overview of console types" on page 97.
Linux
virtual
servers
CP SET SECUSER
OPERATOR
Virtual
console
5
OPERATOR
Programmable
Operator
Routing
Table
.
.
.
logon > log file
shutdown > LGLOPR
CP
Chapter 9. Setting up basic system automation
messages to the
LGLOPR
93