Schedule Association

Summary

TSM schedules exist independant of any particular node; in order to cause a node to participate in a schedule, you must 'associate' the node and the schedule. This document discusses generating that association, between a schedule 'MY-SCHED' (definition example for which available elsewhere and a node 'MY-NODE', definition example for which available elsewhere.

Summary

TSM schedules exist independant of any particular node; in order to cause a node to participate in a schedule, you must 'associate' the node and the schedule. This document discusses generating that association, between a schedule 'MY-SCHED' (definition example for which available elsewhere and a node 'MY-NODE', definition example for which available elsewhere.

Definitions

For this procedure, the following definitions apply:

MY-DOM

Your policy domain. For most local admins, there is only one.

MY-NODE

The name of the node you wish to define.

SERVER

The TSM Server instance you are planning to use. For most local admins, the server in question is 'ext'. See the system structure document if you're unsure.

MY-SCHED

The schedule to which you wish to attach your node.

Procedure 1. Definition of a TSM schedule association (command line)

  • Define the schedule

    Having connected to the correct SERVER, use the define association command:

    The following listing includes the continuation character '-', which indicates that the succeeding line is part of the same command, not a new command. Groups of these lines may be copied and pasted as a set.

     

      DEFine ASSOCiation  MY-DOM MY-SCHED MY-NODE [,more nodes] 

    The opposite process is similar:

      DELETE ASSOCiation  MY-DOM MY-SCHED MY-NODE [,more nodes]