Add Agent support for the new Trigger on Create option for Change file monitors. This allows a zOS agent to look for dataset creations or changes from the same file monitor task instance.

Unix
Windows

Unix
Windows

Fixes a situation in which a UDM file transfer will fail if an attempt is made to allocate a zOS dataset with an EXPDT equal to one of the following special values:

• 00000 - allocate the dataset with no expiration date

• 98000 - used by some tape management systems control when datasets are uncataloged and tape volumes become available for re-use

• 99000 - used by some tape management systems control when datasets are uncataloged and tape volumes become available for re-use

• 99365 - allocate the dataset so that it never expires

• 99366 - allocate the dataset so that it never expires

When none of the above 5-digit values are used, UDM will still expect a 7-digit expiration date as it did prior to this change.

UAGU83

Fixes a problem where an ABEND within the UAGU83 SMF exit module could cause RMF to terminate with an S0C1.

OMSSRV
UAGCMD
UAGSRV
UBROKER
UCERT
UCMD
UCTL
UDM
UEM
UFTP
UPPS

Add support for the following Ephemeral Elliptic Curve Diffie-Hellman (ECDHE) ciphers:

• ECDHE-RSA-AES256-GCM-SHA384

• ECDHE-ECDSA-AES256-GCM-SHA384

• ECDHE-RSA-AES128-GCM-SHA256

• ECDHE-ECDSA-AES128-GCM-SHA256

Provide the ability to automatically retrieve output for Remote File Monitor tasks.

The ability to retrieve output for Remote File Monitor tasks was available prior to UA 7.4.0.0, but this change allows output to retrieved automatically and made available for viewing as soon as the task ends.

Unix (except HP-UX)
Windows

Increase the number of characters supported in the Remote Server field of a File Transfer Task from 63 to 100 characters.

B-14809
B-15877

OMSSRV
UAGCMD
UAGSRV
UBROKER
UCERT
UCMD
UCTL
UDM
UEM
UFTP
UPPS
PKG

Update OpenSSL implementation to support TLS 1.3 sessions.

This feature provides the following configuration options:

• max_ssl_protocol - controls TLS session negotiation by limiting the protocol that will be used
• ctl_/data_ssl_cipher_suites (availability of these options varies by component) - allows the following TLS 1.3 cipher suites to be specified separately from – and mutually exclusive with – earlier TLS 1.x ciphers
  • TLS_AES_256_GCM_SHA384
  • TLS_CHACHA20_POLY1305_SHA256
  • TLS_AES_128_GCM_SHA256

The ability to enable TLS 1.3 across all Universal Agent components is available at install time via the --use_tls1_3 command line option (the Windows system mode install provides the equivalent USE_TLS1_3 command line property). When yes, this option sets the following configuration options:

• max_ssl_protocol to "tls1_3" in omss.conf, uags.conf, uftp.conf, ubroker.conf, ucmd.conf, ucmds.conf, uctl.conf, udm.conf, udms.conf, uem.conf, and upps.conf.

• encrypt to "yes" in ucmd.conf, ucmds.conf, and udm.conf

The interactive Windows installs also provides a new dialog with an option that, when checked, enables this configuration. This dialog is available for new installs and for upgrades from releases prior to 7.4.0.0.

OMSSRV
UAGSRV

Increase the maximum message size that can be transferred between UAG Server and OMS Server from 6 MB to 1 GB. 

The maximum message size allowed can be configured via the new OMS Server configuration option, MAX_MSG_SIZE. Similarly, a new MSG_CHUNK_OPTION option is provided to specify the maximum size for any single message transmitted. Any payload that exceeds this size will be split into multiple messages until the entire payload is transferred.

Add the ability to initialize a Universal Extension template from one of the following sources:

• A Zip File

• HTTP(S) Link to a Zip File

• Git Repository

Add a --register_ubrokerd option to the Linux system mode and user mode install scripts that will register the Universal Broker daemon with systemd.

Unix (except HP-UX)
Windows

Add the ability to report the progress of a Universal Extension task's execution via a new ui.update_progress(percent_done) API call.

Using the new RERUN_PROC_NAME option, allows customized JCL that executes the UAGRERUN utility to be inserted into a job executed from a z/OS task.

This customized JCL would replace the default OPSSTP00 step that UAG Server inserts by default.

Updates the handling for the EXTENSION_PYTHON_LIST, which allows users to configure an ordered list of Python interpreters to use for Universal Extension task execution.

Previously, the Python provided by the Universal Agent were installed, it would always be evaluated first. However, there were times where another Python that also satisfied the extension's requirement was preferred. As long as the Agent's Python was installed, the other Python would not be chosen.

With this change, if the Agent's Python is included in the EXTENSION_PYTHON_LIST value, the default ordering of the list is disabled and the Agent's Python is evaluation in the order in which it appears in the list.

Add support to the Universal Extension development plugin for VisualStudio Code to initializing templates from external sources.

This is a companion delivery to B-15917 for UIP-CLI. 

Add the ability to set the UAG Server MESSAGE_LEVEL and LOGLVL values at:

• Installation, using the --ac_message_level and --ac_loglvl command line options for Unix Installs and Windows user mode installs (the Windows system mode install uses AC_MESSAGE_LEVEL and AC_LOGLVL installation properties)
  • In addition to command line properties, the Windows interactive installs provide a new dialog to set these options
• Universal Broker startup. using the new uag_message_level and uag_loglvl command line options or the UAGLEVEL and UAGLOGLVL environment variables

Unix (except HP-UX)
Windows

Add the ability to access the Key Location of a Universal Extension credential field using a consistent snake_case convention instead of camelCase.

For example, given a credential field called cred_test, the Key Location may be accessed using:

