Of these newly supported prerequisite levels, only the JDK 1.1.6 with Fix Pack 4 for AIX is a hard requirement. The other changes are supported levels that customers may move to if desired.

If you plan to install the JDK 1.1.7b, please refer to the Knowledge Base entry "Component Broker 2.0 Install Limitation with JDK 1.1.7b"

• IMPORTANT NOTE: These steps should be taken after step 6 of  the PTF installation process described in Install the Component Broker PTF2 on Windows NT  in the Installation section near the end of the PTF 2 Readme.
• Uninstall the existing Global Security Kit (GSK)
1. Quiesce all servers 
2. Stop the Component Broker service.
3. Uninstall the existing version of GSK by running the following command:
   c:\winnt\gskRUnin.exe CBroker
   Your installation of Windows NT may be in a different directory.
4. To make sure the GSK has been completely removed from the Windows NT registry, you can invoke regedit to look for GSK. Look for:

   hkey_local_machine\software\ibm

   If you find a subdirectory gsk, look in the subdirectory gsk\current version\regapps to see if there are any applications registered to GSK. If there are NO applications registered, or just your application registered, then you can simply erase the subdirectory gsk (including all subdirectories). If there are any other applications registered then you need to write these down (exactly, it's case sensitive) so you can add them after reinstall and then delete gsk as described.

5. Verify the completeness of uninstallation. Change directories to where you installed GSK previously and make sure all GSK files and subdirectories are removed. If they are not, remove them manually.
• Install the new GSK from the PTF  2
  1. Create a directory into which you want to expand (unzip) the files in the GSK package. Copy GSKRF301.zip from the cbroker\lib directory to the directory you just created.
  2. Change to the directory you created in step 1. Unzip GSKRF301.zip. This will result in several files being extracted into this directory.
  3. Run the set up program that was extracted in step 2 as follows:
     setup CBroker -f1gskRinstIS (that reads, f  "one" g with no spaces).
  4. Follow the instructions and answer questions appropriately. Be sure to install GSK into the same directory it was installed in before you uninstalled the previous version. Component Broker is configured to expect GSK in the same location.
  5. Verify the installation by running the following command from the GSK\bin directory:
     ikmgui.exe
  6. Restart the CBConnector service via the Start->Control Panel->Services panel.
  7. Use the SM EUI to resume the hosts that this fix was applied to. The resume action will re-start all application services, the name server, and the orb daemon.
• Notes and Considerations

  The new version of GSK must be installed on the same drive:directory where the original version of GSK was installed. The setup program for GSK will ask you where you want to install GSK.
  

regedit
select->HKEY_LOCAL_MACHINE->SOFTWARE->IBM->DCE for Windows NT ->2.0
On the right panel, look for privacyOption
If privacyOption is 0x0000001(1). This is DES version of DCE.
If privacyOption is 0x0000002(2). This is CDMF version of DCE.

Then obtain the DCE 2.0 Fixpack 6 (eco6)  from the Component Broker support team. Please send email to cbsupp@us.ibm.com requesting either the DES (encrypted) or CDMF version of the fixpack.

Then:

1. Run the self extracting file eco6??.exe to extract the install image.  Use eco06c.exe for CDMF and eco06d.exe for DES.
2. Once extraction is complete, run setup.exe in the current directory.
3. Select "Continue the installation."
4. After setup complete, enter "Finish" to restart the computer.

See also: If ECO 6 is in use

Corrected Problems Listed by Component

1. They do not override the buildFromData() framework method.
2. They do not override the buildFromDataObject() framework method.
3. The MO framework method overrides call up to the SOMProxy instead of the framework.
4. The BO framework method overrides call up to the SOMProxy only instead to both the SOMProxy and the framework.

The initialization value for nil object reference foreign keys of type "string" has been changed from "" to (const char*)"". In the CORBA C++ bindings, this insures the DO will get its own copy of the "" string to free.

Entry fields for specific and non-specific DDL were added to the  Application family wizard. If those fields are not blank, the DDL files generated will be defined as whatever was entered in the fields. Otherwise, DDL filenames will be generated from the Application Family name, that is, a specific DDL name will be the application family name with "Specific" added in the front as prefix, whereas non-specific DDL names will be the same as the application family name. If user defined specific and non-specific DDL filenames are the same, Object Builder will give an error message to prevent user from entering the same names. If the filenames violate the PDS naming convention (that is,  length exceeds 8 characters, first character not alphabetic, the rest of the characters are not alphanumeric), a warning message will come up. The model consistency checker will also check for this.

error EDC3070: Call does not match any argument list for "IString::operator+=".

The error occured when a Business Object contained an attribute of type wstring in its key. The error occured in the C++ implementation of  the Persistent Object for that Business Object when that Persistent Object used the Procedural Application Adaptor to access data in a CICS or IMS database. 

1. If a managed object is deployable in OS/390 and its IR file name is not compliant with the OS/390 rules for file naming.
2. If a DLL is deployable in OS/390 and its library name is not compliant with OS/390 rules.
3. If a PO is deployable in OS/390 and has a file name or a package name that is not compliant with OS/390 rules.
4. If DDL files will be generated for OS/390 and the specific or non specific file names are not compliant with OS/390 rules.
5. In specifying a DDL file, if the specific file name is the same as the non-specific file name, the non-specific file name will be overwritten.

The OS/390 rules for file naming are:

1. File should be 8 characters or less
2. First character should be an alpha character
3. Subsequent characters should be alphnumeric characters.
   

In assigning a Home to a container (while configuring an application),  if the user selects OS/390 as the only deployment platform, all user defined containers are now selectable in the Container page of the Configure Managed Object wizard.

After creating a Procedural Adapter Object (PAO) which uses the ECI or HOD connectors to access CICS or IMS data, it is common to run a program to test whether that PAO accesses the data properly. This is a common step before the PAO is imported into Object Builder, and the procedure is outlined in the CICS and IMS Application Adapter Quick Beginnings Guide.

Unpredictable results may occur with the first access to the CICS or IMS data. On an insert request, this may result in only the Key of the record being set.

These unpredictable results do not occur when running the PAO in a Component Broker Server in the Component Broker environment. They only occur in the IBM VisualAge for Java unit test environment.

A new version of the IBM Procedural Application Adapter Library project has been provided in the Component Broker R2.0 PTF 2. This new version is installed in the IBM VisualAge for Java IDE when the PTF is installed, but is not automatically selected as the current version to be used in the Unit Test environment.

Users experiencing problems in the Unit Test environment must make the new version the current version by following these steps:

1. Start the Visual Age for Java IDE by selecting the following from the Start Menu: Start->Programs->IBM VisualAge for Java for Windows->IBM VisualAge For Java.
2. Go to the Workbench. If you are not shown the Workbench, select: Window->Workbench.
3. Select the Projects tab on the Workbench notebook or tab book.
4. In the popup menu for the IBM Procedural Application Adapter Library project, select:
   Replace With->Another Edition...
5. In the dialog box titled "Select replacement for IBM Procedural Application Adapter Library", ensure that version 1.0.2.1 is selected. There is a small asterisk (*) preceding the version currently selected. If version 1.0.2.1 is selected, then press Cancel to return to the Workbench. If another version is selected, then select version 1.0.2.1 with the mouse and press OK.
   

IRDBIMExtLocalToServer::IDataObject inheriting from IBOIM390LocalToServer::IDataObject instead of from IBOIM390ExtLocalToServer::IDataObject, and

IBOIM390ExtLocalToServer::IUUIDDataObject inheriting from IBOIM390ExtLocalToServer::IDataObject instead of from IBOIM390LocalToServer::IDataObject.

This was a visual misrepresentation of the true OS/390 Component Broker MOFW and had no effect on code generated by Object Builder.The Object Builder Inheritance pane now shows the correct OS/390 Component Broker  inheritance.

Now, update() throws a java.lang.Exception when the check fails. This exception  is caught in the catch block immediately below the throw statement. It is then rethrown as an IDataObjectFailedException.

Customers will need to regenerate the persistent object's code if they are using   optimistic PAA APPC (LU 6.2) connections. They will also have to rebuild their model and replace the .jar files used by System Manager with the new .jar files.

59002
Windows NT, AIX, S/390

This was a quickfix  for a segmentation violation in somsrsm on AIX when running with AIX JDK 1.1.6 FixPack 4 or newer. The quickfix provided a replacement for ibmcbjs.zip and somshor.zip which synchronized BO/DO finalizers to prevent a thread race condition. The quickfix did not affect NT since finalizers on NT run single threaded.

This problem appears using JAVA BOs on AIX, it does not appear using C++ on AIX. It does not appear at all on NT. If your application has a handle signal at this spot in a Java BO based application, this PTF fix may solve the problem.

The following steps need to be followed to use the MOFW UUID support once the output of MOFW has been generated:

1. Modify the DOImpl idl, ih and .cpp files to use IManagedAdvancedServer include files and IManagedAdvancedServer::IUUIDDataObject  instead of the existing BOIM ones
2. Modify the Copy helper idl, ih and .cpp files to use IManagedAdvancedServer include files and IManagedAdvancedServer::IUUIDCopyHelperBase instead of the existing BOIM ones
3. Modify the client and server makefiles to move the copy helper files from the client makefile to the server makefile
4. Use generateUuid() method instead of generate() on the UUIDPrimaryKey class
   

PrimaryMessage: The function handleSignal(int,int,CONTEXT*):608 reported an error.
ExtendedMessage: A system error was detected - 24 FLT-OVERFLOW (OS signal nbr:3).
Error occurred at (Eip):075ac844, in source file:javai.dll

occurs, followed by server failure.

The IOM runtime (somsh.dll) was modified to  restore the state that the Java VM expects.

CORBA exception CORBA::BAD_PARAM, error code is 0x49420103
(ICACHE_BAD_PARAM_LARGEANYSTR).

IBOIMSystemObject_IContainerImpl::resolveToObject
(IIMFLocalToServer::IKeyComonent_ptr):1672 raised CORBA exception CORBA::INV_OBJREF, error code is0x464 SOMBOIM_ICONTAINERMINOR_REACTIVATION_FAILED.

PrimaryMessage: The function WeakRef::pin:98 reported an activity
RawData: 0000 64 6C 6F 70 65 6E 20 66 - 61 69 6C 65 64 20 20 dlopen failed

Due to the repercussions of this failure, this is typically followed by a handlesignal and a core dump. The problem was eliminated with a change to libsomsh.so which will now  invoke dlopen with different arguments.

Windows NT, AIX

54007
Windows NT, AIX

58617
S/390

Problem Abstract

PTF Fix Information

1. Object Builder errors when JIT turned on (This also requires the Component Broker R2.0 PTF1; see Object Builder problem when JIT on)

2. Garbage collection problems (see PAA/CICS sample failure)

a) Multiple copies of setloc1.dll (DCE, GSK) in Component Broker 2.0 conflict with each other resulting  in the wrong setloc1.dll being loaded. 
b) SSL fails with large amounts of returned data.

