Falling back to DB2V9-NFM from a DB2V10 upgrade results in the following abend: ABEND=0C4-0000003B0c4 Module DT$DIIC9.
When going down from DB2 10 to DB2 V9, the Strobe SQL Agent finds that the PC runs in amode 64, and so incorrectly marks the new entry(DAB) for DB2 V9 as amode 64, which causes a S0C4-03B at the first and subsequent calls even if Strobe is not active.
As circumvention, STROBE parameter SSADB2HOOK needs to be set to N0 and contact Compuware for permanent solution.
SSADB2HOOK:Controls the method of SQL capture initiation. This value controls whether Strobe will install a Strobe DB2 SQL Intercept routine in DB2 to detect automatically the presence of SQL activity in applications being measured. The SQL Intercept code is implanted when the Strobe SQL Agent is initialized. If this keyword is not coded or the value specified is NO, the SQL Intercept code is not implanted in DB2 and a non-intrusive alternative method is used to detect the SQL activity. Valid values are YES and NO. The default is NO.