Subscribe to this APAR
By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.
APAR (Authorized Program Analysis Report) |
Abstract
OSP-DB-SMAPP-SAP400-THREADS-INCORROUT RUNNING THE INAV GENERATE
SQL FUNCTION, THE OUTPUT IS MISSING ONE DOUBLE QUOTE ' " '.
Error Description
The iNav Generate SQL function is not producing correct output.
The output is missing one double quote ' " '.
Problem Summary
The iNav Generate SQL function is not producing correct output.
The output is missing one double quote ' " '.
Problem Conclusion
The file itself had an incorrect long column name. When a
DDS-created logical file is built over a file with a long column
name, by default, the logical file gets that long column name as
well if the column is specified in the DDS. If the long column
name was longer than 30, DD incorrectly truncated the long name
to 30 characters resulting in a name that was invalid.
DD will now preserve the entire long column name rather than
truncating it to 30.
Temporary Fix
Comments
Circumvention
PTFs Available
Affected Modules
Affected Publications
Summary Information
Status............................................ | CLOSED PER |
HIPER........................................... | No |
Component.................................. | 5770SS1DB |
Failing Module.......................... | RCHMGR |
Reported Release................... | R710 |
Duplicate Of.............................. |
System i Support
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information
Document Information
Modified date:
13 October 2012