This is the distribution and support site for the FREE Work with IBM i client project.
❗ 1/2/2026 - The new beta version of the Work with IBM i app V1.0.1.14 is now available.
For initial distribution control I'm asking people to send me a request email and I will provide a download link. I don't want this app in wide distribution until I feel comfortable things are working as expected.
Title the email: Requesting Access to Work with IBM i V1.0.1.14.
Email: richard@mobigogo.net -or- richard@richardschoen.net
⬛ V1.0.1.14 will immediately deprecate older versions of Work with IBM i that were using SSH connectivity. The new version utilizes IBM i Access port functionality so you will need access to your IBM i system over ports (446-449, 8470-8479). I may bring back SSH functionality at some point, but the direct connect is so much nicer for performance and session control.
All questions and issues should be reported via this GitHub site. You'll need to open an issue with detailed info and screenshots on what your problem is if something isn't working right.
Please DO NOT download V1.0.1.9 or older releases. Only work with version V1.0.1.13 and above
Since PDM and SEU are being deprecated over time, The goal of this project is to create a FREE Windows based alternative for PDM developers who are just starting the journey to move their development to the Windows desktop.
Both VS Code and RDi are good development environments, but it's good to have options. Especially ones that give you editor freedom of choice and ability to use existing PDM user options.
Latest Version: V1.0.1.13
I started this project more for some .Net Core WinForms practice, but so far it appears to be quite useful and the core app is FREE to use.
The purpose of Work with IBM i is to provide a usable Windows based replacement for PDM for the 5250 green screen version of PDM to work with IBM i source members without needing a green screen.
Work with IBM i supports integration with iForGit which is the subscription based Git source client for IBM i that I created. Learn more here: https://www.iforgit.com or https://www.github.com/richardschoen/iforgit
The app contains a built-in text editor, but many people these days want to use VS Code for editing source. The application supports using VS Code and the relevant syntax editors available as part of the Code for i plugins.
You can actually use any Windows based editor of choice to edit or view source file content: including Notepad, Notepad++, VS Code, internal. internal is the default setting for the viewer and editor to utilize the internal text editor. You can also use a separate editor and viewer if desired. To use RDI requires a modified strategy of using Work with IBM i to download files and then edit locally with RDI. See this link: https://github.com/richardschoen/workwithibmipdm/blob/main/using_rdi_for_editing.md
PDM user options are supported as long as they don't expect to interface with a 5250 interface. The PDM options file setting defaults to: QGPL/QAUOOPT and can be changed in the settings file. This is a great way to re-use your existing PDM user option commands from Work with IBM i.
The Work with IBM i client also provides a direct interface to the iForGit Source Management CL commands for commiting changes to your Git repositories from your standard source physical files. Use of these commands assumes you have an iForGit annual subscription license. Learn more here: http://www.iforgit.com
The Work with IBM i client also knows if a source member has already been downloaded locally for offline/local editing and provides visual cues in the UI.
As a future enhancement .Net developers will be able to create their own alternatives to PDM user options using a C# plugin.
❗IBM i access ports (446-449 and 8470-8479) are used for communications with the IBM i operating system.
Simply enter a user, password and the host name or IP address to your IBM i system and you should be able to connect. SSH is NO LONGER required.
Send email request per above note.
The app installer is currently a ZIP archive.
You can unzip the installation to any directory, but a good location might be: C:\Program Files\MobiGoGo\MBWorkWithIBMi or simply C:\MBWorkwithIBMi
Then run the app or create a short cut to the app executable:
MBWorkWithIBMi.exe
Your AppSettings.xml file with personalized settings will get created here:
C:\Users\<username>\AppData\Roaming\MobiGoGo, LLC\Work with IBM i\AppSettings.xml
The app automatically creates a work directory here:
C:\tmp_workwithibmi
IBM i V7R3 and above.
IBM i access host servers must be running on ports 446-449 and 8470-8479.
We are using the non-SSL enabled IBM Access ports. At some point we may use the SSL enabled ports, but not in the short term as the method we're using only works with non-SSL enabled ports currently. And within the confines of your local network the non-SSL host server ports are probably acceptable for most shops.
The app creates a library named: TMPMB for temporary objects. If you ever find any objects in this library it can be safely cleared.
The app creates and uses a temporary IFS directory named: /tmp/workwithibmi. If you ever find objects in the directory the directory can be safely cleared.
There may be a few others I have not listed yet.....
Windows 10 and above. So far only tested on Windows 11.
App is based on .Net 10 so no special .Net runtimes or frameworks should be needed other than the app package.
❗
If you use Work with IBM i to download and edit source members, line numbers and source dates are NOT preserved. We're assuming you're stepping in to the brave new world of using PCs to edit your source members where binary line changes and Git or tools like WinMerge can show you exactly what has changed in a source member instead of relying on source sequence numbers and dates or initials in the first 5 columns to identify a change. Source dates and sequence numbers are outdated methods for tracking source changes when tools like Git handle the change tracking automatically in a source member.
Please submit feedback as issues on the GitHub issues tab.
You can also reach out via email: richard@mobigogo.net or richard@richardschoen.net if needed, but a GitHub issue is preferred for questions and issues.
And if you're looking for an easy to implement a Git source management solution for your IBM i Source Members and Git, look no further than iForGit. https://www.iforgit.com
MobiGoGo also provides modernization, web and mobile development, API integration, workflow and process automation consulting directly: https://www.mobigogo.net