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 opened a case for this and will post the findings. Thanks for all the inputs.
I have an issue where a report (fex) can 'run directly' but will not 'Run Deferred' and thinking that it has to do with the value assigned to &WFDESCRIBE, which has a standard is not 'OFF', it's default of 'XMLRUN' (or something other than 'OFF').
The following is the result of the “-? &WFDESCRIBE” command.
-? &WFDESCRIBE
Produces:
CURRENTLY DEFINED & VARIABLES STARTING WITH 'WFDESCRIBE':
&WFDESCRIBE = XMLRUN
&WFDESCRIBE = OFF
My question is: Why is it there twice? The second one, OFF, negates the first one, XMLRUN, or the last one that it’s set to using the ‘-SET &WFDESCRIBE='Whatever';’ command.
My thought is that this is preventing procedures to run successfully as ‘Run Deferred’.
Your Thoughts and Input are greatly appreciated.
~DougThis message has been edited. Last edited by: Doug,
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
Could it be possible that it is two distinct variable's name but only first 10 digits of the name is displayed so we thought that it's the same variable ?
But I can have up to 12 digits displayed from other variables...so I doubt that it's the case...
Maybe your best shot will be to contact TechSupport
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
You might try to put -SET &ECHO=ALL; at the top of the fex and have the output of HTML. After the report runs deferred right mouse click on the output and view source and see if you can see that variable get set.. Not sure if it will display anything...
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005
The "-? Variable" command will display all variables with the specified variable as a prefix, similar to a search for a file as 'FILE*' which displays all files that start with 'FILE'. You can see this as follows:
-? &D
Which returns any variable starting with the letter 'D':
CURRENTLY DEFINED & VARIABLES STARTING WITH 'D':
&DATE = 04/08/20
&DBMSERR = 0
&DELTD = 0
&DMY = 080420
&DMYY = 08042020
&DUPLS = 0
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
Reason why I mentioned that I am able to see variables with a 12 digits name and that I doubt it's the case...
But I also remember that there were an old bug where variable's name get "confused" when first x number of digits were the same. And if I remember well it was something around the tenth digits. But this bug seems to be now resolved because I have many variable's name that have similar digits without any issues.
Good luck
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
As for autoprompting, you can also check the value for the variable &WFDESCRIBE by issuing -? & SAVEPRINT (ala Francis Mariani!) and if the value is anything other than OFF you have autoprompting turned on. The usual setting is XMLPROMPT.This message has been edited. Last edited by: Doug,
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
There was a PCHOLD instead of a HOLD in the procedure. There was no PC to HOLD it to when running DEFERRED so it failed.This message has been edited. Last edited by: Doug,
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005