Migration from v 8.0 to v 8.1

[thurmy34]

Thank you for that.
I understand that the change will apply only for the new job in the projet ?
Am i right ?

[kjaouhari]

Any available document that list the bugs that are fixed by the version 8.1 ? I've read one listing the new features but no mention of the bugs.

Moreover the 8.1 was realesaed shortly after the 8.0, so I guess they were in hurry to fix some issues of the version 8.0

I'm raising the subject cause we don't want to be beta-tester every time. And so far I didn't see any reason to do an upgrade and take the risk.

[chulett]

Should all be in the readme. And 8.0.1 came 'shortly' after 8.0, 8.1 was later. If you don't want to be a "beta tester" then in one sense you'll never upgrade... 8.1 is greatly improved from 8.0 but if you're still leery wait for 8.x to come out and then upgrade to 8.x-1.

[kjaouhari]

Code: Select all

then in one sense you'll never upgrade... 

I can just agree to this.
I'm going to read the readme of 8.1 if it's possible to get it from IBM.

[sriramkk]

Hello folks,

I was wondering if there is any reason for an upgrade from 8.0 to 8.1 ?

By the way I don't see any new significant stage compare to the 7.5.2.

Looks like few people are now working on the server version.

thanks.

Hi There,

We are planning to upgrade from DS 8.0 to 8.1. Just wondering if there was a migration path or is it a full uninstall and reinstall..

What sort of time frames are we looking at. We have about 5 instances

Thx

[J.Calvo]

Hello,
I was wondering if the bug that exist in Datastage version 8.01 which imposibilities the use of parameters correctly in sequential jobs and the server jobs inside it is solved in the new version 8.1. This version correct this bug or we have to use environment variables allways yet?

[chulett]

Never heard of such a bug or the need to "use environment variables always".

Rather than cluttering up someone's lovely migration thread, why don't you start a new post on the topic of this issue and we'll talk about it. Please include lots of gory details when you do. In the new post.

[J.Calvo]

That sounded too sarcastic

[chulett]

Wasn't meant to be.

Putting an issue in your own post let's us not only track it without going off on tangential discussions in other people's topics but also means the Subject can match the topic at hand, we have your particulars for job type and DataStage version plus you can mark the post as 'Resolved' if we reach a resolution. All of which is extremely useful for future searchers and something you cannot do here. Hence the suggestion.