Technical Blog Post
DFHUS0002 A severe error (code X'030C') has occurred in module DFHUSAD
There are many different reasons why you might get a DFHUS0002 abend. For this blog's purpose we will address one specific case, a DFHUS0002 with 030C that I recently worked on.
The DFHUS0002 030C occurs because the USD1 directory Domain entry could not be found on a DELETE Entry request.
In this instance of the problem CICS is trying to delete a USD1 entry from the Directory Domain and the entry is not being found due to the USUDB entry, used to build the key, being corrupted:
DD 0202 DDDI EXIT - FUNCTION(DELETE_ENTRY) RESPONSE(EXCEPTION) REASON(NOT_FOUND) DATA_TOKEN(00000010 , 00000000)
US 030C USAD *EXC* - User-not-in-directory - FUNCTION(DELETE_USER) SIGNOFF_TYPE(USER_SIGN_OFF) DELETE_IMMEDIATE(YES) USER_TOKEN(00000536)
The trace shows the key being looked for is as follows. Notice the userid is just the x'5C' (asterisk) followed by spaces (userid begins at offset zero). So only one byte long:
5C404040 40404040 4040D5D6 40000000 00000000 00000001 00000000 00000000
The key, to search DD Domain with, is built using the USUDB entry which is located at 00000010:
Note 00000030 has 5C604E40 which is *-+ which should be the USERID:
00000010 00000536 00000000 30A5DBB0 00000536 | .........v...... |
00000020 00000000 00000000 7F22D240 001E3001 | ........".K .... |
00000030 5C604E40 40404040 40400000 00000000 | *-+ ...... |
Notice the x'01' located at offset x'1F' (starting from address 00000010 in the display above). This is the length of the userid.
The ACEE address contained within the USUD+X'18' entry is 7F22D240. If you go there in the dump you can see the following:
7F22D240 C1C3C5C5 FF000218 03000000 00000000 | ACEE............ |
7F22D250 00000000 015C0000 00000000 00000000 | .....*......... |
7F22D260 40404040 40400100 0014173F 00000000 | .......... |
Note the length byte is x'01' located at 7F22D254 followed by x'5C' (asterisk).
The problem is due to not being able to find the key used to search the US Domain USD1 entries. The key is built correctly based on the information found. However, the userid appears to not be correct within the ACEE (1 byte of asterisk). In this case, the problem is addressed by CA Top Secret fix RO66585 from CA Technologies. Since I originally wrote this back in 2014, I imagine you have this fix on your system y now but I'm hoping the my diagnostics will help you if you run into a similar problem.
This for taking the time to view this blog entry. As always DO IT JUST FOR CICS!!!