Hi,

I am facing the error :
"UNRECOGNIZED COMMAND ON TABLE SET XRETRIEVAL OFF" when trying to execute a sql query from reportcaster. The fex has only this query to be executed and sent in pdf format. Maybe there's something wrong with the query because some queries seem to be running while others run into the same error.

-SET &ECHO = 'ALL';
ENGINE DB2 SET DEFAULT_CONNECTION DB_UAT
SQL DB2 PREPARE SQLOUT FOR
SELECT TRANS.OBJECT_ID,
MAX(TRANS.SEQ_NUM )AS SEQ_NUMBER
FROM SCHEMA_UAT.TRANSACTION TRANS
INNER JOIN SCHEMA_UAT.WORK_OBJECT WO ON WO.OBJECT_ID = TRANS.OBJECT_ID
GROUP BY TRANS.OBJECT_ID
;
-RUN
TABLE FILE SQLOUT
PRINT
OBJECT_ID
SEQ_NUMBER
ON TABLE HOLD AS DB_TST
END
-RUN
-TYPE NUMBER OF ROWS : &LINES
TABLE FILE DB_TST
PRINT
OBJECT_ID
SEQ_NUMBER
ON TABLE PCHOLD FORMAT PDF
END
-RUN


PS This fex displays correct output when run with format HTML without reportcaster.

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

I don't see anything that would explain why you get the exact error message you're getting, but...

It appears that you forgot to END your SQL PREPARE statement.

Thanks for pointing that out.
Error message now changes to "unrecognized command"...

*huge help wf error messaging system*

turn on your echo
and then run and look at your caster log.
be sure you don't have a pre-processing condition set. that sometimes happens unintentionally when you clone another job.

Susannah,

Already did that.
Placed -TYPE Lines: &LINES before and after this code. Returns non-zero values. I assume that means the hold files are being created and have data in them.

Also tried another thing. Placed -EXIT right before this code and caster log doesn't throw back any error. As soon as sql is processed, error pops up and this is not the first sql being executed in the report.
Hence, the confusion if I'm doing something in the sql which is not correct.

In my experience, the message "unrecognized command" usually means that you forgot to end a previous command properly. That can be quite a bit back up in the code, for example when forgetting to end a DEFINE computation with a semi-colon.

Often, putting a -EXIT before the supposedly offending bit of code doesn't result in an error, while in fact there is one. Not sure what's the reason for that one, apparently the parser thinks that continued lines of gibberish are just fine...

Wep,

Thanks for the tip. Yes, it was actually a missing semi-colon.

I'm astonished that report worked perfectly online.

quote:

SELECT TRANS.OBJECT_ID,
MAX(TRANS.SEQ_NUM )AS SEQ_NUMBER
FROM SCHEMA_UAT.TRANSACTION TRANS
INNER JOIN SCHEMA_UAT.WORK_OBJECT WO ON WO.OBJECT_ID = TRANS.OBJECT_ID
GROUP BY TRANS.OBJECT_ID;
END

The "END" is the END (terminator) of the WebFOCUS "ENGINE DB2 SET DEFAULT_CONNECTION DB_UAT / SQL DB2 PREPARE SQLOUT FOR" command while the semi-colon in the END (terminator) for the SQL pass-thru, right?

Just checking, revisited on April 24 2014 for verification of another associated issue.

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

Yes, Doug. Correct.