JR33177: CAN'T CONNECT A SERVER WITH 8.0.1 FP2 WITH CLIENTS WITH 8.0.1 FP 1 WITHOUT JR30612 INSTALLED.

APAR status

• Closed as program error.

Error description

• The problem is that in JR30612 we changed the path way
  lockObjects(Collection c) works on the server side.  Now, it
  expects an InternalLockRequest to be passed in, and throws an
  exception if anything else is passed in.  We need to change
  this so it will accept both an InternalLockRequest (for patched
  clients) and a collection of EObjects (for unpatched clients).
  This patch became a part of 8.0.1 FP2. This patch is just
  focusing on making a server that has 8.0.1 FP2 installed be
  able to work with an unpatched 8.0.1 FP1 (or even plain old
  8.01) client.
  

Local fix

• this fix is included in 8.0.1 fix pack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  XMeta users that have JR30162
  ****************************************************************
  PROBLEM DESCRIPTION:
  Clients with 30162 applied could not connect to the server at
  FP2.
  ****************************************************************
  RECOMMENDATION:
  Apply JR33177 patch.
  This change is included in 8.1 Fix Pack 1.
  ****************************************************************
  

Problem conclusion

• Clients with JR30162 applied can now connect to server at FP2.
  

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:

Modules/Macros

• XMETA
  

Fix information

• Fixed component name

  INFO SRVR PLATF

• Fixed component ID

  5724Q3612

Applicable component levels

• R801 PSY

     UP