Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.
Space announcement To view the latest version of the product documentation, select the version from the Product version menu above the navigation pane.

Overview of HCI

DevEnterprise uses BMC AMI’s Host Communications Interface (HCI) to provide connectivity between the workstation and the mainframe, using TCP/IP as the communications protocol.

Workstation/mainframe connectivity

image2021-6-18_16-21-30.png
HCI is a component of Enterprise Common Components. See to the BMC AMI Enterprise Common Components Installation and Configuration Guide for more information about HCI.

The design of HCI is based on facilities available to z/OS operating systems. See to the software requirements for MVS host in the release notes for additional information.

  • HCI itself can be started as a started task or as a batch job.
  • HCI starts transaction programs (TPs) as started tasks or as batch jobs. 
    Started task transaction programs can also be set up with master scheduler JCL using the IEFJOBS DD concatenation of MSTJCLxx. See to the step detailing how to set up started task TPs with master JCL.
  • When using HCI, the HCI address space must be authorized by the Authorized Program Facility (APF). However, the application programs or the link-edited interface modules using HCI are not required to be APF-authorized. These are normal MVS non-authorized programs.

 

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