For the BCPii communication, you need to define the community name that you have chosen in your configuration of the Provisioning Manager; for details see Table 14. Note that the address and the network mask of the community name should specify the loopback device 127.0.0.1, 255.255.255.255, respectively. The community name must be authorized for read and write operations. The next step is to allow external programs remote operation using the API. You need to perform the definitions on the SE of each CPC that should be managed by the Provisioning Manager and all CPCs on which the Provisioning Manager can run. For more information about the configuration of an SE for API programs, see z/OS MVS Programming: Callable Services for High-Level Languages.