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.
So, I have a procedure where (as commonly happens) I have a number of -DEFAULT/DEFAULTH statements up top. When I run the procedure with -SET &ECHO = 'ALL'; set and look at the output, for some reason the value of &MEMBR (after defaulting it to FOC_NONE) is nothing but a single blank space. I added a -TYPE &MEMBR to be sure. I have other -DEFAULT &xxxx = 'FOC_NONE'; statements right along with the &MEMBR one, but for some reason this one ends up with a value of ' '. It's driving me mad! Why on Earth would one -DEFAULT not work, while the others have no issue?
Has anyone else here ever ran into this issue with your -DEFAULT statements?? If so, how did you fix it?
WF jar seq number: 28 WF jar release: 8.1.0.5 Build Sys: Windows NT-5.2 X86_64 64bit Support Sys: Windows x86_64 64bit C Compiler: cl C Version: Microsoft (R) C/C++ Optimizing Compiler Version 15.00.30729.01 for x64 Ajax Framework: Bindows(tm) 4.3 Host Name: DVWF02 Server Name: WebFOCUS 80 Server
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
Thank you Martin, Francis and Jack for looking into this on your ends (again).
Jack, I thought it was figured out too. If I -SET &MEMBR = 'FOC_NONE', it works if you run just the procedure itself. If you try to reference the self-same procedure/report inside HTML Composer to set up a form to pass all the -DEFAULT values to it, having &MEMBR -SET still, it shows it working in the live preview panel you create for it. Once you run the thing however, I get the following:
quote:
Error on Reporting Server Agent on reporting server EDASERVE may have crashed or request was halted by the operator with "hard kill" command. Please investigate reporting server log.
I went to the Reporting Server Console to see into this log it speaks of, but it says there are none.
All the controls are populated correctly, and are selectable. I did however notice that on the Parameters tab the listbox control's bound parameter (the one for &MEMBR) is blank (much like its value when reviewing the output of the procedure). The HTML Composer won't let me manually enter FOC_NONE into the parameter either. It's tied to the default value that it's given in the procedure/report. Even though -DEFAULT &MEMBR = 'FOC_NONE' sits squarely in the code. The DIV parameter populated with FOC_NONE without an issue, much like the rest of of the defaults. Not sure where I'm going wrong.
Jack, I also inserted -? &MEMBR right after -SET &ECHO = 'ALL' and got a value of blank as well.
WF jar seq number: 2 WF jar release: 8.1.0.4 Build Sys: Windows NT-5.2 X86_64 64bit Support Sys: Windows x86_64 64bit C Compiler: cl C Version: Microsoft (R) C/C++ Optimizing Compiler Version 15.00.30729.01 for x64 Ajax Framework: Bindows(tm) 4.3 Host Name: ourHostName Server Name: WebFOCUS 81 Server
Looks like you are configured with slightly newer versions than us in some cases.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
So, I've found out a way to reproduce this incorrect behavior (to me). I tried a brand new procedure and got it to work at first (much like all of you did), but then I added the multiselect that &MEMBR is a part of down in my request, and BAM...&MEMBR no longer equals FOC_NONE but blank.
How to reproduce:
1. Create a new procedure; 2. Type the following and run it: -DEFAULT &MEMBR = 'FOC_NONE'; -TYPE &|MEMBR = &MEMBR It works like you all saw. 3. Then add this to the end (not the real code, but a way to add a multiselect for &MEMBR): -DEFAULTH &STRMEMBR = 'Bob'; -SET &MEMBR = IF STRMEMBR EQ &MEMBR.(OR()). THEN 'FOC_NONE' ELSE _FOC_NULL; Now the autoprompt prompts for &MEMBR via a list box, but the value of &MEMBR is blank.
What gives? And how do I fix this if I still need to use a multiselect for &MEMBR?
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
Also, this is code I've brought over from 7.6.11 and it worked with how the multiselect is structured w/o a problem. Bringing it over to 8.1 and all the sudden it just gets borked.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
Jack, I also inserted -? &MEMBR right after -SET &ECHO = 'ALL' and got a value of blank as well.
So the context that is invoking this fex is supplying &MEMBR=' ', which overrides the -DEFAULT.
And I reiterate,
Just add something to catch the situation where &MEMBR is blank: After your "-DEFAULT" statements, add -SET &MEMBR = IF &MEMBR EQ '' THEN 'FOC_NONE' ELSE &MEMBR;
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
Also, this is code I've brought over from 7.6.11 and it worked with how the multiselect is structured w/o a problem. Bringing it over to 8.1 and all the sudden it just gets borked.
As I said, something changed in the launch page, causing it to vote for '' as the value (rather than abstaining) when none are selected.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
Thanks again for your willingness to chime in and review some steps that will help that you've suggested before. I added the check and it does work now at the fex level and with the form. I appreciate it.
I guess when you add a mutliselect within a request that lacks any entries, the value of the parameter it will store those values in will be blank unless you try and run it from the form that has the control with the static list to choose from that populates that multiselect list for &MEMBR.
Again, thank you and take care.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015