JR61593: GROUP MEMBERSHIP IN A PARENT GROUP MIGHT NOT BE REMOVED WHEN AN INTERNAL GROUP IN A CHAIN OF NESTED GROUPS IS DELETED

workflow.19003.delta.repository

APAR status

• Closed as program error.

Error description

• Group membership of users or groups might not be removed when an
  internal group is deleted in a long chain of group membership,
  such as when an internal group is member of an internal group,
  which in turn is member of an internal group. Another example of
   when this issue occurs is when a chain of a team includes an
  internal group that includes a security group.
  
  When you delete the nested internal group in the middle of a
  nested group chain, not all group memberships might be removed
  as intended. Therefore, a group membership might still be
  reported for a user or group after the chain of nested groups is
  cut by removing an internal group in the middle. The database
  needs to be updated with SQL statements. Contact IBM Support for
  assistance
  

Local fix

• To remove nested group dependencies of internal groups, cut the
  group membership in the Process Admin Console by selecting >
  Server Admin > User Management > Group Management, searching for
   the internal group you want to work on and removing the groups
  and users from the internal group.
  
  When you delete the nested internal group in the middle of a
  nested group chain, not all group memberships might be removed
  as intended. Therefore, a group membership might still be
  reported for a user or group after the chain of nested groups is
   cut by removing an internal group in the middle. The database
  needs to be updated with SQL statements. Contact IBM Support for
   assistance
  

Problem summary

• Deleting a nested internal group from the
  LSW_GRP_GRP_MEM_EXPLODED_XREF  doesn't work properly for groups
  that are in the middle of a dependency chain. All entries where
  the respective internal group is the parent (CONTAINER_ID) or
  child (GROUP_ID) in the LSW_GRP_GRP_MEM_EXPLODED_XREF are
  removed properly, but entries where the respective internal
  group is in the middle of the dependency chain (MEM_PATH) are
  not removed. As a result, a "grandchild" group remains member of
   a "grandparent" group when a parent internal group is deleted.
  This group membership can't be deleted later, but the
  LSW_GRP_GRP_MEM_EXPLODED_XREF table must be corrected.
  

Problem conclusion

• A fix that ensures deleting a nested internal group removes all
  dependencies will be available in a future release of Business
  Automation Workflow.
  

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

  BUS AUTO WORKFL

• Fixed component ID

  5737H4100

Applicable component levels