33.2.6.1 Recovery/SRC

This is the basic service provided by SRC. The basic recovery utilizes a proprietary technology that generates the source code from the load module supplied by the client. Data names and labels within the programs recovered are generic.

33.2.6.2 Rename/SRC

This is a service that is sold in addition to the basic recovery service (Recovery/SRC). The renaming service matches client-provided copybooks to the data definitions generated by the recovery technology. The source returned to the client will contain the original data names as defined in the copybook where appropriate.

33.2.6.3 Reconcile/SRC

This service is sold in addition to the basic recovery service (Recovery/SRC). The reconciling service blends client provided versions of the source program with the program generated by the recovery technology. The source returned to the client will contain appropriately matched data names, labels and original comments based on the client provided version of the source program.

33.2.6.4 VersionMatch/SRC

This service is offered separately from the other recovery services. The purpose of VersionMatch/SRC is to match source code to load modules. SRC will respond with a written report that identifies which version of source matches the load module. If no match is found, the client is afforded the option of requesting SRC to provide additional recovery or reconciliation services as defined above.

The Source Recovery Company can recover code written in any version of IBM Assembler or COBOL. Part of the process allows for discovering in just which version of these languages the source code was originally written, and they will return it to you in the original ²flavor² of that language. In fact they are always looking for older versions of compilers, and if you have one, they¢d like to hear from you.

33.2.6.5 A COBOL Recovery Example

Since the compiler does not store any of the original data or paragraph names in the object module, Recovery/SRC must build generic names. The names generated are based upon where the item is located in the program (such as,

²WS² for an item in Working Storage, followed by a hexadecimal number representing the item¢s displacement from the beginning of the record). Rename/SRC and Reconcile/SRC are additional and optional services offered to enhance the actual datanames in the recovered source code.

33.2.6.6 Original Program Source Code Example

For information about source code recovery and an example of a program recovered by The Source Recovery Company in COBOL, see the Internet at:

www.source-recovery.com

526VSE to OS/390 Migration Workbook

Page 550
Image 550
IBM OS/390 manual Recovery/SRC, Rename/SRC, Reconcile/SRC, VersionMatch/SRC, Cobol Recovery Example

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.