IBM OS/390 User Manual

Page of 673
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.
1
Acquire DB2 for OS/390 skills
2
Install 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.
3
Change 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.
4
Migrate object definitions to DB2
5
Move the data by unloading the data from SQL/DS and then doing a load
into DB2
6
Migrate the application programs
182
VSE to OS/390 Migration Workbook