************************************************************************ * Licensed Materials - Property of IBM * * * * 0791003,5724-A39 * * (C) Copyright IBM Corp. 1993, 2001 * * * * US Government Users Restricted Rights - Use, duplication or * * disclosure restricted by GSA ADP Schedule Contract with IBM Corp. * ************************************************************************ COMPONENT_NAME: IBM MQSeries for Compaq NonStop Kernel Version 5.1 Welcome to MQSeries for Compaq NonStop Kernel Version 5.1 from IBM. This README file contains information you need for installing IBM MQSeries for Compaq NonStop Kernel, as well as information that was not available for our printed publications. This README file is divided into the following categories: o Getting help o Service and Technical Support o Key Differences from MQSeries for Tandem NonStop Kernel Version V2.2.0.1 o Migrating from MQSeries for Tandem NonStop Kernel Version V2.2.0.1 o MQI Client Installation o Latest Information on MQSeries Products o Late Breaking News o Trademarks GETTING HELP Accessibility ------------- Accessibility features help people who face physical disability, such as restricted mobility or limited vision, to use our products successfully. MQSeries for Compaq NonStop Kernel, V5.1 is designed to be an accessible product. These are the accessibility features in MQSeries for Compaq NonStop Kernel, V5.1: The MQSC command line can be accessed through the Telnet utility, which is part of Microsoft Windows NT and Windows 2000. Telnet can be used with assistive technologies, such as the WindowEyes V4.1 or JAWS V3.7 screen reader products, to support use by people with limited vision. It is advised that programs which intermittently refresh screen information (for example, clock) are removed when using assistive technologies. Other programs specifically designed to emulate Compaq NonStop Kernel terminals (6530) may also work with these assistive technologies. All documentation for this product is available in HTML so that it can be read by a screen reader Available Documentation ----------------------- GC34-5887 - MQSeries for Compaq NonStop Kernel V5.1 Quick Beginnings SC34-5886 - MQSeries for Compaq NonStop Kernel V5.1 System Administration G511-1908 - MQSeries Brochure GC33-0805 - MQSeries An Introduction to Messaging and Queuing GC33-1349 - MQSeries Planning Guide SC33-1872 - MQSeries Intercommunication SC34-5349 - MQSeries Queue Manager Clusters GC33-1632 - MQSeries Clients SC33-1369 - MQSeries MQSC Command Reference SC33-1482 - MQSeries Programmable System Management SC34-5390 - MQSeries Administration Interface Programming Guide and Reference GC33-1876 - MQSeries Messages SC33-0807 - MQSeries Application Programming Guide SC33-1673 - MQSeries Application Programming Reference SX33-6095 - MQSeries Application Programming Interfaces Reference Summary SC33-1877 - MQSeries Using C++ SC34-5456 - MQSeries Using Java The MQSeries for Compaq NonStop Kernel V5.1 Quick Beginnings and System Administration are provided with this product in PDF format in the ZMQSSYS subvolume as the files MQSQBPDF and MQSSAPDF respectively. HTML and PDF books on the World Wide Web ---------------------------------------- The MQSeries books are available on the World Wide Web in PDF and HTML format. The MQSeries product family Web site is at: http://www.ibm.com/software/ts/mqseries/ By following links from this Web site you can: Obtain latest information about the MQSeries product family. Access the MQSeries books in HTML and PDF formats. Download MQSeries SupportPacs. You can view the MQSeries documentation (including MQSeries for Compaq NonStop Kernel, V5.1 Quick Beginnings and the MQSeries for Compaq NonStop Kernel, V5.1 System Administration Guide) in HTML format directly from the World Wide Web. When you read the books in HTML, you can follow hypertext links from one book to another. If you are reading translated books and link to a book that is not available in your national language, the U.S. English version of the book will be opened instead. All of the above publications are downloadable from the WWW in HTML format also. SERVICE AND TECHNICAL SUPPORT Before installing MQSeries for Compaq NonStop Kernel ask your support organization for any Preventive Service Planning (PSP) information. Note: MQSeries for Compaq NSK V5.1 contains all the applicable maintenance that was available for MQSeries for Tandem NSK V2.2.0.1 KEY DIFFERENCES FROM MQSERIES FOR TANDEM NONSTOP KERNEL V2.2.0.1 MQSeries V5.1 contains several new features that were not available in MQSeries V2.2.0.1: MQSeries Queue Server (MQQS) for message storage and queue management MQSeries Status Server (MQSS) now handles channel statistics and non queue objects True memory based non-persistent message support Support for multiple TCP/IP processes per queue manager Enhanced SNA listener C++ and Java language support Full V5.1 and V5.0 MQSeries API functionality Support for MQSeries Clusters MQSeries administration interface (MQAI) support Maximum message size increased to 100MB FC support for RUNMQSC Updated MQMC panels to reflect new MQSeries functionality ALTMQFLS usability enhanced and usage altered For more information on these features, see the What's new in MQSeries V5.1 section in the MQSeries for Compaq NSK Quick Beginnings or System Administration publications. MIGRATING FROM MQSERIES FOR TANDEM NONSTOP KERNEL V2.2.0.1 To migrate an existing V2.2.0.1 MQSeries installation, select an installation type of 'UPGRADE' when running INSTMQM. Only installations that are at the latest service level (PTF U473441 or later) may be upgraded. Once the installation has completed, individual queue managers must be upgraded with the utility UPGMQM. See the MQSeries for Compaq NonStop Kernel V5.1 Quick Beginnings Guide for information on how to use this utility. You will have to recompile and rebind applications that previously ran with an existing V2.2.0.1 MQSeries installation. Note that the MQI library names have changed so BIND scripts will need editing. MQMLIB or MQMLIBN are the two libraries which must be bound with depending on whether non-native or native applications are required respectively. On upgrading from V2.2.0.1, the following obsolete system files are deleted: - ZMQSEXE.CNV1520 (migration from V1.5.1 not supported) - ZMQSEXE.CNVMSGS (migration from V1.5.1 not supported) - ZMQSLIB.MQMLIBC (C MQI library from V2.2.0.1) - ZMQSLIB.MQMLIBNC (Native C library from V2.2.0.1) - ZMQSLIB.MQMLIBT (TAL / Cobol library from V2.2.0.1) - ZMQSLIB.MQMLIBNT (TAL / Cobol library from V2.2.0.1) MQI CLIENT INSTALLATION No MQSeries clients are provided as part of the MQSeries for Compaq NonStop Kernel product, however MQSeries clients can attach to a NonStop Kernel queue manager. The latest MQSeries client code should be downloaded from the MQSeries home pages. LATEST INFORMATION ON MQSeries PRODUCTS To get all the latest information on MQSeries products via the Internet you can look at URL http://www.ibm.com/software/ts/mqseries/ LATE BREAKING NEWS 1. Native mode Trigger monitor starting Native mode trigger application. In the D4x release when a Native mode application accepts command line arguments as a string, such as those created by the default Trigger monitor (MQS-TRIGMON00), the string is misinterpreted. The triggered application, such as the Native sample amqsech, will fail to interpret the command string properly into the MQTMC2 structure. The application will fail to open the queue named in the trigger message from the Trigger monitor and exit. A system SRL is in error and installation of Tandem IPM T8432AAG corrects this problem. 2. Binder warning 59 Parameter count mismatch for ldiv. When binding applications on various operating system releases, a binder warning 59 parameter count mismatch on ldiv is produced. This causes no ill effect on the application functionality. Install Tandem IPM T8373AAJ to correct this problem. 3. V5.1 non-native applications require CWIDE for binding. To build non-native applications for V5.1 add the following to the bind SELECT SEARCH $SYSTEM.SYSTEM.CWIDE The SELECT SEARCH is now used to keep the C libraries your MQSeries application uses consistent with your host system. 4. Swap space allocation in documentation On page 51 of the MQSeries for Compaq NonStop Kernel System Administration, the section entitled 'Swap space allocation' should also contain: A way of controlling the swap allocation of MQSeries executables is to alter the MQ Pathway server classes by adding: DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME , SWAP Note: the volume.qmD should be set the same as the MQ serverclass VOLUME attribute. An example using the MQSeries Pathway on page 33: ALTER MQS-EC00, DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $DATA1.P101D, SWAP DATA3 By adding the DEFINE, agent processes created by the EC server will also inherit the defined swap volume thereby creating some scalability of swap utilization when multiple EC server classes are used. 5. UNPAK utility All MQSeries service packs (PTFs) are packaged using a utility called PAK. This means that to install a PTF, UNPAK is required. This can be obtained from the World Wide Web, at the following URL: http://www.bsi2.com//DOWNLOAD-FREE.HTML under the Products for Tandem NSK, compress pak and grep utilities for Guardian section. If this download option does not work, see the latest information on the service and support section of the MQSeries home pages for details of how to obtain UNPAK. 6. CONNAME and TPNAME restrictions for SNA Channels The CONNAME and TPNAME attributes of SNA channels are constructed of several pieces of information using the dot character, "." as a delimiter. Consequently it is not possible to use the dot character in LU names or TP names that are to be configured for SNA channels, even if the underlying communications subsystem allows this, because MQSeries would treat them as delimiters. 7. File system security guidelines The correct file system security is essential for operation on MQSeries for Tandem NSK product. The following guidelines are intended to assist you to plan for and setup the correct file system security environment. - MQSeries is managed (administered) by users in the MQM group. There must always be an MQM group. The installation MUST have been created by a user in the MQM group. - All critical executables in ZMQSEXE will be secured to allow execution only by users in the MQM group. The executables will also be secured with the "progid" flag set, meaning that when executed, they run as the user that owns the file, rather than as the user that executed the program. - The default file system security for the user in the MQM group that owns the installation is assumed to allow read access to all files for all users that are required to be able to access the queue manager. - You can establish more restrictive file system security for a queue manager, for example, if you have a queue manager that can contain message data that must not be readable by any user (other than the MQM user that owns the queue manager) by using the following special administrative procedures: - set the default file system security of the MQM group user to "OOOO", allowing access to files ONLY by the administrative user - create the queue manager as normal - modify the file system security of the following files to allow read access for any local user (at least "AOOO"): ZMQSSYS.MSG ZMQSSYS.MQSINI ZMQSCONV.* D.QMINI D.TRACEOPT D.PRIDB D.PRIDBA D.CCSIDMEM D.QMINIMEM - start the queue manager. Note that the file D.UMQSINI are re-created automatically by the queue manager itself when it starts, and are always given file system security "NCCC", allowing network read access to all users. - An existing queue manager may be converted to this file system security scheme by: - ending the queue manager - changing the default file system security of the MQM group administrative user to "OOOO" - changing the file system security of all files in the queue managers subvolumes to "OOOO" - modifying the file system security of the files listed above to "AOOO", if necessary - restarting the queue manager - if Safeguard is employed with control over disk file access, you must ensure that the files listed above are readable by all users that require access to the queue manager. 8. Linking Applications With the MQSeries Native Static Library (MQMLIBN) When linking applications with the Native Static Library, the link command should link in the C++ Runtime Library (ZCPLSRL). This is illustrated in the sample link script (NMLDSAMP). 9. Compiling and Linking NMCOBOL applications with MQSeries Native Library (MQMLIBN) or MQSeries SRL (MQSRLLIB) on D45 systems. Installation of Tandem IPM R8107AAP or greater is required to resolve CALL or ENTER statements in NMCOBOL applications resulting in errors when calling the MQSeries API. 10. Changes to MQSeries for Compaq NonStop Kernel Quick Beginnings Manual. The following changes have been made to the MQSeries for Compaq NonStop Kernel Quick Beginnings Manual since publication: Chapter 2, Page 14, Example should state:- review the 3 spooler jobs named #instmqm, ...... Chapter 3, Page 24, Example should state:- review the 3 spooler jobs named #instmqm, ...... Appendix D, Page 104, Example should state:- review the 3 spooler jobs named #instmqm, ...... Chapter 5. Troubleshooting Page 31 add bullets: Does the system security allow installation of the MQSeries product using the MQM.MANAGER userid? Are the system SRLs located in the SYSnn subvolume secured or licensed? Chapter 8. using MQSeries Page 50 Insert prior to "Starting a queue manager" paragraph Configuring MQSeries to work with RDF . This task is not normally required on your first pass through this book. To make best use of RDF, you are recommended to customize some of the default configuration settings, as follows: 1. Ensure that RDF is set up with identical volume names on both the primary and backup sites. 2. Ensure that the backup site volume on which the queue manager will be created does not have files in the subvolumes in which the new queue manager will be created. 3. Create the queue manager using crtmqm. 4. Change the TS/MP configuration for the queue manager manually (using PATHCOM) to include the definition of the MQRDF PARAM in all server classes (for example, MQS-EC00). 5. Add the MQRDF PARAM to the TACLCSTM files of all users who will be performing administrative operations on the queue manager (normally, those users in the MQM group only). 6. Start the queue manager using strmqm. 7. Run cleanrdf for the first time to establish a baseline configuration for the nonaudited database files for the queue manager. 8. Verify the basic operation as follows: a. Create a local queue using runmqsc. b. Use a sample program to put a few messages on the queue. c. Use a sample program to retrieve the messages. d. Delete the queue using runmqsc. e. Run cleanrdf. f. Recreate the queue using the same name. During these steps, monitor the RDF backup site. No EMS events indicating file-system errors should be generated. Note: RDF operation is not instantaneous, so it cannot guarantee no message loss. Appendix B. The MQSeries control commands Page 93 upgmqm add to Note: The QMINI file is recreated as part of the upgrade process and most V2201 settings will need to be re-applied. For example Channels stanza MaxChannels and MaxActiveChannels and TCPConfig stanza TCPListenerPort. Appendix C. Setting TACL environment variable for MQSeries for Compaq NSK Page 95 change #SET #PMSEARCH $SYSTEM.ZMQSEXE [#PMSEARCH] to #SET #PMSEARCHLIST $SYSTEM.ZMQSEXE [#PMSEARCHLIST] Page 96 change MQTCPIPPORTNUMBER to MQLISTENPORTNUM Page 97 Queue Server tuning parameter Add to the MQQSSIGTIMEOUT paragraph: "The maximum value is 86400 (24 hours). 11. Changes to MQSeries for Compaq NonStop Kernel System Administration Manual. Chapter 3. Using the MQSeries command sets Page 31 Specifying the distribution of processes across CPUs, add after "The CPU hosts the MQS-QMGRSVR00 server class" The CPU hosts the MQS-CHANINIT00 server class, or The CPU hosts the MQS-CMDSERV00 server class, or Page 34 change CPUS(0,1) to CPUS (0:1) for MQS-CHANINT00 and MQS-CMDSERV00 Page 35 change CPUS(0,1) to CPUS (0:1) for MQS-EC00 Page 38 change SERVER MQS-QMGRSVR to MQS-QMGRSVR00 change CPUS(0,1) to CPUS (0:1) for MQS-QMGRSVR00 Page 39 change CPUS(0,1) to CPUS (0:1) for MQS-REPSVR00 Chapter 4. Managing queue managers Page 43 Insert prior to "Backing up configuration files after creating a queue manager" paragraph Configuring MQSeries to work with RDF . This task is not normally required on your first pass through this book. To make best use of RDF, you are recommended to customize some of the default configuration settings, as follows: 1. Ensure that RDF is set up with identical volume names on both the primary and backup sites. 2. Ensure that the backup site volume on which the queue manager will be created does not have files in the subvolumes in which the new queue manager will be created. 3. Ensure RDF updater processes are running for volume queue manager is to be created on. 4. Create the queue manager using crtmqm. 5. Change the TS/MP configuration for the queue manager manually (using PATHCOM) to include the definition of the MQRDF PARAM in all server classes (for example, MQS-EC00). See Appendix C "Setting TACL environment variables for MQSeries for Compaq NSK" for MQRDF setting. 6. Add the MQRDF PARAM to the TACLCSTM files of all users who will be performing administrative operations on the queue manager (normally, those users in the MQM group only). 7. Start the queue manager using strmqm. 8. Run cleanrdf for the first time to establish a baseline configuration for the nonaudited database files for the queue manager. 9. Verify the basic operation as follows: a. Create a local queue using runmqsc. b. Use a sample program to put a few messages on the queue. c. Use a sample program to retrieve the messages. d. Delete the queue using runmqsc. e. Run cleanrdf. f. Recreate the queue using the same name. During these steps, monitor the RDF backup site. No EMS events indicating file-system errors should be generated. Note: RDF operation is not instantaneous, so it cannot guarantee no message loss. Page 49 Insert prior to Guardian segment IDs used by MQSeries paragraph Control of the termination of an existing channel process and the startup of a new process MQSeries allows multiple channel processes for the same channel name to exist. This may not be the desired functionality for your MQSeries queue manager. Use the AdoptNewMCA entries in the Channels stanza in the QMINI file for the queue manager to disable multiple channel occurrences. AdoptNewMCA= NO|SVR|SNDR|RCVR|CLUSRCVR|ALL If MQSeries receives a request to start a channel but finds that a channel process already exists for the same channel, the existing process must be stopped before the new one can start. The AdoptNewMCA attribute allows you to control the termination of an existing process and the startup of a new one for a specified channel type. If you specify the AdoptNewMCA attribute for a given channel type but the new channel fails to start because the channel is already running: 1. The new channel tries to stop the previous one by politely inviting it to end. 2. If the previous channel server does not respond to this invitation by the time the AdoptNewMCATimeout wait interval expires, the process for the previous channel server is killed. 3. If the previous channel server has not ended after step 2, and after the AdoptNewMCATimeout wait interval expires for a second time, MQSeries ends the channel with a "CHANNEL IN USE" error. You specify one or more values, separated by commas or blanks, from the following list: NO The AdoptNewMCA feature is not required. This is the default. SVR Adopt server channels SNDR Adopt sender channels RCVR Adopt receiver channels CLUSRCVR Adopt cluster receiver channels ALL Adopt all channel types AdoptNewMCATimeout=60|1-3600 This attribute specifies the amount of time, in seconds, that the new process should wait for the old process to end. Specify a value, in seconds, in the range 1-3600. The default value is 60. AdoptNewMCACheck=NAME The AdoptNewMCACheck attribute allows you to specify the type checking required when enabling the AdoptNewMCA attribute. The NAME checking is only relevant setting. The QM and ADDRESS while valid settings will have an adverse functional impact if used and are documented only for completeness. The default is NAME,ADDRESS,QM. Specify one or more values, separated by commas or blanks, from the following: QM This means that channel process should check that the queue manager names match. Do not specify this value. ADDRESS This means that the channel process should check the communications address. For example, the TCP/IP address. Do not specify this value. NAME This means that the channel process should check that the channel names match. The AdoptNewMCA entries in the QMINI file can be changed at any time, though the change does not take effect until the queue manager is restarted. Control of the scan of the channel status table for retrying channels The period of time to wait for the next scan of the channel status table for retrying channels is controlled with the ChanInitDiscInterval entry in the Channels stanza in the QMINI file. By default ChanInitDiscInterval is set to 10 seconds. Modifying the value to low, to 1 for example, may adversely effect the other operations the status process has to perform. The ChanInitDiscInterval entry in the QMINI file can be changed at any time, though the change does not take effect until the queue manager is restarted. Page 53 item 2, change SET LIKE MQS-STATUS00 to SET SERVER LIKE MQS-STATUS00. Page 53 item 3, change RESET SERVER PROCESS $ -p A -u MQSEC.FRED The MQSeries OAM authority is added to the file sharing group with: SETMQAUT -m -t qmgr -g TESTSEC1 +connect SETMQAUT -m -t queue -g TESTSEC1 -n +put To assign individual OAM authority use the file sharing member not the group (MQSEC) or principal (A). Adding to the group MQSEC or principal A will assign OAM authority to all groups, Safeguard administrative and file sharing. Page 141 The OAM Database, change The primary key is the object name plus object type. to The primary key is the object name plus object type and sequence number. Page 142 Change the table with Object Name, Type, #Auth Entries, Auth Entries to Object Name, Type, RecSeqNum, #Auth Entries, Auth Entries QUEUE AUTH 1 0 2 PAYROLL ... Add after "object required by the OAM." A RecSeqNum field (2 bytes) with a sequence number for multiple records of the same object and type. Change The #Auth Entries field (4 bytes)" to The #Auth Entries field (2 bytes)" Chapter 12. Recovery and restart Page 171 item 2c, change "All files in the S subvolume." to All files in the S subvolume except SYNCHIDX. Chapter 13. Configuration files Page 175 After TCPListener add: Queue Manager Server Repository Server Page 176 Add to Channels prior to "For more information" The channels stanza contains entries (AdoptNewMCA) that can be used to control the termination of an existing channel process and the startup of a new process for a specified channel type. Chapter 17. The MQSeries control commands Page 232 altmqfls add the following to the Syntax: --qsize (QPriExt,QSecExt,QMaxExt,OPriExt,OSecExt,OMaxExt) --maintain ON / OFF add the following to the Optional parameters: --qsize (QPriExt,QSecExt,QMaxExt,OPriExt,OSecExt,OMaxExt) Specifies the Compaq NSK file extents for the queue manager message files associated with the MQSeries queue object. QPriExt is value for the queue file, Qxxxxxxx, primary extent QSecExt is value for the queue file, Qxxxxxxx, secondary extent QMaxExt is value for the queue file, Qxxxxxxx, maxextents OPriExt is value for the queue overflow file, Oxxxxxxx, primary extent OSecExt is value for the queue overflow file, Oxxxxxxx, secondary extent OMaxExt is value for the queue overflow file, Oxxxxxxx, maxextents --maintain ON / OFF This options allows partitioning of a MQSeries queue Enscribe file(s) without ending the queue manager. Queue partitioning is allowed only on Local queues. ON Disables the MQSeries local queue object for use. Applications attempting a MQOPEN will be rejected with a MQRC_UNKNOWN_OBJECT_NAME (2085) until a maintain OFF is executed. All non-persistent messages are removed when this option is used as the queue is unloaded from the Queue Server. All persistent messages should remain provided customers have not removed them during their maintenance operations. The macro PARTIT located in ZMQSSMPL is provided to aid in file partitioning. OFF Enables the MQSeries local queue object for use after maintenance operations have been completed. Applications will now be allowed to open the object. Page 233 altmqfls Replace --msgofsubvol MsgOvflSubvol paragraph with Specifies the volume and subvolume where the queue server creates new message overflow files for the queue. All queues will initially use their queue manager message subvolume by default. add the following to -- meascount The COUNTER defined in MEASURE must be an ACCUM type. To view the COUNTER data as a value as opposed to a percentage in MEASURE use SET REPORT RATE OFF. Note that the measurement should be started prior to opening a MQSeries queue. The initialization of the COUNTER data is done when a queue is opened. If a measurement is stopped while the MQSeries queue is open all openers of the MQSeries queue must be closed and the queue then needs to be opened and closed to disable the QServer measurecounter so the next time MEASURE is started the correct CURDEPTH is initialized. Page 263 endmqm The arguments for ENDMQM are incorrect. The Queue Manager name is a mandatory argument, not an optional one. If no name is specified a usage message will be displayed, e.g.: TACL> endmqm Usage: endmqm [-z] [-c | -i | -p] QMgrName TACL> Page 271 runmqlsr change Syntax -t tcp to -t Protocol change Optional parameters: -p, change PARAM MQPORTNUMBER to PARAM MQLISTENPORTNUM -tcp, change PARAM MQPORTNUMBER to PARAM MQLISTENPORTNUM change -t tcp to -t Protocol add to -t Protocol Identifies the transmission protocol to execute the listener as and may be one of the following: tcp TCP/IP transmission protocol lu62 SNA LU62 as the transmission protocol for SNAX/ICE setting up the LU62 SNA Listener process. change "This is the only valid value.." to "The tcp protocol is the default transmission protocol on MQSeries for Compaq NSK." add after tcp paragraphs: lu62 Identifies SNA LU62 as the Transmission protocol Note that the LU6.2 Listener cannot be run from TACL, but only from the SNAX/ICE Pathway. See Appendix M Setting up communications for configuration of SNAX or ICE SNA listener. Page 289 upgmqm add to Note: The QMINI file is recreated as part of the upgrade process and most V2201 settings will need to be re- applied. For example Channels stanza MaxChannels and MaxActiveChannels and TCPConfig stanza TCPListenerPort. Appendix C. Setting TACL environment variable for MQSeries for Compaq NSK Page 299 change #SET #PMSEARCH $SYSTEM.ZMQSEXE [#PMSEARCH] to #SET #PMSEARCHLIST $SYSTEM.ZMQSEXE [#PMSEARCHLIST] Page 301 Queue Server tuning parameter Add to the MQQSSIGTIMEOUT paragraph: "The maximum value is 86400 (24 hours). Appendix F. MQSeries and Compaq NonStop Server for Java Page 309 Change "The Product SRL ..." to "The Product SRL MQSRLLIB, from the Guardian ZMQSLIB subvolume" Change "Java binding ..." to "Java binding archive libMQSESSION.a for NSJ2 from /opt/mqm/java/lib/NSJ-2.0 or for NSJ1.5 opt/mqm/java/lib/NSJ-1.5" Change "The MQSeries samples ..." to "The MQSeries samples directory (/opt/mqm/java/samp) contains two sample make files:" Change "MakeJVM.smp" to "Makefile.JVM" Change "MakeJava.smp" to "MQSample.java A sample Java application" Appendix I. Building and running applications Page 323 Using MQGET Wait Interval and Channel DISCINT and HBINT remove references to MQTRANSACTIONLIFE the parameter is no longer valid with the implemention of DCR R2683. Appendix K. MQSeries for Compaq NSK sample programs Page 336 Building C++ samples Native (using SRL MQSRLLIB) change Usage: NMBLDSCP to Usage: NMBLDSCP MQSeries Private SRL volume Page 339 Building sample programs on OSS add The readme.txt file contains information on building the OSS sample programs using the SRL MQSRLLIB or static library MQMLIBN. Appendix L. User Exits Documentation Update for MQ_LOAD_ENTRY_POINT_EXIT The ZMQSSMPL subvolume contains AMQSLXP0 which is a more illustrative example of an MQ_LOAD_ENTRY_POINT_EXIT than that shown on Page 345 of the System Administration manual. Appendix M. Setting up communications Page 353 the Dispatch TP example should be modified: ADD TP , PROCESS <$process>, SERVERCLASS, & PROTOCAL DISPATCH Page 354 Figure 47. Sample MQSeries SNAX setup file (Part 2 of 3) should be modified: SET SERVER PARAM MAXAPPLIOSIZE 32000 SET SERVER PARAM DATAPAGES "100 E" [SET SERVER PARAM CONFIG APCCFG] Page 355 the Add of the TP in NOF syntax should be modified: ADD TP , PROCESS , SERVERCLASS, PROTOCAL DISPATCH, & [,