REAC3301 GDB ERRORs for DELETE KEY and PUT KEY.

Products

• SOLVE:Operations Automation

Issue/Introduction

SOLVE Operations Automation region is repeatedly issuing the following errors for DELETE KEY and PUT KEY. The KEY value changes, it is not the same key on each occasion

09.00.18.19 BG-AOM   N1G1AOMP REAC3301 GDB ERROR, ZFDBK 24 ON DELETE KEY=$RE00M
                              ASTAAWG-TSCCOMMON  21732951607685200SSEXPIRE
09.00.19.20 BG-AOM   N1G1AOMP REAC3301 GDB ERROR, ZFDBK 24 ON PUT KEY=$RE00MAST
                              AAWG-TSCCOMMON  21732951607685200SSEXPIRE
09.06.08.21 BG-AOM   N1G1AOMP REAC3301 GDB ERROR, ZFDBK 24 ON DELETE KEY=$RE00M
                              ASTAAWG-TSICOMMON  21732951607685200IEESYSAS
09.06.09.21 BG-AOM   N1G1AOMP REAC3301 GDB ERROR, ZFDBK 24 ON DELETE KEY=$RE00M
                              ASTAAWG-TSCCOMMON  21732951607685200IEESYSAS
09.06.10.22 BG-AOM   N1G1AOMP REAC3301 GDB ERROR, ZFDBK 24 ON PUT KEY=$RE00MAST
                              AAWG-TSCCOMMON  21732951607685200IEESYSAS

Environment

Release : 11.9

Resolution

Meaning of message code REAC3301 GDB ERROR DURING MESSAGE RULE PROCESSING. ZFDBK P1 ON P2 KEY=P3

Reason:

The P2 action was performed when a GDB error occurred.

The feedback code P1 indicates the nature of the error:

24 indicates that the request timed out while trying to get an exclusive ENQ on the GDB.

The key value P3 indicates which record was being actioned.

 

The FDBK=24 is an indication of an enqueue on the AOMGDB. This normally manifests itself as an enqueue on a system resource called NETMAGDB. The screening table code runs in the address space that issues the WTO that the screening table is processing. If that address space has "issues" e.g. it hangs while SOLVE/NetMaster code is in there and happens to have an ENQ on the GDB, that ENQ is held until the task ends.

The following commands can be used to determine the ENQ.

z/OS Console Command:

D GRS,C,E 

 

SOLVE/NetMaster Command:

sh aomstat=tuning

 

And also the following which will show all of the AOMGDB entries:

 

(1).. /XDB

(2)..Select Option ===> aomgdb    

(3)..Command ===> print

(4)..send the output to us.

 

If the ENQ cannot be determined the SOLVE/NetMaster region will need to be restarted.