DSXchange

Stop it you.

Holey Moley! That guy should get a LIFE!

Not sure why they felt it was any kind of 'next day', in my mind 24:00:00 and 00:00:00 are functionally the same thing - midnight. If you don't need to change the date then don't.

You inserted explicit sort stages set how, to 'Don't sort already sorted'? If so, then you could also use the $APT_NO_TSORT variable but the end result would be identical and the sort stage is better 'documentation' IMHO.

There's always the "export to dsx, edit the dsx and reimport" trick. Make sure you keep an unedited copy handy and work in isolation.

Been discussed a number of times, here is one example a search would turn up for you.

I think we've talked about this before... ah, here it is... it does seem to be a valid DB2 value but DataStage (and others) don't agree so you'll need to explicitly test for it and convert it to "00:00:00".

What are you using to do this import? The only thing that will understand a COBOL copybook would be the Complex Flat File (CFF) stage, as far as I know.

It would be an expression that evaluates to true or false, exactly the same as you would use in a Transformer constraint. When true, the trigger 'fires' and whatever is at the other end executes. You can check for failure condition(s) first and then use an Otherwise trigger for the good path or reve...

A routine could simplify this but you could use trigger expressions to check your parameters for values and a Terminator stage to stop things when any are empty.

A Sequence job could use an Execute Command stage to count the number of lines in the file using wc -l and the result could then be passed as a job parameter to your processing job. It might take a little tweaking - using Field() to separate the count from the filename in the output, if I recall cor...

Meaning, you'll need to get the count of records in the file before the job runs and pass that count in as a parameter so you can compute what 10% of that is at runtime... that or pass in the 10% threshold and use it directly.

Well... don't know DB2 but there's no such hour as "24"... unless that's a DB2 thing. Seems like it should be "00" instead.

Always more than one way to skin a cat, as they say, you'll see that technique referred to as a 'fork join' here.

It all starts and ends with #1 as the answer is 'no'. You can force their use via a Server Shared Container with all the caveats that brings but natively? No.