Skip to Content

Adding BMC AMI Defender for z/OS to your IPL procedures

To avoid having to start BMC AMI Defender after every Initial Program Load (IPL), add BMC AMI Defender to your standard IPL procedures.

Before starting BMC AMI Defender, ensure that TCP/IP is operational. BMC AMI Defender waits for TCP/IP to initialize message CZA0247I unless you specified OPTIONS NOTCPWAIT. For more information, see OPTIONS-statement.

To terminate BMC AMI Defender, enter the STOP command in the console.

Information
Best practice

BMC recommends that you choose a suitable method of automatic startup.

You can schedule automatic startup using one of the following members, commands, or facilities:

  • The COMMNDxx member of your SYS1.PARMLIB concatenation. For more information, see the relevant IBM documentation.
  • A $VS command in your JESx initialization data set (also known as a JES init deck). For more information, see the relevant IBM documentation.
  • The MPFLSTxx member of your SYS1.PARMLIB. For more information, see the relevant IBM documentation.
  • The TCP/IP AUTOLOG facility. For more information, see the relevant IBM documentation.
  • Your console automation system.

Exiting BMC AMI Defender

BMC recommends that you prepare for the orderly shutdown of BMC AMI Defender during a z/OS shutdown or a re-IPL.

To shut down BMC AMI Defender, enter the STOP command before terminating TCP/IP.
If you run the STOP command after TCP/IP has already shut down or become unavailable, thenBMC AMI Defender terminates without waiting for TCP/IP.

Error
Warning

Do not shut down BMC AMI Defender except in an emergency, or before a z/OS shutdown or a re-IPL. If you restart BMC AMI Defender without an intervening IPL, you might have to use the FORCE parameter. For more information, see Restarting BMC AMI Defender for z/OS after an Unexpected Failure.

 

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

BMC AMI Defender for z/OS 6.0