|
I hope you have better luck than I did! Been trying to setup the Extender for two weeks now. There's a Fixpack in IBM that includes DB2 XML Extender administration wizard product in it. That's the only PC piece that I have found so far. I installed it but have not been able to connect to my Iseries yet, funny I get the same error message as you. Of course, I have no clue what I am doing, just had an XML project assigned ot me. I have received two emails from IBM suport pointing me to a couple of manuals to read. I have included them at the bottom of this email, it took me three days to get this information. I've read so many manuals that I think I'm a tree at this point. If anyone has a CHEAT SHEET please send it to me. I am researching other methods & resources, I figure if it is this hard to setup it probably will be harder to use. DB2 Viper 9.1 is available and looks pretty awesome, stores XML and DB2 in the same database. Still checking it out so don't quote me on that. Justsystems an IBM partner has already developed a product with Viper being the driving force. I am currently downloading a trial version of it. I'm hoping for a real voice if I need support help. 1)email Since you are new to the XML Extender , I would recomend reading chapter 1 of the followig book: http://www-1.ibm.com/support/docview.wss?uid=pub1sc18917900 You do NOT want to use the GUI. 2)email http://www-1.ibm.com/support/docview.wss?uid=swg21051065 Debra , you don't need to change the CCSID for the system , if you don't want to, you can just change the ID for the user or the job. The CCSID can be changed to fit your OS/400 environment needs by using the following commands. (You only need to do one of the commands below) CHGSYSVAL SYSVAL(QCCSID) VALUE(37) CHGUSRPRF USRPRF(XXXXX) CCSID(37) CHGJOB CCSID(37) CHGJOBD JOBD(XXXX/XXXX) USER(XXXX) where USER=USRPRF with CCSID 37. -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Manuel CERDA Sent: Wednesday, October 18, 2006 10:03 AM To: wdsci-l@xxxxxxxxxxxx Subject: [WDSCI-L] XML tools with WDSC 6 Generate iseries data from an xmlfile All, I am trying to use for the first time the XML tools within WDSC 6 and os400 V5R3. I want to convert an xml file located on my local pc windows folder to a new iseries data file on my user library. From wdsc, data perspective I have created a connection to my iseries (host name : myhost, database name myhost (I do not seem to be able to change the database name)) using the jdbc for iseries v5r3 which looks fine. I have created a project and imported the database from my connection which looks fine. on the iseries I have got from wrkrdbdire : (This has been defined by my iseries admin) entry: myiseries remote location : loopback entry: myiseriessys remotelocation: *local the database myiseries have been activated DXXA002I Connecting to database MYISERIES. DXXA005I Enabling database MYISERIES. Please wait. DXXA006I The database MYISERIES was enabled successfully. Press ENTER to end terminal session. I can generate the sql ddl from the xml file using the xml tool. When i try to deploy the .sql to the database : I get the error message SQL0104 Token ) was not valid... When I try from the xml file to use the right click, generate database data, I select use existing connection, I got a window with database myiseries, schema MyLib, table, Myfile, action Insert when I click next i can see my four fields from the xml file, when I click finish I got the error message lWAX0010E Reason SQL0104 Token ) was not valid... I think it is something to do with the set up of db2 XML extender. I got the feeling that something needs to installed on my pc. Could anyone tell me a simple way to set up the XML exender on my pc. The documentation is all about xml DAD but in my case I thought I did not need one. Thanks for your help and time. regards, Manuel Cerda
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.