Sending Markers
Markers are synchronization flags that are sent to the destination server to trigger events or to run any executable file that can be run from a command line, for example Windows command files or scripts. Some common uses include: triggering a tape backup (incremental or full), housekeeping scripts or programs, and sending reports or email messages.
Data is automatically flushed before a marker is sent. When the destination server processes an AIM data transfer with a marker, the flag triggers the configured event or program file.
There are two types of markers. User defined markers can be created using a specified name; these markers are sent manually. AIM also provides a default marker, “AimMarker,” that can be sent automatically at specified intervals.
Sending markers is a two step process:
-
Configure the marker definition.
The actions performed via user-defined markers and ”AimMarker” must be defined on the destination server using AIM Destination Manager before they are sent. To define marker receipt actions, refer to Defining Marker Actions.
-
Send the marker.
Markers are sent from the source server using AIM Source Manager. There are four ways to send markers:
-
Manually (refer to Manually Sending User Defined Markers).
-
Automatically (refer to Automatically Sending Default Markers).
-
Scripting with a CLI (refer to Using AIM CLI Commands).
-
Sending markers for a group (refer to Sending Group User Defined Markers).
In AIM Source Manager, the Marker column displays the last command that was processed or pending for the AIM set. The letter “G” means that the command is related to a group, while the letter “S” means that the command is related to a single AIM set. The Marker column can be viewed in the Destination Status View or All View. Refer to Viewing AIM Source Manager Status for view details.