DSXchange

I prefer the 'check the magic number' bit myself as it is a little bit more intuitive, but either way works.

After the job aborts, Reset it and let us know if a 'From previous run...' entry shows up in the log. Specifically, the contents of that entry.

Yup, and Ray has laid it all out in the past, let me see if I can find it... ah:

http://www.dsxchange.com/viewtopic.php?t=86639

The 'SP2 patch' won't help here. This is cetainly not normal behaviour, you should involve your Support provider. Does the same problem happen if you import via the Manager tool?

Forget about VOCs and Q-Pointers, they are far from beginner topics and not something a beginner really needs to be concerned about or should be having to deal with. And a 'beginner in DataStage' really has no business being in DS.TOOLS. Secondly, when you type 'uvsh' (or more properly 'dssh' nowada...

While the two datasets can have different columns names, all Key and Difference Value columns must have identical names. Have you marked B as such or enabled the 'All non-Key columns are Values' property?

This just from reading the docs, btw.

'Empty' means an empty string, also known as quote-quote or "".

Search is your friend!

http://www.dsxchange.com/viewtopic.php? ... userstatus

ThilSe wrote:I am trying to call a User defined after job subroutine (IN_RTN_1) inside another user defined after job subroutine (OUT_RTN_1).

Hence the BASIC code.

That would be the huge caveat I mentioned.

Patch?

I would guess the Project was corrupted before you imported and that's the only reason the 'duplicate' was created. It's certainly not something that passes for normal.

The 7.5 client cannot connect to the 7.0 server. So, you'll need the 7.0 client for sure and then either upgrade it to 7.5 or install it as well as the MCM once the server upgrades.

Yes, from what I recall there is a client portion that needs installing as well.

Hmmm... there's nothing like a 'patch log' that I am aware of. I believe it's just something your DS Admin (or whomever would apply them) would need to have kept track of.

Perhaps someone else knows...

DataStage patches? O/S patches?