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'm thinking that the generation of the report is not the duration which you are concerned about. But that the data extraction is. If that is the case, concider this:
-SET &BEG_TIME = HHMMSS(&TOD) ;
...Data ectraction, or pre-report process, or what ever it is that's really taking the time (duration)
-SET &END_TIME = HHMMSS(&TOD) ;
TABLE FILE [filename]
...
FOOTING
"This report started at &BEG_TIME and ended at &END_TIME"
END
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
In order to get the duration, say in seconds, you could then use HDIFF to calculate the difference between finish and times provided you use their Date-Time representation.
Using this technique was a bit of a habit of mine. I would grab the time from the beginning and end of each extract and report phase of the FEX and build a display of these data at the end of the FEX such that it was visible when 'displaying source.' This was quite helpful in tuning and showing where the time was being used: not in WF code but in the SQL work. Settled more than one argument over the years.
jimster06 DevStu WF 7.6.11 W7 HTML, PDF, EXL2K
Posts: 252 | Location: USA | Registered: April 15, 2003