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.
OK, the communication error seems to have gone away, and it works fine for PDF.
However, I want to be able to send EXCEL or EXL97 files and it doesn't want to accept XLS a a valid file format. If I HOLD AS EXL2K and put XHT it sends me the file in the format filename.htm not a pure Excel format.
I want a vanilla Excel output because we use OpenOffice and not M$ products.
Originally posted by George Patton: OK, the communication error seems to have gone away, and it works fine for PDF.
However, I want to be able to send EXCEL or EXL97 files and it doesn't want to accept XLS a a valid file format. If I HOLD AS EXL2K and put XHT it sends me the file in the format filename.htm not a pure Excel format.
I want a vanilla Excel output because we use OpenOffice and not M$ products.
Suggestions ??
Also covered in a prev. post. In short, the 'EXCEL' files that WebFocus produces are XHMTL files that Excel is forced to open. If you do a normal, vanilla, ON TABLE PCHOLD FORMAT EXL2K and then open the result in Excel (it should actually open in Excel by default) and then try to File > Save As... you will see at the bottom that WFServlet.xls is actually in quotes, meaning it is forcing the filename (and more importantly the extension). To get things like formulas, Data Filters, etc (excelish things), you will have to specify the file type.
That said, it is my belief that OpenOffice Calc will work with this format as well as Excel. You can test this yourself with my first example:
TABLE FILE CAR
PRINT
*
ON TABLE HOLD AS MAIL_FILE FORMAT EXL2K
END
-RUN
EX EDAMAIL my.email@address.com,,edamail test,A,XHT,MAIL_FILE
With true MS Excel deployed, I was prompted with the 'I don't know what to do with this file, select a handler' list. After choosing Excel, it opened normally with all the warts and whistles. That tells me that if I register XHTM as a file type and tell it to open with Excel, everything becomes transparent. If this is the case (I'm theorizing up until this point), if the user were to select OpenOffice.org Calc instead, and choose to do that from now own, the process would become seamless. Even more seamless would be if your IT dept were to manage all the systems and register that filetype to OO.o Calc so the users don't have to do that onetime set up step.
If that is not good enough, you could look into Excel templates which are whole other topics by themselves. Beware, I think it's a big pile of hurt just to get an xls extension on a file. I'd rather you do a FORMAT LOTUS and use a CSV extension before u use templates.
Originally posted by ABT: If this is the case (I'm theorizing up until this point), if the user were to select OpenOffice.org Calc instead, and choose to do that from now own, the process would become seamless. Even more seamless would be if your IT dept were to manage all the systems and register that filetype to OO.o Calc so the users don't have to do that onetime set up step. - ABT
"if your IT department..." - that's ME unfortunately - an IT department of one, jack of all trades, master of none ..
I'll check on the file associations and I'm going to try all the output filetypes with EX EDAMAIL to see which ones actually work. CSV would be fine in most cases because my users want to manipulate the data and fancy headings are of little interest. The EXL2K does open in OpenOffice but with html-type borders on all the cells and vertical spacing issues. If I open it in Lotus Symphony the vertical spacing and borders are OK but I can't save any changes unless I copy the entire sheet to a new spreadsheet.
There is a Data import facility that works, but again I'm trying to make this easy for my users, who are itching for me to buy M$ Office, but I ain't gonna do it.
EX EDAMAIL to, from, subject, [flag], filetype, data
This works
TABLE FILE CAR PRINT COUNTRY CAR MODEL DCOST ON TABLE HOLD AS MAIL_FILE FORMAT EXL2K END -RUN -MRNOEDIT EX EDAMAIL myemail@edamail.com, , edamail test,A,XHT,mail_file
Note the lack of spaces for the last 3 parameters and also NO .xht on the file name
Done via MRE hence the need for the -MRNOEDIT
JG, in MRE where do we have the settings for email and server name? Could you pls say the path! I know one in report caster, is the same settings work for EDAMAIL?
WebFOCUS 7.6.4, Mainframe Focus Windows XP, All Output Formats
For MRE it's exactly the same as for none MRE WebFOCUS. The e-mail server is configured in the WebFOCUS server console see ABT's post.
The -MRENOEDIT is required because MRE tries to find the procedure EDAMAIL so that it can parse it. However it will never find it because it's an internal IBI process.
I did some testing yesterday and the only formats I could get EDAMAIL to recognise and send are the following. The first column here is the desired output and the second column is what I put as the filetype. None of the other HOLD outputs, like ALPHA, COMMA, or COMT work.
OUTPUT FILETYPE
PDF PDF
EXCEL EXCEL (output in Excel95 format)
EXL97 EXCEL
EXL2K XHT
HTML HTML
Not really. It does produce output but it's garbled. Some header/formatting information seems to be missing (I haven't checked). The only outputs that are "perfect" are HTML, PDF and EXL2K. The latter can be opened with OO, but the formatting isn't great. I get a lot better formatting with PCHOLD FORMAT EXL97. We'll be installing ReportCaster soon and I hope that will solve a few issues.
In running this through Managed Reporting, has anyone else noticed that the FEX name has to be named EDAMAIL.fex? It's as if it's calling itself. For fun, I tried renaming the EDAMAIL call to EDAMAIL1 (EX EDAMAIL1 etc etc etc) and renaming the FEX EDAMAIL1.fex and running, but that seemed to be caught up in a loop. I killed it before I could tell (or crash the server).
Anyone else have any experience in creating the file as 'Some_long_fex_name.fex', putting the following code in and it running successfully?
TABLE FILE CAR
PRINT COUNTRY
ON TABLE HOLD AS MAIL_FILE FORMAT PDF
END
-RUN
EX EDAMAIL my.email@address.com,,edamail test,A,PDF,MAIL_FILE
Also, in the interest of documentation. Separating the addresses with semicolons seems to cause the second to be interpreted as a BCC.
TABLE FILE CAR
PRINT COUNTRY
ON TABLE HOLD AS MAIL_FILE FORMAT PDF
END
-RUN
EX EDAMAIL TO.PERSON@domain.com;BCC.PERSON@domain.com,,EDAMAIL TEST,A,PDF,MAIL_FILE
Originally posted by ABT: Also, in the interest of documentation. Separating the addresses with semicolons seems to cause the second to be interpreted as a BCC.
TABLE FILE CAR
PRINT COUNTRY
ON TABLE HOLD AS MAIL_FILE FORMAT PDF
END
-RUN
EX EDAMAIL TO.PERSON@domain.com;BCC.PERSON@domain.com,,EDAMAIL TEST,A,PDF,MAIL_FILE
- ABT
I tried BCC in WF 7.6.4, it isn't working.
WebFOCUS 7.6.4, Mainframe Focus Windows XP, All Output Formats
Originally posted by Vinay Kumar: I tried BCC in WF 7.6.4, it isn't working.
I just tested again and verified that the code as written above does come in as a BCC. Our mail system is Groupwise (server and client) if that make a difference.
I did confirm with our email folks that this is either an issue with our STMP engine or Groupwise's interpretation of the task. My workaround has just been to call EDAMAIL several times, once per address.