IBM i Global

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Hi Michael,

even if it's not officially supported by IBM, RDi runs quite fine under macOS 12.4 Monterey

 

But only could test it on an Intel Mac - I don't have an Apple Silicon / ARM machine here. And you need some "tricks" to get it installed:

1. You have to download Installation Manager version 1.9.2.2

2. From the command line run: xattr -c agent.... to remove the "downloaded from the internet" attribute from the installer archive

3. Unpack

4. From the command line run: ./userinstc  -acceptLicense .... this suppresses an error you will get all the time

5. Run Installation Manager and install RDi from the official online repository

This should work if you have gatekeeper switched to "App Store and verified developers" (hopefully the translation of correct, because I use German system language).

If you need more support, just send me a mail with your questions or problems.

HTH and kind regards,

Daniel

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Hi Michael,

even if it's not officially supported by IBM, RDi runs quite fine under macOS 12.4 Monterey

 

But only could test it on an Intel Mac - I don't have an Apple Silicon / ARM machine here. And you need some "tricks" to get it installed:

1. You have to download Installation Manager version 1.9.2.2

2. From the command line run: xattr -c agent.... to remove the "downloaded from the internet" attribute from the installer archive

3. Unpack

4. From the command line run: ./userinstc  -acceptLicense .... this suppresses an error you will get all the time

5. Run Installation Manager and install RDi from the official online repository

This should work if you have gatekeeper switched to "App Store and verified developers" (hopefully the translation of correct, because I use German system language).

If you need more support, just send me a mail with your questions or problems.

HTH and kind regards,

Daniel

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Hi Michael,

even if it's not officially supported by IBM, RDi runs quite fine under macOS 12.4 Monterey

 

But only could test it on an Intel Mac - I don't have an Apple Silicon / ARM machine here. And you need some "tricks" to get it installed:

1. You have to download Installation Manager version 1.9.2.2

2. From the command line run: xattr -c agent.... to remove the "downloaded from the internet" attribute from the installer archive

3. Unpack

4. From the command line run: ./userinstc  -acceptLicense .... this suppresses an error you will get all the time

5. Run Installation Manager and install RDi from the official online repository

This should work if you have gatekeeper switched to "App Store and verified developers" (hopefully the translation of correct, because I use German system language).

If you need more support, just send me a mail with your questions or problems.

HTH and kind regards,

Daniel

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very easy - isn't it ;-) ?

I wait for the new RDi Version which should appear quickly but I still wait for. In an Interview from 1st of February this year, Steve Ferrell said, it is ready and will support the latest Eclipse with RDi (which is now 18 versions behind) and will support latest OSs on Windows and Mac (with Windows 11 for ARM you get the same problems like on new Mac OS and can solve it the same way as described in the above link).

I hope this helps and I hope that IBM is understanding that they need to speed up the Tool Chain and not going that strange MERLIN way which doesn't lead to modern tools but to the dependency of one IBM Partner and this couldn't be the solution.

Making RDi better and / or support the Visual Studio Code Open Source Tools will be the better way. We already use Git and Jenkins with RPG / Cobol for years so we don't need a Linux to do that for IBM i.

It would be great if IBM will understand what they really have with their native IBM i. With the ILE environment because in these times where Cyberwar is everywhere you need a secure System and IBM I with ILE is really secure.
See the Security Patches for IBM I and which Parts they affect.
Everything but not ILE!

We create fast and secure Microservices and Webservices ONLY with ILE.- without PASE, Websphere, Apache, and other "cool" stuff on IBM i, although I know these things very well and use them in some projects.
But you don't need to do it if there is no need.
Since security comes into the mind of Managers (thanks to Log4j) the ILE way makes a lot of sense to more and more people.
Check how often an IBM I with native IBM I services was hacked... ;-)

Wish you a great time and success with the installation.

Kind regards
Markus

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very easy - isn't it ;-) ?

