DSXchange

So, are we talking about a "grid" here? If not, please explain what you mean by "dynamic config file configuration".

Your ExecSQLProc routine is a user-written custom routine, something we wouldn't know anything about. Find and double-click on it to see what it does and needs.

See, like in the Monitor? No. They can be recreated, however, for a Server job from the 'finishing' log entries from those earlier runs with a little math. A PX job gets more complicated (and this I've never tried to do) but I believe you'd need to farm the 'consumed' and 'produced' log entries wit...

Confusing. :? I'm really unsure exactly what it is you are trying to accomplish. Storing the 'previous value' is simple and is just a matter of setting it last as you've done. However, the "if-then-else" logic you are doing is what is tripping you up. Can you explain in words what it is yo...

In the meantime, have you tried searching for "file is locked" or "Error setting up internal communications"? There are several discussions here on those subjects.

Do a "long listing" in that directory, you should find that your "PXEngine" directory is actually a link to the current version. Something like: $ pwd /appl/Ascential/DataStage $ ls -ld PX* lrwxrwxrwx 1 dsadm dstage 40 Jul 23 2007 PXEngine -> /appl/Ascential/DataStage/PXEngine.75...

I'm guessing you are missing the point that you posted this in the wrong forum. Perhaps we can get a Moderator to move it for us?

So... to make sure we understand, you made an ODBC change to a working job (IP change) and now it no longer works?

Is it possible to start a new post when questions become unrelated to the current topic?

Is this an RTI / SOA / WISD job?

Nothing specific to DataStage, you would issue the same command as you would directly in the database or from your favorite client tool - possibly 'after SQL', possibly 'after job' or even as a separate scripted step post job.

If you still have issues you should take this to your Admins, whomever is mounting the Windows drives, and see if their problems are causing your problem. Otherwise, a couple of points. Is that "xxxx.archive" filename shown as your target a directory? It needs to be. Also note that while y...

Ah... so the Windows 'Command' stage is a Server job stage? Figured it was yet another flavor of Sequence stage, which didn't really make much sense to me.

Right, the name is set when the job starts so it must provided at that time. You'll either need to pass it in as a job parameter or arrange for the file to be renamed post-job.

I don't believe so. The other thing to note is the issue occurs in all projects on both servers, so if someone did this they were very thorough.