IC59163: HATS-IME,ELIMINATEMAXLENGTHINIDEOGRAPHICFIELDS, & AUTOADVANCE ON WITH DATA INPUT EXCEEDING MAXLEN THEN DATA IS WRITTEN NEXT FIELD

Rational Host Access Transformation Services, Version 7.5.0.1
Rational Host Access Transformation Services, Version 7.1.0.4
Rational Host Access Transformation Services, Version 7.1.0.5
Rational Host Access Transformation Services, Version 7.1.0.6
Rational Host Access Transformation Services, Version 7.1.0.3
Rational Host Access Transformation Services, Version 7.5.0.2
Rational Host Access Transformation Services, Version 7.5.1.1
Rational Host Access Transformation Services, Version 7.5.1.2
Rational Host Access Transformation Services, version 7.5.1.3
Rational Host Access Transformation Services Fix Pack 4 (7.5.1.4) for 7.5.1
Rational Host Access Transformation Services Fix Pack 5 (7.5.1.5) for 7.5.1
Rational Host Access Transformation Services Fix Pack 6 (7.5.1.6) for 7.5.1
Rational Host Access Transformation Services, Version 7.1.0.2

APAR status

• Closed as program error.

Error description

• If using IME, eliminateMaxlengthInIdeographicFields, and
  Autoadvance, when data is input that exceeds the max length
  and submitted, the excess data is written into the next field,
  and the cursor is put at the end of that next field.
  For example,
  Turn on IME and input the exceeding data and press Enter
         <AAAAAA>AAA| <BBBBBB>
  Then exceeding data overwrites a part of the next field
  and cursor moves to the end of field.
         <AAAAAA>     <AAABBB|>
  If input more data rapidly, cursor is forwarded to third
  field.
         <AAAAAA>     <AAABBB>   <CC|  >
  They expects that the cursor moves to end of the modified
  data
          <AAAAAA>     <AAA|BBB>
  

Local fix

• none available
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DBCS users that utilize IME,             *
  *                 eliminateMaxlengthInIdeographicFields, and   *
  *                 Autoadvance features.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When data is input that exceeds the     *
  *                      max length and submitted, then the      *
  *                      excess data is written into the next    *
  *                      field, and the cursor is put at the     *
  *                      end of the excess data in next field.   *
  *                      The expected result is for the cursor   *
  *                      to be at the end of the field.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem is caused by JavaScript behavior.
  

Problem conclusion

• Code was added to count the length of the exceeded data.  When
  the cursor moves to the next field the cursor position will be
  reset.
  

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:

Modules/Macros

• DBCS
  

Fix information

• Fixed component name

  RATL HATS MULTI

• Fixed component ID

  5724U6700

Applicable component levels

• R710 PSY

     UP