Mainframes for the younger generation
Mainframes for the younger generation
Embedded Files
Team & project overview
Team & project overview
Product: z/OSMF Software Update "SU" utility
Year(s): 2018-2020
Time frame: 3+ years in the making
Team comp: 1x Product Owner, 1x Scrum Master, 3x Developers, 2x Designers, 2x External (IBM) consultants
Resources: Carbon Design System v9
Achievements: Improved UX by 30 %, directly addressing the industry-wide need for modernization
z/OS, and the z/OSMF (Management facility)
z/OS, and the z/OSMF (Management facility)
z/OS is a 64-bit operating system for IBM z/Architecture mainframes, introduced by IBM in October 2000. z/OS has the attributes of modern operating systems, but also retains much of the older functionality originated back in the 1960s and still in regular use—z/OS is designed for backward compatibility.
The z/OS Management Facility (z/OSMF) framework improves a z/OS system programmer's productivity by using simplified, streamlined and automated tasks. This easier-to-use functionality reduces both programmer training time and the learning curve. It was created to:
Simplify and modernise z/OS management;
Make z/OS more approachable via REST APIs;
Streamline z/OS tasks.
Main features
Main features
Browser based, i.e., removes the need to manage a client application
HTTPS and SAF based for security
Single point of control across systems
Workflows simplify programmer tasks
Sysplex management has many views
z/OS operator console enables system interaction
Software management streamlines the process
Incident log streamlines diagnostics
Workload management tool helps allocate resources
Flexible performance resource monitoring
Capacity provisioning manages domain
REST data set, file services, jobs and console services
Software Update (SU) component use cases
Software Update (SU) component use cases
z/OSMF Software Update provides a graphical user interface (GUI) that z/OS system administrators and system programmers can use to easily manage updates for installed SMP/E managed software.
With the z/OSMF task, users can apply:
Corrective (FIXCAT);
Recommended;
Functional updates to existing software instances.
Target audience
Target audience
SU was designed with especially relatively young and inexperienced Administrators and Systems Programmers (SysAdmins and SysProgs) in mind, to give them a more intuitive set of tools to do their job faster and more efficiently.
Users could manage even in-progress and completed update processes. The task provided a simple alternative to the complex task of running SMP/E JCL and then manually combing through the output and messages to interpret results and take the necessary actions.
What's a Mainframe?
What's a Mainframe?
A mainframe computer, informally called a "Mainframe" or "Big Iron", is a computer used primarily by large organizations for critical applications like bulk data processing for tasks such as censuses, industry and consumer statistics, enterprise resource planning, and large-scale transaction processing.
Mainframe computers are often used as servers and are operated by Systems Administrators (SysAdmins) and Systems Programmers (SysProgs). One such programmer is our Tyler, a 28 y.o. mainframer, with just a few years of experience to his account.
Problems to solve we solved
Problems to solve we solved
Work complexity;
Training costs of staff;
Modernization.
Prior to the emergence of Graphic User Interfaces (GUIs), mainframes were solely accessed through terminal consoles or Command Line Interfaces (CLI), which, despite the fervent support by CLI enthusiasts, were not always the most efficient way of performing tasks. Recognizing the need to appeal to a younger cohort of developers and equip them with tools for enhanced speed and efficiency, IBM collaborated with what was then CA Technologies, presently known as Broadcom, to devise a more intuitive approach that would facilitate the streamlining and contemporary management of z/OS systems.
The approach we took
The approach we took
As an Agile team, we:
Held weekly meetings with IBM consultants discussing mostly technical, but also design challenges;
Met daily for stand-ups (not comedy, although we did have fun) to discuss blockers, etc.;
Worked iteratively based on feedback, which was translated into user stories, after conversations with our IBM counterparts;
Incremental research encompassed:
Interviewing stakeholders and users;
Testing (moderated, participants recruited from panels mostly, but also some IBM people);
Iterative design work based on the above in 2-week sprints. No Sprint 0.
Work on SU meant to:
Work within the confines of z/OSMF, which meant to work as if in an iframe, since we were not allowed to alter anything outside of the designated body for SU.
Work with limited resources (Carbon v9 was, at the time, still largely a WIP), so we hacked some components to adjust them to our needs;
Various other limitations on both ends.
Prototype (demo on-call only)
Prototype (demo on-call only)
Use cases
Use cases
Corrective maintenance
Recommended maintenance
Functional maintenance
...
Our diligent efforts have had a profound impact on the productivity of system programmers, significantly expediting their workflow. Through the implementation of the z/OS Management Facility (z/OSMF) framework, we have successfully enhanced the efficiency of tasks for system programmers, simplifying and modernizing z/OS management.
By utilizing streamlined and automated processes, we have not only minimized training time for programmers, but also reduced the learning curve associated with the system.
Google Sites
Report abuse