PI27696: CANNOT CHANGE SWIFT MESSAGE TYPE TO OUTPUT

Rational Test Virtualization Server Fix Pack 1 (8.7.0.1) for 8.7
Rational Integration Tester Fix Pack 1 (8.7.0.1) for 8.7
Rational Performance Test Server Fix Pack 2 (8.7.0.2) for 8.7
Rational Integration Tester Fix Pack 2 (8.7.0.2) for 8.7
Rational Test Virtualization Server Fix Pack 2 (8.7.0.2) for 8.7
Rational Test Virtualization Server Fix Pack 3 (8.7.0.3) for 8.7
Rational Integration Tester Fix Pack 3 (8.7.0.3) for 8.7
Rational Performance Test Server Fix Pack 1 (8.7.0.1) for 8.7
Rational Integration Tester Fix Pack 4 (8.7.0.4) for 8.7
Rational Test Virtualization Server Fix Pack 4 (8.7.0.4) for 8.7
Rational Performance Test Server Fix Pack 4 (8.7.0.4) for 8.7
Rational Performance Test Server Fix Pack 3 (8.7.0.3) for 8.7

APAR status

• Closed as program error.

Error description

• By default the SWIFT Input message type is used in the message
  editor when applying the SWIFT schema.
  Attempts to change to Output type give a damaged message with
  red crosses and missing Application node.
  
  STEPS TO REPRODUCE:
  
  1. Apply the MT103 message schema to a text message.
  2. Right-click on Application > Type > Application > MT103
  Output
  
  The Input fields remain and are under a blank Message node with
  red crosses on additional added fields.
  
  WORKAROUND:
  
  1. Remove the Application node.
  2. Re-add the Output type Application node.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of Rational Integration Tester working with SWIFT  *
  * messages.                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The SWIFT message type defaults to Input in the message      *
  * editor.  Changing the message type to Output resulted in a   *
  * damaged message.                                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• This issue has been fixed, with the following behavior:
  
  *  If the schema for the new type defines a fixed value for a
  field, that fixed value is used
  *  The name of the root node is taken from the new type
  *  The user has the choice to include optional fields for the
  new type
  

Temporary fix

Comments

APAR Information

• 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 INTEGRA TE

• Fixed component ID

  5725G79IT

Applicable component levels

• R800 PSN

     UP

• R801 PSN

     UP

• R850 PSN

     UP

• R851 PSN

     UP

• R860 PSN

     UP

• R870 PSY

     UP