BMC AMI z/OS subsystem

This topic describes the BMC AMI z/OS subsystem.

Related topic

Getting-started

BMC AMI Datastream for z/OS enables its own subsystem. You can specify the name of the BMC AMI z/OS subsystem in the AMISSID parameter of the CZAGENT JCL procedure. Only one address space can use the name specified in AMISSID. If you start a second address space with the same name, that space does not become part of the active subsystem, but continues to function without a combined BMC AMI z/OS log output file.

To run more than one address space on the same LPAR, do not define a value for AMISSID, but let it use the default value. A subsystem ID is generated dynamically for each additional address space that is started. For more information, see Sample-CZAGENT-JCL-for-running-BMC-AMI-Datastream-as-a-started-task.

Important

You can use any character string for the AMISSID parameter, with the following conditions:

  • You must begin each string with a character, and not with a number.
  • We recommend 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). The subsystem automatically combines CZAPRINT and SYSTSPRT output. You can override the combined output by adding appropriate JCL statements to the JCL procedure. For example: 

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

 

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