APAR status
Closed as program error.
Error description
Rational Business Developer V7.5.1.5: In VisualAge Generator, floating maps can be used as pop-ups. This means a converse is done on a map and then a converse is done on another map that only overlays a portion of the page allowing you to interact with it. After migrating these maps to Rational Business Developer and generating COBOL for the migrated forms (EGL term for maps), the issue is text from the underlying form (the first one conversed) is 'bleeding through' or seen within the boundaries of the floating form. This is not the expected behavior as VisualAge Generator does not show this 'bleedthrough' text data. The reason EGL allows this text to show through is due to the way the VisualAge Generator to EGL migration tool works. VisualAge Generator allows the creation of 'zero length' constant fields without default attributes for any place on the form that does not have text in the constant field (like a label) or a variable field. It was unknown that this technique was used to prevent bleedthrough. Also in VisualAge Generator, the map editor might create many constant fields with no contents and default attributes implicitly based on the layout. Basically, once the map is edited, the editor creates constant fields to 'fill' any white space on the map (no label or variable field). However, in a floating map the 'zero length' fields with default attributes do matter and control the way the datastreams are built. Once maps with these type of fields are migrated to EGL using the migration tool, these constant fields are eliminated from the form. The elimination of these fields is by design as the migration tool is 'cleaning' up all the constant fields with default attributes as they really had no meaning nor was it thought to affect what was displayed on the form. It was thought that all of these were only there due to the way the map editor works and did not affect the behavior. This design is incorrect. In addition to floating maps, fields with a zero length and default attribues should not be removed from fixed partial and full screen maps. Another example of one of the symptoms of this problem is some text remains on the screen after a button is pressed that is supposed to remove that text.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Users Affected: Rational Busniess Developer before V7.5.1.5 users migrating floating maps from VisualAge Generator and generating COBOL for the migrated forms. Problem Description: In VisualAge Generator, floating maps can be used as pop-ups. This means a converse is done on a map and then a converse is done on another map that only overlays a portion of the page allowing you to interact with it. After migrating these maps to Rational Business Developer and generating COBOL for the migrated forms (EGL term for maps), the issue is text from the underlying form (the first one conversed) is ?bleeding through? or seen within the boundaries of the floating form. This is not the expected behavior as VisualAge Generator does not show this ?bleedthrough? text data. The reason EGL allows this text to show through is due to the way the VisualAge Generator to EGL migration tool works. VisualAge Generator allows the creation of ?zero length? constant fields without default attributes for any place on the form that does not have text in the constant field (like a label) or a variable field. It was unknown that this technique was used to prevent bleedthrough. Also in VisualAge Generator, the map editor might create many constant fields with no contents and default attributes implicitly based on the layout. Basically, once the map is edited, the editor creates constant fields to ?fill? any white space on the map (no label or variable field). However, in a floating map the ?zero length? fields with default attributes do matter and control the way the datastreams are built. Once maps with these type of fields are migrated to EGL using the migration tool, these constant fields are eliminated from the form. The elimination of these fields is by design as the migration tool is ?cleaning? up all the constant fields with default attributes as they really had no meaning nor was it thought to affect what was displayed on the form. It was thought that all of these were only there due to the way the map editor works and did not affect the behavior. This design is incorrect for floating maps IF the the maps are used as pop-ups AND the technique to prevent bleed through of the underlying maps is used.
Problem conclusion
This APAR fix has the UI changes in the VAGen to EGL preference page.
Temporary fix
Comments
APAR Information
APAR number
PM17268
Reported component name
VAGEN2RBD MIGRA
Reported component ID
5724S5002
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-24
Closed date
2010-10-14
Last modified date
2010-10-14
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
VAGEN2RBD MIGRA
Fixed component ID
5724S5002
Applicable component levels
R751 PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
14 October 2010