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.
Yes, done that in the very gray past. It required something extra to be installed on the unix box to allow it to map a windows drive/directory to a unix filesystem directory. It does not work with just standard unix. And ... it has been a while ago, so I really can't remember the details any more.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
Well, if you happened to have Novell Open Workgroup Server or Open Enterprise Server as your Unix (Linux) platform you would be laughing. The Novell client attaches to the Linux box so to the user the Linux directories look like Windows folders.
There's also a product called Samba that interfaces Unix and Windows, and finally, for free, you could use PSCP to copy files from the Unix box to any Windows machine.
Most UNIXes, and certainly Linux, have builtin support for mounting smbfs file systems these days. If the drive is mounted (see man mount), you can write to it as if it were any other file system available to the OS.
That said, there are limitations to such file systems that make them less suitable to create focus files on. For example, a Windows share does not provide any means to guarantee that a write operation was flushed to disk. File locking is also somewhat limited on such file systems. If the connection gets interrupted or if something happens to the remote file system, you will end up with a corrupted file, possibly without knowing about it - the write operations completed successfully, but they never ended up on the physical disk(s).
For that reason, you will find that most databases discourage using network-based file systems to store database tables on. Focus files are effectively database tables too, so I expect IBI would discourage doing that as well.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Now that you mention focus files ... I remember, also from the gray past, that focus files created on unix could never be used in a PC environment and vice versa, because unix used a different byte order than windows. This means that when a number field is written on unix it is written as byte1-byte2-byte3-byte4 while on windows it was written as byte4-byte3-byte2-byte1 (this may actually be the other way around, but that doesn't really matter). So any focus datafile written on unix could not be read by pc focus and vv. I had to table out, transport data and modify in again - rebuild also would not work between those platforms.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007