On Wed, 5 Jan 2022 19:15:57 +0000, Rob Scott wrote: >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. > Why state to PDSE rather than build directly from zFS?
>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. > So my pessimism about a SlickEdit<->SDSF API interface was unwarranted. Does the captured information include job logs and SYSPRINTs? >SlickEdit uses FTP as the transport to the zFS source code. > No NFS to share the 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 >Web: www.rocketsoftware.com<http://www.rocketsoftware.com/> > >________________________________ >From: Paul Gilmartin >Sent: Wednesday, January 5, 2022 3:46:53 PM > ... >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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
