Teaching the New Class of Mainframe Architects

Houston has encountered difficulties along the way, however. He is part of the new class of mainframers working alongside the more established folks—and at times he has found himself having to adjust to certain practices. For example: While the older generation tends to employ a command-line interface, or CLI, the newer generation was brought up using a graphical user interface, or GUI. In order to keep up with his team, Houston had to teach himself how to translate one to the other. “You feel like you’re becoming a bridge between two worlds,” Houston remarks. He was able to overcome this challenge by indulging his natural curiosity—using zHMC, he determined ways to safely run commands that would not impact the system.

Another obstacle that Houston faced was learning the shared vocabulary and unique language of the mainframe space. “We use a lot of slang…there’s acronyms inside of acronyms,” he says, adding that each team may even have their own slang. Houston says the shorthand is helpful for conveying information quickly, but it can alienate newcomers.

The solution to filling these mainframe education gaps? Houston suggests that beginner mainframe architects ask their mentors questions. They often know exactly why something is done a specific way and may even have firsthand experience of the moment a method changed or was established. “There’s a lot of history that books just can’t teach, and that’s why you ask questions,” says Houston.

Stanard has served as a valuable resource throughout Houston’s mainframe journey. “I want to make sure that [my] knowledge is shared with people like Bobby, so that he can take it and use it in his career.”

Mentors are also useful because of their connections. Once, Houston needed help with a project that involved installing a Cisco FICON Director, and no one on his team had the knowledge required to assist him. Luckily, his mentor was able to connect him with a Cisco representative, who had the expertise Houston was seeking. Having access to his mentor’s network enabled him to finish the project.

Houston’s experience with mentorship came full circle when he completed the Cisco FICON Director. He was the first on his team to do this, which meant that he could act as a mentor if any of his teammates had questions. “It’s a very powerful thing when we get together because everybody shares stories, and everybody mentors one another,” adds Stanard.

Even admitting to a mistake can have positive consequences. Houston points out, “If I teach you and you make mistakes, you [can] come in and tell me about your mistake …Then, we all make less mistakes.”

The systems that mainframe architects interact with every day are becoming increasingly intricate and nuanced. However, Houston believes the future holds “a more optimized and refined mainframe,” and the wave of emerging mainframe architects is sure to lead to an influx of innovation that can contend with any hurdles that come along.

Both Houston and Stanard are eager to share words of wisdom with incoming mainframe architects. “As [a mainframer] goes through their career, they might hear, ‘Well, it’s always been done this way,’ or ‘We’ve never done it.’…That’s an opportunity. That’s not a roadblock,” Houston says.

Similarly, Stanard advises mainframe architects to not be afraid of change or trying new things.

“I think it’s awfully important that we give people opportunities to try things that are tough,” he says. “You may fall down a few times, it’s okay. My mother would always say, ‘Hey, it’s okay to fall down…Brush yourself off, get up and keep going.’”