I wait for the new RDi Version which should appear quickly but I still wait for. In an Interview from 1st of February this year, Steve Ferrell said, it is ready and will support the latest Eclipse with RDi (which is now 18 versions behind) and will support latest OSs on Windows and Mac (with Windows 11 for ARM you get the same problems like on new Mac OS and can solve it the same way as described in the above link).

I hope this helps and I hope that IBM is understanding that they need to speed up the Tool Chain and not going that strange MERLIN way which doesn't lead to modern tools but to the dependency of one IBM Partner and this couldn't be the solution.

Making RDi better and / or support the Visual Studio Code Open Source Tools will be the better way. We already use Git and Jenkins with RPG / Cobol for years so we don't need a Linux to do that for IBM i.

It would be great if IBM will understand what they really have with their native IBM i. With the ILE environment because in these times where Cyberwar is everywhere you need a secure System and IBM I with ILE is really secure.
See the Security Patches for IBM I and which Parts they affect.
Everything but not ILE!

We create fast and secure Microservices and Webservices ONLY with ILE.- without PASE, Websphere, Apache, and other "cool" stuff on IBM i, although I know these things very well and use them in some projects.
But you don't need to do it if there is no need.
Since security comes into the mind of Managers (thanks to Log4j) the ILE way makes a lot of sense to more and more people.
Check how often an IBM I with native IBM I services was hacked... ;-)

Wish you a great time and success with the installation.

Kind regards
Markus

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very easy - isn't it ;-) ?

I wait for the new RDi Version which should appear quickly but I still wait for. In an Interview from 1st of February this year, Steve Ferrell said, it is ready and will support the latest Eclipse with RDi (which is now 18 versions behind) and will support latest OSs on Windows and Mac (with Windows 11 for ARM you get the same problems like on new Mac OS and can solve it the same way as described in the above link).

I hope this helps and I hope that IBM is understanding that they need to speed up the Tool Chain and not going that strange MERLIN way which doesn't lead to modern tools but to the dependency of one IBM Partner and this couldn't be the solution.

Making RDi better and / or support the Visual Studio Code Open Source Tools will be the better way. We already use Git and Jenkins with RPG / Cobol for years so we don't need a Linux to do that for IBM i.

It would be great if IBM will understand what they really have with their native IBM i. With the ILE environment because in these times where Cyberwar is everywhere you need a secure System and IBM I with ILE is really secure.
See the Security Patches for IBM I and which Parts they affect.
Everything but not ILE!

We create fast and secure Microservices and Webservices ONLY with ILE.- without PASE, Websphere, Apache, and other "cool" stuff on IBM i, although I know these things very well and use them in some projects.
But you don't need to do it if there is no need.
Since security comes into the mind of Managers (thanks to Log4j) the ILE way makes a lot of sense to more and more people.
Check how often an IBM I with native IBM I services was hacked... ;-)

Wish you a great time and success with the installation.

Kind regards
Markus

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very easy - isn't it ;-) ?

I wait for the new RDi Version which should appear quickly but I still wait for. In an Interview from 1st of February this year, Steve Ferrell said, it is ready and will support the latest Eclipse with RDi (which is now 18 versions behind) and will support latest OSs on Windows and Mac (with Windows 11 for ARM you get the same problems like on new Mac OS and can solve it the same way as described in the above link).

I hope this helps and I hope that IBM is understanding that they need to speed up the Tool Chain and not going that strange MERLIN way which doesn't lead to modern tools but to the dependency of one IBM Partner and this couldn't be the solution.

Making RDi better and / or support the Visual Studio Code Open Source Tools will be the better way. We already use Git and Jenkins with RPG / Cobol for years so we don't need a Linux to do that for IBM i.

It would be great if IBM will understand what they really have with their native IBM i. With the ILE environment because in these times where Cyberwar is everywhere you need a secure System and IBM I with ILE is really secure.
See the Security Patches for IBM I and which Parts they affect.
Everything but not ILE!

