The Queue Manager provides the option to requeue work in
the event that a UOW needs to be resubmitted.
Before you begin
Not all UOW types are requeueable. The following table provides
information on which work types can be requeued, and how the result
of a previous submission can have an effect on requeueing the UOWs.
Table 1. Work types that can be requeued
| Work Type |
Requeue on Success |
Requeue on Failure |
| Autodiscovery |
Yes |
Yes |
| Command Set |
Yes |
Yes |
| Configuration Change |
Yes |
Yes |
| Configuration Housekeeping |
No |
No |
| Configuration Synchronization |
Yes |
Yes |
| Import Configuration |
Yes |
Yes |
| Native Command Set |
Yes |
Yes |
| OS Upgrade |
No |
Yes |
| Remove Network Resource |
No |
Yes |
| Search Set |
Yes |
Yes |
| Work Housekeeping |
No |
No |
About this task
There are many reasons why a UOW might be requeued, for example,
UOW failure due to a network problem, or a failure in submission of
individual network resources. UOWs can be requeued on a one-off,
or recurring basis. UOWs with an execution status of Success, Finished,
Cancelled, or Expired may all be requeued. The following procedure
describes the steps to be taken to requeue a UOW
Procedure
- Within Queue Manager, right click on the UOW(s) required
and choose Requeue, or alternatively select from the menu bar.
- The Requeue Work wizard displays Page 1 of 2 Filter
Resources window. These are the options available for requeueing
the selected UOW against the network resources.
- The Requeue Work wizard displays Page 2 of 2 Filter
Resources window. Select the appropriate Failure category.
- The Configure Failure Options window
is displayed. Using the following table as a guide, enter the appropriate
information requested and click Next.
Table 2. Configure
Failure Options fields
| Field |
Definition |
| Ignore All Errors |
Indicates that the UOW is not to stop processing,
regardless of how many failures occur |
| Fail After X Total Errors |
Choose the maximum number of failures that should
occur before the UOW stops processing |
| Fail After X Percent Errors |
Choose the maximum percentage of failures that
should over before the UOW stops processing Select the maximum percentage
of failures you want to occur before the UOW stops processing. This
option is useful when there are a large number of command sets being
applied to a large number of resources. For example, if 51% is chosen,
and there are two command sets and five resources, the formula is
as follows: Max # of failures: (51/100) x (2x5) = 5.1 = 5 |
- The Password Override window is displayed.
To override the Netcool Configuration
Manager authentication, provide a login name and password. Click Next
to continue to the next window.
- TheExecution Priority window is displayed.
By default, all UOWs are submitted with a priority of Medium. Please
select the appropriate execution priority and select Next to continue.
- The Schedule Work window is displayed.
Select either immediate or scheduled execution. If scheduled execution
is chosen, additional fields are displayed prompting for the execution
window. Provide the start date/time, and end date/time for executing
the work. From this dialog, a recurring schedule can be specified
for the UOW. The recurring schedule is offered on a yearly/monthly/weekly/daily/hourly
basis. Click Next when this is complete.
- The Describe Work window is displayed.
Enter a description to identify the UOW, and click Next to finish.
Example
The sequence of windows displayed for requeueing of Work
can vary depending on the request type. For example the request type
“Run Autodiscovery” has a reduced number of windows as some are not
applicable.