Defining INGWHY User Actions

You can use INGWHY to initially analyze a situation to find why a resource is desired to be available or unavailable, or why automation is unable to reach the desired status.

Besides analyzing potential reasons, automation also proposes actions that typically point to the commands that may be helpful for a more detailed analysis. Automation administrators might need to adapt or override these actions for various reasons.
  • The action depends on the installation (sandbox vs. production system).
  • The action depends on the resource (time critical vs. non-time-critical resource).
  • The action depends on the time of day (shift plans).
  • The action depends on whether a problem database including resource-specific actions already exists.
INGWHY reads the action text from the DSIPARM members INGWHYSA and INGWHYU.
  • Member INGWHYSA contains the proposed actions that are delivered with the product. This member must not be changed by users.
  • Member INGWHYU allows users to override actions that are defined in INGWHYSA.
INGWHY processes INGWHYU first. If INGWHY finds a matching action ID in member INGWHYU, it will not search for it again in member INGWHYSA.
Note: INGWHYSA and INGWHYU contain NetView Data REXX in logic mode. You can view these files by using the Browse command with the NOINCL option in NetView.