IBM

Program Directory for

WebSphere MQ Integrator for z/OS

Version 2 Release 1, Modification Level 0

Program Number 5655-G97

FMID HSI2100

for Use with

z/OS

Document Date: December 2001

GI10-2536-00
 Note!

Before using this information and the product it supports, be sure to read the general information under “Notices” on page iv.

A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM a
nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

 Copyright International Business Machines Corporation 2001. All rights reserved.

Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 WebSphere MQ Integrator for z/OS Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 WebSphere MQ Integrator for z/OS FMID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.0 Program Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.1 Basic Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Optional Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3.1 Basic Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3.2 Optional Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 Program Source Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5 Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.0 Program Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 Program Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Preventive Service Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Statement of Support Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.0 Program and Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1 Program Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2 Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5.0 Installation Requirements and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.1 Driving System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1.1 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1.2 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2 Target System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2.1 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2.2 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2.2.1 Mandatory Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2.2.2 Functional Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2.2.3 Toleration/Coexistence Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2.2.4 Incompatibility (Negative) Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2.3 DASD Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.3 FMIDs Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.4 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6.0 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6.1 Installing WebSphere MQ Integrator for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

 Copyright IBM Corp. 2001 iii

Notices

6.1.1 SMP/E Considerations for Installing WebSphere MQ Integrator for z/OS . . . . . . . . . . . . 16

6.1.2 SMP/E Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1.3 SMP/E Options Subentry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1.4 SMP/E CALLLIBS Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1.5 Sample Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1.6 Create SMP/E global zone and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1.7 Create SMP/E distribution zone and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1.8 Create SMP/E target zone and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1.9 Perform SMP/E RECEIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1.10 Allocate SMP/E Target and Distribution Libraries and Paths . . . . . . . . . . . . . . . . . . . 20
6.1.11 Create DDDEF Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1.12 Perform SMP/E APPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1.13 Perform SMP/E ACCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.2 Activating WebSphere MQ Integrator for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Appendix A. WebSphere MQ Integrator for z/OS install logic . . . . . . . . . . . . . . . . . . . . . . 23

A.1 SMP/E Modification control statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
A.2 SMP/E JCLIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Appendix B. High-level qualifiers and symbolic parameters . . . . . . . . . . . . . . . . . . . . . . 24

B.1 High-level qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
B.2 Symbolic parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Reader's Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figures
1. Basic Material: Program Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Program File Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Basic Material: Unlicensed Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Component IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Driving System Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Mandatory Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9. Functional Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
10. Total DASD Space Required by WebSphere MQ Integrator for z/OS . . . . . . . . . . . . . . . . 11
11. Storage Requirements for WebSphere MQ Integrator for z/OS Target Libraries . . . . . . . . . . 13
12. WebSphere MQ Integrator for z/OS HFS Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
13. Storage Requirements for WebSphere MQ Integrator for z/OS Distribution Libraries . . . . . . . 14
14. Storage Requirements for WebSphere MQ Integrator for z/OS Non-SMP/E Data Sets . . . . . . 15
15. SMP/E Options Subentry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

iv WebSphere MQ Integrator for z/OS Program Directory

 Trademarks

16. Sample Installation Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

17. High-level qualifiers for data set names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
18. Symbolic parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Figures v
Trademarks

Notices
References in this document to IBM products, programs, or services do not imply that IBM intends to
make these available in all countries in which IBM operates. Any reference to an IBM product, program,
or service is not intended to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual
property rights may be used instead of the IBM product, program, or service. Evaluation and verification
of operation in conjunction with other products, except those expressly designated by IBM, is the user's
responsibility.

APAR numbers are provided in this document to assist in locating PTFs that may be required. Ongoing
problem reporting may result in additional APARs being created. Therefore, the APAR lists in this
document may not be complete. To obtain current service recommendations and to identify current
product service requirements, always contact the IBM Customer Support Center or use S/390
SoftwareXcel to obtain the current "PSP Bucket".

IBM may have patents or pending patent applications covering subject matter in this document. The
furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to the

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, New York 10504-1785
USA

For online versions of this book, we authorize you to:

Copy, modify, and print the documentation contained on the media, for use within your enterprise,
provided you reproduce the copyright notice, all warning statements, and other required statements on
each copy or partial copy.

Transfer the original unaltered copy of the documentation when you transfer the related IBM product
(which may be either machines you own, or programs, if the program's license terms permit a
transfer). You must, at the same time, destroy all other copies of the documentation.

You are responsible for payment of any taxes, including personal property taxes, resulting from this
authorization.

THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply
to you.

vi  Copyright IBM Corp. 2001

 Trademarks

Your failure to comply with the terms above terminates this authorization. Upon termination, you must
destroy your machine readable documentation.

Trademarks
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:

DB2 OS/390
IBM S/390
MQSeries WebSphere
MVS z/OS

The following terms are trademarks of other companies as follows:

Windows Microsoft Corporation
Windows NT Microsoft Corporation
Java Sun Microsystems, Inc.
UNIX The Open Group

Notices vii
Trademarks

viii WebSphere MQ Integrator for z/OS Program Directory

 Introduction

1.0 Introduction
This program directory is intended for the system programmer responsible for program installation and
maintenance. It contains information concerning the material and procedures associated with the
installation of WebSphere MQ Integrator for z/OS. This publication refers to WebSphere MQ Integrator for
z/OS as WebSphere MQ Integrator for z/OS. You should read all of this program directory before
installing the program and then keep it for future reference.

The program directory contains the following sections:

2.0, “Program Materials” on page 3 identifies the basic and optional program materials and
documentation for WebSphere MQ Integrator for z/OS.

3.0, “Program Support” on page 7 describes the IBM support available for WebSphere MQ Integrator
for z/OS.

4.0, “Program and Service Level Information” on page 8 lists the APARs (program level) and PTFs
(service level) incorporated into WebSphere MQ Integrator for z/OS.

5.0, “Installation Requirements and Considerations” on page 9 identifies the resources and
considerations for installing and using WebSphere MQ Integrator for z/OS.

