 |
|||||
|
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
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. | |||||
Read-Only TopicGo | Search | Notify | Tools |
| Report Caster Error Logging | Login/Join |
| Platinum Member |
I was wondering if anyone could help me come up with a solution where I would be able to say once a say, have something run and check for any reports that for any reason my have not run in report caster for the previous day. And then I could have some sort of log either emailed to me or I can just run a report daily myself to see if anything appears on this "error list". This more of a preventative maintenance thing so I don't have users wondering why their reports didn't run over the weekend, and I would have something that shows what didn't run so I can manually run them myself. dev: WF 7.6.5 w/IIS + Tomcat prod: WF 7.6.5 w/IIS + Tomcat | ||
|
| Virtuoso |
Why don't you just turn on error notification in ReportCaster. Whenever a job fails, people get emails. Regards, Darin In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat | |||
|
| Platinum Member |
Eric, short notification to those who only need to know it failed. detailed notification for those who need to kow what went wrong.. Ira AIX 533 wf 538 aix-533,websphere 5.1.1,apache-2.0, wf 538(d), 537 (p), ============== 7.6.11 (t) aix 5312 websphere 6.1.19 apache 2.0 | |||
|
| Virtuoso |
and if you start your fex with -SET &ECHO=ALL; you get the whole script with errors in your mail.
| |||||||
|
| Expert |
Depending on the kind of RC repository you have, I would caution against leaving an ECHO in the program as astandard operating procedure. The info not only goes into the email you are sent, it also gets written to BOTLOG2. Depending on your purge interval and how many programs you have that in, you could run into space problems. Eric, have you looked at the masters for the Report Caster tables, for instance: BOTLOG, BOTLOG2, BOTSCHED, et al. You can write your own reports against these masters. You can do a few practice queries to check out the contents to see what you need to do to get in information that you want. Dates are an issue and there have been some recent posts about formating the RC dates to something human-understandable. Ginny --------------------------------- Prod: WF 7.7.01 Dev: WF 7.6.9-11 Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google | |||
|
| Virtuoso |
Ginny You are right about that warning, I forget I have encountered that problem once, but the main reason was that the report did something wrong and that created a very big error log, the process only needed one time to fill the log file. Your suggestion about the BOTLOG etc is a good one too, I will take a look and try to create a report on it.
| |||||||
|
| Virtuoso |
Interesting you should mention the &ECHO thing. I was creating a lengthy and complex procedure which we use to integrate with a legacy MVS system and included the &ECHO=ALL. It was very useful in determing when/if things ran, parameters used etc. Then I moved it into production and scheduled it to run EVERY TWO MINUTES. Needless to say, it took only a few hours before the BOTLOG tables took up all available space an caused other DBMS issues. Sad thing is, I didn't figure out that I had left in the &ECHO so we cleaned out the tables and turned things back on. Figured it out soon after when it filled up again. So I would also recommend AGAINST leaving the &ECHO=ALL in procedures scheduled in ReportCaster. Regards, Darin In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat | |||
|
| Expert |
Use -TYPE instead. Then you can pick and choose what you put in the log. Ginny --------------------------------- Prod: WF 7.7.01 Dev: WF 7.6.9-11 Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google | |||
|
| Platinum Member |
.eric, GinnyJakes, FrankDutch, Your cautions about removing &ECHO and using -TYPE in *.fex executed by RCaster are valid, but I have one further caution: Problems arise with leaving ether in active 'old' releases of RCaster. In my case, 'old' is 5.x.x. In my experience, older versions of RCaster differentiate between the 'RCaster Run Log' containing RCaster execution information and the FocEXEC's 'Message Log' containing what would go to the screen when run in MRE. They provide a dataset for the former and not for the latter, so the output from &ECHO and -TYPE has nowhere to go and the job sometimes crashes it's agent. In an old IBI Case, I was told to NEVER leave these statements active in a FOCExec run by RCaster. And I proved that experimentally by getting a job that ran OK in MRE but crashed in RCaster by simply commenting out all &ECHO and -TYPE statements. I agree, and have observed, as you have, that newer versions of the product don't have this problem and one can leave the statements active if one limits the volume of their output. WIN/2K running WF 7.6.4 Development via DevStudio 7.6.4, MRE, TextEditor. Data is Oracle, MS-SQL. | |||
|
| Platinum Member |
Thanks for all the replys guys. Using &echo wouldn't work so much because I would still have to manually check the log to see if they ran or not. Although I do use this when trying to figure out why a job didn't run. But I think using BOTLOG should work fine, I believe the start/enddates are in zulu format or something right? I saw that when looking though older posts to see if anyone was trying to do something similar. dev: WF 7.6.5 w/IIS + Tomcat prod: WF 7.6.5 w/IIS + Tomcat | |||
|
| Expert |
The times are Greenwich Mean Time. And there was a recent post all about how to do the dates and times. Ginny --------------------------------- Prod: WF 7.7.01 Dev: WF 7.6.9-11 Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google | |||
|
| Platinum Member |
Yeah, I used your solution from the other thread. I just changed it to filter out error = '1' and to show the job title name. This is the link to the other thread for reference if anyone needs it: https://forums.informationbuilders.com/eve/forums/a/tpc/...1057331/m/8101080952 Thanks for the help guys. dev: WF 7.6.5 w/IIS + Tomcat prod: WF 7.6.5 w/IIS + Tomcat | |||
|
| Powered by Social Strata |
 | Please Wait. Your request is being processed... |
Read-Only TopicCopyright © 1996-2020 Information Builders
| View $GS_USERNAME's Public Profile |
| Add $GS_USERNAME to my Ignore List |
| View Recent Posts by $GS_USERNAME |
| Notify me of New Posts by $GS_USERNAME |