Database Analyzer U0500 abend module RALMBLD fatal error encountered

Products

• Database Analyzer for DB2 for z/OS
• Fast Unload for DB2 for z/OS
• Fast Check for DB2 for z/OS
• Fast Index for DB2 for z/OS
• Rapid Reorg for DB2 for z/OS

Issue/Introduction

CA Database Analyzer for Db2 for z/OS (PDA) Extract execution is abending with the following: 

USER COMPLETION CODE=0500 
PSW AT TIME OF ERROR 078D1000 9BC5A24C ILC 2 INTC 0D 
ACTIVE MODULE ADDRESS=00000000_1BC58000 OFFSET=0000224C 
NAME=RALMBLD 
DATA AT PSW 1BC5A246 - 00181610 0A0DD603 BA54BA54 
AR/GR 0: 001FFFFF/80000000 1: 00000000/800001F4 
2: 00000000/00000069 3: 00000000/1BC10C10 
4: 00000000/1BC01630 5: 00000000/00000000 
6: 00000000/0001D0D4 7: 00000000/00010EA0 
8: 00000000/00000000 9: 00000000/1BC10DD8 
A: 00000000/9BC5B008 B: 00000000/9BC5A008 
C: 00000000/9BC59008 D: 00000000/9BC58008 
E: 00000000/9BC5A208 F: 00000000/00000004 

IEF450I DBBQT8PL UTIL1 STEP01 - ABEND=S000 U0500 REASON=00000000 

> PDA PROFILE Fatal Abend option was set to YES. Entering debugging mode. < 

Extracting EXTRACT Procedure - xxx.yyyyyyyy 
No objects defined for the Extract Procedure. If it was created outside of the supported user interface then unpredictable results may occur. RC=4 Module: RALCBPB, Return code: 004, Reason code: 001 
Execution stopped - fatal error encounter - Reason Code 105 

Environment

Release:
Component: PDA

Resolution

The presence of the following mesage is related to the U0500 abend in RALMBLD: 

> PDA PROFILE Fatal Abend option was set to YES. Entering debugging mode. < 

The proven way to correct this would be to utilize the PDA panels to regenerate the control cards with the PDA Profile option set to Fatal Abend ==> NO. 

Steps:
 
1. Go into Database Analyzer option P User Profile and verify that Fatal Abend ==> NO is specified. 

2. Go into Database Analyzer option EP and use the (S)ubmit line command to generate the JCL for the Extract Procedure in question.