6.0, “Installation Instructions” on page 16 provides detailed installation instructions for WebSphere MQ
Integrator for z/OS. It also describes the procedures for activating the functions of WebSphere MQ
Integrator for z/OS, or refers to appropriate publications.

Appendix A, “WebSphere MQ Integrator for z/OS install logic” on page 23 provides the install logic for
WebSphere MQ Integrator for z/OS.

Appendix B, “High-level qualifiers and symbolic parameters” on page 24 provides information about
high-level qualifiers and symbolic parameters, including example values.

Before installing WebSphere MQ Integrator for z/OS, read 3.2, “Preventive Service Planning” on page 7.
This section tells you how to find any updates to the information and procedures in this program directory.

Do not use this program directory if you are installing WebSphere MQ Integrator for z/OS with a
SystemPac or ServerPac. When using these offerings, use the jobs and documentation supplied with the
offering. This documentation may point you to specific sections of the program directory as required.

If you are installing WebSphere MQ Integrator for z/OS using the Custom-Built Product Delivery Offering
(CBPDO, 5751-CS3), a softcopy program directory is provided on the CBPDO tape which is identical to
the printed copy shipped with your order. Your CBPDO contains a softcopy preventive service planning
(PSP) upgrade for this product. All service and HOLDDATA for WebSphere MQ Integrator for z/OS are
included on the CBPDO tape.

 Copyright IBM Corp. 2001 1

WebSphere MQ Integrator for z/OS FMID

1.1 WebSphere MQ Integrator for z/OS Description

IBM WebSphere MQ Integrator for z/OS V2.1 extends the availability of Version 2 broker support to the
z/OS platform. WebSphere MQ Integrator for z/OS V2.1 consists of an application layer that maintains full
message capability with the implementations on other platforms and a system layer that provides the
implementation for z/OS. With this release, the Broker and User Name Server are being made available
on z/OS; the Configuration Manager and Control Center remain available only on Windows NT and
Windows 2000.

z/OS-specific features include:

SMP/E install

Service using PTFs

Automatic restart management

Messages written to the operator console

Operation support using console interface

Enhanced serviceability through FFDC, ESTAEs, SVCDUMPs and SYSMDUMPs

1.2 WebSphere MQ Integrator for z/OS FMID

WebSphere MQ Integrator for z/OS consists of the following FMID:
HSI2100

2 WebSphere MQ Integrator for z/OS Program Directory

 Basic Machine-Readable Material

2.0 Program Materials

An IBM program is identified by a program number and a feature number. The program number for
WebSphere MQ Integrator for z/OS is 5655-G97.

Basic Machine-Readable Materials are materials that are supplied under the base license and feature
code, and are required for the use of the product. Optional Machine-Readable Materials are orderable
under separate feature codes, and are not required for the product to function.

The program announcement material describes the features supported by WebSphere MQ Integrator for
z/OS. Ask your IBM representative for this information if you have not already received a copy.

2.1 Basic Machine-Readable Material

The distribution medium for this program is magnetic tape or downloadable files. It is installed using
SMP/E, and is in SMP/E RELFILE format. See 6.0, “Installation Instructions” on page 16 for more
information about how to install the program.

Figure 1 describes the physical tape. Figure 2 describes the file content.
Notes:
1. The data set attributes in these tables should be used in the JCL of jobs reading the data sets, but
since the data sets are in IEBCOPY unloaded format, their actual attributes may be different.
2. If you are installing WebSphere MQ Integrator for z/OS using the Custom-Built Product Delivery
Offering (CBPDO) (5751-CS3), some of the information in these figures may not be valid. Consult the
CBPDO documentation for actual values.
3. If any RELFILEs are identified as PDSEs, ensure that SMPTLIB data sets are allocated as PDSEs.

Figure 1. Basic Material: Program Tape

Physical
Medium Feature Number Volume External Label R/M * VOLSER
3480 cart. 5802 1 WMQI for z/OS V2.1 N SI210A
3480 cart. 5802 2 WMQI for z/OS V2.1 N SI210B
3480 cart. 5822 1 WMQI for z/OS V2.1 N SI210A
3480 cart. 5822 2 WMQI for z/OS V2.1 N SI210B

* R/M = Restricted Materials of IBM

 Copyright IBM Corp. 2001 3

Optional Machine-Readable Material

Figure 2. Program File Content

R L
E R
O C E
R F C BLK
Name G M L SIZE
SMPMCS PS FB 80 N/A
IBM.HSI2100.F1 PDS FB 80 800
IBM.HSI2100.F2 PDS FB 80 800
IBM.HSI2100.F3 PDS VB 32000 800
IBM.HSI2100.F4 PDS VB 32000 800
IBM.HSI2100.F5 PDS VB 32000 800
IBM.HSI2100.F6 PDS VB 32000 800
IBM.HSI2100.F7 PDS VB 32000 800
IBM.HSI2100.F8 PDS VB 32000 800
IBM.HSI2100.F9 PDS VB 32000 800
IBM.HSI2100.F10 PDS VB 32000 800
IBM.HSI2100.F11 PDS VB 32000 800
IBM.HSI2100.F12 PDS VB 32000 800
IBM.HSI2100.F13 PDS VB 32000 800
IBM.HSI2100.F14 PDS VB 32000 800
IBM.HSI2100.F15 PDS VB 32000 800
IBM.HSI2100.F16 PDS VB 32000 800
IBM.HSI2100.F17 PDS VB 32000 800
IBM.HSI2100.F18 PDS VB 32000 800
IBM.HSI2100.F19 PDS VB 32000 800
IBM.HSI2100.F20 PDS VB 32000 800
IBM.HSI2100.F21 PDS VB 32000 800
IBM.HSI2100.F22 PDSE U 0 PDSE

2.2 Optional Machine-Readable Material

No optional machine-readable materials are provided for WebSphere MQ Integrator for z/OS.

4 WebSphere MQ Integrator for z/OS Program Directory

 Publications Useful During Installation

2.3 Program Publications

The following sections identify the basic and optional publications for WebSphere MQ Integrator for z/OS.

2.3.1 Basic Program Publications

