Control-M/Assist implementation

This chapter includes the following topics:

Installing Control-M/Assist components

All software components described in Control-M/Assist main components (IOA, IOAGATE, Control-M Application Server, Control-M for z/OS, CMEM, and Control-M/Restart) must be installed on your z/OS environment. For a complete Control-M/Assist environment you should also have Control-M/EM installed and running in order to connect it to the Control-M/Assist components.

The installation process should follow the installation steps described in details in the INCONTROL for z/OS Installation Guide. This section guides the installation process of the Control-M/Assist components via the Installation and Customization Engine (ICE) and lists the steps that are mandatory and optional.

Administering Control-M/Assist components

This section includes some of the administration tasks that should be considered when using Control-M/Assist.

Control-M/Assist definitions maintenance

The customer must define Control-M scheduling definitions and CMEM rules in order to utilize Control-M/Assist abilities. For examples, see Sample implementation tasks

BMC recommends that users adopt a standard job naming convention that allows them to utilize existing generic Control-M and CMEM definitions or rules whenever changes or additions are made in the existing (third-party) job scheduling definitions. Otherwise, modifications in the Control-M/Assist environment are needed to reflect and synchronize these changes. A generic naming methodology will minimize the amount of maintenance necessary to properly maintain Control-M/Assist definitions.