DSXchange

Is there a way to do this with Filter Command (cat file1 file2)? Tony - yes, you could take that approach if you like. Normally, one would put the filename to be acted upon in the Filename box and the command to do the processing in the Filter box. It automatically handles the 'standard in - standa...

Then it is a 'fixed width' file and should be imported as one.

bunu1977 wrote:and I dont want to use to_date here because it will slow my process.

What makes you think that? It won't.

I vaugely remember them (or some them) not being 'fully' supported. Wasn't there something about it may work but if you changed the value of the parameter you needed to recompile the job?

In any case, my understanding is all goofiness of that ilk has been worked out in the 'latest' release.

We all know you really mean Kim. It's probably just his sig that threw you off.

rleishman wrote:Sorry Craig, as a skinflint member I only got the first 3 lines so I don't what the question was (if there was one).

Doh! Had no intention of marking that as PC... undone.

I'm specifically trying to avoid the situation you found yourself in post-nuke of the VC projects. Been there, done that.

And are you really running PX on Windows so you need a batch file?

Case 1: If you are asking for confirmation - yes, that's how it would work. There will be some changes as you mentioned, like project name and create/mod times, and others that should be of no consequence. What differences are you seeing that concern you? Case 2: I wouldn't even consider doing 'para...

Done.

kduke wrote:Buy ParameterNavigator from me would save you lots of time and trouble.

How much is that bad boy nowadays, Mr Kim?

Of course! So you really think it would be safe, eh? Still got the production machine to do at some point...

Coming in late... you guys do realize you are over a year late, don'tcha?

Been pondering something and wondering if anyone had tackled this yet. Our various Version Control projects have gotten rather... fat... and most of the information in them is well past its prime and no longer useful. I know I can nuke them and start from scratch, but I really don't want to do that ...

I didn't try the 'uvregen' route as I was afraid it would think it was my server authorization code. There is no date or limit or any other value for the RTI Agent other than the additional auth code. Going back through the Server install, I had three choices: 1) Re-install - basically a 'Repair' in...

In your 'Ascential DataStage' entry on the Start menu, you'll find a link to the pdf manuals. One of them is the Server Job Developer's Guide and there is a full chapter in there (14?) on the Command Line Interface.