I have a FEX that first runs an sql script and then build the report upon the SQLOUT.

If I run it from the dashboard or direct from DS it works fine, but when I run it by Reportcaster I get the error message

quote:

Task error: THE DESCRIPTION CANNOT BE FOUND FOR FILE NAMED: SQLOUT No report to distribute.

the fex...

ENGINE SQLMSS SET DEFAULT_CONNECTION Fidessa
SQL SQLMSS PREPARE SQLOUT FOR
	SELECT DISTINCT T.ToBankview,B.*
	FROM 	dbo.BankviewRecords B, dbo.BO_Transactions T
	WHERE B.Fidessa_Transaction_Id = T.Trade_id and T.ToBankview='direct';
END
-RUN
SET ASNAMES = ON
TABLE FILE SQLOUT
SUM
     Quantity AS 'QUANT'
BY BO_Book_Id AS 'BOOK'
BY Instrument_Code AS 'INSTRU'
BY ISIN_code AS 'ISIN'
BY Security_name AS 'SECNAAM'
BY Buy_Sell AS 'BS'
WHERE ( Fidessa_Version EQ 1 );
ON TABLE HOLD AS H_FIDES
END
-RUN
DEFINE FILE H_FIDES
SUBGRP/A10=IF BOOK EQ '216' OR '716' THEN 'OG fondsen' ELSE 'Aandelen';
BOUGHT/D15=IF BS EQ 'B' THEN QUANT ELSE 0;
SOLD/D15=IF BS EQ 'S' THEN QUANT ELSE 0;
END
TABLE FILE H_FIDES
SUM
     BOUGHT AS 'KOOP'
     SOLD AS 'VERKOOP'
COMPUTE TOT_QTY=BOUGHT+SOLD; AS 'SALDO'
BY SUBGRP
BY INSTRU AS 'FCODE'
BY ISIN
BY SECNAAM AS 'FNAAM'
ON TABLE NOTOTAL
ON TABLE HOLD AS HOLDDATA
END
TABLE FILE HOLDDATA
SUM
     KOOP/D12S AS 'Bought'
     VERKOOP/D12S AS 'Sold'
     SALDO/D12S AS 'Total'
BY SUBGRP AS ''
BY HIGHEST SALDO NOPRINT
BY FCODE AS 'FidessaCode'
BY ISIN
BY FNAAM AS 'fundname'
HEADING
"Traderecap Fidessa <+0>&DATEtMDYY <+0> "
ON TABLE SET PAGE-NUM OFF
ON TABLE NOTOTAL
ON TABLE PCHOLD FORMAT EXL2K
END

any suggestions?

how can I debug this

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

Frank I don't know if this makes any difference at all...but I have this in report caster coded this way with no problems
SQL SQLMSS SET SERVER Magic
SET SQLENGINE = SQLMSS
SQL SQLMSS

Where do I put this code?
In the start of the proces or after the ENGINE command?

At the start.

I changed it but no result.

Other suggestions?

Another suggestion..Perhaps deleting the END after the SQL statment...I never use that...

Here is something that I wrote for my developers awhile back.

"Here is a bit of "Best Practice" when dealing with passthru requests:

Basically, when you are doing passthru, you can only have the following between the closing semicolon after the SQL request and the END statement.

SQL SQLDBC
SELECT …

;
TABLE
ON TABLE HOLD {AS holdname}
END

OR

SQL SQLDBC
SELECT …

;
TABLE FILE SQLOUT
Regular report stuff goes here.
END

There can be no -RUN statements.

There can be no DEFINE statements.

If you need to do a DEFINE, hold the data first as in option1 above, then do the DEFINE and TABLE."

What I would do is move your ASNAMES statement to the top and then take out the END and -RUN in front of your TABLE FILE SQLOUT.

Report Caster is a bit pickier than the WF Client when it comes to parsing code.

Hope this helps.

Frank
1) instead of holding the first pass to H_tides. If you were to pchold to exl2k
would that work? This would show most likely the problem is occurring right
up front and cut down some serious debug time.
2) I would suggest this code either as a pro process or right in the top of your procedure.
ENGINE SQLMSS END SESSION;
-RUN
SQL SQLMSS SET SERVER &&XSERVER [your server name];
END

then you can follow with your code....
SQL SQLMSS
SELECT ....
FROM....
WHERE ....
;
TABLE
ON TABLE HOLD
END

RC more sensitive than DS when it comes to parsing....
found that to be the case with SET ASNAMES=ON in one scenario...
Hope this puts you on the right track.

Ira 5.3.6 and 7.6.x aix

Is it possible there was another error right before the one that was distributed by ReportCaster?

Do you need to pass the User ID and Password to access that database?

I have this SQL PREPARE statement that works, though I've never run it via ReportCaster:

SET SQLENGINE=SQLMSS
SQL SET USER MISDEV/quser,qpass

APP HOLD MS_STATEMENT

SQL PREPARE SQLTEMP FOR
 SELECT *  
  FROM MS_STATEMENT.DBO.STATEMENT_MESSAGE_TEXT
END

Thanks for all the suggestions and helpfully hints.
The process was important enough so I created a workaround by changing the sql and putting that on the server as a VIEW.
Next step was creating a master on that VIEW.
That solved my problem in RC, technical there seems to be no difference and I hope to find once what the reason was.