DSXchange

Your slashes are going the wrong way.

No, not the box yet, just DataStage. The box would take an Act of Congress. And yes, everyone has the issue not just me... if it was just me I wouldn't be quite so worried. :wink: I've never been able to telnet over to it, I think they have that locked down for some reason as I can only get there vi...

Well... run it in a loop for all jobs in the project and see if you get a '99' for anything other than your compiled jobs. May give you some peace of mind, or show that we need something "tighter".

jerrylzdd wrote:OK,i will move the topic to Enterprise Edition forum.

Actually, the request was for the Moderator (not you) to move (not repost) this in the proper forum. That way we don't lose the conversation history.

Have you not worked with hashed files yet? They are the heart and sould of Server jobs so something to become very, very familiar with if you haven't already. :? Probably easiest to do this in two jobs. First one that just creates the hashed file and looks something like: OCI -> Transformer -> Hashe...

Nothing, eh? Dang.

I can't tell from your example what the "duplicates" would be. General advice - sort by the grouping key(s) then check for duplicates using stage variables. First time you see a 'group' is ok, if you see the same one again, not so ok and you should be able to discard or capture them fairly...

y dont u use remove duplicate stage nd dn a compare stage. aneways transformer degrades the performance :!: Two points, last one first: Transformer performance has not been an issue for quite some time, that was addressed years ago, so your advice while good intentioned is out of date. Please use a...

You haven't said what exactly your "problem" was.

What operating system?

Actually, your new requirement is to explain to us exactly what you mean by "binary file" in this context. As noted, without a proper explanation of what you need to do, we're all guessing as to the solution.

You can't. You need to be disciplined with how you run jobs and manage the warning limits, typically via some kind of job control, and avoid the urge to run jobs with 'unlimited' warnings.

Then that's what I would expect the job report to show as well. Are you sure you have the JobMonApp running properly?

Here is what I see while my connection attempt is "hung", there's only one other person connected and that's to another project. I removed their small number of records from the Active Record Locks section for clarity. >LIST.READU EVERY Active Group Locks: Record Group Group Group Device.....

Not sure what's going on, so need some help. Had something strange going on in one particular project where you'd open a job named 'A' and internally it would show with name 'B' in the Designer. We found this with two jobs so exported one and found the Category "corrupted" - it showed in t...