A fix is available
APAR status
Closed as program error.
Error description
On a DB2 V10 in CM8* after a fallback (DB2 was running in V10 NFM before returning to CM8), an SQLCODE -199 occurs when unloading from a view. DSNT408I SQLCODE = -199, ERROR: ILLEGAL USE OF KEYWORD FETCH. TOKEN ( . AT MICROSECONDS MICROSECOND SECONDS SECOND MINUTES MINUTE WAS EXPECTED DSNT418I SQLSTATE = 42601 SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNHPARS SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD = 2 0 0 -1 125 506 SQL DIAGNOSTIC INFO DSNT416I SQLERRD = X'00000002' X'00000000' X'00000000' X'FFFFFFFF' X'0000007D' X'000001FA' SQL DIAGNOSTIC INFORMATION INZU128E SYSTEM ERROR: DB2 CATALOG EXTRACTION FAILED When this SQLCODE occurs and when DB2 YES is also specified, processing continues as HPU switches to SQL mode. When DB2 NO was specified, HPU stops. This also occurs with all the other fallback modes: ENFM8*, CM9* and ENFM9*. PB11898
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 High Performance Unload. * **************************************************************** * PROBLEM DESCRIPTION: On a DB2 V10 in CM8* after a fallback * * (DB2 was running in V10 NFM before * * returning to CM8), an SQLCODE -199 * * occurs when unloading from a view. * * DSNT408I SQLCODE = -199, ERROR: * * ILLEGAL USE OF KEYWORD FETCH. TOKEN * * ( . AT MICROSECONDS MICROSECOND * * SECONDS SECOND MINUTES MINUTE WAS * * EXPECTED ) * * DSNT418I SQLSTATE = 42601 SQLSTATE * * RETURN CODE * * DSNT415I SQLERRP = DSNHPARS SQL * * PROCEDURE DETECTING ERROR * * DSNT416I SQLERRD = 2 0 0 -1 125 * * 506 SQL DIAGNOSTIC INFORMATION * * DSNT416I SQLERRD = X'00000002' * * X'00000000' X'00000000' X'FFFFFFFF' * * X'0000007D' X'000001FA' SQL * * DIAGNOSTIC INFORMATION * * INZU128E SYSTEM ERROR: DB2 CATALOG * * EXTRACTION FAILED * * When this SQLCODE occurs and when DB2 * * YES is also specified, processing * * continue as HPU switches to SQL mode. * * When DB2 NO was specified, HPU stops. * * This also occurs with all the other * * fallback modes: ENFM8*, CM9* and ENFM9* * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** The odb2, odb2ctrl, osysibm, oddldb2, odb2cmd, odb2x2, inzcat, inzctrlz, inzctrlh, inzquery, inzqryv8, inzhyacc and inzmsgs modules were fixed.
Problem conclusion
The odb2, odb2ctrl, osysibm, oddldb2, odb2cmd, odb2x2, inzcat, inzctrlz, inzctrlh, inzquery, inzqryv8, inzhyacc and inzmsgs modules were fixed.
Temporary fix
Comments
APAR Information
APAR number
PM86790
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-10
Closed date
2013-06-25
Last modified date
2013-07-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
INZUTILK
Fix information
Fixed component name
DB2 HI PERF UNL
Fixed component ID
5697F4400
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUUV","label":"IBM Db2 High Performance Unload for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 February 2021