This chapter describes how to install the MessageQ MVS Client software. It includes the following topics:
To successfully install MessageQ MVS Client software, refer to the following topics for more information:
Preinstallation Requirements
This section describes the software requirements for the IBM Language Environment for Batch or for CICS. It also describes software requirements for MVS batch environments without the IBM Language Environment.
Note:
The MVS Client software is distributed on an industry-standard ISO 9660-format CD-ROM which can be read using a UNIX or Windows NT system. The installation requires FTP for MVS to transfer the distribution files to the target MVS system. The system on which you read the distribution media must have a TCP/IP network connection to the target MVS system in order for you to use FTP to transfer the MVS Client software.
To develop applications in the MVS and CICS environments, your IBM system must have the following software installed before you can install the MessageQ MVS Client:
Software Requirements
Software Requirements With LE for Batch or CICS
MessageQ MVS Client software also supports VS COBOL II batch development when used with the C/370 Library(5688-188). This is designed for installations that have not moved to IBM's Language Environment for MVS product (5688-197) and are not developing MessageQ CICS applications. The software requirements for this environment are:
Software Requirements Without LE for Batch
In addition to installing and configuring the MessageQ MVS Client, your environment must contain the following MessageQ elements:
MessageQ Server Software Requirements
To run MessageQ and its MVS Client connection, your TCP/IP network software must be installed and running. If you intend to develop client applications, you must have a program development environment that allows you to compile and link your applications on the MVS system.
Note:
You do not need to make any changes to MVS system parameters to install the MVS Client.
MessageQ MVS Client systems require approximately 100 tracks of an IBM 3390 or equivalent device to store the MessageQ MVS Client files.
The MessageQ MVS Client is distributed on CD-ROM media, using industry-standard ISO 9660 format. The media kit contains source and object libraries which will be placed in seven partitioned datasets. Table 2-1 lists the datasets contained on the MessageQ MVS Client media. Appendix A of this manual contains a description of the files in each dataset.
We strongly recommend that you read the MessageQ product release notes before installing MessageQ. The release notes contain late-breaking information about the release that may be important for you to know before installing MessageQ. The release notes file can be viewed or printed from the Installation of the MVS Client requires moving the partitioned data sets from the distribution media kit to the MVS system. This section provides step-by-step instructions for installing the MVS Client from the distribution CD-ROM.
Create an empty dataset on your target MVS system. This dataset will be used to receive a JCL file as described in Step 2.
This initial dataset ( Follow these steps to transfer the initial dataset to your MVS system using FTP:
System Resource Requirements
MVS Client Datasets
Reading Release Notes Before You Install MessageQ
/doc directory on the CD-ROM distribution media.
Installation Steps
Step 1: Create an Empty Dataset On Your MVS System
Dataset: Sequential
Dataset Name: DMQCPDS.JCL
LRECL: 80
Volume: TSOUSR ( substitute your user volume here )
RECFM: FB
BLKSIZE: 6160
SPACE: 1 TrackDMQPDS.JCL) will be used to create the partitioned datasets (PDS) required for the MVS Client installation.
Step 2: Use FTP to Copy the Initial Dataset from the CD-ROM
MVSCL/platform directory, where platform is either
UNIX or NT, depending on the system from which you are loading the
CD-ROM.
Note:
For UNIX platforms, the ";1" file extension must be removed when moving the files to the MVS system. This can be done via FTP using the " The following example illustrates how to copy this file:
ntran" command or on DUNIX, the installation CD can be mounted with the "-o nover" option which will suppress the ";1"
% ftp mvs-node-name
Connected to mvs-node-name.
Name (mvs-node-name:unix-id): tso-id
331 Send password please.
Password: tso-password
230 tso-id is logged on.
Remote system type is OS/MVS.ftp> ntran ";1" ""
ftp> put DMQCPDS.JCL "dataset name allocated in step 1"
200 Port request OK.
125 Storing data set "dataset name allocated in step 1"
2749 bytes sent in 0.00 seconds (555.12 Kbytes/s)
ftp> quit
221 Quit command received. Goodbye.
Follow these steps to create the empty partitioned datasets on the target MVS system:
DMQCPDS.JCL file and modify the JOBCARD to
your standards.
Note:
This is an instream PROC; the variables are at the end of the PROC.
HLQ" and "VOLUME" to match your installation. The HLQ
value is defaulted to DMQ.V3R2.
For example, using the HLQ=`DMQ.V3R2' the following empty datasets are created.
Upload all the files on the distribution CD-ROM to the partitioned datasets allocated by the job INSTALL in Step 3, using FTP transmission mode. The datasets are described in Table 2-1.
The following examples show the syntax for uploading the files using FTP:
Listing 2-1
% ftp mvs-node-name
Connected to mvs-node-name.
Name (beavs:tso-id):
331 Send password please.
Password: tso-password
230 tso-id is logged on.
Remote system type is OS/MVS.
ftp> prompt off
Interactive mode off.
ftp> lcd /cdrom/MVSCL/UNIX/CNTL
Local directory now /cdrom/MVSCL/UNIX/CNTL
ftp> cd 'DMQ.V3R2.CNTL' (or the HLQ designated in the DMQCPDS.JCL)
250 "'DMQ.V3R2.CNTL" partitioned data set is working directory
ftp> mput *
local: CSDU remote: CSDU
200 Port request OK.
<<< files transferred here >>>
ftp> lcd ../SRC
Local directory now /cdrom/MVSCL/UNIX/SRC
ftp> cd 'DMQ.V3R2.SRC' (or the HLQ designated in the DMQCPDS.JCL)
ftp> mput *
local: CSDU remote: CSDU
200 Port request OK.
<<< files transferred here >>>
ftp> lcd ../INCL
Local directory now /cdrom/MVSCL/UNIX/INCL
ftp> cd 'DMQ.V3R2.INCL' (or the HLQ designated in the DMQCPDS.JCL)
ftp> mput *
local: CSDU remote: CSDU
200 Port request OK.
<<< files transferred here >>>
Note: To upload the OBJECT files, set binary mode on
ftp> type image (or binary)
ftp> lcd ../MVSLIB
Local directory now /cdrom/MVSCL/UNIX/MVSLIB
ftp> cd 'DMQ.V3R2.MVSLIB' (or the HLQ designated in the DMQCPDS.JCL)
ftp> mput *
local: CSDU remote: CSDU
200 Port request OK.
<<< files transferred here >>>
ftp> lcd ../mvslib33
Local directory now /cdrom/MVSCL/UNIX/MVSLIB33
ftp> cd 'DMQ.V3R2.MVSLIB33' (or the HLQ designated in the DMQCPDS.JCL)
ftp> mput *
local: CSDU remote: CSDU
200 Port request OK.
<<< files transferred here >>>
ftp> lcd ../MVSNOLE
Local directory now /cdrom/MVSCL/UNIX/MVSNOLE
ftp> cd 'DMQ.V3R2.MVSNOLE' (or the HLQ designated in the DMQCPDS.JCL)
ftp> mput *
local: CSDU remote: CSDU
200 Port request OK.
<<< files transferred here >>>
ftp> lcd ../COBLIB
Local directory now /cdrom/MVSCL/UNIX/COBLIB
ftp> cd 'DMQ.V3R2.COBLIB' (or the HLQ designated in the DMQCPDS.JCL)
ftp> mput *
local: CSDU remote: CSDU
200 Port request OK.
<<< files transferred here >>>
quit
After you have successfully installed the MVS Client, refer to Configuring the MessageQ MVS Client in this manual for complete instructions on how to configure your MessageQ environment.