DSXchange

No, the 'protection' - which in this case is actually 'ReadOnly=1' - comes along for the ride during the export from a Protected Project. If you wanted to lose it, you'd have to edit the dsx before you imported it anywhere else.

ps. Interesting that QA is protected but Production is not.

Are you and "kum_d" working together on this? If not, do you have DataStage installed on a UNIX server? If so, there must be someone in your organization that can help you with a simple shell script like that.

I was supecting that we might have to install multiclient manager first, then 7.5 version, but not 100% sure about that. No, installing it 'last' is perfectly fine. Are you certain it didn't actually install successfully? It's been too long, but I vaguely recall the installation being somewhat... g...

Interesting... I hadn't realized that the @USERx system variables in a before job routine would be visible inside the job itself. I'll have to keep that in mind.

Me? Sorry, no. I learned long ago the difference between feces and a fetus and promised my Mom I wouldn't mix them up again.

Yah, I loves me that utility:

"Power Broker"? Linky?

Does another run of the 'same file' guarantee that the exact same records will be written to the hashed file? If that's the case and no job changes were made between runs, is there any chance that you ran out of disk space where that hashed file lives on the first run?

No, the FTP stage cannot handle compressed or zip or binary (etc) files. It does a metadata driven record by record transfer rather than just streaming bytes, which means text files only. "I need to implement this using datastage only" I don't understand restrictions on using scripts or the O/S for ...

Ah... thanks for posting that. Now time to mark your post as Resolved.

Sorry, but I have no idea what you just said. There's no "conversion" in this kind of operation.

And if you don't need "exact data as it is in the source" why state "I don't want to lose any data and can't strip data"?

Yuck, a fetal error.

There should be more to the error than that, something that should explain why it couldn't 'initialize the connection'. Can you post all warnings or messages related to this?

kavuri wrote:I need to convert a bigint (64bit) into int (32bit). I dont want to lose any data and I cant strip data.

Then you are out of luck when the value in your bigint exceeds what can be stored in the int. What then?

And you've been given two different approaches to do that.

hello, if your target column is for database then you need to use database specific date formating like to_date(), otherwise just check for proper length for that date column. First get it into the 'proper' format then let the SQL generate with the correctly masked version of TO_DATE(), whatever th...