OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM

OSI/FTAM Configuration and Management Manual—421944-001

3-48

Starting and Adding an Alternate Collector

All Tandem FTAM processes default to sending event messages to the primary collector,

$0. However, you can choose to have messages sent to an alternate collector, or to both

the primary collector and an alternate collector. This is determined by the value of

EVENTDESTINATION in the FTC PROFILE object.

Only one alternate collector (and, therefore, only one FTC profile) is allowed for each

Tandem FTAM subsystem. However, two or more Tandem FTAM subsystems may use

the same alternate collector.

You must start an alternate collector before you can add it to Tandem FTAM. To start

and add an alternate collector, follow these steps:

1. Create and start the alternate collector process by issuing an implicit TACL RUN

command using the object file named EMSACOLL. The following command

creates an alternate collector process named $ZFTC running in CPU 0 and a log file

named $SYSTEM.FTAMLOG on the same system as the APLMGR process.

EMSACOLL /NAME $ZFTC, NOWAIT, PRI 180, CPU 0/ &

BACKUP 1, LOGSUBVOL $SYSTEM.FTAMLOG, &

ROTATEFILES ON, EXT 100

2. Add the alternate collector to Tandem FTAM by adding an FTC profile using the

SCF ADD PROFILE command, as follows:

ADD PROFILE $APLMGR.#FTC, COLLECTOR $ZFTC, &

EVENTDESTINATION BOTH

The name specified for COLLECTOR must be the same as the name specified for

NAME in the RUN EMSACOLL command. This command adds an FTC profile that

directs event messages to both the primary collector ($0) and the alternate collector.

An FTC profile cannot be modified after it is added. To change an FTC profile, see

Changing and Deleting an FTC Profile

on page 3-55.