JR64302: IBM RPA "BLOCK RESOURCE" AND "BLOCK SEMAPHORE" COMMAND DOES NOT HOLD THE LOCK DURING THE EXECUTION INSIDE THE CRITICAL REGION

APAR status

• Closed as program error.

Error description

• When using "Block Resource" or "Block Semaphore" the bot should
  hold the lock until the end of the execution of the code in the
  critical region, i.e., the code between the Block Command and
  the Unlock Feature.
  In some cases, when the Block command is executed, the lock is
  released right away or shortly after.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * On Premises user using semaphore with local memory           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Semaphore wasn't respecting the client count, it wasn't      *
  * working for multiple clients. This behavior worked correctly *
  * for Redis semaphore, so it was only fixed for Local memory   *
  * semaphore.                                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Use Redis semaphore.                                         *
  ****************************************************************
  

Problem conclusion

• A fix was delivered on 21.0.3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RPA

• Fixed component ID

  5737N5100

Applicable component levels