Missing Database Analyzer Action Condition members RAAACTB2 and RAAACTB3 from hlq.SRCLIB
search cancel

Missing Database Analyzer Action Condition members RAAACTB2 and RAAACTB3 from hlq.SRCLIB


Article ID: 53107


Updated On:


Database Analyzer for DB2 for z/OS


Successfully upgraded to new r12 Database Analyzer for Db2 for z/OS (PDA) and the pre-defined user-supplied conditions members RAAACTB2 and RAAACTB3
from the hlq.SRCLIB product library are missing, if not copying over the old libraries from previous installed version within the Post Install Process.


Since PDA release r12, the RAAACTB2 and RAAACTB3 members are removed from the hlq.SRCLIB, because of the new #INCLUDE statement.

A new #INCLUDE statement is now provided with Database Analyzer that lets you extend the predicates of existing action conditions and create customized
conditions without modifying Assembler source and building the RAAACTB2 or RAAACTB3 load modules. The latter functionality is being depreciated and is replaced by the #INCLUDEs.

The SQL statements (extended predicates and complete user customized conditions) are created in model members in the model libraries.

Note: The customized member can be put into any of the model libraries in your hlq.CDBAPARM(DSNAMEx).

Once created, you must specify a #INCLUDE statement in the Condition field on the Extract or Action Conditions panel, followed by the member name in which the custom SQL was created.
Database Analyzer reads the contents of the model library member used on the #INCLUDE statement during the condition evaluation and appends the user SQL to the end of the existing condition
(extending the predicate) or executes the complete custom user SQL statement (customizable SQL condition). In either case, the custom SQL is used in Database Analyzer processing to
determine whether an object has met the selection criteria. This enhancement makes adding action conditions and Real Time Object Selection (RTOS) criteria more flexible.