DSXchange

Millions? If you are doing this as some sort of surrogate key creation process, then 'random unique' numbers are definitely not the way to go.

That 'message handler' advice is only valid for the Enterprise Edition, something I mentioned because you posted in the EE forum.

Packed data (any of the COMP family) isn't EBCDIC nor ASCII - it's packed. And 'converting' it in any fashion will corrupt it. You just need to 'unpack' it.

Define the input field as an appropriately sized string and then use DataTypePicComp (since it is signed) to unpack it to an integer.

Whoops, that was what I meant but not what came out of my fingers.

Damn fingers.

Ask whomever wrote that there was a patch for the patch number. Post the question in their thread or explain the issue to your support provider and let them figure out what patch is applicable.

Wait... so is the job actually starting and processing some rows before it ends with that message? I thought it was failing to start but a closer reading of the message implies it was running and then 'finished' with that status.

If so, then I'm barking up the wrong tree.

Bummer. That's kind of... stoopie.

From what I recall, the original version was called "client switcher" and required a batch file but it hasn't worked like that for some time now. AFAIK.

Time to mark the post as Resolved then, use the big button at the top of the screen.

Yes, as long as you install them to two different locations and also install the Multi-Client Manager as only one can be active at any given time.

No. That "99" says it is not in the right state, i.e. the job has to be compiled and "not running". Double-check your logs, I'm still betting something is calling it while it is already running.

Read only != cannot see code. I don't have access to 8.x so are you saying the code cannot be modified or you literally cannot see the underlying code?

I wouldn't worry about the 'deprecated' message, sounds like your problem is the job is not a multi-instance job and you are trying to start it while it is already running.

Welcome! From what I understand you cannot reference an environment variable directly in a derivation. However, you can use the GetEnvironment function to pull that value into the job.

ps. No OCI stage needed. :wink: In Server you can 'source' from a transformer. Add a dummy stage variable as this is what allows the job to compile, create the appropriate metadata on the link and then constrain the output to the number of rows you want generated by the transformer. For example, @OU...