Q1 Why use staging PDSEsand not build directly from zFS. A1 Because at the time that we set this up, we had certain parts that used "compilers" that did not play well in z/OS Unix. I believe that other teams at Rocket have solved these issues now, but what we have works well and can be understood by all members of the team.
Q2 Why not NFS? A1 The SlickEdit FTP transport is easy to configure, seemless and works straight out of the box. I believe NFS would require sysprog configuration and effort. Next time I get to chat to my sysprog mates , I can see if there is any benefit for us and them in using NFS, but what we have works well. Q3 Can you get back joblogs and sysprint? A3 Yes. The current Rexx we use does the following, but could easily be enhanced : 1. SDSF Rexx runs as last job in the build jobgroup. 2. Extracts the jobgroup ID that it belongs to 3. Extracts the jobIDs for every previous job in the same jobgroup 4. Processes the "JS" jobstep info for each job and sends the developer an email with all jobstep summaries for all jobstep. 5. Failing build steps can send output (eg SYSTERM) directly back to SlickEdit console. 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 7:40:19 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 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><http://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 [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
