Fixes are available
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
This APAR is for HATS 7.5 and corresponds to the fix put in the HACL code in the Host On-Demand product via APAR IC65074. "Users of the SysReq mode in 5250 sessions encounter a problem when an Operator-Input Error is returned by the host."
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: HATS 5250 clients using SysReq mode. * **************************************************************** * PROBLEM DESCRIPTION: Users of the SysReq mode in 5250 * * sessions encounter a problem when an * * error(an Operator-Input Error XII) is * * thrown by the host. While still in * * sysReq mode, the user tries to key * * in data on fields which are not * * "input-fields" under the SysReq mode, * * since the SysReq mode will have only * * the "SysReq line"(at the bottom the * * session screen) as the input field * * which ideally needs to be used. This * * results in the "Cursor on the * * protected area of the display" error * * message. At this point, the user * * presses an Enter key (HATS sends the * * AID key only to the host) and this * * results in keying in invalid/wrong * * data on the input fields of the host * * application. * **************************************************************** * RECOMMENDATION: * **************************************************************** While the user is in sysReq mode and tries to enter invalid data in an input field, the user is thrown an error saying "Value entered for field is not valid". The user would use the SysReq mode to enter the correct data. When this sysReq mode is being processed, the user might not use the SysReq line to send the data, rather enter into an Error condition by trying to key in data on the original input field(which would be protected in the SysReq mode). So, as the "Cursor in protected area of the display" message is shown, HATS enters an ERROR mode. The main problem addressed by this APAR is the handling of the ERROR mode within the SysReq mode.
Problem conclusion
There are only two valid combinations in SysReq mode, one being an AID key followed by the SysReq key(or SysReq mode) and the other being the ERROR condition while in the SysReq mode. This fix involves clearing the SysReq mode at the right juncture so as to handle the ERROR mode(while still being in the SysReq mode). When these modes are cleared, the FFT(Field Format Table) would be restored back to the original screen and this would enable HATS to send the data along with the AID key to the host and hence not allow the invalid data to be accepted by the host application.
Temporary fix
Comments
APAR Information
APAR number
IC65637
Reported component name
RATL HATS MULTI
Reported component ID
5724U6700
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-18
Closed date
2010-04-15
Last modified date
2010-04-15
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 MULTI
Fixed component ID
5724U6700
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXKAY","label":"IBM Host Access Transformation Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
15 April 2010