DSExport non interactive and supress warnings

anandsiva · Post by **anandsiva** » Thu Aug 30, 2012 8:07 pm

We have a requirement to export all the jobs as XML and we have created a bat script to export it. But in case of warnings It waits for user input to proceed further. Is there a way to ignore these warning messages or any other alternative approach? We get the jobs list from XMETA and use that to create the DSEXPORT batch scripts

ray.wurlod · Post by **ray.wurlod** » Thu Aug 30, 2012 9:32 pm

Try redirecting stdin from NUL to supply an infinite number of Enter presses.

Code: Select all

dscmdexport -options project < .\NUL

anandsiva · Post by **anandsiva** » Fri Aug 31, 2012 12:12 am

DScmdexport exports as dsx where as the requirement is to export as XML.

ray.wurlod · Post by **ray.wurlod** » Fri Aug 31, 2012 3:01 am

Then do the same for dsexport. Or ANY command.

anandsiva · Post by **anandsiva** » Mon Sep 03, 2012 9:34 pm

It still popped up window with warning the job doesn't exist.

"C:\IBM\InformationServer\Clients\Classic\dsexport" /D=Server:9080 /H=Host /U=user /P=XXX HLK_DEV /XML /JOB=CopyOfSQ25TgtChrgReg D:\CopyOfSQ25TgtChrgReg.xml < .\NUL

chulett · Post by **chulett** » Mon Sep 03, 2012 10:21 pm

Then perhaps you shouldn't be attempting to export non-existent jobs. How are you generating the name(s) to export?

anandsiva · Post by **anandsiva** » Tue Sep 04, 2012 12:47 am

This is a test for what Ray has suggested. We have process which reads from XMETA the job name and then we generate set of dsexport command. For some reasons if dsexport throws some warning the entire batch gets stuck until manual intervention. We wanted to avoid this.

PhilHibbs · Post by **PhilHibbs** » Tue Sep 04, 2012 4:00 am

I don't think it's possible. Well, everything's possible given a broad definition of "possible", but you know what I mean. I remember trying to do this myself, and I gave up and went with DSX exports instead. And if I can't do it easily, it isn't possible.

Perhaps you could try some sort of Windows automation software like AutoIt, write a little script that runs in the background looking for a particular window title and sending a click event to the Close or OK button. I did this to get rid of a bunch of import dialog boxes that were warning me about referenced jobs.

Or, write a DSX to XML converter...

anandsiva · Post by **anandsiva** » Thu Sep 06, 2012 7:50 pm

Thanks.. As suggested we have created a C++ utility that looks for the dialogue box and record the message to a log file and closes the warning message.