> I periodically copy over the current libraries and push the changes to GitHub.
Do you mean push to GitHub and then 'build/deploy/copy over the current (PARMLIB) libraries using some build workflow? > It’s not perfect, but I can get some idea of when a change was made or find > an older version of a member that isn’t working right. Why is it not perfect, what would you want to work better? - KB ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, August 5th, 2021 at 10:06 PM, Pew, Curtis G <curtis....@austin.utexas.edu> wrote: > On Aug 5, 2021, at 11:30 AM, Edgington, Jerry > jerry.edging...@westernsouthernlife.com wrote: > > > Git client on z/OS could be used to "build" PARMLIB. It would just depend > > upon how PARMLIB is allocated, cataloged and used. For example, if PARMLIB > > was cataloged used indirect cataloging, and created on something like the > > RESvolume, then Git could be used as the source input to create PARMLIB on > > the next RESvolume. > > I have a git repository that contains copies of important z/OS configuration > libraries like PARMLIB. I periodically copy over the current libraries and > push the changes to GitHub. It’s not perfect, but I can get some idea of when > a change was made or find an older version of a member that isn’t working > right. > > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Pew, Curtis G > > curtis....@austin.utexas.edu > > > --------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
