On Fri, 4 May 2018 13:00:55 +0000, Rob Scott <[email protected]> wrote:
Dave
As someone who is a complete dinosaur and used to source control
systems like SCLM, it took a bit of getting used to for me.
I found that once I abandoned PDS datasets and used z/OS unix
file systems on z/OS to store the source I was working on, all
things began to fall into place.
For build processes that need PDS input/output, OPUTX/OGETX are
your friends.
Rob.
[Disclaimer: I work at Rocket Software, and have interacted
a fair amount with Rob.]
Rob, if you're a dinosaur, the species must be "velociraptor". :-)
I'm in the Open Source Tools group at Rocket; our goal is to make
the z/OS Unix environment as tool-rich and developer-friendly as
other Unix platforms.
We (the Open Source Tools group) store all of our code in git, using
the Rocket z/OS git port on one side and either BitBucket (internal)
or GitHub (external) on the other. The .gitattributes support we
added to git helps ease the EBCDIC/ASCII impedance mismatch. As Rob
knows, there are still some twitchy spots (ISPF panels can present
problems).
I do nearly all of my work in emacs (shell buffers are a wonderful
thing...), with very ocassional visits to TSO/ISPF and batchland (I
*really* want to be able to run SMP from a shell script; I'll get
there eventually...). While I understand the appeal of tools like
IDz, I personally prefer the somewhat looser integration of emacs,
and use a fair number of browser-based tools for collaboration
(Jira, the Confluence wiki, BitBucket/GitHub). I guess that makes
me the Unix equivalent of a dinosaur...
-- Jerry
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
