Can datastage clients 5.2Ver & 7.5 Ver coexist?

prao · Post by **prao** » Mon Jan 09, 2006 1:48 pm

We are upgrading datastage 5.2 to 7.5 ?. for testing time , we need clients 5.2 ver and 7.5 version client needs to be on the same machine and work with minimum setup. I see some posts talking about the 'multi client manager' to do this. does this multi client manager handle 5.2 version also?. I see one post dated back to 2003 in which was told that 6.0 and 5.2 were not switchable. does any body tried this ?

chulett · Post by **chulett** » Mon Jan 09, 2006 2:05 pm

I don't see anything in the readme for the MCM that mentions a version restriction. I seem to recall using for 6.x and 7.x, pretty sure you'll be fine.

Multi-Client Manager
--------------------
A Windows Service is used by the MCM. This service needs to be run using
a user account that is part of the Administrators Group on the Local
machine. It can not be the built-in Local Administrator. Before the
DataStage Client installer is run, the user must exist and be in that
group. Also the Local Security Policy must be set up so that the user
account must have the "Logon as a service" user rights assigned to it.

1) If a user account that is in the Administrators Group on the Local
Machine is not specified, then the Service will not be placed installed
in the Service Control Manager and so the MCM will not work.

2) If a valid user account is specified, but it does not have the "Logon
as a Service" user rights, then the service will be installed into the
Service Control Manager, but it will not be started. The user would have
to manually go to the Service Control Manager, re-enter the user account
and password for the service and start the service. At this point the
Service Control Manager would automatically assign the correct user
rights to the account. Rebooting the machine will not solve the problem.

Other Multi-Client manager related restrictions:

1) The Multi-Client Manager does not work with DataStage Version
Control. If an installation of Version Control is found during the
installation, the user is notified.

2) Only one version of the Web Service PACK and Java PACK can be
installed on a client system at one time. This means that the
Multi-Client Manager does not work correctly with these PACKS. The last
version of the Web Service and Java PACKs installed will be the only
versions on the system.

3) When installing multiple versions of the clients for use with the
Multi-Client Manager, when at the end of the last installation, the
answer to the question, "Do you want Setup to add program shortcuts to
your desktop?" is NO, then if there are existing shortcuts on the
Desktop they will not be updated. This means that those shortcuts will
point to a version of the DataStage Clients that are no current. If the
Designer shortcut is invoked then the following message will be
displayed, "The incorrect version of vmdsobj.dll is install." and the
Designer will fail to start. For the Manager, Director and Admin Client,
if the version is older than V7.5 then the clients will appear to work.
This could cause instabilities. (53131)

4) When uninstalling DataStage Clients, if the Multi-Client Manager is
to be uninstalled as well, make sure the Multi-Client Manager is
uninstalled last. If the Multi-Client Manager must be uninstalled before
the DataStage Clients, then reboot the machine between the two
uninstalls.

prao · Post by **prao** » Mon Jan 09, 2006 3:26 pm

I heard lot of things changed with version 6.0 on wards , thus I heard lot of incompatibilities before Version 6.0 and after that . that's way I got this question. Thank you for your feedback.

chulett · Post by **chulett** » Mon Jan 09, 2006 3:48 pm

Probably best to ask Ascential Support so you know for sure.

ray.wurlod · Post by **ray.wurlod** » Mon Jan 09, 2006 4:11 pm

I have definitely used the Client Switcher utility (precursor of MCM) in a 5.2 and 7.0 environment, successfully.

tcj · Post by **tcj** » Mon Jan 09, 2006 5:02 pm

Client Switcher utility also works in a 4.2 and 7.1 environment.

WoMaWil · Post by **WoMaWil** » Tue Jan 10, 2006 1:27 am

No problem with switching from any version to any other version. If you succeed in getting up the Switcher it and the Client Installation is done as described, there are no problems.

There is an older commandline Switcher and an newer Windows Switcher.

For the last you need a local administrator on the Client PC not only local administration rights.

anupam · Post by **anupam** » Tue Jan 10, 2006 1:40 am

We have also deployed 5.2 and 7.1 Version of the client on the same machine when we were upgrading the version to 7.1.

There is no issues as far as co-existance of both the version is concerned. You need to have a client switcher.