IBM OS/390 User Manual

Page of 673
Table 1 (Page 3 of 3). Comparison of VSE Functions & Components to OS/390
Replacements
VSE
OS/390
Comment and Reference
ADSM/VSE
A D S M / M V S
DITTO/ESA for VSE 
DITTO/ESA for OS/390
See Chapter 20 page 381
DFSORT/VSE
DFSORT *
See Chapter 19 page 375
Data Base Management
DL/I
DB2 (SQL/DS)
Q M F
Data Base Management
I M S / D B
D B 2
Q M F
See Chapter 8 page 169 
GDDM/VSE
G D D M / M V S *
See Chapter 7 page 155 
D u m p A n a l y s i s
Info/Analysis
(VP)
D u m p A n a l y s i s
IPCS *
Job Scheduler (VP)
OPC/ESA
Report Manager (VP)
RMDS
NetView family
FTP
NetView family
FTP
Key:
(*) = Package is an element of OS/390. (ISV) = VSE function provided by independent
Software Vendor
2.2 OS/390 Components/Products/Subsystems
Note:
The terms OS/390 and MVS (including MVS/XA, MVS/SP, and MVS/ESA)
may be used interchangeably throughout this publication. OS/390, with its
integrated components, refers to the current version and all previous versions of
MVS unless otherwise noted.
Another important aspect to consider when sizing the migration is determining
which OS/390 components will be installed. This is basically determined by
assessing which OS/390 components and/or optional products provide functions
comparable to those in VSE. The previous table in this section provided a
comparison chart for this purpose. What follows is a brief description of some of
the key OS/390 components.
There was discussion about including that which is the same between the
operating systems. This can be a big item when customers are also entertaining
ideas of other operating systems. There is more closeness between VSE and
OS/390 than with RISC6000/UNIX to OS/390. The move to UNIX will require a new
start or complete rewrite.
This is a frequent consideration when customers are considering implementing
ERP Applications. They can put these core business integrated packages (for
example SAP R3, Bond, JDEdwards, Oracle) on either a UNIX or OS/390
platform.
18
VSE to OS/390 Migration Workbook