Description of the fix 

A new version of the Global Security Kit (GSK) package contains the fix. As part of the PTF installation, this package will be placed in your cbroker\bin directory. 

The following steps for uninstalling and installing the GSK package should be taken during the process listed in Install the Component Broker PTF on Windows NT. The proper time to proceed with the GSK steps is noted in item six in the section "Install the Component Broker PTF on Windows NT."

Uninstall the existing Global Security Kit (GSK)

1. Stop the Component Broker service. 

2. Search your system to find out where GSK was originally installed. It may be in \Program Files\IBM\GSK, or some other location. You can find this information by invoking regedit to look for GSK. 
Look for: 

hkey_local_machine\software\ibm.

If you find a subdirectory gsk you want to look in the subdirectory gsk\current version\regapps to see if there are any applications registered to GSK. If there are NO applications registered or just your application register then you can simply erase the subdirectory gsk (including all subdirectories) and this will clean up this portion. If there are any other applications registered then you need to write these down (exactly, it's case sensitive) so you can add them after reinstall and then delete gsk as described.

3. Uninstall the existing version of GSK by running the following command:
       c:\winnt\gskRUnin.exe CBroker
Your installation of Windows NT may be in a different directory.

4. Verify the completeness of uninstallation. Change directories to where you installed GSK previously and make sure all GSK files and subdirectories are removed. If they are not, remove them manually.

Install the new GSK from the PTF

1. Create a directory into which the self-extracting GSK package will be expanded. Copy GSKRF301.exe from the cbroker\bin directory to the directory you just created.

2. Change to the directory you created in step 1.Run the self_extracting GSK package.  This will result in several files being extracted into this directory. GSKRF301 ./ /D

3. Run the set up program that was extracted in step 2 as follows:
       setup CBroker -f1gskRinstISU

4. Follow the instructions and answer questions appropriately. Be sure to install GSK into the same directory it was installed in before you uninstalled the previous version. Component Broker is configured to expect GSK in the same location.

5. Verify the installation by running the following command from the GSK\bin directory:
       ikmgui.exe

6. Restart the CBConnector service via the Start->Control Panel->Services panel.

7. Use the SM EUI to resume the hosts that this fix was applied to. The resume action will re-start all application services, the name server, and the orb daemon.

Notes and Considerations

The new version of GSK must be installed on the same drive:directory where the original version of GSK was installed.  The setup program for GSK will ask you where you want to install GSK.

TOOLKIT

The User Interface has been modified to clarify the selective bridging process.

The getters, setters and framework methods of a subclass BOImpl will now be generated according to the "Lazy Evaluation" configuration of its superclass BOImpl.

The solution included in the PTF is that the Home reference retrieved by the getter is now saved in a DOImpl class static variable the first time the getter is called. On all subsequent calls, the getter simply reuses the Home reference. This avoids unnecessary calls to the Name Service and improves performance.

Previously, when an object reference was mapped to a stringified handle in the PO, the getter method for the reference on the DOImpl was emitted incorrectly by Object Builder if the stringified handle was empty (which represents a nil object reference).

In certain time windows, the home could deadlock when the evaluate method ran on the home while another transaction using the query service on another thread requested data from the home.

Multi-client queries should no longer deadlock in this fashion.

57195
Windows NT

In the Object Builder emitters the correct variable is now assigned to char* temp in getKey().

However, in a future release DDL without the operatingSystem property will be rejected.  This means that DDL generated prior to the PTF will have to be regenerated or the operatingSystem property will have to be added manually.

The operatingSystem property can have the values aix, nt or solaris (no quotes). For example.,

   operatingSystem = aix;

The DOImpl update() method emitted by Object Builder now tests the iDirty flags of all classes in a DOImpl class hierarchy to determine if a true update is required.

1. Method declarations necessary for Queryable Home MOs were missing from the MO.ih file.

2. Several methods were declared and defined in the MO.ih and MO_I.cpp files that should not be:
    - getAttributes()
    - setAttributes()
    - processState()
    - reactivateObject()
    - homeIdentification()
    - getMOContainer()
    - finishInitOrUninit()
    - getContainerName()
    - createProxy()
    - buildDataObject()
    - buildFromData()
    - buildFromDataObject()

3. The getMetadata() method returned ::IBOIMLocalToServerMetadata::IMetadataPackage_ptr.
   It should instead return ::IBOIM390LocalToServerMetadata::IMetadataPackage_ptr.

4. The Java Home MO framework methods delegated to the IManagedAdvancedServer framework class. They should instead delegate to the BOImpl SOMProxy class.

5. There was a call to getMixin() which was removed. In its place should be a reference to the mixin pointer held by the MO.

With the PTF, the key is always going to be public (it must be defined on the interface, and so must be public). New code generation will use the key getter. 

Fixes to EJB deployment tools and runtime

After the PTF has been applied, the MO setMixin() method emitted by Object Builder calls the superclass' setMixin() and then initializes its own reference to the mixin. This insures that all classes in an MO class hierarchy have a properly initialized mixin reference.

The OS/390 Component Broker PAA PO implementation code emitted by Object Builder now calls the correct method, setWorkSpaceID(workSpaceId).

With the PTF, Object Builder has altered the rules for string-to-VARCHAR mappings in the PO. When, and only when, the attribute is part of the primary key, the PO converts "" into a zero-length, non-NULL column value instead of a NULL column value.

With the PTF, a "Files to Include" page has been added to the Business Object Implementation Smart Guide. This page is based upon the like-named page in the Business Object Interface Smart Guide. When adding an include, you may either select from a list of known CORBA IDL files or you may free-type a file name.

Selecting a CORBA IDL file for inclusion in a BOImpl has two effects on the emitted code:

1. The BO.ih file will contain a "#include" statement for the .hh file of the selected IDL file.
2. The BO_I.obj recipe in the makefile will contain, as a dependency, the .hh file of the selected IDL file provided it is not a Component Broker framework file.

Free-typing an include filename for the BOImpl has two effects on the emitted code:

1. The BO_I.cpp file will contain an "#include" statement for the file exactly as entered.
2. The BO_I.obj recipe in the makefile will contain, as a dependency, the filename either...
 a) exactly as entered for platforms other than Windows NT,
 b) exactly as entered for Windows NT if the filename is absolute, or
 c) exactly as entered and prefixed by {$(INCLUDE)}\ for Windows NT if the filename is relative.

