B-12401

IBMi: Update IBMi implementation of agent to support changes for OpenSSL 1.1.1b.

Upgrade the current UA for IBMi to allow support of current SSL/TLS Versions as in any of the UA 6.9.0.0 Agents.

UA 5.1.1.0 now connects to a UA 6.9 Agent that has a TLS1.2 protocol definition in place which is the current default setting.

B-12407

IBMi: Attempt OpenSSL 1.1.1b build on IBMi 5.4.

B-12410

IBMi: packaging of created Agent code as "new" Release (5.1.1.0).

B-12811

Make UBROKER and components (UAG UDM UCMD...) XCF REALLOCATE aware/compatible

B-06093

UAGSRV tracing enhancements

Improved Tracing capabilities for SMF Exits

B-11538

zOS UAGSRV: Extended "Cancel Job" support for jobs running on any Sysplex node

The Problem

1. UAG supports cancelling jobs submitted by UAG and currently executing. This functionality does not work if a job is running on a Sysplex node other than the Primary one.

2. When a UNIX System Services (USS) job is executed as a batch job, multiple address spaces are spawned with the same job name.
   Since UAG cancels jobs by executing a z/OS CANCEL command with the job name as the parameter, the CANCEL fails due to multiple matching address spaces.

The Solution

UAG for z/OS tracks internally which system a job is executing on. When a Task Cancel request is received by a Primary UAG for a job which is not executing on the same system as the Primary UAG, the Task Cancel request will be forwarded to the system on which the job is executing. (Note this only works if the job has started execution and the Primary UAG has received the notification thereof.)

UAG has been extended to capture and save the address space ID of the submitted job. When a Task Cancel request is received, the address space ID is added to the CANCEL command to uniquely identify the job/address space to be cancelled.

B-07134

UAG File Monitor on z/OS should return an error when attempting to use features not supported

z/OS File Monitor enhancements for better supporting Sysplex secondary Agents and allowing Error based handling when non supported Features are being used.

As the primary Agent is, and will remain, the only Agent connected to a Controller and receive workload from a controller, a change has been implemented that will ensure that relevant File Monitors will be made available from the primary to any secondary Agent within the PLEX. That will ensure that any of the secondary Agents can also handle relevant file activity in case it is happening on a secondary Agent.

After a secondary Agents has started, and received his license, a file monitor synchronization process will be initiated by the primary Agent to allow triggering the file activity across the PLEX.

B-11537

zOS UAGSRV: Extend file monitor support for secondary agents in a sysplex environment

B-10365

Add support to UDM scripts for passwords with certain special characters =+-"

In order to support extended UTF-8 characters (those that translate into multibyte sequences) the passwords are internally translated from UTF-8 to UTF-16 and Unicode-aware version of the logon function is now being used for user authentication. This allows to use any extended unicode character to be used in user names and passwords.

Since the change was introduced in the common code for UDM, UCMD and UAG, it added support for those unicode characters not only for UDM, but for UCMD and UAG as well. There are no changes in behavior of UDM, UCMD and UAG as result of this change except for support of extended characters in user names and passwords.

B-12882

update configuration parsing routines to handle password with all supported characters

B-12884

Allow passwords with any characters to be specified in a udm script

B-11141

UFTP (SFTP Protocol) - Separate Connection from Transfer Logic

For the respective protocols, the Return-codes are categorized in 3 different, internal, groups

1.) XP_EXIT_ERROR (1002)

This generally includes any transfer error.

The client should end unsuccessfully with exit code 1002

2.) XP_EXIT_NETWORK (1024)

This error Code describes network issues that are encountered while a file transfer processing

The client should end unsuccessfully with exit code 1024

3.) XP_EXIT_SECURITY (1023)

This error generally occurs with authentication problems.

The client should end unsuccessfully with exit code 1023

Any results provided will be mapped to the Windows or Linux Exit-Code field to allow Job Status to be set accordingly.

B-11140

UFTP (FTP & FTPS Protocol) - Separate Connection from Transfer Logic

B-09713

UFTP - Add support for timestamps on UNV stdout/stderr messages

In Order to synchronize messaging structure, UFTP is enhanced to allow the same or similar timestamp settings as other components to enhance Messages produced for STDout and STDerr.

B-12442

UAG Remove enable SSL from configuration and installs

Necessary changes based on vulnerability findings in the 2020 Audit performed by SECUVERA.

B-12368

UAG change default for enable SSL to YES

E-01561

Universal Agent feature & Function for creating and delivering the Universal Integration Platform