As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I created a report which I'd like to run with the user entering a prompt through a launch page.
Before creating the launch page I am testing the fex with this code:
quote:
-DEFAULT &ASGX = 'sm19';
-SET &ASGX = IF &ASGX.EVAL EQ '' THEN 'FOC_NONE' ELSE '&ASGX'; -RUN
TABLE FILE MMDB1 PRINT WORKDESC ADDRESS DYYMD COMPUTE DIFF/I8 = DATEDIF(DYMD,TDATE,'D'); COMMENT1 COMMENT2 COMMENT3 -* BY ASSIGNEE BY WO WHERE STATUS EQ 'O'; WHERE DYYMD GE AGEDIF;
WHERE ASSIGNEE EQ '&ASGX' ;
END -RUN
When I run this fex, I am surprised to see this error as the ASSIGNEE field is A4 in the MMDB1 table.
quote:
0 ERROR AT OR NEAR LINE 40 IN PROCEDURE ADHOCRQ FOCEXEC * (FOC015) THE TEST VALUE IS LONGER THAN THE FIELD FORMAT LENGTH: &ASGX BYPASSING TO END OF COMMAND (FOC009) INCOMPLETE REQUEST STATEMENT -EXIT
Any ideas?This message has been edited. Last edited by: Kerry,
There is too much EVAL in the world. Just code it like dhagen suggests. Equating one Dialogue Manager variable to another does not require EVAL, which needs to be used in very rare cases.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server