DSXchange

Unless I'm missing something, that just sounds like a Sequence job with the Start Loop and End Loop stages. Have you tried using them for this task?

Sorry, my advice was incorrect - I was thinking we were talking about a Sequence job. And External Source is only for PX jobs. What exactly is the stage doing for you in the job?

You are correct - Windows only for the Command task. You should be able to swap it for an Execute Command task.

Isn't that limitation based on the "bitness" of the software? 2GB only in the 32bit version?

Once more with feeling...

It's not an option when it won't solve your problem. As noted, there is pxEReplace source code posted here for earlier versions. If you want a command line solution, look into sed or awk rather than tr.

OK. Have you tried using EReplace() or the pxEReplace() version posted here? As noted, Convert() is not the correct function for the task and I believe tr is the command line equivalent to convert (one character at a time) so inappropriate as well.

TimeOffsetBySeconds() is perfectly valid. What exact version are you on?

Is this for XML that you are generating? If so, those substitutions should be automatic.

He did. Which part is unclear? There are plenty of examples of OConv() syntax here or in the documentation if that is an issue.

Not a DB2 guy, but are you certain the instance is configured to start automatically? The link is specific to another component: On Red Hat Enterprise Linux 6 (RHEL6) systems, the DB2 Fault Monitor Coordinator daemon (db2fmcd) is not restarted after a system restart. As a result, DB2 instances are a...

Sure... just trying to say that I believe in this case they're not required and thus not part of the problem.

You know, I used to religiously follow those steps to take parameters from the current job or job control and then pass them to another job. One day, I accidently skipped the 'get param' part and it still worked. Meaning they were there and accessible, I believe the get is only needed when you need ...

Once you checked "fixed-width" it is ignoring your delimiter and the fact that you think there are varchar fields and reading them as char using the display size to know how long the fields are. This statement worries me: "I can define all columns as char and it works but I would like...

Yes, how else will it know where each field ends?

And what "same settings" work in a Server job? The options there are different, can you spell out exactly what you are doing in that stage?

Welcome! First, as a Best Practice I would suggest you use a Sequence job to accomplish this rather than putting it in another job's Job Control tab. Visibility is one issue, so is restartability. However, first suggestion would be to check that ErrCode value and use DSLogInfo() to record the result...