However, I never saw a change when I added the. I thought, "Wow this is just a complex way to do exactly what I do in MochaSoft's TN5250 with a checkbox", but hey IBM was never accused of doing anything easy. By adding "KeepAlive=Y" to that file, it is supposed to keep the session from disconnecting from the host. These are the files created by iSeries Access when you create a host connection configuration and save it. Another suggestion that I had my hopes up, was in a forum post somewhere that indicated there was a. None have worked except the KeepAlive checkbox in the Mochasoft TN5250 program. In my free time over the last few weeks I've been search for a solution and trying various suggestions. There are things you can do to recover, like Edit/Copy/Paste into NotePad and then reverse the process-but is that really where we should be in 2011? I can't save my work back to the system, I can't reconnect (why they don't make that an RDp option is still a question) so basically I've lost everything since my last save-to-the-host. Then when I press Save, I get the "Host System Disconnected" message. But then there are those lengthy edit sessions, where I write a new subprocedure and don't save for 10 to 15 minutes. I save changes often because I'm afraid of loosing my connection. Here's what happens: I launch RDp, load 2 or 3 source member and start editing. But lately, if I turn away for more than what seems like 5 minutes, you can hear me swear in Italian. Upon my return everything would be working fine. I had been use to loading up WDSc and/or SEU/PDM and leaving it up all day-often going away from my desk for hours. But mostly I launch IBM iSeries Access when I'm on Windows.īoth iSeries Access and RDp have been timing out-dropping the connection after a short idle period as I said, for the last couple of years. I usually don't have trouble with that package. The MochaSoft TN5250 software has a "Keep Alive" checkbox that tells the software to stay connected even when idle. To accomplish this remote work, I purchased a full license to IBM Rational Developer Platform for i, also (now) known as RDp and of course I use iSeries Access for Windows along with MochaSoft TN5250 to gain green screen access to the box. This website and my RPG IV development are all done using this remote system. Even if you've already run SetKeepAlive.exe on your PCs, you should download, install and re-run setKeepAlive.įor the last few years I've been working remotely-away from the Power7 box that runs IBM i operating system. The app has been updated to accommodate IBM's Client Access v7 enhancements that better supports keep-alive.It now uses a Setup.MSI installation routine and installs the required unicode DLL if it isn't already on your system. I've modified the SetKeepAlive.exe program.So just dump it onto your PC in a folder where it should run from and use it. So I worked on that in early April 2017 and have published it here. Users have asked for a version that runs on the Windows 10 platform. Bob Cozzi's Client Access/RDi SetKeepAlive.exe Solving Disconnect Issues with IBM i Access and RDp/RDi TCP/IP Timeout Fix for RDi/RDp and Client Access under Windows Vista and Windows 7
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |