** This thread discusses the article: TechTip: Map Your Network Drives to the IBM i **
** This thread discusses the Content article: TechTip: Map Your Network Drives to the IBM i **
This thread discusses the Content article: TechTip: Map Your Network Drives to the IBM i Just an FYI to those thinking about using the IFS for backup. We have been doing this for years but recently ran into a snag with response time when remotely connected. We have an iSeries application that opens documents in Word and Excel and these documents are stored in directories on the IFS (not QDLS). When we are locally connected the time to open or save a document is fine. When we are connected remotely through VPN to open MS Word and Excel documents, access takes literally 10 times as long to open, transmit and/or save the documents. We have been working with IBM PartnerWorld on this issue for about a year. They have brought Microsoft in on the issue. Communications traces show that there is literally ten times the amount of traffic between Word and the iSeries IFS then there is when Word tries to open or save to a PC server. Neither MS or IBM have been able to tell us why or correct the issue. Just recently they actually sent us an email throwing up their hands and recommended to us that we not use the iSeries IFS for this function (saving MS application documents) unless locally connected.
** This thread discusses the Content article: TechTip: Map Your Network Drives to the IBM i **
This thread discusses the Content article: TechTip: Map Your Network Drives to the IBM i Just an FYI to those thinking about using the IFS for backup. We have been doing this for years but recently ran into a snag with response time when remotely connected. We have an iSeries application that opens documents in Word and Excel and these documents are stored in directories on the IFS (not QDLS). When we are locally connected the time to open or save a document is fine. When we are connected remotely through VPN to open MS Word and Excel documents, access takes literally 10 times as long to open, transmit and/or save the documents. We have been working with IBM PartnerWorld on this issue for about a year. They have brought Microsoft in on the issue. Communications traces show that there is literally ten times the amount of traffic between Word and the iSeries IFS then there is when Word tries to open or save to a PC server. Neither MS or IBM have been able to tell us why or correct the issue. Just recently they actually sent us an email throwing up their hands and recommended to us that we not use the iSeries IFS for this function (saving MS application documents) unless locally connected.
Comment