==============================================================================
= IBM WebSphere Business Integration for Financial Networks for MP           =
= 5724-D96 SUPPORT FOR SWIFTNET FIN, SUPPORT FOR SWIFTNET INTERACT,          =
=          FINANCIAL MESSAGE TRANSFER V3.1.0                                 =
= PTF for APAR PK91866                                                       =
==============================================================================


Table of contents
-----------------

A. How to use this document
B. Changes to your current system
C. APARs addressed by this PTF
D. Other changes implemented by this PTF
E. Known issues


A. How to use this document
---------------------------

  Only the online version of this readme document is up to date.
  Before you install this PTF, download the latest version from:
    http://www.ibm.com/software/integration/wbifn/support

  This PTF requires the PTF for APAR PK91867 for WebSphere BI for FN Base.

  Install this PTF together with Product code, follow the instructions in 
  the "Planning, Installation and Customization" manual, and ignore this 
  readme document.

  Download the latest version of the WebSphere BI for FN product documentation
  from:
   www.ibm.com/software/integration/wbifn/library

  This document assumes the following:

  1. The default installation directory is /opt/IBM. However, you can choose
     any directory you like. This readme document uses the abbreviation
     <inst_dir> to indicate this directory.

  2. The names of users, groups, files, and directories 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:

      <inst_dir>/dnf_03_01/admin/data/dnfcfcfs.cli
      <inst_dir>/dnf_03_01/admin/data/dnfczfcs.cli
      <inst_dir>/dnf_03_01/admin/data/dnfczfct.cli
      <inst_dir>/dnf_03_01/admin/data/DNFEIAS.xml
      <inst_dir>/dnf_03_01/admin/data/DNFFIN.xml
      <inst_dir>/dnf_03_01/run/classes/dnfceias.jar
      <inst_dir>/dnf_03_01/run/classes/dnfcdrtn.jar
      <inst_dir>/dnf_03_01/run/data/dnfcwdbs.bnd
      <inst_dir>/dnf_03_01/run/data/dnfczfcs.cli
      <inst_dir>/dnf_03_01/run/data/dnfczfct.cli
      <inst_dir>/dnf_03_01/run/flows/DNF_EI_CMD.bar
      <inst_dir>/dnf_03_01/run/flows/DNF_EI_CS.bar
      <inst_dir>/dnf_03_01/run/flows/DNF_ILC_FIN.bar
      <inst_dir>/dnf_03_01/run/flows/DNF_ILS_ACK.bar
      <inst_dir>/dnf_03_01/run/flows/DNF_ILS_FIN.bar
      <inst_dir>/dnf_03_01/run/flows/DNF_PF_IS.bar
      <inst_dir>/dnf_03_01/run/flows/DNF_PF_IR.bar
      <inst_dir>/dnf_03_01/run/flows/DNF_PF_CMD.bar
      <inst_dir>/dnf_03_01/run/lib/libdnfcwetc.a
      <inst_dir>/dnf_03_01/run/lib/libdnfcwdbs.a
      <inst_dir>/dnf_03_01/run/lib/libdnfcwqio.a
      <inst_dir>/dnf_03_01/run/msg/dnfcfmsg.cat
      <inst_dir>/dnf_03_01/run/res/dnfcersp.xml
      <inst_dir>/dnf_03_01/run/res/dnfceevt.xml
      <inst_dir>/dnf_03_01/run/res/dnfchevt.xml
      <inst_dir>/dnf_03_01/run/res/dnfchrsp.xml
      <inst_dir>/dnf_03_01/run/res/dnfcjrsp.xml
      <inst_dir>/dnf_03_01/run/res/dnfcprsp.xml

C. APARs addressed by this PTF
------------------------------

 PK91866 WEBSPHERE BI FOR FN SUPPORT FOR SWIFTNET FIN, SWIFTNET
         INTERACT,AND FMT Update
         The following WebSphere BI for FN V2.2 APARs were not
         contained in the V3.1 GA shipment code and are now fixed:
         PK86003, PK85905, PK86898
         Apar details see below.

 PK95381 ERROR EVENT DNFF4400E DURING THE SAG 6.3 RESTART AND FSM HANG DUE
         TO THE SEGMENT VIOLATION
         Formerly, a restart message send by the SAG was not correctly
         assessed by the SFD and could cause a segment violation afterwards.
         The segment violation was accompanied by the following errror event:
         DNFF4400E <date> <time> <inst> DNF_FSM LT 'IBMADEFFA': WMQ 'PUT'
         operation on queue '' of queue manager 'QM1' failed; WMQ reason
         code='0'; error text='SLS reply to queue not defined. Null response
         dropped'.
         Now, the SAG restart message will be identified and will silently
         be discarded, thereby preventing further processing of the message.

         This APAR was sysrouted from WebSphere BI for FN V3R1 APAR PK93574.


