DSXchange

Sequence jobs haven't changed significantly and I for one wouldn't really compare them directly to Autosys or any other kind of scheduler. I've used Enterprise schedulers to run Sequence jobs, the Sequence jobs control the dependencies between the jobs, notifications, etc. That way you as the ETL de...

It simply means that there is no column named "enddate" in your table.

The value of @OUTROWNUM for the first row coming out will be 1. No clue what you were seeing in 7.1 as my memory fails me for that old of a release, but never saw it count from zero in the 7.5.x versions I used for years. And since there are no incoming rows, you really should be checking @OUTROWNUM...

Yes. It can only return one result but you could parse one of multiple delimited values from there for different parameters.

Are you in fact using a Server job for this, as you marked your post? I ask because you posted it in the PX forum, so just want to check. Also, a little more detail than "couldn't do it" would help us help you, at least if anyone here has any experience with that stage (I don't). So... do ...

I can't imagine this functionality has changed. In order to compile a transformer as a 'source' it must contain a stage variable. You don't need to use it but it does actually need to exist. That and a constraint so it knows how many rows to generate, of course.

I believe that Ray's answer is for the pre-8.x releases, for 8.x they are described in the Designer Client Guide pdf, in the version I have it is Chapter 14. The actual filename is i46dedsc.pdf in your docs directory.

2. An Informatica "disconnected" lookup is akin to a "conditional" lookup. There's not much sense in doing one for every record in the input source like a regular connected one would do, you use it in a derivation only "when needed". For example, I'm using them to emula...

Hmmm... perhaps a custom routine was added with a print statement (or something similar) in it?

Don't try to type it in manually, use the "..." Parameter Helper to make the proper choice and fill it in for you.

That's literally exactly what it says? Just three lines with "start problems" all lower case like that as the first line? If so, that's not something I've ever seen in all my years using the tool.

Sheesh, I don't know why you felt a need to do this when I'd already created your new post for you and all you had to do was update it. OK, fine we'll play here... and I've nuked your other post. As I noted in that other post, nothing you've posted so far indicates any kind of problem. What are you ...

Wouldn't all of the subprocesses show their parent's PID, i.e. their PPID? Am I missing something or couldn't you just simply walk that chain of pids?

Perhaps your Hash partioning keys were not properly defined then. Does the same problem happen if you run the job on a single node?

Chapter 6 in the DataStage Designer Guide pdf.