This Db2 for z/OS News from the Lab blog entry was originally published on 2018-08-08.
By Paul McWilliams and Bruce McAlister.
In Db2 11 and Db2 12, APAR PI79053 introduced a new QUIET option for the TOLWARN parameter for the DSNTIAUL program. APAR PH00572 will soon introduce the same change for several similar applications, including SPUFI and the DSTNTEP2 and DSNTEP4 programs. When you specify the QUIET option for TOLWARN, the result is the same as YES, except that the programs suppress all SQL warnings for FETCH and OPEN statements if the SQLCODE is 0 or greater.
Before the introduction of this capability, some queries when processed with TOLWARN(YES) can cause the programs to print SQL warning messages after every FETCH. With multi-row fetch, millions of messages like the following examples can be issued and fill up the SYSPRINT file.
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
DSNT418I SQLSTATE = 01004 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSN SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 0 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000000' X'00000000' X'00000000' X'FFFFFFFF'
X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION
DSNT417I SQLWARN0-5 = W,W,,,, SQL WARNINGS
DSNT417I SQLWARN6-A = ,,,, SQL WARNINGS
The new QUIET option provides relief for users of these applications who complain about the 'noise' caused by such messages with TOLWARN(YES).
#Db2forz/OS#db2z/os#Db2Znews