Skip to Content


Information
Limited support BMC 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.

Adding BMC AMI Defender for Db2 to your IPL procedures

You add BMC AMI Defender for Db2 to your standard IPL procedures so that it is not necessary to start it manually after every IPL. BMC AMI Defender for Db2 should be started after TCP/IP is operational. BMC AMI Defender for Db2 waits for TCP/IP to initialize unless OPTIONS NOTCPWAIT is specified (see OPTIONS-statement). BMC AMI Defender for Db2 outputs message CZA0247I to indicate that it is waiting; if you want you can terminate BMC AMI Defender for Db2 in this situation with the console STOP command.

You should choose a method of automatic startup that is suitable for your installation needs. Recommending a specific method is outside the scope of this manual. Some of the methods that might be appropriate to your installation include:

  • The COMMNDxx member of your SYS1.PARMLIB concatenation (see the IBM documentation).
  • A $VS command in your JESx initialization data set (commonly referred to as a JES init deck). See the IBM documentation.
  • The MPFLSTxx member of your SYS1.PARMLIB concatenation (see the IBM documentation).
  • The TCP/IP AUTOLOG facility (see the IBM documentation).
  • Your console automation system.

 

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

BMC AMI Defender for McAfee DAM 5.9