DSXchange

Yes, definitely. The job may technically finish but could be writing records to their logs for all that time. Simple enough to check - purge them and let us know.

You would use the ODBC stage. Other than that it should be a fairly standard ODBC configuration that's needed, but to be honest I've never set one of this type up.

That makes no sense. Are you sure there's nothing else between the two or a before/after routine that is skewing the results?

Yes, success. With the "-jobstatus" option you are asking it to return ds status codes:

1 = Finished OK
2 = Finished (See log)
3 = Aborted

Etc etc. All values have been posted here and you can also find them in the dsapi.h file under the DSEngine directory.

There is no procedure and this is the gamble you take when working 'under the covers' like that, any new version can break it. Time to change your old job, it seems. What exactly are you getting from DS_METADATA and what exactly are you doing with it? Perhaps we can come up with a more proper way to...

So go delete yours and then they can delete theirs.

Sure we're not talking about the "KBA Job Control Utilities"?

True, that 'semaphore file' approach is the best way if you can get your source to agree to do this for you. Otherwise you get to play the silly games we've talked about or just cross your fingers and hope it's all there and that your short read will fail the job.

without doubledouble quotes in definition echo command is not giving correct result. What the heck does "not giving correct result" mean? What result does it get you? :? And yes, DataStage is notorious for stripping quotes from string parameters so you need to escape them in some fashion ...

On Windows? Not sure. There are UNIX utilities like "fuser" that let you know if a file is "in use" or not, with the assumption there being that in use means still transferring - perhaps there are Windows equivalents? Old School: looping check of the file size. Check size, wait, ...

OK, then you just need to get the syntax right:

-param A=${A}

No spaces around the equal sign, btw.

$ is for environment variables, sounds like you should just be passing in the string value itself.

-param A='xxxxxxxx'

I'd check with your official support vendor to confirm what your options are, and perhaps also poke around on the Data Direct website which is one source of ODBC drivers.

Why not change them to... Numeric?

As far as I know, you'd need to purchase either an ODBC driver or an IWay Adapter to handle those. Or get your COBOL people to dump them for you.