Figure 3 identifies the basic unlicensed program publications for WebSphere MQ Integrator for z/OS. One
copy of each of these publications is included when you order the basic materials for WebSphere MQ
Integrator for z/OS. For additional copies, contact your IBM representative.

Figure 3. Basic Material: Unlicensed Publications

Form
Publication Title Number
WebSphere MQ Integrator Administration Guide SC34-5792
WebSphere MQ Integrator ESQL Reference SC34-5923
WebSphere MQ Integrator Introduction and Planning GC34-5599
WebSphere MQ Integrator Problem Determination Guide GC34-5920
WebSphere MQ Integrator Programming Guide SC34-5603
WebSphere MQ Integrator Using the Control Center GC34-5602
WebSphere MQ Integrator Working with Messages SC34-6039
WebSphere MQ Integrator for z/OS Customization and Administration Guide SC34-5919

2.3.2 Optional Program Publications

No optional publications are provided for WebSphere MQ Integrator for z/OS.

2.4 Program Source Materials

No program source materials or viewable program listings are provided for WebSphere MQ Integrator for
z/OS.

2.5 Publications Useful During Installation

The publications listed in Figure 4 may be useful during the installation of WebSphere MQ Integrator for
z/OS. To order copies, contact your IBM representative or visit the IBM Publications Center at
http://www.elink.ibmlink.ibm.com/applications/public/applications/publications/cgibin/pbi.cgi on the Internet.

Program Materials 5
Publications Useful During Installation

Figure 4. Publications Useful During Installation

Form
Publication Title Number
IBM SMP/E for z/OS and OS/390 Commands SA22-7771
IBM SMP/E for z/OS and OS/390 Messages, Codes, and Diagnosis GA22-7770
IBM SMP/E for z/OS and OS/390 Reference SA22-7772
IBM SMP/E for z/OS and OS/390 User's Guide SA22-7773
OS/390 SMP/E Commands SC28-1805
OS/390 SMP/E Messages and Codes SC28-1738
OS/390 SMP/E Reference SC28-1806
OS/390 SMP/E User's Guide SC28-1740
OS/390 UNIX System Services Command Reference SC28-1892
OS/390 UNIX System Services User's Guide SC28-1891
z/OS MVS Initialization and Tuning Reference SA22-7592
z/OS MVS JCL Reference SA22-7597
z/OS UNIX System Services Command Reference SA22-7802
z/OS UNIX System Services User's Guide SA22-7801

6 WebSphere MQ Integrator for z/OS Program Directory

 Statement of Support Procedures

3.0 Program Support

This section describes the IBM support available for WebSphere MQ Integrator for z/OS.

3.1 Program Services

Contact your IBM representative for specific information about available program services.

3.2 Preventive Service Planning

Before installing WebSphere MQ Integrator for z/OS, you should review the current Preventive Service
Planning (PSP) information. If you obtained WebSphere MQ Integrator for z/OS as part of a CBPDO,
there is HOLDDATA and PSP information included on the CBPDO.

If you obtained WebSphere MQ Integrator for z/OS on a product tape, or if the CBPDO is more than two
weeks old when you install it, you should contact the IBM Support Center or use S/390 SoftwareXcel to
obtain the current "PSP Bucket".

For access to RETAIN, visit http://webspinner.boulder.ibm.com/retain on the Internet.

PSP Buckets are identified by UPGRADEs, which specify product levels, and SUBSETs, which specify the
FMIDs for a product level. The UPGRADE and SUBSET values for WebSphere MQ Integrator for z/OS
are:

Figure 5. PSP Upgrade and Subset ID

UPGRADE SUBSET Description
MQMINT HSI2100 WebSphere MQ Integrator for z/OS Base function

3.3 Statement of Support Procedures

Report any difficulties you have using this program to your IBM Support Center. If an APAR is required,
the Support Center will provide the address to which any needed documentation can be sent.

Figure 6 identifies the component IDs (COMPID) for WebSphere MQ Integrator for z/OS.

Figure 6. Component IDs

RETAIN
FMID COMPID Component Name Release
HSI2100 5655G9700 WebSphere MQ Integrator for z/OS Base function 100

 Copyright IBM Corp. 2001 7

Service Level Information

4.0 Program and Service Level Information

This section identifies the program and any relevant service levels of WebSphere MQ Integrator for z/OS.
The program level refers to the APAR fixes incorporated into the program. The service level refers to the
PTFs integrated.

4.1 Program Level Information

No APARs have been incorporated into WebSphere MQ Integrator for z/OS.

4.2 Service Level Information

No PTFs against this release of WebSphere MQ Integrator for z/OS have been incorporated into the
product tape.

8  Copyright IBM Corp. 2001

 Driving System Requirements

5.0 Installation Requirements and Considerations

The following sections identify the system requirements for installing and activating WebSphere MQ
Integrator for z/OS. The following terminology is used:

Driving system: the system used to install the program.

Target system: the system on which the program is installed.

In many cases, the same system can be used as both a driving system and a target system. However,
you may want to set up a clone of your system to use as a target system by making a separate IPL-able
copy of the running system. The clone should include copies of all system libraries that SMP/E updates,
copies of the SMP/E CSI data sets that describe the system libraries, and your PARMLIB and PROCLIB.

Some cases where two systems should be used include the following:

When installing a new level of a product that is already installed, the new product will delete the old
one. By installing onto a separate target system, you can test the new product while still keeping the
old one in production.

When installing a product that shares libraries or load modules with other products, the installation can
disrupt the other products. Installing onto a test system or clone will allow you to assess these
impacts without disrupting your production system.

5.1 Driving System Requirements

This section describes the environment of the driving system required to install WebSphere MQ Integrator
for z/OS.

5.1.1 Machine Requirements

The driving system can run in any hardware environment that supports the required software.

5.1.2 Programming Requirements

Figure 7. Driving System Software Requirements
Program Product Name and
Number Minimum VRM/Service Level
Any one of the following:
5647-A01 OS/390 SMP/E Version 2 Release 8 or higher
5694-A01 z/OS Version 1 Release 1 or higher
5655-G44 IBM SMP/E for z/OS and OS/390 Version 3 Release 1 or higher

 Copyright IBM Corp. 2001 9

