Request for a parameter in DB2 z/OS equivalent to the parameter IGNOREWARNINGS available in DB2 LUW into db2cli.ini file.

An SQL stmt accessing DB2 z/OS 10.1, via ODBC, receives a code +354; such a code produces an error inside the application.
The following is the SQL stmt that reproduces the problem, run via a bach job accessing DB2 via ODBC:
printf("DSN8OIVP SQLExecDirect\n");
strcpy((char *)sqlstmt,"SELECT COALESCE(SUM(LIMIT_USE_AMT),0) AS ");
strcat((char *)sqlstmt,"CRAC FROM FSX.VFSX060_LIMUTL WHERE ");
strcat((char *)sqlstmt,"CASH_ACC_TECH_ID IN(SELECT CSHACCNTTECHID ");
strcat((char *)sqlstmt,"FROM IST.VICADLU_CASHACCLISTU2A WHERE ");
strcat((char *)sqlstmt,"CSHACCNTNUMBER=");
strcat((char *)sqlstmt,"'2 ' AND ");
strcat((char *)sqlstmt,"CSHACCNTDELETIONSTATUS='ACTV') ");
strcat((char *)sqlstmt,"AND LIMIT_TYPE='ACOL' ");
strcat((char *)sqlstmt,"UNION SELECT 0 AS CRAC FROM ");
strcat((char *)sqlstmt,"SYSIBM.SYSDUMMY1 AS TB1");
printf("DSN8OIVP sqlstmt=%s\r",sqlstmt);
rc=SQLExecDirect(hstmt,sqlstmt,SQL_NTS);
if( rc ]= SQL_SUCCESS ) goto dberror;
printf("DSN8OIVP successfully issued a SQLExecDirect\n");

The output of such sql stmt is the following:
DSN8OIVP INITIALIZATION
DSN8OIVP SQLAllocEnv
DSN8OIVP-henv=1
DSN8OIVP SQLAllocConnect
DSN8OIVP-hdbc=1
DSN8OIVP SQLConnect
DSN8OIVP successfully issued a SQLconnect
DSN8OIVP SQLAllocStmt
DSN8OIVP hstmt=1
DSN8OIVP successfully issued a SQLAllocStmt
DSN8OIVP SQLExecDirect
DSN8OIVP sqlstmt=SELECT COALESCE(SUM(LIMIT_USE_AMT),0) AS CRAC FROM FSX.VFSX060_
ID FROM IST.VICADLU_CASHACCLISTU2A WHERE CSHACCNTNUMBER='2
LIMIT_TYPE='ACOL'
DSN8OIVP successfully issued a SQLExecDirect
DSN8OIVP SQLFetch
DSN8OIVP entry dberror rtn
DSN8OIVP rc=1
DSN8OIVP entry check_error rtn
DSN8OIVP check_error> SQL_SUCCESS_WITH_INFO
DSN8OIVP SQLError Information
DSN8OIVP SQLSTATE : 01668
DSN8OIVP Native Error Code : 354
DSN8OIVP Error message text:
{DB2 FOR OS/390}{ODBC DRIVER}{DSN10015} ERRLOC=1:13:2
DSN8OIVP SQLGetSQLCA
DSN8OIVP entry prt_sqlca rtn
DSN8OIVP SQLSTATE ... 01668SELECT COALESCE(SUM(LIMIT_USE_AMT),0) AS CRAC FROM FS
HACCNTTECHID FROM IST.VICADLU_CASHACCLISTU2A WHERE CSHACCNTNUMBER='2
CTV') AND LIMIT_TYPE='ACOL' DSN8OIVP exit prt_sqlca rtn
DSN8OIVP exit check_error rtn
DSN8OIVP dberror: environment cleanup attempt
DSN8OIVP dberror: cleanup SQLFreeEnv
DSN8OIVP dberror: cleanup SQLFreeEnv rc =-1
DSN8OIVP dberror: setting error rc=12
DSN8OIVP pgmend: Ending sample
DSN8OIVP***************************
DSN8OIVP Execution FAILED
DSN8OIVP rc =12

So, the +354 is translated bu DSN8OIVP in a real error code (RC=12) that stops the application.
In DB2 LUW it is possible to introduce into the db2cli.ini configuration file a parameter, IGNOREWARNINGS, that lets to instruct DB2 to ignore +354 warning so that the application can continue the execution.

We need a similar parameter in DB2 z/OS too.