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 necessarily 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

Provides Universal Agent support for SAP Task enhancements and improved form layout provided by Universal Controller 7.5.0.0.

Agent enhancements also include support for:

• Email notifications
• Extended print parameters
• Dynamic field population for ABAP reports, variants, languages, and output devices

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

INSTALL

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.