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.
Hi, I need to FTP a Report, so I am using the report caster to do the FTP. My question now is 1. If during the FTP process the file which was FTP’ed actually was a 0 byte file. In this case will the Report caster say that the FTP is successful or will it say failure? Do we have an inbuilt feature to see that the FTP’ed file is not a 0 byte file (i.e All the contents have been FTP’ed successfully)
Can anyone tell me how they have made sure that the file that they have FTP’ed did not have any data loss
You don't specify how you are generating the file, but if it is through a fex, it will not generate a 0 byte file. That, in essence, is a "no data found" and you would see that in the RC logs. If you generate with EMPTYREPORT=ON then it would not be a 0 byte file, but it would also have no data. Part of the standard FTP process checks to see that what was sent is what was received. I don't know all the goings on of that checking process, but I think we could give IBI credit enough to have already considered this. Sometimes that's a stretch, but this is a pretty basic issue with ANY FTP process. If the file transfer was not completely successful, it would show in the RC log.
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
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
My understanding is that the FTP process has built in checking and if, for whatever reason, it is isn't able to completely transfer the file, then it will throw an error. In fact, I don't believe that this situation would ever occur. If packets are lost in transmission, the process would immediately stop and you would never see the partially transmitted file because it never received the EOF. I'm not an FTP guru so someone out there is laughing at my terminology, but you get the picture. In the millions (literally) of transmissions over many years, we have never had this problem with a corrupt (or incomplete) file transfer. It either works or doesn't - never partially. But then again, that's only on our intra/extra network.
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
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007