Table of Contents

Release Notes 1.1.3.5 LTS

Metadata

This release documentation version 1.0.

Release 1.1.3.5-LTS
Release date 2024-08-29
Release type Full release or Patch
Future LTS (Long Term Support)
Server version 1.1.3.5+1.1.3.5-LTS-11730aa
Log Server version 1.1.3.5+1.1.3.5-872ad89
HostScreen Server version 1.1.3.5+1.1.3.5-28f39bba
Web Terminal Hub version 1.1.3.5+1.1.3.5-e66c42f
Web Terminal Client version 1.1.3.5+1.1.3.5-f964517
Management Console 1.1.3.5+1.1.3.5-faa9c25
Log Viewer 1.1.3.5+1.1.3.5-dd17df5

.NET Platform

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

Web Terminal Client Renderer File Names (checksum)

Location: Program Files\Flynet\Jubilant\WebTerminal\web

renderer.2b40fffc4614a3bfab13.js renderer.4b7269853ded7ff1a8af.js
renderer.4e675a3d02e2602145fe.js renderer.7b60e0ba28d5470bdbc8.js
renderer.8e1c52fae1486d84b902.js renderer.854e846020ff37bd1c2d.js
renderer.978ba985dba414cac7f7.js renderer.b6e91dce7ab74396b284.js
renderer.cebb0a643f6656a10137.js renderer.e222fed8fcb653af1aac.js

Upgrade Recommendations

This recommended for security updates in limited situations.

This update is recommended for 5250 users because of a fix for incorrectly merged screens.

Security Notes

This upgrade is recommended for security reasons.

.NET Security

.NET 8.0.7 is used this release of Jubilant that includes security updates. Maximum severity: Important.

However, only one of these vulnerabilities could under very limited circumstances have surfaced in Jubilant (CVE-2024-30105). Please see these .NET 8.0.7 notable changes.

High Importance Fix Notes

This update is recommended for 5250 users to avoid the incorrectly merged screen updates.

In this Release

New

There are never any new features in LTS releases.

Fix

ID Protocols Description
HSB.22 All Always read ScreenBuffer on gaining control to avoid merged screens.
HSB.23 3270 Remove RawDatum from serialized buffer to avoid edge-case failure when using SignalR JSON messaging.
HSS.57 3270 Clear Extended Attributes when mainframe clears the screen.
WTH.33 All Correctly stop all sessions when IIS web server stops.
LS.8 All Fixed the setting of the failover log level.
WTH.35 All Fixed session-clash when stopping / starting many sessions simultaneously.
WTC.298 3270 Fixed incorrectly handled null characters in double-byte-only fields.

Security

ID Protocols Description
.Net 8.0.7 All See .Net Security Notes.

Change Notes

HSB.22 - Always read ScreenBuffer on gaining control to avoid merged screens

In rare occasions, 5250 screen updates could be merged. This has been fixed in this release.

HSB.23 - Remove RawDatum from serialized buffer to avoid edge-case failure when using SignalR JSON messaging

When using 3270 with SignalR messaging in JSON mode, screens with character attributes would fail. This has been fixed in this release.

HSS.57 - Clear Extended Attributes when mainframe clears the screen

When using 3270, in some rare cases, it was possible that extended attributes would not be correctly cleared from the screen during a screen transition. This has been fixed in this release.

WTH.33 - Correctly stop all sessions when IIS web server stops

When IIS stops (or restarts) any sessions connected via the Web Terminal Client would only be disconnected by the HostScreen Server using configured time outs. These sessions become inaccessible as soon as IIS stops.

When IIS stops (or restarts) any sessions connected via the Web Terminal Client are now correctly and immediately disconnected.

LS.8 - Fixed the setting of the failover log level

The failover log level when the logging server is unavailable was not always being applied correctly. This has been fixed.

WTH.35 - Fixed session-clash when stopping / starting many sessions simultaneously

A fix to the session dictionary used by the Web Terminal Hub has increased the speed at which sessions can be started and stopped, avoiding a "cannot start session" error.

WTC.298 - Fixed incorrectly handled null characters in double-byte-only fields

When using 3270 with double-byte characters (for example, Japanese), it was possible for Web Terminal Client to set the null character to single-byte null, instead of the correct double-byte null. This has been fixed.

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.