DSXchange

If true then that's a change that no-one here has mentioned yet. I've only ever worked on UNIX servers so never seen the Command stage in my entire up-to-8.1 DataStage life. The fact that it can run 'UNIX scripts' could be simply because of the MKS Toolkit that is installed with the product. Ask you...

Have you or have you not purchased ODBC drivers for Progress? If not, you'll need to do so to proceed. You being your company, of course.

Where are you looking at the file, on Windows?

Since you've hijacked a two year old thread, why don't you tell us what your requirements are? What kind of "encryption" do you need to do? Ain't no sense in tool talk if we don't know what you aim to build.

Regardless, seems to fulfill the "Any ideas on this to start would be really helpful" request.

Do you see row counts in other jobs and just not in this one?

God knows and google doesn't bring anything up relevant. I'm assuming it's one of those "lost in translation" job descriptions where bits get mistranslated along the way to HR. Call 'em up and apply for the job! Let us know what you find out.

The Command stage is only installed on a Windows server. You would be using the Execute Command stage and both are found in a Sequence job rather than a Server job.

So, a parallel job question that you marked as 'Server' and posted in the General forum... fixed both of those for you.

Answer this:

chulett wrote:Did you type that in by hand or use the External Parameter Helper to populate it for you? If the former, do the latter.

The "helper" is under the ellipsis (...).

Generate the error again, check the 'Copy to clipboard' option before dismissing it and then paste the contents here.

i am not taking about any business rules i just gave an example to my requirement so that it can be easily understood We know, that's the problem - and from the responses here you can see it didn't work... well, except perhaps for Ray. So are you saying you've already solved this problem? If you st...

Again, close. In the Sequence's Job Activity, you set the value of the parameter to ExecuteStageName.$CommandOutput which is what the helper would build for you. With the appropriate stage name substituted in, of course. The next issue will be the fact that the parameter's value will be 'inappropria...

times29 wrote:Then under seq_all for job2 job actvity for parameters name input_file_name i gave expression value "job1.$CommandOutput"

Did you type that in by hand or use the External Parameter Helper to populate it for you? If the former, do the latter.

Close... you need to create a job parameter in 'job 2', use it for the filename and then assign $CommandOutput to that parameter in the Job Activity stage.