DSXchange

NOTE: I changed the status of this from "Workaround" to "Resolved" as that is exactly how you find the information you need. We can revisit this discussion and change the status if the official approach doesn't work for you.

As noted, you can use ODBC if there are input parameters but there's no way to return anything more than a status to the job. Seems to me you need to look into doing something from the command line, a script to call whatever CLI you have for SQL Server. This will be complicated by the fact that your...

Dsexchange users? Yikes!

I think Eric is referring to this Redbook, but it was written when the 8.0.1 release was the latest and greatest. Perhaps there's another. Regardless, being asked to create a document on something one knows nothing about seems a little ridiculous. Never mind the fact that there's already a huge amou...

Moved to the PX forum.

vikram, can you please edit your original post (click on the Edit/Delete this post link just above it) and add the missing information we need - version, job type and O/S of your server.

Two points: I'm assuming the MKS Toolkit enables that date command on Windows and the File Attachment property of the Notification Activity stage allows the use of parameters. It's typically the body of the email where people find they can't use'em but have a need to... then direct calls to DSSendMa...

DataStage allows you to use either, from what I recall.

$ReturnValue is the exit status of the command, while $CommandOutput is whatever it writes to standard out. Can you confirm what exactly it is you get as the $CommandOutput value for the function listed? It will be logged as part of the same log message created when it is executed.

Yes, definitely. Any kind of "real time" protection can affect any application's performance, sometimes even drastically. Think about it checking everything being written to or read from disk and you'll see why. We've even seen reports here of AV programs removing / quarantining vital file...

Probably simpler in a Server job via a routine than in Parallel unless you build something in C++... and easier still if you just use something from the command line, I would think. Have you tried to get your hands on a hex editor? Many are freeware. Have you tried an "octal dump"? The com...

OK. 1) Then you'll need to build them from the data and ensure they only go out as the first row. Turn off any "column headings" the stage might add. 2) Do you know the maximum number of occurances? You could "code" for that and then remove any empty columns. 3) Not quite sure wh...

I've already provided those details, twice now.

You however, have not. You have yet to specify where the parameters you need to pass into the proc need to come from. That would go a long ways towards wrapping this up.

I know, I know... but sometimes that's what you'll have to do. Maybe you'll get lucky and there's a patch that will fix things right up for you. One can always hope. :wink: In the meantime, gets your ducks in a row - logs, job exports, data dumps, whatever you think might help or they might ask for....

Well... what values did you get when you tried? And just to confirm - what is the target here, a flat file?