Checking BCP Internal Interface Interlocks

If applications that exploit the BCP Internal Interface, such as GDPS®, seem to hang or loop while a HW command or HW query is active, this may indicate that internal locks were not freed. Unconditional task interrupts during INGHWCMD processing or an unconditional task termination can cause such a situation.

You can use the LCHECK function of the IBM® Service command INGHWSRV to clear blocking locks. For more information about the service command, use the SA z/OS command HELP INGHWSRV.