Table of Contents

Release Notes 1.1.4.2

Metadata

This release documentation version 1.0.

Release 1.1.4.2
Release date 2024-06-13
Release type Full release
Future Main branch release
Server version 1.1.4.2+1.1.4.2-11730aa
Log Server version 1.1.4.2+1.1.4.2-18e6845
HostScreen Server version 1.1.4.2+1.1.4.2-0b4d9a2
Web Terminal Hub version 1.1.4.2+1.1.4.2-c4c347e
Web Terminal Client version 1.1.4.2+1.1.4.2-3030dc9
Management Console 1.1.4.2+1.1.4.2-ff5f4f5
Log Viewer 1.1.4.2+1.1.4.2-dd17df5

.NET Platform

No .NET Platform upgrade available from Microsoft since previous release of Jubilant (1.1.4.1).

.NET Release 8.0.5
.NET Runtime 8.0.5
ASP.NET Core Runtime 8.0.5
Notable changes Link

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.854e846020ff37bd1c2d.js renderer.854e846020ff37bd1c2d.js.LICENSE.txt
renderer.978ba985dba414cac7f7.js renderer.a84a784903972c2c005e.js
renderer.a84a784903972c2c005e.js.LICENSE.txt renderer.b6e91dce7ab74396b284.js

Upgrade Recommendations

This upgrade is recommended for security updates. Also, recommended for IBM 5250 users.

Security Notes

This upgrade is recommended for security reasons.

.NET Security

.NET 8.0.5 is used this release of Jubilant that includes security updates. Maximum severity: Important. Please see these notable changes.

If the current installed build of Jubilant uses an older version of .NET, this update is recommended.

Node Packages Security

An upgrade to Node Package react-scripts (web development) includes security updates. Maximum severity: High. See WTC.101.

High Importance Fix Notes

This upgrade is recommended for IBM 5250 users.

In rare cases, optimisation applied to the reading of the in-memory screen model could have resulted in incorrect field attributes. The optimisation has been updated to avoid such scenarios from occurring.

Please see HSB!15.

In this Release

New

ID Protocols Description
WTH!25 3270, 5250 Improved trace logging of in-memory reads and writes.
HSS!48 5250 Groups of 5250 host updates are consolidated into one user-facing update.

Fix

ID Protocols Description
WTC!167 5250 Fields marked as display and bypass are no longer editable.
WTC!177 3270, 5250 Allow the typing of special characters using the AltGr key.
HSB!15 5250 In-memory screen model optimisation can no longer result in incorrect field attributes.

Security

ID Protocols Description
WTC.101 All Update to node packages to remove high vulnerabilities.
.Net 8.0.5 All See .Net Security Notes.

Change Notes

New

WTH!25 - Improved trace logging of in-memory reads and writes

To help with diagnostics, trace level logs now contain information regarding the reading and writing of the in-memory screen model (ScreenBuffer).

These new entries have one of the following:

  1. Event ID 9140, process WebTerminal Hub, title Terminal Session System Control with a source ending with ScreenSyncObserver.
  2. Event ID 8310, title ScreenBuffer IBM 3270 Screen with a description of Read ScreenMemoryMappedIbm3270 from memory.
  3. Event ID 8311, title ScreenBuffer IBM 5250 Screen with a description of Read ScreenMemoryMappedIbm5250 from memory.

Examples

[
    {
        "CorrelationId": "215bba64-1439-4fe6-8c55-ecd81f3d6d04",
        "Description": "ScreenSync start",
        "DateTime": "2024-06-11T11:42:28.687Z",
        "EntryId": 85,
        "PayloadType": "string_v1",
        "Process": "WebTerminalHub",
        "SessionId": "60c29f56-9419-4f48-98f1-f3f877371249",
        "Source": "HostSessionIbm5250:ScreenSyncObserver",
        "Category": "Trace",
        "PayLoad": " Thread ID: 9b40fd28-eb2c-4abb-9a23-c278392133cf. Logged Start Time: 2024-06-11 12:42:28.6872. Entry Creation Time: 2024-06-11 12:42:28.6873.",
        "EventId": 9140,
        "Title": "Terminal Session System Control"
    },
    {
        "CorrelationId": "215bba64-1439-4fe6-8c55-ecd81f3d6d04",
        "Description": "Read ScreenMemoryMappedIbm5250 from memory.",
        "DateTime": "2024-06-11T11:42:28.69Z",
        "EntryId": 86,
        "PayloadType": "ScreenMessage_v1",
        "Process": "WebTerminalHub",
        "SessionId": "60c29f56-9419-4f48-98f1-f3f877371249",
        "Source": "Client:ScreenBuffer",
        "Category": "Trace",
        "PayLoad": "{{Removed for Clarity}}",
        "EventId": 8311,
        "Title": "ScreenBuffer IBM 5250 Screen"
    }
]

HSS!48 - Groups of 5250 host updates are consolidated into one user-facing update.

5250 host updates are often multi-part. These parts in previous builds of Jubilant would be sent to the front-end as they were processed by the back-end Jubilant HostScreen Server. However, these multiple updates have been optimised to be sent as one final update.

This improves the speed at which screens are drawn in the front-end.

Fix

WTC!167 - Fields marked as display and bypass are no longer editable

5250 fields marked as display and bypass are correctly displayed as read-only text instead of as read/write entry fields.

WTC!177 - Allow the typing of special characters using the AltGr key

It is now possible to type special characters that are accessed via the AltGr modifier key.

For example the € symbol on a UK keyboard, or the ~ symbol on a German keyboard.

HSB!15 - In-memory screen model optimisation can no longer result in incorrect field attributes

In rare cases, optimisation applied to the reading of the in-memory screen model could have resulted in incorrect field attributes. The optimisation has been updated to avoid such scenarios from occurring.

Security

WTC.101 - Update to node packages to remove high vulnerabilities

Removed reference to node package react-pdf ^6.2.1 as it is no longer used.

Upgraded node package react-scripts from ^3.0.1 to ^5.0.1.

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.

  1. Unzip the installer into a folder.
  2. Close any web browsers.
  3. Close any Services windows.
  4. Open PowerShell ISE as Administrator.
  5. In the PowerShell ISE open the Jubilant PowerShell script: "JubilantUpdate.ps1".
  6. Run the required script by pressing the green play / run script button on the toolbar.
  7. 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.