BEA MessageQ for OpenVMS
Release Notes for
Version 4.0A

Contents (summary)

• Chapter 1 New and Changed Features
• Chapter 2 Corrections to Known Problems
• Chapter 3 Known Problems or Restrictions
• Chapter 4 Corrections To Documentation
• Tables

Contents

• ---

  Chapter 1 New and Changed Features
  • 1.1 Before You Install MessageQ Version 4.0A
  • 1.2 New and Changed Features for MessageQ Version 4.0A
    • 1.2.1 Changes to the Installation Procedure
    • 1.2.2 Changes to the MessageQ Include Files
    • 1.2.3 Message Broadcasting on All Platforms
    • 1.2.4 Enhancements to Ethernet Message Broadcast Protocol
      • 1.2.4.1 Configuring Optimized Ethernet Mode
      • 1.2.4.2 Dual-rail Mode
      • 1.2.4.3 RP/ETH Retransmission Protocol
      • 1.2.4.4 RP/ETH Receive silo rules
      • 1.2.4.5 RP/ETH Examples
      • 1.2.4.6 RP/ETH Sequence of operation
      • 1.2.4.7 RP/ETH Configuration
    • 1.2.5 AVAIL/UNAVAIL Messages Now Work Over Networks With Cross Group Routing
    • 1.2.6 Self-Describing Messaging (SDM)
    • 1.2.7 Support for Large Messages
    • 1.2.8 Changes to The Global Buffer Allocation Algorithm
    • 1.2.9 Dynamic Binding of Queue Addresses to Local and Global Queue Name
    • 1.2.10 Global Naming
    • 1.2.11 Changes to MessageQ Application Programming Interface (API) Functions
      • 1.2.11.0.1 PAMS_ATTACH_Q and PAMS_LOCATE_Q
      • 1.2.11.0.2 PAMS_LOCATE_Q Can be Called Prior to Attach
      • 1.2.11.0.3 Changes to The Messaging Routines to Enable SDM Encoded Messages
      • 1.2.11.0.4 PAMS_PUT_MSG Eliminates The Restriction of an MRQ as a Response Queue
    • 1.2.12 Enhancements to Message Recovery Services
    • 1.2.13 Automatic Synchronized Cluster Group Failover
    • 1.2.14 Distribution of Documentation Online
    • 1.2.15 Runtime Loading of PAMScript Symbols
    • 1.2.16 Start and Stop Commands for Queues
    • 1.2.17 Start and Stop Commands for Client Library Services (CLS)
    • 1.2.18 Added Support For Process Software Corporation (PSC) TCPware
    • 1.2.19 Changes to Group Initialization File
    • 1.2.20 Graceful group shutdown
    • 1.2.21 Queue names are now NULL terminated
    • 1.2.22 MessageQ Client for OpenVMS support
      • 1.2.22.1 Using the OpenVMS MessageQ Client with the Server kit installed
    • 1.2.23 PAMS V2.5 compatible DECnet object is no longer supported
    • 1.2.24 Client Library Server no longer supports same-client reconnect
    • 1.2.25 MessageQ for OpenVMS has been tested to be fully Year 2000 compliant
    • 1.2.26 CUSTOMIZE command procedure updated to ask before purging files

