Suspend requests/goals

Information about suspend goals is provided to the automation manager in the following way:
 1  OPERATOR
By the operator command INGSUSPD (see How Requests Become Goals). These requests are labeled with the originator INGSUSPD(USERID) in the INGVOTE command dialog.

For this type of goal, you cannot specify a priority because suspend goals cannot be conflicting. A resource is either suspended or not. Therefore, the default priority (01220000) is used for every suspend request.

Note:
  1. Because suspend goals always have the same source (INGSUSPD), a more recent suspend request will always overwrite an earlier one. Therefore, it is not possible to have two suspend requests on the same resource.
  2. The suspend goals are handled completely separately from the desired status goals. They are not conflicting in any case, so that it is possible to have start/stop requests and a suspend request on the same resource. The only specialty of the suspend requests is that the automation manager does not try to reach a desired status goal as long as the resource is suspended.