The fix allows applications to install on systems with Component Broker versions later than the Component Broker version on which the application was generated.

The Cache Service PO internalizeData() method no longer leaks memory.

The workspace ID is now correctly initialized on the PO by the DOImpl.

1. From within VisualAge for Java select the project IBM Component Broker Connectors. If this is not currently in your workspace, then select Quick Start ->Add Feature to add it.
2. Right-mouse click and choose import.
3. Select import from a directory.
4. Choose the x:\CBroker\lib directory and select the two .class files:
     CICSEXCIInteractionSpec.class
     IMSOTMAInteractionSpec.class
5. Select OK.
6. It will issue the following warning: The project IBM Component Broker Connectors is a version. A new edition will be created for you.Would you like to continue? Choose Yes. The OS/390 Component Broker InteractionSpecs are now available for developing your CB/390 PAA Beans.

1) Odd characters appeared in the C++ source code where lines would normally be split. The odd character is a control-M.

2) Problems with include malloc.h.

3) An error indicating that identifier workSpaceId was not defined in the constructor of the Persistent Object's key.

The correct temporary variable name is now used to set the Key object inside the getKey() method.

Solution:
The "SchemaIsUpdatable" property is now correctly exported and imported in XML form by Object Builder. However, any XML that was exported prior to this fix will still not have this property. To fix this, after importing the XML, open the properties smartguide on each PO that should be read-only (non-updatable) and uncheck the "Table/View is Updatable" property.

