DSXchange

Ans = UnixOutput<1>

Yes. "7.5.0" would be "different" from 7.5.1 as well as from 7.5.1A, 7.5.2, etc. The differences would be spelled out in the readme - usually in a "What's New in this Release" section. Plus the Version History. If you really are on the initial release of 7.5.x then you should upgrade - these new ver...

Then you need to investigate. Nothing in DataStage would do that, only a person or some other process would. Start with your SAs, explain the situation to them and see if they have any explanation for it. I'd also check that they were ever really scheduled properly. I've seen times where the schedul...

a) No, not really, dead is dead and it just becomes another 'abnormal termination' you need to deal with.

b) I suppose, but I'm not privy to the internal workings of the stage.

I've never seen any metric for that. It seems to vary widely enough that all you can do is process files on your system until you reach your particular limit.

Perhaps Ernie might come along and have more light to shed on this.

Basically, yes. That would be a 'minor' difference or a maintenance release difference. You see 'version details' for a particular job in the job's Properties - which is something else entirely. The version we're discussing here is the version of DataStage itself, details of which can be seen in the...

I would wager that was it as well. Not being 'unscheduled' but you need to realize the schedules are per user and are thus only visible to the user that scheduled them. Check the 'Schedule' option in Director when logged in with a different user and it will show as 'Unscheduled'. The question is - d...

umamahes wrote:Contents of phantom output file =>

That's not the complete message. Double-click on it and post the actual contents.

Now that's funny... and pretty much what I thought it would be:

http://uncyclopedia.org/wiki/Retrophrenology

Then it will only exist inside a running job's environment. And you can still use ECHO from inside the job that needs it.

A little premature to mark this as resolved. Compiled ok != runs ok or even solves the problem. I'd wager you'll need to kill the job. You are going to have problems attaching to the currently running job. It should just use DSJ.ME for the handle rather than attaching. And will link counts really so...

Minhajuddin, you did fine. I know you mentioned that - I was actually pointing that fact out to jreddy. Their solution is fine as long as you don't need to know the sequence number that was generated. When you do - as in your case - you have to 'pull' it beforehand.

What happens when you click on the 'Help' button inside the stage? Or you could open the Parallel Job Developer's Guide to the Data Set Stage chapter and see what it says for Update Policy under Target Category there.

Waaaaayyyy too late for that.

Welcome to Wonderland, Alice.