Fix (APAR):  JR26041

Status:  Fix

Release:  6.0.2.1,6.0.2

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR26041

Byte size of APAR:  114688

Date: 2007-05-02

Abstract:  The MQ body data binding should have access to all the parsed MQ headers when the message comes in from MQ. Lazy parsing defers the execution of the body data binding and some code

Description/symptom of problem:  
JR26041 resolves the following problem:

ERROR DESCRIPTION:                                              
The RFH2 usr folder content from an incoming MQ message is      
needed in the scenario.                                         
Customer intends to develop a custom dat binding and consturct  
the Data Object from MQMD, payload and RFH2 usr attributes.     
However, the RFH2 header in the usr folder is not accessible    
from the Data Binding framework.                                
It has been determined that this information may be stripped    
during the Function Selector step.  The headers are available   
from within the Function Selector, and can be viewed, however,  
the data cannot be manipulated.                                 
                                                                
It has been observed, that a possible workaround was to try     
to use a different function selector: use Type                  
information as the native function as the function              
selector -- hoping that it would keep the RFH2 header content   
and followingly pass to the body data binding where we can      
populate the returned Data Object content from both the RFH2    
header and message                                              
payload (desired result)                                        
                                                                
But the actual results are the data passed in with "arg1" to the
read(MQMD arg0, List arg1, MQDataInputStream arg2) method of the
body data binding is NOT complete - although it contains some   
attributes, it is missing the USR folder attributes.            

LOCAL FIX:                                                      
None at this time.                                              

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x and
6.0.2.x users using RFH2 USR folder in MQ
messages.

PROBLEM DESCRIPTION:
The MQ body data binding should have
access to all the parsed MQ headers
when the message comes in from MQ.
Lazy parsing defers the execution of
the body data binding and some code
to map MQ RFH2 <usr> folder
properties into the generic SMO
message properties inadvertently
removed part of the RFH2 before the
body data bindings got to access it.

RECOMMENDATION:
None

MQ RFH2 headers <usr> folder properties mapping into SMO
messages gets removed by Lazy parsing feature in WPS 602.
These leads to issues if customer is relying on these
properties in their MQ messages.

PROBLEM CONCLUSION:                                             
For inbound flows, the data is carried in two places. For       
outbound over MQ, anything in the RFH2 takes precedence over    
anything of the same name in the JMS properties.                


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.2.1 is installed on the system.
Also download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere





Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.





Directions to re-apply fix:  
1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.





Additional Information: