I didn't find anything about this here. So, once again, I'm off to Ask The Experts...

We need to Schedule a RC job from a System Scheduler and track the error code returned from the RC job.

I have it set up like this (basically):

1) I have a compound report which runs rather nicely from DevStudio (without any error).
* All associated procedures have error handling built in: "No data from source table" = "-EXIT 1000", "non-zero &FOCERRNUM" = "-EXIT 9000".
2) The RC job is set up to produce bursted PDF reports.
3) I am FTPing the bursted files to a server.
4) I have all notifications sent to me via email.

When I RUN the RC Job directly from the RC Scheduler, without error, everything works fine (I get the notifications of successful completion and the the files are on the server, as expected.)

When I RUN the RC Job directly from the RC Scheduler and force an error (changed the acx file to an invalid table). (I get the notifications of failed completion and the the files are NOT on the server, as expected.)

When I run them from a systems scheduler (OPCON), which executes a shell script, OPCON always comes back as "Finished: OK", despite the "-EXIT 9000". So, I suspect that RC does not regard the "9000" exit code when it completes execution. Please refer to the following excerpt from the RC notification:

    BTP1020         **************************************************************************
    BTP1020         *** Get the summary data from WSS_ORG_SUMM and hold as WSS_ORG_SUMM_HOLD
    BTP1020         *** &RptLvl = Chain / &RptLbl = CHN
    BTP1020         SQLCODE IS -1 (HEX: FFFFFFFF)
    BTP1020         : [S1000] Error -1010 (1010data error executing query: Not a table: dgwfte
    BTP1020         : st.wssxxxsummary) executing query
    BTP1020         L    (FOC1406) SQL OPEN CURSOR ERROR.  : WSS_ORG_SUMM
    BTP1020         **************************************************************************
    BTP1020         *** ERROR 1406   : There was an error.  Exit with return code of 9000
    BTP1020         **************************************************************************
    BTP1020         No burst value found in the report
    BTP1020         Task finished.
    BTP1010         No report to distribute.

So, how do I get OPEN to recognize the non-zero return code from within the fex which RC is executing?

This message has been edited. Last edited by: Doug,

What I would do is have the RC job create a small file if successful, otherwise do not create the file.

Then use an OS command to rename or copy the file. When the command fails because the file does not exist, seems to me that OPCON should be able to capture that error and do whatever you need on a failure.

Thanks for the work-around. I'm only referring to it as a "work-around" as I'd prefer RC to exit with a return code (beyond the "On Error" email notification) and for the system sceduler to recognize that return code... The work-around is good and may be the best alternative.

Thanks, Doug