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.
Does anyone know of a way to determine what FOCEXECs were run over a year's time on a mainframe? We used to have mainframe SAS that could read and deal with SMF records, but no longer have that product. And, SMF records are a pain to work with, since they are variable in record length and in blocking.
Again, this is a mainframe question and we are not using WebFOCUS.
Thank you.This message has been edited. Last edited by: Kerry,
Mainframe FOCUS, Rel 7.1.1 running on MVS/TSO Windows XP, Mainframe VM/CMS and MVS/TSO outputs in Reports, Excel, Flat file
Posts: 15 | Location: Texas | Registered: September 01, 2009
We append log information to a text file. And create a new text file each day. Makes it a little harder to process using WebFOCUS but we can also read it into Excel etc.
Information we log is date, time, username, program name and some of the parameters that have been selected e.g. the week number (so we can tell whether people are running reports on current or historic data)
WebFocus 7.6.11 IBM iSeries
Posts: 14 | Location: Leeds, England | Registered: May 16, 2005
we do what Waz does. we have an includable module at the top of every fex, that module sits in the baseapp, and it writes the &FOCFEXNAME, the &SM_USER (whatever your user id is), the &YYMD date, and this is very important: a random variable! so that the MODIFY won't trip over itself when the same user clicks alot. just create a bunch of &vars, and load them to the end of the db. If you have the file in DATE-TIME order, then you're just appending all the time, so the db doesn't get corrupted or need REBUILDING.
MODIFY FILE efinusage
FIXFORM DATE/A8 X1 TIME/A8 X1 USERID/A8 X1 FEXNAME/A20 X1 DOMAIN/A8 X1 CORP/A5 X1 RANDOM/A8
MATCH DATE
ON MATCH CONTINUE
ON NOMATCH INCLUDE DATE
MATCH TIME
ON MATCH CONTINUE
ON NOMATCH INCLUDE TIME
MATCH USERID
ON MATCH CONTINUE
ON NOMATCH INCLUDE USERID
MATCH FEXNAME
ON MATCH CONTINUE
ON NOMATCH INCLUDE FEXNAME DOMAIN CORP
MATCH RANDOM
ON MATCH REJECT
ON NOMATCH INCLUDE RANDOM
DATA
&YYMD &TOD &ftuser &ftname &ftdomain &ftcorp &ftrandom
END
-RUN
USE CLEAR *
END
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003