Availability Guide for Change Management

Making Application Subsystem Changes Online
Availability Guide for Change Management–125506
4-7
NonStop TS/MP Changes You Can Perform Online
Increasing the Maximum Number of Objects Controlled by
PATHMON
Increasing the maximum number of objects controlled by PATHMON requires that you
shut down your transaction-processing application, make the necessary changes, then
cold start your PATHMON environment. You can avoid having to increase the number
of objects controlled by PATHMON by making sure that you select limits that allow
space for growth. For example, if you are not certain whether you might need an extra
TCP or server class, leave room for one or two more of these objects than you currently
need. However, be careful not to set unreasonably large limits because you may cause
PATHMON to waste disk space.
Changing the Owner and Security Attributes
Changing the owner and security attributes of your PATHMON environment requires
that you shut down your PATHMON environment, make the necessary changes, then
cold start your PATHMON environment.
Table 4-1. PATHMON Object Changes
Object must be stopped?
Type of change Object Yes No
Changing backup processors and dump files PATHMON
TCP*
X
X
Exchanging primary and backup processors PATHMON
TCP*
X
X
Deleting objects TCP*
TERM*
PROGRAM*
SERVER
X
X
X
X
Altering object attributes TCP*
TERM*
PROGRAM*
SERVER
X
X
X
X
* TCP, TERM, and PROGRAM are Pathway/TS objects managed by the PATHMON process. Pathway/TS is
discussed in “The Pathway Environment” subsection starting on page 4-25.