DSXchange

I have searched the forum, and I have been unable to find a DS Server Edition BASIC code snippet for setting and getting stage variables inside a routine / function. I know this must be a simple process, since it is referred to in many posts, but I have not been able to locate it on DSExchange... I...

No, negative numbers are error codes. And a -6 means:


See the $DSHOME/include/dsapi.h file.

Not according to your error! As noted, make sure you have room for two copies of the hashed file, at least temporarily.

Batch files, shell scripts - same thing. I have contacted the tivoli scheduling team and they have said that it will not be possible for them to set up the status on a case-by-case basis. I find that very hard to believe. Sometimes that boils down to the fact they either don't know how to do it or s...

Keep in mind the fact that a Routine is expected to return a 0 status upon successful completion, whereas a job never will but will return a 1,2,3 (etc) instead. And if you have automatic error handling turned on in the Sequence any non-zero routine status will be considered to be an 'unhandled fail...

shyamrai wrote:The Tivoli job shcedule is used in a lot of other applications. So, do you think status can be applied only to DataStage.

Certainly, "they" should be able to do it on a case-by-case basis.

Why do you 'need' to release them? Are you sure you don't mean 'unlock' instead?

Why in the world use a routine to run this job? What's so special about this that you can't use a Job Activity stage?

karrisuresh wrote:always sort the data before it is sent to aggregator

As noted, there is more to it than that. You also have to assert the sorted order in the stage so it knows you've done this. And hopefully you've sorted in such a manner that supports the grouping being done, otherwise it's all for naught.

There are also multiple ways to get the system date. If all that doesn't help, come back with an explanation of what 'rundate' means in your world.

What's parallel got to do with any of this? We are discussing a BASIC routine for goodness sake. I know you've got yourself a 'solution' but it's overly complex and it can be easily handled in other ways as mentioned here.

If you want to pursue this we can. The count and redirection do work.

I thought we answered how to do this in another thread?

Well... you are severely hampered in your 'tuning' ability if you "can't change the job design". Those direct database lookups (which it sounds like are being done twice) are the worst performant way the job could have been designed. 45 minutes to an hour to process 700 records is pretty bad. About ...

ray.wurlod wrote:or the Pope has adjusted the calendar in the interim.

Yah, gotta watch out for them Popes. They does stuffs like that every now and then.

That setting in the Administrator is the default setting for the Project and only affects new jobs created after the option was enabled. Ken Bland has a suite of Job Control Utilities available for free download from his website, one of which is a little job to set the auto-purge information across ...