Release Notes 1.1.4.0
Metadata
This release documentation version 1.0.
| Release | 1.1.4.0 |
|---|---|
| Release date | 2024-05-03 |
| Release type | Full release |
| Future | Main branch release |
| Server version | 1.1.4.0+1.1.4.0-11730aab |
| Log Server version | 1.1.4.0+1.1.4.0-18e68458 |
| HostScreen Server version | 1.1.4.0+1.1.4.0-e52f9c32 |
| Web Terminal Hub version | 1.1.4.0+1.1.4.0-b1ad45e4 |
| Web Terminal Client version | 1.1.4.0+1.1.4.0-139b62da |
| Management Console | 1.1.4.0+1.1.4.0-ff5f4f5d |
| Log Viewer | 1.1.4.0+1.1.4.0-dd17df53 |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| renderer.2b40fffc4614a3bfab13.js | renderer.4a6333d2c56e553c9733.js |
| renderer.4b7269853ded7ff1a8af.js | renderer.6de4dcfc18d8e189ec9e.js |
| renderer.7b60e0ba28d5470bdbc8.js | renderer.8e1c52fae1486d84b902.js |
| renderer.26bde444bdc0b84ba505.js | renderer.26bde444bdc0b84ba505.js.LICENSE.txt |
| renderer.854e846020ff37bd1c2d.js | renderer.854e846020ff37bd1c2d.js.LICENSE.txt |
| renderer.978ba985dba414cac7f7.js | renderer.b6e91dce7ab74396b284.js |
In this Release
New
| ID | Protocols | Description |
|---|---|---|
| HSS.42 | All | FakePrinter testing tool allows for unformatted log files. |
| WTC.86 | All | Configurable border around terminal screen |
Fix
| ID | Protocols | Description |
|---|---|---|
| HSB.8 | All | Server and session recovery from crashed and abandoned shared memory threads. |
| HSB.9 | All | Shared memory allocation could fail when IIS or sessions failed unexpectedly. |
| HSB.10 | All | Shared memory flags could end up in bad state causing high CPU. |
| HSS.45 | 3270 | Updated 3270 Adapter to use new shared memory ownership model. |
| HSS.30 | All | The HostScreen Server Session Manager could fail controlling and reporting on session state. |
| HSS.33 | All | TLS connections failed with valid server certificate. |
| HSS.40 | 5250 | Clear Unit command did not leave the keyboard unlocked. |
| HSS.41 | All | The Management Console incorrectly offered the TNVT connection type. |
| HSS.44 | 5250 | Read Screen operation failed when screen is 27 x 132. |
| WTC.98 | All | Font scaling of larger screens could have resulted in squashed text. |
| WTH.13 | 3270, 5250 | A session could become locked due to unavailability of shared memory objects under extremely rare conditions. |
| HSS.39 | 3270 | IND$FILE upload/download did not work correctly with Windows 1252 encoded files. |
| MC.10 | 3270 | Support new IND$FILE file encoding setting in the Management Console created in fix HSS.39. |
Change Notes
New
HSS.42 - FakePrinter testing tool allows for unformatted log files
The testing tool "FakePrinter" now allows the use of log files in their raw format as produced by the logging server. Perviously, they needed to be opened in an editor and "prettified". This step is no longer needed.
WTC.86 - Configurable border around terminal screen
It is now possible to configure border around the screen in the web terminal client. As not to change pervious default behaviour, this defaults to disabled (zero width border).
The default border settings are found in (or can be inserted into) {install location}\Jubilant\WebTerminal\web\settings\settings.json.
{
"ShowScreenBorder": true,
"ScreenBorderHeight": 10,
"ScreenBorderWidth": 10
}
- ShowScreenBorder (boolean): true means that the ScreenBorderHeight and ScreenBorderWidth are applied, false means that they are not.
- ScreenBorderHeight (integer): The height in pixels that is added to both the top and bottom of the emulator screen if ShowScreenBorder is set to true.
- ScreenBorderWidth (integer): The width in pixels that is added to both the left and right side of the emulator screen if ShowScreenBorder is set to true.
The user facing settings appear in the settings accessed via the terminal tool bar (gear bottom left). On the "General Settings" tab, at towards the bottom, the following settings can be seen:
- "Show Screen Border" toggles enables and disables the border settings (represented by the ShowScreenBorder config file setting above).
- "Top and Bottom (pixels)" sets the number of pixels that are to be added to both the top and bottom of the terminal screen (represented by the ScreenBorderHeight config file setting above).
- "Left and Right (pixels)" sets the number of pixels that are to be added to both the left and right of the terminal screen (represented by the ScreenBorderWidth config file setting above.)
The Reset General Settings button at the bottom of the settings dialog resets the border settings back to the default as specified in the settings.json file. If the settings are not in that file, ShowScreenBorder defaults to false.
Fixes
HSB.8 - Server and session recovery from crashed and abandoned shared memory threads
When a server or session process encounters abandoned mutex, Jubilant takes steps to remedy the issue to allow the server or session to continue functioning.
In previous versions of Jubilant, failure would often manifest itself has high CPU usage in the IIS worker of HostScreen Server processes.
HSB.9 - Shared memory allocation could fail when IIS or sessions failed unexpectedly
Shared memory allocation could fail because of a crashed session, dead server process or unexpectedly lengthy logging events. Jubilant now takes steps to remedy this issue, allowing the server or session to continue functioning.
In previous versions of Jubilant, failure would often manifest itself has high CPU usage in the IIS worker of HostScreen Server processes.
HSB.10 - Shared memory flags could end up in bad state causing high CPU
Shared memory flag control and release could end up invalid, causing server or session processes to crash which could ultimately bring the server down. This fix removes the scenarios where this can happen. HSB.8 and HSB.9 take steps that if does still happen, the server is able to recover.
In previous versions of Jubilant, failure would often manifest itself has high CPU usage in the IIS worker of HostScreen Server processes.
HSS.45 - Updated 3270 Adapter to use new shared memory ownership model
Updated the HostScreen Server 3270 Adapter to use fixed shared memory model. See HSB.8, HSB.9 and HSB.10 for more details.
HSS.30 - The HostScreen Server Session Manager could fail controlling and reporting on session state
The Session Manager in the HostScreen Server could fail to start or report the state of running sessions correctly under high load.
In previous version of Jubilant, failure would often manifest itself as failed attempts to connect a session and the Management Console being unable to list active sessions.
HSS.33 - TLS connections failed with valid server certificate
Telnet over TLS connections could fail if configured to only accept valid server certificates.
In the previous version of Jubilant, failure would often manifest itself with the logged error: Server validation SSL policy errors: RemoteCertificateNameMismatch.
HSS.41 - The Management Console incorrectly offered the TNVT connection type
In the previous version of Jubilant, it was possible to select TNVT as a the connection type for a Host Definition. This is not a valid connection type.
A new version of Jubilant will offer TNVT in the near future.
HSS.44 - Read Screen operation failed when screen is 27 x 132
In previous versions of Jubilant, a 5250 Read Screen operation on a 27 x 132 screen could result in an exception:
"Exception": {
"Message": "Index was outside the bounds of the array.",
"StackTrace": " at Flynet.Jubilant.HostScreen.Server.ScreenBufferAdapter.TN5250ScreenBufferAdapter.HandleReadScreenOperation(ReadScreenOperation operation)"
}
This is resolved in this version of Jubilant.
WTC.98 - Font scaling of larger screens could have resulted in squashed text
In previous versions of Jubilant, it was possible that fonts on screens larger than 24 x 80 could appear squashed.
This fix ensures that fonts are scaled and spaced appropriately for the screen dimensions.
WTH.13 - A session could become locked due to unavailability of shared memory objects under extremely rare conditions
Under very rapid update conditions, or when an update was taking a very long time, there was an extremely small chance that a session could become stuck with no reason reported in logs or sent to the front-end.
This rare locking can now occur in even less situations, with a proper log entry and client messages created if it does.
The client facing message error would be along the lines of:
"Unable to obtain control of session"
"The Web Terminal has been unable to take control of the session. Your session may be lost."
"MergeScreenUpdate has been unable to take control of the ScreenBuffer Mutex."
The logged error would be along the lines of:
"ScreenBuffer Control Failure"
"Unable to gain control of the shared ScreenBuffer."
HSS.39 - IND$FILE upload/download did not work correctly with Windows 1252 encoded files
Previously Jubilant did not upload or download Windows 1250 encoded files using 3270 IND$FILE with ASCII conversion. Previously only UTF-8 encoded files would work.
A new setting has been added to {install location}\Jubilant\HostScreenServer\hostscreen-server.serversettings.json.
{
"HostScreenServer": {
"FileTransfer": {
"IndfileEncodingForAscii": "UTF8"
}
}
}
IndfileEncodingForAscii can either be UTF8 or Windows1252. If the setting is not present, Jubilant will default to the previous behaviour of UTF8.
If end users are transferring Windows 1252 encoded files, the IndfileEncodingForAscii setting must be set to Windows1252. When changing this setting, IIS and the HostScreen Server process must be restarted. Use the JubilantRestartHostScreenServerOnly.ps1 to carry out this restart. This is an destructive action and will drop all connected sessions.
It is possible to alter this setting without requiring a HostScreen Server restart by using the Management Console. Please see the complimentary fix MC.10 for more information.
HSS.40 - Clear Unit command did not leave the keyboard unlocked
In previous versions of Jubilant, the keyboard remained locked after a Clear Unit command was issue by the IBM System i. This is no longer the case, and Jubilant correctly unlocks the keyboard.
In the previous version of Jubilant, failure would often manifest itself with a blank screen or fully updated screen and a locked keyboard.
MC.10 - Support new IND$FILE file encoding setting in the Management Console created in fix HSS.39
The Management Console has been updated to allow the setting of the new file transfer encoding setting created for fix HSS.39.
This allows the alteration of this setting without restarting the HostScreen Server.
The new setting can be found in the Management Console under HostScreen Server -> Global Settings -> File Transfer Settings -> File Encoding for ASCII Transfers.
Installation
Fresh Install
Please see the Jubilant Admin Manual for Fresh Install Instructions.
Upgrade
Note
Please note the specials steps below if upgrading from a 1.0.x build to a 1.1.x or later build.
If upgrading from Jubilant 1.0.x to 1.1.x extra steps must be carried out before and after the install steps below.
Upgrade is carried out using Jubilant scripts.
- Unzip the installer into a folder.
- Close any web browsers.
- Close any Services windows.
- Open PowerShell ISE as Administrator.
- In the PowerShell ISE open the Jubilant PowerShell script: "JubilantUpdate.ps1".
- Run the required script by pressing the green play / run script button on the toolbar.
- The upgrade of Jubilant is complete.
If this is an upgrade from Jubilant 1.0.x to 1.1.x, make sure the after install steps are also completed.
Version Validation
Find out how to validate the installed version.