Target System Requirements

5.2 Target System Requirements

This section describes the environment of the target system required to install and use WebSphere MQ
Integrator for z/OS.

WebSphere MQ Integrator for z/OS installs in the MVS (Z038) SREL.

5.2.1 Machine Requirements

The target system can run in any hardware environment that supports the required software.

5.2.2 Programming Requirements

5.2.2.1 Mandatory Requisites
A mandatory requisite is defined as a product that is required without exception; this product either will
not install or will not function unless this requisite is met. This includes products that are specified as
REQs or PREs.

Figure 8. Mandatory Requisites

Program Product Name and
Number Minimum VRM/Service Level
5655-D35 IBM Developer Kit for OS/390, Java2 Technology Edition, Version 1 Release 3 Modification
0 with Service Refresh 9 and PTF UQ56153
5655-F10 MQSeries for OS/390 Version 5 Release 2 with PTFs: UQ52024, UQ54733, UQ55903,
UQ56617
5647-A01 OS/390 Version 2 Release 8 plus HFS PTFs: UW70296, UW77040
RRS must be started and running on PTFs: UW72071, UW72074, UW73227, UW76234,
UW81347.
USS must be at level 2.8
Any one of the following:
5655-DB2 IBM DB2 UDB for OS/390 Version 6 at RSU0107 and PUT0107, plus APARs: PQ45812,
PQ53087 and PTFs: UQ38867, UQ56465.
5675-DB2 IBM DB2 UDB for OS/390 Version 7 Release 1 at RSU0107 and PUT0107, plus APARs:
PQ53087, PQ45812 and PTF: UQ56466

5.2.2.2 Functional Requisites

A functional requisite is defined as a product that is not required for the successful installation of this
product or for the basic function of the product, but is needed at run time for a specific function of this
product to work. This includes products that are specified as IF REQs.

10 WebSphere MQ Integrator for z/OS Program Directory

 Target System Requirements

Figure 9. Functional Requisites

Program Product Name and
Number Minimum VRM/Service Level Function
5647-A01 IBM OS/390 C/C++ C applications

5.2.2.3 Toleration/Coexistence Requisites

A toleration/coexistence requisite is defined as a product which must be present on a sharing system.
These systems can be other systems in a multisystem environment (not necessarily sysplex), a shared
DASD environment (such as test and production), or systems that reuse the same DASD at different time
intervals.

WebSphere MQ Integrator for z/OS has no toleration/coexistence requisites.

5.2.2.4 Incompatibility (Negative) Requisites

A negative requisite identifies products which must not be installed on the same system as this product.

WebSphere MQ Integrator for z/OS has no negative requisites.

5.2.3 DASD Storage Requirements

WebSphere MQ Integrator for z/OS libraries can reside on all supported DASD types.

Figure 10 lists the total space required for each type of library.

Figure 10. Total DASD Space Required by WebSphere MQ Integrator for z/OS
Library
Type Total Space Required
Target 5 tracks
Distribution 1219 tracks
HFS 200 MB

Notes:
1. IBM recommends use of system determined block sizes for efficient DASD utilization for all
non-RECFM U data sets. For RECFM U data sets, IBM recommends a block size of 32760, which is
the most efficient from a performance and DASD utilization perspective.
2. Abbreviations used for the data set type are:
U Unique data set, allocated by this product and used only by this product. To determine the
correct storage needed for this data set, this table provides all required information; no other
tables (or program directories) need to be referenced for the data set size.

Installation Requirements and Considerations 11

Target System Requirements

S Shared data set, allocated by this product and used by this product and others. To determine
the correct storage needed for this data set, the storage size given in this table needs to be
added to other tables (perhaps in other program directories). If the data set already exists, it
must have enough free space to accommodate the storage size given in this table.
E Existing shared data set, used by this product and others. This data set is NOT allocated by
this product. To determine the correct storage needed for this data set, the storage size given
in this table needs to be added to other tables (perhaps in other program directories). This
existing data set must have enough free space to accommodate the storage size given in this
table.
If you currently have a previous release of this product installed in these libraries, the installation of
this release will delete the old one and reclaim the space used by the old release and any service that
had been installed. You can determine whether or not these libraries have enough space by deleting
the old release with a dummy function, compressing the libraries, and comparing the space
requirements with the free space in the libraries.
For more information on the names and sizes of the required data sets, please refer to 6.1.10,
“Allocate SMP/E Target and Distribution Libraries and Paths” on page 20.
3. Abbreviations used for the HFS Path type are:
N New path, created by this product.
X Path created by this product, but may already exist from a previous release.
P Previously existing path, created by another product.
4. All target and distribution libraries listed have the following attributes:

The default name of the data set may be changed

The default block size of the data set may be changed

The data set may be merged with another data set that has equivalent characteristics

The data set may be either a PDS or a PDSE
5. All target libraries listed have the following attributes:

The data set may be SMS managed

It is not required for the data set to be SMS managed

It is not required for the data set to reside on the IPL volume

The values in the "Member Type" column are not necessarily the actual SMP/E element types
identified in the SMPMCS.
6. All target libraries listed which contain load modules have the following attributes:

The data set may be in the LPA

It is not required for the data set to be in the LPA

The data set may be in the LNKLST

It is not required for the data set to be APF authorized

The following figures describe the target and distribution libraries and HFS paths required to install
WebSphere MQ Integrator for z/OS. The storage requirements of WebSphere MQ Integrator for z/OS
must be added to the storage required by other programs having data in the same library or path.

12 WebSphere MQ Integrator for z/OS Program Directory

 Target System Requirements

Note: The data in these tables should be used when determining which libraries can be merged into
common data sets. In addition, since some ALIAS names may not be unique, ensure that no naming
conflicts will be introduced before merging libraries.

