============================================================================== = IBM WebSphere Business Integration for Financial Networks = = 5724-D9621 for Multiplatforms Extending Features V2.2.0 = = PTF UK43088 for APAR PK77083 = ============================================================================== Table of contents ----------------- A. How to use this document B. Changes to your current system C. Post-Installation D. Steps on a customization system E. Steps on a run-time system F. APARs addressed by this PTF A. How to use this document --------------------------- This PTF requires PTF UK38551 for APAR PK67184 for SWIFT Standard Release 2008. Install PTF UK38551 first if you have not yet applied it. 1. The installation directory of Extension for SWIFTNet is /opt/IBM 2. The names of users, groups, files, directories, etc. are the same as those used in the "Planning, Installation and Customization" manual. If you use different names, use those names instead of the names shown here. B. Changes to your current system --------------------------------- The following modules have been changed: /dnf_02_02/admin/data/DNFEIAS.xml /dnf_02_02/admin/data/DNF_EI_CS.msgflow /dnf_02_02/admin/data/dnfcfcfs.cli /dnf_02_02/admin/data/dnfcfrco.cli /dnf_02_02/admin/data/dnfcvcsv.cli /dnf_02_02/admin/data/dnfczcat.cli /dnf_02_02/admin/win/com.ibm.dnf.DefaultInterActService.zip /dnf_02_02/admin/win/com.ibm.dnf.EnhInterAct.zip /dnf_02_02/admin/win/com.ibm.dnf.FinInterfaceLayer.zip /dnf_02_02/admin/win/com.ibm.dnf.Verification.zip /dnf_02_02/run/bin/dnfcfsfd /dnf_02_02/run/bin/dnfcfsfs /dnf_02_02/run/bin/dnfczml2.awk /dnf_02_02/run/classes/Swift2008/dnfcvcks_sf08.jar /dnf_02_02/run/classes/dnfcecom.jar /dnf_02_02/run/classes/dnfceias.jar /dnf_02_02/run/classes/dnfclau.jar /dnf_02_02/run/data/dnfczcat.cli /dnf_02_02/run/lib/libdnfcf.a /dnf_02_02/run/lil/dnfcelil.lil /dnf_02_02/run/lil/dnfdgst.lil /dnf_02_02/run/lil/dnfrmexp.lil /dnf_02_02/run/lil/dnfrmimi.lil /dnf_02_02/run/lil/dnfrmrpt.lil /dnf_02_02/run/msg/dnfccmsg.cat /dnf_02_02/run/res/dnfceevt.xml /dnf_02_02/run/res/dnfchevt.xml /dnf_02_02/run/res/dnfchrsp.xml /dnf_02_02/run/res/dnfclrsp.xml /dnf_02_02/run/res/dnfcvevt.xml C. Post-Installation -------------------- After you have installed this PTF using ISMP: 1. Share the files with your customization system. 2. Ensure that the group ownership of the /dnf_02_02/admin directory and all subdirectories and files therein is set to group dniadmin. To do this, enter the following command in AIX: chgrp -R dniadmin /dnf_02_02/admin 3. Ensure that the group ownership of the /dnf_02_02/run directory and all subdirectories and files therein is set to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dnf_02_02/run D. Steps on a customization system ----------------------------------- To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: D1. Log on to AIX on the customization - - - - - - - - - - - - - - - - - - - - - - Log on to AIX on the customization system as a customizer (UCUST1). D2. Change to the customization directory - - - - - - - - - - - - - - - - - - - - - Change to the customization directory by issuing the following command: cd /var/dni_02_02/cus D3. Run your customization profile - - - - - - - - - - - - - - - - - Run your customization profile by issuing the following command: . ./dnicus_ D4. Start the CDP in migration mode - - - - - - - - - - - - - - - - - - Start the CDP in migration mode by issuing the following command: dnicdpm -i D5. Identify your current CDD - - - - - - - - - - - - - - - If you are not sure whether your .cdd reflects your current WebSphere BI for FN instance layout, generate a CDD using the CDP export command. How to this is described in "Planning, Installation, and Customization", Appendix E "CDP command reference". D6. Import your current CDD as the target CDD - - - - - - - - - - - - - - - - - - - - - - - Import your current CDD as the target CDD by issuing the following command: import cdd/.cdd D7. Prepare customization data - - - - - - - - - - - - - - - Update the customized administrative scripts for FIN in the directory '//admin' by entering the following command: prepare If you have assigned the service bundle DNFEIAS this command will generate deployment data for the resource class 'MBRK' and deployment instructions in the file /var/dni_02_02/cus/depdata///instructions.txt. You will use the customized message flow DNF_EI_CS later in step E1. You will not need the deployment instructions, the necessary deployment steps are integrated in this description. Note: This command also generates a deployment instructions file (instructions.txt) that, under these circumstances, does not contain any instructions. This is normal, expected behavior; you can ignore this file. D8. Implement the customization changes - - - - - - - - - - - - - - - - - - - - After you have successfully deployed the changes in step E11, Implement this CDD as your current CDD to update your 'current definition directory' by entering the following command: implement When the message "DNIZ9013I: Current Definition file already exists." is displayed enter 'y' to continue. D9. Quit the CDP session - - - - - - - - - - - - Quit the CDP session by entering the following command: quit E. Steps on a run-time system ------------------------------ E1. Transferring the WebSphere BI for FN resources to the WebSphere MB Toolkit workstation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To prepare the WebSphere BI for FN resources located on the WebSphere MB Toolkit workstation in the following steps, you must have the authority of the WebSphere MB domain administrator (UWBIMBD1). The access rights of this user are described in the "Planning, Installation, and Customization" manual in Chapter 1. Planning, in the section "Roles, users, and user groups". To transfer the WebSphere BI for FN resources to a WebSphere MB Toolkit workstation: 1. Log on to the Toolkit workstation. 2. Create a temporary directory to store the files to be transferred from the installation system. 3. Open a Command Prompt window and change to this directory. 4. Transfer, in binary mode, from the installation system to this temporary directory following files: /dnf_02_02/admin/win/com.ibm.dnf.DefaultInterActService.zip /dnf_02_02/admin/win/com.ibm.dnf.EnhInterAct.zip /dnf_02_02/admin/win/com.ibm.dnf.FinInterfaceLayer.zip /dnf_02_02/admin/win/com.ibm.dnf.Verification.zip /dni_02_02/admin/win/dni* For example, you can use the following File Transfer Program (FTP) commands to transfer the files: ftp bin prompt cd /dnf_02_02/admin/win get com.ibm.dnf.DefaultInterActService.zip get com.ibm.dnf.EnhInterAct.zip get com.ibm.dnf.FinInterfaceLayer.zip get com.ibm.dnf.Verification.zip cd /dni_02_02/admin/win mget dni* bye 5. Transfer, in binary mode, from the customization system to this temporary directory the message flows customized in step D7: /DNF_EI_CS.msgflow where: The resource file directory created for resource class MBRK during step D7, which has a name of the form .../com.ibm.dni.MBRK For example, you can use the following File Transfer Program (FTP) commands to transfer the files: ftp bin prompt cd get DNF_EI_CS.msgflow bye E2. Setting the Toolkit version and directories - - - - - - - - - - - - - - - - - - - - - - - - To set the correct environment for the tools used in the subsequent steps follow the instructions in the "Planning, Installation, and Customization" manual in "Chapter 3. Preparing to create an instance", "Preparing the WebSphere MB Toolkit workstation", -> "Setting the Toolkit version and directories" E3. Backing up all WebSphere BI for FN resources installed in a WebSphere MB Toolkit workstation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To save the current level of all WebSphere BI for FN resources installed on a WebSphere MB Toolkit: 1. Open a Command Prompt window and change to the temporary directory you used in step E1. 2. Enter the command: dninibak This command creates backup files with names of the form: _dn.zip where represents a letter or letters that indicate to which product feature or features the backup file applies: i The Base feature f All extending features except Enhanced Support for SWIFTNet FileAct fo The Enhanced Support for SWIFTNet FileAct feature Each backup file contains: Links All files in the directory \eclipse\links that have names of the form "com.ibm.dn.link" WebSphere BI for FN eclipse plugins All subdirectories of with names of the form "com.ibm.dn" WebSphere BI for FN project directories All subdirectories of the directory \eclipse\workspace that have names that begin with "DNI_Dn" Note: The dninibak command issues messages to inform you of directories it was unable to find. For example: - If the Enhanced Support for SWIFTNet FileAct feature is not installed, dninibak issues a message to inform you that it was unable to find directories or projects for the feature "dnfo". - If none of the other extending features are installed, dninibak issues a message to inform you that it was unable to find directories or projects for the feature "dnf". If you do not use the corresponding features, you can safely ignore such messages. E4. Installing the updated WebSphere BI for FN Eclipse plug-ins - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To install the updated WebSphere BI for FN Eclipse plug-ins: 1. Open a Command Prompt window and change to the temporary directory you used in step E1. 2. Enter the command: dnininst This command will install the updated Eclipse plugins. A warning message is displayed for each installed file that did already exist. If the dnininst program issues an error message, check the log file for more information about the reason for the error. To refresh the meta data in the Message Brokers Toolkit: a. Start the Toolkit with the -clean parameter. b. In the Message Brokers Toolkit, open the 'Broker Application Development Perspective'. c. Select all projects with names of the form DNI_DnMainflows. d. Right-click and select 'Refresh' from the pop-up menu. To re-build the WebSphere BI for FN projects: - For Message Broker Toolkit V5: a) Select all projects with names of the form DNI_DnMainflows. b) Right-click and select "Rebuild" from the pop-up menu. - For Message Broker Toolkit V6: a) Disable the "Build Automatically" feature. To do this, deselect the "Projects"->"Build Automatically" item in the pull-down menu. b) For all 'DNI_DnMainflows' projects: 1) In the "Resource navigator" window, select the projects. 2) From the main menu, select "Projects->Clean..." 3) In the popup window, select "Clean selected project" and ensure "Start a build immediately" is selected. 4) Press "OK". E5. Preparing BAR files with the updated WebSphere BI for FN flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To activate the changes within the WebSphere BI for FN eclipse plugins all affected message flows need to be deployed to all execution groups on all brokers where they are running. To prepare the broker archive files: a. Ensure the Message Brokers Toolkit is not running. b. In the Command Prompt window and from the temporary directory you used in step E1., enter dniupdbd -prepare -d . -q [-p ] [-h ] where The name of the queue manager to which the WebSphere MB configuration manager (CM) is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine running the CM. The default is 127.0.0.1 (localhost). This step creates broker archive files containing all WebSphere BI for FN message flows affected by the changes contained in this PTF, which is: - DNF_DIAS_CR - DNF_DIAS_CS - DNF_DIAS_SR - DNF_DIAS_SS - DNF_EI_CS - DNF_ILC_FIN - DNF_FSM_QRY - DNF_ILS_ACK - DNF_FSM_STA - DNF_ILS_FIN - DNF_PF_IS - DNF_ILC_SLS - DNF_ILC_CMD - DNF_V_REQ - DNF_V_RSP - DNF_V_ADM c. Check the log file dniupdbd.log to ensure that the files were successfully prepared. E6. Stop all sessions and services you use - - - - - - - - - - - - - - - - - - - - - Stop the SWIFTNet FIN processing: To stop the SWIFTNet FIN processing, log out all SWIFT logical terminals. For a detailed description, see section "Operating components and sessions", subsection "Operating LT sessions", in the System Administration manual. To stop the EIAS service - Release SWIFTNet SnF queues. - Stop Enhanced FileAct File Transfer service. E7. Stop all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - Stop all WebSphere BI for FN message brokers. E8. Updating the run-time system resources - - - - - - - - - - - - - - - - - - - - - This step is not required for this PTF. E9. Update the WebSphere MB environment - - - - - - - - - - - - - - - - - - - - This step is not required for this PTF. E10. Restart all WebSphere BI for FN message brokers - - - - - - - - - - - - - - - - - - - - - - - - - - This step is not required for this PTF. E11. Deploying all affected WebSphere BI for FN message flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To deploy the broker archive files: a. In the Command Prompt window and from the temporary directory you used in step E1. and E5., enter dniupdbd -deploy -q [-p ] [-h ] [-t ] where The name of the queue manager to which the WebSphere MB configuration manager (CM) is connected. The port required to connect to the queue manager. The default is 1414. The host address of the machine running the CM. The default is 127.0.0.1 (localhost). The wait interval for configuration manager and broker response. The default is 600 seconds (10min). This step deploys the broker archive files prepared in step E5. and contained in the current directory to the broker(s). b. Check the log file dniupdbd.log to ensure that the files were successfully deployed. E12. Migrate configuration data - - - - - - - - - - - - - - - - Migrate WebSphere BI for FN Extending Features configuration entities: 1. Ensure that all CTs, COSs and OUs in your current instance are committed, approved, and deployed. 2. On the runtime system on which the message broker runs, log on to z/OS UNIX as the system configuration administrator, for example, SA1. 3. Run the profile for your runtime environment by entering: . /var/dnf_02_02/run/dnfprofile 4. To verify that all necessary components are operational, open a CLI session and issue the list command: dnicli -ou SYSOU -s DNI_SYSADM -c "list -ou %" The CLI displays a list of all OUs. 5. Switch to the directory into which dnfczmlc is to place the files it generates and enter the following command: dnfczmlc.sh -i [-dir ] [-dual YES|NO] where: The name of the instance. -dir The directory on the runtime system in which the resource files dnfczcat.cli, dnfczcas.cli and dnfczcar.cli are located. The default is the /run/data subdirectory of the directory specified in your runtime profile (dnfprofile) by the DNF_PATH variable. For example, if the value of DNF_PATH is /opt/IBM/dnf_02_02, the default directory is /opt/IBM/dnf_02_02/run/data. -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 will 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. Note: This is a long-running task, and might take several minutes to complete. For example, if the name of your instance is INST1 and your system does not use dual authorization, enter: dnfczmlc.sh -i INST1 -dual NO The program dnfczmlc creates the following CLI command files in the current directory: If dual authorization is not used (-dual NO): - dnfczmlc_2_sa_ent_all.cli If dual authorization is on (-dual YES): - dnfczmlc_5_sa_cre_ct_com.cli - dnfczmlc_5_sa_cre_ct_dep.cli Check the file dnfczmlc.log to ensure that dnfczmlc ran correctly. 6. Execute the generated CLI command files by entering the following command: dnicli -i -s DNI_SYSADM -ou SYSOU -cft | tee -a PK77083cli.log where: The name of the instance. The CLI command file name, for example dnfczmlc_5_sa_cre_ct_com.cli. The generated CLI command files must be executed in the following sequence and using the following user authorization: If dual authorization is not used (-dual NO): 1. dnfczmlc_2_sa_ent_all.cli by any system configuration administrator If dual authorization is on (-dual YES): 1. dnfczmlc_5_sa_cre_ct_com.cli by the first system configuration administrator (SA1) 2. dnfczmlc_5_sa_cre_ct_dep.cli by the second system configuration administrator (SA2) E13. Restart all sessions and services you use - - - - - - - - - - - - - - - - - - - - - - - Restart all sessions and services you use. How to do this depends on the features of WebSphere BI for FN that you are using. For instance: - Log in SIPN FIN LTs. - Start Enhanced FileAct File Transfer service. - Start Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Start the applications that send requests to WebSphere BI for FN. For further information refer to the System Administration manual, chapter: 'Operating components, sessions, and services'. *------------------------------------------------------------------------* * End of Migration * *------------------------------------------------------------------------* F. APARs addressed by this PTF ------------------------------ PK77083 FIN DIGEST CALCULATION PROBLEM IN FINCOPY SERVICE EBA AND ERP FOR MT102 Formerly, when a field list contained the same field code twice, whereby the first occurrence is NO wildcard, a digest calculation problem occured in the FINCopy service EBA and ERP for MT102. As a consequence, a SWIFT ISN I102 with service code EBA or ERP would be rejected by EBA with an MT019, reason E5. On receipt of a SWIFT OSN O102 with service code EBA or ERP, you got an event DNFH3860E (digest verification error) passed to the application, resulting in error routing there. Now, the digest calculation for the FINCopy service EBA and ERP for MT102 is corrected. PK77306 RM SHOULD NOT DELETE OTHER BIS OU'S RMDS RECORDS RM import (complete mode) will delete other Biz OU's RMDS records. A rejected record cannot be enabled after re-importing the modified RMA record. Currently, both of the error have been fixed. H. Problems fixed by this PTF ------------------------------ FIN ENHANCEMENT OF ERROR MESSAGE DNFH3954E 'CID' NOT FOUND IN DNFMSGDIGEST REQUEST FOLDER' Formerly, when a FINCopy definition for a received message was not found you got the error DNFH3954E (at least after installing PTF UK39296 - Bootstrap complete, Euro1/Step1). However, this error code does not enable you to easily identify the root cause of the problem. The message is stored in DNF_IAMS and not available to the business application until the problem was recognized and fixed, and a recover command was issued. Now, the new event DNFH3757E will directly identify the root cause so that you can fix the problem immediately and the delay for the message can be minimized. Furthermore, a new configuration option enables you to configure that messages are forwarded to the application with error code DNFH3758E if the FINCopy definition is not available instead of keeping them in DNF_IAMS. The messages are delivered in the exception queue for digest verification errors, if configured. However, DNFH3758E indicates that you cannot be sure that the FINCopy service (CI) has processed this message. To specify this new behaviour, do the following: - add attribute FinCopyConfigError to CT DnfFinParametersSnfil, (commit and deploy the CT) - add the value 'deliver' to this attribute for each OU where messages should be delivered to the application with DNFH3758E when there is an error with the FINCopy definitions, (commit and deploy the OU's) The currently implemented stage does: - not yet write the event DNFH3757E if the message is passed to the application with DNFH3758E - not yet write this message with DNFH3758E into an exception queue The message received specified a FIN Copy service in field 103. No usable configuration was found for that FIN Copy service. The configuration indicates that such message are delivered to the target application or if configured to an exception queue. Due to the missing FIN Copy service definition no FIN Copy authentication is performed, the message is not proven to be processed by central institution therefore. The normal message authentication and RM authorization is performed independent of this. The DNF3758 response must be changed to reflect that the message is NOT kept in the IAMS and that NO Recover can be performed. FIN INCORRECT DIGEST VERIFICATION FOR CLS TPS MESSAGES (MT398) AT THIRD PARTY SERVICE ADMINISTRATOR SITE Formerly, when a MT398 was received by a CLS member bank, the digest verification failed on the embedded MT300 digest. Now, the digest verification works on the embedded MT300 digest. FIN DIGEST CALCULATION/VERIFICATION PROBLEMS WITH FIN COPY SERVICE TPS Formerly, when WebSphere BI for FN calculates incorrect FINCopy digests for FIN messages in the context of the FIN Copy service "TPS" with dual authentication that contain a party identifier in field 57A. This results in verification problems at receiving systems when the FINCopy digest is verified. Additional symptom which might occur: the sending WBIFN site receives FIN abort notifications (MT019). Now, FINCopy digests for FIN messages in the context of the FIN Copy service "TPS" with dual authentication that contain a party identifier in field 57A are calculated/verified correctly. DB2 TIMEOUTS IN DNF_V_REQ Formerly, when the DNF_ILS_FIN message flow was used in multiple instances, processing of MT398 CLS messages could cause DB2 deadlocks in DNF_ILS_FIN or DB2 timeouts in DNF_V_REQ. Now, MT398 CLS message processing no longer causes DB2 deadlocks in DNF_ILS_FIN or DB2 timeouts in DNF_V_REQ. WRONG LAU KEY MIGHT BE USED TO SIGN OUTGOING REVERIFICATION REQUESTS OR VERIFY INCOMMING Formerly, when the DNF_V_REQ message flow and the DNF_V_RSP message flow were deployed in the same execution group or used in multiple instances, signature verification might fail because of an invalid LMAC. In addition, if used in multiple instances, the DNF_V_RSP message flow did not track the number of processed signatures correctly and therefore did not recognize when the processing for a cylce had been completed. Among other things, the DNFV9712I event was not written. Now, LMAC is calculated/verified correclty and the number of processed signatures is tracked correcly. RM RM LAU KEY VERIFICATION FAILS UNDER SPECIAL CIRCUMSTANCES Formerly, some files exported from an RM application might fail importing in WebSphere BI for FN due to LAU verification problems. Occurance of the problem depended on the data included in the file exported from the RMA. The error message you received in such a case was: DNFL9534E Error during RM import processing; calculated LAU value does not match value in import file. Now, the calculation was corrected. White spaces such as x'0A' (line feed) and x'20' (blank) are not removed during SWIFT Mixed XML Canonicalization. EIA EIAS SERVICE DOES NOT REFRESH WAITFORNOTIF COUNTER AUTOMATICALLY MANUALY RESTART IS NEEDED Formerly, when the Enhanced InterAct Service sent an InterAct request message to SWIFT, it received a delivery notification before the InterAct response message from SWIFT was processed. The Enhanced InterAct service wrote the event DNF3418I and kept this delivery notification in its internal database tables. After the InterAct response had been received, the Enhanced InterAct Service had to be restarted manually to further process the outstanding delivery notification. Now, the Enhanced InterAct Service automatically initiates the processing of an outstanding delivery notification when the InterAct response is received. No restart of the Enhanced InterAct Service is required. EIA EIAS SERVICE COULD NOT BE STARTED AND THERE IS NO ERROR MESSAGE. Formerly, when it was tried to start the Enhanced InterAct Service by issuing a start command in its command service. The Enhanced InterAct service failed to start and did not write any error events. The reason for this problem was that the last path element in the LIBPATH environment variable specified the WebSphere MQ libraries, and in some cases the Enhanced InterAct service did not process this last element in the LIBPATH environment variable correctly. Now, the last element in the LIBPATH environment variable is processed correctly. EIA EIAS PROBLEM WITH DB2 LOCKS Formerly, when starting the Enhanced InterAct Service and no messages were processed, then the Enhanced InterAct service kept locks on the table spaces of its database tables. Now, the locks on the table spaces are freed. EIA ISSUE AN EVENT WHEN EIAS CAN'T START DUE TO MISSING MQ JAVA LIBRARY Formerly, when EIAS couldn't start due to missing MQ Java libraries no event was issued. Now, a new event DNFE3441E is introduced for this error scenario. FIN FSM SHOULD DO A RETRY After SQL -904 1. Retry after SQL -904 und -911 Formerly, DB2 might have reported SQL error -904, -911, and -913. All these error situations could have been of temporary nature, and might have disappeared without operator intervention. While the FSM retried a DB service request after SQL error -913, it aborted after -904 and -911. Now, the FSM retries a DB service request after SQL errors -904, -911, and -913 maximum 10 times after waiting 10 seconds between the attempts. The FSM aborts if an SQL error is returned after the 10th attempt. 2. Segment violation during FSM start Formerly, the layout and size of the FSM Communication Area (SFD CA), an IPC shared memory region, was changed in the FSM release 2.2.1 (dnfcfsfd.c 2.2.1 2008/04/15) with respect to earlier releases. The version number of the SFD CA was increased from 2 to 3. When an FSM (the two SFD processes) was canceled rather than cleanly terminated, the IPC SHM might not have been removed from the zOS USS operating system. If the WBI-FN PTF containing FSM 2.2.1 was installed while a backlevel SFD CA existed, the first SFD client process found this SFD CA and tried to re-use it. This process fails because the CA re-use logic lacked a CA version check. Now, a SFD client process checks the version number of an existing SFD CA. A backlevel CA is removed, and a new SFD CA IPC SHM is created. An existing CA is reused if it has the correct version 3, and is not used by existing FSM processes. 3. Enter Resync for all Client SL Retry errors Formerly, the SFD Queue I/O Service checked for and reported an SL retried network error when a null response was not received from SYS as expected. In case of an SL Retry Error, the SFD tried to resync only if a SL retry network error was indicated. SL retried errors that were not reported as network errors might, however, also had been been caused by a network error from a user's point of view. Now, the SFD tries to resync in case of any SL Retry Error. 4. Support effective FIN batch count of 99 Formerly, the WBI-FN SL FSM implementation used a fix length buffer of 1000 bytes for the RequestHeader.RequestRef data. It provided space for 35 RequestReference items. The effective maximum FIN batch count was therefore limited to 35 APDUs. Now, the size of the request refence buffer is increased to 2775 + 1 providing space for 99 request refence items (28 bytes each), the initial nnn field, and the string terminating \0. FIN MT096/MT097 PROCESSING NO LONGER POSSIBLE Formerly, when PTF UK41645 was applied, MT096 got an error on receipt, MT097 was not passed to SWIFT, and a DNFH3954E was reported. Now, this processing for MT096/MT097 is corrected. MESSAGE VALIDATION ERROR DNIY001E Formerly, the message validation of an incorrect MT101 led to a DNIY001E event, instead of passing back the correct validation problem as a response. Now, the message validation processes an incorrect MT101 correctly. RM RMA PERMISSIONS ARE NOT LOADED IN WBIFN DNF_RMPS TABLE Formerly, RMA Permissions were not loaded in the DNF_RMPS table. Now, the RMA Permissions are loaded in the DNF_RMPS table. RM IMPROVE RM LAU KEY VERIFICATION Formerly, the implementation of XML canonicalization for RM import LAU calculation was insufficient for some special cases. Now, the implementation of XML canonicalization and RM import LAU calculation is corrected. SCRIPT TO REMOVE THE LT (DNFCFRCO) DOES NOT CONTAIN THE REMOVE OF CT DNFLTMAP Formerly, the script to remove the LT (dnfcfrco) did not contain the remove of CT DnfLTMap (associated to DNFSYSOU). Now, the script contains the remove of CT DnfLTMap. IAS DIAS NEEDS TO PROVIDE INFORMATION IN COLUMN MWH_EXT_IDENTIFIER IN THE DNI_MWH_ TABLE Formerly, Message Warehouse exploitation has not yet been implemented for DIAS. Therefore, it was not possible to distinguish DIAS messages in MWH by using the extension identifier (column MWH_EXT_IDENTIFIER). Now, DIAS components write extension identifier "ComIbmDnfDIAS" in column MWH_EXT_IDENTIFIER. RM RM 'REPORT' COMMAND FOR TYPE 'R' LISTS TOO MANY MISSING AUTHORIZATIONS Formerly, after PTF UK39367 for APAR PK69368 had been installed the RM 'report' command for type 'r' may have listed too many missing authorizations. In addition, authorizations in status 'Deleted', 'Rejected' and 'Revoked' were not considered and reported as missing. Now, the RM 'report' command for type 'r' only lists those authorizations that are really missing and 'Deleted', 'Rejected' and 'Revoked' authorizations are no longer reported as missing. In analogy to that the RM 'report' command for type 'a' is processed. +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++