• fields['cred_test']['key_location']
• fields['cred_test.key_location']

The camelCase usage (i.e., keyLocation) is still recognized for backward compatibility, but that support could be dropped at any time so new extensions should use key_location.

Eliminate all "benign" ICH408I message occurrences from the RACF log. 

These messages would sometimes appear during UDM's processing, when checking for access to resources it required. UDM would silently ignore the situation that caused these messages, using an alternate execution path. This change will ensure that UDM takes no action that could result in these messages. 

UCMD
UDM

Correct the spelling of a credential's passphrase when referenced by a Universal Extension task. The previous spelling pasphrase is now corrected to passphrase.

For backward compatibility, pasphrase is still accepted, but new extensions should use the correct spelling as this backward compatibility could be lost in future releases.

Unix
Windows

OMSSRV
UAGSRV
UBROKER
UCMD
UCMSRV
UCTL
UCTSRV
UDM
UDMSRV
UEM
UEMSRV
UFTP
UQUERY
UPPS
USAP

Provides changes that:

• Adds operating system name and version to the Universal Query Report heading, and
• Adds operating system name and version to header information contained Universal Agent component trace files.

Add the ability for the VisualStudio Code Plugin for Universal Extension development to detect when an extension's implementation no longer matches the extension template defined in the Controller.

The types of "out-of-sync" conditions the VSCode Plugin will detect are listed below.

• Invalid field name: This occurs when the Python code references an invalid field name for a given context (e.g., extension_start, Dynamic Choice Command, Dynamic Command).

• Field used as incorrect type: The Python code uses a field incorrectly, based on that field's type definition in the Controller.

• Invalid Dynamic Choice Command Name: The Python code references an invalid Dynamic Choice Command name. This can occur when the Dynamic Choice field has been renamed or removed from the template.

• Invalid Dynamic Command Name: The Python code references an invalid Dynamic Command name. This can occur when the Dynamic Command has been renamed or removed from the template.

• Unimplemented Dynamic Choice Command: The template contains a Dynamic Choice field that is not implemented in the Python code.

• Unimplemented Dynamic Command: The template contains a Dynamic Command that is not implemented in the Python code.

• Invalid dependent field mapping for Dynamic Choice field: A Dynamic Choice Field specifies a dependent field mapping for a field that does not exist in the template.

• Invalid dependent field mapping for Dynamic Command: A Dynamic Command specifies a dependent field mapping for a field that does not exist in the template.

Unix
Windows

• UAG_SCRIPT_DIRECTORY - specifies a directory that is visible to the native user environment in which the task executes.
• UAG_SCRIPT_DIRECTORY_RELATIVE_TO - used with UAG_SCRIPT_DIRECTORY to specify a location in an isolated execution environment (e.g., chroot). This is a location that the user in whose context the task executes would not necessary see in their native shell environment, but is visible to the task's environment.

Neither of these variables need to be defined for a task that does not execute in an isolated, secure environment.

Unix
Windows

Revisit changes previously delivered by B-14668 in Universal Agent 7.3.0.0. That delivery provided the ability to automatically recover a Universal Broker database that failed validation at startup. However, to provide backward compatibility, that feature was not enabled by default and had to be manually configured across the enterprise with the Universal Broker RECREATE_DATABASES configuration option.

The UA 7.5.0.0 release provides the following changes to the automatic Broker database recovery feature:

• The RECREATE_DATABASES configuration option is deprecated.
• Automatic recovery now occurs by default for those databases that fail a validation which may occur at Broker startup. This validation is triggered whenever the databases weren't properly closed during shutdown of the previous Broker instance. Affected databases include:
  • bcomponent.db
  • scomponent.db
  • ues.db
  • uems.db
• By default, the Broker creates a copy of any database that fails validation. The Broker then removes the corrupted database and recreates it so that Broker startup may proceed.
• The number of database copies is controlled by a new DB_FILE_GENERATIONS configuration option. The default value of that option is 3. Database archival can be turned off by setting the value of the option to 0 (zero).

The intent of the updated behavior is to improve Agent resiliency and recoverability while retaining some ability to manage these database files.

Unix
Windows

Add the ability to define activity tracing and collect performance metrics for Universal Extension tasks, OMS Server, and UAG Server.

Data is collected by an OpenTelemetry collector, making it suitable for display in front-end applications like Grafana and Jaeger.

Fixes a problem where the output for a task will contain the first character of the next line that exceeds the number of output lines the task is configured to automatically retrieve.

For this problem to occur, a task

1. Must be configured to automatically retrieve stdout/stderr, and
2. Must specify a "number of lines" to retrieve from that output

UCMD
UCTL
UDM
UEM
UENCRYPT
UFTP

Unix
Windows

PKG

Fixes a problem introduced in the 7.4.0.0 release that may cause upgrades to fail if the Python distribution for Universal Agent is installed.

• the task's JCL is pulled from the specified JCL Override Library, and
• a JCLLIB statement is manually inserted within JCL statements that UAG Server generates and inserts into the JCL

Fixes a situation in which a UDM file transfer will fail if an attempt is made to allocate a zOS dataset with an EXPDT equal to one of the following special values:

• 00000 - allocate the dataset with no expiration date

• 98000 - used by some tape management systems control when datasets are uncataloged and tape volumes become available for re-use

• 99000 - used by some tape management systems control when datasets are uncataloged and tape volumes become available for re-use

• 99365 - allocate the dataset so that it never expires

• 99366 - allocate the dataset so that it never expires

When none of the above 5-digit values are used, UDM will still expect a 7-digit expiration date as it did prior to this change.

Remove an extra line that is shown in the Universal Broker log when the Broker is run in console mode and UAG Server encounters a job launch failure.