Identifying and isolating unavailable System Automation resources

Use the Problem Isolation with INGWHY dashboard to identify and isolate resources that are not in the desired state.

1. In the navigation bar, click Administration > Explore Automation Domains.
   The dashboard opens with the automation domain and automation systems displayed in the Domains widget.
2. Right-click the automation system and select Properties....
   

   A dialog opens so you can view the detailed properties information.
3. Switch the tabs to view general properties, additional properties, and other statistics that are not displayed in the table.
   
4. Click Close to exit the properties dialog.
5. In the Resources widget, you can see all the resources on that domain and their state. Select an application group and hover the cursor over the group.
   You can view the detailed properties, of which the Observed State is not in the desired state in this sample scenario.
6. Click the icon +to expand the group.
   You can see the detailed state of the nested resources in this group.

   

   • The compound state of resource XWBSC1/APL/S0W1 is Warning because the observed state (Unavailable) is different from the desired state (Available).
   • A stop request, as indicated in the Operator Request column, is issued on resource XWBSC2/APL/S0W1 and thus its observed state is also Unavailable.
7. Right-click the group XWBSCAPG/APG/S0W1 and select Isolate Problem with INGWHY.
   The Problem Isolation with INGWHY dashboard opens and shows the analysis for the selected resource using the SA z/OS® operator command INGWHY.
8. Go through each widget to get more information for further diagnosis.
   • The Analyzed Resource widget shows detailed information about the analyzed resource.
   • The Causing Resources widget lists each dependent resource that is a cause for the current situation of the analyzed resource.
   • The Suggested Actions widget shows the identified reasons for the current problem and the suggested actions to solve it.
   • The Relationships widget displays the relationships to all resources from and to the selected resource.
   • The Requests widget displays the list of requests for the resource.
9. In the Suggested Actions widget, click the drop-down icon and select Maximize to maximize the widget.
   
10. Review the reason and suggested actions to identify the root cause and solution.
    • For resource XWBSC1/APL/S0W1, you need to check the captured messages and start the resource if needed.
    • For resource XWBSC2/APL/S0W1, you need to cancel the stop request if the resource is stopped by others.

    Tip: The suggested actions can also be customized based on your needs from IBM Z System Automation.
11. Click the drop-down icon and select Restore to restore the widget to the original size.
12. Return to the Explore Automation Domains dashboard, in the Domains widget, right-click the system and select View Captured Messages.
    

    From the Captured Messages dashboard, you can find the critical message indicating that the resource XWBSC1/APL/S0W1 needs start.