OpenFrame Architecture

The Tmax engine monitors transaction processing by checking transactions between heterogeneous computers, balancing loads, and handling errors across a distributed system.

Base runs on the Tmax engine and inherits many of its features such as multi-node clustering, load balancing, and fail-over. These features guarantee high usability and reliability, which are important attributes for any mainframe system replacement.

Mainframe supports a variety of data sets for record I/O and transactions. These data sets can be used at the OS level. The UNIX file system, on the other hand, supports only block unit reads and writes.

Base uses its own relational database technology to provide data set modules and services that support mainframe data set operations.

Mainframes uses EBCDIC encoding, but OpenFrame uses ASCII encoding, the open system standard. When migrating data from a mainframe to an open system or from an open system to a mainframe, Base uses a code page as a mapping table for code conversion.

The system console (or console) consists of a screen for displaying messages from the system kernel and a keyboard for command input. A mainframe administrator uses the given console to manage the system. Some mainframe systems use the system console not only to manage the mainframe system, but also to enter data into an application in real time. OpenFrame provides a virtual console interface for this.

Mainframe applications and JCLs can run in an open system without modifying their application logic. Using them without changes prevents risks associated with program redevelopment.

New batch jobs can be developed easily by using various UNIX applications.

Loads caused by increased batch jobs are distributed by Tmax to existing servers or handled by more physical servers.

If a real or virtual node fails unexpectedly, OpenFrame automatically performs fail over to reroute transactions to other available nodes. When a node failure is detected, the Tmax server automatically recovers the failed node.

Batch provides a host of tools to migrate applications from mainframe to an open system and the libraries needed to develop new tools and utilities. Many of the utility programs used in the existing MVS JCL can be executed in a batch environment.

TJES is OpenFrame’s batch job management component corresponding to the JES subsystem of mainframe. It receives batch job requests, schedules jobs, allocates system resources, executes jobs using the runner, prints job results, and shows job results. TJES allows mainframe JCL to be run in an open system without modification.

Utilities, which are specified in the PGM parameter of JCL, are programs that execute batch jobs after they are submitted. OpenFrame supplies a number of utilities to handle different job functions.

OpenFrame provides utilities that mimic mainframe data set manipulation utilities and interfaces for using desired third-party utilities from mainframe in an open system.

Tools provide various functions for migrating resources, such as data sets and databases, from mainframe to open system and for OpenFrame operation.

A process of screening users who try to access the OpenFrame system. User ID and password are required, and those who fail to be authenticated cannot access the system nor the resources provided by the system.

A resource access list controls access to specific resources by user.

Information about user login time, access frequency and target resource is collected so that the resource manager can monitor each resource’s status and evaluate security vulnerability.

An OSC application server is composed of multiple processes. OSC uses process scheduling to process concurrent transactions quickly and efficiently. It also automatically scales the number of server processes according to load for efficient distributed processing.

Using the configuration files and Run-time System Definition (RTSD) function, OSC allows all processes of a web application server to concurrently access a resource service. An application server and its secondary servers can be mapped to the same OSC region to share the same configurations and resource settings and definitions.

The OSC system provides resource services that are similar or identical to those provided by CICS.

OSC supports the EXEC CICS, EXEC DLI, and CBLTDLI statements so that mainframe programs can run in an open system. The programs must be migrated to the new system using the OpenFrame utilities. You can also migrate the CICS or IMS/DC resources so that you can run the programs in the new system without modification.

You can use TP monitor system utilities to manage OpenFrame.

You can check the OSC system logs and create, update, or view service resource definitions. You can also monitor dynamic system information, such as the OSC server status or dynamic terminal status.

OSI system servers are system modules that provide critical functions required to operate the OSI system, such as message scheduling, management of Message Queues, message conversion via MFS, database integration and processing of system and user commands.

OSI user servers are started directly by users through a process (Tmax server) with JCL or the "/START REGION" command, to run user application programs.

OpenFrame GW supports connection between the web application server and terminals. Through OpenFrame GW, the application server can connect to or disconnect from a terminal based on the application configuration file and allocated resources.

OpenFrame GW allows you to access a web terminal via the 3270 data protocol in the same way as a 3270 protocol emulator.

Available application servers and related resources are shared through a database.

OpenFrame Manager uses a web-based UI with an intuitive interface for monitoring and managing the OpenFrame system. This GUI interface allows users who are not UNIX or mainframe experts to easily manage the system.

If TACF is enabled as the user authentication method, you can use TACF Manager to register and manage user permissions for each resource.