An administrator can schedule one or more clients to process a command for one time action with the DEFINE CLIENTACTION command. The client node will process the command if the client scheduler is active. If the scheduling mode is set to prompted, the client processes the command immediately. If the scheduling mode is set to polling, the client processes the command at its prescribed time interval.
ADSM automatically defines a schedule and associates client nodes with the schedule. The schedule name and association information is returned to the server console or the administrative client with messages ANR2500I and ANR2510I. With the schedule name provided, you can later query or delete the schedule and associated nodes. The one time client action schedules are identified by a special character followed by numerals, for example @001.
For example, you can issue an incremental backup command for client node TOM in domain ENG. ADSM defines a schedule and associates client node TOM with the schedule, assigns the schedule priority 1, sets the duration as clientduration, the DURUNITS parameter as days, and the PERUNITS parameter to Onetime:
define clientaction tom domain=eng action=incremental
You can optionally include OPTIONS and OBJECTS parameters as allowed in the DEFINE SCHEDULE command.
You can determine how long the schedule remains active with the SET CLIENTACTDURATION command. This command allows the administrator to specify how many days the schedule, that was created with the DEFINE CLIENTACTION command, is active. After the specified number of days have elapsed, the schedule is automatically removed from the database whether the associated nodes have processed the schedule or not. The following example specifies that the schedule for the client action be active for 3 days:
set clientactduration 3