The Meaning of Mainframe Modernization - II

Mainframe modernization means different things to different people. Many apply a plain-meaning rule: If you're modernizing your mainframe, strictly speaking, you're modernizing it in place—updating it with new applications and integrations. To yet others, modernization necessarily involves ridding oneself of all of that pesky COBOL and replatforming elsewhere (for instance, on the cloud or a distributed system).

Misty Decker, director of worldwide AMC product marketing at Micro Focus, characterizes the dichotomy as confusing and not entirely helpful. Decker calls for moving to a broader definition of mainframe modernization that is based on goals and outcomes instead of tools.

"The broadest way to define modernization is not about the technology you're using, but by [how you are] meeting modern business needs," said Decker. "It's really about how well [an] application or infrastructure is meeting the needs of the business."

From this point of view, the mainframe component of mainframe modernization is almost incidental. Instead, for Decker, the doctrine of meeting business needs is everything.

"Modernization is not about the age of the application or the infrastructure," said Decker. "A lot of [modernization] techniques apply the same to an application that is only six months old and is no longer serving the needs of the business."

• Modernizing the mainframe can help close the skills gap. As companies continue to face skills gaps in their talent pool, modernizing systems is the most popular way respondents are working to maintain talent pipelines with 45% of respondents citing it as the top method. Forty three percent of respondents plan to offer mainframe-specific education to help address the skills gap.
• Implementing DevOps functionalities presents a valuable opportunity to modernize the mainframe’s capabilities and performance. Forty four percent of respondents say their organization uses multiple tools for DevOps functionality on mainframe applications, but it is not a complete DevOps platform while 24% have a comprehensive platform for mainframe DevOps.
• Integration of the mainframe with the cloud is key. Leveraging the diversity of solutions available from cloud to mainframe and optimizing each layer to operate together will create the most effective, unified environment. Eighty-two percent of respondents are migrating at least some of their workloads and operations from mainframe to cloud, however only 4% are going completely cloud native. This trend towards hybrid environments emphasizes the need for integration and optimization

Mainframe Modernization - I

 Mainframe Modernization refers to the process of upgrading and adapting your current or legacy mainframe systems, in lieu of complete replacement or operating with outdated mainframe applications. While mainframe technology infrastructure may be outdated, but it is still heavily relied upon in many industries. These extensive computers house massive amounts of data and therefore cannot be easily migrated or updated to adapt to changing business practices and digital innovation.

Mainframes continue to run foundational business applications, but continuing a business-as-usual operation of these mainframes is not cost-effective or sustainable. Additionally, skilled programmers needed to update and maintain mainframe code are beginning to retire. Mainframe programming languages are not as popular with developers as more modern languages. With the onslaught of new technology in this digital revolution, proficiency in application modernization and digital transformation is the new normal.

Aging mainframes present several problems, including cost-affecting inefficiencies, legacy applications with hidden code that are impossible to troubleshoot, and overloaded systems impacting performance. Mainframe modernization involves an analysis of what can be migrated or rehosted and identifies any redundant code. Mainframe migration can include any number or combination of solutions, including migrating to the cloud or a multi-cloud system, rehosting on lower-cost platforms, or even rewriting the mainframe applications entirely into new a mainframe environment.

The risk associated with any of these options is a loss of data or functionality. 

In most cases, migrating or rehosting mainframe applications will allow for more speed and competitive advantage, but certain legacy applications and programming languages cannot be moved. In these instances, it is important to find a solution that maintains the ability to be upgraded and fine-tuned over time, while continuing to be held within its legacy infrastructure.

Benefits:

• Reduce cost of maintenance and operation: The towering infrastructure alone denotes a large cost. The associated costs of housing the mainframe, and monitoring and troubleshooting the colossal computers, can be astronomical. Thus, moving data to cloud-based solutions or removing redundancies eliminates sizeable costs.
  
  
• Skill shift: The original code writers of mainframe software are aging out and retiring. And their skillset is no longer being taught to the next generation of engineers and code writers. New and innovative technologies are taking the place of outdated ones, and your mainframe will no longer be sustainably serviceable if it does not keep up with the changing technology.
  
  
• Reduced dependency: Along with the retirement of those skilled in legacy mainframe technology comes an opportunity for independent management and operation of mainframe systems. Updating technology to more automated systems can create more efficient and cost-effective maintenance options.
  
  
• Competitive advantage: With rapidly improving applications and technologies being introduced every day, the only way to stay competitive is with a system that is easily updated and integrated. Constantly adapting to new trends and innovation is a competitive advantage.
  
  
• Employee Productivity: Allowing legacy systems to move to more automated processes frees up IT department bandwidth to engage in higher-level issues. Eliminating redundancies reduces the time needed to find and fix problems within the code.

