DSXchange

For the one case; there is exactly 11 students in the xml file; resulting in 257 rows in total. It seems I have to work my way up from some random number like 60 then it will go to 85 then 114 and so on until it finally reaches the total.

I will continue to debug; thanks for the heads up

My job is working though it has a peculiar property. It seems to produce more rows with each execution. I doesn't produce too many rows; but with each turn it can read more rows until it can consume the whole file. I have hierarchical stage that reads xml, in that stage it produces at the beginning ...

chulett wrote:(re)Read my post for how cron is used. And not used.

"At" was not running; it is working now Thanks Craig for your help.

qt_ky,

I just tried it 10 minutes into the future and the status numbers do not change.

Preface: Job is already designed compiled and tested. Steps: 1. Launch Director Client to the appropriate project as myself "irvinew" I have admin privileges. It opens in the "status" window 2. I open the "Schedule" window; right click and either "add to schedule&q...

I have completed my job and it is ready to be scheduled. I think I have to use Director to do this; all I think I do is simply launch Director; schedule the job to run at a certain time. I don't save the job somewhere; I compile it in design; verify it runs. However nothing ever executes; I check th...

Sorry for the late reply; I found my work around. The testfile generated in the parser step seemed to bog the system down; I found a workaround by first generating a sample XSD file then a test file from that to test the Main XSD document. If I left it blank it also worked. Question is; why would it...

I have solved my own problem. 1. Datastage does not like the XSD document I had; I had to reverse engineer one of the XSD documents to make it an element a complex type just so Datastage could drill down into the XML. The XML had an embedded XML document where that document could be 1 or many. 2. I ...

I have hit a wall. It is a very simple job, which is supposed to parse xml The newest problem is that now I get errors: 1) Out of String space when you save 2) Error message: Error calling subroutine: *DataStage*DSR.ADMIN (Action=36); check DataStage is set up correctly in project ETL_TEST_PROJECT_W...

Update: I got 1 row to work; seems as reason the hierarchical stage didn't want to drill down into the xml was that it couldn't resolve where the schema location was........I think. Anyway I got it to resolve 2 different ways: 1) I butchered the xsd and made the highschool a complex type xs:complexT...

Further context: I think I figured out why it doesn't read rows; though I've yet to get it to work. I have a multiple XSD validating and parsing a single xml file; within that XML file it has other xml files bundled into it; that is supposed to be contained in the "BatchContent". Within th...

Hope this helps; its the HighSchool XSD; the include CoreMain is far to large to paste here; the AcademicRecord is quite big as well. Those 2 files don't appear in the Library as name spaces; only the AcademicRe ordBatch and HighSchoolTranscript can be found to be used as XSD documents in the parser...

I have successfully read on 4 XSD files I have 1 xml source test file to read in. The source xml file has really 2 parts, one called AcademicRecordBatch which has basic Sender/Destination info that does not change; I can read in that. it produces rows in a seperate job. I The second part has high sc...

Combined xsd's is the norm. So that should be fine....at least one or more of them probably has an import or include statement. Chances are they are all four intertwined The Hierarchical Stage has a steep learning curve. Keep at it. Things like "no rows retrieved", etc. are normal when fi...

I hope someone can help me here. I have 4 xsd documents that are interlinked. Their names are: 1)AcademicRecord_v1.9.0 2)AcademicRecordBatch_v2.1 3)CoreMain_v1.14.0 4)HighSchoolTranscript_v1.5.0 Crazy I know.... I have a test xml file that imports the "AcademicRecordBatch" and the "Hi...