If {exit code of action != 0}

Content Authoring
1

(imported topic written by MattPeterson)

I found a couple of old threads that mentioned people had problems with this as well, but I haven’t been able to find an answer. I have a few wait commands in my task where if they don’t return an exit code of 0 I want to run another command, then exit the action. Below is a simplied example of what I’m trying to do. (I added the prefetch command in here, because others mentioned this works if you don’t have any downloads in the action).

prefetch install.exe sha1:3214 size:132
http://url

wait __Download\Install.exe

if {exit code of action != 0}

wait c:\windows\somescript.exe

//Now exit

continue if {false}

endif

//Run other stuff

I’m getting a relevance subsitution error on the exit code of action line

2

(imported comment written by jgstew)

This appears to be valid from looking at this:
http://www-01.ibm.com/support/docview.wss?uid=swg21506222

I see a similar issue here:
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014756981

Could this be part of the issue? "This value will not exist if the action has not yet produced an exit code."
http://support.bigfix.com/cgi-bin/inspectorsearch/single_inspector.cgi?cpx=p&keyphrase=exit+code+of+%26lt%3Baction%26gt%3B&type=action&win=&lin=&hpux=&mac=&aix=&sol=&wm=&ubu=&client=1

3

(imported comment written by MattPeterson)

That’s what I was thinking the problem was. It seems if you have download statements (or prefetch) in your action the client evaluates all “if” statements prior to running. The exit code of the action obviously wouldn’t exist until after the action was running. So I added an “if exist exit code of action then else” statement and was able to get this to work. One thing to mention is even though the client evaluates the if statements (and parameters) prior to running the action, it will evaluate them again during the action. So in my case the exit code parameter is evaluated prior to running, and must not contain errors, however it will evaluate again when that line is reached in the action, so the correct exit code is set. I used parameters for the exit code in order to retrieve it in the console in the event of failure, example below.

waithidden run.cmd

parameter “Exitcode” = “{if exist exit code of action then exit code of action as string else “52311”}”

if {parameter “Exitcode” != “0”}

//Run.cmd did not complete as expected. Now run run2.cmd and exit the task with the exit code from run.cmd

Waithidden run2.cmd

exit {parameter “Exitcode”}

endif

4

(imported comment written by jgstew)

I was under the impression that parameters were always evaluated before execution and never changed once set, which would suggest this would never work.

5

(imported comment written by MattPeterson)

I just tested it and it works (exit code parameter set to 0). I’ve been using paramaters that are set based on things that happen in the action for a while… They seem to be evaluated prior to running (to check for errors and to determine what downloads are needed), but then again during the task.

6

(imported comment written by jgstew)

Thanks for that info, I’ll have to take a closer look at parameter behavior. Perhaps I’m confusing the problems I’ve run into if you try to set a parameter more than once in actionscript with this.