The configuration refresh is asynchronous in both cases. Mark Haye (马克海), IBM TSM Server Development, [email protected], 8/321-4403, (520)799-4403, 0N6/9062-2, Tucson Professional programmer. Closed source. Do not attempt.
"ADSM: Dist Stor Manager" <[email protected]> wrote on 05/07/2012 13:20:27: > From: Thomas Denier <[email protected]> > To: [email protected] > Date: 05/07/2012 13:26 > Subject: [ADSM-L] Forced profile updates > Sent by: "ADSM: Dist Stor Manager" <[email protected]> > > We have a script used for scheduling backups. It defines a > schedule and then defines an association between the schedule > and a node. We recently started trying to use this script with > a TSM server that obtains policy domain definitions from a > configuration manager. The schedule has to be defined on the > configuration manager, and the updated policy domain has to > be replicated to the managed system before it is possible to > define the association. > > It is possible to force more or less immediate replication from > the configuration manager using the 'notify subscriber' command. > Based on the way errors are reported when the configuration > manager has trouble contacting managed servers, I am reasonably > sure the replication is asynchronous; completion of the 'notify > subscriber' command does not imply that the replication is > complete. > > It is also possible to force more or less immediate replication > from the managed server using a 'set configrefresh' command with > a non-zero interval. Does completion of this command imply that > replication is complete? I have not found any TSM documentation > that covers this point (an omission that is, unfortunately, > completely typical for TSM documentation).
