MQSeries® for AS/400® IBM Quick Beginnings V5.
MQSeries® for AS/400® IBM Quick Beginnings V5.
Note! Before using this information and the product it supports, be sure to read the general information under “Appendix C. Notices” on page 105. First edition (March 2000) This edition applies to MQSeries for AS/400, Version 5 Release 1, and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2000. All rights reserved.
Contents Tables. . . . . . . . . . . . . . vii Welcome to MQSeries for AS/400 . . . . ix Conventions . . . . . . . . . . . . ix Chapter 1. About MQSeries. . . . . . . 1 Message Queuing . . . . . . . . . . 1 MQI – a Common Application Programming Interface . . . . . . . . 1 Time-Independent Applications . . . . . 2 Message-Driven Processing . . . . . . 2 Messages and Queues . . . . . . . . . 2 What is a Message? . . . . . . . . . 2 What is a Queue? . . . . . . . . . 3 MQSeries Objects . . . . .
Setting the Queue Manager CCSID for MQSeries for AS/400 . . . . . . . . 43 Chapter 6. Planning to Install MQSeries Clients . . . . . . . . . . . . . Applications on Version 5 Clients . . . . . AIX Client: Hardware and Software Required Hardware . . . . . . . . . . . . Software . . . . . . . . . . . . Compilers for MQSeries Applications on AIX Clients . . . . . . . . . . . Components for AIX . . . . . . . . . Digital UNIX Client: Hardware and Software Required . . . . . . . . . . . . . Hardware . . . . . .
Installation . . . . . . . . . . . Kernel Configuration . . . . . . . . Translated Messages . . . . . . . . Removing an MQSeries Client from Sun Solaris . . . . . . . . . . . . . Installing on Windows 95 or Windows 98 . . Installation . . . . . . . . . . . Unattended Installation on Windows 95 and Windows 98 . . . . . . . . . Removing an MQSeries Client from Windows 95 and Windows 98 . . . . . Installing on Windows 3.1 . . . . . . . Installation . . . . . . . . . . .
vi MQSeries for AS/400, V5.
Tables 1. 2. 3. National-language versions of MQSeries for AS/400, V5.1. . . . . . . . . 14 Authorities required to open an object 29 Authorities for Context and AlternateUserID . . . . . . . . . 29 © Copyright IBM Corp. 2000 4. 5. 6. MQSeries for AS/400 books . . . MQSeries publications – file names Sample programs – source files . . . . . 91 95 .
viii MQSeries for AS/400, V5.
Welcome to MQSeries for AS/400 This book describes IBM® MQSeries for AS/400, Version 5.1. It explains how to plan for, install, and begin to use the product. For latest information about MQSeries for AS/400, V5.1, refer also to the readme file on the publications CD-ROM, and to the MQSeries family Web site at: http://www.ibm.com/software/ts/mqseries/ Conventions Knowing the conventions used in this book will help you use it more efficiently. v Boldface type indicates the name of an item you need to select.
Conventions x MQSeries for AS/400, V5.
Chapter 1. About MQSeries This chapter introduces IBM MQSeries and describes its relationship with other products. It contains basic explanations of the following topics: v “Message Queuing” v “Messages and Queues” on page 2 v “MQSeries Objects” on page 3 v “Clients and Servers” on page 6 v “Instrumentation Events” on page 7 v “Transactional Support” on page 8 For more detailed explanations of these topics see the MQSeries Planning Guide.
Message Queuing Time-Independent Applications With message queuing, the exchange of messages between the sending and receiving programs is time independent. This means that the sending and receiving applications are decoupled; the sender can continue processing without having to wait for the receiver to acknowledge receipt of the message. In fact, the target application does not even have to be running when the message is sent. It can retrieve the message when it starts running.
Messages and Queues What is a Queue? A queue is a data structure that stores messages. The messages may be put on the queue by applications or by a queue manager as part of its normal operation. Queues exist independently of the applications that use them. A queue can exist in main storage (if it is temporary), on disk or similar auxiliary storage (if it must be kept in case of recovery), or in both places (if it is currently being used, and must also be kept for recovery).
MQSeries Objects Queue Managers A queue manager provides queuing services to applications, and manages the queues that belong to it. It ensures that: v Object attributes are changed according to the commands received. v Special events such as trigger events or instrumentation events are generated when the appropriate conditions are met. v Messages are put on the correct queue, as requested by the application that makes the MQPUT call.
MQSeries Objects Process Definitions A process definition object defines an application that is to be started in response to a trigger event on an MQSeries queue manager. A trigger event is a logical combination of conditions that is detected by a queue manager. For example, a trigger event may be generated when the number of messages on a queue reaches a predefined level. This event causes the queue manager to put a trigger message on a specified initiation queue.
MQSeries Objects Namelists A namelist is an MQSeries object that contains a list of other MQSeries objects. Typically, namelists are used by applications such as trigger monitors, where they are used to list a number of queues. The advantage of using a namelist is that it is maintained independently of applications. You can update a namelist without having to stop any of the applications that use it. Also, if one application fails, the namelist is not affected and other applications can continue using it.
Instrumentation Events Instrumentation Events You can use MQSeries instrumentation events to monitor the operation of queue managers. Instrumentation events cause special messages, which are called event messages, to be generated whenever the queue manager detects a predefined set of conditions.
Transactional Support Transactional Support An application program can group a set of updates into a unit of work. These updates are usually logically related and must all be successful for data integrity to be preserved. If one update succeeded while another failed then data integrity would be lost. A unit of work commits when it completes successfully. At this point all updates made within that unit of work are made permanent or irreversible. If the unit of work fails, all updates are instead backed out.
Chapter 2. What’s New in MQSeries for AS/400, V5.1 MQSeries for AS/400, V5.1 is an update to MQSeries for AS/400, V4.2.1. However, it is more than just an upgrade to the features of that product. It includes significant new function and a redesign of the product base, to bring MQSeries for AS/400 to the same level of function as other version 5.1 products. MQSeries for AS/400, V5.1 now offers platform consistency with the other products at the 5.
What’s New Java support MQSeries classes for Java™ include support for MQSeries for AS/400, V5.1. New calls MQSeries for AS/400, V5.1 supports the following new calls: v MQCONNX, which allows you to specify queue-manager connection options. v MQCMIT, MQBACK, and MQBEGIN, which allow MQSeries to coordinate a local unit of work. Two-phase commit MQSeries for AS/400, V5.1 participates as a two-phase commit resource in global units of work (UOW) managed by OS/400®.
What’s New Message queue size A message queue can be up to 2 GB. Message size A single message can be up to 100 MB. Administration application The administration application is not supported in MQSeries for AS/400, V5.1. Chapter 2. What’s New in MQSeries for AS/400, V5.
What’s New 12 MQSeries for AS/400, V5.
Chapter 3. Planning to Install the MQSeries for AS/400 Server This chapter provides a summary of the requirements for running MQSeries for AS/400. It discusses the network protocols and compilers supported, the delivery media, and the various components of the product. The information in this chapter applies to the server environment only. For information about client environments, see “Chapter 6. Planning to Install MQSeries Clients” on page 45. Hardware Requirements MQSeries for AS/400, V5.
Connectivity AS/400 Install Libraries and Directories MQSeries for AS/400 installs into the AS/400 library structure and also uses directories in the IFS root file system. AS/400 Library Structure Installation of MQSeries for AS/400 creates the following libraries: QMQM The MQSeries base product library. QMQMSAMP The MQSeries samples library (if you choose to install the samples). QMQM29xx A library containing a message file that is specific to your national language.
Connectivity derived from the name of the queue manager prefixed with the characters QM. For example, for a queue manager called TEST, the library would be called QMTEST. You can use the WRKLIB command to list all the libraries that MQSeries for AS/400 has created. Against the queue manager libraries, you will see the text QMGR: QMGRNAME. The format of the command is: WRKLIB LIB(QM*) These queue manager-associated libraries are retained when the product is deleted.
Connectivity User Profiles When you install MQSeries for AS/400, V5.1, a number of user profiles are created. These include QMQM, QMQMADM, and NOBODY. These three objects are central to the correct running of MQSeries for AS/400. Under no circumstances should you alter or delete them. If you do, IBM cannot guarantee correct behavior of your product. These profiles are retained when the product is deleted. Compilers Supported for MQSeries for AS/400, V5.1 Applications MQSeries for AS/400, V5.
MQSeries for AS/400 Components Samples Sample application programs. The source is supplied in the QMQMSAMP library and executables are supplied in the QMQM library. See “Appendix A. Sample MQI Programs” on page 99. MQSeries online documentation HTML and PDF versions of the books are supplied on the publications CD-ROM. They are not installable. You can read them directly from the CD-ROM or you can copy them to your system.
18 MQSeries for AS/400, V5.
Chapter 4. Installing, Migrating to, and Deleting MQSeries for AS/400 This chapter describes installation of and migration to MQSeries for AS/400, V5.1. It covers the following topics: v “Before Installation” v “Installation Procedure” on page 21 v “Verifying the Installation” on page 22 v “Quiescing MQSeries” on page 23 v “Migrating to MQSeries for AS/400, V5.1” on page 24 v “Verifying the Migration” on page 29 v “Deleting MQSeries for AS/400, V5.
Before Installation QCCSID Every message has a coded-character set identifier (CCSID) in its header. The CCSID tag identifies the code page and character set of the source. For CCSIDs that are supported on the AS/400 see the AS/400 National Language Support book. The CCSID information is obtained, when a queue manager is created, from the job CCSID. If this does not contain a valid value in the range 1–65534, the information is obtained from the default CCSID value for the job.
Installation Installation Procedure 1. To install the MQSeries for AS/400, V5.1 base product, issue the command: RSTLICPGM LICPGM(5733A38) DEV(install device) OPTION(*BASE) where: v 5733A38 is the product identifier for MQSeries for AS/400, V5.1, and v install device is the device from which the product is to be loaded, typically a CD-ROM - for example, OPT01. 2.
Verifying the Installation Verifying the Installation To ensure that the product has loaded correctly, issue the Display Software Resources (DSPSFWRSC) command and check that the licensed program 5733A38 is listed.
Quiescing MQSeries Quiescing MQSeries The orderly shutdown of MQSeries for AS/400 is called quiescing. You may need to quiesce MQSeries for AS/400, for example, to: v Take a backup of the system, or v Update MQSeries for AS/400 Quiescing previous releases of MQSeries for AS/400 To quiesce one of the previous releases of MQSeries for AS/400: 1.
Quiescing MQSeries Quiescing V5.1 of MQSeries for AS/400 To quiesce MQSeries for AS/400, V5.1: 1. Use F12 (Cancel) to return to your initial MENU Note: If you have MQSeries Commands (CMDMQM) as your initial menu, change the initial menu in your user profile, sign off and sign back on. 2. Ensure that you have: v *ALLOBJ authority, or object management authority for the QMQM library. v *USE authority for the following programs: – QMQM/AMQIQES4 – QMQM/AMQIQEM4 – QMQM/AMQSTOP4 – QMQM/AMQSPECA 3.
Migrating MQSeries What are the Differences MQSeries for AS/400, V5.1 provides significant new function over previous releases, including support for multiple queue managers, queue manager clusters, and substantially increased message and queue sizes. Enabling this new function has involved some changes to the internal architecture of MQSeries. For example this release makes substantial use of the Integrated File System whereas, previously, all MQSeries data was stored in OS/400 objects in libraries.
Migrating MQSeries The process is the same except that: v If you are moving to a new machine, there is one additional step, which is to transfer data from the old machine to the new. v If you are upgrading the system on the same machine, you must save your MQSeries data because the migration process completely deletes your old version of the product. To help you migrate, MQSeries for AS/400, V5.1 includes a utility program called MIGRATEMQM.
Migrating MQSeries 8. Save details of your existing MQSeries authorities. To find these details, issue the DSPMQMOBJN command to list the queue manager and all the MQSeries queues and processes that you have. Then issue the DSPMQMAUT command to list the access that users have to each of these objects. 9. Quiesce the product. To do this, refer to “Quiescing previous releases of MQSeries for AS/400” on page 23. 10. Copy your MQSeries CL and MQSC files to a suitable save library such as QGPL. 11.
Migrating MQSeries 2. Restore the MQSeries objects for libraries QMQMDATA and QMQMPROC using the following commands: RSTLIB SAVLIB(QMQMDATA) DEV(*SAVF) SAVF(QGPL/QMQMDATA) RSTLIB SAVLIB(QMQMPROC) DEV(*SAVF) SAVF(QGPL/QMQMPROC) 3. Restore the MQSeries local and remote journals using the following command: RSTOBJ OBJ(AMQ*) SAVLIB(QUSRSYS) DEV(*SAVF) OBJTYPE(*JRN) SAVF(QGPL/QMQMJRN) 4. Associate the journal receivers by: a.
Migrating MQSeries Note: Any PCF applications must be given explicit access to the queues. See the MQSeries for AS/400 V5.1 System Administration book for further information about security. Table 2. Authorities required to open an object Opening MQSeries object with option MQOO_ MQSeries object authority MQSeries object authority required - earlier releases required - V5.
Migration Verification 2. Ensure that the MQSeries subsystem, QMQM, is active. To do this, issue the command: DSPSBSD SBSD(QMQM/QMQM) If it is inactive, issue the command: STRSBS SBSD(QMQM/QMQM) 3. Ensure that the newly-created default queue manager is available. To check this, use the command: DSPMQM If it is not available, start it by issuing the command: STRMQM MQMNAME(QMGRNAME) 4. If applicable, verify that the queue manager and its objects have been successfully retained.
Deleting MQSeries Deleting MQSeries for AS/400, V5.1 There are two ways of deleting MQSeries for AS/400: v A standard deletion removes MQSeries product code but preserves user data. v An entire deletion removes both MQSeries product code and user data. Standard Deletion Perform a standard deletion of the MQSeries for AS/400 product if you wish to retain your user data, for example, because you intend to reinstall the product at a later date. To perform this deletion: 1. Quiesce MQSeries for AS/400.
Deleting MQSeries 3. End the MQSeries subsystem, by entering: ENDSBS SBS(QMQM/QMQM) 4. Delete the directory /QIBM/UserData/mqm and its subdirectories. Do this using the EDTF command and then use option 9 for the mqm directory. Note: If you do this, you will no longer have any information regarding your installation. Use this command with extreme caution.
Chapter 5. Using MQSeries for AS/400, V5.1 This chapter introduces MQSeries command sets and some basic tasks that you can perform to get yourself started with MQSeries for AS/400, V5.1. Tasks include creating and starting a queue manager, and creating, clearing, browsing, and deleting a local queue. The examples given use CL commands, but you can select the appropriate command from any of the supplied command sets. Before you Start Before you can use MQSeries for AS/400 you must start a subsystem.
Before you Start CL Commands The AS/400 CL commands for MQSeries can be grouped as follows: v Channel commands - used to create, start, and delete channels. v Cluster commands - used to work with queue manager clusters. v Command server commands - used to display, start, and end the command server. v Data type conversion command - used to convert data types. v Dead-letter queue handler command - used to start the dead-letter queue handler. v Media recovery commands - used to record and re-create objects.
Before you Start Command Usage CRTMQMNL (create MQM namelist) CRTMQMPRC (create MQM process) CRTMQMQ (create MQM queue) CVTMQMDTA (convert MQM data type command) DLTMQM (delete message queue manager) DLTMQMCHL (delete MQM channel) DLTMQMNL (delete MQM namelist) DLTMQMPRC (delete MQM process) DLTMQMQ (delete MQM queue) DSCMQM (disconnect message queue manager) DSPMQM (display message queue manager) to create a new namelist. to create a new process definition. to create a queue definition.
Before you Start Command Usage SPDMQMCLQM (suspend cluster queue manager) STRMQM (start message queue manger) STRMQMCHL (start MQM channel) STRMQMCHLI (start MQM channel initiator) STRMQMCSVR (start MQM command server) to inform cluster queue managers that the local queue manager is not available. to start a local queue manager. to start a channel. to start a channel initiator. to start a command server for a queue manager. to start the dead-letter queue handler.
Before you Start PCF Commands MQSeries programmable command format (PCF) commands allow you to program administration tasks into an administration program. For a complete description of the PCF commands and how to use them, see the MQSeries Programmable System Management book. Working with MQSeries If you are new to MQSeries for AS/400, you are recommended to set up a test system. Then you can verify that you have installed the product correctly and perform some basic MQSeries operations.
Working with MQSeries 2. On the CRTMQM panel, type in a Message Queue Manager name, for example TEST.QMANAGER and press Enter. The name of the queue manager can be a maximum of 48 characters in length. Valid characters are detailed in MQSeries for AS/400 V5.1 System Administration book. The queue manager is then created, along with a set of default objects.
Working with MQSeries 4. Fill in the name of your queue manager in the Message Queue Manager name field. For example TEST.QMANAGER. 5. Press Enter. There are three more parts to the CRTMQMQ panel. Scroll through them and enter values for the other options if you wish, or otherwise just accept all the defaults. The panels are shown in Figure 3 through Figure 5. Create MQM Queue (CRTMQMQ) Type choices, press Enter. Queue name . . . . . . . . . . . > _____ Queue type . . . . . . . . . . .
Working with MQSeries Create MQM Queue (CRTMQMQ) Type choices, press Enter. Default share option . . . Message delivery sequence Harden backout count . . . Trigger type . . . . . . . Trigger depth . . . . . . Trigger message priority . Trigger data . . . . . . . _____ Retention interval . . . . Maximum queue depth . . . Maximum message length . . Backout threshold . . . . Backout requeue name . . . _____ Initiation queue . . . . . _____ F3=Exit F4=Prompt F24=More keys . . . . . . . . . . . . . . . . . .
Working with MQSeries Sending a Test Message To put a test message on your queue use the supplied sample programs. For example, to put messages to a queue called TEST.QUEUE, defined for a queue manager called TEST.QMANAGER, enter the command: CALL PGM(QMQM/AMQSPUT0) PARM(TEST.QUEUE TEST.QMANAGER) You can now type a message (a simple character string is sufficient) and press Enter to send the message to the queue. Press Enter again to return to a command line.
Working with MQSeries There are 4 options you can use when ending a queue manager: 1. OPTION (*CNTRLD). This allows current transactions to complete, and all applications to disconnect, before ending the queue manager. This option is the default. 2. OPTION (*IMMED). This immediate shutdown allows any current calls to complete, but stops any new calls. It does not wait for applications to disconnect from the queue manager. 3. OPTION (*WAIT).
User Exits User Exits Before using user exits on MQSeries for AS/400, V5.1, relink them with the threaded libraries and ensure that they are thread-safe and teraspace enabled. See the MQSeries Application Programming Guide and the MQSeries Intercommunication book for further information about creating user exit programs. Setting the Queue Manager CCSID for MQSeries for AS/400 When you create a queue manager, its coded character set identifier (CCSID) is set by default.
44 MQSeries for AS/400, V5.
Chapter 6. Planning to Install MQSeries Clients This chapter provides a summary of the hardware and software required to run the following MQSeries clients: v MQSeries client for AIX v MQSeries client for DOS v MQSeries client for HP-UX v MQSeries client for OS/2 Warp v MQSeries client for Sun Solaris v MQSeries client for Windows 3.1 v MQSeries client for Windows 95 and Windows 98 v MQSeries client for Windows NT® You can install all of these clients from the MQSeries Client CD.
Hardware and Software, AIX v AIX Version 4.2 (5765-655 or 5765-C34) or AIX Version 4.3 or later. Later levels of some listed products might be required for AIX Version 4.2, SMP, and SP™. Later levels of operating system might be required to support corequisite products. Connectivity For TCP/IP connectivity: v TCP/IP (in the operating system) For SNA LU 6.2 connectivity: v IBM eNetwork™ Communications Server for AIX, Version 5.0 Optional software v IBM DCE Version 2.2. This must be the U.S.
Components for AIX MQSeries Client for Java This allows Java applets running on your client machine to communicate with MQSeries. It includes security exits for encryption and authentication of messages sent across the Web by the MQSeries Client for Java. These exits consist of some Java classes. To use the client for Java you need to have Java run-time code on your machine, at the following (or later compatible) levels: AIX Java version 1.1.1 HP-UX Java version 1.1.2 Sun Solaris Java version 1.1.
Hardware and software, Digital UNIX Compilers for MQSeries applications on Digital UNIX clients The following compiler is supported: v DEC C, Version 5.2 for Digital UNIX DOS Client: Hardware and Software Required This section outlines the hardware and software requirements for an MQSeries client for DOS. Hardware An MQSeries client can run on DOS, on a personal computer.
Components for DOS Components for DOS MQSeries Client The MQSeries client code for your platform. MQSeries Toolkit This includes: v Sample programs - some of these are required for verifying the installation of the MQSeries client/server system v Header files that you can use when writing applications to run on the client HP-UX Client: Hardware and Software Required This section outlines the hardware and software requirements for an MQSeries client for HP-UX.
Hardware and Software, HP-UX Compilers for MQSeries Applications on HP-UX Clients The following compilers are supported: v Micro Focus COBOL for UNIX, Version 4.0 v HP-UX ANSI C compiler v C Softbench, Version 5.0 v HP CFRONT C++, Version 3.1 v IBM C and C++ compilers, Version 3.6 v HP ANSI C++ Components for HP-UX These are identical to those for AIX. See “Components for AIX” on page 46.
Hardware and Software, OS/2 Warp Optional software v IBM Directory and Security Server for OS/2 Warp, Version 4 or later compatible versions. This must be the U.S. Domestic version supporting DES encryption if the user wishes to run the MQSeries-supplied DCE send, receive, or message exits.
Components for OS/2 Warp for Java must be installed on an HPFS formatted drive. For information about Java runtime see “HTML and PDF Books on the World Wide Web” on page 96. Note: If it is possible on your platform, at installation time the CLASSPATH environment variable will either be updated if already present, or created if not. MQSeries Internet Gateway documentation MQSeries Internet Gateway documentation supplied in HTML format.
Hardware and Software, Sun Solaris Optional software Transarc DCE, Version 1.1. This must be the U.S. version supporting DES encryption for users to run the MQSeries-supplied DCE send, receive or message exits. DCE names and security modules for MQSeries are provided as part of the MQSeries for Sun Solaris product. Compilers for MQSeries Applications on Sun Solaris Clients The following compilers are supported: v SunWorkShop Compiler C, Version 4.2 v SunWorkShop Compiler C++, Version 4.
Hardware and Software, Windows 3.1 Compilers for MQSeries Applications on Windows 3.1 Clients The following compiler is supported: v Microsoft Visual C++, Version 1.5 Components for Windows 3.1 These are identical to those for DOS. See “Components for DOS” on page 49. Windows 95 and Windows 98 Client: Hardware and Software Required This section outlines the hardware and software requirements for an MQSeries client for Windows 95 and Windows 98.
Components for Windows 95 and Windows 98 Components for Windows 95 and Windows 98 MQSeries Client The MQSeries client code for Windows 95 and Windows 98. MQSeries Toolkit This includes: v Sample programs v Header files that you can use when writing applications to run on the client Windows NT Client: Hardware and Software Required This section outlines the hardware and software requirements for an MQSeries client for Windows NT.
Hardware and Software, Windows NT v Microsoft Visual C++ for Windows 95 and Windows NT, Version 4.0 and Version 5.0 v IBM C and C++ compilers, Version 3.6 v IBM PL/I for Windows, Version 1.2 v IBM VisualAge for PL/I for Windows v IBM VisualAge PL/I Enterprise, Version 2.1 v IBM Visual Basic for Windows, Version 4.0 (16-bit) and Version 5.0 (32-bit) or higher v IBM VisualAge for Java, e-Business Edition for Windows 95 and Windows NT v IBM VisualAge Java Enterprise Edition, Version 2.
Chapter 7. Installing MQSeries Clients This chapter describes the following: v “Installing MQSeries Clients on the Same Machine as the Server” v “Installing on AIX” v “Installing on DOS” on page 64 v “Installing on HP-UX” on page 65 v “Installing on OS/2 Warp” on page 66 v “Installing on Sun Solaris” on page 75 v “Installing on Windows 95 or Windows 98” on page 77 v “Installing on Windows 3.
Installing on AIX The MQSeries client is installed into the /usr/mqm directory. This cannot be changed. However, if you do not have enough space in the /usr/mqm file system, follow the procedure given in “Creating Another File System for the Client” on page 59. If you have a previous version of the MQSeries for AIX client installed on your system, or if a file system remains from a previous AIX client installation, see “Migrating from an Earlier Version of MQSeries for AIX” on page 62.
Installing on AIX Creating Another File System for the Client If you do not want to have the client installed in the /usr/mqm file system, you can do either of the following things: 1. Create a new file system and mount it as /usr/mqm. or 2. Create a new directory anywhere on your machine that is large enough to contain the client files, and create a symbolic link from /usr/mqm to this new directory.
Installing on AIX 3. Add a password to the new user ID. You can display the window for doing this using this sequence: Security & Users Passwords 4. Add the newly created group mqm to an existing user ID. You can display the window for doing this using this sequence: Security & Users Users Change / Show Characteristics of a User When the window is displayed, enter the name of the user who is to have the mqm group added.
Installing on AIX 7. Click on Install/Update. A bundle of software products is created: mqm.Client 8. Choose the mqm.Client bundle and click on Install/Update again. A work in progress window gives information as the installation proceeds. 9. At the end of installation you can click on the View log button and scroll to the bottom of the log to see the filesets that have been installed successfully.
Installing on AIX Migrating from an Earlier Version of MQSeries for AIX If you want to migrate from an MQSeries for AIX V5.0 client to an MQSeries for AIX V5.1 client, you must first end all MQSeries activity on the target machine, and remove any shared resources that are used by MQSeries. Do this either by shutting down the system and restarting it, or by issuing the icprm command to remove the shared resources.
Installing on AIX Installation of the MQSeries for AIX V5.1 client will fail if a file system mounted as /usr/lpp/mqm is detected. If you are migrating from an earlier version and a file system exists for this directory, you will need to do one of the following things before installing the MQSeries for AIX V5.1 client.
Installing on AIX Software Installation and Maintenance Install and Update Software Install and Update from ALL Available Software 3. Press the List button to display the Single Select List window. 4. Select: /dev/cd0 (CD-ROM Drive) 5. Press the List button on the Software to Install field. 6. Select the message catalog that you want to install. 7. Press Do to install the chosen message catalog or catalogs. To check the initial locale setting for your machine type: smitty mle_cc_cust_hdr and press Enter.
Installing on DOS 5. Edit the autoexec.bat file using a suitable editor. If the PATH statement exists, add the following to it: c:\mqmdos;c:\mqmdos\bin;c:\mqmdos\en_us If the PATH statement does not exist, add the following line to the autoexec.bat file. SET PATH=c:\mqmdos;c:\mqmdos\bin;c:\mqmdos\en_us Removing an MQSeries Client from DOS Delete all the files in the directory where you installed the MQSeries client, and then remove the directory.
Installing on HP-UX For stand-alone machines, you can create the new user and group IDs locally. For machines administered in a network information services (NIS) domain, you can create the user and group IDs on the NIS master server machine. Installation Use the HP-UX swinstall program, or use SAM, after mounting the CD-ROM. For further details, see the appropriate HP-UX documentation. If you are using HP-UX V10.x, the depot to use is in the HPUX10/MQS510.000.V10 file under the mount point.
Installing on OS/2 Warp You can install the version of the MQSeries client software specific to your national language. This means that the installation program, online help and messages will be in your national language. Installation Online help is available by selecting the Help push button or by pressing PF1. Before you start, make sure that you have at least 150 KB of free space on the drive containing the operating system. This is required by the installation program. 1.
Installing on OS/2 Warp Use the push buttons as necessary: v To display descriptions of the selected options, select Descriptions. v To select all of the options, select Select all. v To deselect all of the options, select Deselect all. The Work and File Directory field allows you to specify a drive and directory other than the default for the installation files (File directory) and for the working files that might be created when you use the MQSeries client (Working directory).
Installing on OS/2 Warp Note that the MQSeries client is a set of services and it does not have to be explicitly run. Therefore the folder does not have an object called a “client”. 13. Remove the installation CD-ROM from the drive. 14. If your CONFIG.SYS file has been updated, shut down the system and restart. If the CONFIG.SYS file was not updated, rename the CONFIG.ADD file to CONFIG.SYS before shutting down the system (CONFIG.ADD will be in the same directory as CONFIG.SYS). 15.
Installing on OS/2 Warp Attention Note that the INSTALL.EXE file in the root directory of the CD-ROM must not be used to perform unattended installations. You must instead invoke the INSTALL.EXE file located in the directory corresponding to the language version of the product that you want to install. Starting Unattended Installation The following steps describe how to perform an unattended installation: 1. Connect to the drive containing the MQSeries product software.
Installing on OS/2 Warp command, you must type it as one continuous line. In the example above, for clarity, the command is spread over several lines. In this example, the MQSeries client is installed from the redirected drive J: on the server, according to the options supplied in the response file AMQISMC2.RSP. Note that drive J: must be a writeable drive that you must create, and the .RSP file must be put on that drive. The installation log files will also be created on the J: drive.
Installing on OS/2 Warp /G:include path Specifies the drive and path of a general response file to be included by the specific response file. For more information about response files, see “Installation Response Files” on page 73. /L1:error log Specifies the drive, path, and file name of the error log file. The error log contains messages associated with installation, including confirmations and error messages. Messages are written to the error log if you specify the /X parameter.
Installing on OS/2 Warp When you specify this parameter, no progress indicator panel is shown and error messages are logged in the error log file. (You specify the path name of the error log file using the /L1 parameter.) If you do not specify all of the information required for the action to complete, an error occurs. If you do not specify the /X parameter, the user is prompted for any information that the install program needs to complete the action.
Installing on OS/2 Warp CFGUPDATE Specifies whether CONFIG.SYS is updated automatically. Valid values for this keyword are: AUTOAutomatically updates CONFIG.SYS MANUALDoes not update CONFIG.SYS Actions: INSTALL, UPDATE, DELETE. COMP Specifies the name of a component on which to perform an action. See the server or client component lists for valid values. You do not need to enclose the product names within quotes. Actions: ALL actions.
Installing on OS/2 Warp file found that matches the specification is included. If the specification is not valid, no general response file is included. Note: You should not have more than five levels of included response files. Actions: All actions. OVERWRITE Specifies whether to overwrite files automatically during installation. Valid values for this keyword are YES and NO. Actions: INSTALL, UPDATE. SAVEBACKUP Specifies whether to save a backup version of MQSeries for OS/2 Warp when it is updated.
Installing on Sun Solaris Note: If you plan to install an MQSeries client and server on the same machine, see “Installing MQSeries Clients on the Same Machine as the Server” on page 57. The MQSeries product is installed into the /opt/mqm directory. This cannot be changed. Before Installation Before you can install an MQSeries client on your Sun Solaris system you: v Must create a group with the name mqm. v Must create a user ID with the name mqm.
Installing on Sun Solaris b. You are prompted for a list of components to be installed. Select the ones you require - if you want to install all the components, select all. The component MQSeries Client for Java should be installed only if you have Java 1.1.1 (or later compatible) runtime code on your machine. You also require Version 2.6 or later of the Sun Solaris operating system. c. Press the Enter key.
Installing on Windows 95 or 98 Installation 1. Insert the MQSeries Client CD-ROM into the CD-ROM drive. 2. The installation automatically starts and an MQSeries Language Selection window is displayed. Note: If you have disabled auto-playing of CD-ROMs, run SETUP instead, from the root directory. 3. 4. 5. 6. This window presents you with a list of the national languages that are available.
Installing on Windows 95 or 98 If you view the README file, close the window of the README to continue the installation process. 10. The installation of the MQSeries client is now complete, and a window is displayed giving you the option of restarting your computer now or leaving it until later. It is recommended that you restart your computer now. Close all the other applications that are running before continuing with this step.
Installing on Windows 95 or 98 v SetupKo – Korean v SetupPt – Brazilian Portuguese v SetupTw – Traditional Chinese 4. From the selected language directory, run setup.exe, with the -r option to create a response file. This can be done by: a. Highlighting setup.exe b. Dragging it to the Start, Run dialog c. Adding -r to the end of the fully-qualified file name d. Selecting OK to start the process e. Selecting the components that you want to install Notes: a.
Installing on Windows 95 or 98 1. Use the NET USE command as follows: NET USE devicename \\servername\netname For example: NET USE J: \\MQMNT\MQMSHARE where: v J: is the logical drive name to be connected to the shared resource directory. v MQMSHARE is the netname for M:\INSTMQS. 2. Go to the language directory that contains the SETUP.EXE and SETUP.ISS files and run SETUP -s. Notes: 1. The -s parameter indicates that the installation is to be carried out in silent mode.
Installing on Windows 3.1 setupen setuppt setupfr setupde setupit setupjp setupko setupes setupcn setuptw - English Brazilian Portuguese French German Italian Japanese Korean Spanish Simplified Chinese Traditional Chinese 4. Run setup.exe The MQSeries Welcome window is displayed. 5. Make sure you are installing the correct client for your system, Windows 3.1, as displayed in the Welcome window. 6.
Installing on Windows 3.1 Select Yes, I want to restart my computer now and click on the Finish button to complete the setup. 12. When setup is complete, the MQSeries Client folder is added to the Program Manager. Note that the MQSeries client is a set of services and it does not have to be explicitly run, so the folder does not have an object called a “client”. Removing an MQSeries Client from Windows 3.
Installing on Windows NT 3. On the MQSeries Language Selection window select the language of your choice, and click on the OK button or press Enter. The MQSeries Welcome window is displayed. 4. Make sure you are installing the correct client for your system, as displayed in the Welcome window. 5. Choose Installation Folders lets you choose folders into which the MQSeries program files and data files will be installed.
Installing on Windows NT Installing from a LAN There are two ways to put MQSeries installation files on a LAN file server for easier access: you can make the MQSeries for Windows NT Client CD-ROM drive shareable, or you can copy the installation files from the CD-ROM to a file server, by following these steps: 1. Create a folder on the LAN file server to store the installation files. For example: md m:\instmqs 2. Load the MQSeries for Windows NT client CD-ROM.
Installing on Windows NT Using the System Management Server with MQSeries for Windows NT This section describes how to install, or remove, an MQSeries for Windows NT client using the System Management Server (SMS). Creating SMS Packages and Jobs for MQSeries You must create: v An SMS software package containing the MQSeries software. v An SMS job to distribute and install the software package (see “Creating the MQSeries SMS Job” on page 87).
Installing on Windows NT Note: If you specified a local path in the Source Directory entry field, you get a pop-up dialog warning you that the local path you specified might not be accessible to SMS components running on another machine. Click on the OK button to continue. 10. Click on the OK button to close the Package Properties window. A pop-up dialog appears indicating that SMS will update the software package at all sites. Click the OK button to continue.
Installing on Windows NT 3. Carry out an installation on a machine and record the options selected to install the product in a response file. To do this you must run setup.exe with the -r parameter, and optionally, the -noinst parameter: a. Load the MQSeries for Windows NT client CD-ROM. If you have autorun enabled, the language selection panel will appear. Cancel this panel. b. Run setup.exe from the root folder of the CD-ROM, with the -r parameter. This can be done by dragging setup.
Installing on Windows NT you omit the -g parameter, Setup creates a file called amqilogn.txt in the data-files folder on the machine running the installation. In this case, any messages generated before the data-files folder is created are lost. The -g parameter must be placed before the -f1 and the -s parameters, otherwise it is ignored. The full path to the response file you prepared.
Configuring a Client Configuring and Verifying a Client After you have installed the client, you need to configure your communications and verify the installation. For information on how to do this, see the MQSeries Clients book. 90 MQSeries for AS/400, V5.
Chapter 8. Obtaining Additional Information This chapter describes the documentation for MQSeries for AS/400, V5.1. It starts with a list of the publications, and then discusses: v “Hardcopy Books” on page 93 v “Online Information” on page 93 MQSeries for AS/400, V5.1 is described in the following books: Table 4.
Additional Information Table 4. MQSeries for AS/400 books (continued) 92 Order Number Title Description SC33-1872 MQSeries Intercommunication Defines the concepts of distributed queuing, and explains how to set up a distributed queuing network in a variety of MQSeries environments.
Additional Information Table 4. MQSeries for AS/400 books (continued) Order Number Title Description SC33-1673 MQSeries Application Programming Reference Provides comprehensive reference information for users of the MQI. It includes: data-type descriptions; MQI call syntax; attributes of MQSeries objects; return codes; constants; and code-page conversion tables.
Online Information Publications CD-ROM Included with the product is a publications CD-ROM. On this CD-ROM there are three directories; books, amqaa60w, and readme. CD-ROM books directory The books directory contains the MQSeries for AS/400 books in HTML and PDF formats. To access them point you Web browser to books/start.htm. HTML: You can view the MQSeries online documentation in HTML format directly from the publications CD-ROM.
Online Information To find out which ones are available in your language, look for the appropriate directory on the CD-ROM. The PDFs are in the directory BOOKS/PDF/ll_LL, where ll_LL is one of the following: v en_US (English) v fr_FR (French) v de_DE (German) v it_IT (Italian) v ja_JP (Japanese) v ko_KR (Korean) v es_ES (Spanish) v zh_CN (Simplified Chinese) Within these directories, you can find the complete set of PDFs that are available. Table 5 shows the file names used for the PDF files. Table 5.
Online Information CD-ROM amqaa60w directory The amqaa60w directory contains a package of searchable PDF files. The package comprises a set of panels, books, and index files and provides a method of searching the MQSeries library on your workstation using Adobe Acrobat Reader with Search. The package is available in U.S. English only.
Online Information BookManager CD-ROMs The MQSeries library is supplied in IBM BookManager® format on a variety of online library collection kits, including the Transaction Processing and Data collection kit, SK2T-0730.
98 MQSeries for AS/400, V5.
Appendix A. Sample MQI Programs MQSeries for AS/400 provides a set of short sample MQI programs. You can choose to install these when you install the base product. If you do install them, you get them in both source form and object form. You can use the objects as they are or you can modify and recompile the source for experimental purposes. C, COBOL, and RPG Program Samples Table 6 lists the sample MQI source files.
Samples Table 6.
Samples c. ILE RPG programs using prototyped calls to the MQI. The source for these is in QMQMSAMP/QRPGLESRC. The members are named AMQ3xxx4, where xxx indicates the sample function. Copy members exist in QMQM/QRPGLESRC. Each member name has a suffix of ’G’. If the objects required by the sample programs are missing from your system, you can create them. Use the program in member AMQSCOMA in the source physical file QMQMSAMP/QMQSC.
102 MQSeries for AS/400, V5.
Appendix B. Applying Maintenance to MQSeries for AS/400 This appendix tells you how to apply maintenance to MQSeries for AS/400. Service updates for MQSeries for AS/400 are supplied as PTFs (Program Temporary Fixes). They may be supplied on a CD-ROM, or you may obtain them electronically as save files, which are normally stored in the QGPL library.
104 MQSeries for AS/400, V5.
Appendix C. Notices This information was developed for products and services offered in the United States. IBM may not offer the products, services, or features discussed in this information in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
Notices improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
Notices Trademarks The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both: AIX CICS IBM OS/2 RISC System/6000 WIN-OS/2 AS/400 DB2 IBMLink OS/390 SupportPac 400 BookManager eNetwork MQSeries OS/400 VisualAge Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries.
108 MQSeries for AS/400, V5.
Index bibliography 91 BookManager 97 books ordering 93 printing 94 browsing queues 41 commands CL CLRMQM 41 CRTMQM 37 DLTMQMQ 41 ENDMQM 41 ENDMQMCSVR 26 RCDMQIMG 27 STRMQM 30, 38 STRMQMMQSC 36 WRKMQMCHL 26 WRKMQMCHST 26 WRKMQMMSG 26, 41 MQSC 36 programmable command format (PCF) 37 compilers 16 components installed 16 configuration, kernel 66, 77 conventions ix creating groups client 58, 65, 76 queue manager 37 user ID 58, 65, 76 crtmqm command 37 custom installation AIX client 61 C D C sample programs
installing AIX client 60 AIX client (custom install) 61 clients on the server (Version 5.1) 57 clients on Windows 3.
Removing clients Windows 3.1 83 requirements disk storage 13 MQSeries for AS/400, V5.
112 MQSeries for AS/400, V5.
Sending your comments to IBM If you especially like or dislike anything about this book, please use one of the methods listed below to send your comments to IBM. Feel free to comment on what you regard as specific errors or omissions, and on the accuracy, organization, subject matter, or completeness of this book. Please limit your comments to the information in this book and the way in which the information is presented.
IBMR Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber.
Spine information: IBM MQSeries® for AS/400® MQSeries for AS/400, V5.1 Quick Beginnings V5.