We create fast and secure Microservices and Webservices ONLY with ILE.- without PASE, Websphere, Apache, and other "cool" stuff on IBM i, although I know these things very well and use them in some projects.
But you don't need to do it if there is no need.
Since security comes into the mind of Managers (thanks to Log4j) the ILE way makes a lot of sense to more and more people.
Check how often an IBM I with native IBM I services was hacked... ;-)

Wish you a great time and success with the installation.

Kind regards
Markus

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very easy - isn't it ;-) ?

I wait for the new RDi Version which should appear quickly but I still wait for. In an Interview from 1st of February this year, Steve Ferrell said, it is ready and will support the latest Eclipse with RDi (which is now 18 versions behind) and will support latest OSs on Windows and Mac (with Windows 11 for ARM you get the same problems like on new Mac OS and can solve it the same way as described in the above link).

I hope this helps and I hope that IBM is understanding that they need to speed up the Tool Chain and not going that strange MERLIN way which doesn't lead to modern tools but to the dependency of one IBM Partner and this couldn't be the solution.

Making RDi better and / or support the Visual Studio Code Open Source Tools will be the better way. We already use Git and Jenkins with RPG / Cobol for years so we don't need a Linux to do that for IBM i.

It would be great if IBM will understand what they really have with their native IBM i. With the ILE environment because in these times where Cyberwar is everywhere you need a secure System and IBM I with ILE is really secure.
See the Security Patches for IBM I and which Parts they affect.
Everything but not ILE!

We create fast and secure Microservices and Webservices ONLY with ILE.- without PASE, Websphere, Apache, and other "cool" stuff on IBM i, although I know these things very well and use them in some projects.
But you don't need to do it if there is no need.
Since security comes into the mind of Managers (thanks to Log4j) the ILE way makes a lot of sense to more and more people.
Check how often an IBM I with native IBM I services was hacked... ;-)

Wish you a great time and success with the installation.

Kind regards
Markus

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very easy - isn't it ;-) ?

I wait for the new RDi Version which should appear quickly but I still wait for. In an Interview from 1st of February this year, Steve Ferrell said, it is ready and will support the latest Eclipse with RDi (which is now 18 versions behind) and will support latest OSs on Windows and Mac (with Windows 11 for ARM you get the same problems like on new Mac OS and can solve it the same way as described in the above link).

I hope this helps and I hope that IBM is understanding that they need to speed up the Tool Chain and not going that strange MERLIN way which doesn't lead to modern tools but to the dependency of one IBM Partner and this couldn't be the solution.

Making RDi better and / or support the Visual Studio Code Open Source Tools will be the better way. We already use Git and Jenkins with RPG / Cobol for years so we don't need a Linux to do that for IBM i.

It would be great if IBM will understand what they really have with their native IBM i. With the ILE environment because in these times where Cyberwar is everywhere you need a secure System and IBM I with ILE is really secure.
See the Security Patches for IBM I and which Parts they affect.
Everything but not ILE!

We create fast and secure Microservices and Webservices ONLY with ILE.- without PASE, Websphere, Apache, and other "cool" stuff on IBM i, although I know these things very well and use them in some projects.
But you don't need to do it if there is no need.
Since security comes into the mind of Managers (thanks to Log4j) the ILE way makes a lot of sense to more and more people.
Check how often an IBM I with native IBM I services was hacked... ;-)

Wish you a great time and success with the installation.

Kind regards
Markus

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very easy - isn't it ;-) ?

I wait for the new RDi Version which should appear quickly but I still wait for. In an Interview from 1st of February this year, Steve Ferrell said, it is ready and will support the latest Eclipse with RDi (which is now 18 versions behind) and will support latest OSs on Windows and Mac (with Windows 11 for ARM you get the same problems like on new Mac OS and can solve it the same way as described in the above link).

I hope this helps and I hope that IBM is understanding that they need to speed up the Tool Chain and not going that strange MERLIN way which doesn't lead to modern tools but to the dependency of one IBM Partner and this couldn't be the solution.