How is the IBM Z architecture different from that of other servers?

IBM Z has its own architecture which is designed to work with huge caches, and it has instruction sets to handle enterprise workloads by using IBM’s own S/390x chip architecture. The S/390x architecture is supported by several popular Linux operating systems including SUSE, Red Hat, and Ubuntu, as well as a large number of open source applications.

The “Z” stands for “zero downtime,” which reflects the reliability of the system. IBM Z uses the IBM S/390 chip architecture. 

Data that’s handled by IBM Z is encrypted by dedicated encryption processors over the complete ecosystem, and encryption keys are handled with the most secure hardware security module (HSM) in the industry — which means it is highly secured.

What are the various OS options for Z?

IBM Z runs operating systems including  z/OS, z/VM, z/VSE, z/TPF, and Linux. In fact, it is common for multiple operating systems to run on a single mainframe. 

LinuxONE is an IBM Z system that’s specifically dedicated to running Linux; this combines the benefits of the Linux OS with the capabilities and strengths of the mainframe like outstanding data security, availability, performance, efficiency, and cost savings.

z/OS commands to find out CPU and SU_SEC

To find out the CPU PRocessor details in z/OS


Type


TSO TASID


To Find out the Service unit per second.


Type


TSO SUSEC

RD4Z Comparison Chart

How to install a custom Image into BASE24-eps Desktop

After a BASE24-eps Service Pack upgrade, the custom BASE24-eps Desktop image will be overwritten with the product image.

Therefore, you have to follow the procedure below to replace the BASE24-eps Desktop image with the  custom one (attached).

1) Using a file explorer, go to $ES_HOME/ESUI/Server/Repository/Desktop/UIF

2) Ftp in binary mode the uif_dt.jar to your PC.

3) Open the jar file using 7-Zip(select file and right click) and drag in the two attached files, replacing the existing ones.

4) FTP the jar back to the Server.

Sample JCL to do codepage conversion between z/OS datasets, and also z/OS Unix files.

Sample JCL to do codepage conversion between z/OS datasets, and also z/OS Unix files.

//ICONV    PROC INFILE=,         < INPUT DATA SET            

//   REGSIZ='6M',                < ICONV REGION SIZE          

//   OUTFILE=,                   < OUTPUT DATA SET            

//   FROMC=,                     < INPUT CODE SET NAME         

//   TOC=                        < OUTPUT CODE SET NAME       

//*                                                           

//ICONV     EXEC PGM=EDCICONV,REGION=&REGSIZ,                 

//          PARM=('FROMCODE(&FROMC),TOCODE(&TOC)')             

//SYSUT1    DD DSNAME=&INFILE,DISP=SHR                        

//SYSUT2    DD PATH=&OUTFILE,                                 

//          PATHOPTS=(OCREAT,OWRONLY),PATHMODE=(SIRUSR,SIWUSR)

//SYSPRINT  DD SYSOUT=*                                        

//STDOUT DD SYSOUT=*                                          

//STDERR DD SYSOUT=*                                          

//SYSIN     DD DUMMY                                           

// PEND                                                       

//S1       EXEC ICONV,                                        

//         INFILE='YOUR.INPUT.DATASET',                        

//         OUTFILE='''/your/output/iconvtstd''',  

//         FROMC='IBM-037',

//         TOC='01200'     

//*-----------------------------------------------------------------

//* Convert UNICODE to EBCDIC                                      

//*-----------------------------------------------------------------

//ICONV     EXEC PGM=EDCICONV,REGION=0M,                           

//          PARM=('FROMCODE(01200),TOCODE(IBM-037)')               

//SYSUT1    DD DSNAME=GB41.TEST.UNICODE,DISP=SHR                    

//SYSUT2    DD DSNAME=GB41.TEST.EBCDIC,DISP=(,CATLG,CATLG),        

//             AVGREC=M,SPACE=(15,(15,15),RLSE),                   

//             RECFM=FB,LRECL=15                                   

//SYSPRINT  DD SYSOUT=*                                            

//STDOUT    DD SYSOUT=*                                            

//STDERR    DD SYSOUT=*                                            

//SYSIN     DD DUMMY