It will land you in endless discussions with auditors about system integrity issues and you will be pointed to a list of allowed open source software where the thing you want to upload is not on. I cannot speak for every installation of course.
If you manage to install something, it will not be on production, which is managed by systems support staff. In most installations I know, the only way is to introduce something in development and taking care that it is deployed with the application. This is foiled of course the first time there is a fix on it - now you have applications with sometimes conflicting versions of tools, that end up on search paths. This is how everybody ended up with multiple releases of log4j. When you have approval from audit, some systems programmer will ask what you want with it, and will have a ´better´ solution, or tells his management that he will build an application in which you can do something like 12% of what you wanted. That will be OK’d by his management but he will never finish. This is why tools (let’s not name them, but make an exception for the Rexx Stream I/O library as a case in point) do not exist unless they are in IBM’s MVS base deliverable. This is why it is so bad that IBM does not maintain Rexx as it should, does not include Pipelines in TSO, and delivers, with its allied companies, various tools in conflicting versions, and seems to be always behind on JVM releases. If you want to modernise the mainframe, make it run Java 17 last week. How do I know? It is because in this story, I have been the auditor, the sysprog, the manager, the developer, the project manager and the IT manager. Best regards, René. > On 22 Jun 2022, at 16:20, Seymour J Metz <[email protected]> wrote: > > >> >> for most mainframe personnel installing something by themselves >> is a sure way to be fired from the job. > > What happens if you ask for permission to install free downloads? > > ________________________________________ > From: IBM Mainframe Discussion List <[email protected]> on behalf of > René Jansen <[email protected]> > Sent: Wednesday, June 22, 2022 5:52 AM > To: [email protected] > Subject: Re: Some UNIX file usage questions > > Hi David, > > You did that to yourself; by going off into a discussion with Charles about > his use of Rexx and assembler. Your company website says it best: "friendly > for programmers who lack conventional mainframe language skills” > (https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rocketsoftware.com%2Fplatforms%2Fibm-z%2Fpython-for-zos&data=05%7C01%7Csmetz3%40gmu.edu%7C3351d7d6a5cb4746af2308da5434f588%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637914883696343467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8dA%2FHF2lH94rLYfUQX2AeGw2aDNbjB3Tto531%2BMngH8%3D&reserved=0). > > However interesting this modernising is, there is no standard python > installation on our customers’ systems. There is an IBM port and a Rocket > port, they are different and for most mainframe personnel installing > something by themselves is a sure way to be fired from the job. There is an > enormous installed base of older technology and it is not going away. All the > disasters I witness, are caused by young boys and girls that have been let > loose in an environment that they pretend to know, with tools that react > slightly different. All of them are grateful when shown how it is done. > > Best regards, > > René. > >> On 21 Jun 2022, at 15:35, David Crayford <[email protected]> wrote: >> >> I don't want to get into another ping pong debate over REXX. Everyone knows >> my opinion by now. >> > > ---------------------------------------------------------------------- > 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
