The SDSF development team have been using git for z/OS for the last 5 years or so.
The source code is kept in zFS and our in-house build tool extracts to staging PDSEs for the batch submission using jobgroups. Some of us use SlickEdit rather than ISPF and we can instigate builds from there using custom options on SlickEdit drop-down menu. The builds use SSH from SlickEdit to run simple scripts on z/OS to construct and submit JCL. We use SDSF Rexx to capture build success and failure and can feedback that info to the developer via email or straight into the SlickEdit console. SlickEdit uses FTP as the transport to the zFS source code. We use Bitbucket for remote repo and Jira for project tracking. I tend to only use ISPF for debugging and unit testing these days (something that would raise eyebrows with myself from 10 years ago). The power of git on z/OS is quite something to behold, especially the merge function. Rob Scott Principal Architect, Mainframe Systems Tools Distinguished Engineer Rocket Software 77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA Tel: +1.781.684.2305<tel:+17816842305> Email: [email protected]<mailto:[email protected]> Web: www.rocketsoftware.com<http://www.rocketsoftware.com/> ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Wednesday, January 5, 2022 3:46:53 PM To: [email protected] <[email protected]> Subject: Re: ... Re: Top 8 Reasons for using Python instead of REXX for z/OS EXTERNAL EMAIL On Wed, 5 Jan 2022 10:47:55 +0800, David Crayford wrote: > ... > * An IDE such as VS Code, IntelliJ, Slickedit with plugins for > mainframe languages and to access the MVS file system. > What access vehicle? NFS? Other? I've found NFS very satisfactory. > * They don't use TSO or the ISPF editor so there is no need for REXX > edit macros etc. ISPF is mainly used for SDSF and submitting jobs. > ISPF shouldn't be necessary to submit jobs. The alternatives are better, at at least in eliminating the antediluvian 80-column restriction. (Why does ISPF still impose that?) I've used FTP, ad-hoc INTRDR, ":w ! submit", ... . It ought to be a simple Slickedit macro. No such easy interface from SDSF API to Slickedit via macro, though I suspect your tribe yearns for one. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ================================ Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
