DSXchange

I'm going to guess that you're doing a default implicit conversion. Implicit conversions will frequently generate a warning message (harmless and preventable). Using an explicit conversion will usually eliminate the warning.

Please post your transformer expression.

Mike

No bug. Just standard parameter behavior. A job resolves its parameter values when it starts. Changes to parameter values after a job starts won't be recognized. In your case, the job sequence read the values file when it started executing. Any changes that were made to the values file after that wo...

Kind of a waste to create and wait for a dummy file... and I suppose you need to clean up that dummy file before your next cycle. A simpler design is to have the executed command write the row count to stdout and then put a Nested Condition activity after it to direct flow based on the row count in ...

Define your column as NVarchar(10) or use an unbounded Varchar. The length for VarChar specifies maximum number of bytes. The length of NVarchar specifies maximum number of characters. UTF-8 characterset has variable-length characters... so 10 characters can exceed 10 bytes. I prefer unbounded Varch...

Create yourself a little utility using your favorite tool ksh, perl, server job, parallel job, BASIC routine, or whatever. Your utility will read through the schema file looking for decimal columns and generate all of modify specifications that you need. Then just pass all of the modify specificatio...

The default read method in the sequential file stage is "Specific File(s)". You can specify more than 1 file if you like. You'll have to experiment to see how you need to delimit the file list and whether there is a max size on that property. Craig never forgets anything, so I had some dou...

How much physical memory did you have for Linux vs. what you have now on Windows? And is the concurrent workload about the same on the 2 servers? The same article that you found indicates that the memory allocated to the lookup needs to be contiguous. Perhaps Windows is unable to deliver as much con...

If you have read access to XMETA, here is some SQL that I've used in the past: SELECT J.DSNAMESPACE_XMETA AS PROJECT_NAME, J.DSJOBTYPE_XMETA AS JOB_TYPE, COUNT(*) AS CNT FROM XMETA.DATASTAGEX_XMETAGEN_DSJOBDEFC2E76D84 J GROUP BY J.DSNAMESPACE_XMETA, J.DSJOBTYPE_XMETA ORDER BY 1, 2 Mike

As qt_ ky suggests, try SyncProject.

It appears to me that the tree in Designer gets populated from the local repository; while the Director tree appears to get populated from XMETA.

The 2 repositories are probably out of sync.

Mike

Nice job so far Koti. I tend to like using parameter set values files to support my generic multi-instance RCP jobs since it provides a nice container for organizing everything that needs parameterizing. Now you can appreciate the challenge of handling a variable number of keys. And you also have th...

My Requirement is to replace these many transformers with some other stage to improve performance of my job. That isn't the source to target mapping requirement that your job needs to satisfy. You're so far out in the weeds, I'm not sure how to bring you back in. Nothing you've mentioned so far sug...

Perhaps you should explain what you're trying to accomplish in your job design. I have no idea what you could possibly be doing with 70 transformer stages. You do understand that a transformer stage works at the record level. You can transform 70 fields in 1 transformer stage (i.e. you don't need 70...

Review the documentation for the Ceil function. It is not a rounding function.

You could try out the DecimalToDecimal function with the round_inf argument.

Mike

That most likely depends on your plan for handling a variable number of key fields. I opted for using a single concatenated key called KEY, so the partitioning and sorting was simply by KEY. I found a generic RCP-enabled shared container to be more useful than a generic RCP-enabled job. Gives you mo...

No mistake on your installation. You just haven't done the post installation steps necessary to enable database access from the engine computer. The engine computer is a database client. You will need to install and configure a DB2 client instance to use the DB2 Connector to connect to DB2 databases...