Configuring BMC II for z/OS

This chapter describes how to implement the bidirectional communication between BMC Impact Manager cell and the BMC Impact Integration for z/OS Server through a TCP/IP connection. To establish a connection, you must have

• the z/OS TCP/IP product

• installed the MainView AutoOPERATOR product on z/OS

• at least one MainView AutoOPERATOR PAS with the BMC II for z/OS component active

• updated the BMC Impact Manager directory file (mcell.dir)

• installed the BMC Impact Integration for z/OS cell components

After the above requirements have been completed, you are ready to configure BMC Impact Integration for z/OS.

To configure BMC Impact Integration for z/OS, edit the sample JCL member, IIMSALC1, which allocates and initializes two files that are needed to connect BMC II for z/OS with BMC Impact Manager.

You must also edit one of the sample JCL members IIMSALC2, IIMSALC3, or IIMSALC4 depending on your site requirements for persistency queueing and detailed trace data collection.

Editing IIMSALC2 is preferred when persistency queueing and detailed trace data collection are required, and the job must be run once for each connection, including the server connection and all the clients.

Editing IIMSALC3 is preferred when neither persistent queuing nor detailed trace data are required and the configuration file can be shared by all BMC II for z/OS connections.

Editing IIMSALC4 is preferred when you want to collect detailed trace data, but persistence queuing is not required for the BMC II for z/OS connections.