Re: Empty RSEXXXXX members...

On Thu, 14 Feb 2013 at 22:41:22, Mike Hockings <hockings@xxxxxxxxxx> wrote:

Yes, up until the 8.0.3-ish time (going from memory here so I could be
wrong as things start to get fuzzy this late in the day) there was a
problem that would leave residue of the temp RSE* member in the cache so
the next time you start they would appear in the RSE view. Refreshing the
RSE view would resolve the problem. So asking you to refresh the RSE view
was more or less a test to see if the problem had come back somehow - I
don't think it possible but you never know...

An empty RSE* member in the IBM i file system would seem to indicate to me
that a save had been attempted and only got so far as creating the temp
file before the connection was lost to the IBM i thus indicating a dubious
connection. And can I point out that it didn't result in an empty source
member thanks to the two-phase save that is used now. Ain't those RDP
developers smart or what !

Actually Mike I wasn't the one with a problem with them appearing in the RSE view. They only appear there for me when they actually existed on the IBM i.

You are correct about the connection being lost. I would dispute the "dubious" part - my comms (other than as noted below) are pretty solid. Besides it happens no matter what system I am connected to and no matter where I am at the time (customer site, hotel, home office). I wonder if perhaps RDP uses a different comms mechanism to create the temporary member than it uses for the actual save. I have an occasional problem where the firewall times me out if I haven't done anything for a while - I do some more editing (without realizing that the connection is "broke") and then try a save. There is a brief delay and then I am told the connection has failed. In the meantime it seems to have created the temp file but cannot do the actual save. I have often wondered why RDP doesn't offer a keep-alive option on _all_ of its connection types. It would certainly save me some grief.

And yes - those RDP developers are smart. And nice folks too. Did I mention handsome/beautiful? <grin> Although the debugger developers were a bit stubborn about fixing their comms architecture! Finally fixed but it took a lot of years.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com