It just took me getting away from it a little. The problem was I had some subroutines that were called from my dictionaries that either needed to be compiled or cataloged. I did both so not sure which one fixed it.
Glenn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glenn Batson Sent: Friday, February 24, 2006 9:40 PM To: [email protected] Subject: [U2] UniXML exception from UO.NET I have a piece of code that submits a query through UO.NET like: list SQL_DIST WITH DIST_NBR = "100001" ID NAME ID.SUPP TOXML *** Note there are a lot more columns than what I show in the above query. I get the following exception. Can anyone give me pointers on what the error is trying to tell me. I see the error in the UO.NET documentation but it is just a mapping of numbers to error, so not much help. The query does work from the ECL. Exception: IBMU2.UODOTNET.UniXMLException Message: [IBM U2][UODOTNET - UNICLIENT][ErrorCode=30111] This is not an I-Type or the I-type is corrupt[IBM U2][UODOTNET - UNICLIENT][ErrorCode=91] Please verify UniVerse or UniData Version. This feature may not be supported in older UniVerse or UniData version. Glenn ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
