DSXchange

Interesting... memory is a harsh mistress. I thought all the tips we got on how to handle situations like yours was in the pdf document I mentioned. Now that I actually go back through it, I see that wasn't the case. Going back through my collection of DataStage flotsam and jetsam, I found that what...

ray.wurlod wrote:OK, your site has not licensed server jobs. They have a server licence; they've just decided not to use it.

That's just crazy talk!

1. In steps 4 & 5, I cannot seem to use parameters in the tablename portion of the user defined query. For example, one of my tables goes as follows: UPDATE UCWS.ADM_ACCT_PERIOD SET TRIGGER_STATUS = '0' WHERE UCWS.ADM_ACCT_PERIOD.SEQ_NUM = ? AND UCWS.ADM_ACCT_PERIOD.STATUS_FLAG IN (1,2)...

Is this related to this thread by any chance?

snassimr wrote:Why IBM doesnt provide Java for Transformations ?

Does... Java PACK.

Just... create one, or request the same of an SA. There's no such thing as a "DataStage User" per se, they are just normal operating system users that DataStage authenticates against.

You can build a routine to take a date as one of three inputs and then check to see if it is the "Xth Y" of that month. We built one that will generically handle any occurance of any day name... however, didn't set it up for 'Last' - just 1st Monday, 2nd Friday, etc. We then run a Sequence every day...

If all you are using is the Director to create cron entries, then it becomes a manual effort. You tell it which dates are the dates to run in any given month.

Yah, except for that it should work fine.

Huh... quite a number of posts on the subject that a search should turn up. This one, for example.

Lance, the file is (was) called dsclient_xpsp2.zip and you can reference ECase 60128. No clue if it's still out on a website anymore, probably best to contact Support and ask them... then let us know what you find out.

Have you read the XMLPACK_20_Designer.pdf document yet?

First question from me would be - what version of the Oracle database are you working with? 8i? 9i? A mixture of both?

Wouldn't be a problem, per se. Make sure both the DDL and the DML statements use the same table name job parameter. You'll also need a DROP TABLE command or this will only work once - after that you'll get an 'Object already exists' error. Also, make sure the stage generates the DDL and not you, oth...

I believe that actually leaving required fields (like Date or Integer) empty in a Job Activity stage when they have no default in the actual job will generate a compiler error. You'll also see this particular 'not appropriate' error if you supply a parameter value to a List and it's not in the list ...