DSXchange

No, by default (which is what I assume you mean by 'implicitly') DataStage pads with NULLs which are I assume what the boxes are in your target. You want the fields padded with spaces and to do that you'll need to explicitly set the environment variable noted to "0x20".

First off, confirm the data types of both your source and target fields. If they are both not CHAR fields, then this discussion is moot. If they are then you really should be padding with spaces not nulls.

Your example looks wrong for the description posted... -11 months? :? It would probably be helpful to know what you've tried already, for example did you give DateFromDaysSince() a try? Granted you'd have to use 30 or 31 for the number of days in a month, but it would get you... close. I'd also be c...

If I felt this discussion was something specific to the PX product, I would have moved it already.

This is a perfectly appropriate General topic. Carry on!

That variable was set to 0x20 I assume, if you are getting spaces as the padding character. To switch back to null padding, you would set it to 0x00 instead.

Note that this only applies to CHAR fields, not VARCHAR fields.

Nikhil - please start your own post so we can know the details of your 'similar' issue.

So Teradata needs the date in internal format? Don't recall hearing that before. Have you verified that you get the correct date in the database rather than it works because the job no longer throws the error?

srinivasudatastage wrote:Conversion is not required for your senario.

we can't convert integer to varchar.

a) yes it is
b) yes you can


ps. they're going the other way (varchar to bigint)

Some body is incorrect. Investigate the StringToDecimal() function.

1) Use a Server job to fetch the parameter value. 2) Write the parameter value to the job's USERSTATUS area 3) Assign all downstream job parameter values to $UserStatus from the Server job. You'll need to build a little routine to call the DSSetUserStatus function but the code for that can be found ...

Well... there is an actual "Orchestrate Guide" but according to Ray you have to request it from your support provider.

It's because of the aggregation you are doing in the source SQL, in essence creating a calculated column. While you may know that the column being aggregated is not nullable, DataStage makes no such assumption about the result and assumes that any computed field can be null.

Welcome. :) I have other co-workers who have Director installed locally (i accesse a remote computer). And they can see the jobs and Director works fine. But with i try to access remotly to the computer with the Director, the jobs don't load. Thanks for the detailed explanation. The fact that it wor...

Well... without a more definitive explanation of the issue, we're just guessing. How are you running the script after the Exception Handler - the Execute Command stage? If so it should wait for the script to complete before moving on to the Email Notification unless you are doing something unusual t...

I'm not sure how far you are going to get past this: I have installed datastage 7.5x2 on windows 7 ultimate OS. That version is ancient and specifically architected to run on XP. I do not think it was architected for XP. XP is for client but the server has to be Windows Server 2003, I think. You ar...