Re: RDi blues...

[Brian Parkins <goodprophet.bp@xxxxxxxxx>]

(Cross-posted from RPG-List)

As other have already indicated, this issue does happen occasionally. 
From my own personal experience, I believe it results from RDi 
suffering temporary disconnects due to network issues. RDi then gets 
itself in a tizzy between local/remote source code.

Frustrating, but I guess something we have to live with in this 
client/server world. (I doubt we'll ever get the solid connectivity 
we've enjoyed with simple 5250 emulation over an internal LAN.)

To solve the problem, try renaming, (or deleting) the downloaded source 
code that exists in your Workspace. This usually works for me.

Drill down - C:\ . . . 
.\<workspace>\RemoteSystemsTempFiles\<server>\QSYS.LIB\<library>\. . .

Others have suggested changing timeout values to address the problem. 
Here's another tip: have you tried using iProjects in RDi? I find this a 
useful way of organising the source code locally, thus avoiding some of 
the back & forth, download/upload of source members. Just "push" the 
source back when you need to - less traffic and less impact from 
connectivity issues. (You always have the source "master copy" at your 
finger tips, on your workstation.)

HTH.

Brian.

On 10/09/2018 16:46, john erps wrote:
> Does anybody else have the problem that so now and than it suddenly
> complains about "Operation failed. File system input or output error"?
>
> Time-out?
>
> Yes. For RDi that is.
>
>
> I'm going to check Liam's editor.
>
> RDi is no fun. AT ALL