Search found 20 matches

by metabill
Thu Nov 18, 2004 3:52 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: xls.files
Replies: 8
Views: 3585

It apears I have solved my own problem....

After taking another look at the Import dialog, I noticed a Filter button. After clicking on that, I did see the Include System Tables checkbox. Selecting that and proceeding resulted in the table definitions being loaded OK.

-Bill
by metabill
Thu Nov 18, 2004 3:47 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: xls.files
Replies: 8
Views: 3585

(Using DataStage 7.5 on WinXP/SP2) Even after following the instructions in the previous post, I still cannot import the table definitions from the sheets in an Excel 2002 worksheet file. The file contains 3 tabular sheets, all with column headings on the 1st line. I've created an ODBC system DSN (M...
by metabill
Thu Sep 04, 2003 9:19 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Bad XML exported?
Replies: 2
Views: 1375

Ray is correct about what the value represents (thanks for the insight!). Indeed, it is an escaped representation of the character corresponding to hex 1B, or 27 decimal, which is the Unicode "escape" control character. But this is not a legal XML character. The XML spec states that the on...
by metabill
Wed Sep 03, 2003 12:46 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Bad XML exported?
Replies: 2
Views: 1375

Bad XML exported?

Greetings. I'm using DataStage 5.1. When I export a job to XML, the XML contains an unescaped ampersand, which is invalid as an XML character. This causes grief for whatever XML parser I try. The text sequence occurs twice within a TrxOutput element; once as the text for a RoutineTransforms property...
by metabill
Wed Sep 03, 2003 12:33 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Bad XML exported?
Replies: 0
Views: 441

Bad XML exported?

Greetings. I'm using DataStage 5.1. When I export a job to XML, the XML contains an unescaped ampersand, which is invalid as an XML character. This causes grief for whatever XML parser I try. The text sequence occurs twice within a TrxOutput element; once as the text for a RoutineTransforms property...