DSXchange

How do we backup DataStage 7.5.2 and IIS 8.0.1 installed on the same server

We have DataStage 7.5.2 and IIS 8.0.1 Upgrade installed on the same server.
Issue: How does the dscmdexport command find the project with two project directories?

The IIS 8.0.1 projects are in the /u01/dsprojsv801 directory.
The DataStage 7.5.2 projects are in the /u01/dsprojs directory.

When the dscmdexport.exe (script) is executed it 'Failed to attach to the project'
- Can a path be coded in project parameter within the dscmdexport parameters

Example: %DSExportCmd% /H=%Host% /U=%User% /P=%Password% %%i %BackupDirDT%%Host%_%%i.dsx >> %LogFileName%
%%i is the project with a value of HMKSandboxv801
dscmdexport can't find this project.

The DataStage 7.5.2 backup script that worked in a single DataStage 7.5.2 environment doesn't work in the DataStage 7.5.2 and IIS 8.0.1 Upgrade environment (dscmdexport).

LOG:
DataStage Backup ran on 20070906 13:14:20 with the following parameters
Host=auriga
User=dsadm
BackupDirDT=F:\DataStage\DataStageBackups801\DataStageBackup801_20070906\
DSExportCmd=C:\IBM\InformationServer\Clients\Classic\dscmdexport.exe
ProjectList=F:\DataStage\Scripts\BackupScripts801\ProjListDev801.txt
DSLog=BackupLog801

Projects in backup list on auriga:
HMKSandboxv801
training801
Backing up Project HMKSandboxv801
Attaching to 'HMKSandboxv801' ...
dscmdexport aborted:
Failed to attach to the project

I believe that the project must be a project name, not a path.

Try setting the DSHOME environment variable to the path of the correct DataStage engine directory - the 7.5.2 one or the 8.0.1 one. It is from the UV.ACCOUNT hashed file in this directory that the pathname of the project is decoded.

Using the single project name doesn't find the project so i was trying to figure out how to point to the DataStage 7.5.2 projects versus the IIS 8.0.1 projects. It's interesting that our script pulls the dsparams files for the requested project but the dscmdexport can't find the project.

Note: Our backup script works in our current dataStage 7.5.2 environment driven by a file with a list of projects that we want backed up.

Have you tried setting DSHOME environment variable?

Have you tried setting DSHOME environment variable?

As far as i can see the DSHOME environment variable has been set up correctly.

DataStage 7.5.2
/dstage/Ascential/DataStage/DSEngine/dsenv

DSHOME=/dstage/Ascential/DataStage/DSEngine; export DSHOME

LIBPATH=`dirname $DSHOME`/branded_odbc/lib:`dirname $DSHOME`/DSComponents/lib:`dirname $DSHOME`/DSComponents
/bin:$DSHOME/lib:$DSHOME/uvdlls:$ASBHOME/apps/jre/bin:$ASBHOME/apps/jre/bin/classic:$ASBHOME/lib/cpp:$ASBHOME/apps/p
roxy/cpp/aix-all-ppc:/usr/teragss/aix-power.32/client/lib:/usr/odbc/drivers:$ORACLE_HOME/lib32:$LIBPATH
export LIBPATH

IIS 8.0.1
/IBM/InformationServer/Server/DSEngine/dsenv

DSHOME=/IBM/InformationServer/Server/DSEngine; export DSHOME

LIBPATH=`dirname $DSHOME`/branded_odbc/lib:`dirname $DSHOME`/DSComponents/lib:`dirname $DSHOME`/DS
Components/bin:$DSHOME/lib:$DSHOME/uvdlls:$ASBHOME/apps/jre/bin:$ASBHOME/apps/jre/bin/classic:$ASBHOME/lib
/cpp:$ASBHOME/apps/proxy/cpp/aix-all-ppc:/usr/teragss/aix-power.32/client/lib:/usr/odbc/drivers:$ORACLE_HO
ME/lib32:$LIBPATH
export LIBPATH

Pete,
Dscmdexport.exe simply doesn't work in 8.0.1 environment. I even tried to use incorrect server name, user ID, or password, but I got the exact same error message "dscmdexport aborted: Failed to attach to the project". It doesn't even say due to incorrect server, ID, or invalid password.
So, it's better to open a case with IBM.

IBM Case 701084 has been opened to address this issue.

IBM RESPONSE:
Finally got the syntax down for what you are attempting to do. The first thing is that the dscmdexport.exe will not work in a batch file exporting from both DataStage 7.5.2 and DataStage V8.0.1. You need to run the Multi-Client Manager to set which version you are planing to export, and then use the dscmdexport.exe in that Client version directory.

When you are exporting the DataStage V8.0.1 projects you need to use the following syntax:
>dscmdexport /D=Domain:PortNumber /H=DataStageServer:Port /U=UserName /P=UserPassword Project Export.dsx

Or in your case:
> dscmdexport /D=auriga:9080 /H=auriga:31801 /U=dsadm /P=dsadm-Password HMKSandboxv801 Export.dsx

DataStage V8.0.1 TEST RESULTS:
Directory: C:\IBM\InformationServer\Clients\Classic\dscmdexport.exe
dscmdexport /D=auriga:9080 /H=auriga:31801 /U=dsadm /P=dsadm-Password HMKSandboxv801 Export.dsx

The Multi-Client Manager version was set to DataStage V8.0.1.
The backup of both the .dsx and the dsparams files all work as designed.

The Multi-Client Manager version was set to DataStage 7.5.2 .
The backup of the .dsx files didn't work (Cannot create Repository).

DataStage V7.5.2 TEST RESULTS:
Directory: C:\Progra~1\Ascential\DataStage7.5.2

The Multi-Client Manager version was set to DataStage 7.5.2 .
The backup of both the .dsx and the dsparams files all work as designed.

The Multi-Client Manager version was set to DataStage V8.0.1.
The backup of the .dsx files didn't work (Cannot create Repository).

Note: DataStage 7.5.2 and DataStage v8.0.1 coexist on same server.

Next Step:

Backup scripts are run once per day backing up all out DataStage/IIS Servers.
We have to determine how to switch the Multi Client Manager within a script so we can run our backups without manual intervention!!

IBM RESPONSE: Re: ISSUE: How do we execute/switch the Multi Client Manager within a script so we can run our backups without manual intervention!!

You can't. The Multi-Client Manger is not designed to support command mode switching.

The original version was all command line driven, having to execute a batch file to switch things. Once they 'improved' it and made it a service, that option went out the window.

What about using one of the many 'macro recording' utilities that record and 'play back' a series of mouse clicks and key presses? Perhaps something like that could be leveraged?

Leo, did you find a solution to the dscmdexport.exe problem? I would like to automate the backup process on our end as well.

What port are you using for the host - I get the 9080 for the domain, but which port/process are you using.