============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2013 All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ============================================================================== ============================================================================== README for IBM(R) WebSphere(R) Business Integration for Financial Networks for Multiplatforms V3.1.1 Message Management PTF UK96830 for APAR PM91176 Driver level: 3384 Date 2013-09-30 ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Installation E APAR details F Other changes G Known issues A. About this document ---------------------- Only the online version of this readme document is current. Before you install the corresponding PTF, download the latest version from: http://www.ibm.com/software/integration/wbifn/support Download the latest version of the WebSphere BI for FN product documentation from: http://www.ibm.com/software/integration/wbifn/library The structure of WebSphere BI for FN readme documents is identical for all PTFs. Sections that are not applicable are left blank. If you install more than one PTF at a time, combine the readme documents by merging the contents of each section. During the installation phase of this PTF your system cannot process messages. This readme document uses the following variables: The installation directory of WebSphere BI for FN. The directory /opt/IBM is used in examples. The customization directory. The directory /var/dni_03_01/cus is used in examples. The deployment directory. The directory /var/dni_03_01/cus/depdata is used in examples. The name of the WebSphere BI for FN instance. The name INST1 is used in examples. The name of the organizational unit. Depending on the context, this might be SYSOU, DNFSYSOU, or the name of a business OU. The names of users, groups, files, and directories are the same as those used in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization, SH12-6942. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM91176 MM SWIFT SR2013: UPDATED NAK CODES FOR SR2013 CHANGES PM95265 MM INPUTENABLED ATTRIBUTE CONFUSING IN DNQCPCQO.CLI SCRIPT PM96602 MM POTENTIAL DEADLOCKS WHEN ACTING ON 'ALL MSGS IN QUEUE' PM96618 MM THE MER AUTO-COMPLETE FUNCTION FOR THE DESTINATION ADDRESS NEEDS TO BE ENHANCED Additional functional changes: - Prevent actions to be selected in message list - Entitle admin to change local address - Enhancement to edit multi-line fields - Enhancements to message validation - Automatic completion of destination address - Show reference column for templates - Import of FIN templates added to Sequential data facility (SDF) Documentation updates: The following manuals have been changed: - Messages and Codes - System Administration - Application Programming - Message Entry and Repair Facility User's Guide The following modules have been changed: /dnqv311/admin/appsrv/res/dnq.app.main.ear /dnqv311/admin/data/DNQER.xml /dnqv311/admin/data/dnqcecoo.cli /dnqv311/admin/data/dnqcpcdo.cli /dnqv311/admin/data/dnqcpcqo.cli /dnqv311/admin/data/dnqcpcso.cli /dnqv311/admin/data/dnqczcar.cli /dnqv311/admin/data/dnqczcat.cli /dnqv311/admin/data/dnqczcah.lst /dnqv311/admin/data/dnqczcob.cli /dnqv311/admin/data/dnqczeob.cli /dnqv311/admin/toolkit/com.ibm.dnq.api.jar /dnqv311/admin/toolkit/dnq.project.interchange.zip /dnqv311/admin/toolkit/DNI_DnqErCommon.zip /dnqv311/run/classes/dnqcbsdf.jar /dnqv311/run/classes/dnq.common.jar /dnqv311/run/classes/dnq.header.jar /dnqv311/run/data/dnqczcar.cli /dnqv311/run/data/dnqczcat.cli /dnqv311/run/data/dnqczcah.lst /dnqv311/run/data/dnqczcob.cli /dnqv311/run/data/dnqczeob.cli /dnqv311/run/flows/DNQ_K_FIN1.bar /dnqv311/run/flows/DNQ_K_FIN2.bar /dnqv311/run/flows/DNQ_K_MX1.bar /dnqv311/run/flows/DNQ_K_UAR.bar /dnqv311/run/msg/dnqcbmsg.cat /dnqv311/run/msg/DNQB_Msg.properties /dnqv311/run/msg/dnqcemsg.cat /dnqv311/run/msg/DNQE_Msg.properties /dnqv311/run/res/dnqcbevt.xml /dnqv311/run/res/dnqceevt.xml /dnqv311/run/samples/dnqcbsdf.sh C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Ensure that all previously prepared deployment instructions were carried out. 2. Ensure that all previous CDD changes were implemented using the CDP. To check this, log on to AIX on the customization system as a customizer (UCUST1) and enter the following command on your customization system: /dniv311/admin/bin/dnicdpst -i -cdefs where The name of the WebSphere BI for FN instance The name of the customization definitions directory as specified in the CDP ini file, for example: /var/dni_03_01/cus/defs If the response to this command indicates that a customization operation is still pending and it was carried out in: - Customization mode (dnicdp), implement the pending operation before continuing. - Migration mode (dnicdpm): - Ensure that you have not yet shared the files contained in this or any other PTF as described in section D5 step 2. - Implement the pending operation before continuing. 3. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 4. Ensure that all configuration administration changes have been deployed. To check this, enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou % -qo amorz > list -cos % -qo amorz > list -ct % -qo amorz Each list command should result in 'No [OU/COS/CT] match search criteria'. 5. Ensure that all security administration changes have been approved. To check this, enter the following commands for each OU: dnicli -s DNI_SECADM -ou > list -ro % -qo mor [only for SYSOU] > list -user % -qo mor Each list command should result in 'No roles found that match specified criteria'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UK96829 for APAR PM91175 (Base 3.1.1.14, SWIFT SR2013: UPDATE PTF FOR WEBSPHERE BI FOR FN MESSAGE VALIDATION) - UK95620 for APAR PM90826 (MM 3.1.1.10, SWIFT SR2013: MESSAGE MANAGEMENT UPDATES FOR SWIFT SR2013 CHANGES) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MB application developer (uwmbad1) - WebSphere MB administrator (uwmba1) - WebSphere Application Server operator (uwaso1) - WebSphere Application Server administrator (uwasa1) - First WebSphere BI for FN system configuration administrator (sa1) - Second WebSphere BI for FN system configuration administrator (sa2) - First WebSphere BI for FN security administrator (ua1) - Second WebSphere BI for FN security administrator (ua2) D. Installation --------------- D1. Stopping all sessions and services you use ---------------------------------------------- Stop all sessions and services, for example: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Close MSIF SnF input and output channels. - Release SWIFTNet SnF queues. - Stop the MSIF Message Transfer service. - Stop the Enhanced InterAct service. - Close all dnicli sessions. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D2. Stopping all application servers ------------------------------------ Stop all application servers. D3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. D4. Backing up your system -------------------------- We recommend to backup your AIX LPAR so that in case of migration issues you can revert to your previous system setup and continue to process workload. D5. Installing PTF by InstallAnywhere ------------------------------------- 1. Install this PTF using IAW based on the chapter "Installing WebSphere BI for FN" in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization, SH12-6942. Please be aware of the directory containing the installation data for this PTF has changed compared to the directory documented in this chapter, use the path Disk1/InstData/NoVM instead of Disk1/InstData/VM. 2. Ensure that the group ownership of the /dnqv311/admin directory and all of its subdirectories and files, is set to group dniadmin. To do this, enter the following command in AIX: chgrp -R dniadmin /dnqv311/admin 3. Set the group ownership of the runtime directories and its files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dnqv311/run D6. Steps on a customization system ----------------------------------- To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: 1. Log on to AIX on the customization system as a customizer (ucust1). 2. Change to the customization directory: cd 3. Run your customization profile: . ./dnicus_ 4. Start the CDP in migration mode and use the following commands to migrate customization data: dnicdpm -i > export cdd/_UK96830.cdd > import cdd/_UK96830.cdd > prepare This step updates the customized administrative scripts in the directory '//admin' and generates deployment data for migration of the run-time system for the following resource classes: - CFGPF * instructions and files required to update the WebSphere BI for FN enterprise applications running in the application server Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the step D7. 5. Implement the customization definition data and quit the CDP session: > implement When the message "DNIZ9013I: Current Definition file already exists." is displayed enter 'y' to continue. > quit D7. Following the deployment instructions created in step D6 ------------------------------------------------------------ Follow the deployment instructions that were created in step D6 with the following exception: - do not execute the instructions provided for resource class CFGPF now; you will use them in step D13.3. D8. Additional activities ------------------------- NOT APPLICABLE. D9. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. D10. Customize BAR files when using mqsideploy or the Toolkit to deploy them ---------------------------------------------------------------------------- Backup the BTD repository ------------------------- NOT APPLICABLE. Customize BAR files ------------------- Perform this step only if you use mqsideploy or the Toolkit to deploy broker archive (BAR) files manually. If you use the BAP (dniczbap) to automatically deploy the BAR files, skip this step and later deploy the BAR files directly as described in step D11.2.2. If you are unsure which method to use, use the same method that you used when you initially created your instance as described in "Planning, Installation, and Customization". To customize the BAR files for manual deployment: 1. On the runtime system on which you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory to which you have read and write access and that has at least 35MB of free space. This is the directory in which dniczbap will store the customized BAR files. 3. The component to which the BAP deploys message flows depends on which version of WebSphere Message Broker is used: - For V6.1, the BAP deploys message flows to the configuration manager. - For V7, the BAP deploys message flows to the broker. Sometimes, the BAP cannot connect directly to this component, for example, when you use Broker V6.1 and the configuration manager is located on Windows. How you customize the BAR files depends on whether the BAP can connect to this component: a. If a connection is not possible, issue the following command to customize all BAR files: dniczbap -cmd prepare -all -dir where represents the output directory created in step 2. b. If a connection is possible, ensure that the configuration manager (if using Broker V6) and the brokers are running, and that no flows or execution groups are stopped. Issue the following command to cause the BAP to identify the BAR files that are to be updated: dniczbap -cmd prepare -update new -dir where represents the output directory created in step 2. Regardless of which method (a or b) you use, each of the customized BAR files in the output directory has a name of the form: ....bar where The name of your instance. The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. 4. If you performed step 3.a, identify the BAR files that are listed in section "B. Summary of changes" and delete all other BAR files from the output directory. 5. Transfer, in binary mode, the customized BAR files in the output directory to the Toolkit or to the system on which you will later issue the mqsideploy command. 6. If you will use the Toolkit to deploy the message flows, import the customized BAR files. D11. Redeploy updated BAR files ------------------------------- Deploying the WebSphere BI for FN BAR files that are delivered in this PTF updates the message flows that run in the broker. For a list of flows contained in each BAR file, refer to "Planning execution groups" section of "Planning, Installation, and Customization". Each WebSphere BI for FN message flow has a suffix that represents its version. For example, the flow DNI_SYSADM_1141 has the version 1141. The version of a flow corresponds to the number of the PTF that most recently updated it. Refer to the header of this readme to determine the PTF number of this PTF. To deploy BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). D11.1 Deploy new message flows - - - - - - - - - - - - - - - NOT APPLICABLE. D11.2. Update existing message flows - - - - - - - - - - - - - - - - - - If you already prepared the customized BAR files as described in step D10, proceed with step D11.2.1; otherwise, proceed with step D11.2.2 D11.2.1 Deploying the BAR files customized in step D10 - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use the Toolkit or the mqsideploy command to manually deploy the BAR files. Remove the old versions of the message flows that have been updated by the BAR files you deployed. If you neglect to do this, two different versions of the flows will run simultaneously with unpredictable results. D11.2.2 Deploying BAR files when step D10 was not performed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use the BAP (dniczbap) to customize and automatically deploy the BAR files: 1. Ensure that: - The configuration manager is running (applies only for Broker V6.1) - The brokers are running - No flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation. 2. On the runtime system where you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 3. Ensure that you have at least 35 MB of free space in the current directory. 4. Issue the following command: dniczbap -cmd prepare -update new -deploy 5. Issue the following command to verify that all previous versions of the updated message flows were removed successfully: dniczbap -cmd check The result should be: DNIZ1314I: No problems detected. If you receive the message DNIZ1313E follow the instructions provided in the user response to correct the problem. D11.3. Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D12. Migrating configuration data --------------------------------- D12.1 Generating configuration data migration scripts ----------------------------------------------------- To prepare the migration of configuration entities: 1. On the runtime system on which the message broker runs, log on to AIX as the system configuration administrator, for example, sa1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 3. Switch to this directory and enter the following command: dnfczmlc.sh -i [-dual YES|NO] [-to timeout] where: -i The name of the instance. -dual YES|NO Specifies whether files are to be created for a system that uses dual authorization for SYSOU. The default is -dual YES. Specify -dual NO only if dual authorization is to be turned off for both DNI_SYSADM and DNI_SECADM in SYSOU at the time when the created files are executed. Whether dual authorization is switched on or off for other OUs is irrelevant. -to timeout The number of milliseconds that the CLI waits for a response to this command before it issues an error message. The default is 100000 (100 seconds). It must be a whole number between 20000 and 9999999. Note: This command starts a long-running task that might take several minutes to complete. Check the file dnfczmlc.log to ensure that it completed successfully. The program dnfczmlc creates the following CLI command files: If dual authorization is not used (-dual NO): 1. dnfczmlc_2_sa_ent_all.cli 2. dnfczmlc_3_ua_cre_ro_all.cli If dual authorization is used (-dual YES): 1. dnfczmlc_5_sa_cre_ct_com.cli 2. dnfczmlc_5_sa_cre_ct_dep.cli 3. dnfczmlc_6_sa_cre_co_com.cli 4. dnfczmlc_6_sa_cre_co_dep.cli 5. dnfczmlc_8_ua_cre_ro_com.cli 6. dnfczmlc_8_ua_cre_ro_app.cli 4. Edit file dnfczmlc_2_sa_ent_all.cli or dnfczmlc_6_sa_cre_co_com.cli. For each MER Edit-queue add: add -ct DnqERQueue -ou -co -attr CHANGELOCALADDR where Name of the OU that includes your Edit queue Name of the Edit queue This PTF changes the following configuration entities: - New attribute added to CT DnqEROUOptions add -ct DnqEROUOptions -attr EditorWrapLines - New attributes added to CT DnQERQueue add -ct DnQERQueue -attr CHANGELOCALADDR add -ct DnQERQueue -attr ActionListRequireOpen - Role DnqERMsgAdmin changed add -ro DnqERMsgAdmin -ct DnqERQueue -co * -attr CHANGELOCALADDR - New attribute for CO DnqEROUOptions of type DnqEROUOptions added add -ct DnqEROUOptions -ou -co DnqEROUOptions -attr EditorWrapLines -val No - New attribute for CO FIN1Edit of type DnqERQueue added add -ct DnqERQueue -ou -co FIN1Edit -attr CHANGELOCALADDR - New attribute for CO FIN2Edit of type DnqERQueue added add -ct DnqERQueue -ou -co FIN2Edit -attr CHANGELOCALADDR - New attribute for CO MX1Edit of type DnqERQueue added add -ct DnqERQueue -ou -co MX1Edit -attr CHANGELOCALADDR D12.2 Executing the migration scripts ------------------------------------- Execute the CLI command files generated in step D12.1 in the following sequence and using the following user authorization: If dual authorization was not used (-dual NO): - dnfczmlc_2_sa_ent_all.cli by any SA - dnfczmlc_3_ua_cre_ro_all.cli by any UA If dual authorization was on (-dual YES): - dnfczmlc_5_sa_cre_ct_com.cli by the first SA (sa1) - dnfczmlc_5_sa_cre_ct_dep.cli by the second SA (sa2) - dnfczmlc_6_sa_cre_co_com.cli by the first SA (sa1) - dnfczmlc_6_sa_cre_co_dep.cli by the second SA (sa2) - dnfczmlc_8_ua_cre_ro_com.cli by the first UA (ua1) - dnfczmlc_8_ua_cre_ro_app.cli by the second UA (ua2) 1. On the runtime system, log on to AIX as the indicated user and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Switch to the temporary directory you created in step D12.1 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a UK96830cli.log where: DNI_SYSADM for files executed by the system configuration administrators, abbreviated as SA DNI_SECADM for files executed by the security administrators, abbreviated as UA The CLI command file name, for example dnfczmlc_5_sa_cre_ct_com.cli. D13. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ D13.1. Backing up the WebSphere Application Server configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The resources you need to back up depends on whether you use a clustered application server environment or a single server: - If you have a clustered application server environment, back up your deployment manager profile and all other profiles on all nodes that belong to the cluster. - If you have a single application server environment, back up the application server profile. As the WebSphere Application Server operator (uwaso1), issue the following command for each profile that is to be backed up: On Windows: \bin\manageprofiles.bat -backupProfile -profileName -backupFile On other platforms: /bin/manageprofiles.sh -backupProfile -profileName -backupFile where represents the installation directory of the application server and represents the file name under which the backup should be stored. D13.2. Update the WebSphere Application Server environment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D13.3. Migrating the enterprise application - - - - - - - - - - - - - - - - - - - - - - If the instructions created in step D6 contain the resource class CFGPF, follow this section now to update the enterprise applications. Before starting to update the enterprise applications, start the application server on which the enterprise application runs. If you use a clustered application server environment, start the deployment manager, node agent, and all members of the application server cluster. D14. Restarting all sessions and services ----------------------------------------- Restart all of the sessions and services that you use. How to do this depends on which WebSphere BI for FN features you use. For example: - Log in SIPN FIN LTs. - Subscribe MSIF to SAGs to enable file transfer and session monitoring. - Start the MSIF Message Transfer service. - Start the Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Open MSIF SnF input and output channels. - Start the applications that send requests to WebSphere BI for FN. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D15. Updating the Toolkit development environment ------------------------------------------------- If you use WebSphere BI for FN nodes or message sets in your own message flows, or if you modified WebSphere BI for FN sample message flows, you must update your Toolkit environment and redeploy your message flows. The following resources have changed in this PTF: -> API nodes: - DnqErQueueOutput -> Sample user action routing: - DNQ_K_UA.msgflow To update your Toolkit environment: - If you modified samples that were provided by WebSphere BI for FN and want to keep your modifications, rename the projects. However, these saved projects will not be updated. - Delete the old WebSphere BI for FN provided projects in your workspace. - To reinstall the new versions of the Toolkit resources, follow the instructions provided in the section of 'Application Programming' that describes how to prepare the WebSphere Message Broker Toolkit workstation. - Clean all projects and redeploy the message flows that you built using nodes that were provided by WebSphere BI for FN. D16. Verifying your Installation -------------------------------- This PTF contains updated version of the MER Facility enterprise application. To verify that an enterprise application is the most current version: 1. Log-on to the enterprise application. 2. Click the 'About' link in the upper right corner. A dialog box opens. 3. In the dialog box, locate the build number. Compare it to the driver level specified in the header of this readme file. Both numbers should be identical. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM91176 MM SWIFT SR2013: UPDATED NAK CODES FOR SR2013 CHANGES Adaptions for S.W.I.F.T. Standard Release 2013 (SR2013) changes. For S.W.I.F.T. Standard Release 2013 (SR2013) changes updated NAK codes are delivered. PM95265 MM INPUTENABLED ATTRIBUTE CONFUSING IN DNQCPCQO.CLI SCRIPT Formerly, in the sample file dnqcpcqo.cli the statement to add the attribute InputEnabled to the print-queue CO of type DnqPrintQueue begins with a comment sign. Now, the comment sign is removed. PM96602 MM POTENTIAL DEADLOCKS WHEN ACTING ON 'ALL MSGS IN QUEUE' User encountered DB2 deadlocks in the context of 'all messages on queue' batch actions. This has been corrected. PM96618 MM THE MER AUTO-COMPLETE FUNCTION FOR THE DESTINATION ADDRESS NEEDS TO BE ENHANCED The MER auto-complete function for the destination address has been been enhanced. Additionally, the upper case conversion of GPA system messages has been enhanced. F. Other changes ---------------- - Message updates: * Response messages changed: DNQB0003E * Response messages removed: DNQE9990I * Response messages new: DNQE6155E, DNQB0010I-DNQB0038E, DNQB0100I-DNQB0105I, DNQB2000E-DNQB2010I - Prevent actions to be selected in message list This function allows to specify a list of actions that are excluded from the pop-up menu in the message list. The user is required to open the message in order to carry out the action. - Entitle admin to change local address This function introduces the capability to change the local address of a message in an Edit/Main or Edit/Draft queue. It can be restricted to an administrator like DnqERMsgAdmin. - Enhancement to edit multi-line fields This function introduces a line-wrapping mode for multi-line fields. The mode is switched on when you add value 'Char' to the attribute EditorWrapLines of CO DnqEROUOptions by type DnqEROUOptions. If you edit a multi-line field, a line break is added automatically, when the last line is completely filled and, when the user continues to write at the end of the that line. The input field stops to accept characters typed by the user, if the cursor is located at the end of the maximum line. - Enhancements to message validation The client-side field-level validation now highlights fields in error with a red box. The detected errors are displayed only while the cursor is in the field. Validation problems detected on the server are displayed when the focus is on the warning icon next to a field. If there are multiple problems for a field, all of them are now displayed instead of only one. - Automatic completion of destination address This function completes the destination address to a BIC12 when a BIC8, BIC9 or BIC11 is entered. It appends or inserts 'X' characters as required. - Show reference column for templates The message list for template queues now displays the Reference column. When creating a message, the template list also displays the Reference column. - Import of FIN templates added to Sequential data facility (SDF) Now, SDF can import FIN templates to MER. You can specify if a HFS file or PS dataset is used as input or output file. For further information, see "Exporting and importing messages to and from files" in "WebSphere BI for FN for z/OS: System Administration". - MWH_EXT_IDENTIFIER extension identifier Formerly, when a message was deleted in MER Facility with a user action or inside a routing flow the extension identifier in column MWH_EXT_IDENTIFIER in the message warehouse was ComIbmDnqMM. Now, this is corrected, so that the actual extension identifier is ComIbmDnqER. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++