×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Ok...IBM 7.1 with latest TR (TR6?). Lots of info below and I'm sure that I didn't get it all.
Here is the general scenario...
PGMA is executed by a SQL stored proc and receives a CLOB(1048576). The CLOB contains Call data (typically XML, but not always) and is passed to PGMLOGGER that accepts the CLOB and writes it to a log table.
The variable's definition for the XML (XML_IN is the incoming parameter and XML_CLOB the value being written to the table) is being changed from CHAR(32000) to CLOB(1048576).
The CLOB in the table is defined: (XML_String aka XML_CLOB)
XML_STRING FOR COLUMN WBXXML CLOB(1048576) NOT NULL DEFAULT ' '
The variable in PGMLOGGER that accepts the parameter and writes it to the log is defined:
DXML_CLOB SQLTYPE(CLOB:1048576)
The listing (via a STRDBG session)displays this as:
D*XML_CLOB SQLTYPE(CLOB:1048576)
DXML_CLOB A LEN(1048580)
DXML_CLOB_LEN 10U 0 OVERLAY(XML_CLOB)
DXML_CLOB_DATA A LEN(1048576) OVERLAY(XML_CLOB:5)
When PGMA calls PGMLOGGER to log the data, the parameter contains the correct data:
After entering into PGMLOGGER, the value is changed:
EVAL XML_IN
XML_IN_LEN OF XML_IN = 1289060756
XML_IN_DATA OF XML_IN =
....5...10...15...20...25...30...35...40
1 'e>WPGQSL2020</Name>QB432960|||I|N||
Consistent with the expanded definition of the SQLTYPE, XML_CLOB is redefined as a DS with two variables...XML_CLOB_LEN and XML_CLOB_DATA.
The issue is that the SQL0311 error states:
Message ID . . . . . . : SQL0311 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 07/11/14 Time sent . . . . . . : 11:05:30
Message . . . . : Length in varying-length, LOB, or XML host variable not
valid.
Cause . . . . . : Host variable WBXMLD_ROW.XML_CLOB was specified. The
value in the length portion of the variable length, LOB, or XML host
variable is either negative or greater than the declared length. If the
host variable is graphic the length should be the number of DBCS characters.
The host variable number is 14. The specified length is 1289060756. The
variable is declared to have length 1048576.
Recovery . . . : Change the length portion of the varying-length, LOB, or
XML host variable to a valid positive number or zero. Try the request again.
So how did the specified length change from 1,048,576 to 1,289,060,756? How do I fix it?
In spite of the redefine that occurs, the XML_CLOB data is correct after it is populated with this statement:
Steve Needles | IT Architect | Specialized Distribution | Northland Insurance
Travelers
385 Washington | SB03
St. Paul, MN 55102
W: 651.310.4203
[cid:image002.jpg@01CF9CF9.2F9509C0]
________________________________
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.
TRVDiscDefault::1201
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
