Command Reference Guide

Specifies the session(s) to which the abort message should be sent.

-abortsess

Specifies the abort session command.

-abortid{== | !=} application_id

Specifies the application identification.

-inhibit{* | 0 | minutes}

Specifies the number of minutes for Cell Manager backup inactivity, where *

means forever and 0 means activate now.

NOTE

The command can only be used in the cluster environment.

EXAMPLES

Following example illustrates how the omniclus command works.

1. Abort all running sessions

omniclus -clus cluster.domain.com -session * -abortsess

Note: On UNIX systems replace the * wildcard with '*' .

The utility will connect to all running sessions and will send them abort messages.

The state of the sessions can be then checked with the Application Recovery

Manager omnistat utility.

2. Abort specific running sessions

omniclus -clus cluster.domain.com -session mybackup

-abortsess

The utility will connect to backup session managers issuing abort messages and

sending them additional information - the backup specification name. Each

backup session manager checks whether the command addresses it and if this

is the case it aborts.

3. Abort sessions (all or specific) with application identifications

omniclus -clus obvs.hermes.com -session * -abortsess

-abortid != 10

Note: On UNIX systems replace the * wildcard with '*'.

This way the user can define groups of sessions and abort only the ones that

are actually related to the application that failed over. For example a backup

session that performs a normal filesystem backup of a remote client is not aborted