APAR status
Closed as program error.
Error description
===== State: WaitingInfo by:ramearum at 8/27/2012 4:29:02 PM ===== Can we move the escalation to 'Engineering complete'? You can track the issue further with the APAR. ===== State: Engineering by:mpaul at 8/24/2012 10:04:08 PM ===== Yes you can create a APAR for this issue. ===== State: WaitingInfo by:jamesbur at 8/23/2012 10:37:47 AM ===== can we open a defect on this issue? Thanks ===== State: WaitingInfo by:jamesbur at 8/22/2012 8:04:16 AM ===== Customer has replied back with the following (can we create an APAR on this issue?): ######### We have been using whole numbers in our sequence diagrams because we must document the steps of our diagrams. The steps in the documentation field are numbered to match the numbers in the diagram. The option to change the numbers is not stored per diagram. That option is set globally and only for that particular user. Our standard for the diagrams is to have whole numbers. This issue only occurs with diagrams that start from the leftmost edge, which are few in number in our models. We have been simply living with the fact that these diagrams do not show the numbers rather than having to redo the numbering in the documentation field. We are okay with what we're doing, but we would like a fix in the near future. Keith ############# ===== State: Engineering by:mpaul at 8/21/2012 6:07:56 PM ===== I was able to reproduce the problem with 8.5.x as well. However, this problem seems to be related to only 'Integer (whole) numbers' type of message numbering on sequence diagrams. If we use 'Complete, decimal separated numbers' then this problem is not observed. The message numbering setting can be changed by following preference option: Modeling-?UML Diagrams-?Sequence and Communication-?'Message numbering on Sequence Diagrams'. Please let me know if customer is comfortable with using 'Complete, decimal separated numbers' instead of integers as work around? While we continue to investigate the problem related to integer numbering. ===== State: Engineering by:gsynnes at 8/18/2012 4:56:08 AM ===== Please let us know when to expect an update on this issue. Thank you. ===== State: Engineering by:mpaul at 8/13/2012 12:57:01 PM ===== We were busy with end of iteration commitments last week. I will look into the issue now. Expect response by EOD 16/Aug. ===== State: Engineering by:mpaul at 8/2/2012 3:21:01 AM ===== Dev team will look into this issue and try to identify root cause of problem. Since team is working towards next release commitments, we will get back with updates by EOD tuesday (7/Aug). ===== State: Engineering by:ramearum at 7/31/2012 1:53:12 AM ===== We are able to reproduce the issue. Will investigate further and update you with the information as early as possible. ===== State: Dev_Submitted by:gsynnes at 7/30/2012 5:44:33 PM ===== Hello Ramesh, Customer is requesting a Hotfix, please let us know if this is possible. ===== State: Support_Esc by:gsynnes at 7/30/2012 5:43:03 PM ===== ****Description field information .**** This defect is in RSA, RSA 4WS, 8.5, 8.04 and 7.5.5.5 1. Problem description and statement ------------------------------------ RSA:Sequence Dgm.,Message numbers disappear if re-open 2. Customer Environment ----------------------- RSA 8.0.4 will update to 8.5, requesting fix for RSA 8.5. 3. When did this start happening? Did this always happen? What changed? ---------------------------------------------------------------- ------- always happens. 4. Customer Impact, users affected -------------------------------------- 4 users, US Army. 5. What does Support expect from the Development team to be able to close this escalation? ---------------------------------------------------------------- -------------------------- Provide a Hot fix. 6. What does the customer expect? The WHOLE numbers to stay after re-open. 7. Research made and Reproduction steps --------------------------------------- Reproduced the issue in RSA, RSA4WS7.5.5.5, 8.0.4.1 and 8.5 following the steps: In a sequence diagram, if the first message in the diagram comes from the edge of the diagram, the numbers on the diagram disappear. - In Windows Preferences, the numbering option for the sequence diagrams is set to 'Integer (whole) numbers'. The UML Fragment capability is also enabled. To reproduce: (1) Create a new UML model. (2) Create a single class with a single operation. (3) Create a new sequence diagram. (4) Add the class to the diagram to create a lifeline by dragging and dropping the class from the Project Explorer onto the diagram. (5) Create a synchronous message from the edge of the diagram to the lifeline using the single operation of the class. (6) Create a nested synchronous message on the lifeline. (7) Within the nested message, add an Option fragment. (8) Within the Option fragment, add another nested synchronous message. At this point there are three synchronous messages and an Option fragment on one lifeline. The numbering, from top to bottom, are 1, 2, (1, 2), 3, 4. (9) Between the bottom of the Option fragment and the return message labeled 3, add another nested synchronous message. After doing so, the numbers will not show up on the new message. (10) Save and Close the diagram. (11) Open the diagram. All the numbers outside of the Option fragment are now missing. 8. Attachment(s): ----------------- diagram image. 9. Is this known product defect? If so, provide a RATLC number? Not that I know of. 10. Does the customer have a workaround? No 11. Customer details information, technical/field representative information. ---------------------------------------------------------------- ------------ *** Customer contact full name: Keith Squier *** Telephone: 2563276332 *** Email: keith.squier@ngc.com ****Note Entry field information .****
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Lost message number on Sequence diagrams at re-open
Problem conclusion
The reported issue is fixed. The fix involves handling empty stack problem.
Temporary fix
Comments
APAR Information
APAR number
PM71636
Reported component name
RATL SW ARCHITE
Reported component ID
5725A3000
Reported release
803
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-27
Closed date
2012-12-04
Last modified date
2012-12-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 SW ARCHITE
Fixed component ID
5725A3000
Applicable component levels
R803 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYK2S","label":"Rational Software Architect Designer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"803","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYK2S","label":"Rational Software Architect Designer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"803","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 September 2020