TS/MP System Management Manual (H06.05+, J06.03+)

Managing the Pathsend Environment
HP NonStop TS/MP System Management Manual—541819-007
6-7
ACS Subsystem Core Processes
For more information about the commands listed in Table 6-2, see Section 10,
PATHCOM Operation Commands, Section 11, PATHMON Environment Control
Commands and Section 12, SERVER Commands.
If you have TS/MP 2.3 (or later version) installed on your system, you need to
configure and bring up the ACS subsystem processes using SCF commands. You
cannot start ACS subsystem processes with TACL RUN commands.
Process Names
ACS subsystem processes appear in PATHCOM displays in the form
L\system.$ZPnn, where nn is the number of the processor on which the ACS
subsystem processes reside. PATHCOM adds an “L” before the system name to
indicate that it is a link manager process, for example:
L\ABC.$ZP05
Table 6-3 lists the ACS core processes and their respective process names and object
names.
Initialization
Unlike the TS/MP 2.0 LINKMON process, the ACS subsystem core processes are
initialized as soon as they are started. The status of ACS core processes on each CPU
on the system is logged in the ACS subsystem log file. The ACS subsystem log file can
be set while configuring the ACS subsystem using the SCF commands.
Limits
The ACS subsystem provides higher Pathsend limits per CPU compared to the TS/MP
2.0 LINKMON process. For more information on ACS subsystem limits, see the TS/MP
Release Supplement.
Extended Memory
In TS/MP 2.3 and later versions, the operating system manages the extended memory
requirements of the ACS subsystem. Therefore, an external swap file is not required.
Table 6-3. ACS Core Processes
ACS Core
Process Process Name Object Name
DC ($ZACS) $SYSTEM.SYSnn.BC
PB ($ZPnn) $SYSTEM.SYSnn.PB
CS ($ZCSnn) $SYSTEM.SYSnn.CS
ROUT ($ZLnn) $SYSTEM.SYSnn.ROUT