Fixes are available
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
Editing a macro in a HATS V7.5 project, when the macro is saved, code similar to the following is inserted automatically by HATS into the top section of the macro: <extract handler="default.jsp" index="0" indexed="false" name="" overwrite="true" save="false" separator="" showHandler="true" variableName=""/> which causes an error when trying to generate an Integration Object from the macro. A popup message with 'HATS Toolkit' in the title bar and a message of "An error occured while creating the IO. The prompt has an invalid name. The prompt name must sta rt with a lowercase letter and be a valid Java identifier."is displayed. Removing the prompt handlers with blank names that were inserted automatically resolves the problem and lets the IO be built.
Local fix
Remove prompt handlers with blank names that were automatically inserted.
Problem summary
**************************************************************** * USERS AFFECTED: HATS Developers using the Visual Macro * * Editor (VME). * **************************************************************** * PROBLEM DESCRIPTION: When trying to generate an Integration * * Object from a macro, a popup message * * with 'HATS Toolkit' in * * the title bar and a message of: * * "An error occured while creating * * the IO. The prompt has an invalid * * name. The prompt name must start * * with a lowercase letter and be a * * valid Java identifier." * * is displayed. * **************************************************************** * RECOMMENDATION: * **************************************************************** HATS automatically inserts prompt/extract handlers with blank names when an edited macro is saved. The name attribute of the macro prompt/extract handler tag is not set. This problem only occurs when there are prompt and extract actions in a macro that do not have corresponding HATS handler tags. Because these actions did not have HATS handler tags, HATS automatically creates them. HATS used a method that builds a default handler tag. This default handler tag does not include the name.
Problem conclusion
To fix this problem, the VME now sets the handler name after creating the default handler tag.
Temporary fix
Comments
APAR Information
APAR number
IC62366
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
2009-08-04
Closed date
2009-10-16
Last modified date
2009-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
HATSSTUD
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:
04 November 2009