DSXchange

Not totally surprising. Since the parameter is optional the SQL should be crafted such that it can stand alone if a value is not provided.

If "not recognizing values" means you are losing the quotes, check here. Otherwise, please explain.

Educate them. In other words, that or upgrade if you want to write native Excel files rather than csv files. Or purchase a converter that runs on UNIX. Or just stick with creating csv files as most people do.

Basically, they are completely different under the covers with the Connectors being 'new' and which are what you should be using, while all other types (including the Enterprise ones) have been deprecated.

abbhi wrote:when im trying to find downloads and media page its asking for site number? what is that ?

That's the part that let's them know you are a legitimate owner of the software. Find out what yours is.

And yet the prepared SQL with the bind variable is exactly what I'd expect to see at that point when the DEBUG message was written out. After the SQL is prepared, each time it is called the bind variable is replaced with a value from the input stream. I'm surprised that that is "not working&quo...

Or looking into getting your hands on UNIX ODBC drivers for Excel. While primarily used by people to read Excel files, I would imagine they could be used to write them as well.

[shrug] No, not really. I guess just because it involves exporting the entire project, searching for a string and then working back up from there to find the name of the job. Getting a query against DS_JOBOBJECTS would be much more better. Or as I've mentioned many times over the years, we automated...

Ah... so they've "fixed" that, good to know. Yes, as Eric notes you should be looking in the export, can't get by with stars there.

Seeing as how you are saying the metadata was "manually entered" I'm assuming you already tried #2 and it didn't work for you, even if you have the metadata saved in the repository. If I can find my DS_JOB notes, I'll post them but someone like Ray will probably wander by and pony up some ...

... or look in the job's log. From what I recall you'll see the 'encrypted' value there rather than the stars you'll see in the prompt.

Thanks, I also opened up a PMR asking about this trigger option. Not sure why it's published and doesn't work. I only found this documented in the 9.1 release... is that what you are running? And did you see in the documentation for it that they use "if" several times, meaning it may not ...

8.1 is old enough that you will probably run into changes that affect your jobs, typically where code was tightened up. You may also find things that no longer work as you expect which typically means you've been relying on a bug that has since been fixed. As noted, an extensive test will be require...

Short answer? No.