Fixes are available
APAR status
Closed as program error.
Error description
When editing a BMS map and moving or shifting fields around, the editor does not sort the fields according to their respective row and column position within the BMS source. The problem was found to only manifest itself when editing and filtering on the top-most MAP listed of the MAP set in the source containing multiple BMS maps. Recreate steps: 1. Open BMS source containing two maps MAP2 and MAP1 2. From the design view (tab), select the "Filtering" icon and choose the top-most mapset MAP2 3. Grab and move (shift) one of field on row 1 over a few spaces. Then click on the source tab and inspect the order of the field positions (column and row) 4. Observe the field that was just moved appears as the first field on that row instead of its expected order MAPSET DFHMSD TYPE=&SYSPARM,LANG=COBOL,MODE=INOUT, X STORAGE=AUTO,TIOAPFX=YES MAP2 DFHMDI SIZE=(24,80), X LINE=01, X COLUMN=01, X DATA=FIELD, X TIOAPFX=YES,JUSTIFY=(LEFT) MAP1 DFHMDI SIZE=(24,80), X LINE=01, X COLUMN=01, X DATA=FIELD, X TIOAPFX=YES,JUSTIFY=(LEFT * DFHMSD TYPE=FINAL END *
Local fix
The workaround for this problem is to manually sort the fields in their respective order.
Problem summary
When a BMS field is dragged and dropped to a new position (row and column) on the BMS map using the Design tab, the definition for the field may not get re-located in the Source tab. Instead the definition for the field may remain in the original location in the source even though the row and column in the field definition will correctly represent the new position (row and column) on the screen. This can make it difficult for users reviewing the source to locate field definitions since typically the fields are ordered in the source by their position (row and column) on the screen.
Problem conclusion
The problem would only occur when there are multiple BMS maps in the BMS mapset. In addition it would only occur for BMS fields being dragged and dropped whose original position (row and column) on their map was the same as another field on a subsequently defined map within the mapset. The problem listed in this APAR has been resolved with IBM Rational Developer for System z V8.5.1.6 Fix Pack which is available from the Recommended Fixes support download page: http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
Temporary fix
Comments
APAR Information
APAR number
PI31087
Reported component name
RATL DEV FOR SY
Reported component ID
5724T0700
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-12-08
Closed date
2015-02-04
Last modified date
2015-02-04
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
RATL DEV FOR SY
Fixed component ID
5724T0700
Applicable component levels
R851 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSTRMM","label":"IBM Developer for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
16 October 2021