Page Comparison

Enhance options used to override a CA-7 Schedule ID with the following changes:

• Support lists and ranges of Schedule IDs with the #JI statement (e.g., #JI,ID=(1,3,5-8,12)).
• Accept #XI, #XO, and #XEND statements as synonyms for the #JI, #JO, and #JEND statements already supported by UAG Server

UAGSRV
UAGUTIL

Provides a local data store to hold job execution and checkpoint information to support standalone executionUAG for z/OS can now maintain a local job history dataset which that holds job history that can be used to manually rerun jobs originally executed by UAG Server.

Jobs Note that any job rerun manually in this manner are is not monitored or tracked by UAG or UC.See UAGCFG00 configuration options history_dataset and history_retention and installation job UNVIN12 for details on how the z/OS Universal Agent or Universal Controller.

This feature adds the UAG Server configuration options HISTORY_DATASET and HISTORY_RETENTION. A new installation job, UNVIN12, is provided to create and configure this functionalitynew feature.

See : "the UAGRERUN Stand Alone Execution" section in the Universal Agent User Guide for complete details on stand alone rerun execution.

Ubroker should mount UNVSPOOL with RWSHARE in Sysplex

Provides a change that causes the Universal Broker on z/OS to mount the UNVSPOOL file system with the zFS RWSHARE option in a Sysplex to prevent sharing violations in a Sysplex configuration.

Unix (except HP-UX)
Windows

UAGSRV
UEXT

Unix
Windows

UDM
UDMSRV

Introduces the following UDM variables that provide access to the following Utility Agent credential and hostname information:

• $(ops_utility_cred_user)
• $(ops_utility_cred_pwd)
• $(ops_utility_agent_name)

Support for JES2 /*ROUTE PRINT statements

Add support for z/OS tasks whose JCL contains a JES2 /*ROUTE PRINT statement, the output can to ensure proper output processing.

Prior to this change, output could be routed to another system before UAG has Server had a chance to process it. UAG Will now recognize the existence of these statements and comment them out while saving the destination. The job's output will be temporarily routed to the output class specified on the jes_sysout_class configuration parameter in UAGCFG00. When output processing is complete, UAG then route the job's output to the original class and destination

When UAG Server encounters this statement, it will use its JES_SYSOUT_CLASS configuration parameter to manage output processing and routing.

Add PGP signatures to Universal Agent distribution files.

For information on verifying these signatures, please refer to the following information.

UAGSRV
UBROKER
UFTP

Add end-to-end OpenTelemetry tracing support to UFTP when run from a File Transfer or Remote File Monitor task. Tracing support is also available for stand-alone UFTP execution.

UAGSRV
UAGRERUN

z/OS - Add support for EXEC RD parameter

New behavior. This backlog adds support for the JCL RD keyword on the JOB and EXEC statements. When RD=NR or RD=NC is specified, the affected step will be marked as non-restartable by UAG.

This new behavior can be disabled with the NORDNR UAGRERUN parameter.

See new configuration option rerun_options in UAGCFG00 for disabling this behavior globally.

Support Deletion of unexpired datasets

Update UAGRERUN behavior so that it deletes datasets prior to a run or rerun of a job, it will now override the expiration date, if anyincluding those datasets whose expiration date has not passed.

Prior to this change, unexpired datasets were not deleted by UAGRERUN's dataset cleanup processing.

OMS
UAGSRV

Provides an optional installation job, UNVIN14, that can be used to assist Agent configuration. This new job will automatically generate the EXIT ADD statements that should be added to a SYS1.PARMLIB PROGxx member to ensure SMF exits used by the Agent are configured correctly.

UNVINV14 uses the SYS1.PARMLIB SMFPRMxx as input and generates a list of missing exit point definitions and/or SMF record types.

UAGSRV
UEXT

Provides a change to the Universal Extension Event API to support arrays (Python list) as attribute values.

When the Universal Agent AGENT_IP configuration option specifies an IP address instead of a host name, eliminate the UNV0182E 'Cannot resolve' error, and accept the IP address as entered.

The extensions directory, located in the DATA_DIRECTORY path option for UAG Server, will now be created automatically when a non-default value is set for this option.

Prior to this change, Universal Task instances would stay in an Undeliverable status until directory was created.

Fixes a UAG Server crash that may occur when multiple Remote File Monitor instances finish at the same moment as a new instance is starting.

Always insert the UAGRERUN step ahead of any IF statements in the JCL. This will ensure that UAGRERUN is executed ahead of any initial EXEC or PROC statement that may be enclosed within an IF statement.

Fixes a problem where a debugging session will not start if the Debug button in the "Run and Debug" section of the activity bar is selected.

Prior to this change, the only way to start a debugging session was with F5.

Fixes a problem where a user specifies a dynamic choice field in the configuration.yml file that does not exist, and there are no dependent fields specified in the template.json file.

In this situation, the debugger fails to launch, and the error message KeyError: 'raw_type' is displayed.

Fixes an issue where Program and Variant Names do not appear in their respective drop down lists when adding an ABAP Program Job Step to an SAP Task.

The failure applies to Load Balancing (Type-B)

connections only and results in a "Missing required Value for RFC Connection" error.

Prevent a JCL error by ensuring that line numbers are not pulled into a JCL statement when

• The JCL used for a z/OS task contains line numbers, and
• A z/OS task variable is replaced with a value that is shorter than the variable name

The fix also prevents truncation of JCL statements that contain in-line data with hexadecimal values.

UAG: Improve handling of ABEND Step Conditions

When a step ABENDs and a Step Condition is used to ignore the ABEND (OK/Contiue), a subsequent step which references the ABENDing step in a JCL COND= keyword can execute, even if it normally would not. With this fix, any step which references an ABENDing step will not execute.

Resolves unexpected behavior for a z/OS task, under the following conditions:

• The z/OS task contains a Step Condition that is defined treat an ABEND as an expected result, by specifying an action of Continue/Success
• A subsequent step in the z/OS task's JCL contains an EXEC COND= parameter that references the ABENDed step, that would normally prevent execution of the step

Prior to this fix, the EXEC COND= parameter is not honored when the ABEND occurs, and the step executes.

This fix ensures the Step Condition and the EXEC COND= configuration is honored.

Windows
Unix (except HP-UX and Solaris)