Automated Conversion Process, Cortex MS

routines must allow users to custom adapt the tools to specific local conversion requirements. These requirements, not addressed by standard processing, are always identified. The conversion tools must be custom modified by positioning execution options, coding exit routines, and possibly developing some ad-hoc pre- or post-processors.

Finally, tools specifically designed for mass conversion must simplify and accelerate the review and verification of mass conversion results by producing summary statistical reports, which allow identifying and assessing at a glance the conversion of hundreds or thousands of items.

32.2.4 Automated Conversion Process

Assembling and customizing the mass conversion tools result in an automated conversion process, which converts the entire VSE application portfolio to OS/390 in only a few hours, including:

∙

Collection and verification of the application inventory

Translation of application programs and associated macros, copybooks or subprograms

∙

Generation of OS/390 load modules

Migration of the CICS maps

Conversion of other production source items such as FCBs or PSBs and DBDs

∙Conversion of VSE and POWER JCL streams including application and utility steps and associated SYSIN cards

∙Generation of new OS/390 JCL complying with the selected OS/390 production standards

∙Migration of VSE production files to OS/390

32.2.5CORTEX MS

CORTEX Migration System (CORTEX MS distributed by Sisro Inc.) is the primary tool for mass conversions from VSE to OS/390. It consists of seven software components for converting VSE systems to OS/390. All of the CORTEX MS components are menu-driven through TSO/ISPF panels. CORTEX MS is installed either on the future OS/390 production system or on a temporary OS/390 conversion system. All seven CORTEX MS components are necessary to automate the mass conversion. Listed below is a description of the CORTEX MS software components:

DMT (DOS/OS/390 Translator)

A translator for VSE JCL and programs written in COBOL,

Assembler, PL/1, and RPG II.

INT (File Integration)

Consolidates the results of JCL translation, classifies files according to their life cycle, and loads the Production Database (PDB).

PDB (Production Database)

A batch application change control system that automatically generates OS/390 JCL to custom defined OS/390 standards. PDB uses an internal Production Control Language (PCL) for

490VSE to OS/390 Migration Workbook

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.

IBM Automated Conversion Process, Cortex MS, DMT DOS/OS/390 Translator, INT File Integration

Models: OS/390