If Resources Do Not Start

If you have attempt to start a subsystem and SA z/OS does not do it, there are some things you can check:

Use INGWHY command to initially analyze the situation to see possible reasons for the current state of the resource.
If INGWHY doesn't help, locate and examine the AOF313I message for the resource. This should clearly state why the startup request was rejected.
If there isn't a AOF313I message, search your netlog for more information.
Use the INGLKUP resource REQ=COLLECT command to collect diagnostic information about the resource from several SA z/OS commands (such as INGAMS, INGINFO, DISPMTR, DISPSTAT, and so on). You can also specify a data set for the output of the INGLKUP command. If you do not specify a data set, the output is written to the netlog.

Other issues to consider include:

Supporting resources are not up
If supporting resources are not up, SA z/OS tries to start them. If you wait for a short period of time they should come up and then the target subsystem will be started.

You can check on the state of the parents through the DISPTREE display, including status, or through messages issued to the Network Communications Control Facility (NCCF) console. If for example, it turns out that a parent is in a status of BROKEN, it is not possible to start the desired subsystem until this problem is fixed.
Automation flags are turned off
Automation flags may be turned off for the subsystem or for just the INITSTART or RESTART actions. If the INITSTART flag is turned off, the subsystem cannot be started from a DOWN status. If the RESTART flag is turned off, the subsystem cannot be started from a RESTART status.

To see the flag settings for a subsystem you can use either DISPFLGS or DISPINFO. DISPFLGS will show you both the current settings in force for the subsystem and, perhaps more importantly, the settings that were made that resulted in those values.
Trigger is not satisfied
Triggers tell SA z/OS when it is allowed to stop and start subsystems. If a trigger has been linked to a subsystem, SA z/OS will not stop or start that subsystem unless the trigger says it is OK to do so. Normally this function is fine, but there may be times when you need to override it.
To find out about the trigger linked to a subsystem, use the DISPTRG command. For example, the following command shows the triggers and events that are associated with the resource TEST0:
```
  DISPTRG TEST0,TARGET=KEY3
```
If you want to start something and override the event settings you can either issue an INGREQ REQ=START OVERRIDE=TRG command or with the INGREQ command, you can specify that trigger conditions should not be considered by specifying option Override ==> TRG in the INGREQ command dialog panel. If you want to ensure that the trigger is satisfied before you start the resource, you can set it with INGEVENT. INGEVENT can be used to set an event (but may affect more than just the subsystem you are dealing with).
The automation manager automation flag is off:
Use the INGINFO command or the INGLIST command to find out what the current setting is. If the automation flag is off, the automation manager will not send the order to start the subsystem to the automation agent.
The subsystem is suspended:
Use the INGINFO command or the INGLIST command to find out what the current status is. If the subsystem is suspended, the automation manager will not send the order to start the subsystem to the automation agent.

If you want to start a subsystem and override its suspend request, you can either issue an INGREQ REQ=START OVERRIDE=SUS command or specify option Override ==> SUS in the INGREQ command dialog panel to ignore the suspend requests.