×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Speed has not been an issue for us on WDSC doing this. We are on a 1GB Ethernet network between the developers and the iSeries
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Monday, July 13, 2009 5:49 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Using IFS for workspace
Mike,
IBM has always recommended that the workspace should be local to your
client. The IFS is comparatively slow as a file server to begin, and
unless you have gigabit Ethernet, a few workstations can easily consume
a significant portion of your network bandwidth.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mike Cunningham
Sent: Monday, July 13, 2009 3:42 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: [WDSCI-L] Using IFS for workspace
Is anyone using RDi and pointing the workspace to a location on the IFS
via a drive mapping? We have been doing this with WDSC for a few years
because we would get the workspace corrupted on occasion and when we use
the IFS they can backup up nightly and we can restore a workspace and
save some time. We just started using RDi 7.5 and are having problems
with developers who are using the IFS for workspace but not on those
using local C: drive for workspace. The RDi errors are not consistent
but do only happen with those using IFS workspaces.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.