Fixes are available
Rational Host Access Transformation Services Fix Pack 1 (220.127.116.11) for 8.5
Rational Host Access Transformation Services Fix Pack 2 (18.104.22.168) for 8.5
Rational Host Access Transformation Services Fix Pack 3 (22.214.171.124) for 8.5
Rational Host Access Transformation Services Fix Pack 4 (126.96.36.199) for 8.0
Rational Host Access Transformation Services Fix Pack 4 (188.8.131.52) for 8.5
Closed as program error.
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.
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.
In HATSV5 global rule search process, add exceeded buffer length handling for DBCS session to solve this problem.
Reported component name
RATL HATS FOR 5
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
RATL HATS FOR 5
Fixed component ID
Applicable component levels