Greetings

Would anyone from this group know how to apply svn-git concepts in Mumps?
Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.

Has anyone done this?

Thanks.
Best regards,
Bianca Nunes.

On Tuesday, April 26, 2022 at 2:03:01 PM UTC-4, bianca.nun...@gmail.com wrote:
> Greetings
>
> Would anyone from this group know how to apply svn-git concepts in Mumps?
> Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
>
> Has anyone done this?
>
> Thanks.
> Best regards,
> Bianca Nunes.

Which MUMPS are you using? We routinely use git for version control of M code in our applications (https://gitlab.com/YottaDB/Util/YDBAIM is just one example of many).

Regards
– Bhaskar

On Tuesday, April 26, 2022 at 2:03:01 PM UTC-4, bianca.nun...@gmail.com wrote:
> Greetings
>
> Would anyone from this group know how to apply svn-git concepts in Mumps?
> Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
>
> Has anyone done this?
>
> Thanks.
> Best regards,
> Bianca Nunes.

As Bhaskar indicated, with YottaDB or GT.M, either will work since the routines are just normal files. I originally used SVN, but moved to GIT since it became a defacto standard that had multiple hosts (gitlab, github, etc).

For Cache/Iris or other M systems that store the routines in the database, I would look at the George James products, they are top notch and designed specifically for that environment.

Mark

Em terça-feira, 26 de abril de 2022 às 16:03:28 UTC-3, K.S. Bhaskar escreveu:
> On Tuesday, April 26, 2022 at 2:03:01 PM UTC-4, bianca.nun...@gmail.com wrote:
> > Greetings
> >
> > Would anyone from this group know how to apply svn-git concepts in Mumps?
> > Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
> >
> > Has anyone done this?
> >
> > Thanks.
> > Best regards,
> > Bianca Nunes.
> Which MUMPS are you using? We routinely use git for version control of M code in our applications (https://gitlab.com/YottaDB/Util/YDBAIM is just one example of many).
>
> Regards
> – Bhaskar

Hi Bhaskar.
Thank you for replying.

The version I'm using is:
MSM-UNIX VERSION 4.4. 0a
I'm also using MSM Workstation version 2.0.0, build 36.

Em sexta-feira, 24 de junho de 2022 às 09:43:49 UTC-3, Bianca Nunes escreveu:
> Em terça-feira, 26 de abril de 2022 às 16:03:28 UTC-3, K.S. Bhaskar escreveu:
> > On Tuesday, April 26, 2022 at 2:03:01 PM UTC-4, bianca.nun...@gmail.com wrote:
> > > Greetings
> > >
> > > Would anyone from this group know how to apply svn-git concepts in Mumps?
> > > Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
> > >
> > > Has anyone done this?
> > >
> > > Thanks.
> > > Best regards,
> > > Bianca Nunes.
> > Which MUMPS are you using? We routinely use git for version control of M code in our applications (https://gitlab.com/YottaDB/Util/YDBAIM is just one example of many).
> >
> > Regards
> > – Bhaskar
> Hi Bhaskar.
> Thank you for replying.
>
> The version I'm using is:
> MSM-UNIX VERSION 4.4. 0a
> I'm also using MSM Workstation version 2.0.0, build 36.

Hello guys.
Thank you for replying.

In MUMPS, all globals and routines are saved within the system. There are no separate files for us to open, for example, in a notepad++. Unless we manually export each and every routine through Workstation.

What I need is: when a colleague makes a change to a "Window" or routine, I have control, and know which row that colleague made the change. And that the "commit" is done only with the routine or window changed, and not the whole system. And if something goes wrong, I can go back to the previous version, via SVN or GIT. In TORTOISE SVN for example, in other languages like C#, I can see what each user has changed in each line of code, including the date. I want to do the same with MUMPS, but I don't know how to do it.

I thank you for your attention.
Best regards,
Bianca Nunes.

Em sexta-feira, 24 de junho de 2022 às 10:02:20 UTC-3, Bianca Nunes escreveu:
> Em sexta-feira, 24 de junho de 2022 às 09:43:49 UTC-3, Bianca Nunes escreveu:
> > Em terça-feira, 26 de abril de 2022 às 16:03:28 UTC-3, K.S. Bhaskar escreveu:
> > > On Tuesday, April 26, 2022 at 2:03:01 PM UTC-4, bianca.nun...@gmail.com wrote:
> > > > Greetings
> > > >
> > > > Would anyone from this group know how to apply svn-git concepts in Mumps?
> > > > Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
> > > >
> > > > Has anyone done this?
> > > >
> > > > Thanks.
> > > > Best regards,
> > > > Bianca Nunes.
> > > Which MUMPS are you using? We routinely use git for version control of M code in our applications (https://gitlab.com/YottaDB/Util/YDBAIM is just one example of many).
> > >
> > > Regards
> > > – Bhaskar
> > Hi Bhaskar.
> > Thank you for replying.
> >
> > The version I'm using is:
> > MSM-UNIX VERSION 4.4. 0a
> > I'm also using MSM Workstation version 2.0.0, build 36.
> Hello guys.
> Thank you for replying.
>
> In MUMPS, all globals and routines are saved within the system. There are no separate files for us to open, for example, in a notepad++. Unless we manually export each and every routine through Workstation.
>
> What I need is: when a colleague makes a change to a "Window" or routine, I have control, and know which row that colleague made the change. And that the "commit" is done only with the routine or window changed, and not the whole system. And if something goes wrong, I can go back to the previous version, via SVN or GIT. In TORTOISE SVN for example, in other languages like C#, I can see what each user has changed in each line of code, including the date. I want to do the same with MUMPS, but I don't know how to do it.
>
> I thank you for your attention.
> Best regards,
> Bianca Nunes.

I'll take a look at this tip: https://www.georgejames.com/deltanji
Thank you very much!

Em quarta-feira, 27 de abril de 2022 às 07:38:22 UTC-3, John Murray escreveu:
> On Tuesday, 26 April 2022 at 19:03:01 UTC+1, bianca.nun...@gmail.com wrote:
> > Greetings
> >
> > Would anyone from this group know how to apply svn-git concepts in Mumps?
> > Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
> >
> > Has anyone done this?
> >
> > Thanks.
> > Best regards,
> > Bianca Nunes.
> Bianca, are you required to use svn or git? If not, there's another way of implementing source code management for MUMPS applications. See https://www.georgejames.com/deltanji for an overview of our Deltanji product, which runs natively in the environment where you are coding.
>
> I hope you will take a look, and contact us if you would like a demo or an evaluation license.
>
> Best regards,
>
> John Murray
> Senior Product Engineer
> George James Software

Hi John.
Thank you for replying.
Unfortunately I couldn't access the link: "THE PAGE CAN’T BE FOUND."

On Friday, June 24, 2022 at 8:35:28 AM UTC-5, bianca.nun...@gmail.com wrote:
> Em quarta-feira, 27 de abril de 2022 às 07:38:22 UTC-3, John Murray escreveu:
> > On Tuesday, 26 April 2022 at 19:03:01 UTC+1, bianca.nun...@gmail.com wrote:
> > > Greetings
> > >
> > > Would anyone from this group know how to apply svn-git concepts in Mumps?
> > > Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
> > >
> > > Has anyone done this?
> > >
> > > Thanks.
> > > Best regards,
> > > Bianca Nunes.
> > Bianca, are you required to use svn or git? If not, there's another way of implementing source code management for MUMPS applications. See https://www.georgejames.com/deltanji for an overview of our Deltanji product, which runs natively in the environment where you are coding.
> >
> > I hope you will take a look, and contact us if you would like a demo or an evaluation license.
> >
> > Best regards,
> >
> > John Murray
> > Senior Product Engineer
> > George James Software
> Hi John.
> Thank you for replying.
> Unfortunately I couldn't access the link: "THE PAGE CAN’T BE FOUND."

Bianca,
It appears that the George James website is in the middle of an update, and that is why the link does not work. It's already the weekend in the UK, so wait a few days for John to get back. If you do not find a better solution, I can dig out a utility I wrote for MSM several years ago which keeps a history of routines. It runs periodically (typically, once a day) and compares the active version of every routine with the latest stored version and if they are different, the active one is added to the history. It can be run anytime on demand for all routines in a UCI or for an individual routine. The history is stored in a global, and there's a way to load any version into the routine editor. This is far from a true source management system, but it works and would be a base to build on if you wanted. You should know, it would be relatively easy to write routines to files, and then treat them with an open source app. With MSM, the problem is that you need to change the normal "load, edit, store" method of editing routines if yo want to have real code management. BTW, my utilities do not provide any sort of locking if multiple programmers are working on the same code.

On Saturday, June 25, 2022 at 6:56:55 PM UTC-4, Maury Pepper wrote:
> On 6/24/2022 12:36 PM, Maury Pepper wrote:
> > On Friday, June 24, 2022 at 8:35:28 AM UTC-5, bianca.nun...@gmail.com wrote:
> >> Em quarta-feira, 27 de abril de 2022 às 07:38:22 UTC-3, John Murray escreveu:
> >>> On Tuesday, 26 April 2022 at 19:03:01 UTC+1, bianca.nun...@gmail.com wrote:
> >>>> Greetings
> >>>>
> >>>> Would anyone from this group know how to apply svn-git concepts in Mumps?
> >>>> Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
> >>>>
> >>>> Has anyone done this?
> >>>>
> >>>> Thanks.
> >>>> Best regards,
> >>>> Bianca Nunes.
> >>> Bianca, are you required to use svn or git? If not, there's another way of implementing source code management for MUMPS applications. See https://www.georgejames.com/deltanji for an overview of our Deltanji product, which runs natively in the environment where you are coding.
> >>>
> >>> I hope you will take a look, and contact us if you would like a demo or an evaluation license.
> >>>
> >>> Best regards,
> >>>
> >>> John Murray
> >>> Senior Product Engineer
> >>> George James Software
> >> Hi John.
> >> Thank you for replying.
> >> Unfortunately I couldn't access the link: "THE PAGE CAN’T BE FOUND."
> > Bianca,
> > It appears that the George James website is in the middle of an update, and that is why the link does not work. It's already the weekend in the UK, so wait a few days for John to get back. If you do not find a better solution, I can dig out a utility I wrote for MSM several years ago which keeps a history of routines. It runs periodically (typically, once a day) and compares the active version of every routine with the latest stored version and if they are different, the active one is added to the history. It can be run anytime on demand for all routines in a UCI or for an individual routine. The history is stored in a global, and there's a way to load any version into the routine editor. This is far from a true source management system, but it works and would be a base to build on if you wanted. You should know, it would be relatively easy to write routines to files, and then treat them with an open source app. With MSM, the problem is that you need to change the normal "load, edit, store" method of editing routines if yo want to have real code management. BTW, my utilities do not provide any sort of locking if multiple programmers are working on the same code.
> Bianca,
> When you talk about controlling changes to a "Window", are these
> routines or something else?
> Where are you located?

Maury,
She is referring to MSM-Workstation Windows, which I believe was the only commercial implementation of MWAPI. I suspect they are stored in the MSM database just like routines are.

FYI Bianca, MSM, Cache, DSM-11 and probably most M implementation indeed stored routines in the M globals database. GT.M and YottaDB don't, they are plain text files on the Linux operating system and are easily handled by 'standard' version/release control systems like GIT and SVN. Unfortunately, since MSM is no longer supported, the routine Maury can provide is probably the best option you are going to find.

Mark

Hi Bianca,

John is out of the office at the moment, so I am replying on his behalf. Our website is going through a bit of a change at the moment - that link should have been auto-directed, but that appears to have not worked. You'll be able to find the original content here: http://www.gj0.net/deltanji (whilst we're transferring the information to our new site!)

If you would like any more information on Deltanji or would like to arrange a demo please get in touch with us.

Many thanks,
Laurel

Em sexta-feira, 24 de junho de 2022 às 14:36:45 UTC-3, mpepper%...@gtempaccount.com escreveu:
> On Friday, June 24, 2022 at 8:35:28 AM UTC-5, bianca.nun...@gmail.com wrote:
> > Em quarta-feira, 27 de abril de 2022 às 07:38:22 UTC-3, John Murray escreveu:
> > > On Tuesday, 26 April 2022 at 19:03:01 UTC+1, bianca.nun...@gmail.com wrote:
> > > > Greetings
> > > >
> > > > Would anyone from this group know how to apply svn-git concepts in Mumps?
> > > > Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
> > > >
> > > > Has anyone done this?
> > > >
> > > > Thanks.
> > > > Best regards,
> > > > Bianca Nunes.
> > > Bianca, are you required to use svn or git? If not, there's another way of implementing source code management for MUMPS applications. See https://www.georgejames.com/deltanji for an overview of our Deltanji product, which runs natively in the environment where you are coding.
> > >
> > > I hope you will take a look, and contact us if you would like a demo or an evaluation license.
> > >
> > > Best regards,
> > >
> > > John Murray
> > > Senior Product Engineer
> > > George James Software
> > Hi John.
> > Thank you for replying.
> > Unfortunately I couldn't access the link: "THE PAGE CAN’T BE FOUND."
> Bianca,
> It appears that the George James website is in the middle of an update, and that is why the link does not work. It's already the weekend in the UK, so wait a few days for John to get back. If you do not find a better solution, I can dig out a utility I wrote for MSM several years ago which keeps a history of routines. It runs periodically (typically, once a day) and compares the active version of every routine with the latest stored version and if they are different, the active one is added to the history. It can be run anytime on demand for all routines in a UCI or for an individual routine.. The history is stored in a global, and there's a way to load any version into the routine editor. This is far from a true source management system, but it works and would be a base to build on if you wanted. You should know, it would be relatively easy to write routines to files, and then treat them with an open source app. With MSM, the problem is that you need to change the normal "load, edit, store" method of editing routines if yo want to have real code management. BTW, my utilities do not provide any sort of locking if multiple programmers are working on the same code.

Thank you for replying.
If you can make this utility available, I would appreciate it. :)

Em sábado, 25 de junho de 2022 às 19:56:55 UTC-3, Maury Pepper escreveu:
> On 6/24/2022 12:36 PM, Maury Pepper wrote:
> > On Friday, June 24, 2022 at 8:35:28 AM UTC-5, bianca.nun...@gmail.com wrote:
> >> Em quarta-feira, 27 de abril de 2022 às 07:38:22 UTC-3, John Murray escreveu:
> >>> On Tuesday, 26 April 2022 at 19:03:01 UTC+1, bianca.nun...@gmail.com wrote:
> >>>> Greetings
> >>>>
> >>>> Would anyone from this group know how to apply svn-git concepts in Mumps?
> >>>> Here where I work, we are having issues with version control. We don't actually have any version control for Mumps.
> >>>>
> >>>> Has anyone done this?
> >>>>
> >>>> Thanks.
> >>>> Best regards,
> >>>> Bianca Nunes.
> >>> Bianca, are you required to use svn or git? If not, there's another way of implementing source code management for MUMPS applications. See https://www.georgejames.com/deltanji for an overview of our Deltanji product, which runs natively in the environment where you are coding.
> >>>
> >>> I hope you will take a look, and contact us if you would like a demo or an evaluation license.
> >>>
> >>> Best regards,
> >>>
> >>> John Murray
> >>> Senior Product Engineer
> >>> George James Software
> >> Hi John.
> >> Thank you for replying.
> >> Unfortunately I couldn't access the link: "THE PAGE CAN’T BE FOUND."
> > Bianca,
> > It appears that the George James website is in the middle of an update, and that is why the link does not work. It's already the weekend in the UK, so wait a few days for John to get back. If you do not find a better solution, I can dig out a utility I wrote for MSM several years ago which keeps a history of routines. It runs periodically (typically, once a day) and compares the active version of every routine with the latest stored version and if they are different, the active one is added to the history. It can be run anytime on demand for all routines in a UCI or for an individual routine. The history is stored in a global, and there's a way to load any version into the routine editor. This is far from a true source management system, but it works and would be a base to build on if you wanted. You should know, it would be relatively easy to write routines to files, and then treat them with an open source app. With MSM, the problem is that you need to change the normal "load, edit, store" method of editing routines if yo want to have real code management. BTW, my utilities do not provide any sort of locking if multiple programmers are working on the same code.
> Bianca,
> When you talk about controlling changes to a "Window", are these
> routines or something else?
> Where are you located?

Hi Maury
Window would be the code behind that window. Code behind the MSM-Workstation windows.
I also want version control for the routines.
I'm from Brazil.

Em segunda-feira, 27 de junho de 2022 às 06:47:50 UTC-3, Laurel James escreveu:
> Hi Bianca,
>
> John is out of the office at the moment, so I am replying on his behalf. Our website is going through a bit of a change at the moment - that link should have been auto-directed, but that appears to have not worked. You'll be able to find the original content here: http://www.gj0.net/deltanji (whilst we're transferring the information to our new site!)
>
> If you would like any more information on Deltanji or would like to arrange a demo please get in touch with us.
>
> Many thanks,
> Laurel
Hi Laurel

Thank you for replying. I was able to download it from google cache.
I have some work to do here at the company where I work. When I have time, I'll test it out here.

Bianca, to try Deltanji on MSM you will need to contact us first. Please email info@georgejames.com when you are ready to proceed, or if you require more information first.

Thanks,
John

Em quinta-feira, 30 de junho de 2022 às 14:39:59 UTC-3, John Murray escreveu:
> Bianca, to try Deltanji on MSM you will need to contact us first. Please email in...@georgejames.com when you are ready to proceed, or if you require more information first.
>
> Thanks,
> John

Hi John.

Do you offer trial version?
We need to know if it will meet our needs.

Thank you!
Bianca.

Yes Bianca, trials are available. Please email us at info(a)georgejames.com

Thanks,
John