Resolution:
Description:
============
Customers who are upgrading to R5.2 and using old EECONFIG JCL to implement configuration changes do not see  these changes take effect.

Environment:
============
o Object Service Broker (OSB) customers on z/OS

Symptoms:
=========
The symptoms of this problem are that new configuration changes do not take effect.

Cause:
======
The problem here is the name of the configuration modules produced.  
At R4.x  releases these were prefixed HRN.
At R5.0 these were prefixed S6B with an alias prefix of HRN but the system used HRN prefixed alias name.
At R5.2 the system looks for the S6B prefixed name.

The EECONFIG JCL supplied with the OSB upgrade package creates both the S6B prefixed name and the HRN prefixed alias.

Older EECONFIG JCL only generated the HRN prefixed name. At R5.0 this still worked but at R5.2  this no longer works.
When the old JCL is run for the first time the ALIAS between the S6B prefixed module and the HRN prefixed alias is broken and you end up with an obsolete S6B prefixed module, that will still be used, and a new HRN prefixed module that will  not be used.

Resolution:
===========
Change your old EECONFIG JCL to generate S6B prefixed module names.

References:
===========
TIBCO® Object Service Broker for z/OS Installing and Operating Software Release 5.2.0

Using an old EECONFIG JCL deck.