DSXchange

No, though I guess you could use the Java PACK and one of the existing Java applications "out there" to access AD/LDAP from DataStage. In version 8.x one of the options for user authentication is to use LDAP to access a user registry such as Active Directory. However, this is configured wi...

You can rename the copy, again off the right-click menu.

Get yourself on a DataStage training class, sooner rather than later.

It drops common key fields because they are identically valued and identically named. You can avoid this by using different naming conventions on the two inputs. A Copy stage is the most efficient stage for simply renaming columns.

I believe this is another thing addressed (to be addressed) in the next version.

This is a database error. Presumably your two environments are pointing at different database instances, or at least at different database schemas. Check the nullability of the 34th column in the 15th table in tablespace #4 and in the corresponding column/table in the other location.

The next version will have server-side export and import.

There is a non-IBM product out there from a company called Compact Solutions (partnered in Australia by Zenith Solutions Pty Ltd) that has a tool which can decode other ETL products, like Informatica and Ab Initio, and put their mappings into the XMETA database so that they can be seen by lineage an...

There is a non-IBM product out there from a company called Compact Solutions that has a tool which can decode other ETL products, like Informatica and Ab Initio, and put their mappings into the XMETA database so that they can be seen by lineage analysis from Metadata Workbench.

These problems are related - the report templates can't be loaded into the remote DB2 database. From memory, the ypcat error can be avoided by including the name and IP address of the DB2 server's host machine in the /etc/hosts file. Even if you ordinarily use DNS. Don't forget to flush the DNS cach...

It is there, in the Processing folder. Both for server jobs and for parallel jobs. (And mainframe jobs, for what it's worth.)

as a constraint expression.

Once you introduce validation you lock in the column name into the validation expression. There is no mechanism for validating an arbitrarily named column. If you can somehow map the arbitrary column onto a consistenly-named column then there might be a solution for you.

Yes you can, as my response shows. It's up to you when you get your premium membership. It's not expensive (under 30c (Rs12) per day) and worth every penny/paise).

Should the source be schema.sequencename.NEXTVAL ?

Declare all the fields as VarChar when importing the "table definition". Use a Transformer stage. Use Derivation Substitution to apply a Trim() function to as many VarChar fields as you like with a single operation.