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.
Is there a way to figure out how long a report took to run? Can I put a timestamp at the beginning of the report and the end and substract the difference and write it to a table stating how long it took to run?
Or can someone point me in the right direction or forum that shows how to do this.
Thanks, prodriguThis message has been edited. Last edited by: Kerry,
-* File jcs.fex
-SET &ECHO=OFF;
-* Start elapsed time
-SET &NOW=HHMMSS('A8');
-TYPE &NOW
-* CPU start
-SET &START=&FOCCPU;
SET MSG=OFF
-REPEAT #A FOR &I FROM 1 TO 2000;
TABLE FILE CAR
COUNT COUNTRY CAR BODY
ON TABLE HOLD
END
-RUN
-#A
-RUN
-* CPU end
-SET &END= &FOCCPU;
-* CPU time used
-SET &TIME=&END - &START;
-TYPE &START &END &TIME
-* End elapsed time
-SET &NOW=HHMMSS('A8');
-TYPE &NOW
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006
there's a way to set your &TOD system variable to actually change according to clock time. by Default, it doesn't change, it only gets set at the start of a fex. I can't remember where i saw that method. so... i use this (b/c i wrote it ages ago and it still works, so wth...): at the top of my fex -INCLUDE baseapp/mod_timestart ...stuff happens at the end of my fex -INCLUDE baseapp/mod_timestop
... and here are the 2 fexes. timestart:
-*timestart 2/2001
-* sljones@alumni.stern.nyu.edu phd ms mba
-* 12/08/09 NYU edited to clean up detritis
-SET &HOLDECHO = &ECHO ;
-SET &ECHO = OFF ;
-SET &TIMEIS = HHMMSS('A8');
-SET &HHSTART = EDIT(&TIMEIS,'99');
-SET &mm = EDIT(&TIMEIS,'$$$99');
-SET &ss = EDIT(&TIMEIS,'$$$$$$99');
-SET &TIMESTART= (&HHSTART * 3600)+(&mm * 60) + &ss ;
-TYPE timestart is &DATE &TIMEIS
-SET &ECHO = &HOLDECHO ;
-SET &mm =;
-SET &ss =;
and it types the DURATION right into my echo log. especially good for long dataextract jobs. you can then just MODIFY some file you keep with the fexname, say, and the &DURATION.. you know how to do that, right? i'm sure there is an easier way...
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003