DSXchange

Does this problem only occur for you from your workstation, or is it a problem for everyone?

It's a specific ls option, perhaps that particular OS has it 'on' by default or you are using an alias there.

Or you might consider looking those up from another source rather then farming the logs just for that.

What is only in SunOS? I don't see anything here that isn't standard UNIX.

Sort your input data to support the aggregation you are doing and mark it as sorted in that order in the Aggregator. If you do it correctly, rows will flow through the stage for each 'sort group' instead of holding on to all rows before returning any.

Source database? And this is with the DRS set to ODBC as well, I presume?

I didn't misunderstand anything. Actually, you shouldn't be getting questions to other DataStage products posted here. However, it happens, so we double-check if it's unclear. Some of us read all forums. I don't expect to answer anything here but do enjoy learning whatever I can from the exercise. A...

'Their own forums'? So you own this one? And you're a mind reader as well, it seems. If you check vijaya's posting history, you'll find that all of the questions they've posted have been for Server or PX jobs and this isn't the first one that looks like it's here by accident - so asking if it's real...

Nah... it's not a regular expression. It's just the notation that the script is executable when 'listing' it. You need chmod to enable the appropriate 'x' bits. Check your man pages or talk to your admin.

Use the Exception Handler to catch anything other than 'Ran OK'. Follow it with a Routine Activity stage that calls the UtilityAbortToLog function to abort the Sequence. I doubt you really need the Terminator, but I'll leave that up to you.

Isn't there also a licensing consideration? I seem to remember reading here of that being a factor in compile length at times, where only one person at a time was allowed access to the compiler??

Jeez, didn't even think of that - but you are right, it only works from the Director. It is restart aware, Designer could care less. You need to get out of the habit of running jobs from the Designer unless you are debugging them. The Director is the weapon of choice to fight that particular battle.

If you've done everything correctly, the job will be in an 'Aborted/Restartable' status. Only then can you run it and have it pick up where it left off.

Without recompiling or resetting... just run it again.

can u please tell me in specific ,what kind of internal format does DB2 expect .. The kind you get from using IConv. and also ,i am using lots of userdefined sqls and before after scripts in OCI stage. i understand that this is not possible in DB2. What makes you think this isn't possible? I don't ...