Making RDi better and / or support the Visual Studio Code Open Source Tools will be the better way. We already use Git and Jenkins with RPG / Cobol for years so we don't need a Linux to do that for IBM i.

It would be great if IBM will understand what they really have with their native IBM i. With the ILE environment because in these times where Cyberwar is everywhere you need a secure System and IBM I with ILE is really secure.
See the Security Patches for IBM I and which Parts they affect.
Everything but not ILE!

We create fast and secure Microservices and Webservices ONLY with ILE.- without PASE, Websphere, Apache, and other "cool" stuff on IBM i, although I know these things very well and use them in some projects.
But you don't need to do it if there is no need.
Since security comes into the mind of Managers (thanks to Log4j) the ILE way makes a lot of sense to more and more people.
Check how often an IBM I with native IBM I services was hacked... ;-)

Wish you a great time and success with the installation.

Kind regards
Markus

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very Respectfully,

Michael Mayer

IBM i on Power System Admin.

IT Operations.

The Florida Bar

651 E. Jefferson St

Tallahassee, Florida 32399-2300

mmayer@floridabar.org

https://www.floridabar.org

Office: 850.561.5761

Cell: 518.641.8906

IBM i Reference blog page: http://ibmireference.blogspot.com/

Please note: Florida has very broad public records laws. Many written communications to or from The Florida Bar regarding Bar business may be considered public records, which must be made available to anyone upon request. Your e-mail communications may therefore be subject to public disclosure.

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very Respectfully,

Michael Mayer

IBM i on Power System Admin.

IT Operations.

The Florida Bar

651 E. Jefferson St

Tallahassee, Florida 32399-2300

mmayer@floridabar.org

https://www.floridabar.org

Office: 850.561.5761

Cell: 518.641.8906

IBM i Reference blog page: http://ibmireference.blogspot.com/

Please note: Florida has very broad public records laws. Many written communications to or from The Florida Bar regarding Bar business may be considered public records, which must be made available to anyone upon request. Your e-mail communications may therefore be subject to public disclosure.

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very Respectfully,

Michael Mayer

IBM i on Power System Admin.

IT Operations.

The Florida Bar

651 E. Jefferson St

Tallahassee, Florida 32399-2300

mmayer@floridabar.org

https://www.floridabar.org

Office: 850.561.5761

Cell: 518.641.8906

IBM i Reference blog page: http://ibmireference.blogspot.com/

Please note: Florida has very broad public records laws. Many written communications to or from The Florida Bar regarding Bar business may be considered public records, which must be made available to anyone upon request. Your e-mail communications may therefore be subject to public disclosure.

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Very Respectfully,

Michael Mayer

IBM i on Power System Admin.

IT Operations.

The Florida Bar

651 E. Jefferson St

Tallahassee, Florida 32399-2300

mmayer@floridabar.org

https://www.floridabar.org

Office: 850.561.5761

Cell: 518.641.8906

IBM i Reference blog page: http://ibmireference.blogspot.com/

Please note: Florida has very broad public records laws. Many written communications to or from The Florida Bar regarding Bar business may be considered public records, which must be made available to anyone upon request. Your e-mail communications may therefore be subject to public disclosure.

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

We all understand that "Wrong" Michael.

But this is an important discussion thread and you need to report this problem directly to the IBM folks. Simply asking people not to post here is not the way to go. This is an important thread for those of us who use Mac and should be maintained. It was started by someone with the same name as you and IBM's software is screwing up for some reason.

Please just report it to IBM and ignore any emails related to Macs and IBM i.

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

• Multi-cursor
• Linting
• Ease of managing extensions
• Support (extensions) for non-IBM i source like Python, JavaScript, bash, JSON, XML and more
• Price
• It's open source - so you can change it if you like (and know JavaScript) and help extending the product

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

Hi Sean,

this sounds very bad and strange.

