Fixes for the following APARs are contained in this PTF:
PM74134 Base UPDATES FOR ADMINISTRATION AND OPERATION
A new Administration and Operation Facility is introduced. You
can install it after the migration has finished by assigning the
new service bundle DNPAO. For further information refer to the
Administration and Operation Facility Users Guide.
PM77555 Base MODIFY THE CONTENT OF THE ERROR MESSAGE "DNFL9430E" TO BE
CLEARLY DISPLAYED ON MERVA SCREEN
The message text for message DNFL9430E was changed from
"The local RM data store does not contain an authorisation that
authorizes the request; direction='direction', ASP name='aspName',
ASP version='aspVersion', reason='reason'."
"Request is not authorized; direction='direction', reason='reason',
ASP name='aspName', ASP Version='aspVersion'."
PM77417 Base DNICPD/DNICDPM IMPROVEMENTS NECESSARY TO DETERMINE THE STATE OF
A PREVIOUS ACTION AND AVOID PROBLEMS DURING APPLYING MAINTENANCE
Formerly, there were poor indications to determine whether the
last re-customization or migration has been implemented.
Now, the preparation status information is enhanced with the
mode (customization or migration) for which deployment data has
been generated and are not yet implemented. A script 'dnicdpst'
is introduced to show whether a deployment is ongoing and in
which mode it has been initiated.
PM76884 Base REMOVE CHECK FOR CHARACTER 8 IN RECEIVERS BIC, NOW ALLOW "1"
The check for character 8 in receivers BIC has been removed.
Now, "1" is allowed.
PM73084 Base DNICONFIGSVB WAS NOT REMOVED WHILE USER REMOVE A DNFEFAS SVB
Formerly, after completing a recustomization with the remove of
the DNFEFAS SVB the DNFEFAS was still existing on the system.
The dnfczmlc generated the EFAS configuration even the DNFEFAS
SVB was removed.
Now, dnfczmlc removes DNFEFAS SVB correctly.
PM74801 Base Update CIN for MSIF Apar PM71255
The changes required for MSIF Apar PM71255 make an update of
Base components CIN, RMA, and RM necessary. This Base PTF for
APAR PM74801 provides the required changes.
Formerly, if a user attempted to start the CIN for the DNF_L_TR
or DNF_L_IMP and the CIN was already active, the error event
DNFL9037E was issued.
Now, the informational event DNFL9041I is issued instead.
Fixes for the following APARs from superseded PTFs are also contained in this
PM75280 BASE REQUIRED BASE UPDATE FOR PTF FOR FIN APAR PM73889 (NO CONSISTENCY
CHECK IN FIN FOR LIVE VS T&T BICS)
This Base PTF provides the RM filtering stored procedure updates
required to fix the problems detected in FIN Interface Layer:
- handling of a tank file from SWIFT
- consistency check for LIVE vs TEST LTs (as described in APAR
PM74804 Base DELAYS IN FIN LOGIN AFTER APPLYING PTF UK81038
After applying PTF UK81038, FIN login will complete with a
delay of serval minutes only. The timeframe between the event
DNFF4101I and DNFF4103I, which normally occurs within less than
a second, will take several minutes.
Now, this has been corrected.
PM69720 Base CLIC LIBRARY TOOK A LOT OF SYSTEM RESOURCE WHILE
USER RUN THE FIN LOGIN AND RM IMPORT
Formerly, in some cases crypto service (used e.g. in FIN login or
RM import) could hang for several minutes consuming lots of CPU
Now, this has been corrected.
PM71482 Base IMPROVEMENT IN CONFIGPROVIDERNODE
During FIN processing, the WebSphere BI for FN Configuration-Data
Provider node (CPN) occasionally must check whether the cache is
out-dated and needs to be rebuilt.
Formerly, when a certain type of database error occurred during
an attempt to check the cache, the CPN was unable to properly
detect and handle that error. This caused the cache to become
corrupted, which in turn resulted in the following errors:
- BIP2230E MQW1BRK DNF_FIN 43 ERROR DETECTED WHILST PROCESSING
A MESSAGE 173 IN NODE 'DNF_ILS_ACK_1251.DnfIlsAck1.
DniConfigProvider.DniCPN1'. : ImbCniNode(1892)
- DNIP3402E MQW1BRK DNF_FIN 43 WEBSPHERE BI FOR FN ERROR DURING
CPN PROC 174 Processing SEE DESCRIPTION OF MESSAGE 'DNIP3370E'.:
- Error in DNI_A_EVENT : DNIP3402E 5/8/12 12:36:40 PM OUMO
DNF_ILC_FIN WebSphere BI for FN error during CPN processing;
see description of message 'DNIP3370E'.
Now, the CPN properly detects and handles the database error.
When it detects the error for the first time, the CPN reports the
error and causes the current transaction to be rolled-back. If it
detects the error additional times, the CPN does not report these
additional occurrences and does not rebuild the cache.
Note that this APAR fix does not address the underlying database
error, but only ensures that the CPN properly detects and handles
that error, and prevents the cache from becoming corrupted.
PM70132 Base CONFIGURATION CHANGES ON 29TH OF FEBRUARY LEADS TO A DNIP3370E
Formerly, when WebSphere BI for FN configuration data was
changed on 29 February, this sometimes caused error message
DNIP3370E to be issued.
Now, this has been corrected.
PM69280 Base DNICDP DNIZ9004E 'JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION
Formerly, when issued in a BPXBATCH job the IBM WebSphere BI
for FN Customization Definition Program dnicdp aborted with
the message DNIZ9004E Exception:
Now, dnicdp works correctly when called in a BPXBATCH job.
PM69803 Base IMPORT BIC DATA WITH DNPRDU LEADS INTO JAVA LANG OUTOFMEMORYERROR
Formerly, when importing most actual BIC data, for instance,
BIDELTA_20120707.TXT with dnprdu, the dnprdu dumped and ended
Now, the Xmx in the parameter in dnprdu has been set to 512 MB.
PM70742 Base SWIFT SR2012: UPDATE PTF FOR WEBSPHERE BI FOR FN MESSAGE
This PTF delivers support for Funds 4.4 and updates to the
FIN System Messages (Cat 0) and schemas.
PM73201 Base PARSING ERROR IN XSD SCHEMA MQRFH2_COMIBMDNI_DNF.XSD DUE
TO MISSING ELEMENT 'SWIFTTIME'.
Formerly, there was a parsing error in xsd schema
MQRFH2_ComIbmDni_Dnf.xsd due to missing element <SwiftTime>.
Now, a new element for MSIF API field <SwiftTime> is added.
PM73120 BASE ASP PROCESSING THREAD HANDLING WITH 2 DIFFERENT SYMPTOMS
'DNPA1153E: MISSING ELEMENT' AND NULLPOINTER EXCEPTION
Formerly, after you installed the Base PTF UK80316 you might
experience an unexpected behavior in FIN and FMT FIN services.
One or both of the following events could occur:
DNIE4497E 9/10/12 11:40:19 AM OU1 DNF_ILC_FIN Exception without
valid message ID; exception data: message catalog='BIPv610',
error number='4395', parameters='((java.lang.NullPointerException)
DNFH3715E 9/17/12 3:35:52 AM OU1 DNF_ILS_FIN Cannot access ASP
data; reason='DNPA1153E: Missing element 'RequestTypePattern'
in top-level element 'RMAFilter'.'.
For this, ISN Messages processed by the DNF_ILC_FIN (or DNF_PF_IS
for FMT) might be returned to the sending FIN application with an
DNFH3799E reason. OSN Messages processed by the DNF_ILS_FIN might
get stuck in the DNF_IAMS database table. The corresponding
trigger message is discarded.
Now, this behaviour has been corrected.
PM66812 Base RMA FILTER CRITERIA DOES NOT WORK PROPERLY SEARCHING FOR
Formerly, when searching RMA filter criteria for Q&A Status
"Action Required" the resulting hits are not shown as number
of hits, but only the the total number is shown.
Now, the number of hits is shown.
PM69567 Base RMA: DISPLAYING THE PERMISSION DIALOG WITH IE V8
Formerly, when using Internet Explorer V8 in compatibility mode
and when displaying the Permission dialog to select specific
message types for the displayed category, the dialog is empty.
Now, the Permission dialog is shown correctly.
PM64150 Base RMA APPROVAL PROCESS CONFIGURATION IS IGNORED.
Formerly, if the name of a business OU follows SYSOU when
sorted alphabetically, the configuration for the RMA approval
process was ignored and the default values were used instead
(Approval Steps = 1, Approval User Restriction = NotPrevious).
Now, the RMA approval process follows the configuration.
PM57686 Base NO RESPONSE DURING WRONG .QUIT CMD FROM DNICLI
Formerly, when dnicli command '.quit' was issued with
parameters dnicli did not issue an error message and did
Now, when dnicli command '.quit' is issued with
parameters dnicli responds with error message DNIK2508E.
PM57921 Base DNPRDU CREATES EMPTY TRACEFILE
Formerly, when a trace level was set to SEVERE or WARNING,
dnprdu created an empty trace file, even when no SEVERE or WARNING
Now, when one of the trace levels is set and no SEVERE or
WARNING messages occure dnprdu deletes the trace file.
PM49728 BASE NO DEPLOYMENT DATA CREATED BY DNICDP WHEN ONLY BROKER BAR FILE
PROPERTIES ARE CHANGED
Formerly, when the CDD was modified to change broker bar file
properties only (e.g. commit count and/or commit interval),
DNICDP provided a wrong output. The updates to the CDD were
not reflected in deployment data. Though activities were required,
the instructions.txt was generated resulting in the following
message issued: "No deployment data was generated because it
is not needed."
Now, this has been corrected.
WBIFN V3.1.1 Base for z/OS
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.