Exit codes from PowerBuilder executable in Redwood

[Former Member]

We are currently in the process of Integration Testing for SAP Go-Live planned for March 31, 2008. Our Integration Testing is being done thru Redwood Job Scheduler. There appears to be a problem with exit codes from our PowerBuilder executable that does not correlate to condition codes in Redwood. The PowerBuilder executable either returns an exit code of 1 for successful or -1 for not successful. Redwood interprets -1 as KILLED. In reality the situation is that some records are processed successfully, but once a bad record is encountered, an exit code of -1 is set to indicate an error. The question is - what can be done in Redwood to interpret PowerBuilder exit codes correctly? In this case, we would expect an ERROR status to be produced but not a KILLED status which is misleading.

[Former Member]

This is much simple. Redwood is based on Oracle. You can get a help of oracle developer, you can handle this based on either exceptions or decode statement.

Otherwise, you can write a job that gets triggered based on killed status of this job and checks the actual error in PB log file. Then it will change the status of this job to Error in database instead of Killed.

- Bhushan