I have RDi installed and running (even with some Plugins like iSphere or CMOne) on my MacBook Pro M1 Max and MacBook Air M2 running Mac OS Ventura 13.2 without problems.
So I would say it is not a general problem at all but it is very sad that it is still not supported for actual Operating Systems.

Maybe you uninstall everything and install it again with the instructions I mentioned in my post above from 27th of July 2022:

https://www.ibm.com/support/pages/issues-rational-developer-i-rdi-v960x-and-macos-big-sur-version-11

This should work also with Ventura and RDi 9.6.0.12

We all still hope that a new RDi Version soon appears based on actual Eclipse and supporting actual Operating Systems like the Mac OS Versions as well as the Windows 11 for ARM.
On the other side Visual Studio Code together with the Code4i Add Ons should also get better quickly so it can be a real alternative for RDi.
Depending on what you want to do it is already an alternative...

I wish you success and would like to read about your results.

Kind regards
Markus

------------------------------
Markus Litters

Original Message:
Sent: Tue February 07, 2023 06:50 PM
From: Sean Batson
Subject: What's an IBM i Mac RDi Developer to do?

I have run into issues where v9.6 was part of a macOS upgrade from 11, 12 and now 13 worked without issue at V9.6.0.6 and made the mistake of updating to the latest v9.6.0.12. That was the end of the IDE. Installers don't work, and the IDE doesn't run. It seems the only stable support IBM has for this is Windows.

------------------------------
Sean Batson

Original Message:
Sent: Mon July 25, 2022 03:46 PM
From: Michael Mayer
Subject: What's an IBM i Mac RDi Developer to do?

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

------------------------------
Michael Mayer
------------------------------

In regards to Windows 11 for ARM, you should theoretically be able to run any Windows version of RDi. Windows 11 for ARM has a built-in x86 emulator so any x86/x64 apps should theoretically run. I have used Windows 11 for ARM with Parallels and QEMU for VMs.  Parallels has a quick install option which is nice.

------------------------------
Richard Schoen
------------------------------

Original Message:
Sent: Wed February 08, 2023 01:23 PM
From: Markus Litters
Subject: What's an IBM i Mac RDi Developer to do?

Hi Sean,

this sounds very bad and strange.

I have RDi installed and running (even with some Plugins like iSphere or CMOne) on my MacBook Pro M1 Max and MacBook Air M2 running Mac OS Ventura 13.2 without problems.
So I would say it is not a general problem at all but it is very sad that it is still not supported for actual Operating Systems.

Maybe you uninstall everything and install it again with the instructions I mentioned in my post above from 27th of July 2022:

https://www.ibm.com/support/pages/issues-rational-developer-i-rdi-v960x-and-macos-big-sur-version-11

This should work also with Ventura and RDi 9.6.0.12

We all still hope that a new RDi Version soon appears based on actual Eclipse and supporting actual Operating Systems like the Mac OS Versions as well as the Windows 11 for ARM.
On the other side Visual Studio Code together with the Code4i Add Ons should also get better quickly so it can be a real alternative for RDi.
Depending on what you want to do it is already an alternative...

I wish you success and would like to read about your results.

Kind regards
Markus

------------------------------
Markus Litters

Original Message:
Sent: Tue February 07, 2023 06:50 PM
From: Sean Batson
Subject: What's an IBM i Mac RDi Developer to do?

I have run into issues where v9.6 was part of a macOS upgrade from 11, 12 and now 13 worked without issue at V9.6.0.6 and made the mistake of updating to the latest v9.6.0.12. That was the end of the IDE. Installers don't work, and the IDE doesn't run. It seems the only stable support IBM has for this is Windows.

------------------------------
Sean Batson

Original Message:
Sent: Mon July 25, 2022 03:46 PM
From: Michael Mayer
Subject: What's an IBM i Mac RDi Developer to do?

