DSXchange

OK, I finally got it. Thanks to a tip from IBM support, I found: 1) the job schedule information in RT_CONFIG nn files is not reliable, as explained above -- you can't tell whether a schedule is active or not, and 2) on both Unix and Windows, when you schedule a job, DataStage Director in turn creat...

The information that is in the DSX of an executable job for scheduling is in the record "JOBSCHEDINSTS" of RT_CONFIGnnn. And the parameters are in JOBPARAMINSTS. The records are not present if the job has not been scheduled. Dean, I wonder if you can share any more insight. After some off...

Well, I couldn't find much scheduling info in the XMETA DB. I was able to find job names and their corresponding project and path, but if there's any other job schedule info in the other tables, it's encoded in hex. But I don't think it's there at all; I ran a DB trace while scheduling and unschedul...

I can verify Dean's assertion that the info is in the exported DSX files -- if you export the executables along with the job design. I created a dead-simple Server job in Designer, saved, compiled, ran, scheduled it in Director, and then went back to Designer and exported the job with executables to...

You can see that information in the RT_CONFIGnnn file, or export the executable and it is visible in the DSX too. Dean, Can you please explain a bit more? On my system (DS 8.0 on Windows), %INSTALL_ROOT%\IBM\InformationServer\Server\Projects\%PROJECTNAME%\RT_CONFIGnnn are directories, not files, an...

heh, fair enough, back to doing it the hard way ;-) Hopefully I'll be back with some info -- send a search party if I don't return in a week or so!

Hi all, I'm trying to write a report to analyze DataStage job schedule information, and need a little help understanding where and how the data are stored. We have a bunch of DS Server jobs scheduled in Director. From time to time we change a job's schedule, and occasionally we forget to change it b...

Thanks for the tip! I've been lamenting the lack of a 'sink' stage that I can route to when I want to just do nothing but exit. This will do the trick -- not as self-explanatory as I'd like, but functional. Thanks again!

I've searched the docs and the forums, but can't find much to go on for this problem: I have a sequence job that is scheduled to start in the morning, runs all day waiting for input files, processes them through a few server jobs, then loops back and waits for more input until a certain time of day ...

Guys, Thanks for the feedback. I'm on the final push on a big conversion project, and going on a few days' vacation tomorrow, so I'll follow these tips in a few days. I'm particularly interested to try Ray's debugging technique to see what's coming in and out -- I've only been using DataStage a few ...

Sure, why not. It won't give away secrets, just make me look stupid. So, don't bother to tell me there are better ways to compare dates -- the issue is returning @TRUE/FALSE! ;-) Or, please tell me a better way to compare dates -- but I really am focused on the return value! That said, here's a simp...

Sure, why not. It won't give away secrets, just make me look stupid. So, don't bother to tell me there are better ways to compare dates -- the issue is returning @TRUE/FALSE! ;-) Or, please tell me a better way to compare dates -- but I really am focused on the return value! That said, here's a simp...

yep, I just tried a similar test. I made a routine that does: if Arg1 = 1 then Ans = @TRUE else Ans = @FALSE and a transformer derivation that calls it: if testTF(1) then 'T' else 'F' if testTF(2) then 'T' else 'F' and get the expected T or F in my output. But I have a couple of other routines, one ...

I've searched the docs and the forums, but can't find any reference to the problem I'm experiencing: For the second time, I built a routine that sets Ans = @TRUE or @FALSE, and when I call that routine in a Transformer derivation, the result seems to be ignored. Is there any know problem with passin...

I think you're probably correct -- the dsjob docs don't say anything about a param set option, and trying to use the param set name as a param: -param <paramsetname>=<value>, like -param DSNParamSet=dev doesn't work. This would suck -- I don't want to specify e.g. production passwords on the command...