IC76117: WEBSPHERE MQ V7: INSTALLATION OF FIX PACK 7.0.1.4 TERMINATES UNEXPECTEDLY

WebSphere MQ V7.0 Fix Pack 7.0.1.6
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.6

APAR status

• Closed as program error.

Error description

• The end user applied WebSphere MQ fixpack 7.0.1.4 on top of an
  earlier fix pack. The installation processing terminated
  unexpectedly, reporting the following errors in the install log
  (amqicsdn.txt):
  
  15:49:34   Time difference 72000000000 is not 1 hour.
  15:49:34 ***Unacceptable
  
  When this error happens the installation ends with:
  "amqicsdn.exe ending with RC 1603 (0x00000643)".
  

Local fix

• This parameter will allow the install to complete:
  .
  MQPNOCHECKVER=1
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users installing the 7.0.1.4 fix pack on top of an earlier fix
  pack on a Windows platform, when Daylight Savings time is in
  force.
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM SUMMARY:
  Before installation of 7.0.1.4, files are unpacked to a local
  "source" directory.
  
  The unpacking phase of the install placed files in the "source"
  directory with a Coordinated Universal Time (UTC) timestamp
  that was incorrect. The timestamp was incorrect by multiples of
  one hour.
  
  Testing has shown the problem to be present when Daylight
  Savings time is "on" in the operating system, and the WebSphere
  MQ 7.0.1.4 install activity is being performed in a time of the
  year when Daylight Savings is applicable.
  
  Further WebSphere MQ install processing takes place after the
  unpacking phase. At this time, checks are made that timestamps
  on files to be installed are no older than the files already
  installed. In 7.0.1.4 there were several files that had no
  change, or a small change, to their timestamp since earlier fix
  packs.
  
  Combined with the problems relating to timestamps during
  unpacking, this check was identifying some files as being too
  old, and then halting the installation processing.
  

Problem conclusion

• WebSphere MQ 7.0.1.5 does not suffer this problem, because all
  the files that were not updated in 7.0.1.4, are updated in
  7.0.1.5.
  
  To prevent this problem emerging again in future, an
  improvement is also made in the WebSphere MQ fix pack
  packaging, to ensure that files are always updated with newer
  timestamps for each fix pack.
  
  It is possible to work around this problem with 7.0.1.4, by
  including an additional switch MQPNOCHECKVER=1 on the command
  line:
  
  WebSphereMQMDV7.0.1.4EnUs.exe -a MQPNOCHECKVER=1
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.6
  --------           --------------------
  Windows            U200328
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available, information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• 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

  WMQ WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R700 PSY

     UP