============================================================================== ============================================================================== 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 UI12329 for APAR PM98193 Driver level: 3501 Date 2013-12-20 ============================================================================== ============================================================================== 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. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM98193 MM CHANGES FOR AO MESSAGE PRINTING PM85696 MM MER FILTER CRITERIA IS TRUNCATED PM96675 MM DNQ_P_CMD: UNNECESSARY BIP2232E, BIP2230E AND BIP2488E AFTER FAILED DNICLI COMMAND PM97382 MM STORE TIME DOESN'T MATCH TIME IN HISTORY OF AN MER MESSAGE PM97383 MM VALIDATION ERROR IN OSN MSG, UNNECESSARY EVENTS ARE GENERATED PM98187 MM FIX FOR SDF RESTART HANDLING PM98629 MM DNQ_P_CMD RESPONSES EXPOSE CONFIGURATION OF ALL PRINT QUEUES PI05546 MM FIN1SAMPLE: MQMD MSGTYPE MUST BE CHANGED TO MQMT_REQUEST WHEN COPYING A MESSAGE TO THE EDIT QUEUE PI06309 MM ADDRESS COMPLETION FOR GPA MESSAGES IN MER MISSING Additional functional changes: - Requirement MR0627133040 "Ease input of data in occurrences/sequences of FIN messages" implemented - Support of SWIFT FUNDS 4.5 solution added - Support of WebSphere Message Broker V8 added - Support of Microsoft Internet Explorer 9 added - Restricted local address when editing unparsable messages - SDF import command did not set values for MWH_APPL_NAME and MWH_USER_ID - Message Printing enhancements Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - 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/DNQPRINT.xml /dnqv311/admin/data/dnqczeob.cli /dnqv311/admin/data/dnqczpct.ddl /dnqv311/admin/data/dnqczpgt.ddl /dnqv311/admin/toolkit/com.ibm.dnq.api.jar /dnqv311/admin/toolkit/DNI_DnqErSwiftNetFin.zip /dnqv311/admin/toolkit/dnq.project.interchange.zip /dnqv311/run/classes/dnqcbsdf.jar /dnqv311/run/classes/dnq.print.jar /dnqv311/run/data/dnqczeob.cli /dnqv311/run/flows/DNQ_K_FIN1.bar /dnqv311/run/flows/DNQ_K_FIN2.bar /dnqv311/run/flows/DNQ_K_TPL.bar /dnqv311/run/flows/DNQ_O_SFI.bar /dnqv311/run/flows/DNQ_O_SFO.bar /dnqv311/run/flows/DNQ_P_DSP.bar /dnqv311/run/flows/DNQ_P_CMD.bar /dnqv311/run/flows/DNQ_P_PRT.bar /dnqv311/run/msg/DNQB_Msg.properties /dnqv311/run/msg/DNQE_Msg.properties /dnqv311/run/msg/DNQP_Msg.properties /dnqv311/run/msg/dnqcbmsg.cat /dnqv311/run/msg/dnqcemsg.cat /dnqv311/run/msg/dnqcpmsg.cat /dnqv311/run/res/dnqcbevt.xml /dnqv311/run/res/dnqceevt.xml /dnqv311/run/res/dnqcpevt.xml /dnqv311/run/samples/dnqcbsdf.sh The following modules are new: /dnqv311/admin/data/dnqczp03.ddl /dnqv311/admin/data/dnqczp1g.ddl /dnqv311/admin/data/dnqczpm3.ddl 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: - UK96830 for APAR PM91176 (MM 3.1.1.11, SWIFT SR2013: UPDATED NAK CODES FOR SR2013 CHANGES) - UI12328 for APAR PM98191 (Base 3.1.1.16, AO FACILITY: ADD MESSAGE PRINTING SUPPORT) This PTF supersedes the following PTFs: - UI11994 for APAR PI05169 (MER THROWS DNIY0013E WHEN TRYING TO OPEN AN SR2013 COMPLIANT MESSAGE IN MTXML FORMAT CONTAINING FIELD 98A FROM ANY MER QUEUE) 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) - First WebSphere BI for FN security administrator (ua1) 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/_UI12329.cdd > import cdd/_UI12329.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: - DB * Index DNIvSN.DNQU1PQU ON DNIvSN.DNQP_QUEUE added * Index DNIvSN.DNQU2PQU ON DNIvSN.DNQP_QUEUE added * Index DNIvSN.DNQU3PQU ON DNIvSN.DNQP_QUEUE added * Index DNIvSN.DNQY1POR ON DNIvSN.DNQP_ORDER added * Index DNIvSN.DNQX1PQU dropped * Index DNIvSN.DNQX1POR dropped * Table DNQP_MESSAGE changed - Column MSG_TRANSREF VARCHAR(128) added - Column MSG_LOCAL_ADDR VARCHAR(128) added - Column MSG_REMOTE_ADDR VARCHAR(128) added - CONSTRAINT PMS_FK_PQU dropped - DBGNT * GRANT SELECT ON DNIvSN.DNQP_QUEUE TO GROUP DNIvUGRP added * GRANT SELECT ON DNIvSN.DNQP_ORDER TO GROUP DNIvUGRP added * GRANT SELECT ON DNIvSN.DNQP_MESSAGE TO GROUP DNIvUGRP added - 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 exceptions: - do not execute the instructions provided for resource class CFGPF now; you will use them in step D13.4. D8. Additional activities ------------------------- D8.1. DB2 related activities - - - - - - - - - - - - - - - Follow the instructions in "Maintaining DB2 catalog statistics for tables used by the message printing service" of WebSphere BI for FN for Multiplatforms: System Administration. D8.2. WebSphere MB related activities - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D8.3. WebSphere MQ related 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 ------------------------- 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 7 or Broker 8 BTD repository by copying the directory, enter the following commands: mkdir -p $DNI_BAP_PATH/bap/UI12329/$DNI_I cp -R $DNI_BAP_PATH/bap/$DNI_I/ $DNI_BAP_PATH/bap/UI12329/$DNI_I 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 WebSphere BI for FN for Multiplatforms: 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 WebSphere BI for FN for Multiplatforms: 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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 7.0 or 8.0 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 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 -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 --------------------------------- NOT APPLICABLE. 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 D2.4 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 option. In the Advanced options select the Network notebook page. Click on the "Clear Now" button to clear the browser cache. Internet Explorer 8 or 9 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 for Multiplatforms: System Administration. D15. Updating the Toolkit development environment ------------------------------------------------- You must update your Toolkit environment if you use: - 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 that are based on the WebSphere BI for FN API. The following resources are changed by this PTF: - WebSphere BI for FN nodes: DnqErFinInput DnqFinInput DnqPrintInputAdapter - WebSphere BI for FN sample message flows in projects: DNI_DnqErSwiftNetFin 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 for Multiplatforms: 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 for Multiplatforms: Application Programming. Otherwise, continue with the instructions provided in "Preparing the WebSphere Message Broker Toolkit workstation" in WebSphere BI for FN for Multiplatforms: 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 for Multiplatforms: 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: PM98193 MM CHANGES FOR AO MESSAGE PRINTING Now, the Message Management (MM) feature is enabled to support the AO Facility Message Printing component. If you use the DnqPrintInputAdapter node, you have to rebuild and redeploy your printing message flows. PM85696 MM MER FILTER CRITERIA IS TRUNCATED Formerly, when specifying multiple filter criteria for an MER message list, in certain situations, only part of the filter criteria are displayed in the filter summary. Now, all filter criteria are displayed in the filter summary. PM96675 MM DNQ_P_CMD: UNNECESSARY BIP2232E, BIP2230E AND BIP2488E AFTER FAILED DNICLI COMMAND Formerly, when an erroneous command was issued to service DNQ_P_CMD, for example a wrong command name or parameter was used, an exception was thrown and visible in SYSLOG. Now, the handling of syntax errors has been changed to omit the exception listing in SYSLOG. PM97382 MM STORE TIME DOESN'T MATCH TIME IN HISTORY OF AN MER MESSAGE Formerly, when viewing the history information of a message in MER, the date and time of a history entry is not displayed correctly. Now, the date and time of a history entry is displayed according to the local time zone. PM97383 MM VALIDATION ERROR IN OSN MSG, UNNECESSARY EVENTS ARE GENERATE Formerly, a DnqErFinInput node performed message validation regardless of the setting of the MessageValidation node property. Now, the DnqErFinInput node performs message validation only if the MessageValidation node property is set to Yes. PM98187 MM FIX FOR SDF RESTART HANDLING Formerly, not all messages were imported if the previous import of messages was interrupted and the import was restarted with the -new option. Now, all messages are imported. PM98629 MM DNQ_P_CMD RESPONSES EXPOSE CONFIGURATION OF ALL PRINT QUEUES Formerly, service DNQ_P_CMD exposed retrieved configuration data for print queues in responses to the CLI. Now, the configuration is not exposed to CLI response any more. PI05546 MM FIN1SAMPLE: MQMD MSGTYPE MUST BE CHANGED TO MQMT_REQUEST WHEN COPYING A MESSAGE TO THE EDIT QUEUE Formerly, the MER routing sample flows DNQ_K_FIN1_4 or DNQ_K_FIN2 copied a message which has been NAK'ed by SWIFT to the edit queue. The message field MQMD.MsgType kept the value MQMT_REPLY. Due to this, the MsgGrp ID was reset to the MsgGrp ID value of the original message, when the message was routed to DNF_ILC_FIN flow. This caused the DNF_ILC_FIN flow to overwrite the Message Warehouse record of the original message. Now, the MQMD.MsgType field value is changed to MQMT_REQUEST before the message is copied to the edit queue. Due to this, the corrected message keeps the new MsgGrp ID. This causes the DNF_ILC_FIN flow to write a new Message Warehouse record. PI06309 MM ADDRESS COMPLETION FOR GPA MESSAGES IN MER MISSING For most GPA messages, the destination address is mandated by SWIFT. Formerly, for these GPA messages, MER did not offer the appropriate BIC. Now, MER offers automatic completion of destination address in system GPA messages: 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. For all message types except GPA090 a default value is presented in the destination address field. Destination address information is displayed. Fixes for the following APARs from superseded PTFs are also contained in this PTF: PI05169 MM MER THROWS DNIY0013E WHEN TRYING TO OPEN AN SR2013 COMPLIANT MESSAGE IN MTXML FORMAT CONTAINING FIELD 98A FROM ANY MER QUEUE Formerly, when opening a message containing field 98 in MER, a DNIY0013E error showed up indicating that field 98 is unexpected or in an incorrect position. Now, such messages can be opened successfully. J. Other changes ---------------- - Message updates: * Event messages changed: Printing: DNQP1069E -> DNQP1069I DNQP1053E, DNQP1061E, DNQP1062E, DNQP1073E, DNQP1080E, DNQP1111E * Event messages new: DNQP1088E, DNQP1089E, DNQP1090E, DNQP1143E-DNQP1149E, DNQP1165E, DNQP1166E * Response messages changed: Printing: DNQP1016E -> DNQP1016I DNQP1019E -> DNQP1019I DNQP1066E -> DNQP1066I DNQP1112I -> DNQP1112E DNQP1003E, DNQP1011E, DNQP1012E, DNQP1023E, DNQP1026E, DNQP1030E, DNQP1038I-DNQP1042I, DNQP1301E, DNQP1302E * Response messages new: MER: DNQE6195E Printing: DNQP1343E * Response messages deleted: MER: DNQE6135E Printing: DNQP1105I, DNQP1106E - MER supports Microsoft Internet Explorer 9 - MM supports the WebSphere Message Broker V8.0 and its toolkit. How to migrate your current Broker 7 environment to Broker 8 is described in WebSphere BI for FN for Multiplatforms: Planning, Installation, and Customization. - Message Printing: * Print command service: - The status command is enhanced. If you call the status command with parameter -level msg it shows the LocalAddress and RemoteAddress instead of Sender and Receiver of the message. The Transaction Reference Number (TRN) is displayed in addition. The order of the displayed values is also changed. See the following example: [DNQ_P_CMD:OU1] status -qname File2 -level msg 2013-10-25 14:00 DNQP1046I Print queue status, queue name 'File2' Status : STARTED Messages : 24 Order Size : 10 Order Timeout: 99999 minutes Confirmation : Yes BIC Expansion: No DNQP1044I Order sequence number '100000', status 'PRTO_WAIT_CONF'. DNQP1041I Status, Msg_SN, Msg_ID, Type, LocalAddr, RemoteAddr, ApplRef, TRN DNQP1042I DELETED, 000001, X'9be90434e3e311e2ae1f09980a0d00000000000000000000', FIN202, PTSATWFFAXXX, PTSADEFFXXXX, APPLREF0, TRN0 DNQP1042I DELETED, 000002, X'9c0eee24e3e311e2ae1f09980a0d00000000000000000000', FIN199, PTSATWFFAXXX, PTSADEFFXXXX, APPLREF1, TRN1 DNQP1042I DELETED, 000003, X'9c11499ee3e311e2ae1f09980a0d00000000000000000000', FIN199, PTSATWFFAXXX, PTSADEFFXXXX, APPLREF2, TRN2 - Formerly, neither the issued print command nor the result was audited in case of an error. Now the issued command as well as its response message are audited if an error occurs. - Formerly, if invocation of a print command resulted in an error response, this error was written to the SYSLOG. Now such errors are no longer reported in the SYSLOG. - Formerly, escape character backslash (\) in queue names was not recognized. Now you can actually use the backslash to mark the underscore '_' as a literal in a queue. - Formerly, if you issued a delete command that resulted in deletion of more than 254 messages, an SQL error with SQLSTATE HY014 occurred. Now, this error does no longer occur. * Message printing service: - Order statuses PRTO_PRTD and PRTO_CONF are dropped. - Message status PRINT is dropped. - Formerly, existing print output files were overwritten when a message was reprinted. To make print output files unique, a timestamp is added to the name now. Thus print output files are no longer overwritten and have names similar to the following one: Main_BANKA_PrintQFile_100291_20131130140532.prt - Formerly, if an order had a message in status DELETED, and if an error occurred during printing of this order, then this message was completely printed instead of being marked with label 'Message was deleted'. Now deleted messages are actually marked as deleted after an error during printing. * Print input adapter: Formerly, the DnqPrintInputAdapter node did not accept print queues that were not yet started. Now, it accepts each valid print queue that is configured, even if the queue was never started. - MER: * Requirement MR0627133040 implemented: When you create or edit a message you can specify in the MER formatted view how many occurrences are added. * MER supports the FUNDS 4.5 solution. * MER restricts the local address when editing unparsable messages. Formerly, it was possible to enter an arbitrary local address for an unparsable FIN message and submit it. The message could then be routed to a queue where no user has the right to work with it, because the local address is not configured at all. Now, the editor of an unparsable FIN message needs rights for the local address and message type DNIUNPARSABLE as well as for the local address and message type of the corrected message. Rights for DNIUNPARSABLE are checked before the message is opened. Rights for the corrected message are checked before the editor proceeds from fixing the unparsable message to the formatted view. - SDF: * The values for MWH_APPL_NAME and MWH_USER_ID in MWH were not correctly set when parameters "-appl" and "-user" were used in a SDF operation. Now this has been corrected. G. Known issues --------------- NOT APPLICABLE. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++