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 some sort of function or command that we can use to include a time stamp? It would be helpful to see a time stamp after each sql pass through to get a time as to when something failed or didn't fail. We do have auditing, but it seems to cause some over head and our reports depending on the measures selected can take several hours to run. This is part of the output from a report that I got a "NO EDA HTML output" from. It would be nice just to see a quick time stamp at the bottom there.
Thanks for any help.
TABLE FILE SQLOUT PRINT * ON TABLE HOLD AS TRANS_HIER_DETAIL FORMAT XFOCUS INDEX SITE_NUM LEVEL_1 LEVEL_2 LEVEL_3 LEVEL_4 LEVEL_5 PROD_NUM END -RUN (FOC1400) SQLCODE IS -968 (HEX: FFFFFC38) : [57011] [IBM][CLI Driver][DB2/AIX64] SQL0968C The file system is full. : SQLSTATE=57011 (FOC1407) SQL FETCH CURSOR ERROR. (FOC1400) SQLCODE IS 1400 (HEX: 00000578) : SQLCODE IS -968 (HEX: FFFFFC38) (FOC1407) SQL FETCH CURSOR ERROR. : SQLOUTThis message has been edited. Last edited by: Kerry,
the HHMMSS function grabs system time when the function is encountered. so you can in fact measure elapsed time with a timestart and a timestop and measure a duration. The &TOD systemvariable only grabs the time when focus first kicks off the job, and doesn't change throughout the job. Which can make you think you're in a time warp.
I'm sure there's a more elegant way to determine duration, someone will come along and spiff us up. To use: -INCLUDE timestart ...do busy work -RUN {to make Jack happy } -INCLUDE timestop -TYPE started at: &TIMESTART stopped at: &TIMESTOP duration: &DURATIONThis message has been edited. Last edited by: susannah,
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
1. make sure to include -RUN after the "busy work" (or at the top of timestamp.fex itself); otherwise it will still report zero time elapsed. 2. It looks like the data extraction operation is overwhelming DB2 ("SQL0968C The file system is full"). I would split off the creation of the xfocus file from the extraction (TABLEF file sqlout / print * / on table HOLD / end), at least till the dust settles, so you can be certain which process fails. 3. given the size issues, it's advisable to design a standing MFD for that xfocus file and load it via Modify. 4. ... using an alternate mfd, to defer population of the indexes till after the data are loaded.
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005