∙http://www.software.ibm.com/year2000/db2-html

SQL/DS Version 5 (proper name is DB2 for VSE Version 5) is Year 2000 compliant.

8.2.2.2 DRDA Considerations

DRDA level of functions in SQL/DS are upward compatible to DRDA functions in DB2. DB2 has more DRDA functions than SQL/DS. For the DRDA Remote Unit of Work (RUW) level, DB2 is compliant as an Application Requestor (AR) and Application Server (AS). SQL/DS is only on the AS level for RUW. For the DRDA Distributed Unit of Work (DUW), DB2 is AR and AS compliant, again SQL/DS is only at the AS level. Stored Procedures in DB2 can be used to do DRDA AR and AS level work, SQL/DS has no such support.

8.2.2.3 Data Replication and Data Access

DB2 has an Apply and Capture component for DataPropagation - both are separate products. SQL/DS only has a Capture component as a feature of the SQL/DS product. Both DBMSs can be accessed by DataJoiner. DB2 can interface with DataPropagator NonRelational, SQL/DS has no interface to this product. Both DBMSs have interfaces to the DataRefresher product to do data extractions.

8.2.2.4 Transaction Management

SQL/DS can interface to CICS/VSE and ICCF. DB2 can have the front-ends of

IMS/ESA, CICS/ESA or TSO.

8.2.2.5 Other Product Areas

Both products can be accessed from the internet using Net.Data. SQL/DS has a VSAM Transparency product, DB2 does not. Both can be used with DataHub. In the area of administration tools, SQL/DS has a tool called SQL Master. For DB2, there is the Automated Utility Generator, and DB2 Administrative Tool. QMF can be used to query both DBMSs.

8.2.3 Summary of Migration Task

It is difficult to be precise as to what are the specific tasks and their order for a migration effort, but we can give you general ideas.

1Acquire DB2 for OS/390 skills

2Install DB2 and prerequisites products (at supported levels). Then install other companion products of your choice (in the area of transaction management, data replication, administration and so on). Next you need to tailor your DB2 system by specifying DB2 parameters and execution options.

3Change SQL syntax where required. This will probably not be a big effort for DML (programs and user queries). For DDL and DCL, this is a different story and there is a bigger difference in these two areas of security administration and data and DB2 object definition. The SQL Reference document will be very helpful here.

4Migrate object definitions to DB2

5Move the data by unloading the data from SQL/DS and then doing a load into DB2

6Migrate the application programs

182VSE to OS/390 Migration Workbook

Page 205 Page 207
Page 206
Image 206
IBM OS/390 manual Summary of Migration Task, Drda Considerations, Data Replication and Data Access, Transaction Management
Page 205 Page 207

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.
Top Page Image Contents