DSXchange

At some point in the future that "no support" statement may have to be rescinded. They are definitely looking at password policies for the internal registry. "In the next major release" [after 8.7] according to the IBM tech note below. I have to assume this means in the internal...

Jayanto wrote:how do I determine my ODBC Driver's version?

See this coincidentally titled IBM tech note:

How can I find the DataDirect ODBC driver version used by DataStage jobs?

http://www-01.ibm.com/support/docview.w ... wg21574486

Try it out and let us know what you find.

absatyam wrote:need your urgent help

Please help!

Where's the quote about the cost of providing urgent help?? I thought you guys had that thing automated...

The dsjob command can perform similar functions to the API functions Ray outlined.

2 MB is rather small. Are you sure the limit should not be 2 GB instead? If you're having trouble adding a timestamp on the reject link, you could insert a Transformer stage before the Lookup stage, and derive the timestamp there. If the row is rejected, then it already has the timestamp. If it's no...

Automatic time zone changes are not built-in to any parallel job functions. If you know the time zone offset, then you can use either of these built-in parallel jobs functions:

TimeOffsetByComponents()

TimestampOffsetByComponents()

Search on Data Warehouse. If you're not doing DW work, then it will not apply so much...

Try using the Head stage or the Sample stage. They operate in parallel, so any record count you give is per node.

I'm not going to say it's impossible, but it's still not going to be supported (same answer as before).

I think extra dots will confuse it, as the dot is a delimiter. If you're set on using a dot, check with IBM. You may be able to request it as an enhancement for a future release. If other people are not requesting the same thing though, then I don't think it's too likely to be added.

Go into the web console as an admin and grant the DataStage Admin role to the developer ID. Then it will no longer be a developer-only ID. You should be able to use the Command button after that.

See if this IBM tech note is at all related. It mentions a similar problem with the Oracle Connector stage. JR40765: ORACLE CONNECTOR: THE ROWID ROUND ROBIN PARTITIONING INSERTS THE RIGHT PARENTHESIS AT THE WRONG PLACE. http://www-01.ibm.com/support/docview.wss?uid=swg1JR40765&myns=swgimgmt&...

Do you mean to say it works for an admin ID like dsadm or isadmin but not a regular developer ID?

New IBM tech note regarding the Redhat memcpy() fix:

http://www-01.ibm.com/support/docview.w ... JPZ&mync=E