DSXchange

First thing that comes to mind is why are you writing the SQL? If you let the Connector automatically generate it by setting Generate SQL at runtime to Yes, you won't have to worry about things like that. Provide the SQL only if it is something that the stage is incapable of generating. That being s...

Can you provide some... details, please? Some starter questions: 1) Define 'long time'. Only for jobs with transformers or all jobs? 2) What happens? What error message do you get? 3) Define 'long time'. Some or all stages? 4) Corrupt how? When? And for the 'long time' bits, are you remote / far awa...

I don't see anywhere that the DB2 Connector let's you control the level of locking used - however you can lock the entire table should you so desire. Plus I see a 'Lock with force' property for how to deal with any other applications that hold conflicting locks. In your shoes I'd have a chat with yo...

So not a workaround but rather the resolution. Marking as such.

No... you would have to use two (or more) 'boxes'.

Welcome. Can you clarify some things for us, please? What exact 8.x version are you running? I'm curious why you mention a Parallel job and then mark the Job Type in your post header as '390' which is a mainframe job type. I'm also wondering if you did a copy/paste your exact error message into your...

Right... SQL files do not support #parameters# in them so you've got to build / rebuild the file each run with any parameter values subsituted in.

*throws another penny in the cup*

Here I was thinking it would need to be a service but then I thought... heck, I'll just wait for Ernie.

Curious if you ever got an answer / solution for this...

not sure why you have the -l on your LS command since you are just counting lines. Guilty of this over the years for a couple of reasons. Force of habit mostly and it generally works just fine. :wink: Now, perhaps it can contribute to the dreaded "argument list too long" error you'll see ...

Not that I am aware of. You could always script something from the command line, use the dsjob functionality to get all of the jobs and then loop through them, exporting them individually. Or people have posted 'cutter' scripts over the years, perhaps something in these threads can be adopted to you...

kethya11 wrote:target have sql server datatype has sql server.

Anyway, perhaps the replies here can help, even if they are about Oracle.

CMD does not support UNC paths as current directories

Ah... so forget the "cd" part and see if a restructured command like this works:

Right... when your directory path cannot be found you are still in the CWD or Current Working Directory of the executing process. I have no idea if your UNC path is both valid and if the user executing the DataStage job has access to it. I'm suspecting it's not or it doesn't. Regardless, I'd suggest...

Is there not someone you work with that is Java proficient and can help?