DSXchange

Need the Null handling as mentioned. Use Operator Combinablity option available in transformer to false, so that you can get know more on where you getting the error.

Care to specify the solution that you had opted and mark the topic as resolved, so the search function can be more efficient for others.

Try this

Try using LongVarChar as datatype.

Or you can use your front end tool also.
You can check the Performance tab available on Instances folder of Control Center. You can change the Query heap size. By default it is 1000, you can change to 2048 or even more.

Yes
Yes.

You mean JobActivity? Equ DSJS.RUNNING To 0 ;* This is the only status that means the job is actually running Equ DSJS.RUNOK To 1 ;* Job finished a normal run with no warnings Equ DSJS.RUNWARN To 2 ;* Job finished a normal run with warnings Equ DSJS.RUNFAILED To 3 ;* Job finished a normal run with a...

What was the condition that you gave in the Warning conditional. That might have lead to the warnings in the main Job control. DSSetUserStatus can be used either in BASIC transformer or in Server shared container in PX.

Dont use it as Fixed width. Change it to varchar and have line terminator as none. Pretty much thats it.

That was an excellent collation of useful materials.
Shouldn't the WebSphere II Developernet be pointing to new IBM website.

Any APT variable which can set a sequence to create a warning when its underlying job finishes ok?!?! (Iam sure Kim, wont refer to Message handler)

Took me while to get the result of the query

Then you better index on what you know, to avoid full table scan. Juz kidding.

As mentioned by Whale, read it as single varchar field, parse it in a transformer. Check for "generation date:" and store the date into a stage variable, and populate this variable in 4th column until you get a records with "generation date:". The 5th can be populated with SYSDATE or Date() in datas...

The status might be showing as running. But have you checked the output for that job, was the target table been populated. There might be a chance where the status might not be shown with the updated information. Or probably you noticed, the node 6 might have got some problem by the time when the jo...

without loosing the log records that is under the main job

But the log records are accumulated under main job only. The 300 instance are just the representation of it.

You may use something like