The zigi package has been generated in TSO XMIT format and sent to Sam for inclusion on the CBTTape and it will be there in the near future. The initial packaging was for those who could run git to clone. There is also the option to download the package in a zip file, which then requires that it be uploaded to z/OS.
The Rocket port of git, bash, etc. needs to be uploaded as well but most of it is in binary. Using OGETX might solve the issue (haven't tried) for the various partitioned dataset files.. Lionel B. Dyck <sdg>< Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Monday, December 9, 2019 12:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Interchange best practice? (was: GIT ... length issue) On Mon, 9 Dec 2019 05:44:08 -0600, Lionel B Dyck wrote: >If you are trying to ftp the rocket git distribution then you should be >ftp'ing it to OMVS and not to z/OS datasets. If you are trying to work >with the zigi (z/OS ISPF Git Interface) then again, ftp to OMVS files >and use the install.sh script to get the files to z/OS for use. > "... to z/OS ..."? Isn't OMVS already just part of z/OS? What technique requires the least error-prone human interaction. I believe the package should be a single file, transferred to z/OS as *binary*. o cksum is your friend. Is a checksum supplied with the package. o CBTTAPE.org has some practices worth assimilating. o The package might be a pax archive, extractable with "pax -r ..." o Or a .zip, extractable with "jar -x ..." Is jar generally available on z/OS systems without optional installation? o PDS[E]s can be TRANSMIT unloaded within the pax/zip. Cf. CBTTAPE.org. RECEIVE has an INDD option which can accept allocated OMVS files. RECEIVE runs only under TSO, and getting to TSO from OMVS is a tedious extra step. o It's a shame that: - RECEIVE can't run outside TSO. JCL EXEC or Rexx ADDRESS LINKMVS would be great. - RECEIVE requires reply to a prompt. - IEBCOPY doesn't support OMVS files as PDSU. SMP/E does an extra conversion step to make that work. - AMATERSE doesn't support OMVS files as archive SYSUT1. I can cheat this, but support would be lacking. - OMVS directories are not supported as STEPLIB catenands. - OMVS directories are not supported as SYSEXEC catenands. o Accommodating site naming standards can be a PITA. o What about the instructions? An ASCII README file outside the archive? o SMP/E? Any suggestions? -- gil ---------------------------------------------------------------------- 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