APARs from superseded PTFs:

 - none -


APARs of WebSphere BI for FN V2.2 not contained in the V3.1 GA shipment code
and now fixed:

 PK86003 FIN  WHEN WBIFN RECEIVED MT021 MSG WHICH WAS EMBEDDED WITH AN
              F05 MSG, USER WILL ENCOUNTER DNFH3951E ERROR CODE
              Formerly, when WBIFN received MT021 msg which was embedded with
              an F05 msg, user encountered DNFH3951E error code and msg
              stuck in IAMS table.( F05 is a "quit" command of service msg.)
              Now, this behavior has been corrected.
              
 PK85905 FIN  TPS MESSAGES STUCK IN DNF_IAMS, THOUGH
              FINCOPYCONFIGERROR=DELIVER IS CONFIGURED
              WebSphere BI for FN can be configured so that, when it receives
              a message that used a FINCopy service for which no profile is
              configured, the message is delivered to the receiving
              application. This is done be setting the value of the
              FinCopyConfigError attribute of the CO of type
              DnfFinParametersSnfil to "deliver". However, due to a program
              error this did not work for messages that used the FINCopy
              service TPS; such messages remained in DNF_IAMS table and
              were not processed.
              Now, this behavior has been corrected (see also Apar PK86898).

 PK86898 FIN  IN THE TPS FINCOPY AREA FOR CASES 3A AND 3B THE BIC8 MUST NOT
              BE TAKEN FROM THE PROFILE NAME, BUT THE CID HAS TO BE TAKEN.
              In the TPS FINCopy area for cases 3a and 3b, the BIC8 is no longer
              taken from the profile name, that is, from the name of the CO of
              type DnfFinCopyService. Instead, the central institution ID
              that is specified in the profile is used.
              For profile names of the form TPS_<adminBIC>_<type>, customers
              must verify that they have configured the correct value for the
              Centralinstitution attribute.

              The minimum configuration requirement for customers who use the
              TPS service only to receive messages is now:

              add -ct DnfFinCopyService -co TPS_LIVE -ou <bou> -attr ServiceMode -val T
              add -ct DnfFinCopyService -co TPS_LIVE -ou <bou> -attr TransferDirection -val R

              Setting the service mode to T indicates that TPS is a T-Copy service,
              and so does not require double authentication.

              If a message is sent with a TPS service code that corresponds to an
              incomplete or incorrect FinCopy profile, the event DNFH3757E is
              issued and the message is returned to the application with an
              error code.
              If a message with a TPS service code is received that contains
              a CopyDigest 2 (contrary to the T-Copy rules), an event (DNFH3757E)
              is issued and the setting of FinCopyConfigError ("keep" or "deliver")
              determines whether the message is kept in IAMS or is delivered to the
              application.

              A new attribute "TransferDirection" for DnfFinCopyService was used
              with following values:
              SR - This FINCopy service can be used to both send and receive
                   messages. This is the default.
              S  - This FINCopy service can be used only to send messages. If a
                   message is received from this service, WBIFN issues an event
                   message.
              R  - This FINCopy service can be used only to receive messages. If
                   a local application attempts to send a message that specifies
              Customers who wish to receive message with service code TPS at least
              need the minimum TPS_LIVE configuration:
              add -ct DnfFinCopyService -co TPS_LIVE -ou <bou> -attr ServiceMode -val T
              We also recommend for receive-only customers:
              add -ct DnfFinCopyService -co TPS_LIVE -ou <bou> -attr TransferDirection -val R

 FIN  DB2 -302 ERROR WITH 12 CHARACTER LTGROUP DEFINED CAUSED THE
      SWIFT LOGIN AND/OR SELECT TO ABORT
      Formerly, when all 12 characters for the LTGROUP name were used
      a DB2 error occured. The DB2 -302 error caused unpredictable
      results when logging in and selecting application to the SWIFT
      network. When 11 characters or less for the LTGROUP name were
      used the problem did not occur.
      Now, for the LTGROUP name 12 characters or less can be used.


 EIA  EIAS ISSUES SOME EVENTS WITH SERVICE DNF_ILC_FIN, IF MESSAGE
      WAREHOUSE IS SWITCHED ON
      Formerly, when message warehouse was enabled for EIAS, it might
      happen, that DNF_ILC_FIN was used as service name in events
      from the DNF_EI_CS service.
      Now, the correct service name is used in events from the
      DNF_EI_CS service.

 FIN  DNFH3861E SIGNATURE VERIFICATION ERROR WHICH CAUSE MESSAGES
	    TO ARRIVE IN DNF_IAMS WITHOUT SIGNATURE AND BEEING STUCK.
      Formerly, when messages with signature verification error but
      without SignatureList were stored in DNF_IAMS they could not
      be processed and therefore stuck in the database table.
      Now, these messages are flagged with error code DNFH3862E
      and passed to the FIN application or to SignatureException
      queue if configured.

 EIA  QUERY COMMAND IN SERVICE DNF_EI_CMD DOES NOT DISPLAY ALL
      DEFINED MESSAGE PARTNERS
      Formerly, the query command does not display all defined
      message partners.
      Now, the query command displays all defined message partners.

 EIA  EIAS SERVICE STOPS WHEN NOT YET CORRELATED DELIVERY
      NOTIFICATION ARE AVAILABLE WHICH ARE OLDER THAN 2 WEEKS
      Formerly, the Enhance InterAct Service (EIAS)sent InterAct
      requests to the SIPN, but due to network problems the
      corresponding InterAct responses got lost. Instead EIAS
      received delivery notifications for the sent InterAct requests.
      Due to the missing InterAct responses, EIAS could not correlate
      the delivery notifications with the requests. These delivery
      notifications remained in an internal Websphere BI for FN
      database for two weeks until they were deleted automatically.
      After the deletion of each expired delivery notification, EIAS
      issued an error event and stopped, and afterwards had to be
      restarted manually to delete the next expired delivery
      notification.
      Now, EIAS deletes all outstanding delivery notifications after
      two weeks without stopping.

 FIN  QUERY COMMAND RETURNS WRONG RESULT, I.E NO NUMBER OF MESSAGES
      FAILING SIGNATURE VERIFICATION
      Formerly, when the incoming message which needed signature
      reverification stayed in IAMS table if deliver mode was set as
      'keep'. However, the query command returned wrong result.
      The result did not return the number of messages which failed
      signature verification.
      Now, this has been corrected.

 FMT  MESSAGE WAREHOUSE INFORMATION FOR FMT MESSAGES NOT CORRECT
      Formerly, when message warehouse is activated for FMT, some
      message warehouse information is missing in the records, and
      some information is obsolete.
      Now, when message warehouse is activated for FMT, the message
      warehouse information is complete and up-to-date.

 FMT  FMT ROUTING DOES NOT WORK, IF A FINCOPY SERVICE CODE IS
      AVAILABLE IN FIELD 103 OF THE MESSAGE
      Formerly, when a message which contained a FINCopy Service
      code in field 103 was received via FMT service (not passed
      via SWIFT), the routing within FMT did not work correctly.
      Now, FMT routing is corrected.

 FMT  EXCEPTION QUEUE HANDLING IN FMT DOES NOT WORK CORRECTLY
      Formerly, when exception queues were defined for FMT
      processing, OSN handling might not be correct.
      Now, when exception queues are defined for FMT
      processing, OSN handling is correct.

 FMT  FMT SERVICE DOES NOT PASS DIGEST TO APPLICATION
      Formerly, when using FMT services of WebSphere BI for FN to
      send messages directly without using the SWIFT Network,
      calculated digests were not passed to the application for
      the received message ("OSN"). This caused error routing in the
      application, as the message was not considered "authenticated".
      E.g. if the receiving application is MERVA, the missing digests
      prevent the calculation of a dummy MAC by MERVA User exit 8136.
      Now, this behavior is corrected.


 FMT  REPORT MESSAGE (E.G. MT012, MT082) CONTAINING THE STRING {103
      REMAINS IN DNF_IAMS (FMT)
      This Apar PK75399 for FMT corresponds to the Apar PK74933
      for FIN. Refer to APAR PK74933:
      Formerly, when a report message (e.g. MT012, MT082) containing
      the string {103 was received, it remained in DNF_IAMS with
      DNFH3954E (prior to PTF UK41019/UK41022) or DNFH3757E
      (with UK41019/UK41022 applied) and was not delivered to the
      FIN application.
      Now, these messages are delivered to the receiving FIN
      application correctly.


D. Other changes implemented by this PTF
----------------------------------------

 - The message text or explanation of following InterAct messages have been
   changed: DNFJ3240I, DNFJ3242I, and DNFJ3247I


E. Known issues
---------------
  n/a

++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++