DSXchange

And just to head Ray off at the pass, no it's not 42.

daignault wrote:As a rule of thumb, never EVER develop a Datastage job in enterprise with 1 node.

Unless, of course, it will always be run under a single node config.

Not sure how much of this will still work in the 8.x world but do an exact search here for "OLETYPE" and go from there.

OK, I'll bite... do you not have a SysAdmin?

An exact search for "Exporting nullable field without null handling properties" would help as well.

And here we are.

The stage (or you) are using TO_DATE() to populate the target, I assume. Use TO_TIMESTAMP() instead.

Esoteric Usage Alert

YourField[1] will return 1 character from the end of the string.

OK, specifically - you are querying the 'base' Multi-Instance job (the one that always shows Compiled) rather than one of the actual instances. Use JobName.InvocationID in the dsjob command rather than just JobName.

XML should be "one long string". Only peoples 'need' that pretty printed structure, no consumer of the file will. However, the Formatted option in the stage will do something like that for you... emphasis on something like that. My advice? Don't bother, continue to let tools like IE (tempo...

Sounds like you are using $ReturnValue, and zero = successful. Use $CommandOutput instead. Are also read up here about 'Field Marks', aka the @FM system variable and the need to strip them.

Assuming you really need that output format... what is your target datatype for this? String or Date?

Nothing magical, simply check for null and if found, set to your "in-band" value otherwise keep the original value. On the way back out, reverse the check. Biggest thing is to make sure the value you pick will never occur naturally in your data. For the first check, you have the NullToValu...

Jeremy - make sure you read the XML Best Practices document at Kim Duke's website in his 'DS Tips' section. It's old but still solid information on how to solve XML problems, including yours from what I recall.

rsunny wrote:So do i need to ask system admin for the user name and password to connect to the client server?

Yes, of course.

Your log table has too many messages written to it and 'overflowed' into a corrupted state. Do an exact search here for "computed blink" to see what your options are at this point.