DSXchange

You might want to consider using project level user-defined environment variables from the db credentials. There the password can be encrypted. The jobs would use $PROJDEF as their default value.

That zero already is a zero - simply moving it to a number field should "handle" it just fine. What issue are you having?

Internal quotes in job parameters tend to get stripped when passed into the job unless escaped properly, which usually happens when people try to pass in SQL. For example, this string could be problematical: where ColumnA = 'Fred' and ColumB = 'Ginger' You may end up with this instead: where ColumnA...

Do you have access to that project from Director? That should show you that information from the most recent run. From UNIX you'd have to use dsjob with the various "-log" options to fish out that information.

I think you need to put something (anything) in the boxes to shut it up and then it will ignore them.

ExecSH before job or Execute Command in a Sequence job or using DSExecute() in a Server routine or... many ways to skin that cat.

Sure, have DataStage run a script that does the sftp or scp transfer. You will, however, need to set up the proper RSA keys between hosts so this will work in a 'secure' manner. Have that conversation your SysAdmin.

I believe the Sequential stage can handle that if you set the extended properties correctly.

Worst case you could run the job with a warning limit of 1, it seems to me.

pandujoy wrote:...infact its "sftp"....is there any diff.

Yes, BIG "diff" and no the stage does not support secure ftp.

Or in a Sequence job.

Wow, stop and take a breath occassionally.

Can you post your syntax, both before and after?

One doesn't, only a moderator (or I guess a 'content editor' <waves to Andy>) can actually move posts which is why I asked them to re-post it. And for whatever it is worth, I've stopped replying to posts that are in egregiously incorrect forums... I mean, how hard is it to get that right? Or at leas...