DSXchange

I'm a little confused. You don't use the MQSeries Plug-in in DataStage simply to read XML, you use it because you have to interface with MQSeries.

If all you need to do is read XML files, that's what the Folder stage and the XML Input stage are for... in both 7.0 and 7.5.

Actually, a single record with a hard-coded key cached in memory is pretty darned efficient for something like this. I've been known to do something like that in other situations. So Ravindra, to clarify are you saying that: 1) You counted the number of lines in the sequential file. 2) You loaded th...

Actually, you've gotten several solutions. Stop fixating on the 'Filter' ability of the Sequential file stage, it's not appropriate for any of the scenarios you've made up yet. If you need to 'pre-process' a file or series of files to build something the Sequential File stage can read, then as previ...

There's no text file support inside the Filter command, so you can't take that route. Multiple command support there is probably pretty limited. Dont' expect to be able to run multiple commands in a serial fashion there, but you may be able to pipe commands together. Keep in mind how the Filter work...

Those are not appropriate Filter commands. Those could go in a Command stage in a Sequence job. They could also be used directly or via a script before/after job with ExecSH or ExecDOS.

Spin off another leg from your Transform to an Aggregator. Pass it anything - a single field, a constant value - and have it 'Count' it. What comes out is the count needed for your trailer record. Then either write it to a separate file and cat the two together 'after job' or - if and only if - the ...

If you are sure there are no warnings when you check the job's log from the Director and the monitor shows the correct number of rows going 'in' to the target stage, check a couple of things: Double-check the table name you are writing to. Are you specifying a schema/owner in the stage? Also double-...

Yah, still using a version of this on a daily basis. I should probably look into adding your magic unlocker from ETLStats so that I don't get 'skipped' jobs all the time. Are you using this with 7.5.1A Kim? It was working flawlessly for me before I upgraded but since the upgrade been having an odd p...

Yah, Ray's pretty 'old school' (wink wink) when it comes to aborting jobs. In the past I would have agreed 100% with him, but when Checkpoint Restarting was added to Sequencer jobs that all changed - in that context. I prefer to not manually run or rerun failed bits of Sequence jobs. Once you come t...

In my case, I dont want my Master sequence to abort, I just want it to finish with warnings so that if I restart it, only the jobsequence containing the aborted server job runs. You need to abort it in order for that to happen. I do this 'all the time' and it does work. The status of the Sequencer ...

I've found they work just fine. The 'trick' when running sub-sequencer jobs is to propogate any errors in a sub-sequence job up to the master sequence.

Use the Exception Handler. When a sub-sequencer doesn't complete normally, branch there and abort the master sequence job as well.

Oh nos, Mr Kim, please don't tell on me!

rxs0005 wrote:I have a TAB delimited txt file that I saved using TOAD it has more than 65000rows so i cannot save it using .CSV extension

Sure you can, there's no limit on the number of rows that can be in a csv file. Just don't try to load it into Excel...

I agree. Too many times stopping or killing the DS process leaves the database process joyfully continuing on it's merry way.

You don't think so because you have been doing it. Trust me, Average Job wants to work only in the GUI and not have to write or maintain hand coded job control. I'm not in a position where I can check, but those components probably do ship with DataStage. Perhaps I'm incorrect, but if they use the '...