dscmdexport using command activity diff dsx size

SURA · Post by **SURA** » Tue Sep 20, 2016 7:06 pm

Hello All

When i execute the Datastage job to export the Datastage project, it ran successfully, but the dsx file size is 42,018 KB.

I copied the same command from the Datastage director, executed in the command line. All good, but this time the dsx file size is 244,335 KB.

I would like to know why the dsx is differ?

About the code:
This datastage export job was developed by me, we as using Datastage 8.5 may be 4 - 5 years back, if i am right.

Now we are using Datastag 8.7.

ray.wurlod · Post by **ray.wurlod** » Tue Sep 20, 2016 7:41 pm

Methinks that your job does not export all artefacts, such as binaries and dependent objects.

SURA · Post by **SURA** » Tue Sep 20, 2016 9:52 pm

Thanks Ray, but is there any difference if the same command has been executed using command line vs command activity stage?

chulett · Post by **chulett** » Tue Sep 20, 2016 10:53 pm

Methinks he is saying it is not 'the same command'.

battaliou · Post by **battaliou** » Wed Sep 21, 2016 5:54 am

Are you using /EXEC option? Check out http://www.ibm.com/support/knowledgecen ... mmand.html

SURA · Post by **SURA** » Wed Sep 21, 2016 9:21 pm

chulett wrote:Methinks he is saying it is not 'the same command'.

Means the command behaves differently ?
Or
Totally the different command ?

As i said before, i copied the command from the Datastage director. That means , to me it is a same command.

Even i tried the Export options from the Designer, none of them are not matching the dsx file size!!

I don't know what is happening?

SURA · Post by **SURA** » Wed Sep 21, 2016 9:26 pm

battaliou wrote:Are you using /EXEC option?

Thank you battaliou for sharing this link.

Code: Select all

D:\IBM\InformationServer\Clients\Classic\dscmdexport /D=#DOMAIN_NAME# /U=#USER_NAME# /P=#PASSWORD#  /H=#HOST_NAME# #PROJECT_NAME# #DSX_FILE_PATH##PROJECT_NAME#.dsx /V > #DSX_FILE_PATH##PROJECT_NAME#.log

This is the command.

chulett · Post by **chulett** » Thu Sep 22, 2016 9:37 am

Meaning, perhaps it behaves differently. As Ray noted, sounds like one includes executables / binaries (etc) and one does not. Which is also why the /EXEC question came up.