Gil, Yes, you can have a git repo with PARMLIB or any other configuration file and each PARMLIB member in the PARMLIB directory. This can be cloned to z/OS, using zOAU to allocate PARMLIB, then use OCOPY to copy the PARMLIB members to the PDS.
There are some items to be aware of. 1. Non-roundtripable characters or characters which don't have a UTF-8/ASCII to EBCDIC translation. 2. Make sure the members are valid LRECL=80, or less than 71, with 72 as the continuation. 3. LOADLIBs will not work in git, but you can store the source for the LOADLIB, then compile and linkedit, with the output to LOADLIB member. Jerry -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Friday, July 31, 2026 1:14 PM To: [email protected] Subject: [EXTERNAL] Re: I want to keep multiple PDS's in sync On Fri, 31 Jul 2026 11:30:17 -0500, Donald H. Blake wrote: >Indeed, and that was my first through. This is unfortunately not for backup >purposes, but rather the dataset is a parmlib dataset consumed by a program >product. There's no way to make the program product consume its parms directly >from git. However, I wonder if Rocket's port of git has an option to sync a >PDS or PDSE ... I'll look into that. > Can a Git repository be mounted as a remote file system, which could then be allocated as PARMLIB? >And it hasn't been lost on me that git brings versioning (as to what has >changed and when) to the table as well, which is definitely nice to have. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
