Introduction to NonStop Operations Management

Operations Management Tools
Introduction to NonStop Operations Management–125507
14-4
$CMON
$CMON
$CMON is a user-written program that monitors some command-interpreter activities.
You can use $CMON to secure your system by auditing and restricting attempts to:
•
Log on and log off
•
Run a program
•
Alter the priority of a process
•
Add users to the system or delete users from the system
•
Change a user’s logon password and remote passwords
The International Tandem Users’ Group (ITUG) can supply you with a sample copy of
$CMON.
Command Files
A command file is a file that contains a series of commands. When the file is executed,
the commands within the file are automatically executed. Command files are supported
by TACL and many subsystems and interactive interfaces (such as FUP and
PATHCOM).
Command files are most useful for automating tasks that:
•
Require many commands and few decisions. For example, if operators must start
100 terminals every time they start an application, you can create a command file
that contains all the commands for starting the terminals and the application. When
it’s time to start the application, the operators can execute the command file instead
of entering all the commands themselves.
•
Are repetitive. For example, if operators must frequently check NonStop TM/MP
status, you can create a command file that contains all the appropriate NonStop
TM/MP status commands. With this command file, the operators check NonStop
TM/MP status with one command instead of several.
•
Can create serious problems if not executed properly. For example, system shutdown
and system startup can be complex tasks requiring many commands. If one of the
commands is entered incorrectly, a serious error can result. By creating command
files for system shutdown and startup, operators no longer have to worry about
incorrectly entering the commands; they simply execute the command file. To create
this type of command file, you should first carefully plan all the steps involved in the
task before creating the command files. After creating the files, you should test them
on a development system.
Table 14-2 lists typical command files and their functions. Use this table to help you
determine which tasks to automate in command files. Many Tandem manuals explain
how to create command files and provide examples of the files.