DSXchange

how can i schedule a one job at after 3 months. I don't have any DataStage access but you certainly can schedule as far out in advance as you'd like. It only shows you "one month" for things like the "Every" scheduling option where you say "Every 3rd of the month", but...

Confused as to how that actually fixed the problem as there was no need to return multiple anything in the example given, just one.

Not all who respond are Rays. And do it just like you did for Cmd1 where you bound in the value of parmDBPass for example.

Specifically meant a new partition or mount point rather than simply a folder, they are more akin to your existing (I assume) separate drive letter. Data files will need to be 'local' to the ETL server to be accessable but make sure you understood my point about not using the same area that DataStag...

Do something similar to what you are doing, a dedicated separate partition for your data files would be typical. So as noted, not something off the root filesystem and not where DataStage is installed... someplace where filling it up would not be catastrophic.

You need to 'bind' the values for them in when you build the Cmd3 string.

Note: I did post the topic earlier but the answers were use of agregator with min max dates. But here we need to handle 200 millions of records in input file so please suggest some optimal method regarding this. I'm curious... did you even try using an aggregator to do this simple min/max grouping?...

Hmmm... based on the advice I've seen given out over the years, I'm thinking the documentation may be incorrect. That or the advice.

Force the Sequence to fail if need be, for example with a Terminator. The 'automatically handle' option can do that as well, but you'll need a trigger from the last object for it to be handled... run that to a Sequencer.

In other words, the 'mask' you use in StringToDate() must match the incoming string's format. And that will get you a Date which has no external format. If you really need something in an external format like YYYYMMDD you'll need to also use DateToString() afterwards, again with the appropriate mask.

That would depend entirely on the version. And as noted, you're much better off creating a simple csv file which Excel will happily (and automatically) open and convert.

Make use of the IsValid() function. That and ask yourself - what does an invalid varchar look like?

Put quotes around the tablename.

You need to ensure that each 'segment' of the date is the correct number of digits as you've found. That means breaking it up, padding the ones that need a leading zero, putting it back together and then calling the function. That or enforce a Date format in the spreadsheet that lets you not need to...

So i need to create DSN for each DB separately but this is a very difficult to maintain. I'm curious why this would be 'very difficult' to maintain. To me, this is a normal and expected part of communicating with databases and really shouldn't be all that onerous. Also, are these multiple instances...