DSXchange

Check to ensure that jobmonapp is running, an exact search here for that word should help with the where and the how.

I think actually there is a service involved on Windows but have nothing I can check that against.

What happened with your "jobs not displaying" issue? Did this start after a reindex attempt?

paranoid wrote:Oh Thanks a lot Chulett. So it is x86 chip set.

Seriously?

If you mean they are not listed, i.e. you can't "see" them, then search here for the proper use of the DS.REINDEX command. If you mean they are listed but you get an error trying to open them, let us know.

... however, you'll still need the "do self join after aggregation" part to put this back together with the remaining columns. Might as well stick with the Aggregator and figure out how to get the fork join working properly. Sure seems like you would be able to use this "code" co...

That's a known standard behaviour of DataStage with regards to unbound varchar fields, there have been many discussions here on the subject.

The easiest question to ask is whether Solaris is running on SPARC or x86 chipset. I have got the following output when i executed isalist -v sparcv9+vis2 sparcv9+vis sparcv9 sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc sparc sparc sparcy sparc sparc Seems pretty obvious to me. ...

Just want to make sure people understand that this is a DataStage limit we're talking about here. Regardless of the underlying database, the GUI widget in the stage imposes a limit on the size of the sql and that is what Maverick has needed to work around.

As noted, there's no "updating" of a sequential file. You'll need to join the two files and based on that decide if a record is new or needs to be changed before writing.

OK Ray, but what happend if I need to use the Automatically handle activities that fail option in my sequence?. If the Reply of a stage is distinct of zero, this option will interpret it like abort . That's true - left to its own devices it will interpret anything other than a zero status as some k...

Is there some particular reason that you're not using a Job Activity stage for this?

For 1 & 3 you can use a Folder stage to write out the records to dynamic files based on a key column. Not sure what #2 means as there are no "updates" to sequential files.

First tip: post in the correct forum so I don't have to move your post. The Site/Forum forum is for comments, suggestions or problems relating to the site itself, not DataStage ones. Since your question is specific to PX jobs, that's where we are now. Second tip: Post an actual question in the body...