DSXchange

The configuration does not contain the invoking node bldbt75041. If you start the job on node bldbt75041 then at least one of the nodes in the configuration must have this node as its fastname. This becomes known as the conductor node. You can force all processing to occur on dpengep1 if you wish, b...

Meantime as a workaround

I suspect that this was the initialization pane for stage variables. So illegal value for init is a perfectly valid error message.

The sequence has two jobs, one to read the table name based on the file name (presumably a sequence parameter) and load that into its user status area. The second job does the load, with the table name passed as a parameter value whose value is obtained from the $UserStatus activity variable of the ...

Does the metadata in the link properties mention these columns that it's "not considering"?

No. Communications are established between the relevant player processes (the operators on each end of the link in which repartitioning is occurring) and they pass data to other nodes using APT_Communicator class (if I remember correctly) using TCP port numbers beginning at 11000 by default (again i...

In a sequence read the value then pass it to a job that includes parameterized SQL within the job design itself. Or have the sequence generate the entire SQL statement and pass that to the job as a parameter.

I have just finished installing just that combination. We went with 8.7 primarily because of the workflow feature in Business Glossary - the client prefers to have a Development Glossary that other users can't see, plus a governance (approval) process for publishing terms from there.

I doubt it.

These "cryptic names" are generated (guaranteed unique) keys to other tables in the metadata repository database.

Why would you ever expect it to work? The scope of a job parameter is the job itself. The SQL file is external to the job.

Make your VarChar larger in the job metadata.

Do the lookup in a sequence and pass the table name to the job as a parameter.

Job control is the old way of doing it. You end up adding source code to run jobs. You can edit this code using DataStage API functions. However, it is NOT an alternative to a job design, it is completely separate from the code you might place in a Transformer stage. On that basis, your question abo...

(What James said)... and, should you ever need to re-partition, you will need to move rows across the network.

Worth logging in today. Learned something.