The great thing about green screens is that they are so easy and so quick to use. Basically, a screen appears, you enter some information, press tab, enter some more information, and press enter. It’s quick, it’s simple to use, what’s not to like? And that’s how so many mainframers feel. They’ve been using green screens since they were really green to get their work done accurately and efficiently. ISPF, SDSF, and SMP/E are just so straightforward to use with a 3270 display.
So, how did all this start? The IBM 3270 terminal first saw the light of day in 1971 as a way to communicate with the mainframe. At that time, display screens were very expensive, and therefore used a zinc sulphide coating, because it was the cheapest way to get a screen that was bright enough display to be useful. And the result was green characters on a dark background. The words (there were no pictures) that appeared arrived in large blocks of data known as data streams, and the screen was mapped so that it would only accept text in certain fields. Often, a screen’s worth of information would be 24 lines by 80 characters.
The later 3279 came with a colour screen – but it was still referred to as a green screen. IBM stopped making 3270 terminals, but the protocol continued to be used, allowing people to access the mainframe in terminal emulation mode. Back in the early 1990s, every connection used SNA, but people gradually switched to Telnet, which was a popular protocol for the Internet or local area networks because it provided a bidirectional interactive text-oriented communication facility using a virtual terminal connection. Nowadays, you don’t hear very much about Telnet because of security issues – people now use SSH. Telnet 3270 (tn3270) describes both the process of sending and receiving 3270 data streams using the Telnet protocol and the software that emulates a 3270 class terminal communicating using that process. What made it so successful was that tn3270 allowed a 3270 terminal emulator to communicate over TCP/IP instead of SNA.
But things never stay the same for long in IT, and even though experienced mainframers were getting work done speedily and efficiently on their green screens, the rest of the world was using browsers and enjoying lots of colours and pictures – something that 3270 emulators couldn’t quite match. A whole generation of IT people grew up wanting to use a GUI to talk to the mainframe – they wanted the same flexibility as a browser screen. New users were surprised (horrified) when they saw the antiquated looking green screens being used – even though mainframers could get more work done in less time using them than using the pretty browser windows.
And that’s where mainframe environments are today and. How do you make your mainframe applications palatable for younger, GUI-loving people, while at the same time allowing your experienced (but older) staff to continue to quickly get work done using their familiar ‘green screens’?
One possible solution (although the odds are quite long at this stage) is to do away with systems programmers because they can be replaced by Artificial Intelligence (AI). The fact that Watson will now run on mainframes makes it possible that it will become such a powerful AI that people won’t be needed to do anything to keep z/OS running optimally. And it will even troubleshoot itself and install PTFs, etc.
Another option for development work is to use Eclipse. The reason for that suggestion is that younger people are probably familiar with it because they may well have used it for Java development already, and it’s Open Source, and it’s supported by IBM.
So, in conclusion, let me confirm that, like so many mainframers, I love green screens. I just know that moving forward, all-singing and dancing software is the way to attract younger people into the world of Big Iron.
Regular Planet Mainframe Blog Contributor
Trevor Eddolls is CEO at iTech-Ed Ltd, and an IBM Champion since 2009. He is probably best known for chairing the Virtual IMS, Virtual CICS, and Virtual Db2 user groups, and is featured in many blogs. He has been editorial director for the Arcati Mainframe Yearbook for many years.