DSXchange

Also, another note. I talked to IBM support and there is not a DS/EE document for V8.0.1.

I am working on a project to try an implement DataStage Enterprise Edition (DS/EE). The information I have recieved so far about DS/EE says the same constraint still applies in V8.0.1.

The DataStage Enterprise Edition version used in the IBM document that I refer to above is 7.5.1a

I have a document from IBM dated January 23, 2006, titled - 'DataStage Enterprise Edition, Configuring Parallel DB2 Remote Connectivity'. It states in the prerequisites, 'The hardware and operating system of the ETL server and DB2 nodes must be the same.'

I have been advised by a knowledgable IBM consultant to set the xmeta password to be non-expiring. If the xmeta is not accessible, then your datastage environment will not work.

I had an error with the same message and found out the the client did not have the correct fixpack installed. Check the version.xml file under the C:\IBM\InformationServer directory on your workstation to ensure that the fixpack1 or fixpack1a has been applied successfully. APT_CombinedOperatorContro...

Has the DB been cataloged?

Have you been able to resolve your login problem? Are you logging to the IS console as isadm to setup the initial rights?

What web service are you addressing ? The server is not up for development yet so those problems may show up then but I am able to use the web console. I am going to switch the security to the OS Monday, what security option are you using?

I have encountered an error installing FixPack1 on a Linux Redhat 4.0 server. I wanted to share a solution for the benefit of others. The installation of the fixpack was successful with warning and I had no option but to cancel the install, the finish button was inactive/non-selectable. The error ms...

I am the data Stage Administrator working on this problem. I contacted the vendor support and the problem was that the pop-up window displaying the properties for the DB2 API was not viewable. Simply pressing the escape key resolved this problem. It was thought that the registry key used to position...