Stream: Virtual Room 5
Time: 17:00 - 18:00
Over 50 years ago IBM allowed installations to customize their systems with assembler language code that runs as authorized extensions to the operating system. Since then, the underlying system has become more complex, the understanding of how to interact with the operating system has greatly diminished, the skills in assembler language have almost vanished, and concerns about the integrity and security of the system have increased.
All these factors lead us to find a better solution for specifying JCL rules and other installation policies. This presentation describes a path to eliminating much of the installation exit code that now presents an issue, if not a thread, to the maintenance and smooth running of z/OS systems. It describes a new tool to identify and locate the active installation exit code on a system and then to re-implement the policy embodied in the assembler code with specifications on ISPF panels so that the customer-written installation exit code can be retired. Going forward, the active policies can be transparently viewed on the ISPF panels rather than having to decipher them from arcane decades old assembler language code.
The exit locator tool and the customization capabilities are provided by the zOSEM product of Trident Services. The presentation describes the problem in general terms and goes on to describing a specific solution approach based on the zOSEM product capabilities.
Bob Rogers worked on mainframe system software for 43 years at IBM before retiring as a Distinguished Engineer in 2012. He started with IBM as a computer operator in 1969. After receiving a B.A. in Mathematics from Marist College in 1971, he became a computer programmer at the Poughkeepsie Programming Center, where he worked on the OS/370 operating system. Bob continued to work on mainframe operating system development for his entire career at IBM. He contributed to the transitions to XA-370 and ESA/370, and was lead software designer for the transition to the 64-bit z/Architecture. He implemented the support for single z/OS images with more than 16 CPUs and was a lead designer of the z/OS support for the zAAP and zIIP specialty engines. Today's z/OS implements dozens of his design ideas. Bob has been for many years, and continues to be, a popular speaker at the IBM System z technical conferences and other venues. He is currently working with Trident Services, a California-based z/OS software and services company. Bob has also returned to IBM as a part-time retiree supplemental on the zVM development team.
Bob Rogers worked on mainframe system software for 43 years at IBM before retiring as a Distinguished Engineer in 2012. He started with IBM as a computer operator in 1969. After receiving a B.A. in Mathematics from Marist College in 1971, he became a computer programmer at the Poughkeepsie Programming Center, where he worked on the OS/370 operating system. Bob continued to work on mainframe operating system development for his entire career at IBM. He contributed to the transitions to XA-370 and ESA/370, and was lead software designer for the transition to the 64-bit z/Architecture. He implemented the support for single z/OS images with more than 16 CPUs and was a lead designer of the z/OS support for the zAAP and zIIP specialty engines. Today's z/OS implements dozens of his design ideas. Bob has been for many years, and continues to be, a popular speaker at the IBM System z technical conferences and other venues. He is currently working with Trident Services, a California-based z/OS software and services company. Bob has also returned to IBM as a part-time retiree supplemental on the zVM development team.
Bob Rogers worked on mainframe system software for 43 years at IBM before retiring as a Distinguished Engineer in 2012. He started with IBM as a computer operator in 1969. After receiving a B.A. in Mathematics from Marist College in 1971, he became a computer programmer at the Poughkeepsie Programming Center, where he worked on the OS/370 operating system. Bob continued to work on mainframe operating system development for his entire career at IBM. He contributed to the transitions to XA-370 and ESA/370, and was lead software designer for the transition to the 64-bit z/Architecture. He implemented the support for single z/OS images with more than 16 CPUs and was a lead designer of the z/OS support for the zAAP and zIIP specialty engines. Today's z/OS implements dozens of his design ideas. Bob has been for many years, and continues to be, a popular speaker at the IBM System z technical conferences and other venues. He is currently working with Trident Services, a California-based z/OS software and services company. Bob has also returned to IBM as a part-time retiree supplemental on the zVM development team.
Bob Rogers worked on mainframe system software for 43 years at IBM before retiring as a Distinguished Engineer in 2012. He started with IBM as a computer operator in 1969. After receiving a B.A. in Mathematics from Marist College in 1971, he became a computer programmer at the Poughkeepsie Programming Center, where he worked on the OS/370 operating system. Bob continued to work on mainframe operating system development for his entire career at IBM. He contributed to the transitions to XA-370 and ESA/370, and was lead software designer for the transition to the 64-bit z/Architecture. He implemented the support for single z/OS images with more than 16 CPUs and was a lead designer of the z/OS support for the zAAP and zIIP specialty engines. Today's z/OS implements dozens of his design ideas. Bob has been for many years, and continues to be, a popular speaker at the IBM System z technical conferences and other venues. He is currently working with Trident Services, a California-based z/OS software and services company. Bob has also returned to IBM as a part-time retiree supplemental on the zVM development team.
Bob Rogers worked on mainframe system software for 43 years at IBM before retiring as a Distinguished Engineer in 2012. He started with IBM as a computer operator in 1969. After receiving a B.A. in Mathematics from Marist College in 1971, he became a computer programmer at the Poughkeepsie Programming Center, where he worked on the OS/370 operating system. Bob continued to work on mainframe operating system development for his entire career at IBM. He contributed to the transitions to XA-370 and ESA/370, and was lead software designer for the transition to the 64-bit z/Architecture. He implemented the support for single z/OS images with more than 16 CPUs and was a lead designer of the z/OS support for the zAAP and zIIP specialty engines. Today's z/OS implements dozens of his design ideas. Bob has been for many years, and continues to be, a popular speaker at the IBM System z technical conferences and other venues. He is currently working with Trident Services, a California-based z/OS software and services company. Bob has also returned to IBM as a part-time retiree supplemental on the zVM development team.
Bob Rogers worked on mainframe system software for 43 years at IBM before retiring as a Distinguished Engineer in 2012. He started with IBM as a computer operator in 1969. After receiving a B.A. in Mathematics from Marist College in 1971, he became a computer programmer at the Poughkeepsie Programming Center, where he worked on the OS/370 operating system. Bob continued to work on mainframe operating system development for his entire career at IBM. He contributed to the transitions to XA-370 and ESA/370, and was lead software designer for the transition to the 64-bit z/Architecture. He implemented the support for single z/OS images with more than 16 CPUs and was a lead designer of the z/OS support for the zAAP and zIIP specialty engines. Today's z/OS implements dozens of his design ideas. Bob has been for many years, and continues to be, a popular speaker at the IBM System z technical conferences and other venues. He is currently working with Trident Services, a California-based z/OS software and services company. Bob has also returned to IBM as a part-time retiree supplemental on the zVM development team.
Click here to give some Feedback so we can make it even better next year!