• ---

  Chapter 2 Corrections to Known Problems
  • 2.1 Message Recovery Services (MRS)
    • 2.1.1 Recoverable Messaging Intermittently Stops to Older MessageQ Versions
    • 2.1.2 Corrections to Target Presentation Quota And Journal File Cleanup
    • 2.1.3 Interoperability Problems with MessageQ for OpenVMS V2.X Systems
    • 2.1.4 Problems When MRS Encountered File Access Failures
    • 2.1.5 MRS Continually Logs "DQF write error"
    • 2.1.6 MRS Did not Close all Files When Journaling Was Disabled
    • 2.1.7 SAF Message Traffic Stalled And Messages Lost Between OpenVMS and UNIX/Windows NT
    • 2.1.8 SAF Messages Marked As PAMS__POSSDUPL When Sent to Pre-V3.0 Groups
    • 2.1.9 SAF Messages Marked As PAMS__STALE
    • 2.1.10 SAF Messages Delivered Out Of Order
    • 2.1.11 SAF Messages Incorrectly Flagged As Incomplete
    • 2.1.12 Internal MRS Traffic Caused User Message Sends To Timeout
    • 2.1.13 MRS Server Sometimes Failed To Unblock Senders
  • 2.2 MessageQ Application Program Interface (API)
    • 2.2.1 PAMS_GET_MSGW() Fails to Wakeup on Multi-reader Queue (MRQ) Reads
    • 2.2.2 PAMS_ATTACH_Q() to a Temporary Queue Will Hang The Process If The Temporary Queues Are Exhausted
    • 2.2.3 PAMS_PUT_MSG() Hangs
    • 2.2.4 Q_NOTIFY_RESP Message Not Endian Converted
    • 2.2.5 Secondary Queue Names are Sometimes Deleted
    • 2.2.6 PAMS_ATTACH_Q()/PAMS_DETACH_Q() Could Cause The Process To Abort With An Access Violation
    • 2.2.7 PAMS_PUT_MSG() Returns PAMS__NOACCESS
  • 2.3 Communication (COM) Services and Link Drivers
    • 2.3.1 Inbound Link Connection Request Is Rejected
    • 2.3.2 COM Server Generates Unneccesary Tracebacks
    • 2.3.3 COM Server Aborts With an ACCVIO
    • 2.3.4 COM Server Fails to Spawn Subprocesses
    • 2.3.5 COM Server Immediately Drops New Connections
    • 2.3.6 COM Server Fails with an ACCVIO During Startup
    • 2.3.7 COM Server Becomes Compute Bound on Alpha Processors
    • 2.3.8 Adding Cross-Group Entries Following Startup are not Seen
    • 2.3.9 COM Server Logs Wrong Group Number on "Forcing link down" Events
    • 2.3.10 Link Driver Logs "Protocol failure" Errors
    • 2.3.11 COM Server Memory Leak While Processing UNDECLARE_SQ Message
    • 2.3.12 DECnet/OSI Link Transitions Not Seen By The DECnet Link Drivers
    • 2.3.13 COM Server Did Not Handle Message Visit Counts Correctly
    • 2.3.14 DECnet Link Ownership Sometimes Not Passed Correctly Between DECnet Link Drivers
  • 2.4 General
    • 2.4.1 Process termination via CONTROL-Y Followed By The DCL STOP Command Causes a System Level BUGCHECK
    • 2.4.2 Message Byte Counters Overflowed On Fast AXP Processors
    • 2.4.3 Multiple Attachers Were Allowed To Access The Same Primary Queue
    • 2.4.4 Loader Not Validating Permanent Queue Range
    • 2.4.5 Link Management (LINKMGT_REQ) Connect Command Not Handling The "reconnect timer" Correctly
    • 2.4.6 Cross-Group Table Entries Ordering Restriction
    • 2.4.7 MessageQ Command Procedures Now Handle "<>" Directory Syntax
    • 2.4.8 DMQ$STARTUP.COM Now Allows a User Settable Timeout
    • 2.4.9 DMQ$SCRIPT Logical Name Limited To 32 Characters
    • 2.4.10 Ethernet User Callback Returned DMQCS__AREATOSMALL Back To PAMS_GET_MSG()
    • 2.4.11 AVAILMSGDEF.H Included Unknown .H File
    • 2.4.12 Product Installation Failed During Link of CLS Server
    • 2.4.13 Conversion Utility Failed to Convert RTO User Directory when DEV License Loaded
  • 2.5 Client Library Services (CLS)
    • 2.5.1 Single-client CLS does not properly close UCX BG devices
    • 2.5.2 Exits Following an "unexpected signal 10" Error
    • 2.5.3 CLS Server Reports "Endpoint Is Probably In Use"
    • 2.5.4 Client Task ID Incorrectly Logged As Negative Numbers
  • 2.6 Interoperability
    • 2.6.1 AVAIL Service Interoperability Between OpenVMS V3.2 and UNIX/Windows NT Was Not Working Correctly

• ---

  Chapter 3 Known Problems or Restrictions
  • 3.1 Limitations for the Version 4.0A Kit
    • 3.1.1 DMQ$CVT.COM uppercases node name in %XGROUP section
    • 3.1.2 Routing limitations with AVAIL and SBS Services
    • 3.1.3 Client Applications Using OpenVMS-based CLS via Temporary Queue Unable to Use Monitor Utility
    • 3.1.4 MessageQ for OpenVMS Maximum Queue Number
    • 3.1.5 Known Problem With DECnet Cluster Aliases
    • 3.1.6 Known Problem with Temporary File Deletion
    • 3.1.7 Sending Messages With New Delivery Modes to Older MessageQ Groups
    • 3.1.8 Cross-group AK_CONF/UMA_SAF is Downgraded to NN_DQF/UMA_SAF
    • 3.1.9 Restriction on Using OpenVMS Alpha Version 7.0 64-bit Addressing
    • 3.1.10 POSIX and MessageQ
    • 3.1.11 Minimum Version of MessageQ for MRS Interoperability
    • 3.1.12 Startup of MessageQ Will Fail if The Default Directory is Invalid
    • 3.1.13 Script Parsing Does Not Recognize Group Names That Start With a Number
    • 3.1.14 SBS Ethernet broadcasting limited to 32K messages
    • 3.1.15 PAMS API calls are NOT thread safe
    • 3.1.16 CONF and ACK delivery modes may only be confirmed by the receiving process
    • 3.1.17 P_ENTRY.H include file path usage for sys/types.h with the VAXC compiler
    • 3.1.18 Unsupported delivery mode and undeliverable message action (UMA) combinations
    • 3.1.19 PCJ large message journaling restriction
    • 3.1.20 Restriction on dynamic updating of Message Byte Quotas
    • 3.1.21 Problem with x_putbig.c examples program
    • 3.1.22 Problem with linking examples program
    • 3.1.23 Example programs

• ---

  Chapter 4 Corrections To Documentation
  • 4.1 Corrections to the Installation and Configuration Guide for OpenVMS
    • 4.1.1 Addition to the "Running the CUSTOMIZE command procedure" section
    • 4.1.2 Correction to "Modifiable Parameters in the Group Initialization File" Table
  • 4.2 Corrections to the Programmer's Guide
    • 4.2.1 Correction to LINKMGT_REQ/LINKMGT_RESP "Message Data Fields" Table
    • 4.2.2 Correction to SBS_SEQUENCE_GAP Message Description
    • 4.2.3 Automatic AVAIL Deregistration of Temporary Queues on OpenVMS Only
    • 4.2.4 Default Selection Filter Always Reads from the Timer Queue First
    • 4.2.5 Reusing handles after augmenting messages
    • 4.2.6 Addition to the SBS_STATUS_REQ Message description
    • 4.2.7 Correction to PAMS_EXIT API description

• ---

  Tables
  • 1-1 name_space_list settings forpams_attach_qandpams_locate_q