Author: Yuliya Kirkorava

Navigating the Challenges

As technology continues to evolve, new tools and technologies are emerging in the market. Mainframe teams must keep up with these advancements to remain relevant in the fast-changing business environment. However, the adoption of new technologies by mainframe teams can be quite challenging, and organizations must adequately plan and execute these changes to take advantage of their benefits.

Here are some of the key challenges that COBOL teams face when adopting new technologies:

1. Legacy Infrastructure: While there is a push towards mainframe modernization and migration to newer technologies, many companies still rely on their legacy infrastructure to run critical business applications because mainframes and COBOL code are stable and reliable, and because many of these applications have been refined and optimized over decades of use. However, there are challenges associated with maintaining and updating legacy mainframe infrastructure, including a dwindling pool of experienced COBOL developers, security concerns, and the need to integrate with new platforms and applications.
2. Legacy Platforms: Mainframe teams run into problems when adapting to modern development platforms. These platforms may require new development skills and practices that are beyond the scope of your mainframe team.
3. Data Integration: Modern data integration often requires applications to expose APIs. However, many legacy COBOL applications do not have built-in APIs, making it challenging to leverage new technologies such as AI/ML and cloud computing.
4. Security: Mainframes are renowned for their high security and data privacy capabilities. However, with new technologies, mainframe teams must ensure that they maintain this high level of security while utilizing modern development tools and practices.

Despite these challenges, COBOL teams can implement new technologies effectively by taking a planned and systematic approach. Here are some of the strategies that organizations can adopt:

1. Collaborate: Organizations should encourage collaboration between COBOL teams and other development teams in the organization. For example, bringing DevOps culture to the COBOL team requires a shift in mindset. Collaboration between development, operations, and testing teams is crucial for effective DevOps implementation. Encourage open communication and collaboration between these teams.
2. Training and Upskilling: COBOL teams may need training on new tools and methodologies from distributed world.  Providing the right training can help everyone feel comfortable with new processes and techniques.
3. Testing: Testing is an essential aspect of adopting new technologies within mainframe COBOL teams. Organizations should invest in comprehensive testing to ensure that modern development practices and tools integrate seamlessly with legacy infrastructure.

Technology Adoption Lifecycle (TALC)

The Technology Adoption Lifecycle (TALC) was first proposed by sociologist Everett Rogers in 1962 in his book “Diffusion of Innovations”. The TALC describes the stages that a new technology goes through from its introduction to the market to its widespread adoption by users. Rogers’ theory has been widely applied to a variety of fields, including marketing, economics, and innovation management.

Frequently, an innovation is adopted first by a small group of innovators, followed by early adopters, early majority, late majority, and finally, laggards.

Let’s apply this theory to mainframe COBOL development (or PL/I) teams that have to deal with legacy applications and process upgrades. As a rule, such teams consist of experienced COBOL developers, have established work processes, and do not want to change anything in their work.

1.Find Innovators and Start Small

For many experienced COBOL developers, new technologies can be intimidating. Start small, introducing new tools and technologies gradually and only for those developers who are open to innovation (remember, there are about 2.5% of such people). Start with a small pilot project to demonstrate how new technologies can work with the existing system. This approach allows COBOL developers to become familiar with a new technology without being overwhelmed.

2.Provide Adequate Training for Early Adopters

Inadequate training is one of the biggest barriers to technology adoption. Organizations should invest in comprehensive training programs for mainframe developers to understand the concepts of new technologies and their practical uses. Online courses, seminars, and webinars are popular learning options that provide an interactive learning experience. However, even after having training, COBOL developers do not rush to introduce new processes. It is important to have repeated training, so that COBOL developers get used to the idea that introduction of new processes boosts productivity and efficiency. At this stage, it is important to hear and share experiences with Innovators. If we win buy-in from opinion leaders, we will get support of a very important group of people who will become Early Adopters.

3.Collaboration for Early Majority

Encourage collaboration between COBOL developers and other development teams to grow together and learn from one another. This may sparkle communication amongst different development teams and push for an organizational culture that values cross-functional collaboration.

4.Address Concerns of Late Majority

In order to convince other Сobol developers to embrace new technologies and processes, organizations need to address the challenges associated with adopting new technologies. One of the methods is to prepare a report or presentation that highlights the benefits and potential risks of introducing new technologies. If you listen to the people’s concerns and demonstrate a willingness to address these, you can build trust within the team, contributing to a smoother rollout.

