for your first question:
Running the chase command does not result in the automatic restart of jobs that are stuck in the STARTING state. Instead, chase writes a message to standard output that manual intervention might be required. Jobs that are stuck in the STARTING state are not be automatically restarted -- it is possible (for example, due to network problems) that the job might already have run, and its state was not yet communicated to the database. Verify the actual status of these jobs before you manually restart them.
for your second question: If you use the '-A' option it will send an alarm when it finds a job stuck ini starting, which you could then take action on.
The documentation has some more detail as well: https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-ae-and-workload-control-center/11-3-6-SP8/reference/ae-commands/maintain-system/chase-command-verify-job-starting-or-running-status.html