In my experience, there are Luddites in every camp. Some mainframers are 
bleeding edge; others are stuck in the past. Likewise for PC users.

"Be not the first by whom the new are tried, Nor yet the last to lay the old 
aside."


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
Colin Paice [[email protected]]
Sent: Wednesday, January 5, 2022 11:39 AM
To: [email protected]
Subject: Re: ... Re: Top 8 Reasons for using Python instead of REXX for z/OS

David,

Are there any white papers or blog posts giving examples of IBM's use of
git on z/OS, Im sure there would be a lot of interest in this.  Are there
any share or guide presentations?  Far from being luddites, z/OS people
tend to adopt change, as long as the new stuff can meet the same standards
as before.

How do people using Git  build the products.   Before I left IBM our build
system on z/OS had XML files configuration files (which I found very
complex).  40 years ago I was in build and had a simple file with one line
per source file.

I found file tagging a challenge.  The only way I could get a python file
to compile was to copy an existing .py file, and edit it and insert my
content;  or ftp in* binary *a file from linux and use chtag -ct SO8859-1
name.py.  Im sure there must be an easy way, but I could not find it.

Colin

On Wed, 5 Jan 2022 at 15:29, David Crayford <[email protected]> wrote:

> On 5/1/22 8:55 pm, René Jansen wrote:
> > It is undeniable that git - which I love and use every day, is much more
> complicated on z/OS because of EBCDIC, access methods, records and block
> sizes.
>
>
> It's not complicated Rene. There are UNIX commands that make it snack!
> Company policy says we need to use Git. Some projects still use MVS data
> sets so we sync to the file system. You would be surprised what products
> you use every day that are hosted and built from the z/OS UNIX file
> system and managed by Git. File tagging makes EBCDIC a non issue and
> block sizes and records are nothing more than I/O methods of the
> utilities that do the sync. The most compelling Git advocates where I
> work are some of our best mainframe engineers who have witnessed it's
> capabilities such as merging.
>
> ----------------------------------------------------------------------
> 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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to