On 9/07/2020 5:52 pm, Jake Anderson wrote:
Does anyone have experience in using git for zOS(rocket open-source) to
manage parmlib or proclib ?
I have been doing some experimentation with this to track changes.
At the moment I have a script to copy all members from PARMLIB/PROCLIB
and various other configuration datasets and files into a git working
copy. I can commit the changes with a note about what changed etc. then
push to a central repository where I can use other tools to search, look
back at changes etc.
It might be useful to e.g. automatically create a tag after every IPL,
so you can see exactly what changed between IPLs. It seems very useful.
One word of warning: be very careful with current releases of ZIGI.
There are processes where it deletes and reallocates datasets, which
could be embarrassing if they are important e.g. SYS1.PROCLIB. I have
suggested that it should avoid doing that. I did some experimentation
with it, but manual processes are safer at the moment.
If ZIGI was enhanced to handle datasets a bit more safely, I can see
workflows where a systems programmer could check out their own copy of
PARMLIB, make changes, push them to the central repository and have them
merged with other peoples changes into the real SYS1.PARMLIB. You could
then have detailed line by line tracking of changes with descriptions
and links back to change records, see exactly which members had
modifications as part of the same change etc. It would be very nice.
--
Andrew Rowley
Black Hill Software
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
