Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Datastream for Db2 7.1.

Restarting BMC AMI Defender for z/OS after an unrecoverable failure

BMC AMI Defender for z/OS generally shuts down in an orderly fashion after failures, including abends. If BMC AMI Defender fails to shut down properly, it attempts a warm start.

(SPE2101) BMC AMI Defender might also attempt a warm start if it detects that records are still being processed on the message queue during shutdown. A warm start attempts to recover and continue processing the records on the queue.

If BMC AMI Defender fails to shut down properly, you might receive the following message:

CZA0350I Instance name 'instanceName' is already in use by instance 0, attempting warm start

If the warm start fails, restart BMC AMI Defender using the INSTALL=FORCE parameter. For more information, see START-command.

Note

Before using INSTALL=FORCE, make sure that BMC AMI Defender is not still running. 

Do not alter the OPTIONS SUBSYS parameter between a non-orderly shutdown and a restart using the INSTALL=FORCE parameter.

To alter the SUBSYS parameter after an unexpected failure:

  1. Run CZAGENT INSTALL=FORCE.
  2. Shut down the product by using the STOP command.
  3. Modify the SUBSYS parameter parameter in the OPTIONS-statement.

Related topics

Troubleshooting

STOP-command


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*