DSXchange

I used the command "unzip" in Execute Command activity. OK, what happened? If there was an error, what was it? As noted, the "-d" option specifies an output directory to extract everything to, however it needs to be followed by the desired directory. Otherwise I suspect it unzip...

The only thing I am "driving at" is comprehension. I missed the distinction in the conversation between named and local message handlers, sorry if that upset you somehow.

OK... fully aware of where they live. And the handlers have had to be moved manually since they arrived on the scene as your link shows. To the best of my knowledge, saying "it will not work when migrating from 8.0.1 to 8.5" doesn't sound right, rather I would say "it will continue to...

Then I'll repeat that, in my opinion, you have a procedure code problem and not a DataStage one. And again, since you and yours are the only ones with access to the code, I don't see how anyone here can help you. Have you discussed this with whomever wrote it?

I don't think you need to know what my stored proc is doing. Errr... ok. Then I think that after two pages of my "views" on the subject, I'm done and ready to let someone else take over. Hopefully in the meantime, you've actually involved your official support provider and asked them what...

To check for file existence, set the timeout to zero. Then as Ray noted, you just need "OK" and "Otherwise" triggers from the stage - the former for the file being found and the latter for it not being found. Those two triggers should also tell the generated code that you are han...

1) It just means reset, exactly the same as if you had done it manually from Director. 2) When checkpoints are enabled, that option disables them for that particular stage. Meaning it will always run rather than being skipped on a abort/restart even if it ran ok. 3) Enable checkpoints. Make sure you...

I just checked the documentation for 8.5 and there only seems to be user-defined sql functionality for reading, which to me seems... odd. Realized I was seeing the Server ODBC stage in my head when talking about all this, something much more flexible, it seems. I suppose one would leverage the "...

What throws this error, the DataStage job or the proc itself? I can't tell from your description. Can you post it in its entirety, unedited?

So... exactly the same scenario that you've outlined here but now you want to know how to script it rather than use a job? If so, there are other web forums where it would be more appropriate to post questions like that, I'm afraid.

saraswati wrote:I am getting an error

Take that error to your DBA.

Tell me one thing....The ODBC stage must be used as a source and not as a target. That's not correct. In fact, I was assuming you were using it as a target here, which is probably where much of the confusion comes from. Row Generator --> ODBC Why as a source? You said you didn't want to 'return any...

Without knowing what your proc is doing internally, there's not much anyone here can help with. I will say that if your source is truly a VARCHAR(12) and your target is truly a VARCHAR(12) then you should not be getting any such error from the proc, it should just be passing it through as a string. ...

And what does "through the job" mean? If that means as job parameters, then you are getting closer though you may need to wrap them in hash signs and whatever columns you include in the stage will be ignored. If that means as data on the input link, then you need to refer back to the post ...

More details about the job in question would be helpful here.