Note: typically, tables should be updatable and views should not be updatable.

Code changes were made to ensure that the generated makefiles account for the situation where a DOImpl's POs are in a linked model. Customers who have exercised a bottom up scenario with their DOImpls in one model while their POs are in another will need to regenerate their makefiles with the PTF. Otherwise, their makefiles will continue to assume that a DOImpl's associated POs are in the same model, which could result in build breaks.

Here is the workaround: Select SIGTRAP notification in the Options->Debugger Settings->Exception Filtering menu. If/when a SIGTRAP is generated, click examine on the exception notification to clear the exception, then press run to continue execution.

1. A fix was made to JDK 1.1.6. Apply the AIX Developers' Toolkit for Java (JDK) 1.1.6 Fixpack 4 (fixpack level IX86441) to obtain this fix.
2. A fix was made to the Object Builder code.

 1. Open the SmartGuide for the module that contains the struct definition.
 2. Change to the "Constructs" page, and select the struct.
 3. Select the member(s) for which the error occurs, and change the type(s) to anything else (such as long)
 4. Hit Finish on the SmartGuide
 5. Re-open the SmartGuide, and locate the member(s) in question.
 6. Change the type(s) of the member(s) back to their original definition.
 7. Save the model.
 8. If required, generate the code.

Exception in thread "main" java.util.MissingResourceException: can't find resource for com.ibm.ivb.olt.constants.OLT_sv_SE (where sv_SE = default input locale)
...

