nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwodstart.bat confusion

Ottawa_IWOV

Hi All -

I know this has been posted ad-nauseum, but I can't seem to get an answer.

We are using OD 6.0.2 on Windows 2003 Server

Does iwodstart.bat return an error code when invoked in a Perl script?
Does iwodcmd start return an error code when invoked in a Perl script?
We have been using iwodstart.ipl a lot (previous projects), but have been told it is thje way to go now.

Basically, we want to keep using our DNR archictecture and want to make sure that we can still get error codes if we move off of iwodstart.ipl.

Any advice on this one would be great!

Regards,

Find more posts tagged with

Comments

Migrateduser

To my knowledge, iwodstart.ipl is how you can get the most detailed response. For instance, the other commands can tell you if it succeeded or failed but iwodstart.ipl will give you an error code giving slightly more detail as to why it may have failed.

If you just need to know pass or fail, it seems that you could use any of these and parse stdout.

Adam Stoller

Hi All -

I know this has been posted ad-nauseum, but I can't seem to get an answer.

We are using OD 6.0.2 on Windows 2003 Server

Does iwodstart.bat return an error code when invoked in a Perl script?
Does iwodcmd start return an error code when invoked in a Perl script?
We have been using iwodstart.ipl a lot (previous projects), but have been told it is thje way to go now.

Basically, we want to keep using our DNR archictecture and want to make sure that we can still get error codes if we move off of iwodstart.ipl.

Any advice on this one would be great!

Regards,

I don't have an environment to test this in - but it should be trivial (if you have the environment) to quickly test whether or not iwodcmd start returns reasonable error codes - and thereby answer your own question with empirical evidence.

Have the script attempt to launch a deployment config file that doesn't exist - check the exit status.
Have the script attempt to launch a deployment configured for a target node that doesn't exist - check the exit status
Have the script attempt to launch a deployment configured for a replicationFarm in which one, of N, nodes doesn't exist - check the exit status
Have the script attempt to launch a deployment with a syntactic error in the deployment configuration file - check the exit status
Run a deployment with a DNR that runs for a long time [synchronous]
Have the script attempt to launch the same deployment concurrently (no '-inst' name in either case) and check the exit status (assumes you do not have the pending queue enabled)
Add a whole bunch of tests like the above
and finally, have the script launch a deployment that should (and does) succeed - check the exit status.