On 8/14/23 12:54 AM, Jon Perryman wrote:
You're confusing z/OS with Unix where all programmers are
systems programmers who can do anything they want.
No, I'm not confusing z/OS with Unix.
I'm speaking agnosticly about any OS that will run on the platform;
z/OS, VM, z/TPF, or even Linux.
N.B. I don't consider USS/OMVS to be it's own independent OS. This is
despite it being an integral and important z/OS sub-system.
z/OS is NOT about be welcoming and encouraging. It's about what's best
for the business.
What is better for the business, discouraging people from learning
$THING to the point that there is nobody to support and maintain it or
providing a safe place for newcomers to learn $THING in a controlled
safe location.
I obviously think that a safe place is better. Ideally said safe place
is also accompanied by access to more experienced people to help guide /
tutor newer more junior people to make sure the newcomers do things safely.
Your on a multi-million dollar computer shared by thousands.
If anything the cost of the system implies that it will be more
difficult for newcomers to gain access to the platform to learn. As
such I think it's more important to provide a safe environment for
people to learn.
As a business programmer (not Unix sysprog), you're not qualified
nor authorized to make these decisions.
What gives you the impression that any and all things to be investigated
don't go through the change approval board and don't have managerial
support.
Once upon a time Java, or more recently Node.JS, was considered new and
toy software. Yet today, they are both critical.
It's my understanding that many, but definitely not all, companies have
multiple CECs, one (or more) newer for production, and one (or maybe
more) older for DR.
My experience is that these older DR systems gain some additional value
to the business if they are /also/ used to host sandbox VMs / LPARs.
Programmers leave z/OS for Unix in order to be in full control.
I've never heard that before.
I question the veracity of the idea that everything is about control. I
think there is quite a bit that's about how to safely do tasks on the
mainframe or z/OS in a way that utilizes it's unique capabilities not
found on other platforms.
Why do you think it's difficult to get z/OS programmers.
Quite honestly, I think that the mainframe / z/OS is difficult for
people to get access to in any capacity, and even more difficult for
them to get access to a small safe sandbox environment for them to learn in.
Would you rather have someone that blindly follows directions that have
been written out for 30 years with zero understanding of what problems
any mis-step may cause, or would you rather have someone that has been
coming up through the ranks and has lots of experience with a procedure
and has learned what each step of the procedure is for and who it
impacts the overall process?
I can't think of a single instance that providing a test / sandbox / lab
instance has been a net negative. I can think of many instances where
having a test / sandbox / lab instance to mimic production and test
changes before applying the changes to production has improved
understanding, identified problems in procedures, optimized the process,
or generally helped the overall process in many different ways.
If you believe that proof of concepts are not necessary, then please
explain why a development system is needed as opposed to just making the
changes in production directly.
N.B. Nothing about a what I'm advocating for negates, sidesteps, or
usurps change control or approval process. If anything I advocate for
quite the opposite; work within and exercise the established process so
that you understand it and are familiar with it. I firmly believe that
the only way to identify problems in a process and make the process
better is to use the process. I firmly believe that it's best to do
this work in a non-production environment whenever possible.
Grant. . . .
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
