DSXchange

Big assumption.

Yes, if indeed there is a shell script involved here. Kind of hard to tell from the original post.

Did you try #parameter#+1 ?

They're not 'held' anywhere by DataStage. You can export whatever you like and hold it wherever you like on your client PC via the Manager. So, best to export just the source (Job Design) for the entire project, and then use your editor of choice to search for the table name. I prefer UltraEdit as i...

Welcome. You'll need to be more specific - would not simply setting the parameter type as Encrypted work for you?

Ah... perhaps so. That was (technically) a Server answer - but why would something as trivial as this need to be a PX job?

Sure, all you need is a dummy stage variable to make it compile, and a constraint to control the number of records it spits out.

sud wrote:why did you multiply 3 and 16 ?

Simply because 'hexadecimal' is base 16 and then I did the 'tri' or 'triple' or 'times 3' part.

All sud means by their improper use of 'URL' is the filename, something we're already checking. Of course, you could always write your own version, either scripted in your shell of choice or a custome BASIC routine. No real need to reinvent the wheel, however, as the WFF stage works just fine - unle...

If it was 'ok' this would all be working for you. As a test, try hard-coding the pathname in the stage and see if that works.

I asked about the " - A" because it makes it look like it is part of the filename and that you have spaces in it - and I don't think that is supported, hence the question.

And I just wanted to convey that you can if you first copy it out to another job.

but i doubt you can custom code job control of job sequencer with basic code, you cant edit the code of job control that is developed automatically. People have been building custom job control code in BASIC for years, well before the Sequence job came into the picture. And while you can't edit the...

sud wrote:Though, the performance of the parallel routine was much better than the build op.

Up until the 'Boom!' part, of course.

True. Easy enough to get just what you want from that output, but... true.

Check your Job Parameter value, it obviously doesn't like it. What is the - A supposed to be/do?