A fix is available
APAR status
Closed as program error.
Error description
QMF needs a new message to issue to report DB2 SQLCODE -423 when selecting LOBs from a 3 part name table.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All QMF for TSO/CICS V8.1 and V9.1 users * * experiencing an SQL code -423 (SQLCODE423) * * when running QMF queries. * **************************************************************** * PROBLEM DESCRIPTION: Users running queries that produce an * * SQL code -423 (SQLCODE423) error * * situation from the database will * * receive the standard DB2 message text * * reporting the error situation. This * * APAR will map the SQL code -423 text to * * a QMF defined error message text in * * order to specifically address certain * * error conditions in which an SQL code * * -423 is expected and unavoidable in the * * QMF product. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a user runs a QMF SQL, QBE or prompted query containg a LOB data type column against a 3 part table name, an SQL code -423 error condition will occur. This error condition is due to the QMF design for retrieving LOB data types from the database. The current design will not work properly when retrieving LOB data type columns from a 3 part table name scenario. The current QMF design does properly retrieve LOB data types from locally connected databases or after CONNECTing to a remote database server. This APAR will add additional text to the QMF defined message for an SQL code -423 to add this QMF limitation information. Note that an SQL code -423 can occur for many reasons which will also be listed in the message text. This APAR does not fix any SQL code -423 errors, just improves the message text that reports the condition.
Problem conclusion
Three new messages are added to the QMF product to describe the DB2 for z/OS defined SQL code -423 error situations. These messages will include the error scenario of selecting LOB data type columns from 3 part table names through QMF. The new message numbers are MSGDSQ15423 (DSQ15423) for a QMF QBE query, MSGDSQ17423 (DSQ17423) for a QMF SQL query and MSGDSQ35423 (DSQ35423) for a QMF prompted query. All three messages will map to the following text: **************************************************************** The locator specified in position "&O1." is invalid. Position &O1 in the list of locator variables in the SQL statement contains a variable with an invalid value. The causes of this error depend on the type of locator variable: Result set locators Common causes of errors involving result set locators include: The host variable used as a result set locator was never assigned a valid result set locator value. Result set locator values are returned by the DESCRIBE PROCEDURE and ASSOCIATE LOCATORS statements. The SQL cursor might be closed. Result set locator values are valid only as long as the underlying SQL cursor is open. If a commit or rollback operation closes an SQL cursor, the result set locator associated with that cursor is no longer valid. LOB locators Common causes of errors involving LOB locators include: The host variable used as a LOB locator was never assgined a valid LOB value. A commit or rollback operation or an SQL FREE LOCATOR statement freed the locator. You tried to run a QMF query that uses a three-part name to reference a table that contains a LOB column. QMF does not support queries that use three-part names to reference tables that contain LOB data. To run queries that retrieve or manipulate LOB data at a remote server, first use the QMF CONNECT command to connect to the remote server, then run the query again. Table locators For a table locator, this error commonly occurs when the host variable that was used as a table locator was never assigned a valid table locator value. See the DB2 UDB for z/OS information in the following information center for additional details on locators: http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2
Temporary fix
Comments
APAR Information
APAR number
PK67718
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-06-17
Closed date
2008-07-22
Last modified date
2008-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK38359 UK38360
Modules/Macros
DSQCBRDI DSQCBRDX DSQCELTT DSQCEMSG DSQCRSNC DSQPNLE DXYE0762
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 August 2008