5.Success

Of course, there will always be developers who are unwilling to embrace innovation and changes in the organization. If they amount to less than 15% of the development team, consider it as your success. Probably, these people need more time to get used to new processes, or to work through all their doubts and anxieties once again. Recognizing the success of a team may improve morale and drive better results.

Our Use Case for Adoption of GitHub Copilot in COBOL Teams

One of our clients who was struggling to modernize mainframe (their code and workflows), decided to use the above method to adopt GitHub Copilot in their COBOL teams.

We talked to the teams, discussed the advantages and disadvantages of modern AI tools, and concluded that we could give it a try, though many team members, especially experienced COBOL developers, were skeptical. To our advantage, several young employees were open to innovation and motivated to do something new.

So, we found Innovators.

The Innovators began experimenting with using Copilot in coding. They were amazed at how much time it saved them and how it helped them spot bugs they might have missed before. The AI tool also made suggestions for code updates that would improve performance and speed them up.

The Innovators shared their findings and views with the rest of the mainframe team at demo meetings over the course of a couple of months. Everyone was interested to know the opinion of the Innovators, but the rest of the COBOL team was in no hurry to change their approach to work.

Finally, we decided to organize a hands-on meeting where each team member could try installing and working with GitHub Copilot. To do this, one of the Innovators shared his screen and showed step-by-step how to install and use the AI tool within his preferred IDE – Intellij IDEA.

After the meeting, we received positive feedback from experienced COBOL developers, saying they would not mind starting to use the Github Copilot tool in their work. They wanted to see in practice how much Copilot would help or hinder their work. They became our Early Adopters!

As the Early Adopters began to trust Copilot more, they began to use it in their daily lives. They even started teaching other members of the COBOL team how to use the tool. Soon, other team members started using COBOL (Early Majority). GitHub Copilot has become an integral part of their coding process.

There are still skeptics (Late Majority) who find more and more reasons why they do not want to change their work process. Irrespective of this, we are positive, and we are sure that over time, the whole team will be open to innovation and the adaptation process will be easier.

In conclusion, the adoption of new technologies in any mainframe teams is a complex process that requires careful planning and good execution. Organizations that start innovating with the right people and invest in training, collaboration, and testing strategies can seamlessly integrate modern tools and technologies with legacy mainframe infrastructure to meet the changing business needs and stay ahead of the competition.

Author: Yuliya Kirkorava

SHARE conference has passed and this participation was a significant milestone for IBA Group. The conference marked a special anniversary for The Open Mainframe Project’s Zowe community, celebrating 5 years since the project’s initial announcement.

During the conference, IBA Group had the privilege of featuring speakers who presented the Zowe Explorer plugin for IntelliJ IDEA, showcasing the mainframe integrated development environment.  IBA Group was also mentioned in an article by Joe Winchester,  member of the Zowe Advisory Committee (ZAC) and Senior Technical Staff Member at IBM.

“I was excited to be a part of SHARE 2023! This year IBA Group showcased a suite of tools designed to help businesses implement modern DevOps for mainframes. If you didn’t get a chance to attend the conference, please feel free to reach out to me to discuss our plugins for IntelliJ.” – Alex Burak, representative of IBA Group at SHARE 2023.

Tracing the Milestones

The journey of a thousand miles begins with a single step, and for IBA Group, every version release represents a significant stride toward perfection. One of the most noteworthy releases is the Zowe Explorer plugin for IntelliJ IDEA. It’s not just a figure of speech when we say that we’ve surpassed 1,690 installations; it’s a testament to the trust and confidence the community has shown in our endeavors.

Version 1.0.0 emerged as a major game changer, introducing:

•  TSO CLI: This isn’t just a feature; it’s a revolution. Enabling users to submit TSO commands directly through IntelliJ, it brought about a new level of convenience. Working with the plugin, it is possible to establish multiple TSO CLI sessions and work with all of them at the same time. Now, basic TSO functions are available. Later we plan to add new features and provide complex scenarios handling basing on users feedback.

• File Encoding Management: Handling file encodings has always been challenging for mainframe developers. With the ability to manage and change file encodings seamlessly, we addressed a longstanding pain point. Now it is possible to change the encoding of any USS file, specifying either reloading of the file with the specified encoding tag and without changing the contents, or changing the actual contents of the file. With that, the plugin will show all the contents correctly if the source encoding was not correct.

