This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: How to debug batch scripts
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 12, 2010
05:46 AM
How to debug batch scripts
Hi ,
I am executing batch script through my installer .I have used a display message panel,that if it gets unsuccessful ,then the $EXECUTE_VIEW_STDERR$
================================
$EXECUTE_VIEW_STDOUT$ should be displayed.
I have set the rules also ,that $EXECUTE_VIEW_EXITCODE$ should not be equal to 0.
Now when script is not found in the path,then this message is getting displayed properly.But when the script is getting fail,I am not getting this error panel,and installer shows successful installation.
What should i do to check that the script called from inside the installer is successful or not ?
Regards
Shilpa
I am executing batch script through my installer .I have used a display message panel,that if it gets unsuccessful ,then the $EXECUTE_VIEW_STDERR$
================================
$EXECUTE_VIEW_STDOUT$ should be displayed.
I have set the rules also ,that $EXECUTE_VIEW_EXITCODE$ should not be equal to 0.
Now when script is not found in the path,then this message is getting displayed properly.But when the script is getting fail,I am not getting this error panel,and installer shows successful installation.
What should i do to check that the script called from inside the installer is successful or not ?
Regards
Shilpa
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 14, 2010
03:19 PM
In my experience IA batch scripts don't propagate the exit code from the contents of the script. So if your script calls something that gets an error, you don't see the error in $xxx_EXITCODE$; it still has 0. So instead you have to have your rule do $xxx_STDERR$ "does not contain" .
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)