I've been a developer on IBM i and it's predecessors since 1981. I transitioned away from green screen SEU many years ago when WDSC was announced and then RDi. I then got away from Microsoft and started developing on a MacBook Pro about 15 years ago. I used VMWare to setup a virtual machine on the Mac for Windows and used RDi there. Once RDi became available for Mac, I was quite the happy camper. I love my RDi for Mac!

Much to my dismay, It appears I may need to give it up as IBM has not announced support for macOS above level 10.13.6 (that I'm aware of). I'm currently using RDi V9.5 since I can't get V9.6. Via Googling, I've seen many threads on this dilemma with input from IBM Champions Jack Woehr, Jon Paris, Scott Klement and IBM'ers like Eric Simpson and others. I've yet been able to put all that research together in one concise place and make it work. If I were able to get it to work, what's the guarantee the next macOS won't kill it?

The ole MacBook has served itself well since 2017 but it's time for a new one. Hence the huge dilemma. I cannot upgrade without being able to use RDi. It is the life-blood of my business. So I began investigating other options and have found a couple of close-but-no-cigar alternatives. Visual Studio Code for IBM i and MiWorkplace.  Now I see there is Merlin. While these have their merits, they're still no RDi and here's why (at least in my experience).

For the typical day-to-day IBM i developer, I believe there are three main perspectives we use: i-Projects, Database Developer, DDS Design. Let's first examine i-Projects differences.

Today, writing RPG code can be done in almost anything; even notepad. No biggie, right. I say nay nay. If you write in free format and utilize procedures, embedded SQL, service programs, /include, /copy then the "Outline View" is indispensable. VS Code for IBM i does not have an outline view. MiWorkplace does but it does not seem as robust. In RDi, when using op-codes like dcl-proc, dow, if, select, etc, RDi puts the end-proc, etc in for you. The others do not. The other products do have a way to make it work by making your own snippets, but, should we really have to do that? For /include and /copy, RDi gives you a way to edit and browse those members within the current member. The others do not.

Now let's examine the Database Perspective. For me, this is also an indispensable item. My RPG code is 100% SQLRPGLE. I no longer use traditional RPG I/O. I use SQL for I/O.  The only time I use a F-Spec (dcl-f) is for printer files. In addition, I no longer use DDS to create physical files. I use SQL create table.

MiWorkplace does not appear to have any database support. VS Code for IBM i has a extension to launch SQL from IBM i Access. But again, iAccess SQL is nowhere near as robust as the RDi Database Perspective. The ability to have a tree view of schemas, tables, views, etc, is huge when doing 100% embedded SQLRPG. It also give me the ability to store connection settings so that I can connect to multiple servers.

Some of my shops work with external databases such as MySQL and SQL Server. Database Perspective gives me the ability to connect to these servers very easily; and thanks to Scott Klement's JDBC from RPG service program, I've done this quite often in RPG.

In so far as the DDS design perspective goes, I've yet to find anything remotely similar. Report output is  the most tedious and mundane task of day-to-day life as a coder. I still have my 1980's vintage IBM RPG Ruler for report design! The DDS design perspective makes it so simple I no longer dread it. You just can't beat WYSIWYG design tools.

I've made no mention of Merlin in this narrative because I've yet to find any documentation on how to get it or how to install it. So I can't make any comparisons.

In conclusion, I dread having to go backwards and install Windows on a Mac. I also hope RDi isn't going away and that IBM sees the overall value in it. Not just as a stand-alone tool but for the entire IBM i value proposition was well. I have to think I'm not alone and that there are hundreds of other developers around the world in the same boat as me.

I still believe the good ole AS/400 is the greatest machine ever made. I've spent the majority of this century proving to my client base it can do anything any other system can do and then some. I've saved many IBM shops from migrating away from it. RDi was one of the tools that helped me accomplish saving these systems from going to Microsoft. 

I would love to hear if anyone else out there has faced this situation and how they've handled it. Or what tools other IBM i Mac developers use. Thanks for reading!

------------------------------
Michael Mayer
------------------------------