APAR status
Closed as program error.
Error description
Unnecessary processing of graphical data maps may occur on restart if the maps are stored in a named folder and either (for WebSphere Message Broker v8.0.0.4 or later) the MQSI_PREPARE_MAPS_ON_DEPLOY environment variable is set to TRUE or (for IBM Integration Bus v9.0.0.1 or later) the broker function level is set to 9.0.0.1 or later. This applies to restart of any of the following items: For WebSphere MessageBroker: - Message Broker - Execution group - Application - Message flow For IBM Integration Bus: - Integration Bus - Integration Server - Application - Message flow . When, in WebSphere Message Broker v8.0.0.4 or later, the MQSI_PREPARE_MAPS_ON_DEPLOY environment variable is set to TRUE, or, in IBM Integration Bus v9.0.0.1 or later, the function level is set to 9.0.0.1 or later, the behavior on restart for graphical data maps used in message flow Mapping nodes is that the deployed map references are validated, and if a persisted prepared map is available, then it can be used. However, if the maps are stored in a named folder, for example in a folder named "gen", then the restart time is extended by the time taken for full map preparation of the maps in the named folder.
Local fix
Move the affected maps from the named folder to the project root folder.
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Message Broker V8.0 or IBM Integration Bus V9.0 where maps for mapping nodes are prepared on deployment. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Unnecessary processing of graphical data maps may occur on restart if the maps are stored in a named folder and either (for WebSphere Message Broker v8.0.0.4 or later) the MQSI_PREPARE_MAPS_ON_DEPLOY environment variable is set to TRUE or (for IBM Integration Bus v9.0.0.1 or later) the broker function level is set to 9.0.0.1 or later. This applies to restart of any of the following items: For WebSphere Message Broker: - Message Broker - Execution group - Application - Message flow For IBM Integration Bus: - Integration Bus - Integration Server - Application - Message flow . When, in WebSphere Message Broker v8.0.0.4 or later, the MQSI_PREPARE_MAPS_ON_DEPLOY environment variable is set to TRUE, or, in IBM Integration Bus v9.0.0.1 or later, the function level is set to 9.0.0.1 or later, the behavior of graphical data map is altered and the maps are prepared for execution on deployment instead of when the first message flows through the node. With this option, the behavior for graphical data maps on restart is also changed. On restart, the deployed map references are validated, and if a persisted prepared map is available, then it can be used. However, if the maps are stored in a named folder, for example in a folder named "gen", then the restart time is extended by the time taken for full map preparation of the maps in the named folder. There are a number of resource name changes between WebSphere Message Broker and IBM Integration Bus Version 9.0. For details visit http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e tools.mft.doc/bb23814_.htm
Problem conclusion
The product no longer performs unnecessary map preparation on restart when maps are stored in a named folder. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.6 v9.0 9.0.0.4 The�latest�available�maintenance�can�be�obtained�f http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If�the�maintenance level�is�not�yet�available,�inf its�planned�availability�can�be�found�on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT04579
Reported component name
INTEGRATION BUS
Reported component ID
5724J0530
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-09-24
Closed date
2014-10-28
Last modified date
2014-10-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
INTEGRATION BUS
Fixed component ID
5724J0530
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020