Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

The error level return is not defined in the build.xml



The build.xml that executes the batch remotely is not handling the error levels and is not returning the error level at current scenario. The error level is important to capture as it indicates if there is any failure or batch is completed successfully.

Error Messages

Not Applicable

Steps to Reproduce

Execute build.xml and observe that the error levels are not handled. The error level at current scenario is also not returned. 

The ant is not returning the error level; mostly because there is no variable to hold the status of "javaReturnCode".

Root Cause

In the current implementation, the custom ant tasks used for Scriptable DMA do not expose a return code which can be accessed in the ant script to identify the status of the task. Exit codes for the Ant process determine the success or failure of the executed tasks, supplemented with stack traces on standard error.


The %errorlevel% property can be used to get the exit code of the ant task by calling it from a .bat file. Execute the ant task by using a 'call' command from the batch file.

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us