DSXchange

Row counts are based on link names only. If you use update and then insert then there is no way to call an API to get this count. I do not think there is a way ask Oracle how many updated versus inserted either.

It does not purge anything. It overwrites the whole record, every column or inserts a new record.

It appends or overwrites based on the key.

The BASIC code has an engine which controls it. It is a nightmare to extract anything from it. Kumar is correct it is much easier to get metadata about the job designs from the repository tables like DS_JOBOBJECTS.

Not sure if these are documented but they should be in a folder called sdk\Utility. The source code is even included for most of these routines. Edit them and learn how to write routines. Great learning tool.

Maybe it is the XP patch that takes it away.

Jobs run as phantoms. They have no UNIX shell like ksh therefore they do run any .profile. You need to add this to dsenv or uv.rc or as Ray's states.

By the way you will not add much to a project directory if you leave this hashed file in the project. It only has one record. Not a problem.

You won't need a RoutineActivityStage in between your Jobs. Code: JobActivity1->>JobActivity2 In your JobActivityStage2, for the last parameter, rightclick and choose DSTransform>>>sdk>>>Utility>>>UtilityHashLookUp and then pass the values in here. Kris, I am on 7.5 and I cannot right click and do ...

I don't think they are backward compatible. If you create a project in 7.5 I don't think you can go back to 7.1. It complained when I tried it. Version Control works well and is included with DataStage. It will keep older versions so you could roll back to an older version. It does not have a diff. ...

Put your hashed file in the current project then you do not need SETFILE.

EtlStats will not work across projects. So you need to install it in the other project.

dsjob can list all jobs in any project.

Sure, write a job to save it to a hashed file. Make the hashed file have a key and this value. Hard code the key to "Something" or whatever you like. Use UtilityHashRead to read this value into a stage variable in a job sequence. You can now use this value as a parameter. All the Utility routines ar...

It takes several calls to get this to work. You need a valid JobHandle by using DSAttach(). StageName has to be a valid stage name. Same with LinkName.

DwNav which I wrote. MetaStage which IBM sells.