DSXchange

Especially with the Disable BBCode in this post option checked.

I can do the same in run time...But our testing team needs this requirement to be set in the job itself. What does this mean, exactly? How are the jobs run in test? As you note, there is a "-warn" option for the command line 'dsjob' function where you could set it to 1. The limit can also be set wh...

The DRS stage supports multiple interfaces, that's the Dynamic part. We're wondering what interface you've selected in the stage? My laptop is shutdown right now or I give the explicit name of the control, but it's where you set Oracle, ODBC, etc.

MCM is the Multiple Client Manager and ships with the latest products on the Client CDROM. If you have installed multiple clients in separate directories, you can use it to 'manage' which Client version is the active version. You can only have one version active at any given time, but it will adjust...

I've found that I also need to set $LC_CTYPE to C.utf8 to get this to work for me on my server.

Haven't had to do this, but I'd try '010' if you mean linefeed or '013' if you mean a hard return.

The NLS_LANG approach is the correct one. How exactly did you try to 'set it' in your job? You should be setting the value in the Administrator as a User Defined Environment variable, adding it as a parameter to your job and then overriding the default value there.

He didn't tell you because there is no other answer. A least I've never heard of one. Trick question. Be happy to be proven wrong, however!

Keep in mind that the DB2 stage will want dates in internal format from what I recall.

There was a presentation at AscentialWorld 2004 that went into how one particular company (BCBS?) leveraged distributed hashed files. It was very interesting, pros and cons, routines, the whole nine yards from what I recall.

I'll have to see if I can dig it up.

Best answer is to build some form of 'job control' that negates the need to worry about default values across projects. A central store of some kind where parameter values are automatically assigned at runtime is what is typically implimented.

Another option of the 'brute force' variety for a global / mass change of default values is the old 'export / edit / import' techinique. Perform a full export of the job's source then edit the .dsx, doing a search and replace of the values. Lastly reimport and recompile. Not all that elegant, but do...

No, there's no other way. You need a stage variable so the job will compile and a constraint so it doesn't generate an infinite number of rows.

If this is a Server question as you've marked the post, the first response you're going to get is "there is no Join or Lookup stage in Server jobs and Merge is for files". Actually, you just got it.

So is this actually a PX question?