InterConnect 2017 : Git for COBOL and PL/I?—Yes, It Can Make Sense
2 likes450 views
The document discusses the integration of Git with COBOL and PL/I for z/OS systems, presenting Git as an open-source source code management tool designed for distributed development. It outlines user workflows using ISPF and IDz for managing files and processes with Git on z/OS, as well as highlighting the benefits and configurations needed for effective implementation. Additionally, it includes important disclaimers regarding the information's accuracy, future product plans, and legal implications related to IBM's services.
InterConnect 2017 : Git for COBOL and PL/I?—Yes, It Can Make Sense
- 1. InterConnect 2017 Git for COBOL and PL/I - Yes it can make sense Rosalind Radcliffe Distinguished Engineer, Chief Architect for DevOps for Enterprise Systems rradclif@us.ibm.com @RosalindRad 1 3/20/2017
- 2. 2 3/20/2017 Please note IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
- 3. 3 3/20/2017 What is Git? • Open Source source code management capability built to manage Linux development • Distributed Source Code Management • Full copy of the repository locally for each user their own private copy on their own machine • Uses a commit ID instead of a version • SHA-1 hash based on the code, what came before it, who made the commit, when they made it, and other metadata • Forking the repository is normal 3 Shared Repo P 1 P 2 P 3 Shared Repo Shared Repo Shared Repo P 3 P 1 P 2
- 4. 4 3/20/2017 More on Git • More info https://en.wikipedia.org/wiki/Git • Git is available via https://git-scm.com • Git for z/OS is provided by Rocket Software • http://www.rocketsoftware.com/zos-open-source/tools • Part of ported tools • Provides the ability to run Git on z/OS • Writes files to zFS • Supports tagging files for EBDCIC, ASCII, UTF-8 • Adding a tag file to Git repository to indicate which files should be in which code page • Configuration to say what code page should be used for repo
- 5. GIT - With Build 5 GIT Users workstations GIT GIT GIT Central Server GIT GITHUB or other solution GIT Build Systems Distributed servers Jenkins Jenkins slave
- 6. GIT - With Build 6 GIT Users workstations GIT GIT GIT Central Server GIT GITHUB or other solution GIT Build Systems Distributed servers z/OS GIT Jenkins Jenkins slave Jenkins slave z/OS Mac/Linux/Windows GIT What build script ?
- 7. Open Source pipeline 7 Jira Git Eclipse Artifactory, Nexus Sonar – Sonarqube Pipeline Automation - Jenkins No true open source options Jenkins sometimes used IBM Development and Test Environments for z Systems (zD&T) – no open source options for the Ant, Maven, Gradle, Jenkins
- 8. 8 Jenkins • Jenkins Slave already runs on z/OS • Allows running tasks on z/OS • With Rocket Git port can use existing Git plugins to pull code to z/OS for build
- 9. 9 3/20/2017 User Steps using ISPF • Load files using Git pull • Loads files to zFS • Edit the files with standard ISPF editors • Compile out of zFS or copy to PDSE as first build step • Commit back to Git when successful compile or wanting to save state • Push to central Git with successful test
- 10. 10 3/20/2017 User Steps using IDz • Git pull using eclipse git plugin • All IDz local project function available • Push file to z/OS to do JCL build • Commit to Git when wanting to save state • Push to central Git when ready to share with others
- 11. 11 3/20/2017 Resources https://ibm.biz/apis2zdevops - new DevOps from APIs to z Systems Dummies book
- 12. 12 3/20/2017 Notices and disclaimers Copyright © 2017 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM. U.S. Government Users Restricted Rights — use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM. Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. This document is distributed “as is” without any warranty, either express or implied. In no event shall IBM be liable for any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of opportunity. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided. IBM products are manufactured from new parts or new and used parts. In some cases, a product may not be new and may have been previously installed. Regardless, our warranty terms apply.” Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice. Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation. It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law.
- 13. 13 3/20/2017 Notices and disclaimers continued Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM expressly disclaims all warranties, expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular, purpose. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right. IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®, FileNet®, Global Business Services®, Global Technology Services®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli® Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.