Logicals You Need to Run WATCH
This chapter shows you the logicals WATCH uses and how to define them.
To use WATCH you must define several logicals. Here is a description of each logical that may be defined on your system for WATCH.
WATCH_CDU - This logical points to the [WATCH.CDU] directory. It is used to access the WATCH command definition table. WATCH_CDU is optional.
WATCH_COM - This logical points to the [WATCH.COM] directory. It is used to access WATCH DCL command procedures. WATCH_COM is optional.
WATCH_DAT - This logical points to the [WATCH.DAT] directory. It is used to access the data files, including the DISKNAMES.DAT file for the DISKS screen. WATCH_DAT is required and must be defined in the system logical table.
WATCH_DOC - This logical points to the [WATCH.DOC] directory. The help files are stored in this directory. WATCH_DOC is optional.
WATCH_EXE - This logical points to the [WATCH.EXE] directory. It is used to access the WATCH executables. It is required and must be defined in the system logical table. If you cannot access WATCH check to see that this logical is defined in the system table.
WATCH$ACTIVE - Define this logical to be YES in your process table before starting WATCH and only active processes will be displayed on the user screen.
Privileges You Need to Run Watch
This section describes the privileges WATCH requires to run. WATCH requires WORLD and CMKRNL privileges.
WATCH checks for the appropriate privileges and issues an error message if it doesn't have them.
It should be run out of a privileged account or be given privilege when it is installed.
NOTE: If you have ALTPRI, you can run WATCH at an elevated priority by specifing /PRIORITY=n, where n is the priority you wish to run at. If the /PRIORITY qualifier is not specified, WATCH will execute at priority 4.
The Priority WATCH Needs to Run
WATCH should be run at elevated priority to ensure accurate data collection. To run WATCH at an elevated priority, use the /PRIORITY=n qualifier, where 'n' is the desired priority, when you start it.
WATCH does not allow you to specify a priority higher than 15 because priorities 16 to 31, while valid, can cause conflicts with system processes. If the /PRIORITY qualifier is not specified, WATCH will run at priority 4.