Subject: M6-WMQ 6.7.4.2 for z/OS
Date: 05-Dec-2025
File: M6WMQ_6.7.4.2_ZOS.zip

Includes

V6742.LOAD.XMI — M6-WMQ load modules
V6742.JCL.XMI — M6-WMQ JCL files

IMPORTANT

This package contains a full installation of M6-WMQ, including agent, event publisher, message server and utilities.

Prerequisites

z/OS V2.1 or higher installed
IBM WMQ v8.x or later installed
TCP/IP Services

Installation Steps

Stop all Nastel processes if you have an existing installation.
Back up your current z/OS APWMQ data-set installation, if one exists.
Restore customized configuration files (not applicable for this version).
Unzip the distribution file on a PC.
Upload the JCL and LOAD .XMI files to z/OS as described in Navigator Components Installation Guide, Section 5.5.2: Transferring and Restoring Data Sets.
Receive the uploaded .XMI files into a new set of PDS (partitioned data sets).

Copy the members from the new JCL and LOAD libraries into the appropriate execution data sets (for example: NASTEL.M6WMQ.V674.PROD.XXX).

LOAD Library Members
- NSQMQ — MQ agent
- NSQCSUB — MQ agent sub-task
- NSQSTOP — Utility to stop agent, event publisher, message server, and trace control
- NSQPUB — Event publisher
- NSQPSUB — Event publisher sub-task
- NSQMSG — Message server
- NSQMSRV — Message server sub-task
- NSQMMFCL — Message management CL utility
- NSQMSGF — Message management queue-to-file load/unload CL utility
- ENDMCS — Message server stop CL utility
- NSQMQSC — MQSC CL utility
JCL Library Members
- M6$674 — Version marker
- RDME674 — Readme file
- NSQMQ — Defines flat-file data set used by the agent for CSQUTIL output
- 20+ additional files — Start/stop APWMQ jobs, INI configuration files, and readme files.
  Refer to Table 5-2: Contents of the M6WMQ.JCL Data Set in the Navigator Components Installation Guide.
Restore your customized configuration files, if applicable.
Edit or merge your existing custom JCL with the new NSQMQ JCL:
- Update the high-level qualifiers (++hlq++) and MQ series qualifiers (++mqser++) to match your environment.
- Merge any additional custom JCL lines from your previous configuration.
  Refer to Fix 21932 for details.
Create the data set ++hlq++.DATA.FLAT.
Refer to Fix 21932.
Start the Nastel processes to complete the installation.

APWMQ

6.7.4.2 for z/OS

WGSCM-730: [WMQ Agent] OS Agent encountering 80-character limitation in MQGROUP DD

Old Fix Packs

APWMQ 6.7.4.1 for z/OS

WGSCM-474: z/OS Agent Fails to Register if Workgroup Server Name has Dash character

APWMQ 6.7.4 for z/OS

0021932: [WMQ Agent] Cannot get z/OS CSQUTIL output when called while running Explorer/Navigator command MQSC Apply Script file.
- Navigator and Explorer GUIs will now see reply details from MQSC command processing by CSQUTIL, for both successful and failed commands.
- If the command failed, the exact lines with the syntax errors will be displayed, not just the message 'MQSC command failed'.
- Associated with this fix is a changed NSQMQ JCL for starting the agent.
- It has an added data definition (DD) statemet with a ddname CSQOUT to define a data set <apwmq_hlq>.DATA.FLAT that will be used by the agent when submitting MQSC commands to the CSQUTIL utility program.
- CSQUTIL will write its output to that file.
- As part of installing the fix, please create the DATA.FLAT data set as stated in the NSQMQ JCL with these properties:
  - Data set name: <++hlq++>.DATA.FLAT
  - Organization=PS (physical sequential)
  - Record format=VBA (variable blocked ANSI carriage control)
  - Block size=6144
  - Record length=120
0022936: [Command Utilities] nsqmqsc generated MQSC script for z/OS qmgr has has problems and fails in spots when imported on z/OS by CSQUTIL
0023102: [WMQ Agent] z/OS agent missing tracing of discovery reply messagess
0023134: [WMQ Agent] Some topics do not appear in the z/OS agent discovery trac
0023777: [WMQ Agent] Error creating a subscription on z/OS
0024192: [WMQ Agent] Message server prints no error message if invalid queue manager is given
0024732: [Installation] JCL file 'NSQMQ' to start z/OS agent missing DD (data definition) lines for reason code and severity code files
0024734: [Command Utilities] Port number option -snnnn alone to z/OS NSQSTOP ca exit without a message
0024736: [WMQ Agent] z/OS agent can get into condition that makes it difficult stop or cancel the job
0025863: [WMQ Agent] z/OS agent discovery occurs at 10 min intervals instead of Discovery Interval defined in the node properties
0025864: [WMQ Agent] z/OS agent does not always action shutdown command from AP Explorer, Navigator or nsqstop
0025874: [WMQ Agent] Null strings in MQSC commands submitted by z/OS agent to z qmgr cause error 'required parameter for xxx not specified'
0025877: [Common Engine] z/OS agent trace message "UNKNOWN PCF Attribute(1009): unable to print" while printing MQCMD_INQUIRE_CHANNEL reply message
0025885: [WMQ Agent] Apply Script using nsqmqsc dump output file with 1153 comm displays output with only 244 commands processed
0026058: [WMQ Agent] Missing PCF cmd reply traces in agent log after each alter filter check that indicates 'no filtering needed'
0026089: [WMQ Agent] MQSC snapshot written by z/OS agent to CSQUTIL gets trunca to length of NAMES and NAMELIST param line
0026090: [Message Server] z/OS message server prints no error message if an inv queue manager is given
0026105: [Publisher] Extraneous characters 'CDLL' (or other junk) in z/OS event publisher startup message
0026110: [Publisher] Publisher crashes while stopping after a nsqstop command
0026119: [WMQ Agent] Nav command Subscription > Rename to z/OS agent fails with "unknown_object_name"

APWMQ 6.5.9.2 for z/OS (01-June-2020)

0019109: [WMQ Agent] Print PCF param IDs as name strings in agent and workgroup server PCF traces
0019976: [WMQ Agent] Shared queues not showing up in ZOS node in APWMQ Explorer
0021298: [WMQ Agent] Ensure all admin messages are set as non-persistent
0021776: [WMQ Agent] z/OS agent errors while executing MQSC script to define local queues