I believe that IBM i developers can have a meaningful discussion with Java developers about the merits of DevOps. It is the case that we (IBM i devs) have for long implemented many of the "new" concepts like isolated development environments, automatic deployments, and isolated and protected production environments. When using a DevOps tool like TD/OMS, the concepts of task-based development, automated builds and deployments are also well established.

However, there are some new ideas that seem wild west at first but are amazingly effective when implemented. Let's go over some of these DevOps ideas and see how we measure up on the IBM i.

Proximity and Remain Software have announced a partnership to market and support Remain’s market-leading change and workflow management solutions for the IBM i, Windows, Linux and Unix in the UK and Ireland.

To IT, modernization means DDS to SQL, RPGIII to RPG Free, 5250 to Web, Web to Mobile, or any technology specific milestone or objective. To business, modernization means quicker to market, more market feedback, more sales channels, better buying power, lower operating costs, real-time performance, and operational feedback.

Remain Software is committed to protecting the privacy of individuals whose personal data we collect. Remain Software may collect personal data from individuals who register to use Remain's services, applications, and programs (“Services and Solutions”), visitors to our website, individuals who request information, prospective customers, and event attendees. This Privacy Policy describes how Remain Software and its subsidiaries and affiliated companies (“Remain Software” or “we”) collect, use, and disclose personal data, and the choices Remain Software offers regarding its collection and use of personal data.

In many conversations with IT project managers and Application architects our team sees one recurring pattern, the need to work with a unified DevOps approach. The approach should be a simplified and seamless experience for all the involved teams at all stages of the development process. Think about it, this is a huge difference how DevOps should be doing and what is really happening in day-to-day operations.

A lot of companies promote ALM solutions which are always shiny and look nice on paper. What appears quite often afterwards is that either the solutions get dysfunctional after going through many ALM processes or they become inadequate during the integration process with other tools essential for the process.