The type of the attribute is now genererated correctly, and will compile. The name of the attribute now follows the standard Object Builder naming conventions (iAttributeName).

• Java Business Objects were used
• There were multiple clients accessing the server simultaneously
• Java garbage collection ran in the server.

Symptoms were that the server process permanently stopped responding to client requests. 

To verify that this is your problem, you can set the enable verbose garbage collection option on the Java Virtual Machine page of the System Management settings for your server image to yes and monitor the console output of the server process. You should see a message from the Java Virtual Machine shortly (within 0-3 minutes) before the server stop responding. The message will start with "managing allocation failure" andinclude the text "synchronously running <nn> finalizers" where <nn> is some number.

You may also see what appears to be a server hang due to long Java garbage collection runs. In this case, the server stops responding for up to several minutes, and then runs normally.

With the default settings for Java minimum heap size,
the server may run Java garbage collection so infrequently that delays more than a minute occur when garbage collection finally runs.

In this case clients with the default timeout setting (30 seconds) may report NO_RESPONSE. There are two ways to address this problem.

1) Set the client timeout to a larger value (System Management-> Client Style Images -> your client style -> ORB page -> "request timeout" field).

2) Set the minimum heap size on the Java Virtual Machine page in your server image's System Management settings to "100000". This will set the minimum heap size to the smallest possibly value (100,000 bytes), thus maximizing garbage collection efforts.

Setting this field will cause garbage collection to occur approximately 12 times more frequently than the default settings (in minutes instead of hours) and reduce the length of the garbage collection pause proportionately.

For more information about making this change to your System Management settings, see the topic Java Virtual Machine Tuning in the Late Breaking News for Component Broker 2.0.

The fix makes the implementation of string_to_object() properly transfer ownership of the object returned to the caller. It does this by incrementing the object's reference count.

This could happen if a local only object is put in an Any, or if string_to_object was called directly, in addition to other ways.

Since the fix properly increases the reference count, where previously it wasn't being incremented, applications may have been written that didn't expect to take ownership and weren't releasing the object properly. Therefore the fix may expose memory leaks in the application. Any applications currently doing a string_to_object and getting a local object must not have been releasing it properly, otherwise they'd be seeing traps or coredumps.

SAMPLES

To work around this problem when running with any JDK 1.1.6 level earlier than Fixpack 4, restart the server after the sample fails and it will then run successfully.