BMC AMI z/OS subsystem

BMC AMI Defender for z/OS dynamically enables its own subsystem. The BMC AMI z/OS subsystem name is specified in the AMISSID parameter of the CZAGENT JCL procedure.

You can use any four-character, alphanumeric (A–Z or 0–9) string as the BMC AMI z/OS subsystem name. Use the AMISSID parameter in the sample CZAMIOPS JCL to specify the subsystem name. If you do not specify a name, the default CZAO is used. For more information, see Sample-CZAMIOPS-JCL-for-running-BMC-AMI-Datastream-for-Ops-as-a-started-task.

Important

While SPE2101 allows you to use any character string:

  • You must begin each string with a character, not a number.
  • BMC recommends that you use CZA as a prefix for the subsystem name. The CZA prefix has been registered with IBM and is therefore restricted for use by BMC only.

You can use the BMC AMI z/OS subsystem to combine output from multiple sources and send it to the BMC AMI z/OS log output file (CZAZOSLG). CZAPRINT and SYSTSPRT output are combined automatically by the subsystem. You can override combined output by adding appropriate JCL statements to the JCL procedure. For example: 

//CZAPRINT DD SYSOUT=&$SOUT
//SYSTSPRT DD SYSOUT=&$SOUT


Important

Only one address space can use the name specified in AMISSID. If you start a second address space using the same name it does not become part of the active subsystem. It continues to function without a combined BMC AMI z/OS log output file.

Related topic

Getting-started


 

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