• JES Explorer new options: With the new version, there are some new options to work with JES jobs introduced. Now it is possible to edit the source JCL, run the changed job, view its execution logs and purge the job from JES.

• UX changes: Some UX changes are introduced. The most notable – we changed the “plus” button behavior. So now, it expands to show the possible new items to create instead of being just a “plus” button that “does something”.

• Performance Enhancements: By optimizing dataset loading and other functionalities, we ensured that the user experience remained fluid and interruption-free.

• The subsequent versions, from 1.0.1 to 1.0.3, focused on refinements. These updates were pivotal in ensuring stability, compatibility across IntelliJ versions, and enhancing overall user interaction. One key fix that stands out is the resolution of a critical bug affecting the project tree, ensuring users do not face disruptions during their development journey.

Crafting the Future

Peeking into the horizon, we have already released version 1.1.0. This version is about:

• “whoami” feature to fetch the correct name of the user: This feature later gives the possibility to get the real name of the user, so that it will ease interactions with USS files.

• Hint after a connection is created: It notifies the user that after the connection is created, they are able to work with other essential plugin’s features.

• Copy + resolve conflicts: When files or folders are being copied, sometimes it makes conflicting situations when there are the same names for any of the entities. This feature helps to resolve such conflicts, providing the opportunity to decide, which kind of action will be taken.

• Dataset presets: Sometimes it is not so easy to decide the parameters of the dataset being created. The presets will provide some basic types of template working sets to work with.

• Default mask name during a mask creation: Sometimes it is not needed to provide a specific mask name and it is easier just to fetch the default list of datasets by the default user’s wildcard.

• “Duplicate” option for a dataset’s member.

• “No items found” as empty children list of the specified entity.

• Unit tests for source code: We are actively increasing the coverage of the plugin’s source code. This process may be not perfectly visible, but of course, we are working on it.

• Auto-synchronization option for datasets and file content, which we plan to make the default setting in subsequent releases. This option is turned on by default starting from 1.1.0 version of the plugin. It can be changed later in Settings->Other settings.

• Infrastructure to integrate the much-anticipated CICS plugin.

• A plethora of other user-centric features, such as a reworked UI for error messages, spool log downloads, and intuitive file sorting.

We’re aiming to bring a holistic suite of plugins to the table, encapsulating JCL, Jenkins, CICS, and COBOL functionalities. One pioneering venture we are exploring is the application of LSP technology, recently introduced by Jetbrains. Alongside, we are actively researching integration avenues with Zowe API ML.

Conclusion

In this ever-evolving domain of plugins and mainframe interactions, our team is committed not just to keep pace, but to set the pace. Our mission is singular: to make Zowe Explorer plugin for IntelliJ IDEA the go-to interface for all mainframe interactions. As we continue on this voyage, your feedback is our compass, guiding us towards creating better, more innovative solutions.

Disclaimer: All trademarks, service marks, trade names, logos, and brand names mentioned or used within this communication, including any accompanying documents, website content, or other materials, belong to their respective owners. The inclusion of these trademarks is purely for informational and referential purposes and does not imply any association, endorsement, sponsorship, or authorization by the trademark owners, unless explicitly stated. Efforts have been made to identify and acknowledge the trademarks used in this communication. However, the absence of any such acknowledgement or reference should not be interpreted as a challenge to the validity or ownership of those trademarks. Here are some of the registered trademarks mentioned in this communication: Zowe™, the Zowe™ logo, and the Open Mainframe Project™ are trademarks of The Linux® Foundation. Linux® is a registered trademark of Linux Torvalds. IntelliJ, IntelliJ IDEA, PyCharm, and PhpStorm are trademarks or registered trademarks of JetBrains, Inc. BMC, BMC Software, the BMC logo, the BMC Software logo, and other BMC marks are the exclusive properties of BMC Software, Inc. and are registered or may be registered in the U.S. and in other countries. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Broadcom®, the pulse logo, Connecting everything®, and the Connecting everything logo are among the registered trademarks of Broadcom Corporation and/or its. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Azure, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Kotlin is a registered trademark of the Kotlin Foundation. Jenkins® is a registered trademark of LF Charities Inc. Additionally, other company, product, and service names mentioned in this communication may also be trademarks or service marks of their respective owners.