A fix is available
APAR status
Closed as program error.
Error description
DSQ10492 mapping to a SQL code +354 followed by DSQ10497 mapping to a SQL code +802 **************************************************************** DB2 error handling of MR fetch processing (ROWSET processing) can issue a SQL code +354 condition which can possibly indicate negative or positive SQL code errors during MR fetch (rowset) processing. The PK54846 design did not account for possible positive SQL codes and allow QMF processing to continue. .
Local fix
...
Problem summary
**************************************************************** * USERS AFFECTED: All QMF for TSO/CICS V8.1 and V9.1 users * * starting QMF with DSQSMRFI=YES (MR=YES). * **************************************************************** * PROBLEM DESCRIPTION: Users who have started QMF with the * * multi-row fetch feature enabled can * * experience the error message * * MSGDSQ10492 (DSQ10492) 'Database fetch * * error occurred while processing your * * command.' under invalid circumstances. * * The error message might appear when * * issuing the RUN QUERY or RUN PROC * * commands. * **************************************************************** * RECOMMENDATION: * **************************************************************** The QMF error message MSGDSQ10492 'Database fetch error occurred while processing your command.'was added with QMF APAR PK54846. This message is issued when QMF receives a SQLCODE354 (SQL code +354) during MR fetch (rowset fetch) processing. The SQL code +354, issued by DB2 for z/OS for MR fetch related problems, can indicate underlying positive (successful) and/or negative (unsuccessful) SQL codes for one or more rows of data in the rowset returned. The design added by PK54846 for SQL code +354 error reporting was to stop QMF fetch processing completely, retrieve underlying SQL codes reported by DB2 for the rowset, write them to the DSQDEBUG trace data set and issue the DSQ10492 to alert the user to the condition. But, if all of the underlying SQL codes for which the SQL code +354 condition was raised were positive SQL codes, the PK54846 design would make QMF stop processing invalidly as the current QMF design does not terminate processing on positive SQL codes. For the original query reported for this APAR, the query was run using QMF MR fetch and produced an SQL code +354 with underlying SQL code +802 errors. The query stopped running and ended in error with the DSQ10492 message. This same query, when run in single row fetch (MR=NO), ran successfully.
Problem conclusion
This fix will add new logic to retrieve all underlying SQL codes for which the SQL code +354 condition was raised. If any of the underlying SQL codes are negative, the DSQ10492 error message and original design of PK54846 will proceed. If all of the underlying SQL codes for which the SQL code +354 was raised are positive, the QMF command will proceed as normal so that single-row fetch and multi-row fetch behavior are consistent within QMF.
Temporary fix
Comments
APAR Information
APAR number
PK65110
Reported component name
QMF-QUERY MGMT
Reported component ID
566872101
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-04-28
Closed date
2008-05-12
Last modified date
2008-06-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK36420 UK36421
Modules/Macros
DSQEFSQ8 DSQESDGN DSQFFSQ8 DSQFSDGN DSQIFSQ8 DSQISDGN DXEDGN
Fix information
Fixed component name
QMF-QUERY MGMT
Fixed component ID
566872101
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCWRCK","label":"QMF for TSO\/CICS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
02 June 2008