Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Troubleshooting

This troubleshooting information can help you diagnose some common Abend-AID installation problems.

ERROR: AA172: AB5B2- HOOK RELEASE = 17.02, IS INCOMPATIBLE WITH RELEASE = 12.04 OF #XAAINTR

Possible Causes:

  • AUTHLIBS in the SVC51 interface are at a different release level than the Abend-AID hlq.SPAALOAD library in the link list.
  • AUTHLIBS in the SVC51 interface are at a different release level than the Abend-AID libraries in the BDCAS started task.

Suggested Corrections:

  • Confirm that the libraries in the Abend-AID SVC51 started task are the same release as the Abend-AID hlq.SPAALOAD library in the link list.
  • Confirm that the libraries in the Abend-AID SVC51 started task are the same release as the libraries in the BDCAS started task.

ERROR: FDBRC1107S SUBTASK 7 FDBMSPLU ABENDED. SYSTEM COMPLETION CODE=X'047'

Possible Causes:

At dump capture processing, the TDCAS attempts to access the CSECT and load module information from the libraries in the DFHRPL. The external security package rejects the request of the ownerid of the TDCAS started task to read this information.

Suggested Corrections:

Do one of the following:

  • Add the DFHRPL_READ parameter and set it to NO.
  • Request that the z/OS security administrator authorize the ownerid of the TDCAS address space to read the load libraries during dump processing.

ERROR: AB536 BATCH CONSISTENCY MODULE: 12.04.00 / AB536 BDCAS CONSISTENCY MODULE: 17.02.00

Possible Causes:

This error is frequently seen on systems that have a previous release of batch Abend-AID installed, while you are testing the new release on the same system. Using the test option of the SVC51 hook enables you to test the new release. However, the existing Abend-AID environment directs you to the previous release's version of the BDCAS, resulting in this error.

Suggested Corrections:

As a workaround, insert a //AACWxxxx DD DUMMY statement into your batch JCL, where xxxx is the subsystem that the new release of BDCAS uses. The subsystem name is in the first step of the BDCAS started task.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*