Figure 11. Storage Requirements for WebSphere MQ Integrator for z/OS Target Libraries
R L
T E R No. No.
Y O C E of of
Library Member Target P R F C 3390 DIR
DDNAME Type Volume E G M L Trks Blks
SBIPINST Sample ANY U PDS FB 80 5 3

Figure 12 (Page 1 of 2). WebSphere MQ Integrator for z/OS HFS Paths

T
Y
P
DDNAME E Path Name
SBIPOBIN N /usr/lpp/wmqi/bin/IBM/
SBIPOCLS N /usr/lpp/wmqi/classes/IBM/
SBIPOINC N /usr/lpp/wmqi/include/IBM/
SBIPOIPL N /usr/lpp/wmqi/include/plugin/IBM/
SBIPOLIB N /usr/lpp/wmqi/lib/IBM/
SBIPOLIL N /usr/lpp/wmqi/lil/IBM/
SBIPOMSG N /usr/lpp/wmqi/messages/IBM/
SBIPOMEN N /usr/lpp/wmqi/messages/En_US/IBM/
SBIPOMJA N /usr/lpp/wmqi/messages/Ja_JP/IBM/
SBIPOMZH N /usr/lpp/wmqi/messages/Zh_CN/IBM/
SBIPOSMP N /usr/lpp/wmqi/sample/JavaPlugin/com/ibm/samples/IBM/
SBIPOSPL N /usr/lpp/wmqi/sample/plugin/IBM/
SBIPOSCL N /usr/lpp/wmqi/sample/scribble/classes/IBM/
SBIPOTCN N /usr/lpp/wmqi/template/cntl/IBM/
SBIPOTDT N /usr/lpp/wmqi/template/data/IBM/
SBIPOTPR N /usr/lpp/wmqi/template/proc/IBM/
SBIPOTRE N /usr/lpp/wmqi/template/rexx/IBM/
SBIPOTSH N /usr/lpp/wmqi/template/shell/IBM/
SBIPDJAP N /usr/lpp/wmqi/docs/JavaAPI/IBM/
SBIPDPLG N /usr/lpp/wmqi/docs/JavaAPI/com/ibm/broker/plugin/IBM/

Installation Requirements and Considerations 13

Target System Requirements

Figure 12 (Page 2 of 2). WebSphere MQ Integrator for z/OS HFS Paths

T
Y
P
DDNAME E Path Name
SBIPDFIL N /usr/lpp/wmqi/docs/JavaAPI/com/ibm/broker/plugin/doc-files/IBM/

Figure 13. Storage Requirements for WebSphere MQ Integrator for z/OS Distribution Libraries
R L
T E R No. No.
Y O C E of of
Library P R F C 3390 DIR
DDNAME E G M L Trks Blks
ABIPOFLT U PDS VB 32000 2 3
ABIPOWDP U PDS VB 32000 2 3
ABIPOP U PDSE U 0 N/A PDSE
ABIPOJCL U PDS VB 32000 3 3
ABIPOGIF U PDS VB 32000 6 3
ABIPOREX U PDS FB 80 13 3
ABIPOJAR U PDS VB 32000 431 3
ABIPOH U PDS VB 32000 8 3
ABIPOJAV U PDS VB 32000 7 3
ABIPOSO U PDS VB 32000 420 3
ABIPODAT U PDS VB 32000 7 3
ABIPINST U PDS FB 80 5 3
ABIPOSH U PDS VB 32000 4 3
ABIPOXML U PDS VB 32000 6 3
ABIPOAWK U PDS VB 32000 6 3
ABIPOC U PDS VB 32000 8 3
ABIPOCAT U PDS VB 32000 70 3
ABIPOPRO U PDS VB 32000 176 3
ABIPOX U PDS VB 32000 17 3
ABIPOCSS U PDS VB 32000 6 3
ABIPOHTM U PDS VB 32000 21 3

The following figures list data sets that are not used by SMP/E, but are required for WebSphere MQ
Integrator for z/OS to execute.

14 WebSphere MQ Integrator for z/OS Program Directory

 Special Considerations

Figure 14. Storage Requirements for WebSphere MQ Integrator for z/OS Non-SMP/E Data Sets
R L
T E R No. No.
Y O C E of of
Data Set P R F C 3390 DIR
Name E G M L Trks Blks
UBIPINST U PO FB 80 15 20

5.3 FMIDs Deleted

Installing WebSphere MQ Integrator for z/OS may result in the deletion of other FMIDs. To see what
FMIDs will be deleted, examine the ++VER statement in the product's SMPMCS.

If you do not wish to delete these FMIDs at this time, you must install WebSphere MQ Integrator for z/OS
into separate SMP/E target and distribution zones.
Note: These FMIDs will not automatically be deleted from the Global Zone. Consult the SMP/E manuals
for instructions on how to do this.

5.4 Special Considerations

SYSLOGD, which is part of IBM's TCP/IP, needs to be configured and running for informational messages
to be filtered out of the System console.

Installation Requirements and Considerations 15

Installing WebSphere MQ Integrator for z/OS

6.0 Installation Instructions

This chapter describes the installation method and the step-by-step procedures to install and to activate
the functions of WebSphere MQ Integrator for z/OS.

Please note the following:

If you want to install WebSphere MQ Integrator for z/OS into its own SMP/E environment, consult the
SMP/E manuals for instructions on creating and initializing the SMPCSI and the SMP/E control data
sets.

Sample jobs have been provided to help perform some or all of the installation tasks. The SMP/E jobs
assume that all DDDEF entries required for SMP/E execution have been defined in the appropriate
zones.

The SMP/E dialogs may be used instead of the sample jobs to accomplish the SMP/E installation
steps.

6.1 Installing WebSphere MQ Integrator for z/OS

For details of high-level qualifiers and symbolic parameters, including example values, see Appendix B,
“High-level qualifiers and symbolic parameters” on page 24.

6.1.1 SMP/E Considerations for Installing WebSphere MQ Integrator

for z/OS
This release of WebSphere MQ Integrator for z/OS is installed using the SMP/E RECEIVE, APPLY, and
ACCEPT commands. The SMP/E dialogs may be used to accomplish the SMP/E installation steps.

