DSXchange

We are coming from DS7.5 with DB2 API stage and migrating to 8.7 but are facing the problem, that generating SQL in 8.7 Connector stage is extremely limited. Did we miss the WHERE condition or is this really not there anymore? Is there really just tablename and the columns? The SQL builder seems not...

Compile options are pretty much at standard for 8.7, almost the same as suggested here. APT_COMPILEOPT -O -q64 -c APT_LINKOPT -G -q64 Under 7.5 we have: APT_COMPILEOPT -O -c -qspill=32704 APT_LINKOPT -G So difference is the qspill (but conforming to docs that should be only set when code doesn't com...

We are migrating from Datastage 7.5 (AIX 5.3, XL C 8.0) to 8.7 (AIX 7.1, XL C 11.1) and are experiencing quite long compile times. As far as I can see, it's not client related but the time seems to be rather spent by the XL C compiler process on AIX. Is there anthing known on how to improve compilat...

Yes we really do job validation, especially after each automatic deployment but also manually.

Yes, chulett understood that absolutely correct. Basically, I don't want my subroutine to run when you just click on "validate" instead of "run" for the job.

Thanks a lot that works so far but it seems like I can't distinguish between a validation run and a normal run with that (never get DSJS.VALOK). Is there a way for doing that?

How may I obtain the JobStatus from an After-Job Subroutine in DS 7.5 on Unix? I mean getting the "Finished", "Finished(with warnings)", "Aborted" (or something similar in numerical form). I tried to get it via DSGetJobInfo(DSJ.ME, DSJ.JOBSTATUS) but apparently, this al...

@kwwilliams: Thanks a lot. I will try it with column export/import. Regarding your concerns with overwriting these tables: Well, we have a pretty huge datawarehouse with historization (we've 4 dates for this: editing time and end, effectiveness date and end). However, the tables I'm speaking about i...

You are right: The key values are different and could be handled over as Job parameters or so.
Performance should not be an issues because these are rather small tables (<100 entries).
I didn't understand what you meant with the CDC stage. I don't see an option to set a schema file there?

I have to create lots of jobs which basically just put data from stage to core tables. Only some technical fields need to be added (creation time, jobname) but no fields changed. We would need to do a change capture to check if data has changed and do an update or insert based on this (if nothing ha...

I tried to export a CSV file. I've set the delimiter to , and the quote char to ". If there's a " in the string supplied from the source, Datastage seems to not handle it correctly: The file is then read wrong (for example with view data) and in my opinion it is made wrong (no escaping don...

What is the correct way to return the value from a routine in a Datastage sequence? If I just return it via the return value, I have to disable "Automatically handle activities that fail" and "Log warnings after activites that finish with status other than OK" in the sequence. Ot...

Well DB2 thinks it is valid because it comes from there and goes there. So this is really strange...

Noone having an idea on this one?

In my files I can get it only using
EVAL "@RECORD<8>"
in the derivation field of the universe stage (perhaps depends on DS version?). It now works fine, thanks a lot!