|
|
|
The manager automatically sends notifications to remote nodes when a dependency job either completes successfully or is deleted.
For example, suppose Job B on node LOCAL depends on Job A on node REMOTE. When job A runs successfully or is deleted, node REMOTE must notify node LOCAL. However, if node LOCAL is off the network due to communication failure, node REMOTE keeps trying to send notification to node LOCAL at a specified time interval. You set the time interval with this command.
When a node receives notification that a dependency job has been deleted on a remote node, the manager automatically removes the deleted job from all job dependency lists in the job database.
By default, the manager tries to send the notification every 15 minutes, for up to 2 days. To change the default expiration time, see the SCHEDULE SET NETWORK EXPIRATION_RETRY command.
The manager automatically places all retry notifications currently being attempted in the RETRY.DAT file. System managers can use the SCHEDULE SHOW NETWORK command to see this file’s contents. They can also stop all pending retry attempts by using the DELETE NSCHED$:RETRY.DAT; command.
By default, the manager automatically logs all attempted retry events in the NSCHED$:RETRY.LOG file. System managers can use the TYPE NSCHED$:RETRY.LOG command to review this historical file’s contents.
See the SCHEDULE SHOW NETWORK command for details on how to review this and other retry settings on your manager instance.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |