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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
The only real effect is that it has to echo additional information back to your browser. In essence, the answer is no, it doesn't affect performance. The only issues i have come across are: 1. If not removed in a PROD environment, you are showing things to a user that they don't need to or should not see.
2. If the fex is scheduled in ReportCaster, all of the ECHO is added to the RC log for that job. Could fill up the logs a lot faster.
Rule of thumb: leave it in until fully tested. Comment it out (-*) before putting into production.
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
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
I have not noticed any difference when running with MRE, but I worked with one WF version that you could not schedule a job thru Report Caster if it contained ECHO or -EXIT. Oddly enough, once it was scheduled they could be added and the job would run without a problem.
Pat WF 7.6.8, AIX, AS400, NT AS400 FOCUS, AIX FOCUS, Oracle, DB2, JDE, Lotus Notes
Posts: 755 | Location: TX | Registered: September 25, 2007