============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2014 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 (3.1.1.17) PTF UI22203 for APAR PI21901 Driver level: 4490 Date 2014-12-19 ============================================================================== ============================================================================== 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-01.ibm.com/support/docview.wss?uid=swg27041133 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. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PI21901 MM DNQD1022E ERROR WHEN USER TRIES TO OPEN A MESSAGE FROM A MER QUEUE: DNQD1022E SQL code='-104', SQL state='42601' PI23195 MM WRONG MWH_MSG_STATUS VALUE WHEN INSERT DONE VIA DNQFINAPPLICATIONOUTPUT PI23299 MM UNNECESSARY MWH ENTRIES FOR DELETED TEMPLATE PI23301 MM POSSIBLE DUPLICATE MARKER IN MESSAGE LIST AND IN CONTEXT DISPLAY IS MISSING WHEN ACKED PI27940 MM BIC INFO IS NOT SHOWN IN OSN AND PRINT-OUTS PI30339 MM ON ATTRIBUTE EXTRACTION FOR MTX92, THE MESSAGE CANNOT BE SEND IF AMOUNT FIELD IS 32B AND AMOUNT HAS 6 DIGITS BEFORE COMMA Additional functional changes: - Browser-based message printing Documentation updates: The following manuals have been changed: - Concepts and Components - Messages and Codes - System Administration - 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/dnqcecoo.cli /dnqv311/admin/data/dnqczcah.lst /dnqv311/admin/data/dnqczcat.cli /dnqv311/admin/data/DNQER.xml /dnqv311/admin/toolkit/com.ibm.dnq.api.jar /dnqv311/admin/toolkit/DNI_DnqErCommon.zip /dnqv311/admin/toolkit/dnq.project.interchange.zip /dnqv311/run/classes/com.ibm.dnq.attex.jar /dnqv311/run/classes/dnq.common.jar /dnqv311/run/classes/dnq.header.jar /dnqv311/run/classes/dnq.maxhf.api.jar /dnqv311/run/data/dnqczcah.lst /dnqv311/run/data/dnqczcat.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/flows/DNQ_O_SFI.bar /dnqv311/run/flows/DNQ_O_SFO.bar /dnqv311/run/flows/DNQ_O_SMX.bar /dnqv311/run/msg/dnqcemsg.cat /dnqv311/run/msg/dnqckmsg.cat /dnqv311/run/msg/DNQE_Msg.properties /dnqv311/run/msg/DNQK_Msg.properties /dnqv311/run/res/dnqceevt.xml /dnqv311/run/res/dnqckevt.xml C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Check if you have any efixes (emergency fixes) applied in your WebSphere BI for FN installation. In case you have efixes installed after your previous WebSphere BI for FN PTF installation and migration contact your IBM support before installing and migrating this PTF. 2. Ensure that all previously prepared deployment instructions were carried out. 3. 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. 4. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 5. 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'. 6. 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 -rg % -qo mor [only for SYSOU] > list -user % -qo mor The list command should result in 'No roles/role groups/users found that match specified criteria'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UI21663 for APAR PI26117 (MM 3.1.1.16, WEBSPHERE BI FOR FN MESSAGE MANAGEMENT UPDATES FOR SWIFT VL/142014) - UI22202 for APAR PI21851 (Base 3.1.1.22, SECURE WBIFN SEMAPHORES ON GROUP LEVEL TO AVOID ALTERATION BY OTHER APPLICATIONS) C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - 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) 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. - 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. 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/_UI22203.cdd > import cdd/_UI22203.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: If you continue, the current CDD will be overwritten by a new CDD." 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 exceptions: - do not execute the instructions provided for resource class CFGPF now; you will use them in step D13.4. D8. Additional activities ------------------------- NOT APPLICABLE. D9. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. D10. Prepare BAR file deployment -------------------------------- D10.1. Backup the BTD repository - - - - - - - - - - - - - - - - 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 backup of your BTD repository. The location of this directory depends on the version of WebSphere Message Broker you are using: - for version 6.1: $DNI_BAP_PATH/bap/$DNI_QMGR_CFG - for version 7 or version 8: $DNI_BAP_PATH/bap/$DNI_I where the values of the environment variables DNI_BAP_PATH, DNI_QMGR_CFG and DNI_I correspond to the settings made in your dniprofile. For example, to create a backup of a Broker V7 or Broker V8 BTD repository by copying the corresponding directory, enter the following commands: mkdir -p $DNI_BAP_PATH/bap/UI22203/$DNI_I cp -R $DNI_BAP_PATH/bap/$DNI_I/ $DNI_BAP_PATH/bap/UI22203/$DNI_I D10.2. Customize BAR files when using mqsideploy or the Toolkit to deploy them - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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 or V8, 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 or CDP generated output - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - Note: If you have configured multiple broker servers you must deploy the BAR files to each broker server. 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Note: If you are using Broker V7 or V8 and you have configured multiple broker servers you must perform the following steps on each broker server. 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 systems 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 -broker The parameter -broker is only required if you use multiple broker servers. 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 If dual authorization is used (-dual YES): 1. dnfczmlc_5_sa_cre_ct_com.cli 2. dnfczmlc_5_sa_cre_ct_dep.cli This PTF changes the following configuration entities: - New attribute added to CT DnqERQueue add -ct DnqERQueue -attr BrowserPrintActionList 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 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) 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 UI22203cli.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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Which 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. Restarting all application servers - - - - - - - - - - - - - - - - - - - - - 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. D13.4. 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. Note: A new web application may contain changed JavaScript and HTML files. To assure that the user works with the most current web application content it is recommended to clear the browser cache on each client workstation before the user logs in the next time. It is not sufficient to just reload the page. Please find the following sample description for the different browser types as reference for the user communication: Firefox 10.0.6 ESR and later From the menu bar select Tools -> Options. In the options dialog select the Advanced section. In the Advanced section select the Network notebook tab. Click on the "Clear Now" button to clear the browser cache. Internet Explorer 8 or later From the menu bar select Tools -> "Internet Options". On the General notebook page click the "Delete..." button in section "Browsing History". In the "Delete Browsing History" dialog check at least "Temporary Internet files" and click the Delete button to clear the browser cache. 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. - 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 System Administration. D15. Updating the Toolkit development environment ------------------------------------------------- You must update your Toolkit environment if you use at least one of the following components: - WebSphere BI for FN sample message flows as foundation for your own flow development - WebSphere BI for FN nodes in your own message flows - WebSphere BI for FN message set projects containing XML schema definitions, that, for example, are utilized by the XPath wizard Furthermore, you have to rebuild and redeploy your message flows if they are based on the WebSphere BI for FN API. The following resources are changed by this PTF: - WebSphere BI for FN sample message flows: DNQ_K_UA contained in projects: DNI_DnqErCommon.zip dnq.project.interchange.zip - WebSphere BI for FN nodes: DnqFinApplicationOutput DnqFinServiceOutput DnqGenericMqOutput DnqMsifServiceOutput - WebSphere BI for FN message sets: none - WebSphere BI for FN message set projects: none To install the new versions of the Toolkit resources, follow the instructions of the listed sections provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Transferring the WebSphere BI for FN resources - Installing the WebSphere BI for FN Eclipse plug-ins If you use WebSphere BI for FN sample message flows as foundation for your own flow development follow the instructions provided in "Using the sample routing flows" in WebSphere BI for FN Application Programming. Otherwise, continue with the instructions provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Importing WebSphere BI for FN Base sample projects - Importing the message sets and sample routing flows Additionally, if you use WebSphere BI for FN message set projects containing XML schema definitions for your own flow development follow the instructions provided in section "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN Application Programming: - Importing the message sets and sample routing flows - Importing XSD files for SWIFT message payloads 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: PI21901 MM DNQD1022E ERROR WHEN USER TRIES TO OPEN A MESSAGE FROM A MER QUEUE: DNQD1022E SQL code='-104', SQL state='42601' Formerly, when the decimal point representation of DB2 was set to a comma (DECIMAL=COMMA), a database error occurred when a user attempted to open a message from an MER queue. Now, this has been fixed. PI23195 MM WRONG MWH_MSG_STATUS VALUE WHEN INSERT DONE VIA DNQFINAPPLICATIONOUTPUT Formerly, when a message was routed to the FIN output adapter (either DnqFinServiceOutput or DnqFinApplicationOutput), the MWH status for this message was set to 'FIN'. Now, when a message is routed to the FIN output adapter, the MWH status for this message is set to 'Routed'. PI23299 MM UNNECESSARY MWH ENTRIES FOR DELETED TEMPLATE Formerly, when MWH was enabled for messages processed by the MER user action routing sample, unwanted MWH records have been created, if MER was used to: - Delete a template - Save a draft of a message - Delete the draft of a message Now, this has been fixed. PI23301 MM POSSIBLE DUPLICATE MARKER IN MESSAGE LIST AND IN CONTEXT DISPLAY IS MISSING WHEN ACKED Formerly, when a FIN message with "PDE:" trailer is created in MER, the PD column in the MER message list will display a PD marker and the context view will show "Possible duplicate: True". However, when a FIN message with "PDE:" trailer is not created in MER, the PD column in the MER message list will not display a PD marker and the context view will show "Possible duplicate: False". This is not correct. Now, this has been fixed. For any FIN message with "PDE:" trailer, the PD column in the MER message list will display a PD marker and the context view will show "Possible duplicate: True". PI27940 MM BIC INFO IS NOT SHOWN IN OSN AND PRINT-OUTS Formerly, when displaying the content of a message in MER, the BIC information for the sending LT of an OSN message is not displayed in the formatted view. This is not correct. Now, this has been fixed. When displaying the content of a message in MER, the BIC information for the sending LT of an OSN message is displayed. PI30339 MM ON ATTRIBUTE EXTRACTION FOR MTX92, THE MESSAGE CANNOT BE SEND IF AMOUNT FIELD IS 32B AND AMOUNT HAS 6 DIGITS BEFORE COMMA Formerly, when a DnqFinInput node was used in a custom flow to transform a FIN MTx92 containing field 32B with an amount that has exactly 6 digits, an error occurred during attribute extraction and an exception was thrown, indicating that the probe 'AmountCurrencyDate' could not be evaluated. Now, this has been fixed. F. Other changes ---------------- - Message updates: * Messages new: DNQE5083I, DNQE5084E, DNQE6156E, DNQK2099E * Messages updated: DNQE6115E, DNQE6911E, DNQK3099E - Browser-based message printing added Users of the MER facility can manually print the currently viewed message or several messages from a message list on a printer that can be accessed from the browser. In addition, MER actions can be configured to automatically initiate the printing of the processed message on such printers. - MER adaptions for Base APAR PI30628 (EMBEDDED MT202 COV IN MTx92 MAY CAUSE VALIDATION ERROR DNIY0018E) The changes done for Base APAR PI30628 are made available to MER. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++