BCPii address space does not start up at IPL

If the HWIBCPii address space is not active after an IPL has been done, look for HWI* messages in the system log. Most of the time, these messages pinpoint the reason for the failure of BCPii to become active.

In most cases, the address space did not start for one of two main reasons:

The support element that controls the CPC that contains the image of z/OS on which BCPii is being started has the improper configuration. Make sure all the steps have been followed in Setting up connectivity to the support element.
The community name of the local CPC is either not defined in the security product or contains an incorrect value. This is accompanied by message HWI022I (when the value defined in the security product is incorrect). See Community name defined in the security product for each CPC for detailed information.

When these problems have been corrected, restart the BCPii address space. See Restarting the HWIBCPii address space for more information.