Fixes are available
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.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
APAR status
Closed as program error.
Error description
Change the data on the field that has CHECK(RB),CHECK(RZ) or CHECK(FE) attribute on 5250 screen and press Enter on the same field, auto fieldexit function works on HATS runtime by default. There is the runtime settings emulateFieldExit and the default value is true. I found that the additional symptoms on O type field and G type field. If input DBCS data with emulateFieldExit=true (default), the string is truncated. If the field length is 10byte,.... and these fields have CHECK(XX) keyword on DDS and fieldExitRequired="true" on redered HTML O type: If input SO AA BB CC DD The string is sent to i/5 as SO AA BB SI ( Two DBCS characters are truncated.) G type: If input AA BB CC DD EE The string is sent to host as AA BB HATS FIELD IS NOT CLEARED PROPERLY WITH EMULATEFIELDEXIT ENABLED ON FIELDS THAT HAVE EXISTING DATA
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: DBCS users that have coded a DDS * * attribute of * * Check(RZ)- Right justify with Zeros, * * Check(RB) - Right justify with Blanks, or * * Check(FER) - FieldExitRequired. * **************************************************************** * PROBLEM DESCRIPTION: When a DBCS user has a 5250 field * * that is coded on the host as a DDS * * field attribute of Check (RB, RZ, or * * FER), and the field has data in it * * already then new data entered and sent * * to the host may be send unwanted data. * **************************************************************** * RECOMMENDATION: * **************************************************************** This problem is a side effect of composite character support (DBCS), some Hiragana characters also are part of composite characters. The length of the field that needed to be cleared was not properly calculated. Therefore, data was being left that should have been cleared.
Problem conclusion
Modified HostScreen.java to correctly calculate the length of the DBCS field, and modified lxgwfunctions.js to check if the character is a composite character or not.
Temporary fix
Comments
APAR Information
APAR number
IC61143
Reported component name
RATL HATS FOR 5
Reported component ID
5724U6800
Reported release
710
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-15
Closed date
2009-05-20
Last modified date
2009-05-20
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 HATS FOR 5
Fixed component ID
5724U6800
Applicable component levels
R710 PSY
UP
R750 PSY
UP
Document Information
Modified date:
20 May 2009