6.1.2 SMP/E Environment

You must decide whether to install WebSphere MQ Integrator for z/OS into a new or an existing SMP/E
environment. Remember that installing a new release of WebSphere MQ Integrator for z/OS into the
same SMP/E zones as an existing release will cause the earlier level to be deleted from both the SMP/E
zones and the existing release data sets.

If you are going to install into the same SMP/E zones, then to preserve your current release while you
install and test the new release you should copy the existing release data sets into data sets with different
names. Do not rename or delete the current data sets because they need to be available to SMP/E for
delete processing during the installation of the new release. If they are not available, the APPLY and
ACCEPT steps will fail with a return code of 12. After running a successful ACCEPT of the WebSphere
MQ Integrator for z/OS products, the previous release data sets are no longer required and can be deleted
when testing of the new release has been completed.

16  Copyright IBM Corp. 2001

 Installing WebSphere MQ Integrator for z/OS

If you use existing SMP/E data sets, you need to know the names of your target zone and distribution
zone, and the data set name of your global CSI.

You must decide upon the names for the SMP/E zones.

6.1.3 SMP/E Options Subentry Values

The recommended values for some SMP/E CSI subentries are shown in Figure 15. Use of values lower
than these may result in failures in the installation process. DSSPACE is a subentry in the GLOBAL
options entry. PEMAX is a subentry of the GENERAL entry in the GLOBAL options entry. Refer to the
SMP/E manuals for instructions on updating the global zone.

Figure 15. SMP/E Options Subentry Values

SUB-ENTRY Value Comment
DSSPACE (1000,1000,800) These are the minimum required values.
PEMAX SMP/E Default IBM recommends using the SMP/E default for PEMAX.

6.1.4 SMP/E CALLLIBS Processing

WebSphere MQ Integrator for z/OS uses the CALLLIBS function provided in SMP/E to resolve external
references during installation. When WebSphere MQ Integrator for z/OS is installed, ensure that DDDEFs
exist for the following libraries:

CSSLIB

SCSQLOAD

SCEELKED
Note: The DDDEFs above are used only to resolve the link-edit for WebSphere MQ Integrator for z/OS
using CALLLIBS. These data sets are not updated during the installation of WebSphere MQ Integrator for
z/OS.

6.1.5 Sample Jobs

The following sample installation jobs are provided as part of the product to help you install WebSphere
MQ Integrator for z/OS:

Figure 16 (Page 1 of 2). Sample Installation Jobs

Job Name Job Type Description RELFILE
BIP8RECV RECEIVE Sample RECEIVE job IBM.HSI2100.F2
BIP8ALOE ALLOCATE Sample job to allocate target and distribution IBM.HSI2100.F2
libraries
BIP8MKDJ MKDIR Sample job to invoke the supplied BIP8MKDR IBM.HSI2100.F2
EXEC to allocate HFS paths

Installation Instructions 17
Installing WebSphere MQ Integrator for z/OS

Figure 16 (Page 2 of 2). Sample Installation Jobs

Job Name Job Type Description RELFILE
BIP8DDDF DDDEF Sample job to define SMP/E DDDEFs IBM.HSI2100.F2
BIP8APLY APPLY Sample APPLY job IBM.HSI2100.F2
BIP8ACPT ACCEPT Sample ACCEPT job IBM.HSI2100.F2
BIP8DZON DZONE Optional sample job to set up an SMP/E distribution IBM.HSI2100.F2
zone and definitions
BIP8GZON GZONE Optional sample job to set up an SMP/E global IBM.HSI2100.F2
zone and definitions
BIP8TZON TZONE Optional sample job to set up an SMP/E target IBM.HSI2100.F2
zone and definitions

You may copy the jobs from the tape or product files by submitting the job below. Use either the
//TAPEIN or the //FILEIN DD statement, depending on your distribution medium, and comment out or
delete the other statement. Add a job card and change the lowercase parameters to uppercase values to
meet your site's requirements before submitting.
//STEP1 EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=
//TAPEIN DD DSN=IBM.HSI21.F2,UNIT=tunit,VOL=SER=SI21A,
// LABEL=(3,SL),DISP=(OLD,KEEP)
//FILEIN DD DSN=IBM.HSI21.F2,UNIT=SYSALLDA,DISP=SHR,
// VOL=SER=filevol
//OUT DD DSNAME=jcl-library-name,
// DISP=(NEW,CATLG,DELETE),
// VOL=SER=dasdvol,UNIT=SYSALLDA,
// SPACE=(TRK,(2,1,1))
//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSIN DD 
COPY INDD=xxxxIN,OUTDD=OUT
/
where tunit is the unit value matching the product tape, filevol is the volume serial of the DASD device
where the downloaded files reside, jcl-library-name is the name of the output data set where the sample
jobs will be stored, dasdvol is the volume serial of the DASD device where the output data set will reside
and xxxxIN on the SYSIN DD to either TAPEIN or FILEIN depending on your input DD statement.

You can also access the sample installation jobs by performing an SMP/E RECEIVE and then copying the
jobs from the SMPTLIBs to a work data set for editing and submission. See Figure 16 on page 17 to find
the appropriate SMPTLIB data set.

18 WebSphere MQ Integrator for z/OS Program Directory

 Installing WebSphere MQ Integrator for z/OS

6.1.6 Create SMP/E global zone and definitions

Edit and submit sample job BIP8GZON to create an SMP/E global zone and definitions. Consult the
instructions in the sample job for more information. See Appendix B, “High-level qualifiers and symbolic
parameters” on page 24 for details of high-level qualifiers and symbolic parameters.
Note: You must run this job if you are installing into a new zone.

Expected Return Codes and Messages: 0

6.1.7 Create SMP/E distribution zone and definitions

Edit and submit sample job BIP8DZON to create an SMP/E distribution zone and definitions. Consult the
instructions in the sample job for more information. See Appendix B, “High-level qualifiers and symbolic
parameters” on page 24 for details of high-level qualifiers and symbolic parameters.
Note: You must run this job if you are installing into a new zone.

Expected Return Codes and Messages: 0

6.1.8 Create SMP/E target zone and definitions

Edit and submit sample job BIP8TZON to create an SMP/E target zone and definitions. Consult the
instructions in the sample job for more information. See Appendix B, “High-level qualifiers and symbolic
parameters” on page 24 for details of high-level qualifiers and symbolic parameters.
Note: You must run this job if you are installing into a new zone.

Expected Return Codes and Messages: 0

6.1.9 Perform SMP/E RECEIVE

Edit and submit sample job BIP8RECV to perform the SMP/E RECEIVE for WebSphere MQ Integrator for
z/OS. Consult the instructions in the sample job for more information. See Appendix B, “High-level
qualifiers and symbolic parameters” on page 24 for details of high-level qualifiers and symbolic
parameters.

NOTE: If you obtained WebSphere MQ Integrator for z/OS as part of a CBPDO, you can use the
RCVPDO job found in the CBPDO RIMLIB data set to RECEIVE the WebSphere MQ Integrator for z/OS
FMIDs as well as any service, HOLDDATA, or preventive service planning (PSP) information included on
the CBPDO tape. For more information, refer to the documentation included with the CBPDO.

Expected Return Codes and Messages: 0

GIM2271I RECEIVE PROCESSING WAS SUCCESSFUL FOR SYSMOD HSI21

Installation Instructions 19
Installing WebSphere MQ Integrator for z/OS

6.1.10 Allocate SMP/E Target and Distribution Libraries and Paths

Edit and submit sample job BIP8ALOE to allocate the SMP/E target and distribution libraries for
WebSphere MQ Integrator for z/OS. Consult the instructions in the sample job for more information. See
Appendix B, “High-level qualifiers and symbolic parameters” on page 24 for details of high-level qualifiers
and symbolic parameters.

Expected Return Codes and Messages: 0

Edit and submit sample job BIP8MKDJ to allocate the HFS paths for WebSphere MQ Integrator for z/OS.
Consult the instructions in the sample job for more information. See Appendix B, “High-level qualifiers
and symbolic parameters” on page 24 for details of high-level qualifiers and symbolic parameters.

If you plan to create a new HFS for this product, you should consider updating the BPXPRMxx PARMLIB
member to mount the new HFS at IPL time. This may be helpful if an IPL occurs before the installation is
complete.

Expected Return Codes and Messages: 0

6.1.11 Create DDDEF Entries

Edit and submit sample job BIP8DDDF to create DDDEF entries for the SMP/E target and distribution
libraries for WebSphere MQ Integrator for z/OS. Consult the instructions in the sample job for more
information. See Appendix B, “High-level qualifiers and symbolic parameters” on page 24 for details of
high-level qualifiers and symbolic parameters.

Expected Return Codes and Messages: 0

Note: This job should complete with a return code of 0. If you are installing into existing zones, this job
might give a return code of 8, because it attempts to add DDDEFS that might already exist.

6.1.12 Perform SMP/E APPLY

Edit and submit sample job BIP8APLY to perform an SMP/E APPLY CHECK for WebSphere MQ
Integrator for z/OS. Consult the instructions in the sample job for more information. See Appendix B,
“High-level qualifiers and symbolic parameters” on page 24 for details of high-level qualifiers and symbolic
parameters.

To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the following
on the APPLY CHECK: PRE, ID, REQ, and IFREQ. This is because the SMP/E root cause analysis
identifies the cause only of ERRORS and not of WARNINGS (SYSMODs that are bypassed are treated
as warnings, not errors, by SMP/E).

Once you have taken any actions indicated by the APPLY CHECK, remove the CHECK operand and run
the job again to perform the APPLY.

20 WebSphere MQ Integrator for z/OS Program Directory

 Installing WebSphere MQ Integrator for z/OS

Note: The GROUPEXTEND operand indicates that SMP/E apply all requisite SYSMODs. The requisite
SYSMODS might be applicable to other functions.

Expected Return Codes and Messages from APPLY CHECK: 0

GIM251I APPLY PROCESSING IS COMPLETE.

THE HIGHEST RETURN CODE WAS .

Expected Return Codes and Messages from APPLY: 0

GIM2271I APPLY PROCESSING WAS SUCCESSFUL FOR SYSMOD HSI21

6.1.13 Perform SMP/E ACCEPT

Edit and submit sample job BIP8ACPT to perform an SMP/E ACCEPT CHECK for WebSphere MQ
Integrator for z/OS. Consult the instructions in the sample job for more information. See Appendix B,
“High-level qualifiers and symbolic parameters” on page 24 for details of high-level qualifiers and symbolic
parameters.

To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the following
on the ACCEPT CHECK: PRE, ID, REQ, and IFREQ. This is because the SMP/E root cause analysis
identifies the cause only of ERRORS and not of WARNINGS (SYSMODs that are bypassed are treated
as warnings, not errors, by SMP/E).

Before using SMP/E to load new distribution libraries, it is recommended that you set the ACCJCLIN
indicator in the distribution zone. This will cause entries produced from JCLIN to be saved in the
distribution zone whenever a SYSMOD containing inline JCLIN is ACCEPTed. For more information on
the ACCJCLIN indicator, see the description of inline JCLIN in the SMP/E manuals.

Once you have taken any actions indicated by the ACCEPT CHECK, remove the CHECK operand and
run the job again to perform the ACCEPT.
Note: The GROUPEXTEND operand indicates that SMP/E accept all requisite SYSMODs. The requisite
SYSMODS might be applicable to other functions.

Expected Return Codes and Messages from ACCEPT CHECK: 0

GIM251I ACCEPT PROCESSING IS COMPLETE.

THE HIGHEST RETURN CODE WAS .

Expected Return Codes and Messages from ACCEPT: 0

Installation Instructions 21
Activating WebSphere MQ Integrator for z/OS

GIM2271I ACCEPT PROCESSING WAS SUCCESSFUL FOR SYSMOD HSI21

If PTFs containing replacement modules are being ACCEPTed, SMP/E ACCEPT processing will
linkedit/bind the modules into the distribution libraries. During this processing, the Linkage Editor or Binder
may issue messages documenting unresolved external references, resulting in a return code of 4 from the
ACCEPT step. These messages can be ignored, because the distribution libraries are not executable and
the unresolved external references will not affect the executable system libraries.

6.2 Activating WebSphere MQ Integrator for z/OS

The publication WebSphere MQ Integrator for z/OS Customization and Administration Guide, SC34-5919
contains the step-by-step procedures to activate the functions of WebSphere MQ Integrator for z/OS.

22 WebSphere MQ Integrator for z/OS Program Directory

 SMP/E JCLIN

Appendix A. WebSphere MQ Integrator for z/OS install logic

A.1 SMP/E Modification control statements

The SMP/E Modification Control Statements (SMPMCS) for WebSphere MQ Integrator for z/OS are
contained in the SMPMCS file on the installation tape. The SMPMCS for each FMID in the product will be
loaded to the SMPPTS data set, with a member name matching the FMID, when the FMID is SMP/E
RECEIVEd. You may browse or print these members using TSO/E, ISPF, or IEBGENER (or IEBPTPCH).

A.2 SMP/E JCLIN

The JCLIN for WebSphere MQ Integrator for z/OS is contained in the RELFILEs on the installation tape.
These files will be loaded to disk by SMP/E when the product is SMP/E RECEIVEd. You may browse or
print these files using TSO/E, ISPF, or IEBGENER (or IEBPTPCH).

The file containing JCLIN is:

FMID HSI2100: 'high-level-qualifier'.HSI2100.F1(HSI2100)
Note: 'high-level-qualifier' is the qualifier specified as the DSPREFIX in the SMP/E OPTIONS.

 Copyright IBM Corp. 2001 23

Symbolic parameters

Appendix B. High-level qualifiers and symbolic parameters

B.1 High-level qualifiers

Use Figure 17 to plan the high-level qualifiers for the WebSphere MQ Integrator for z/OS data sets.

Figure 17. High-level qualifiers for data set names

Parameter Example value Description
name in
the sample
JCL
provided
-CEEQUAL- PP.ADLE370.OS39028 High-level qualifiers for the Language
Environment target libraries.
-CSSQUAL- SYS1 High-level qualifiers for the OS/390 callable
service library CSSLIB.
-CSQQUAL- MQM.V520 High-level qualifiers for the MQSeries product
libraries.
-DHLQUAL- WMQI.V210.DIST High-level qualifiers for the WebSphere MQ
Integrator for z/OS distribution data sets.
-SHLQUAL- WMQI.V210.SMPE High-level qualifiers for the new SMP/E data
sets that you are going to use to install
WebSphere MQ Integrator for z/OS. If you
are going to install into existing data sets, this
name is already defined.
-THLQUAL- WMQI.V210.TARG High-level qualifiers for the WebSphere MQ
Integrator for z/OS target data sets.

If these high-level qualifiers do not already exist, you must define them to RACF, or any other security
product you are using, and have ALIAS definitions in the master catalog.

B.2 Symbolic parameters

Use Figure 18 to plan the symbolic parameters for the WebSphere MQ Integrator for z/OS sample jobs.

24  Copyright IBM Corp. 2001

 Symbolic parameters

Figure 18. Symbolic parameters

Parameter Example Value Description
Name in the
Sample Jobs
-DISVOL- VOLSER WebSphere MQ Integrator for z/OS
distribution data set volume.
-DZNAME- DZONE The name of your distribution zone.
-GZONECSI- WMQI.V210.SMPE.GLOBAL The data set name of your global zone CSI.
-SMPUNIT- 3390 Type of disk unit for SMP/E data sets.
-SMPVOL- VOLSER SMP/E data set volume if installing into new
SMP/E data sets. Also used for temporary
libraries.
-TARVOL- VOLSER WebSphere MQ Integrator for z/OS target
data set volume.
-TZNAME- TZONE The name of your target zone.

Appendix B. High-level qualifiers and symbolic parameters 25

Reader's Comments
Program Directory for WebSphere MQ Integrator for z/OS December 2001

You may use this form to comment about this document, its organization, or subject matter with the understanding that
IBM may use or distribute whatever information you supply in any way it believes appropriate without incurring any
obligation to you.

For each of the topics below please indicate your satisfaction level by circling your choice from the rating scale. If a
statement does not apply, please circle N.

RATING SCALE
very very not
satisfied <=====================> dissatisfied applicable
1 2 3 4 5 N

Satisfaction
Ease of product installation 1 2 3 4 5 N
Contents of program directory 1 2 3 4 5 N
Installation Verification Programs 1 2 3 4 5 N
Time to install the product 1 2 3 4 5 N
Readability and organization of program directory tasks 1 2 3 4 5 N
Necessity of all installation tasks 1 2 3 4 5 N
Accuracy of the definition of the installation tasks 1 2 3 4 5 N
Technical level of the installation tasks 1 2 3 4 5 N
Ease of getting the system into production after 1 2 3 4 5 N
installation

How did you order this product?

CBPDO
CustomPac
ServerPac
Independent
Other

Is this the first time your organization has installed this product?
Yes
No

Were the people who did the installation experienced with the installation of z/OS products?
Yes

26 WebSphere MQ Integrator for z/OS Program Directory

 No

If yes, how many years? __

If you have any comments to make about your ratings above, or any other aspect of the product installation, please
list them below:

Please provide the following contact information:

Name and Job Title

Organization

Address

Telephone

Thank you for your participation.

Please send the completed form to (or give to your IBM representative who will forward it to the WebSphere MQ
Integrator for z/OS Development group):

Reader's Comments 27
 WebSphere MQ Integrator for z/OS Development,
Mailpoint 127,
IBM United Kingdom,
Hursley Park,
Winchester,
Hampshire SO21 2JN,
England.

FAX Number: (+44) 1962 870229

E-Mail: idrcf at hursley.ibm.com

28 WebSphere MQ Integrator for z/OS Program Directory

IBM

Printed in U.S.A.

GI1-2536-