Problem

In the Enterprise Analyzer Interactive Analysis, it is possible to run a clipper query and then export the data for use in Enterprise Develeoper. Is there a way to do this in a batch environment?

Resolution

To complete this task in a batch environment, run ExportToXML.bj

To run the clipper query and ExportToXML, the process would be..

1. Use clipper within the Enterprise Analyzer Interactive Analysis to generate the necessary results.  

2. The clipper query should be run and the list of results generated in batch by running ClipperSearch.bj

3. The clipper query results list will then be exported, in batch, by running ExportToXML.bj, producing a file ready to be fed into Enterprise Developer.

The attached ExportXMLForED.zip contains the following :

- ClipperQuery&ExportXMLForED.bat file.

- ExportXMLForED.bat file.

1602.ExportXMLForED.zip

ClipperQuery&ExportXMLForED.bat 

This .bat file runs any known clipper query, as an example the attached runs "Dead Statements", and exports the results list into a file ready to be fed into Enterprise Development, in a single unit of work.

To use the ClipperQuery&ExportXMLForED.bat file,

1. Extract the ClipperQuery&ExportXMLForED.bat from the zip file into any directory.

2. Modify the ClipperQuery&ExportXMLForED.bat file to match the installation, environment, workspace and clipper query and results list required.

3. Run the ClipperQuery&ExportXMLForED.bat from a DOS Command line or schedule it as a windows started task.

ExportXMLForED.bat. 

This .bat file will export any known clipper query results list, into a file ready to be fed into Enterprise Development.

To use the ExportXMLForED.bat file,

1. Open Enterprise Analyzer.

2. Open Interactive Analysis.

3. Run the desired query interactively, into a Results List.  

    NOTE : Make a note of the "full" results list name as it will be used in the ExportXMLForED.bat

    NOTE : The interactive clipper query does not need to be run immediately before the batch ExportToXML job is run, as long as the results list exists before it is run.

4. Modify the ExportXMLForED.bat file to match the installation, environment, workspace and clipper query results list name from step 3 above

5. Run the ExportXMLForED.bat from a DOS Command line or schedule it as a windows started task.

The resulting file out of either of these processes can be fed into Enterprise Developer manually.

Incident#2671374