DSXchange

There's no concept of a globally scoped variable in Sequence jobs you can update while the job runs. You may be able to build another job that takes in your new UserStatus value and appends it to its current UserStatus, thus concatenating them there but I'm not sure a job can query its own UserStatu...

As noted, you need to escape the quotes inside your parameter value so they are not stripped by DataStage.

The resolution is (IMHO) spelled out pretty clearly in the answers here. If you need some clarification, let us know what is unclear. If you have an actual problem to solve, please start a new post and give us all the particulars of your issue.

hello, you know my habit of not opening new posts since similar problems are already reported in here. <snip> if you have any advice I would gladly take it :) First bit of advice? Break this habit. Similar != same, so please start a new post and then reference the old post if you feel it would be h...

HariK wrote:if the excel file has more than one sheet than converting to CSV will not work.

Sure it will, it just means you end up with more than one csv file.

Somewhere there is a large number mapped to a smaller number and it won't all fit. Typically this happens with Aggregator output which, if not explicitly handled, will output its results in dfloat format.

The Pivot stage is the correct answer. Tell us how you have it set up and what output you are getting.

It means that any 'Incomplete Column' handling must be done from whatever column you start with to the end. In other words, you can't have 10 columns and set this on 7 only, you have to set it for 7-10.

Make sure the link order is correct - that your Reject link is last - and try removing the constraint. Just let the fact that it is marked as a Reject row do the work and see if that helps.

Please stop with the exclamation marks in your subjects, I don't need the extra work running around behind you and cleaning them up.

Thanks.

Your problem isn't the length of the job name (per se) but the length of the trace file generated from that job name - it looks to be "too long" for whatever operating system you are using.

Well, then... a reinstallation if the reboot doesn't help.

There's no MODIFY stage in a Server job... that functionality would need to be done in a Transformer.

A number of years ago, Ken Bland posted several items here about landing data, including this thread. If you search for "pressure" with "kcbland" as the author, you'll also find a number of discussions on the concept of "back-pressure" and why landing between the extrac...

You do understand that DataStage has no 'native scheduling facility' and what it talks to is the Windows scheduler, yes? So the two approaches aren't really any different. Also, can you guarantee that your job never runs longer than five minutes? What I've built in the past for situations like this ...