Since the DB2 warning messages are returned in the result set, AFMorphWarning processing is no longer needed. Also, the SQLWarning class is now in a different path com.ibm.db2.jcc.am.SqlWarning. The classes hard coded into the AFScriptContext, BaseScriptContext and ShellScriptContext call to AFMorphWarning are no longer valid so will also remove those.
|
139 KB
|
132 KB
|
108 KB
|
170 KB
|
188 KB
svn #53665
Hi QA Team,
Please create some warning scenario test cases and test DB2 LUW versions 8.1 to 11 and DB2 Z versions 10 and 11. Make sure that the warning messages are displayed correctly in ADS. See attached examples.
Thanks, Tom
z/OS servers are up and running. Please test and revert back
z/OS servers are up and running. Please test and revert back
Verified in ADS-19.0-beta-5. Refer screenshots for both databases. DB2LUW_Warning Message.png and ZOS_Waring message.png
Verified in ADS-19.0-beta-5. Refer screenshots for both databases. DB2LUW_Warning Message.png and ZOS_Waring message.png
Issue #15094 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build ADS 19.0.0-dev-5 |
No time estimate |
svn #53665
Hi QA Team,
Please create some warning scenario test cases and test DB2 LUW versions 8.1 to 11 and DB2 Z versions 10 and 11. Make sure that the warning messages are displayed correctly in ADS. See attached examples.
Thanks, Tom