DSXchange

So you got your date issue resolved. Is that what you are saying???

Abhijeet1980 wrote:So far no one has ever tried. It is desperately needed.

I wouldnt say desperately. The DS help documents are help files. Gather them together in a nice binder, cover it up on in a nice covering and viola, theres your book.

Actually not acievable out of the box, by setting some property, but the 0 byte file could be deleted within the same job. And hence my compact statement that 'it is achievable'. I mean the end result
But yes, there is no way that the empty file can be avoided from being created.

Wow, lots of fun chit chat huh. I see craig had fun over the holidays Praburaj, i think Craig cleared out your question that was referred to me. There isnt really much we can do from this side of the glass as Craig already pointed out to you. Follow the second last entry of Craig and post the results.

Narasimha, your approach will not work if job B and job D need to be fired regardless of success or failure of job A or Job C respectively.

Certainly achievable. Search for specific methods.

It doesnt "have to have to "be changed. Argue your way accross. If no avail, then atleast post the logic, maybe we can help you build a c routine.

When you say " works erroneously ", do you mean that it does get fired but doesnt do what its require to do or does not fire at all. I bet the latter, if thats the case then there should be something in the log to tell us what really happened. Its too little information for us to help you debug. Nee...

This is an OS level error message. Do an exact search on "received signal SIGSEGV " and you will find many posts on this. Here is a starter
http://www.dsxchange.com/viewtopic.php? ... al+SIGSEGV

Welcome Aboard
Use the search facility of this website. It is very powerful and will save you lots of time. Search on the key word 'SAP Pack'.

Read about restartability with checkpoints. Thats the mechnism that a job sequence uses. If the job aborts, only then it will restart from that point. If the job finished with warnings (JobStatus = 2), it still finished and hence will not be repeated the next time you fire the job sequence, unless y...

Split the inserts and updates for one, use the enterprise stage. Search this forum. This topic has been discussed time and again. You will also find that rows/sec is meaningless. It depends upon a lot of factors.

chulett wrote: You need to work on your thread titles. I mean, come on...'general'?

That made me laugh so hard... I kinda like the topic, general , keeps you in this delimma , "what could it be, what could it be"

Perhaps

pssst. 2B