Fix pack 7.5.1.4 is now available. It includes fixes in many areas of the
product, as well as significant runtime performance improvements in both Java and COBOL environments. Everyone using RBD 7.5.x should install it. See IBM Rational Business Developer 7.5.1.4 Release Information for more info, including installation instructions and the list of APARs which are fixed. The download instructions are here.

If you generate COBOL for System z, you should also install PTF UK51729.

Rational Business Developer version 7.5.1.4 includes these enhancements:

• Improvements in COBOL runtime performance affect the following kinds of processing:
  data-table access, dynamic-array access, assignments, SQL statements,
  exception handling, calls, string handling, and other memory usage. Consider re-generating existing applications, especially if they access SQL databases extensively or access data tables.
• Improvements in Java runtime performance affect the processing of system libraries
  sysVar, vgVar, and converseVar. Re-generate existing applications only
  if you notice a problem with performance.
• An EGL-generated Java wrapper can now call an EGL main program that is
  generated to Java and can share a database connection with that
  program.
• EGL-generated Java code and the EGL debugger can now access z/OS batch programs and DL/I databases.
• A new preference exists to change the behavior of SQL Retrieve at
  development time, so that you can define EGL fields of type CHAR in
  relation to SQL table columns that are of type DATE, TIME, or
  TIMESTAMP. The new preference is Use EGL type char for SQL date, time, and timestamp in SQL Retrieve.
• The sysvar.remoteSystemID function can be used to dynamically specify the
  system name of a remote program, data file, asynchronous transaction,
  or transient data queue. The function now supports 256 characters if
  the EGL code is generated to Java.
• In regard to COBOL or Java generation, the new blanksAsZero
  build descriptor option helps control the runtime behavior when a
  program assigns text to a numeric variable. The default value is NO,
  which matches the previous behavior for Java generation. If you
  generate COBOL and currently set v60NumWithCharBehavior to NO, you should also set blanksAsZero to YES if the program compares character data to numeric data.
• Several new COBOL symparms are in place; for example, WRITEFUNCTIONDETAILS and WRITESTATEMENTDETAILS support the debugging of EGL-generated CICS COBOL programs.
• The Rich UI widgets were upgraded to version 1.0.2 and now match those that became available in EGL Community Edition.
• JavaScript code is now compressed when you deploy Rich UI code in the Workbench. Re-deploying existing Rich UI applications significantly reduces the size of the application code.
• In relation to widget-type creation in Rich UI, the @VEWidget complex
  property now includes a field named container. If you create a widget
  type and indicate that it represents a container, an EGL developer can
  place a container on the Design surface, drag a widget of another type
  from the palette, and drop that widget into the container.
• An EGL-generated VG Web transaction can now call another with parameters,
  such that the called transaction can interact with the browser. This
  capability is available if the target for each Web transaction is a
  Java platform. Also, you can use a new program property, enableJ2ee, to
  specify whether a VG Web transaction that runs completely in a JEE
  application server uses these JEE capabilities: data sources rather
  than direct database connections, and the JEE deployment descriptor
  rather than a Java properties file.
• The JSONName property can be used to copy a JSON string to or from a
  record, when the JSON field name is an EGL-reserved word or is not
  valid in EGL. Similarly, the FormName property is available when you
  develop an Interface part for accessing a service and are prevented
  from sending form data to the service because a field name in the form
  is not valid in EGL.