Provisioning-related alarms
You configure alarms on the Niagara Network Job Builder and Niagara Network Prototype View.
Alarm routing uses the alarm class specified in the
(source state) in the alarm console, which identifies the BatchJobService ORD as source (local:|station:|slot:/Services/BatchJobService).
Figure 3. A provisioning alarm is an alert with source as BatchJobService
The single alarm source of the BatchJobService applies to all provisioning-related alarms (alerts). This means that only one row is used in the alarm console for all provisioning alerts. Keep this in mind if there are multiple alerts. When you click Acknowledge on the row, you are acknowledging all provisioning alerts.
To see multiple provisioning alerts in the Alarm Details view for the BatchJobService, double-click the row.
Each provisioning alert includes a hyperlink 
for more detail. When you select (highlight) the alert and click the Hyperlink button, the view changes to either:
- Batch Job Log File View — For that job, in cases where the alert is raised for successful job completion.
- Batch Job Step Log File View — For a failed job step, in cases where the alert is raised for a job failure.
Figure 4. A Batch Job Step Log File View from the Hyperlink in the Alarm Console
If you disposed of a provisioning job before acknowledging an alarm it generated in the Alarm Console, and you click the Hyperlink button to view it from an associated Alarm Details view, the system advises, “Cannot Display Page.” This happens because disposing of a job removes the batch job log (.bjl) file and all batch job step log (.bjsl) files associated with the job. Therefore, acknowledge any related alarms (alerts) before disposing of provisioning jobs.