DSXchange

dr.murthy wrote:we are just discussing about transformer stage in server jobs...

And where exactly is that specified in the original post?

So... you always have four (and only four) fields in each record? Or the first four are the key fields and there can be a variable number of fields after them per type? And out of curiousity, are you wanting to build one job to handle all record types and target tables or one job per record type / t...

I know, but that 'underlying compatability' part is the rub. I guess if you stuck with generic data types, never using anything product specific either from a data type, derivation / transform rule or database package standpoint in your database and job design, you could make it work for you. Click,...

Me neither, don't have v8 to work with here.

Same way you did before with an RSA key but in the other 'direction'. This isn't a DataStage question nor problem, really, but since you ask for a way 'in DataStage' I answered it like it was.

If you really need to match that NLS format, then set the field to a Varchar in the job and change the "D-YMD[4,2,2]" part to "D-DMY[2,A3,4]" as previously posted.

Welcome! Same way you run anything scripted or command line in DataStage: Sequence job Execute Command stage, Before/After job with ExecSH, using DSExecute() from a custom routine or job control, etc. Really depends on how you need to tie this into your work-flow.

1. Well, it is a optional plug-in stage for Server, so I'm guessing it could have been installed for PX and not the Server product. If you go to the Manager and open Stage Types / Server / Database is it listed there? 2. Yes, that's how it works. 3. Can't answer this one as I use the STP stage. And ...

Stick with the 'big sql' that works rather than breaking it all up to be more 'DataStage like'. If it turns out to be 'too long' for the stage, create a view in your DB and source from the view.

And 'CLI' = 'OCI' here. :wink: In spite of the fact that ODBC doesn't really have a performance penalty any longer, I stick with the native OCI stage for Oracle since we have an Oracle client installed on the DataStage server and for the full functionality of 'update actions' that it offers over the...

'Errors' generated by a reset can be ignored. I'm assuming it does in fact 'reset' and that you can rerun the job, yes?

Sorry, it is 'showing red' where? What stage(s) are we talking about here?

Typically, one would explain the how of something, not simply state that it can be done.

FYI, just for completeness and to combine what Ray and I posted: OConv(IConv(Field(YourField," ",1,1),"D"),"D-YMD[4,2,2]") : " " : OConv(Iconv(Convert(" ","",Field(YourField," ",2,2)),"MTS"),"MTS:") The only th...

The Version Control 'repository' is nothing more than a project with some special hashed files in it - so that means it must be created on a 'DataStage server' and for that you use the Administrator. If you have more than one, you can choose the where. The only other choice to make is the name of th...