ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Apply Hiper Fix Apply RO87538 to avoid ENQ contention caused by custom AOM message screening exits

book

Article ID: 36881

calendar_today

Updated On:

Products

SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS SOLVE

Issue/Introduction

Problem:

If you use any custom AOM message screening exits that update the AOM Global Data Base (GDB) this can result in ENQ contention.

Environment:

SOLVE:Operations Automation 11.9
SOLVE:Operations Automation for CICS 11.9

Resolution:

1. Check all existing custom screening table exits for the GDB-Verb together with one of these parameters: ADD, PUT, UPDATE, or DELETE

2. If this is the case, please replace the GDB with the EVENT Verb or a mirrored vartable.

3. Apply RO87538 and review the HOLD doc for the PTF.

Environment

Release: SLOPEM00200-11.9-SOLVE:Operations-Automation
Component: