|
| name = OpenFrame
| developer = TmaxSoft
| genre = Mainframe rehosting
| latest_release_version =
| latest_release_date = {{release date}}
| latest_preview_version =
| latest_preview_date =
| operating system = [[Unix, Linux]]
| genre = [[Web Server]]
| license = [[Proprietary software|Proprietary]]
| website = {{url|httphttps://www.tmaxsoft.com/products/openframe/}}
}}
'''OpenFrame''' is a [[Mainframe computer|mainframe]] [[rehosting]] solution developed by [[TmaxSoft]] that aims to help customers move existing mainframe assets to the [[Cloud computing|cloud]] quickly and with minimal risk.<ref>{{Cite news|url=https://www.tmaxsoft.com/products/openframe/|title=Mainframe Rehosting {{!}} OpenFrame{{!}} TmaxSoft|work=TmaxSoft|access-date=2017-11-02|language=en-US}}</ref> It replaces legacy CICS/IMS/JES mainframe engines and shifts business applications written in legacy code like [[COBOL]] and [[PL/I]] to [[Linux]].<ref>{{Cite news|url=http://www.eweek.com/networking/tmaxsoft-openframe-challenges-ibm-mainframe-business|title=TmaxSoft OpenFrame Challenges IBM Mainframe Business|work=eWEEK|access-date=2017-11-03|language=en-US}}</ref> This allows reduced licensing costs compared to the mainframe.
It also includes a test tool which helps users determine if the migration will preserve functionality without additional adjustments.<ref>{{Cite web|url=https://virtualizationreview.com/articles/2016/11/17/walking-away-from-the-mainframe.aspx|title=Walking Away From the Mainframe -- Virtualization Review|website=Virtualization Review|language=en|access-date=2017-11-03}}</ref>
'''OpenFrame''' is a Mainframe legacy rehosting solution that enables mainframe assets in a mainframe legacy system to be migrated to a more reliable and high performance open system. OpenFrame has been chosen as the replacement IT infrastructure for many leading companies around the world. <ref>http://www.tmaxsoft.com/bbs.do?cms_cd=ABO_10. Retrieved 2014-02-27.</ref><br />
The current version of OpenFrame is 7.0, which was first released in Japan in September, 2015.<ref>{{Cite web|url=https://cn.tmaxsoft.com/company/noticeView.do?seq=38|title=TmaxSoft - Better Technology, Better Tomorrow - News & Events|website=cn.tmaxsoft.com|language=ko|access-date=2017-11-29}}</ref> The previous version, OpenFrame 6.0 was released in the U.S. market in 2009.<ref>{{Cite web|url=http://www.marketwired.com/press-release/tmaxsoft-launches-openframe-60-to-us-market-1173849.htm|title=TmaxSoft Launches OpenFrame 6.0 to U.S. Market|date=10 November 2009|website=MarketWired}}</ref>
'''OpenFrame''' is comprised of a number of different elements required to provide replacement features and functionality for a legacy mainframe system to be migrated and run in an open system environment. These correspond to elements of a mainframe system and include; OpenFrame Online, OpenFrame Batch, OpenFrame OSC for IBM CICS, OpenFrame OSI for IBM IMS, OpenFrame Web, OpenFrame TACF, OpenStudio and SysMaster for OpenFrame.<br />
== Mainframe Migration ==
OpenFrame can be used to Migrate the applications resources and datasets from Legacy IBM, Fujitsu and Hitachi mainframe systems. In the majority of cases applications run on a mainframe system can be automatically converted to run in an Open Environment with little or no change to the original source code or business logic.<br />
Organizations that run on mainframes tend to have difficulty with costs and agility.<ref>{{Cite news|url=http://www.information-age.com/mainframes-hinders-application-delivery-123463643/|title=The mainframe is hindering application delivery - Information Age|date=2016-12-14|work=Information Age|access-date=2017-11-29|language=en-GB}}</ref> Rehosting is one approach an organization may take to migrate their mainframe operations to the cloud, with other options including batch-job migration and full re-engineering. With the rehosting option, the entire mainframe is emulated on the cloud so that the end-user experience is essentially unchanged.<ref>{{Cite web|url=https://medium.com/aws-enterprise-collection/yes-you-can-migrate-your-mainframe-to-the-cloud-92df0277d1ac|title=Yes, You Can Migrate Your Mainframe to the Cloud|last=Orban|first=Stephen|date=2017-01-09|website=AWS Enterprise Collection|access-date=2017-11-29}}</ref>
== Compatibility ==
[[File:OpenFrame 7 Architecture.jpg|thumb|440x440px|Solution architecture of OpenFrame 7.0 (click to enlarge)]]
[[File:OpenFrame Implementation Methodology.jpg|thumb|440x440px|OpenFrame 7.0 implementation methodology (click to enlarge)]]
OpenFrame advertises the following components can be migrated and continue working without modification, provided they run on open systems components such as Linux:
* [[Compiler|Compilers]]
** [[COBOL]]
** [[PL/I]]
** [[Assembly language#Assembler|Assembler]]
* Datasets
** [[Flat file database|Flat files]]
** GDGs
** [[Virtual Storage Access Method|VSAM]]
* [[Database|Databases]]
** [[IBM Information Management System|IMS]]
** [[IBM Db2|DB2]]
** [[IDMS]]
** [[Oracle Database|Oracle]]
* Online Systems
** [[CICS]]
* Batch Systems
** JES
** JCL
== HistoryNotable Users ==
'''OpenFrame''' for IBM MainFrame was launched in 2002.<ref>http://www.tmaxsoft.com/bbs.do?cms_cd=ABO_10. Retrieved 2014-02-27.</ref><br />
'''OpenFrame''' OSC 6.0 was released in November 2009.<ref>http://www.marketwired.com/press-release/tmaxsoft-launches-openframe-60-to-us-market-1173849.htm . Retrieved 2014-02-27.</ref><br />
The most recent version '''OpenFrame''' OSC 7.0 was released in 2013.<br />
=== Kela ===
The following table shows the release dates of OpenFrame Software versions for IBM MF, Fujitsu MF and Hitachi MF, the COBOL Compiler and OpenStudio.
[[Kela (Finnish institution)|Kela]], the Finnish government agency in charge of the nation's social security programs, used OpenFrame to rehost its mainframe. The agency had estimated that the rising costs of maintaining a mainframe would become prohibitive in the near future, and saw a shortage of IT professionals skilled in working in a mainframe environment. As a result, Kela was able to lift over 10 million lines of code to the rehosted environment and reduce the cost of system maintenance. Since the rehosted iteration was functionally similar to the mainframe system, Kela was also able to keep its existing IT staff in place.<ref>{{Cite news|url=http://www.dataversity.net/case-study-kela-rebirth-mainframe-system/|title=Case Study: Kela and the Rebirth of the Mainframe System - DATAVERSITY|date=2017-10-04|work=DATAVERSITY|access-date=2017-11-29|language=en-US}}</ref><ref>{{Cite web|url=https://digitalisationworld.com/article/52298/2|title=Digitalisation World|website=digitalisationworld.com|date=6 September 2017 |access-date=2017-11-29}}</ref>
=== GE Capital ===
{| class="wikitable"
[[GE Capital]] opted to use OpenFrame to modernize its aging IT infrastructure, which was mostly made up of mainframes. Before rehosting, the GE Capital system was managing 5 million account schedules, over 382 interfaces, with up to 1,700 concurrent users, resulting in an average of 3.5 million transactions per day. In addition to high costs, the disaster recovery process was slow and the system was generally inefficient. OpenFrame allowed GE Capital to rehost without redeveloping any applications or changing the user interface. The results included 66% reduction in costs associated with running the system and a 240% increase in disaster recovery speed.<ref>{{Citation|last=Modern Systems YouTube Channel|title=GE Capital Gartner Case Study|date=2016-07-20|url=https://www.youtube.com/watch?v=3fjvs2zGljk|accessdate=2017-11-29}}</ref><ref>{{Cite web|url=https://tmaxsoftnews.com/2016/03/03/ge-capital-revives-mainframe-with-openframe-by-tmaxsoft/|title=Assessing, Converting & Replatforming a Massive Business Critical Application with Astonishing Results|date=March 3, 2016|access-date=November 29, 2017|archive-date=December 1, 2017|archive-url=https://web.archive.org/web/20171201044353/https://tmaxsoftnews.com/2016/03/03/ge-capital-revives-mainframe-with-openframe-by-tmaxsoft/|url-status=dead}}</ref>
|-
! Product/Year !! 2005 !! 2006 !! 2007 !! 2008 !! 2009 !! 2010 !! 2011 !! 2012 !! 2013
|-
| OSC || 2.0 || - || 4.0 ||- || 6.0 || - || - || - || 7.0
|-
| OSI || -|| -|| 2.0 || - || 3.0 || - || - || - || 4.0
|-
== References ==
| MVS Batch || 2.0|| -|| 4.0 || - || 5.0 || - || - || - || 5.2
<references />
|-
! COBOL Compiler !! !! !! !! !! !! !! !! !!
|-
| OFCOBOL || - || - || - || - || - || v-alpha || -|| 1.0 || 2.0
|-
| OpenStudio || (Eclipse) || - || - || - || - ||- || - || - || -
|-
! Fujitsu Mainframe !! !! !! !! !! !! !! !! !!
|-
[[Category:Proprietary software]]
| AIM || - || 2.0 || - || 3.0 || - ||- || - || - || 4.0
[[Category:Software maintenance]]
|-
[[Category:Installation software]]
| XSP Batch || - || 2.0 || - || - || - ||- || - || - || 2.2
|-
| MSP Batch || - || - || - || 2.0 || - ||- || - || - || 2.2
|-
| NDB || - || 2.0 || - || 3.0 || - ||- || - || - || 4.0
|-
| OpenStudio || - || - || - ||(Eclipse)|| - ||- || - || - || -
|-
! Hitachi Mainframe !! !! !! !! !! !! !! !! !!
|-
| VOS3 Batch || - || - || - || - || - ||- || 2.0 || - || 3.0
|-
| ADM/DC || - || - || - || - || - ||- || 2.0 || - || 3.0
|-
| ADM/DB || - || - || - || - || - ||- || 2.0 || - || 3.0
|-
| OpenStudio || - || - || - || - || - || - || (Eclipse) || - || -
|-
|}
<br />
== Features ==
The main feature of '''OpenFrame''' is that it is possible to migrate applications, resources, and data from a mainframe system to an open system, without modifying the original business logic. <ref>OpenFrame White_Paper: Legacy Modernization through Rehosting http://www.platformmodernization.org/tmaxsoft/Lists/ResearchPapers/Attachments/2/OpenFrame_White_Paper.pdf. Retrieved 2014-02-27.</ref><br />
Switching to OpenFrame® can reduce the [[Total cost of ownership|TCO]] (60%) of the existing system.<ref>http://eyeball.bloter.net/archives/1674. In Korean. Retrieved 2014-02-27.</ref>,<ref>http://www.tmaxsoft.com/product/productView.do. Retrieved 2014-02-27.</ref>,<ref>Mainframe Rehosting with TmaxSoft OpenFrame(TM) Drives Cost Savings at LIG Insurance. http://www.thefreelibrary.com/Mainframe+Rehosting+with+TmaxSoft+OpenFrame(TM)+Drives+Cost+Savings...-a0153696536. Retrieved 2014-02-27.</ref>. <br />
The main components of an '''OpenFrame''' solution are as follows:<br />
* '''OpenFrame Online'''
OpenFrame Online handles user requested programs and allows [[CICS|CICS]] / [[IMS|IMS]] programs to run without modification to the original source code or changes to functionality.<br />
* '''OpenFrame Batch'''
OpenFrame/Batch is used to run JCL batch jobs in OpenFrame. These are typically run after hours. OpenFrame/Batch offers the following features:<br />
JCL and batch applications can be migrated from a mainframe and run without modification to the original source code or the business logic and therefore avoiding the risks caused by program redevelopment.<br />
New batch jobs can be developed easily by using applications provided by the UNIX system.<br />
If real or virtual nodes fail unexpectedly, OpenFrame's fail-over functions automatically reroute
transactions to other available nodes. After the node failure is detected, an automatic recovery
of the failed node can be performed by the Tmax server.
OpenFrame Batch provides a host of tools to migrate applications from the mainframe to an open system environment, as well as the libraries needed to develop new tools and utilities. Many of the utility programs used in the existing MVS [[Job Control Language|JCL]] can be executed in a batch environment.
* '''OpenFrame TACF'''
Security and permission management is provided by OpenFrame TACF which is comparable to [[RACF|RACF]] in a mainframe system. OpenFrame/TACF uses a Tmax CS (client/server) type interface, as well as API type interfaces. The main features of OpenFrame/TACF are as follows:<br />
'''User Authentication:''' Users must possess a valid ID and password to access resources within OpenFrame.<br />
'''Resource Access Control:''' The administrator can define the specific resources that each user can access.<br />
'''Resource Access Log:''' TACF records a range of system statistics, such as connection times, access counts, resources
accessed, etc. These log records are the source for providing statistical reports and analyzing user behavior and resource usage trends.<br />
* '''SysMaster for OpenFrame'''
'''Tmax SysMaster''' is an [[Application Performance Management|APM]] solution that manages a wide range of enterprise system components. It supports efficient resource management by enabling identification of IT infrastructure status and error causes and supporting statistics analysis for applications such as [[Application Servers |WAS]] Web Application Servers, [[TP-Monitor|TP-Monitors]], [[database|databases]], and [[framework|frameworks]].
* '''OpenStudio'''
OpenStudio is a GUI-based tool for analysis, control, and development of the processes for OpenFrame. It provides effective monitoring and optimization functions for the system environment.
'''OpenStudio''' consists of a client application and RMI Based Objects. The client Application (OpenStudio Client)is based on the Eclipse Rich Client Platform and a Java server (OpenStudio Server) for interfacing and secure handling of the OpenFrame system. The structure of OpenStudio Server follows the master/agent model. The master is responsible for communications within the OpenFrame system, and the agent is responsible for communicating with particular machines.
The RMI (Remote Method Invocation) based objects such as OSM, DEV, DEP, OMC, BM and TM, contain client modules developed by the Eclipse Project. Modules are standalone allowing easy updates, development, customization and inter-operability.<br />
The main features of OpenStudio are as follows:<br />
'''Easy-to-use user interface:'''
As a tool which provides an overall user interface needed to operate OpenFrame, OpenStudio provides a Java Eclipse Rich Client based console. Users can manage the system from the comfort of a familiar environment through a user-friendly-designed UI, even when they do not have sufficient knowledge of the UNIX operating system or OpenFrame.<br />
'''TACF authentication:'''
If the authentication type within the common.properties file is set up as TACF, authentication
function can be interlocked with OpenFrame’s own TACF to authenticate users and resources.
In this case, user permissions are controlled by the TACF manager allowing a high degree
of flexibility in user management policies.<br />
'''Built-in database support:'''
If the user-processed information needs to be recorded, OpenStudio uses "HSQLDB" internally
to store them (e.g. DEV module's compilation information for each project and DEP module's
request deployment information, etc.).
Databases other than HSQLDB are also compatible through the db.properties file.<br />
'''Automatic update:'''
When multiple users login, the updated modules are downloaded automatically, without user
input required, maintaining the latest modules allowing easy roll-out of patches and new
features.<br />
'''Failover and load balancing:'''
OSM manages the master and agent directly, providing load balancing for multiple connections
and a failover mechanism in case of server error.<br />
OpenFrame also provides a [[COBOL| COBOL Compiler]] which is compliant with [[COBOL85|COBOL85]] standard and IBM Extension language specifications and supports VSCOBOLII and MFCOBOL dialects<br />
== Further Reading ==
OpenFrame White_Paper: Legacy Modernization through Rehosting
http://www.platformmodernization.org/tmaxsoft/Lists/ResearchPapers/Attachments/2/OpenFrame_White_Paper.pdf
==References==
{{Reflist}}
| 