Changes in Version 5.0.8Functions extended by this Refresh PackNone. Problems fixed in this Refresh PackSee the HATS support page for a more detailed description of these APARs. IC47955 - Data doesn't change in input field when user modifies numbers. IC49187 - Not all DBCS characters in a DDS window are displayed. IC49386 - Client receives nullpointer exception when playing the connect macro. IC49430 - Object Not Defined error message. The following problems were found internally, so there is no additional information about them on the HATS support page: 32287 - Tabbed folder overlays Field component using Mac Firefox, Mozilla, Safari. 32814 - Aborted Operation error on Internet Explorer. 33019 - Unicode DBCS fields are recognized incorrectly as hidden. Changes in Version 5.0.7New Functions in this Refresh PackNew option to follow transformation order instead of green-screen order if autoAdvance=trueWith this feature you can specify that HATS use auto-advance tabbing that follows the screen transformation order of fields on the screen to include your non-HATS input areas. This feature overrides the previous HATS autoAdvance support if it is enabled. To enable the feature, add to your transformation default.jsp file the following call anywhere after the JavaScript (.js) file declarations and before the closing HATS:Form tag: <script> turnAutoTabOn(); </script> If you add the above call, you must refresh your browser window and refresh the page for the change to become effective. Problems fixed in this Refresh PackSee the HATS support page for a more detailed description of these APARs. IC47196 - Pressing Field Exit after typing N-1 characters in a numeric field of length N doesn't justify input correctly IC47308 - Attempt to invoke 'Window.Close" browser call from a HATS session fails with Object Unknown IC47315 - If autoAdvance is enabled, will not be able to use IME on some DBCS input fields IC47637 - When the parent browser window is closed, the HATS application on the child is also closed IC47640 - HATS sends back fields marked modified even when they're not. Client Access (CA) is using a host application error message. IC47886 - HATS application hangs when unable to detect graphics system. The following problems were found internally, so there is no additional information about them on the HATS support page: 32282 - SelectionList and buttons not working properly with Internet Explorer on Apple Macintosh or with Opera browser 32467 - DBCS: Auto-advance fails in 5250 G-type and J-type fields Changes in Version 5.0.6New Functions in this Refresh PackNew autoEraseFields setting to automatically delete host field dataThe HATS runtime can now optionally detect when you have cleared an input field of all data or changed the data, and automatically clear the field on the host. If there is newer data supplied, that newer data will then be put into the cleared host field. This solves problems some customers encounter if HATS uses space characters to clear data in host fields. For example, without this new feature enabled, HATS will send a space-padded string to clear old data in a host field. If a host supplies an eight-position field with 00345678 and the user types 9999 for the new field value, HATS will actually send a space-padded value "9999 " (9999 plus four space characters) in order to replace the old data (5678). Certain applications and certain host fields will not accept the space characters, and so either the application may refuse the update with an error message or the host might end up with 99995678 in the field instead of just 9999. Enabling this feature causes HATS to automatically clear the field using the [clearfld] host function, and then send 9999 to the field. A similar case occurs when an end-user uses the Delete key to erase a field's contents instead of using the [clearfld] host function. If a field's initial contents is ABC and the end-user uses the Delete key to erase the field, HATS will actually send " " (three space characters) to overwrite the field's contents. Some applications require that the field be cleared instead of set to space characters. Enabling this feature will cause a [clearfld] to automatically be used for this case instead of three space characters. To enable the feature, add the following to the <classSettings> section of the application.hap file: <class name="com.ibm.hats.common.RuntimeSettings"> If there is already a <class> section by this name, just add the <setting> line inside the section. Limitations: Any host field that is rendered as multiple HTML input fields will not be automatically cleared. For example, long host fields that wrap from one line to the next are rendered as multiple HTML input fields, and so will not be automatically cleared before updating. Those fields will continue to use space padding, if needed. This prevents unintentional data loss that would result if [clearfld] were used automatically. New suppressUnchangedData project-level settingThis feature modifies the default behavior of a HATS application to send modified input field data even when the contents of the field are identical to the data supplied by the host. For example, if the host filled a field with "ABC" and the user typed "ABC" into the field, the typed data will be returned to the host. Prior to this change, the typed data would not have been returned to the host. If the previous behavior is required by your application, then you may revert back to it by adding a new project setting in the application.hap file. To enable the the old default behavior, add the following to the application.hap file: <class name="com.ibm.hats.common.RuntimeSettings"> If there is already a <class> section by this name, just add the <setting> line inside the section. Problems fixed in this Refresh PackPlease see the HATS support page for a more detailed description of these APARs. IC46626 - An unexpected exception was received: java.lang.ArrayIndexOutOfBoundsException: 15 >= 15 IC46765 - HATS inserts SOSI pair into incorrect position in J-field IC46779 - Subfile menu displayed multiple times IC46846 - Position is miscalculated for screens containing a DBCS character The following problems were found internally, so there is no additional information about them on the HATS support page. 31972 - Intermittent problems with applet and Firefox 32089 - Java Script Error when allowing positioning in protected field 32166 - Entry into O Type fields not handled correctly 32243 - DBCS characters shifted in DBCS-open wrapping field after submission 32259 - Widget scenario causes JavaScript error 32269 - DBCS: JavaScript error (event.srcElement) when using Mozilla 32270 - Data in DBCS fields sent out twice Changes in Version 5.0.5New Functions in this Refresh PackAlternative to HTML anchor tags for "allow positioning on protected text" feature This feature provides enhancements to help reduce the number of bytes being transported from HATS to client browsers, which improves network utilization and end user response time. Currently, the Field widget has a setting named "Allow positioning on protected text". When this setting is enabled, the Field widget generates HTML anchor <A> tags around each segment of protected text (the number of tags generated changes based on the "alignment" setting). An example of a typical tag that can negatively affect the overall size of a page: <a href="javascript:setCursorPosition(162, 'HATSForm');
ms('[enter]', 'HATSForm')" class="HBLUE null HATSPROTLINK" style="">
Tabbing between input fields is also a problem with the current implementation. Because HTML anchor tags can receive focus, you must tab over these links to navigate between input fields. This is both time consuming and not consistent with a typical terminal emulator. To solve both of these problems, an enhancement has been added to the Field widget. You can choose between using the current protected text positioning mechanism (anchor tags) or the new method. The new method works by adding an "id" attribute to the existing <td> (table cell) tags that are generated by the Field widget. The "id" attribute indicates the 1-based linear screen position of the cell. An example of a typical tag: <td id="p_162" class="HBLUE" colspan="28"> An example of the tag generated when you specify that a specific aid key be sent when a user clicks the text: <td id="p_162" class="HBLUE" colspan="28" action="[enter]"> When running in a portal environment, the generated HTML tag differs slightly from the tag shown above, as follows: <td id="p_162_FORMID" class="HBLUE" colspan="28"> where FORMID is the ID of the enclosing HTML form. In portal, every HATS portlet is given a unique name. This unique name enables the Javascript to know the form on which to set the cursor position. Bidirectional applications use the bdo tag in order for the Field widget to be able to apply directions. Therefore, a bdo tag must be added within the table cell tag (<td>) and the table cell id attribute must also be used inside the bdo tag, as shown below: <td id="p_162" class="HBLUE" colspan="28"> <bdo dir="ltr" id="p_162"> </bdo>user </td> At runtime in the browser, the HATS Javascript is notified when one of these cells is clicked. HATS updates the cursor position internally and then visually indicates the new cursor position to the user. This visual indication can be controlled by the developer via a CSS style. By default, the visual indication is to set the background color of the text to yellow. With this setting enabled, the following is provided:
Usage Notes:
Limitation: To enable this feature, you must enable "Allow positioning on protected text" (a setting of the Field widget, named showLinksForProtectedFields in the source file) as well as set the "renderProtectedTextAsLinks" Field widget setting to "false". There are various ways in which you can enable this new setting:
You must also add the following snippet of CSS to your associated style sheet (a project or transformation's template .jsp file): .HCURSORINDICATOR {
text-decoration: underline;
background-color: yellow;
}
Note: For information about how HATS uses style sheets, visit: http://publib.boulder.ibm.com/infocenter/hatshelp/index.jsp?topic=/com.ibm.hats.doc/doc/ugtmplat.htm Remove empty HTML attribute elements (for example, style="") Prior to this feature, HATS did not check that values were present before rendering attributes with no value. In some cases (depending on the widget and its setting), empty attributes are generated. These empty attributes have no affect on the visual display of the page, nor do they affect the behavior of the page. They can, however, affect the overall size of the page. For example: Sample tag before this change: <td class="HBLUE" style=""> Sample tag after this change: <td class="HBLUE"> Problems fixed in this Refresh PackPlease see the HATS support page for a more detailed description of these APARs. IC45088 - Blank screen coming down from host. This is caused by an unbind followed by a bind in the midst of the flow during logon. IC45634 - Nothing displayed on query screen on iSeries wrkqry sequence. IC46275 - HATS: PF key links do not work if Internet Explorer browser on MAC OS. The following problems were found internally, so there is no additional information about them on the HATS support page. 31881 - DBCS: NullPointerException when creating text input. 32085 - Prevent subsequent clicks leading to BusyPage. Code is now fixed so that modifying lxgwfunctions.js per Technote instructions will block Busy Page, even from multiple mouse clicks. Changes in Version 5.0.4New Functions in this Refresh PackPlease see the HATS support page for a more detailed description of these APARs. New setting for the Function Key component Some host screens have function keys close together, or the function key descriptions have multiple words in them. Either of these situations makes it difficult for the component to recognize each function key in a group. A new setting, searchType, has been added to the function key component to enable correct recognition of function keys for those situations. There are two values for the setting:
You can implement this setting at the component level or the default rendering level. Following are examples of how to implement the new setting for those levels: Component level in the project settings (application.hap):
<class name="com.ibm.hats.transform.components.FunctionKeyComponent">
<setting name="delimiter" value="=| - |-| = |:"/>
<setting name="searchType" value="allDelimitersFirst"/>
<setting name="reqValueAfterDescription" value=" "/>
<setting name="reqValueBeforeLeadingToken" value=" "/>
<setting name="startDelimiter" value="PF#|F#| #=|#"/>
</class>
Default rendering level in the project settings:
<renderingItem associatedScreen=""
description="Transform function keys" enabled="true"
endCol="-1" endRow="-1" startCol="1" startRow="20"
type="com.ibm.hats.transform.components.FunctionKeyComponent"
widget="com.ibm.hats.transform.widgets.ButtonWidget">
<componentSettings>
<setting name="delimiter" value="=| - |-| = |:"/>
<setting name="searchType" value="allDelimitersFirst"/>
<setting name="reqValueAfterDescription" value=" "/>
<setting name="startDelimiter" value="PF#|F#| #=|#"/>
<setting name="reqValueBeforeLeadingToken" value=" "/>
</componentSettings>
<widgetSettings/>
</renderingItem>
Problems fixed in this Refresh PackPlease see the HATS support page for a more detailed description of these APARs. IC43425 - GETCURSORROW() and GETCURSORCOL() do not return correct value for 27x132 screen. IC43799 - DBCS space padding input fields. IC43950 - After applying IC43272, incorrect data entered into input field can't be removed or typed over. IC44112 - HATS does not correctly render dialog pop-up box when it includes text in the border of the box. IC44134 - In J FIELD, SO/SI pair moves to incorrect position after deleting the character in J FIELD, when using SHIFT-JIS encoding. The following problems were found internally, so there is no additional information about them on the HATS support page. 28730 - See New setting for the function key component. 30214f_1 - Dropdown does not auto submit when used with Input component 31179 - The refresh icon on the HATS Administrative Console Managed Connections panel fails when using Netscape or FireFox 31628 - When the subfile uses the Field Component (none) to render the subfile, the Submit button is not displaying properly 31629 - Subfile component in default rendering consumes a region of the screen that is not a part of the subfile. 31648 - Input fields with hints are not recognized in RTL screen. 31653 - Wrong version number displayed in HATS LE Administrative console. 31654 - Subfile component renders a blank screen when "none" is selected for rendering the subfile data. 31656 - Subfile Actions are rendered in Subfile Header. 31659 - The Save As... function of the template editor displays "Missing Permission" error. 31682 - The Save as... panel is not displayed with the Mozilla browser. 31706 - Entering data into a 5250 SignedNumericField on the browser and pressing the Enter key displays "Enter key not allowed" error. 31713 - Input fields corrupted when running a bidirectional application on a server. 31716 - Clicking "Must be specified color" in subfile actions panel checks box in subfile header instead. 31724 - DBCS characters are truncated in command line when "showUnprotectedSISOSpace=false." 31729 - In HATS LE Administrative Console, clicking a session on the Manage connections page displays the wrong session information. 31735 - When saving application.hap using the Mozilla 1.7.2 browser, all host names change to localhost. 31737 - In DBCS applications, foreground color attributes are not rendered in the subfile widget. Changes in Version 5.0.3New Functions in this Refresh PackExtra named style (CSS Class) to enable style sheet color mapping of reverse video fields A new feature available in HATS V5.0.1 enables reverse video to be rendered on a Web page as displayed on host screens. HATS formerly only supported an inline style for reverse video fields which allowed displaying a common background (gray by default) for text in these fields. To enable reverse video support in HATS, you must change some of the settings of the field widget by selecting (your HATS project) -> Project Settings -> Rendering Tab -> Widgets -> Field. On the field widget settings:
For example, suppose a host screen has a field with a black background, and red text. When the reverse video attribute is turned on for this field, the host terminal displays black text with a red background. Previous versions of HATS could not render this combination in its HTML display of the host screen. To enable reverse video, HATS generates an additional named style (CSS class) that you can use. Following are examples of text rendered by HATS: Before enabling reverse video:
<input name="in_1989_9" maxLength="9" class="HLRED" onChange=""
type="text" onClick="" onFocus="" value=" CURRENT" size="9">
After enabling reverse video:
<input name="in_1989_9" maxLength="9" class="HLRED RHLRED" onChange=""
type="text" onClick="" onFocus="" value=" CURRENT" size="9">
Notice the addition of the second named style (CSS Class), RHLRED. When reverse video is enabled, an additional named style is appended to the text rendered by HATS, for fields of any color. The new named style will start with an R followed by the current color mapping (RHBLUE, RHWHITE, and so on). The named style will contain the new style tags that give the desired display. Following are example style tags that could be used for the new named styles associated with reverse video.
.RHBLANK {
color: black;
background-color: #00ff00;
}
.RHBLUE {
color: black;
background-color: #3c9dff;
}
.RHGREEN {
color: black;
background-color: #00ff00;
}
.RHCYAN {
color: black;
background-color: #00ffff;
}
.RHRED {
color: black;
background-color: red;
}
.RHMAGENTA {
color: black;
background-color: #ff00ff;
}
.RHBROWN {
color: black;
background-color: yellow;
}
.RHWHITE {
color: black;
background-color: #eeeeee;
}
.RHGRAY {
color: black;
background-color: #a0a0a4;
}
.RHLBLUE {
color: black;
background-color: #4040c0;
}
.RHLGREEN {
color: black;
background-color: #40c040;
}
.RHLCYAN {
color: black;
background-color: #40c0c0;
}
.RHLRED {
color: black;
background-color: #ff4040;
}
.RHLMAGENTA {
color: black;
background-color: #c040ff;
}
.RHLYELLOW {
color: black;
background-color: #c0c000;
}
.RHHWHITE {
color: black;
background-color: white;
}
These reverse video style tags match some of the color styles defined in the blacktheme.css style sheet. The styles can be added to your project by:
New Fast5250 minimum delay setting in the HATS connection file for APAR IC43452 The Fast5250 screen-settling algorithm (default algorithm for 5250) had no minimum delay setting. In some cases, the Fast5250 algorithm completed screen-settling before all of the related events are processed at the Telnet client. 5250 screens may settle too quickly, and text from the transient host screens might not be included in a transformation. This can happen especially when the screen is responding to a host application error with a locked-keyboard condition. A new minimum delay setting, fast5250.minimumWait, can now be added to the HATS connection settings file (.hco). To enable this function, edit the source of the connection settings file in the HATS Studio. Locate the com.ibm.hats.common.NextScreenSettings class in the <classSettings> tag. Add the following setting:
<setting name="fast5250.minimumWait" value="0"/>
For the value attribute, specify the minimum time, in milliseconds,
HATS should wait during screen settling when using the Fast5250 algorithm.
The initial default value is 0 milliseconds, which signifies that there is
no minimum wait time.
The Fast5250 algorithm is not affected.
Increasing this value to a small minimum wait time enables more dependable
screen settling.
New setting for the field widget for defect 30600 HATS Version 5.0.3 introduced a new setting, verticalSegmentAlignment, for the field widget to better handle complex host screens. When you add
<setting name="verticalSegmentAlignment" value="true"/>
as a setting for the field widget in your application.hap file, multiple
fields are aligned word-by-word in the transformation.
A nowrap flag is automatically added to the HTML output when
verticalSegmentAlignment is defined.
A new nowrap setting can now be added to the application.hap file for the field widget to turn off the automatic addition of the nowrap flag to the HTML output when verticalSegmentAlignment is defined. To enable this function, edit the source of the application.hap file in the HATS Studio. Locate the class name="com.ibm.hats.transform.widgets.FieldWidget" class in the <classSettings> tag. Add the following setting:
<setting name="nowrap" value="false"/>
This setting should only be added if the verticalSegmentAlignment setting
is also specified for the field widget, and you continue to have alignment
problems.
The value of nowrap should always be "false".
Setting the value to "true" could cause undesirable results.
Problems fixed in this Refresh PackPlease see the HATS support page for a more detailed description of these APARs. IC42567 - Screen reverse not working in BiDi 5.0.2 environment. IC42686 - Symbols render incorrectly after applying CSD3. IC42725 - Partial screen rendered with FAST5250 enabled. IC42767 - Numbers are left justified on subfile screen. IC42967 - Input of KANA(SBCS-KATAKANA) into W-FIELD(KANA) disappear. IC42970 - DBCS keyboard input into DBCS-only fields of = - period and other characters & % $ are OK. IC43249 - Graph widget not rendering negative numbers correctly. IC43335 - S-JIS character EBCDIC 0X43A1 not being correctly displayed. IC43350 - Not all input fields from multiple drop-down boxes are updated to host. IC43409 - Drop-down menus not working. IC43431 - Resume application from View Print Job prompts for LU. IC43452 - Extended help pop up from host screen not rendered. See New Fast5250 minimum delay setting in the HATS connection file for APAR IC43452 for more information. IC43481 - 3270 numeric only field being padded with blanks. SE17083 - Error cvc-elt.1 when editing application settings. The following problems were found internally, so there is no additional information about them on the HATS support page. 28355 - DBCS: Cursor position in browser status didn't jump two columns. 29787 - Highlighted row not rendering to end of subfile. 30122 - SelectionList: String before leading token not working. 30214 - Dropdown does not auto submit when used with input component. 30232 - Unexpected data in preview window when codepage=1399. 30236 - The header and data isn't aligned of AlgecoM. 30305 - Subfile recognition with field table; second record of subfile not rendered. 30311 - BIDI text replaced in field widget is clipped. 30385 - The visual table component is recognized as blank. 30455 - Show cursor position in status window enabled, but status window is not displayed in transformation. 30469 - LE runtime.properties is missing .COMPONENT and .WIDGET parms. 30600 - Add "nowrap" to field widget for word-by-word alignment. See New setting for the field widget for defect 30600 for more information. 30691 - <BR> tag shown in widget preview for subfile. 30781 - Select Item popup only updating first input field on host using the Konqueror browser. 30929 - Subfile: subfileActionFieldStartCol function not working. 30984 - Mozilla sends unchanged input fields to the server. Mozilla sends more fields to the server than were actually modified. This may cause some problems for legacy applications, such as TSO. This fix only allows modified fields to be sent to the server. 31165 - Blank pages displayed for HATS Administration. Changes in Version 5.0.2New Functions in this Refresh PackAdditional options for subfile recognition and rendering In previous versions and releases of HATS, subfiles have been recognized using visual hints. With this Refresh Pack, you have the option of recognizing the table by visual hint (VisualTable) or by field information (FieldTable). In addition, you have the option to not render a subfile in a table at all, but to render the drop-down for detected actions and render each row line by line. To use any of these options, you must edit the project settings file (application.hap) or a transformation. To edit the application.hap file, click the Advanced link from the HATS Administration console, and then select Click here to edit the XML file representing the settings for this application. Locate the com.ibm.hats.transform.components.SubfileComponent class in the file for recognizing the subfile component, and specify one of the settings for the class, as follows:
There are various ways in which you can set these settings; at the component level, the default rendering level, and at the transformation level. Following are examples of how to set the subfile to render each row line by line: Component level in the project settings (application.hap):
<class name="com.ibm.hats.transform.components.SubfileComponent">
<setting name="tableComponentClassName" value="none"/>
</class>
Default rendering level in the project settings:
<renderingItem associatedScreen="WorkWithActiveJobs"
description="Transform subfiles" enabled="true"
endCol="-1" endRow="-1" startCol="1" startRow="1"
type="com.ibm.hats.transform.components.SubfileComponent"
widget="com.ibm.hats.transform.widgets.SubfileWidget">
<componentSettings>
<setting name="tableComponentClassName" value="none"/>
</componentSettings>
<widgetSettings/>
</renderingItem>
Transformation level:
<HATS:Component type="com.ibm.hats.transform.components.SubfileComponent"
widget="com.ibm.hats.transform.widgets.SubfileWidget"
row="6" col="1" erow="19" ecol="80"
componentSettings=
"tableComponentClassName:com.ibm.hats.transform.components.FieldTableComponent"
widgetSettings="" textReplacement="" />
When row by row rendering is specified, you can specify that each subfile "row" should be visually separated with different colors on odd and even rows. To specify this, use the following settings in the com.ibm.hats.transform.components.SubfileComponent class in the source of the project settings file (application.hap):
<class name="com.ibm.hats.transform.components.SubfileComponent">
<setting name="subfileFixedNumberOfRows" value="true"/>
<setting name="subfileNumberOfRowsPerRecord" value="1"/>
<setting name="subfileDetectActionInputFieldPos" value="false"/>
</class>
Following are the descriptions of the settings:
In previous versions and releases of HATS, the input fields in subfile records are sometimes incorrectly recognized as action fields if the input field length is less than three, and rendered as drop-down lists. To render the text input fields correctly, you can now specify the action input field start column and action input field length. To edit the application.hap file, click the Advanced link from the HATS Administration console, and then select Click here to edit the XML file representing the settings for this application. Locate the com.ibm.hats.transform.components.SubfileComponent class for recognizing the subfile component, add the following settings, and modify their values:
<class name="com.ibm.hats.transform.components.SubfileComponent">
<setting name="subfileOverrideActionFieldStartCol" value="false"/>
<setting name="subfileActionFieldStartCol value="1"/>
<setting name="subfileOverrideActionFieldLength" value="false"/>
<setting name=subfileActionFieldLength" value="1"/>
</class>
Following are the descriptions of the settings:
The subfile widget now supports foreground colors and extended attributes detected in the subfile. Supporting foreground colors and extended attributes requires additional settings in the project settings file (application.hap) or a transformation. To edit the application.hap file, click the Advanced link from the HATS Administration console, and then select Click here to edit the XML file representing the settings for this application. Locate the com.ibm.hats.transform.components.SubfileWidget class for transforming the subfile widget, add the following settings, and modify their values:
<class name="com.ibm.hats.transform.widgets.SubfileWidget">
<setting name="preserveColors" value="true"/>
<setting name="mapExtendedAttributes" value="true"/>
<setting name="blinkStyle" value=" "/>
<setting name="reverseVideoStyle" value=" "/>
<setting name="underlineStyle" value=" "/>
<setting name="columnSeparatorStyle" value=" "/>
</class>
For consistency, you might want to set these values to match the same settings
for the field widget.
For the reverseVideoStyle setting, the default is blank, but you can create a cascading style sheet (CSS) class to control the appearance of the background colors. You can also create cascading style sheet classes to control the appearance of the extended attributes. Style sheets control elements of output such as font color, size, and background color. Cascading stylesheet (CSS) is a simple style language that you can use to attach style to HTML elements. HATS provides stylesheets to modify color schemes and font size. The stylesheets that HATS provides are located in the Web Content/Common/Stylesheets node of the HATS Project View tab. For more information on cascading style sheets, go to http://www.w3.org/Style/CSS. New setting for the selection list component for APAR IC42366 One of the functions of the selection list component is to group related list items together when used in default rendering. For two list items to be grouped together, the target input field for the value of one of the list items is the same for both list items. The two list items must not have any other text between them. HATS was not rendering some text following list items when default rendering was used with the selection list component. Text is lost when a long list item is grouped with a short list item that contains text or input fields immediately following them on the same line. A new setting, groupIndividually, has been added to the selection list component to group list items individually, preventing text immediately following a list item from being lost. Note: This setting will cause undesirable behavior if it is used with the drop-down (selection) or radio button (selection) widgets, because they require groups of one or more list items to render properly. When this setting is enabled, it is recommended that you use a widget that is not concerned with grouping. The button and link widgets are both examples of widgets not concerned with grouping. To enable this function, edit the source of the project settings file (application.hap) in the HATS Studio. Locate either the <renderingItem> tag defining the default rendering of the selection list or the <class name="com.ibm.hats.transform.components.SelectionListComponent"> tag for recognizing the selection list. Add the following setting:
<setting name="groupIndividually" value="true"/>
New setting for the field widget for APAR IC41065 HATS was not rendering some complex host screens correctly when default rendering was used, resulting in the misalignment of input fields and text. A complex screen is one that contains multiple input fields at varying column positions across the screen, or contains fields of static text that are expected to align above or below a row of associated input fields. Default rendering uses an HTML table to align a Web page. The number of columns in the table is equal to the number of columns on the host screen. Normally, each field on the host screen is rendered in its own table data (<td>) tag, ensuring that every field starts at the correct horizontal position. However, misalignment can occur on screens that contain input fields at multiple column positions, even at differing vertical row positions, because input fields take up more horizontal space than normal text. A new setting, verticalSegmentAlignment, has been added to the field widget to better handle complex host screens. Instead of using a single <td> tag for a field of static text that is not in an input field, multiple <td> tags are used. Each word segment is now wrapped in its own <td> tag. A word segment is defined as a group of sequential letters followed by any trailing whitespace. Multiple <td> tags ensure that every word on the host screen rendered by the field widget begins at the correct horizontal position in the HTML table generated by default rendering. To enable this function, edit the source of the project settings file (application.hap) in the HATS Studio, locate the (<class name="com.ibm.hats.transform.widgets.FieldWidget"> tag, and add the following setting:
<setting name="verticalSegmentAlignment" value="true"/>
Problems fixed in this Refresh PackPlease see the HATS support page for a more detailed description of these APARs. IC41065 - Menu has Arabic and English listings and the menu items on the right do not line up correctly. See New setting for the field widget for APAR IC41065 for more information. IC41371 - If there is an underscore in data entry field, HATS will not accept data being entered. IC41471 - No error is detected when a SBCS is entered into a DBCS only field. IC41550 - PF15 Key displays PF51 on the status line in browser. IC41577 - Pressing "Enter" multiple times causes a JavaScript error. IC41696 - Subfile header not recognized by color. IC41724 - Enter key not permitting exit from 5250 screen after error occurs. IC41777 - Last AID key in row not recognized. IC41990 - Fields with hints are incorrectly rendered when used in default rendering rule. IC41996 - DBCS data can be entered into an A type field and no error is displayed. IC42167 - DBCS characters adjacent to host URL component not rendered correctly to link widget. IC42227 - Field minus/field plus keys not working properly. IC42366 - Selection list rendering incorrect when there are input fields in the list items. See New setting for the selection list component for APAR IC42366 for more information. IC42372 - Input data length is over limit of host definition and host rejects it. The following problems were found internally, so there is no additional information about them on the HATS support page. 29285 - DBCS would display twice on subfiles after pressing the Enter key. 29373 - The options should not be shown in the header of a subfile. 28392 - Intermittently, the application server won't stop after running a HATS application. 29543 - The button widget is not working in a HATS project using the 424 Hebrew codepage. 29755 - Subfile rendering doesn't consume the first column in host screen. Changes in Version 5.0.1New Functions in this Refresh PackOption added to keep or remove spaces for SI/SO characters in unprotected fields on DBCS host systems This new function only applies to Double Byte Character Set (DBCS) host systems. These systems use Shift In and Shift Out (SI/SO) characters to switch from DBCS characters to Single Byte Character Set (SBCS) characters and vice-versa. HATS currently converts a SI/SO character into a single space character in both protected and unprotected fields. This is working fine in protected fields. However, in some cases, inserting the space character in an unprotected field might cause some errors when the field is sent to the host application. A new setting, showUnprotectedSISOSpace, has been added to enable you to determine whether the space character is added to unprotected fields. This setting affects the unprotected fields in the Field, Subfile, Table, and TextInput widgets. To use this new setting, edit the project settings file (application.hap). Click the Advanced link from the HATS Administration console, and then select Click here to edit the XML file representing the settings for this application. Add the following to your application.hap file as a separate class between the <classSettings> and </classSettings> tags:
<class name="com.ibm.hats.common.DBCSSettings">
<setting name="showUnprotectedSISOSpace" value="true"/>
</class>
If the value of the showUnprotectedSISOSpace setting is set to true, which is the default, the spaces converted from SI/SO characters in unprotected fields are displayed. If the value of the showUnprotectedSISOSpace setting is set to false, the spaces converted from SI/SO characters in unprotected fields are removed. For example, suppose there is a string of mixed SBCS and DBCS characters, xxx[SO]DDD[SI]xxx in an unprotected field, where x stands for SBCS characters, [SO] for ShiftOut, [SI] for ShiftIn, and D for DBCS characters. To display the SI/SO characters as spaces, set the showUnprotectedSISOSpace setting to true. The original string xxx[SO]DDD[SI]xxx is converted to xxx[sp]DDD[sp]xxx, where [sp] stands for a single space. To remove the spaces for the SI/SO characters, set the showUnprotectedSISOSpace setting to false. The original string xxx[SO]DDD[SI]xxx becomes xxxDDDxxx. The space characters between the SBCS characters and DBCS characters for SI/SO characters are not displayed. Specifying the location of log, trace, and license tracking output files HATS V5 uses the default value of HATS.ear\logs for the trace and log output directory, where HATS.ear represents the path to which the HATS5LE.ear file was deployed. Now, you can specify the directory to which you want the output files written. You can add an additional optional keyword, traceLogDirectory, to the runtime.properties file. This enables you to specify a particular directory for the output files. To edit the runtime.properties file on WAS V5.0 Base edition, go to /QIBM/UserData/WebAS5/Base/instance_name/installedApps/cellname/application_name.ear/runtime.propertiesand edit the file with your favorite text editor. For example, on WAS 5.0 Base edition: traceLogDirectory= /QIBM/UserData/WebAS5/Base/instance_name/installedApps/cellname/application_name.ear/logs Notes:
New component for use with default rendering The new Dialog component is a special component used to aid default rendering in recognizing modal frames (popups) on the host screen. To use the new component, you must add it to the default rendering section of the project settings file (application.hap), and set the enabled attribute to true. To edit the application.hap file, click the Advanced link from the HATS Administration console, and then select Click here to edit the XML file representing the settings for this application. You can enter the new default rendering item into the source file.
<defaultRendering>
<renderingSet name="main"/>
<renderingItem associatedScreen=""
description="%NLS:TRANSFORM_DIALOGS%" enabled="true"
endCol="-1" endRow="-1" startCol="1" startRow="1"
type="com.ibm.hats.transform.components.DialogComponent"
widget="com.ibm.hats.transform.widgets.DialogWidget">
<componentSettings/>
<widgetSettings/>
</renderingItem>
Problems Fixed in this Refresh PackPlease see the HATS support page for a more detailed description of these APARs. IC39779 - Selecting one input field when using the input field component causes two input fields to be rendered. IC40248 - Successful attempts at using drop down lists corrupts data being sent to host. IC40364 - HATS running on WAS 5.0 express gets SRVE0026E servlet error. IC40369 - In BIDI:NETPASS, host screen PF key descriptions are before PF key delimiters, which causes the delimiters not to be recognized. IC40420 - FieldExit key does not clear or pad field before the jump to the next input field. IC40479 - Hidden field is displayd by default transformation when it contains text describing a function key. IC40653 - Can't map a key to IC40654 - HATS doesn't recognize CLEAR and ENTER keys as AID keys
IC40692 - DBCS spaces may be truncated in subfile character rendering.
IC40819 - Subfile recognition incorrect when hidden fields are in
the subfile.
IC40821 - SBCS Katakana with IME input breaks auto advance
IC40842 - Subfile not rendering function keys properly
IC40937 - New parameter in connection settings to allow modification
to wait time for OIA
IC40971 - When using visual table, a 6-character input field is being
split into 1-character and 5-character input fields.
IC41226 - Internet Explorer script error occurs with auto-advance
set to true and one character input field.
The following problems were found internally, so there is
no additional information about them on the HATS support page. 28664 - When migrating the transformations of a HATS V4 application
that have Option List widgets with certain settings, an unnecessary Submit
button is added to the transformation.
28705 - When a form is submitted from a bidirectional LTR or RTL Web
page, brackets ([]) are displayed reversed (][).
28722 - In a 5250 session, autopush is off by default.
It should be on.
28923 - The Dialog component is consuming lot of CPU.
The algorithm has been changed to correct this situation.
29067 - In the transformation settings for Option Lists,
if you set the number of columns per row greater than 1, they are not
rendering in the browser.
29144 - The HATS V5 Input component has a setting to extract
a caption for an input field, by searching for text to the left of the input
field.
The algorithm searches to the left until it encounters the start of the row
(column 1) or until it encounters another input field.
If there is a gap between protected fields of the caption, the gaps are
ignored.
No space (or set of spaces) is added to compensate for the gap.
The resulting caption will not contain the appropriate number of spaces.
29159 - Summary JSP: Improper Window/Banner Title shown
29259 - Application does not become active when you click Finish button
29275 - Bidi options for default rendering in LE
29288 - Bidi options for disable password field shape in LE
This service update is packaged in the form of a .zip file,
hatslerefreshpack.zip.
Copy this file to a temporary directory on the iSeries system, from which the
user can execute shell script commands on the iSeries QShell.
Exploding the hatslerefreshpack.zip file
creates a QShell script and a hatsleservice.zip file of the updated code.
Note: The user who runs this complete process must have QSECOFR or equivalent
authority.
It is highly recommended that you back up your existing configuration by
exporting the HATS LE project as a .zip file from the HATS LE Admininistrative
Console:
To install this service update, you must first stop your
HATS Limited Edition application:
After stopping your HATS Limited Edition application, following these
instructions:
The command searches /QIBM/UserData/ for HATS LE install directories,
which exist under WAS installedApps directories,
to find HATS LE installations as candidates for maintenance.
The script prompts the user to select whether to apply maintenance to each of the
ear directories of this type that it finds.
Here is the syntax for the command:
This service document will appear in the list of documents in the
Help section of the Administrative Console.
For technical assistance or questions, please call the IBM Support Center
for your Country.
For example in the USA call: 1-800-426-7378 License to the contained APAR fixes is conditioned upon the recipient
holding a license to the prerequisite product.
The license terms and conditions of the APAR fixes are the same as those
for the prerequisite product.
Please see the product license for specifics. Host Access Transformation Services V5.0 Limited Edition
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc.
in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both. Other company, product and service names may be trademarks or service
marks of others.
|