<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rose Sakach on Medium]]></title>
        <description><![CDATA[Stories by Rose Sakach on Medium]]></description>
        <link>https://medium.com/@rose.sakach?source=rss-581fc0caf500------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*UT_qKeZHcdb-EdL-90cDvQ.jpeg</url>
            <title>Stories by Rose Sakach on Medium</title>
            <link>https://medium.com/@rose.sakach?source=rss-581fc0caf500------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:50:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rose.sakach/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Zowe’s™ 5 Year Journey from Concept to Key Modernization Enabler for Mainframe]]></title>
            <link>https://medium.com/zowe/zowes-5-year-journey-from-concept-to-key-modernization-enabler-for-mainframe-2d42f9880ea1?source=rss-581fc0caf500------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d42f9880ea1</guid>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[zowe]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[zowe-community]]></category>
            <category><![CDATA[zowecore]]></category>
            <dc:creator><![CDATA[Rose Sakach]]></dc:creator>
            <pubDate>Mon, 28 Aug 2023 23:47:55 GMT</pubDate>
            <atom:updated>2023-08-28T23:47:55.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*IcaAnxdqdUmr34aK" /><figcaption>Open Mainframe Project’s Zowe Celebrates 5 years</figcaption></figure><h4>Zowe, a true story</h4><p>{<a href="https://github.com/zowe/community/blob/master/blogging/blog_guidelines.md#zowe-core">Core</a>} It is August of 2023. The Zowe Community, in partnership with <a href="https://openmainframeproject.org/">Open Mainframe Project</a>, are celebrating a major milestone — the 5th anniversary of the mainframe’s <strong>first-ever Open Source Project:</strong> <a href="https://zowe.org/">Zowe</a>. Community members recognized the milestone at the recent <a href="https://www.share.org/Events/SHARE-New-Orleans-2023">SHARE</a> conference hosted in New Orleans with a 14-session Zowe track including a Community-lead Zowe day and a roadmap overview for discussing plans and exchanging ideas for enhancing and growing the technology.</p><p>In 5 years, Zowe has grown and matured in many ways including:</p><ul><li>Projects (Core &amp; Extension Components)</li><li>Community membership &amp; organizational structure</li><li>Security policies, procedures, &amp; practices</li><li>Software releases &amp; downloads</li><li>Conformance programs, Vendor Extensions, Vendor Support Providers</li><li>Industry recognition (<a href="https://devopsdozen.com/devops-dozen-2022-tools-and-services-award-winners/">awards</a> &amp; <a href="https://itech-ed.com/arcati/">adoption</a>) &amp; <a href="https://interskill.com/">Education</a></li></ul><p>A pretty good resume for a concept many felt would struggle to survive in the industry. Which leads us to wonder how Zowe began. What in the world convinced very successful, highly competitive companies to collaborate and support such a mission? Many of us in the Community have heard various bits on how it all began, yet none of us seem to have the complete picture. In recognition of this major milestone, the Zowe Advisory Council (the Product Management arm of Zowe known as ZAC) felt it was the perfect time to reminisce, inquire, and unpack the untold story from the perspective of those who were there.</p><p>Over the past weeks, we spoke with several current and prior Zowe Community members from the initial contributing vendors. All of them were part of the original team responsible for the foundation on which the success of Zowe is built. As you read on, please bear in mind, there were <strong>many more people who worked tirelessly</strong> to set Zowe up for success. We wish we could, but we are not able to mention all of them. We look forward to sharing more from their accounts at future milestones. This story focuses on the recollection of the small sampling we were able to contact in a very short timeline. It is a documentary-type story that is better than we imagined with a mix of forward-thinking, determination, brilliance, generosity, heart-felt debate, common sense, relationships and trust. Do you know the Zowe story? Let’s find out. Here’s what we learned.</p><h4>Before Zowe was Zowe: The “mainframe made easy” vision</h4><p>We took our interviewees back to late 2017, early 2018 and asked them what they knew and how they participated in the project. Though many remember Zowe as code-name project Giza, <strong>Greg MacKinnon</strong><em> (Distinguished Engineer, Zowe APIML Founder/Creator, Broadcom)</em> and a select few recall the name zLUX and many remember the initial spelling of Zowe without the “w”, which didn’t survive, it failed copyright. Interestingly enough, the name is NOT an acronym and quite honestly seemed to be a result of tireless brainstorming efforts to land on something that began with a Z and was “catchy”. The next thing you know as <strong>Matt Hogstrom</strong> <em>(Distinguished Engineer, Broadcom, formerly IBM)</em> says “I was reserving the zowe.org domain” and that ignited the project. Yay, we’ve got a website. But what REALLY got this open source project going? Who started it? Why? How did it survive?</p><p>Greg recalls, it started with Rocket Software. Enter <strong>Joe Devlin</strong> <em>(former Rocket Software CTO, VP of Systems Software, Zowe z/OS Lead)</em> and <strong>Sean Grady</strong> <em>(Senior Software Architect, Zowe Web UI Lead, Rocket Software).</em> Just 3-years into his tenure, Sean led an internal hackathon to introduce a Mainframe Virtual Desktop. “I was just out of college and I wanted a better mainframe interface, not just for me, but for everyone”. Supported by Joe, who staffed the effort with talented interns, zLUX was born and ultimately became Zowe’s Web Desktop. Delivering the technology was only part and perhaps the easiest chunk of the mission. The more challenging aspect was making it universally available. Both knew instinctively they would need IBM to help make that a reality.</p><p>Meanwhile, several new-to-mainframe Broadcom Engineers were tinkering around with IBM z/OSMF APIs and FTP in an attempt to improve their efficiency by aligning processes with methods they’d used on other platforms. <strong>Gene Johnston</strong> <em>(Product Architect, Zowe CLI, Zowe Explorer, Zowe Client SDK, Broadcom)</em> recalls how he leveraged his background in Windows/Linux to cobble together technology in order to add automation and flexibility to his mainframe testing techniques. “I was running FTP in PowerShell scripts to transfer files and submit jobs”.</p><p>Not far from Gene, on the other side of the building, unknowingly, <strong>Dan Kelosky</strong> <em>(Product Architect, Zowe CLI Co-creator, Broadcom)</em> and <strong>Jason Tucker</strong> <em>(Product Architect, Zowe CLI Co-creator, Broadcom)</em> along with their colleague (at the time) <strong>Chris Boehm </strong>zoomed in on another way to solve the same need using IBM’s z/OSMF APIs. The team’s desire to gain access to a wider range of off-host technologies for both testing and dynamic environment creation &amp; teardown paired with Dan’s unyielding investigative nature to learn new technology is what ultimately led to the creation of Zowe CLI. Called “z/OSMF CLI” at the time, it immediately gained traction within the team and ultimately throughout the organization. Broadcom had uncovered a tool to modernize the mainframe experience. But Broadcom originally headed down the commercial route and introduced it as CA Brightside. Why did they contribute the CLI and eventually the API Mediation Layer to Zowe? What changed their mind?</p><h4>Educate, Contribute, and Trust: Doing what’s right for the ecosystem</h4><p>Rocket Software and Broadcom weren’t alone in their quest to deliver technology to change the interaction with and perception of the mainframe.<strong> Joe Winchester</strong> <em>(Senior Technical Staff Member, Zowe TSC, IBM)</em> put it this way “we were working on a project with similar goals as Zowe and released it in beta form.” Joe confirmed, IBM was also headed down the commercial road.</p><p>So, what tipped the scales? Wait for it… Believe it or not, a customer. It was an outspoken leader attending a Rocket Customer Advisory Council — someone who stood face-to-face with ISV leaders. That customer’s statement went something like this “<em>Rocket, IBM, and CA are all trying to solve the same problem for the platform — you [all] need to DO SOMETHING about it — join forces with each other and figure it out</em>”. If you ask anyone in the Zowe Community how this all got started, most will share some version of that quote. Indeed it was that statement that triggered the next, and probably the most critical move. Rocket’s response? Take zLUX to IBM and make the pitch to join forces.</p><p>Confidential project Giza was formed soon thereafter. While at IBM Matt Hogstrom recalls “we had a discussion with Rocket about their desktop technology and we [IBM] had ours, but we felt it wouldn’t be enough to start an Open Source project, so we reached out to CA”. Discussions began, meetings ensued and with the assistance and guidance of John Mertic, Linux Foundation Director of Program Management, the logistics associated with creating an Open Source project were tackled. <strong>Tim Brooks</strong> <em>(Product Manager, former Zowe Leader / Organizer, IBM)</em> was leading the effort on the administration side of Zowe. He recalls the early legal agreement challenges. “Each of the vendors had concerns over the IP particularly if a vendor backed out”. What ultimately mitigated this concern? A passion for doing the right thing backed by a licensing model that ensured the Community operated in good-faith. They truly recognized the collaborative result, not any individual result would be most valuable and impactful for the mainframe. To Tim’s surprise, it took weeks, not months to finalize the agreement.</p><p>It didn’t hurt that many involved early on in the project had prior experience in Open projects and were determined to learn from their past to make Zowe a success. Most agreed settling in on the technology stack was the challenge that stood out. Joe Winchester recalls “it wasn’t all peaches and roses’’ and it was very hard at first — but we landed in the right place. Greg MacKinnon put it this way, “staying open-minded, being diplomatic and focused on educating each other” proved to be the right strategy for making a selection where there was overlap. And, by the way, just about everyone mentioned, key to Zowe’s grounding was the trust and respect each of the ISV Product Managers, as well as the individual ISV leaders had for each other prior to its formation. Yes, the folks onstage at SHARE 2018. They were very supportive and influential in bringing it all together. The time was right for mainframe open source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/0*ENCgDUMbp4dc3RvV" /></figure><h4>A mainframe open source project is born</h4><p>With the technology settled, the teams somewhat formed, and the Open Mainframe Project as a home, Zowe was logistically good-to-go. But the Community knew they had a challenge ahead of them. Despite statistics showing the majority of mainframe customers were already embracing open source in other areas of their organization, everyone knew adoption on the mainframe would come with its unique challenges. Zowe was an opening act, a debut if you will, and everyone knew it had to succeed. <strong>Michael Bauer</strong> <em>(Engineering Manager, former Zowe CLI, Zowe Explorer, Zowe Client SDK Squad Lead, Broadcom)</em> put it this way “If we weren’t successful it may be life threatening for any future attempts”. The Community was in no way shape or form, in denial. They recognized a series of obstacles but this did not detract from their readiness to take them on.</p><p>When first introduced to the project, <strong>Mark Ackert</strong> <em>(Product Architect, Zowe Systems Lead, Broadcom)</em> described the skepticism and excitement over the possibilities in his initial reaction, “ I was dumbstruck at not only the thought of cooperation from competing vendors, the novelty of open sourcing any mainframe solution, but also the shifts in culture and potential this would bring to mainframe .” Mark was quick to point to immediate challenges — “How would we make software accessible to an Open Community that does not sit behind a vendor’s 100 foot wall?” Interestingly enough, what had to happen, happened. Mark mentioned how unusual it is for an open source sponsor to do much beyond hosting artifacts. The OMP changed its operating model to accommodate Zowe’s need to distribute the binaries.</p><p><strong>Elliot Jalley</strong> <em>(Product Manager, Zowe APIML, Broadcom)</em> had other concerns, “my first thought was around security, how is this going to work? And, how are various vendors going to settle in on a code, build, delivery process? “ He goes on to say, “The first planning meeting gave the project a real sense of community.” And then, it all seemed to come together, and we all felt the momentum — especially once the Community began to witness signs of adoption. What sealed the deal around true cross-vendor collaboration for Michael Bauer was witnessing another vendor showcase software he was originally responsible for delivering. “Seeing our software being demonstrated by another vendor as though it was their own was AWESOME!” This is at the heart of what makes Zowe successful. Access to the industry’s experts, leveraging all technological backgrounds, collaborating with the collective experience and expertise around the world.</p><h4>Adoption and Growth: The importance of Zowe Explorer</h4><p>Key to early adoption was the ability to experiment with minimal set-up required. Every seasoned Mainframer knows this is easier said than done. Despite some thinking the z/OS components would be first, it was initially Zowe’s CLI (~1500 weekly downloads) and the Visual Studio Code extension known as “Zowe Explorer” (~98k installs) that fired up Zowe’s adoption trend. Not at all part of the original core components of Zowe, Zowe Explorer was sort of an afterthought. Dan Kelosky explains “after publishing other mainframe extensions to assist with coding outside of Zowe in the VS Code Marketplace, I knew I’d need something that gave me access to jobs and files — at a basic level I needed a place to put the code that I wanted to highlight.” So Dan and Jason began tackling this need with a new extension fundamentally back-ended with CLI commands.</p><p>What happened next? Remember the earlier Rocket hackathon story? Once again, new-to-mainframers came to the rescue. Broadcom interns picked it up as part of a project, improved the performance by re-coding to the CLI node SDK, added capabilities and introduced it to the marketplace. The Zowe Community recognized its value soon thereafter, onboarded the code and expanded it for enterprise consumption. Voila! With a core component for managing jobs and files through a Visual Studio Code extension and minimal back-end requirements, Zowe now had traction with every mainframe educator that wanted to train a VS Code developer on z/OS. Zowe could play a vital role in mainframe modernization for every mainframe vendor. Entry point for adoption, Zowe Explorer.</p><h4>Zowe’s future is bright</h4><p>When asked whether or not they think Zowe is a success, there were mixed responses. In contrast, there is absolute unanimity in the benefits of working on an open source project. For one thing, it attracts high-performing, conscientious mindsets. <strong>Fernando Rijo Cedeno</strong> <em>(Software Engineer, Zowe CLI, Zowe Explorer, Zowe Client SDK, Broadcom)</em> put it this way “you find yourself amongst people who are very motivated and are self-starters’. Not to mention, given that all of your code contributions are tracked via commits, it increases your value, it’s like “having a transparent resume”. Elliot Jalley added “Working on an open source project gave me more confidence both technically and strategically”, indicating it fast-tracked his exposure to the wider IT landscape. While Mark Ackert rattled off a number of professional benefits including, comradery, a greater sense of teamwork, world-wide team collaboration, status, influence and a sense of ownership with visible outcomes from personal contributions.</p><p>Another benefit, sometimes perceived as a detriment is the added security afforded by open source. When asked about the consumer concerns and the perception of being less secure, Greg MacKinnon summed it up and Dan Kelosky agreed, “Open Source is perceived as being less secure but in reality it is more secure, simply because there are more eyes on it… many don’t look at it this way but when you code in the open, you are vulnerable to criticism, and that’s ultimately what helps you improve the most.” That’s certainly the case with Zowe. Highly motivated, extremely talented individuals contributing their expertise and criticism for the benefit of the platform.</p><p>Interestingly enough, our team is not collectively convinced the industry has recognized the true value of the project. Sean Grady put it this way “just about every month I meet a new customer who hasn’t heard about Zowe” and that’s disappointing. Joe Winchester admits “I predicted more people would install the z/OS components and would be building apps, I never imagined the success of Zowe Explorer and Zowe CLI”. Joe Devlin explains he’s “more disappointed than overjoyed” with the state of Zowe. Admittedly recognizing good signs of success (a la Zowe Explorer) but expecting more prominent mainframe software leveraging it. As a seasoned veteran in the space, Joe is confident Zowe will be there in 5 more years. Jason Tucker concurs and is not convinced the industry has caught on to the usefulness of Zowe CLI’s ability to connect platforms.</p><p>Despite these cautionary concerns, many view Zowe as a success. Citing the<a href="https://itech-ed.com/arcati/"> Arcati Yearbook</a> statistics of mainframe sites who have adopted or are planning to adopt Zowe, as “amazing progress” for z/OS software. But also in terms of empowering the Community itself. More than Committers, they have embraced and furthered that spirit of exploring and expanding where it makes sense for the platform. The evidence is peppered throughout Zowe’s brief history with the emergence of new projects: Client SDKs, Explorers (VS Code &amp; IntelliJ), Zowe Mobile, ZEBRA, the Workflow Wizard, Zowe Chat, ZEN, and most recently Event Management. Zowe remains on a path to “join forces and figure out” how best to bring the mainframe forward for the benefit of all.</p><p>Mark Ackert summed it up nicely. “Zowe makes too much sense. What we are doing is fundamentally core to the platform and if they don’t [know it] already, our customers will recognize how critical it is for the platform. We are in alignment. Doing the right thing for the right reasons.”</p><p>So there you have it. The origin of the first-ever Open Source Project for mainframe, changing the way the mainframe is managed forever — well grounded and going strong.</p><p>For all who played a role in Zowe’s existence and have moved on,</p><p>For all who continue to work on improving Zowe,</p><p>For all destined to join the Zowe Community,</p><p>Thank you for what you have done, are doing, and will do for Zowe, you are all a part of history.</p><p>On behalf of all Mainframers, we are forever grateful for your effort, your passion and your contributions. Happy Anniversary Zowe. Given the Community that supports you, we are certain you’ll be around for many more.</p><p>Learn more about and download Zowe at <a href="http://zowe.org/">zowe.org</a> .</p><p>Read more Zowe blogs <a href="https://medium.com/zowe">here</a>.</p><p>Ask a question or join the conversation on an <a href="https://openmainframeproject.slack.com/ssb/redirect">Open Mainframe Project Slack</a> Channel #zowe-api, #zowe-explorer-intellij, #zowe-explorer, #zowe-cli, #zowe-dev, #zowe-user, or #zowe-onboarding.</p><p>First time using the Open Mainframe Slack Channel? Register <a href="https://slack.openmainframeproject.org/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d42f9880ea1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zowe/zowes-5-year-journey-from-concept-to-key-modernization-enabler-for-mainframe-2d42f9880ea1">Zowe’s™ 5 Year Journey from Concept to Key Modernization Enabler for Mainframe</a> was originally published in <a href="https://medium.com/zowe">Zowe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brightside 4.0 Advances Mainframe Modernization with Enterprise-grade Extras]]></title>
            <link>https://medium.com/modern-mainframe/brightside-4-0-advances-mainframe-modernization-with-enterprise-grade-extras-4938ca8c4711?source=rss-581fc0caf500------2</link>
            <guid isPermaLink="false">https://medium.com/p/4938ca8c4711</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cobol]]></category>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[zowe]]></category>
            <category><![CDATA[vscode]]></category>
            <dc:creator><![CDATA[Rose Sakach]]></dc:creator>
            <pubDate>Mon, 25 Jul 2022 21:09:07 GMT</pubDate>
            <atom:updated>2022-07-25T21:09:07.942Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*soXiBN8q7cLr7iCNW-DlGQ.png" /><figcaption>Brightside introduces 4.0</figcaption></figure><p>Now that Zowe has cleared the early-adopter hurdle with the introduction of <a href="https://www.openmainframeproject.org/press/2022/05/26/zowe-lts-v2-release">Zowe V2 LTS</a>, it’s not surprising to learn, the number of mainframe customers interested in some form of experimentation with one or more components is on the rise. Zowe not only introduces open source to mainframe, its transformative approach to interacting via API services fundamentally changes the way mainframe infrastructure is managed and mainframe apps are developed. Zowe is an enabler; a foundation on which to build. The power lies in its extensibility and connectedness. This opens the door to rationalize on tooling and proven technologies — both open source and vendor instantiated — already in use within your organization. If you think of Zowe as holding the keys to the open-first approach for mainframe automation &amp; modernization initiatives, think of Brightside as your must-have starter kit for implementing them. The recently introduced 4.0 release is what you want to grab sooner rather than later to be in a position to take advantage of the latest advances in mainframe open source and stay ahead of the competition.</p><p><strong>Support for open source and more</strong></p><p>Brightside 4.0 is more than support for Zowe V2. The offering can be characterized into 3 categories: (1) Support for Open Source, (2) entitlement for proprietary software that is built-on-open, and (3) a “beyond code” partnership that lends a helping hand when you need one. We believe it is these three in combination that provide organizations with what is necessary to complete their mainframe transformation. Confidence in using open solutions, quick access to supplemental technologies that enhance them, as well as non-technical extras designed to guide, facilitate, educate and assist in getting to the finish line are key to successful modernize-in-place efforts. Let’s take a closer look at each.</p><p><strong>First<em>, be confident in not only trying but implementing open source solutions</em>.</strong></p><p><strong>Support for Open Source. </strong>Broadcom provides 24 x 7 enterprise-grade support for several open source projects. We characterize enterprise-grade as what you would expect with any vendor-owned product: always-available staff, traditional issue monitoring and tracking, access to SMEs, training and education. Supported projects include:</p><p>The<strong> </strong><a href="https://www.zowe.org/"><strong>Open Mainframe Project Zowe</strong></a> core components and plug-ins for all of the ACTIVE &amp; MAINTENANCE LTS continuous delivery releases. They include:</p><ul><li>Zowe API Mediation Layer*</li><li>Zowe App Framework*</li><li>Zowe Command Line Interface*</li><li>Zowe Explorer*</li><li>IBM® CICS® Plug-in for Zowe CLI</li><li>IBM® Db2® Database Plug-in for Zowe CLI</li><li>IBM® IMS™ Plug-in for Zowe CLI</li><li>IBM MQ for z/OS Plug-in for Zowe CLI</li><li>z/OS FTP Plug-in for Zowe CLI</li></ul><p><em>*Minimum component support coverage required to earn the comprehensive Support Provider badge via the </em><a href="https://www.openmainframeproject.org/all-projects/zowe/conformant-support-provider"><em>Zowe Conformant Support Provider Program</em></a><em>. Brightside is recognized via the </em><a href="https://landscape.openmainframeproject.org/card-mode?category=support-provider-comprehensive-zowe-v2,support-provider-explorer-for-visual-studio-code-zowe-v2,support-provider-api-mediation-layer-zowe-v2,support-provider-app-framework-zowe-v2,support-provider-cli-zowe-v2&amp;grouping=category"><em>OMP interactive landscape</em></a><em>, as a Comprehensive Support Provider for Zowe V1 and Zowe V2. </em><a href="https://medium.com/zowe/got-zowe-let-the-zowe-conformant-support-provider-program-be-your-guide-for-support-a76f61b609ee"><em>Introduced in Sept 2021</em></a><em>, the program was designed to vet the applicants’ ability to both support core components and contribute code back to Zowe in a timely manner, resulting in an easy search &amp; select for certified support vendors.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/228/0*7XMQRNXWgtf90BYp" /><figcaption>Brightside is a Zowe Conformant Support Provider</figcaption></figure><p>The <a href="https://marketplace.visualstudio.com/items?itemName=broadcomMFD.code4z-extension-pack"><strong>Code4z</strong></a><strong> VS Code Extension Pack. </strong>The pack includes extensions that help new-to-mainframe users understand program logic and become effective and efficient in developing mainframe applications with minimal platform knowledge. Code4z covers the end-to-end needs of a mainframe developer including extensions for resource access, edit, compile, debug, fault analysis, test and test data editing.<strong> </strong>This group of Visual Studio Code extensions presented together — like a bundle — make it easy for organizations to recommend and users to decide how to build their mainframe-centric modern workspace. Brightside 4.0 includes support for all Code4z 2.x releases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/0*pOJEhz0a1GKgZFoc" /></figure><ul><li>The software is available at the <a href="https://marketplace.visualstudio.com/items?itemName=broadcomMFD.code4z-extension-pack">Visual Studio Marketplace</a> as well as the <a href="https://open-vsx.org/extension/BroadcomMFD/code4z-extension-pack">Open VSX Registry</a>. We’ve included a <strong>Code4z Overview</strong> PDF at <a href="http://support.broadcom.com/">support.broadcom.com</a> in the “My Downloads” to help you navigate to the latest components and their installation instructions.</li></ul><p><strong>Second<em>, Leverage innovative solutions to further your initiatives.</em></strong></p><p><strong>Entitlement for proprietary software.</strong> Similar to 3.0, Brightside 4.0 includes Broadcom proprietary software that seamlessly interacts with and complements the foundational Zowe components. Brightside customers are entitled to download, install and use these extensions. These fully supported z/OS components are available in both PSWI and SMP/E form. They are:</p><p><strong>Test4z:</strong> Broadcom data verification APIs that introduce highly-efficient, distributed-style test automation concepts to mainframe. The Test4z open-first approach offers freedom-of-choice when selecting testing frameworks, which, in turn, encourages the implementation of mainframe test automation. Our Test4z public GitHub <a href="https://github.com/BroadcomMFD/test4z">repository</a> includes both Jest: JavaScript-based and Pytest: Python-based test framework examples which illustrate how easy it is to get started with the Jest framework. Brightside 4.0 includes Test4z 2.0 and complimentary editions of our mainframe file management and manipulation tools: File Master Plus™, File Master Plus™ for IMS and File Master Plus™ for Db2 to maximize test automation capabilities.</p><p><a href="https://medium.com/modern-mainframe/two-innovations-for-the-zowe-api-mediation-layer-from-broadcom-f2994d845ce"><strong>Zowe Conformant API-ML Extensions</strong></a>: Proprietary features requested by customers, engineered by Broadcom that work seamlessly with Zowe’s API Mediation Layer.</p><ul><li><strong>The API State Monitor for Zowe API Mediation Layer</strong> monitors the state (active, inactive, etc.) of all of the API services registered to Zowe primarily to alert for and prepare for service outages. Information is delivered to the z/OS System Log (SYSLOG) in the form of a Write To Operator (WTO) message making it easy to blend Zowe-managed service activities in with any z/OS monitoring tool and operational rules engine.</li><li><strong>The API Audit Log for Zowe API Mediation Layer</strong> produces audit logs for all of the API services registered to Zowe. Data can be (1) further analyzed through visualization tools such as <a href="https://www.elastic.co/kibana/">Kibana</a> or (2) integrated into other data sources as a means to easily identify and prevent service degradation, trace and track usernames and login events for incident investigation or trouble-shoot access issues with services.</li></ul><p><strong><em>Third, we are in this effort with you!</em></strong></p><p><strong>Beyond Code. </strong>At Broadcom, we believe in partnering for success — that means we are committed to providing a helping hand even when you haven’t reported an issue. We call this aspect of our offering “beyond code”. All Brightside customers are entitled to:</p><ul><li>Broadcom Web-based training courses at no additional cost</li><li>Request demonstrations/meetings with technical experts and product management</li><li>Schedule personalized workshop events to help progress open-first modernization initiatives</li></ul><p><strong>Broadcom’s strategic commitment to Open-First</strong></p><p>In addition to support for open source projects, we are always looking for ways to ensure your experience remains consistent and your trust is uncompromised. To that end, we certify every open source release prior to posting distributions and respond quickly to accommodate your needs.</p><ul><li>Want to acquire, install, and maintain Zowe the same way you install other Broadcom products? For the Zowe runtime z/OS components, you’ll find both a traditional <strong>SMP/E</strong> distribution as well as a Portable Software Instance (<strong>PSWI)</strong> for use with z/OSMF</li><li>Already have a Zowe distribution and you’d rather not re-install? We <strong>support any authentic Zowe distribution</strong></li><li>Looking for an offline package with all Zowe Conformant Broadcom product extensions? You’ll find an all-inclusive <strong>LOCAL PACKAGE</strong> .zip file at the “My Downloads” at support.broadcom.com</li><li>Prefer a registry distribution for Zowe CLI? We’ve got that too! Same place! Look for the <strong>Brightside CLI 4.0 Registry </strong>entry</li><li>Concerned about upgrading to Zowe v2? Brightside is an OMP certified <a href="https://www.openmainframeproject.org/all-projects/zowe/conformant-support-provider">Zowe Conformant Support Provider</a>. We’ve got SMEs for all components to help with the upgrade AND you’ve got time to plan your upgrade. Support continues for Zowe V1 LTS throughout the maintenance phase (See the <a href="https://www.zowe.org/download.html#timeline">Zowe Release Timeline</a>).</li></ul><p>Interested in speaking to the Product team? Feel free to contact us!</p><ul><li>Brightside: <a href="/service/mailto:Rose.Sakach@broadcom.com">Rose.Sakach@broadcom.com</a></li><li>Zowe Client-Side Components: <a href="/service/mailto:Rose.Sakach@broadcom.com">Rose.Sakach@broadcom.com</a></li><li>Zowe z/OS Components: <a href="/service/mailto:Elliot.Jalley@broadcom.com">Elliot.Jalley@broadcom.com</a></li><li>Code4z: <a href="/service/mailto:Ekaterina.Tumanova@broadcom.com">Ekaterina.Tumanova@broadcom.com</a></li><li>Test4z: <a href="/service/mailto:Petr.Vacula@broadcom.com">Petr.Vacula@broadcom.com</a></li></ul><p><strong>There’s never been a better time to be a Broadcom Customer</strong></p><p>If you are a Broadcom customer you’ve probably heard us speak about our “Open-First” strategy. As a Broadcom employee, we live it. Broadcom utilizes open source and is committed to delivering open interfaces, conformant extensions, applications and innovations that serve as the foundation for the open-first strategy. In addition, we’ve introduced an offering that makes it easier than ever to ensure you are well positioned to modernize critical areas at your own pace. Our <a href="https://docs.broadcom.com/doc/devops-suite">DevOps Suite</a> is a comprehensive solution that includes Brightside and a number of products that facilitate the adoption of hybrid tools and practices. As a leader and major contributor in open source communities like Zowe, Broadcom is uniquely positioned to provide the level of support and partnership customers expect and can rely on. Mainframe CAN be as easy to use and to automate as any other platform. That IS the Brightside of open-first. Let us help you get there with Brightside 4.0!</p><p><strong>Read more about Zowe V2 LTS</strong>:</p><p><a href="https://medium.com/zowe/zowe-version-2-1434a1e1ed88">https://medium.com/zowe/zowe-version-2-1434a1e1ed88</a> <a href="https://techchannel.com/Trends/07/2022/zowe-lts-v2">https://techchannel.com/Trends/07/2022/zowe-lts-v2</a></p><p><strong>More details about Broadcom’s Zowe Conformant API Mediation Layer Extensions</strong>: <a href="https://medium.com/modern-mainframe/two-innovations-for-the-zowe-api-mediation-layer-from-broadcom-f2994d845ce">https://medium.com/modern-mainframe/two-innovations-for-the-zowe-api-mediation-layer-from-broadcom-f2994d845ce</a></p><p><strong>Hear what customers are doing with Zowe:</strong> <a href="https://www.youtube.com/watch?v=b6vloD0qwuk">June 2022 Zowe Quarterly Webinar</a></p><p><strong>Learn about Test4z:</strong> <a href="https://medium.com/modern-mainframe/test4z/home">https://medium.com/modern-mainframe/test4z/home</a></p><p><strong>Learn about Code4z:</strong> <a href="https://medium.com/modern-mainframe/vscode/home">https://medium.com/modern-mainframe/vscode/home</a></p><p><strong>Getting Started with Zowe V2:</strong> <a href="https://docs.zowe.org/stable/getting-started/release-notes/v2_0_0">https://docs.zowe.org/stable/getting-started/release-notes/v2_0_0</a></p><p><strong>Zowe CLI V2 Reference Blogs:</strong></p><ul><li><a href="https://medium.com/zowe/zowe-cli-getting-started-made-easy-f53d769c678e">https://medium.com/zowe/zowe-cli-getting-started-made-easy-f53d769c678e</a></li><li><a href="https://medium.com/zowe/automatic-zowe-cli-service-configuration-using-api-mediation-layer-e0de159b6e0c">https://medium.com/zowe/automatic-zowe-cli-service-configuration-using-api-mediation-layer-e0de159b6e0c</a></li><li><a href="https://medium.com/zowe/zowe-cli-a-faster-experience-made-better-7b23e426f821">https://medium.com/zowe/zowe-cli-a-faster-experience-made-better-7b23e426f821</a></li><li><a href="https://medium.com/zowe/migrating-zowe-cli-plug-ins-for-v2-conformance-c538d75fd860">https://medium.com/zowe/migrating-zowe-cli-plug-ins-for-v2-conformance-c538d75fd860</a></li></ul><p><strong>Zowe Explorer V2 Reference Blog</strong>: <a href="https://medium.com/zowe/team-configuration-the-new-sheriff-in-town-fffa4572e983">https://medium.com/zowe/team-configuration-the-new-sheriff-in-town-fffa4572e983</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4938ca8c4711" width="1" height="1" alt=""><hr><p><a href="https://medium.com/modern-mainframe/brightside-4-0-advances-mainframe-modernization-with-enterprise-grade-extras-4938ca8c4711">Brightside 4.0 Advances Mainframe Modernization with Enterprise-grade Extras</a> was originally published in <a href="https://medium.com/modern-mainframe">Modern Mainframe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zowe Embraces Visual Studio Code Extensions]]></title>
            <link>https://medium.com/zowe/zowe-embraces-visual-studio-code-extensions-259b6cee0bec?source=rss-581fc0caf500------2</link>
            <guid isPermaLink="false">https://medium.com/p/259b6cee0bec</guid>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[zowe-community]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[zowe-explorer]]></category>
            <dc:creator><![CDATA[Rose Sakach]]></dc:creator>
            <pubDate>Thu, 18 Nov 2021 19:51:39 GMT</pubDate>
            <atom:updated>2021-11-18T19:51:39.929Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/324/0*UkQyeWNxzplyKqs2" /></figure><p>{Core} The <a href="https://linuxfoundation.org/">Linux Foundation</a>’s <a href="https://openmainframeproject.org/">Open Mainframe Project</a> <a href="https://zowe.org/">Zowe</a> has extended the <a href="https://www.openmainframeproject.org/projects/zowe/conformance">Zowe Conformance Program</a> to include Visual Studio Code extensions! This is great news for Zowe consumers, mainframers and for Visual Studio Code enthusiasts. The <a href="https://insights.stackoverflow.com/survey/2021">2021 Stack Overflow Developer Survey</a> confirmed that Visual Studio Code has a “significant lead as the IDE of choice across all developers” — at 71%, more than 4 times greater than Eclipse (16%). It should come as no surprise<strong> this has led to the emergence of numerous mainframe VS Code Extensions</strong>. And now Zowe has a means to officially embrace them. The new Zowe Explorer for Visual Studio Code conformance program ensures that VS Code users will get a superior, integrated experience with extensions designed to interact with and amplify the value of <a href="https://www.zowe.org/#zowe-explorer-intro">Zowe Explorer</a>. Instead of hoping their choice of VS Code extension “plays well” with Zowe, users simply need to look for the Zowe Explorer for Visual Studio Code conformance badge.</p><p>Similar to the existing Zowe V1 extender conformance programs like Zowe CLI and Zowe App Framework, the Zowe Explorer for Visual Studio Code program requires conformant extensions to <strong>satisfy a list of requirements. </strong>Together these confirm Zowe baseline functionality, interoperability and a consistent user experience with each Zowe release introduced within a given Long Term Support (LTS) version. All the considerations and testing criteria were developed by the Zowe Community with oversight from the Open Mainframe Project.</p><h4><strong>Explorer Basics</strong></h4><p>Since its introduction in the marketplace, Zowe Explorer downloads have steadily and continuously increased to a skyrocketing 44k with as many as 6k in a single month. But what exactly is Zowe Explorer? Simply defined, it is a Visual Studio Code extension whose primary function is to provide users with the ability to perform traditional mainframe actions from a single user interface with all the modern capabilities offered by the Visual Studio Code platform. The actions are interactive and offer capabilities focused on:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*e1_DnbEbUhM0Bla6" /></figure><ul><li>z/OS data sets in various formats (i.e. PDS, PDS/E, Flat files FB or VB)</li><li>Unix Systems Services (USS) files</li><li>z/OS Jobs</li></ul><p>A major advantage of the off-host presentation of these capabilities is the ability for users to connect into any and all mainframe systems (LPARs) with a click of the mouse. This may seem trivial, however, <strong>unlike traditional mainframe user interfaces,</strong> provided a user has the proper authority, Zowe Explorer gives users the ability to <strong>perform any of these actions on any mainframe system from a single VS Code workspace</strong>. This is particularly valuable for Systems Programmers tasked with managing and maintaining multiple LPARs or Developers needing to perform work on both DEV and PROD LPARs. No need to exit one session and enter another. All work can be performed from one VS Code window.</p><p>Although “Visual Studio Code” is not officially part of this Zowe component’s name, it is understood as the de facto Zowe integrated development environment (IDE); but won’t necessarily be the only Zowe IDE. With the pending onboarding of the IntelliJ incubator project, it is likely that a <strong>Zowe Explorer for IntelliJ</strong> — the platform that includes IDEs like IntelliJ, PyCharm, and Webstorm — with matching mainframe actions and capabilities is not too far behind. This offers developers the option to choose a preferred IDE when integrating mainframe functions in with their mobile, cloud, and distributed work.</p><h4><strong>Why Zowe Explorer Extensions</strong></h4><p>With the growing popularity of VS Code, many Vendors have introduced Visual Studio Code extensions for a variety of mainframe product-centric activities. Until now, none could earn the Zowe stamp of approval in the form of a conformance badge. The introduction of this program gives Vendors the ability to earn and showcase their V1 Conformant <strong>Zowe Explorer for VS Code extension</strong> badge. They do so by ensuring their specific Visual Studio Code extension satisfies the associated program criteria which, by section, assures extensions:</p><ul><li><strong>General</strong>: Satisfy all of the general extension requirements such as naming, user settings, and error message formats when adding any new capability</li><li><strong>Profiles: </strong>Leverage the Zowe client profile configuration to ensure consistency in host connectivity, security, and credentials management</li><li><strong>Data Provider</strong>: Serve as a data-provider that enables access to z/OS in a consistent manner to offer Zowe Explorer capabilities</li><li><strong>Menu Extensions</strong>: Add menu options and/or commands to VS Code that utilize Zowe Explorer data or extend Zowe Explorer capabilities</li></ul><p>To earn Zowe V1 conformance, at a minimum, applicants must satisfy all of the test evaluation criteria marked as <strong>required</strong> in the GENERAL EXTENSION section of the conformance test evaluation form. Beyond that, extensions that use any of the Zowe Explorer extensibility APIs ranging from accessing Zowe profiles to serving as data providers to expanding VS Code menus, must also satisfy all of the criteria marked as “required” in those sections of the form.</p><p><strong>Applying for Conformance</strong></p><p>Extenders interested in applying for Zowe Explorer for Visual Studio Code V1 conformance can navigate to the <a href="https://www.openmainframeproject.org/projects/zowe/conformance">Zowe conformance program site</a> directly or can click on the EXTEND tab from z<a href="https://www.zowe.org/">owe.org</a> to visit <a href="https://www.zowe.org/extend.html">zowe.org/extend</a> . From there simply review the program terms and conditions, view the Zowe Explorer for Visual Studio Code test evaluation criteria in the test evaluation guide and submit the signed participation form. The application is free to Open Mainframe Project members, fees apply to all others. Provided there are no findings, typical turnaround is one week. Applicants with questions can reach the Zowe Explorer squad members directly on <a href="https://openmainframeproject.slack.com/archives/CUVE37Z5F">slack</a> or may join one of their weekly scrum meetings advertised on the <a href="https://lists.openmainframeproject.org/g/zowe-dev/calendar">Zowe calendar</a> for help and assistance.</p><p><strong>Value For Extenders and Consumers</strong></p><p>As with all Zowe Conformance programs, this program serves as a means for conformant Zowe extenders to proudly display the conformance badge alongside their offering. For consumers? A means to quickly and easily determine whether or not the Visual Studio Code extension they decide to add to their workspace will not only function with their current release of Zowe, it will integrate with all of the Zowe client components, including Zowe Explorer and Zowe CLI in a manner that ensures the value-add is greater than the sum of the individual parts. Roughly translated, the next time you go shopping (via the <a href="https://marketplace.visualstudio.com/search?term=Zowe&amp;target=VSCode&amp;category=All%20categories&amp;sortBy=Relevance">Visual Studio Code Marketplace</a>) — keep an eye out for extensions proudly displaying the Zowe Explorer for Visual Studio Code V1 conformance badge as they emerge!</p><p>If you enjoyed this blog checkout more <a href="https://medium.com/zowe">Zowe blogs here</a>. Or, ask a question and join the conversation on the <a href="https://slack.openmainframeproject.org/">Open Mainframe Project Slack Channel</a> #Zowe-dev, #Zowe-user or #Zowe-onboarding. If this is your first time using the OMP slack channel register <a href="https://slack.openmainframeproject.org/">here</a>.</p><p><em>Special thanks to Michael Bauer and Michael DuBois</em></p><p><a href="https://medium.com/zowe">Read more about Zowe</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=259b6cee0bec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zowe/zowe-embraces-visual-studio-code-extensions-259b6cee0bec">Zowe Embraces Visual Studio Code Extensions</a> was originally published in <a href="https://medium.com/zowe">Zowe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Got Zowe? Let the Zowe Conformant Support Provider Program be your guide for support!]]></title>
            <link>https://medium.com/zowe/got-zowe-let-the-zowe-conformant-support-provider-program-be-your-guide-for-support-a76f61b609ee?source=rss-581fc0caf500------2</link>
            <guid isPermaLink="false">https://medium.com/p/a76f61b609ee</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[zowe-community]]></category>
            <category><![CDATA[zowe]]></category>
            <category><![CDATA[zowe-general]]></category>
            <dc:creator><![CDATA[Rose Sakach]]></dc:creator>
            <pubDate>Fri, 24 Sep 2021 18:23:22 GMT</pubDate>
            <atom:updated>2021-11-16T10:52:59.152Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S2xj_8djnmlOKLhY" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/237/0*9ciAKyIVaQWvEm8w" /></figure><p>{<a href="https://github.com/zowe/community/blob/master/blogging/blog_guidelines.md#zowe-ecosystem">Ecosystem</a>} At their <a href="https://events.linuxfoundation.org/open-mainframe-summit/">Open Mainframe Summit 2021 Virtual Event</a>, the Linux Foundation’s <a href="https://openmainframeproject.org/">Open Mainframe Project</a> announced a new Zowe Conformance program called <a href="https://www.openmainframeproject.org/projects/zowe/conformant-support-provider">The Zowe Conformant Support Provider Program</a> and congratulated both Broadcom and IBM as the first two Providers accepted into the program by the Linux Foundation.</p><p>For those familiar with the first <strong>Zowe Conformance Program</strong>, it is aimed at certifying certain software characteristics of the products and solutions that extend Zowe. Conformant extenders earn their Zowe Conformance badge by satisfying a specific set of conformance requirements associated with the Zowe component being extended. For example the Endevor plug-in for Zowe CLI has earned a CLI — Zowe V1 conformance badge. And while Zowe Conformant extensions offer consumers assurances associated with baseline functionality, component interoperability and consistency in user experience across Zowe core components for every release introduced within a Long Term Support (LTS) version i.e. V1 Conformance = V1 LTS, this Support Provider program offers Support Providers the ability to showcase their Zowe Support competencies.</p><p><strong>Why the Support Provider Program Matters</strong><br>What makes Zowe unique, successful and fundamental for the longevity of the z/OS platform is the fact that it is open, familiar, and extensible. It is the combination of these characteristics that enables a z/OS interactive experience that is similar to other platforms that embrace Open. Simply put, in addition to making it look and feel like “just another server”, the technical transformation of mainframe management and development to be more like Cloud, makes learning about it, accessing it from other platforms, and developing applications for it more intuitive to the majority of IT Administrators and Developers. While at the same time, it is the very open-nature — specifically the sole reliance on the Community to resolve any issue at any time of day or night — that <strong>may inhibit enterprises from fully adopting Zowe</strong>. That’s where Support comes in and why it matters. Whereby LTS represents stability in the maturity of the technology, Support Offerings can take an open source LTS release to the next level by introducing risk mitigation that essentially translates to stability in problem resolution. They make the technology Enterprise-Grade by addressing the challenge of “who do I call when I have an issue” head-on. Some offerings go even further and include guidance-type services for implementation planning, technology workshops for initial onboarding and ongoing touch-points.</p><p><strong>How Will You Know Who Can Support Zowe?</strong><br>Similar to how the first Zowe Conformance Program assures Zowe consumers that conformant extensions have the Zowe stamp of approval on them for interoperability within an LTS release, the Zowe Conformant Support Provider program offers a virtual safeguard that a given Support Provider has been Zowe-TSC (Technical Steering Committee) -vetted for their ability to both support Zowe components and contribute the code back to Zowe in an appropriate and timely manner. Essentially, it does the homework of verifying a given Support Provider has cleared the qualifications bar. What is included in the qualifications? In general, Support Providers certify they have the hardware, software and personnel needed to diagnose issues, code &amp; test solutions, and provide both standard and emergency fixes for the specific Zowe core component(s) they indicate as being supported. More specifically, a conformant Support Provider will support any authentic distribution of Zowe regardless of where it was obtained — meaning — they will not require a Zowe consumer to download their specific Zowe distribution. Conformant Providers also abide by the applicable Zowe source code licensing, agree to report security vulnerabilities to the Security team, and understand and follow all of the code contribution rules established by the Zowe TSC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/0*UvQW-gjUMtQr8ePs" /></figure><p><strong>Who’s Eligible for the Program?</strong><br><strong>Any provider can participate</strong> in the program and all are encouraged to apply. The applicant will disclose the set of Zowe components for which they’re seeking a conformance badge, which may or may not be the same set of Zowe components for which they offer support. A Support Provider may seek Comprehensive Zowe Support — meaning they satisfy the criteria for all Core Zowe components — but they don’t have to — there is also an option to offer <strong>partial Zowe support</strong>. In this case the Provider would indicate a specific component like Zowe CLI or Zowe App Framework and be awarded a conformance badge for that component. For consumers interested in Comprehensive Support Providers, look for the Comprehensive badge. These providers will also be displayed as Support Provider Conformant for each of the individual Zowe components as well.</p><p>Just like Zowe, the Zowe Conformant Support Provider program will continue to evolve and is actively developed by the Zowe Community. To ensure neutrality, the program is administered by the Linux Foundation and Open Mainframe Project staff.</p><p><strong>A Showcase for Zowe Support for Providers </strong><br>The Zowe Support Provider conformance program serves as a Zowe-vetted directory of available providers for your consideration. Every Conformant Support Provider will be showcased both on the <a href="https://www.openmainframeproject.org/projects/zowe/conformant-support-provider">conformance page</a> itself as well as at the <a href="https://landscape.openmainframeproject.org/card-mode?category=zowe-conformant&amp;grouping=category">Open Mainframe Project Interactive Landscape</a>, where the Zowe- conformant extenders for technology are also displayed. To-date, you will find two providers listed as “Support Provider Comprehensive ZOWE V1”. They include <strong>Broadcom Brightside </strong>and <strong>IBM Z Distribution for Zowe</strong>. We expect this list to grow as more providers become familiar with the program and the application process. Consumers interested in locating a conformant Support Provider that suits their needs can quickly and easily navigate to the directory from <a href="https://www.zowe.org/">zowe.org</a>.</p><p>In summary: Got Zowe? Need support? Don’t stress. Embark on your journey of mainframe modernization powered by open source with the confidence of a trusted, Zowe-vetted support partner.</p><p>Find more Zowe blogs <a href="https://medium.com/zowe">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a76f61b609ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zowe/got-zowe-let-the-zowe-conformant-support-provider-program-be-your-guide-for-support-a76f61b609ee">Got Zowe? Let the Zowe Conformant Support Provider Program be your guide for support!</a> was originally published in <a href="https://medium.com/zowe">Zowe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open and Trustworthy — Three Telltale Signs Zowe is Enterprise-Ready]]></title>
            <link>https://medium.com/modern-mainframe/open-and-trustworthy-three-telltale-signs-zowe-is-enterprise-ready-578838f455e2?source=rss-581fc0caf500------2</link>
            <guid isPermaLink="false">https://medium.com/p/578838f455e2</guid>
            <category><![CDATA[zowe]]></category>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[vscode]]></category>
            <dc:creator><![CDATA[Rose Sakach]]></dc:creator>
            <pubDate>Fri, 30 Oct 2020 20:05:55 GMT</pubDate>
            <atom:updated>2020-12-11T18:17:58.419Z</atom:updated>
            <content:encoded><![CDATA[<h3>Open and Trustworthy — Three Telltale Signs Zowe is Enterprise-Ready</h3><p><strong>“Open Source” and “trust” are no longer mutually exclusive</strong></p><p>By now, you’ve heard of the Open Mainframe Project called Zowe™ — perhaps your organization has even had a chance to give it a test run, particularly now that you can <a href="https://validate.broadcom.com/key/Broadcom-ZoweDistribution">download</a> it from a <a href="https://medium.com/modern-mainframe/zowe-download-challenge-solved-e92855d6af6e">trusted source</a>. With more than 11,000 downloads, it seems the novelty and curiosity associated with the technology are more than hype and in some sense are contagious. Truth be told, we imagine what begins as excitement is quickly followed by a concern with a thought process that goes something like this: “<em>Wow! An Open Source project for z/OS! — But wait a minute, who supports it? And why would I bet my business on an Open Source project in the first place?!?!</em>”. Important questions, indeed. If they’ve crossed your mind and you’re ready for answers, read on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*BVxneEXXz4vY_CVJ" /></figure><p><strong>“Open” Offers the Power of the Community</strong><br>As an open source project, Zowe not only has the benefit of garnering the collective intelligence of all contributors and all of their customers, it also fosters and expands this brain power by leveraging the entire community. This is how Open Source communities work. This is how Open Source communities drive unsurpassed value into the projects they support. Evident in the approximately 5 million lines of code in more than 12,000 contributions in the form of project commits, participation in the Zowe Project has grown steadily since the Open Mainframe Project announced its creation in August 2018. And this trend has bled into mainframe ISVs anxious to extend Zowe by building Zowe-conformant plug-ins along with mainframe users anxious to give them a try. Over 35 product extensions have passed the accreditation of the <a href="https://www.openmainframeproject.org/projects/zowe/conformance">Zowe Conformance Program</a>, while the Zowe Explorer for Visual Studio Code has been downloaded over 20,000 times! Not certain these statistics indicate a willingness of Mainframe clients to consider using Zowe? Consider this one: 99% of the Fortune 500 companies — known to leverage mainframe — already use some form of Open Source!</p><p><strong>LTS Offers Stability Mainframer’s Expect</strong><br>Zowe introduced its first Long Term Support (LTS) release in March of 2020. This release designation is important and impactful. Why? Because it addresses critical Mainframe client expectations and frankly, any consumer of Open Source, with respect to software traits like a comprehensive and compliant approach to security, maintaining stability, ensuring interoperability, and providing advanced warning on both feature deprecation and community-level support termination timelines. The LTS designation is hugely significant particularly, with Open Source. It means Zowe has matured to an “Enterprise-ready”, supportable state.</p><p><strong>Uniquely Positioned to Offer Comprehensive Support</strong><br>Finally, as vendors increasingly make Zowe foundational to their product and solution offerings, they become more capable of supporting the use cases that Zowe facilitates. Broadcom’s focus on enabling the use of Open Source in Mainframe DevOps, Mainframe Modernization, and across its broader portfolio of products demonstrates a large commitment to Zowe. Combine this with Broadcom’s initial contribution of two of the three core Zowe components, their high percentage of Zowe community leaders, representation on each of the Zowe component Squads, and a continuous stream of repository commits from employees, a natural conclusion is that Broadcom is in a unique position to support Zowe. But how does this help bring confidence to your decision to adopt? We understand delving into the open-first approach for your Enterprise, regardless of the advantages, requires some reassurance that it will work as intended, all the time. And on those rare occasions when it does not, you need the reassurance that it can be supported — any time — any day — not just when the larger community can find the time to tend to your issue. To that end, Broadcom has built a commercial support offering around Zowe which provides exactly that. We call this support offering <a href="https://www.broadcom.com/products/mainframe/application-development/brightside">CA Brightside</a>, and it is based on the aforementioned Zowe LTS release.</p><p>In addition to providing enterprise-grade, 24 x 7 support for the Zowe LTS release, CA Brightside offers streamlined, tested software distributions, IP legal assurance, and support for all of the extensions included in the Code4z mainframe developer code pack available at the <a href="https://marketplace.visualstudio.com/vscode">Visual Studio Code marketplace</a>. CA Brightside customers will have access to and support for innovations like API monitoring and API auditing capabilities developed exclusively by Broadcom. It is also important to note that all Zowe Conformant Broadcom product plug-ins include comprehensive support as part of their “parent” product license. No additional license is required.</p><p>There’s never been a better time to offer your staff freedom of choice with an open-first approach in solving your mainframe modernization challenges. With CA Brightside, leverage the power of the open community with confidence. Tap into innovations with vigor! And call us any day, anytime you need assistance. We’ve got you covered. Go ahead — bet your business on it!</p><p><strong>For more information on Zowe</strong>, visit <a href="https://www.zowe.org/">https://www.zowe.org</a></p><p><strong>Learn about it! </strong>Read a blog<strong>:</strong> visit <a href="https://medium.com/zowe">https://medium.com/zowe</a></p><p><strong>Talk about it</strong>! Join our Slack Channel, visit: <a href="https://slack.openmainframeproject.org/">OMP Zowe Slack Channel</a></p><p>Questions? Comments? <em>Send me an email</em>: Rose.Sakach@broadcom.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=578838f455e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/modern-mainframe/open-and-trustworthy-three-telltale-signs-zowe-is-enterprise-ready-578838f455e2">Open and Trustworthy — Three Telltale Signs Zowe is Enterprise-Ready</a> was originally published in <a href="https://medium.com/modern-mainframe">Modern Mainframe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zowe Download Challenge Solved]]></title>
            <link>https://medium.com/modern-mainframe/zowe-download-challenge-solved-e92855d6af6e?source=rss-581fc0caf500------2</link>
            <guid isPermaLink="false">https://medium.com/p/e92855d6af6e</guid>
            <category><![CDATA[zowe]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[broadcom]]></category>
            <category><![CDATA[mainframe]]></category>
            <dc:creator><![CDATA[Rose Sakach]]></dc:creator>
            <pubDate>Thu, 10 Sep 2020 20:23:43 GMT</pubDate>
            <atom:updated>2020-10-21T17:28:19.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/219/0*ndzhhIMV3c9vByY_" /></figure><p><strong>Obtaining authorization to download Zowe™ for your Enterprise just got easier</strong></p><p>When The Open Mainframe Project (OMP) introduced Zowe to the Mainframe world, the contributors not only introduced Open Source and the power of the open source community to Mainframers — the resulting service-oriented software framework dramatically changed the available tooling landscape for both DevOps and Modernization efforts associated with the mainframe. The collective Zowe components (z/OS Services, Application Framework, API Mediation Layer, and Command Line Interface) enable off-platform access to mainframe services. The CLI (Command Line Interface) component, which installs on the desktop, enables a platform interaction style often used by cloud developers. The look-and-feel is very familiar to many experts within organizations. In fact, when Enterprise Architects, Release Engineers, and Next-gen Developers are introduced to Zowe they’re eager to try it out only to be disappointed to learn that one obstacle still prevents them from beginning their journey with Zowe — until now.</p><p><strong>Mainframe Organizations have Software Restrictions</strong></p><p>Though all of the Zowe components are available for download at <a href="https://www.zowe.org/download">https://www.zowe.org/download</a>, many organizations have enabled policies that impose website restrictions, preventing Systems Administrators from accessing the software. We have heard from several customers interested in trying Zowe who have no means in which to obtain it. So despite the free availability of Zowe, downloading software from an Open Source website is simply not permitted and therefore poses a challenge to DevOps teams technically capable of experimenting and exploiting the components for viability.</p><p><strong>Open Source and More from a Trusted Vendor</strong></p><p>At Broadcom, we recognized this challenge and as a result, implemented an alternative. We have introduced a Broadcom site dedicated to providing the latest Zowe Release software distribution. The site enables enterprise customers the ability to quickly obtain all of the Zowe components from a company-authorized, trusted website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gJN3XVafTyiq7eSRaRTDjQ.png" /></figure><p>Navigate to the <a href="https://validate.broadcom.com/key/ZoweDistributionLink">Zowe Free Distribution site</a> to download the Zowe components, which include:</p><ul><li>The current release of the Zowe documentation in PDF format</li><li>The current release of all core Zowe components</li><li>The current release of all Zowe Conformant Broadcom product plug-ins</li></ul><p>In addition, we realized we could augment the download experience by offering a quick-access Q&amp;A forum and we could easily and more visibly share installation and getting-started pointers obtained from a wide range of resources. They include: our Customers, Mainframe Engineers, Technical Experts, User Experience Designers and the Open Source Community. This inspired us to expand our deliverable. So, in addition to offering downloads for all Zowe components, the Broadcom <a href="https://validate.broadcom.com/key/ZoweDistributionLink">Zowe Free Distribution site</a> also provides:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7GphbHQcYKlmkkHT7YAUUg.png" /><figcaption>Broadcom Zowe Distribution Landing Page</figcaption></figure><ol><li>Local packages (.TGZ files) for every published Zowe CLI Broadcom Product Plug-in</li><li>A quick-start, 5-step process describing the minimal install for trying Zowe CLI with any of the Broadcom product plug-ins</li><li>A one-click “Ask Broadcom” capability where registrants can both post and review threads related to Zowe installation experiences and challenges</li></ol><p><strong>Not a Broadcom Customer? No problem.</strong></p><p>The Broadcom Zowe download site is not limited to Broadcom customers. Any Mainframe organization wishing to obtain Zowe software downloads can visit the <a href="https://validate.broadcom.com/key/Broadcom-ZoweDistribution">Zowe Free Distribution site</a>. Simply follow the registration instructions. It is important to note that software obtained from the site does not include any formal support for the Zowe components. However, if you would like formal support, Broadcom has a comprehensive, 24 x 7 Enterprise Grade Support offering for all Zowe components. The offering is called <a href="https://www.broadcom.com/products/mainframe/application-development/brightside">CA Brightside</a>. In addition to providing support for Zowe, CA Brightside also provides IP legal assurance, early access to innovations and support for all of the extensions included in the Code4z mainframe developer code pack available at the <a href="https://marketplace.visualstudio.com/items?itemName=broadcomMFD.code4z-extension-pack">Visual Studio Code marketplace</a>. It is also important to note that all Zowe Conformant Broadcom product plug-ins include comprehensive support as part of their “parent” product license. No additional license is required.</p><p><strong>Zowe Support and More</strong></p><p>In addition to offering Zowe Conformant CLI plug-ins for a growing list of mainframe products, Broadcom continues to invest in innovative plug-ins and offerings that complement the Zowe foundational components. These Broadcom add-ons for Zowe are available exclusively to CA Brightside customers. For more details, product and contact information please visit the <a href="https://www.broadcom.com/products/mainframe/application-development/brightside">CA Brightside</a> web page. In the meantime, now that you can download Zowe, go ahead and give it a try!</p><p><strong>For more information on Zowe</strong>, visit <a href="https://www.zowe.org/">https://www.zowe.org</a></p><p><strong>Learn about it! </strong>Read a blog<strong>:</strong> visit <a href="https://medium.com/zowe">https://medium.com/zowe</a></p><p><strong>Talk about it</strong>! Join our Slack Channel, visit: <a href="https://slack.openmainframeproject.org/">OMP Zowe Slack Channel</a></p><p>Questions? Comments? Send me an email at <a href="/service/mailto:Rose.Sakach@broadcom.com">Rose.Sakach@broadcom.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e92855d6af6e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/modern-mainframe/zowe-download-challenge-solved-e92855d6af6e">Zowe Download Challenge Solved</a> was originally published in <a href="https://medium.com/modern-mainframe">Modern Mainframe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IBM Db2, DBAs and Zowe CLI]]></title>
            <link>https://medium.com/zowe/ibm-db2-dbas-and-zowe-cli-d1e4e8eaaa57?source=rss-581fc0caf500------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1e4e8eaaa57</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cobol]]></category>
            <category><![CDATA[zowe-general]]></category>
            <category><![CDATA[zowe-cli]]></category>
            <category><![CDATA[db2]]></category>
            <dc:creator><![CDATA[Rose Sakach]]></dc:creator>
            <pubDate>Thu, 04 Jun 2020 19:01:01 GMT</pubDate>
            <atom:updated>2020-06-04T19:01:01.076Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*i6w9ssYM-BaYO6bX" /></figure><p><em>A DBA Overview of Zowe CLI and the IBM Db2 Database Plugin for Zowe CLI</em></p><p><strong>{</strong><a href="https://github.com/zowe/community/blob/master/blogging/blog_guidelines.md#zowe-ecosystem"><strong>Ecosystem</strong></a><strong>}</strong> In 2018, when The Linux Foundation’s <a href="https://www.openmainframeproject.org/">Open Mainframe Project</a> (OMP) introduced <a href="https://www.openmainframeproject.org/projects/zowe">Zowe</a> to the Mainframe world, the contributors not only introduced Open Source and the power of the open source community to mainframers — the resulting service-oriented software framework dramatically changed the available “tooling” landscape for both DevOps and Modernization efforts associated with Mainframe. The collective Zowe components (z/OS Services, Application Framework, API Mediation Layer, and Command Line Interface) enable off-platform access to mainframe services. The CLI (Command Line Interface) component, which installs on the desktop, enables a platform interaction style often used by Cloud Developers. The look-and-feel is very familiar to Enterprise Architects and Next-Gen Developers — both capable and comfortable working in Command Line.</p><h3>CLI enables the use of desktop tools</h3><p>The CLI makes programmatic interaction with APIs and other services much easier, straightforward and very familiar to modern developers. Instead of having to write code against APIs, a developer can use logical CLI commands that can be initiated from their own desktop. Since a developer’s desktop can include a multitude of open source technologies, having “local” mainframe access gives them the ability to leverage them while performing their mainframe work. For example, Mainframe teams can use continuous integration — continuous delivery (CI-CD) pipeline orchestration tools like Jenkins and Bamboo, task runners like Gulp and Gradle, or testing frameworks like Mocha and Jest. They do this by adding Zowe CLI commands into the scripts they’ve written to invoke these tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/248/1*efB59MMZ8kCDTf9mucqDlA.png" /></figure><p>As developers realize they have a need to — and are able to — chain together various repeatable processes they will naturally prefer to create their own pipelines. These pipelines can be simple (compile-link after code save or code check-in) or more complex (compile-link-deploy, execute and validate tests, promote to the next stage etc.). They can be limited to a single developer for personal use, they can be used by a development team, or they can be leveraged by DevOps Engineers responsible for creating and maintaining enterprise CI-CD pipelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*Tv4Iag-KIKzHeq94MZRySA.png" /><figcaption>Simple CI-CD pipeline</figcaption></figure><h3>Where Db2 fits in</h3><p>Many mainframe business applications rely on data stored in Db2 databases. The developers responsible for maintaining these applications now have the ability to create pipelines that include creating masked Db2 test data, compiling Db2 programs and testing Db2 programs and Db2 stored procedures. As a DBA responsible for building, maintaining, and managing the Db2 databases associated with these applications, it’s important to understand where developers and DevOps Engineers may want to take their application pipelines and what types of actions can be performed using the Zowe CLI plug-in for Db2.</p><p>At the present time, the plug-in offers 3 basic actions: CALL, EXECUTE, and EXPORT. These actions are a result of the use cases most requested by customers and can be invoked using the CLI interactively (i.e. command prompt) or executing them within a script. They include:</p><ol><li>Call a Db2 stored procedure</li><li>Execute a Db2 SQL query</li><li>Export a Db2 table</li></ol><p>For the first use case, developers wanted the ability to create test automation for an application that included a Db2 stored procedure initiated from a COBOL program. Specifically, they wanted to be able to execute the stored procedure as part of an automated test included in their CI-CD pipeline. The <strong>zowe db2 call</strong> command gave them the ability to achieve this goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/229/1*Ir2uTRwSbI_bW_Tk3Wie0w.png" /></figure><p>For the next use case, we needed to augment an existing, regularly scheduled automated testing scenario that executed a series of test suites. The goal was to capture the results of the test suites as a step in the CI-CD pipeline. For this we added the <strong>zowe db2 execute</strong> command to the existing script to invoke several SQL statements. The first issues an <strong>insert sql</strong> statement that writes the test output from each of the suites to a specified Db2 table. Then, once all output is collected, the pipeline includes another <strong>zowe db2 execute</strong> command with a <strong>select sql </strong>statement to obtain the entries that were just added to the table for viewing or programmatic comparison.</p><p>We also leverage the <strong>zowe db2 execute</strong> command by adding it to a pipeline that verifies Db2 table updates were successful after executing a CICS transaction.</p><p>The third use case satisfied the request to export the contents of a Db2 table to enable a simple data comparison after a code change.</p><h3>How DBAs can help</h3><p>Each of the use cases required specific Db2 interactions to be included as part of an automated script. They are simple use cases meant to describe the possibilities and are by no means, meant to comprehensively cover all use cases associated with interacting with mainframe Db2 applications. The current list of actions included in the IBM Db2 Database Plugin for Zowe CLI represent the beginning of a series of actions that allow Db2 applications to participate in maturing Enterprise DevOps processes. To that end, we welcome the voice of all of the mainframe Db2 DBAs in the Zowe Community to help us to understand their perspective on where application teams struggle specifically with moving mainframe Db2 application changes through the development process and into production. We are anxious for you to share your expertise, to help set direction and ideally help lead the efforts to grow the list of actions available in the plug-in. If this has piqued your curiosity, please consider reaching out directly to share your perspective or better yet, consider taking the next step and join our team!</p><p><strong>If you enjoyed this blog checkout more Zowe blogs </strong><a href="https://medium.com/zowe"><strong>here</strong></a></p><p><strong>Ask a question and join the conversation on the </strong><a href="https://slack.openmainframeproject.org/"><strong>Open Mainframe Project Slack</strong></a><strong> </strong>Channel #Zowe-dev, #Zowe-user or #Zowe-onboarding<strong>.</strong></p><p><strong>Get started with Zowe CLI with this 5 minute read: </strong><a href="https://medium.com/zowe/getting-started-with-zowe-cli-7a29420c6be7"><strong>https://medium.com/zowe/getting-started-with-zowe-cli-7a29420c6be7</strong></a></p><p><strong>For more information on Zowe</strong>, visit <a href="https://www.zowe.org/">https://www.zowe.org</a></p><p><strong>For more information on the Db2 plug-in</strong> visit: <a href="https://docs.zowe.org/stable/user-guide/cli-db2plugin.html">IBM Db2 Database Plug-in for Zowe CLI Documentation</a></p><p><strong>Try it</strong>! Get a sample script: visit <a href="https://github.com/zowe/zowe-cli-sample-scripts/tree/master/use_cases/sonarqube_datasets">Zowe CLI samples repository</a></p><p>Questions? Comments? Got a suggestion for the next use case? Send me an email at <a href="/service/mailto:Rose.Sakach@broadcom.com">Rose.Sakach@broadcom.com</a></p><p>Click the links to learn more about <a href="https://www.openmainframeproject.org/projects/zowe">Zowe</a> and more <a href="https://medium.com/zowe">Zowe blogs</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1e4e8eaaa57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zowe/ibm-db2-dbas-and-zowe-cli-d1e4e8eaaa57">IBM Db2, DBAs and Zowe CLI</a> was originally published in <a href="https://medium.com/zowe">Zowe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A first step for merging Mainframe into Enterprise DevOps with CA Endevor® and Zowe CLI]]></title>
            <link>https://medium.com/zowe/a-first-step-for-merging-mainframe-into-enterprise-devops-with-ca-endevor-and-zowe-cli-582781a6bb9?source=rss-581fc0caf500------2</link>
            <guid isPermaLink="false">https://medium.com/p/582781a6bb9</guid>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[endevor]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[zowe-cli]]></category>
            <dc:creator><![CDATA[Rose Sakach]]></dc:creator>
            <pubDate>Mon, 09 Dec 2019 21:45:28 GMT</pubDate>
            <atom:updated>2025-12-08T15:11:12.273Z</atom:updated>
            <content:encoded><![CDATA[<h3>A first step for merging Mainframe into Enterprise DevOps with Endevor® and Zowe CLI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*UgWwWtTeRto-S13sEdtwmQ.png" /></figure><h4>Learn how to implement code quality scanning with SonarQube to unify DevOps</h4><p><strong>{</strong><a href="https://github.com/zowe/community/blob/master/blogging/blog_guidelines.md#zowe-ecosystem"><strong>Ecosystem</strong></a><strong>}</strong> Like many companies that continue to leverage the processing power of mainframes as an integral part of the business, there is likely a finely-tuned mainframe development-to-deployment process in play at your shop which leverages Endevor as the backbone. An acronym for DevOps [ENvironment for DEVelopment and OpeRations] with groundbreaking parameterized scripting for continuous integration and deploy for mainframe-centric applications, Endevor continues to manage, secure, and deploy millions of mainframe software assets while providing a development environment, intelligence for impact analysis and proof of compliance for audit. Purpose-built for flexibility, it supports waterfall and current agile development practices using traditional mainframe interfaces or, with the introduction of the Endevor Bridge for Git, an endless number of modern IDEs.</p><h4><em>Mainframe is left out of the conversation.</em></h4><p>While this proven engine continues to drive the release process for business-critical application mainframe components, there is probably an active or an “in-the-works” Enterprise DevOps initiative gaining quite a bit of visibility within your organization, rightfully challenging, with plans for standardizing on, all aspects of software development and delivery. What’s confusing is that Mainframe tends to be left out of the conversations. Why? Most Enterprise Architects talk about tools traditionally associated with Distributed, Mobile, and Cloud platforms. Jenkins/Bamboo (CI-CD automation server), Python / JavaScript (scripting), Gradle/ Gulp (task runner), Gradle (build tool), Mocha (testing framework), SonarQube (code quality and security inspection) even Git (with associated hosting services GitHub, GitLab) are all on this list. Traditionally, most are not compatible with mainframe — that is, until the Open Mainframe Project (OMP) introduced Zowe. Specifically, the Zowe CLI (Command Line Interface) component changes the game. With client-side access and scripting capabilities, it allows mainframe to join in on the conversation in a comfortable fashion. How so?</p><h4><em>Our customers are introducing Zowe!</em></h4><p>Here’s what our customers are doing and you can do as well. Simple. DevOps architects realize incorporating the mainframe doesn’t require them to learn mainframe. Instead, they are using the Endevor Plug-in for Zowe CLI to fold existing Endevor processes into their Enterprise initiative. Let’s take the example of including code quality tools as part of the mainframe automated pipeline. SonarQube is a very popular solution in this space. Incorporating code scanning — for code quality and security vulnerabilities — in with their existing Endevor pipeline was THE use case that sold a mature DevOps team at a large healthcare company on the automation capabilities of Zowe CLI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*hIfcGyQ6TUZBzcSNqBWa1g.png" /><figcaption>Sample CA Endevor Zowe CLI Bulk RETRIEVE command</figcaption></figure><p>Step 1. Execute Zowe CLI script to securely access code stored in Endevor</p><ul><li>Obtain code from the Endevor inventory location to the desired platform or Jenkins server (use the NEW! single command, bulk retrieve — shown above — to fetch the latest application code with dependencies or just the changed code)</li></ul><p>Step 2. Execute the SonarQube scanner on the fetched code</p><ul><li>run scans</li><li>update the SonarQube dashboard and metrics</li><li>log activities (Jenkins)</li></ul><p>This automation using Zowe CLI extends standardized code quality and security practices to the mainframe. This is just one example using non-z/OS hosted tools. The options are endless. But don’t take my word for it. Speak with some Zowe early adopters, other contributing vendors, or our colleagues.</p><h4><em>Zowe CLI extends the value of existing investments to incorporate DevOps initiatives</em></h4><p>What if you have other SCM tools? Zowe CLI can still help, albeit with more work and some creativity on your end. Check out Jason Tucker’s Blog, “<a href="https://medium.com/zowe/how-to-write-cleaner-and-safer-z-os-code-with-zowe-cli-and-sonarqube-6afb283348f9">How to Write Cleaner and Safer z/OS Code with Zowe CLI and SonarQube</a>” to get started. Jason walks you through the “how-to” with all the technical details. It may inspire you to create your own Zowe CLI Plug-in for your current mainframe CI-CD process, similar to what we’ve done. Meanwhile, we are continuing to build on our inventory of actions with Zowe CLI. With the Endevor Zowe CLI Plug-in, DevOps Architects can:</p><ul><li>Create automation scripts that interact with existing build, deploy, packaging and authorization functions to synchronize mainframe delivery with all platforms</li><li>Incorporate these scripts into Enterprise DevOps processes, including Jenkins pipelines and deployment orchestrators</li><li>Leverage other code scanning tools for quality and security of mainframe code</li><li>Experiment with open source testing frameworks to cover comprehensive mobile-to-mainframe test requirements at pre-determined checkpoints throughout the pipeline</li><li>And more…</li></ul><p>We plan to continue to share our experiences, so that you can learn how to leverage the Endevor Zowe CLI Plug-in as you mature your enterprise DevOps processes. We will share popular use cases, like this code quality one, to make it easy for you to understand how to leverage it for your organizations’ requirements.</p><h4>Next steps:</h4><p><strong>Try it</strong>! Get a sample script for this use case and more: visit the <a href="https://github.com/zowe/zowe-cli-sample-scripts/tree/master/use_cases/sonarqube_datasets">Zowe CLI samples repository</a>.<br><strong>Talk about it</strong>! Join in on our conversation, visit: <a href="https://slack.openmainframeproject.org/">OMP Zowe Slack Channel</a>.</p><p>For more information on Zowe, visit <a href="https://www.zowe.org/">https://www.zowe.org</a>.<br>For more information on the CA Endevor Plug-in for Zowe CLI visit: <a href="https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/19-0/integrating/zowe-cli.html">Endevor Zowe CLI Plug-in Documentation</a>.</p><p>Learn more about <a href="https://www.ca.com/us/open-source-mainframe-zowe.html">Zowe at this site</a>; read more <a href="https://medium.com/zowe">Zowe blogs here</a>.</p><p>Questions? Comments? Got a suggestion for the next use case? Send me an email at <a href="/service/mailto:Rose.Sakach@broadcom.com">Rose.Sakach@broadcom.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=582781a6bb9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zowe/a-first-step-for-merging-mainframe-into-enterprise-devops-with-ca-endevor-and-zowe-cli-582781a6bb9">A first step for merging Mainframe into Enterprise DevOps with CA Endevor® and Zowe CLI</a> was originally published in <a href="https://medium.com/zowe">Zowe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>