IC86688: DBCS ISSUE: GLOBAL RULES WHEN MIGRATING FROM HATS V5 TO V8.5, EXCEEDED CHAR ARRAY LENGTH ARE INCORRECTLY HANDLED.

Rational Host Access Transformation Services Fix Pack 1 (8.5.0.1) for 8.5
Rational Host Access Transformation Services Fix Pack 2 (8.5.0.2) for 8.5
Rational Host Access Transformation Services Fix Pack 3 (8.5.0.3) for 8.5

APAR status

• Closed as program error.

Error description

• When checking the program settings file (application.hap)
  <setting name="enforceImmediacy" value="true" is added to each
  global rule. However, when there is this setup, only the time of
  "A protected field containing:" being a SBCS character string
  works correctly. It does not work correctly at the time of a
  DBCS character string. If <setting name="enforceImmediacy"
  value="true"/> is removed from a program settings or
  "enforceImmediacy" is "false", it will work correctly. Basically
  there are specific differences between SBCS and DBCS.
  User successfully completed migration of their project from HATS
  v5.0 to HATS 8.5. When looking into User's converted project,
  the keyword of <setting name="enforceImmediacy" value="true"/>
  is automatically added to the program setting file.
  (application.hap) So, User checked the behavior of
  "enforceImmediacy" with value set to "true". If User sets the
  SBCS keyword to "A protected field containing:" field, the
  global rule worked correctly and the matched part in the display
  file was hi-lighted. But, if User sets the DBCS keyword to "A
  protected field containing:"field, the global rule does not work
  and the "Next" button is grayed out. User believes the behavior
  of DBCS keywords should
  work same as the behevior of SBCS keywords. User believes that
  the value of "enforceImmediacy should work without making it
  "false" regardless on whether it refers the SBCS keywords or
  DBCS keywords.
  

Local fix

Problem summary

• If enforceImmediacy setting is true, HATS will use HATS V5 way
  to perform global rule search process, but some DBCS logic of
  common method such as retrieve screen text function was changed
  after HATSV5, the retrieved screen buffer has exceeded length
  and need be handled in HATSV5 global rule search process.
  

Problem conclusion

• In HATSV5 global rule search process, add exceeded buffer
  length handling for DBCS session to solve this problem.
  

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

• DMH0731
  hsrendr
  

Fix information

• Fixed component name

  RATL HATS FOR 5

• Fixed component ID

  5724U6800

Applicable component levels

• R850 PSY

     UP