WBIFN V3.1.1 Messaging Services for SWIFTNet InterAct and FileAct for z/OS PTF-Readme for PTF UK90513 / APAR PM74319

Product readme


Abstract

PTF Readme

Content


APAR details

---------------------

Fixes for the following APARs are contained in this PTF:

PM74319 MSIF MSIF REPLICATION OF SEND SNF TRANSFER MAY RESULT IN UNNECESSARY
INTERNAL MESSAGES THAT CAN EXTEND PROCESSING TIME
SWIFT reports in the Ack to an SnF outbound transfer a status
indication about their progress in replicating transfer information
to another database for being safe in case of an SnF System
Recovery gets necessary. Using this information, MSIF determines
whether a particular transfer is now safe for being marked as
complete by setting its condition to "finished".
Formerly, MSIF checked this information for every response and
sent an internal trigger MQ message to affected transfers.
In case of high volume transfers, this could have resulted in
sending more than one trigger message to the same transfer.
Now, MSIF only records the status information received from SWIFT.
Scanning for affected transfers and sending trigger MQ messages
is done periodically. In addition, transfers that are waiting for
being replicated by SWIFT are marked with a new condition
"waitForReplication" until the corresponding trigger message is
sent.

PM71255 MSIF DNFO4097E SHOULD BE AN INFORMATIONAL EVENT
Formerly, if a user attempted to start the CIN for the DNF_O_FT
service and the CIN was already active, the error event DNFO9047E
was issued.
Now, the informational event DNFO9051I is issued instead.

PM77109 MSIF LFTRETRY ON GETFILEQ FAILS ON THE FIRST OCCURANCE AFTER
MQ CONNECTION HAVE BEEN RE-ESTABLISHED
Formerly, when a file was to be received by MSIF using MQHA and
the queue manager was not accessible due to a missing connection
and the SAG tried to put the message to the MQHA GETFILE queue,
this MQPUT could result in the WebSphere MQ error 2113. MSIF sent
an error response to the SAG. The SAG didn't therefore retry the
MQPUT. The user needed to recover the transfer manually.
Now, MSIF can recover the transfer automatically.

PM77407 MSIF HIGH CPU UTILIZATION DURING CLEANUP OF OLD MSIF TRANSFERS
Formerly, the MSIF cleanup procedure caused a high CPU load.
Now, by improving an SQL statement of the cleanup procedure
the CPU load and the execution time could be reduced
significantly.

Product Alias/Synonym

WBIFN V3.1.1 Messaging Services for SWIFTNet InterAct and FileAct for z/OS

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Integration for Financial Networks
PTFs

Software version:

3.1.1

Operating system(s):

z/OS

Reference #:

7037014

Modified date:

2014-10-15

Translate my page

Machine Translation

Content navigation