IBM OS/390 User Manual

Page of 673
your MQSeries based applications.
In the next sections each of these topics will be addressed at a general level. No
detailed checklists or migration guidelines are given. This would go beyond the
scope of this chapter. The purpose of this discussion is to make you aware of the
areas which need to be studied in detail when you intend to migrate.
Only straight forward migration is considered. MQSeries applications under
VSE/ESA always:
run under CICS for VSE/ESA
are coded in COBOL and compiled with COBOL for VSE
communicate with other systems through SNA/LU6.2.
Under VSE/ESA you do not have any other options.
The basic assumption is that you migrate to MQSeries for MVS/ESA as directly
as possible:
using CICS/ESA to run your migrated MQSeries applications
staying with COBOL as the programming language
still using SNA/LU 6.2 connections to communicate with other MQSeries
systems.
If you want to make use of the additional facilities of MQSeries for MVS/ESA,
such as IMS support or C language support or TCP/IP connectivity, this would
have to be done in a separate, second step not discussed here.
9.5.1 MQSeries in Your Operating System Environment
You will have to verify that you have the necessary software prerequisites on
your OS/390 system to run the migrated applications, install the MQSeries for
MVS/ESA product, verify that you have space for the required data sets and
define them on your OS/390 system. These points will be addressed below.
9.5.1.1 Prerequisites
MQSeries for VSE/ESA V1.4 (product number 5787-ECX) is an MSHP-installable
licensed program. It operates with CICS for VSE/ESA, providing coordination
between MQSeries and CICS resources by allowing CICS for VSE/ESA
transactions to issue MQSeries (MQI) calls.
MQSeries for VSE/ESA does not run in a VSE partition. It executes under control
of CICS for VSE/ESA.
It supports communication with other MQSeries products through SNA/LU 6.2.
198
VSE to OS/390 Migration Workbook