DSXchange

Wow - thanks for all the input. I'm not convinced though that the parameters aren't being recognized -or translated- in the execution of the script since the echo statements I already have in there echo back the correct values of the parameters I'm sending it. Really? $CB and $PT echo out correctly...

That brings us to the question, how can we pass a value in a transformer, for example, value contained in a stage variable to a newly created job parameter in the middle of a job and use that in the sequential file name box? It's been said already and I'll just add to the chorus - you can't. The na...

Sorry, should have mentioned that as it is the official 'workaround'.

As stupid as it sounds - you can not pass Job Parameters to a script using the Execute Command stage. It will look like it's working in the log, but they do not get translated in the actual script execution.

Painful bug been there since Day One with the stage.

It gets confused. When you send 500 records at a time, it can't always correctly tell you which one was the problem child. Sometimes it doesn't even give you the correct count.

Yup!

'Last' is an aggregation method in the Aggregator Stage.

Do you have Row Buffering turned on? Try it with it off.

If your 'Array Size' is greater than 1, change it to 1 and try it again.

Kinda going slightly OT here, but how would I find all jobs where a certain job parameter name has no default value?

Which part do you need help with? Your 'Contents of the sequential file' becomes a Job Parameter and is used in the OCI stage just like Ray illustrated in his first example - surrounded by pound signs (#) in the where clause. You'll need something, typically a piece of Job Control code, to read the ...

'Truncate' means truncate. The table is logically cleared almost instantly.

'Clear' means delete all records. This is transactional and can take time, rollback, etc etc.

The simplest 'trick' to get the last day of a month is to still set the day portion to '01' like you do for the first day. Then, bump the month to the next month and increment the year if you need to as well. Then subtract 1 day. For example: 200405 -> 2004-05-01 -> 2004-06-01 -> 2004-05-31 In DataS...

I would think you should be able to build three hash files and check them in order to get the data you need. Both of your conditions, where you either get one row or more than one row, can be satisfied by the hash by taking advantage of its 'destructive overwrite' behaviour - bring the keys in in de...

Not by much, it would appear.

Put this at the top of your routine:


Or more properly: