This document describes the steps for installing Natural Messaging (product code NMQ) on z/OS.
For information on the features and functions provided by Natural Messaging, see Natural Messaging in the Database Management System Interfaces documentation.
When used in this document, the notation
vrs or
vr represents the relevant product
version (see also Version in the
Glossary).
The installation medium contains the following data sets required for product installation:
| Data Set Name | Contents |
|---|---|
NMQvrs.LICS |
Load modules for the z/OS license check software containing
the LICUTIL license utility
The placeholder
For detailed information on the license check software and the LICUTIL utility, see Mainframe Product Licensing. |
NMQvrs.LOAD |
Load modules |
NMQvrs.INPL |
DDMs for Natural Messaging and examples |
Copy the data sets into your environment as described in Copying Data Sets to a z/OS Disk in the section Installing Natural.
Be sure to read Installation Process and Major Natural Features before you start the installation procedure.
Step 1: Prepare, Convert, Assemble and Link the License File
Step 2: Build the Natural Parameter Module with a Database Assignment for Natural Messaging
(Job I007, Steps 3401, 3402, 3404)
In addition to the Natural product license file, a valid Natural Messaging license file
is required and must be installed for each environment in which Natural Messaging (NMQ)
runs. For license file NMQvrs.LICS, see
Mainframe Product
Licensing.
Copy the license file from the installation medium to disk or transfer it from the PC as described in Transferring a License File from PC to a z/OS Host Using FTP in Mainframe Product Licensing.
Check, convert, assemble, and link the license file:
| Step 3401 | Check the license file
NMQvrs.LICS. This job executes
the CHECK function of the LICUTIL license utility.
|
| Step 3402 | Convert the license file into an assembler source. This job executes the MAKE function of the LICUTIL license utility. |
| Step 3404 | Assemble and link the assembler source to generate load
module NMQLIC. This module is then linked to the nucleus (see
below).
|
The functions and option settings provided by LICUTIL are described in Using the License Utility: LICUTIL in Mainframe Product Licensing.
| Warning: Natural Messaging is not enabled unless you install a valid Natural Messaging license file. Trying to activate Natural Messaging without a valid license file results in warnings or errors at session start. |
(Job I060, Steps 0010, 0015 for batch)
(Job I080, Steps 2210, 2220 for CICS)
(Job I080, Steps 2300, 2310 for Com-plete)
(Job I080, Steps 0010, 0015 for TSO)
Build the Natural parameter module:
Modify the appropriate jobs according to the batch modules or TP monitor you are relinking: Job I060 for batch, Job I080 for CICS and Com-plete.
Add the following macro call to your Natural parameter module:
NTDB MQ, my-dbid
Assemble and link the Natural parameter module.
(Job I060, Step 0105)
(Job I060, Step 0020 for batch)
(Job I080, Steps 2230 for CICS)
(Job I080, Steps 2320 for Com-plete)
(Job I080, Steps 0020 for TSO)
Modify the JCL used to link your environment-independent nucleus by adding the following
INCLUDE statement:
INCLUDE NMQLIB(NQMNUC)
Modify the JCL used to link your environment-dependent nucleus for the Natural CICS Interface by adding
the following INCLUDE statements:
INCLUDE NMQLIB(NMQTAB) INCLUDE MQLIB(CSQCSTUB)
CSQCSTUB is the IBM MQ stub for CICS provided in the IBM MQ
library.
Modify the JCL used to link your environment-dependent nucleus for all other environments besides CICS
by adding the following INCLUDE statements:
INCLUDE NMQLIB(NMQTAB) INCLUDE MQLIB(CSQBSTUB)
CSQBSTUB is the IBM MQ stub for batch and TSO provided in the IBM MQ
library. This is also applicable for Natural under Com-plete.
(Job I061, Step 3410)
Load the DDMs and Natural example objects specific to Natural Messaging from the
NMQvrs.INPL data set into the Natural system
file by using the Natural INPL utility.