Fix a problem where File Monitor tasks do not honor a specified stable period if there are multiple file monitor instances running with the same credentials.

Note

This item may be identified in other UA releases as D-10568 or D-10705.

Prevent a deadlock that may occur when a CHANGE File Monitor instance detects new matching files.

Note

This item may be identified in other UA releases as D-10587 or D-10707.

Prevent a CHANGE File Monitor that specifies a stable period from incorrectly generating multiple events.

Note

This item may be identified in other UA releases as D-10544 or D-10733.

Prevent a failure for the Display Event History command when the timestamp exceeds 8 characters.

Note

This item may be identified in other UA releases as D-10742 or D-10795.

Prevent a failure when a model job uses a jobname of exactly 32 characters in length.

Note

This item may be identified in other UA releases as D-10730 or D-10828.

Remove world-writable permission from the ./spool/reservedSpace file.

Note
This item may be identified in other UA releases as D-05312.

Add the KILL_PROCESS_TREE option to control how UAG Server responds to a Cancel task command from Universal Controller. When yes, the entire process tree is terminated via SIGTERM. Any process within the tree that is still running after 10 seconds is terminated with a SIGKILL. UAG Server will confirm that all processes in the process tree are terminated before it notifies the Controller of the termination.

To preserve compatibility with existing behavior, the default value for this option is no, which can prevent the termination of a process in the tree that ignores the SIGTERM signal. This may cause the task's status in the Universal Controller to show Cancelled although the (now orphaned) process continues to run.

Remove internal DEBUG-level messages that are generated by the Universal Extension base class when the extension task's log level is DEBUG.

Only DEBUG messages issued by the extension developer should be shown.

Add the following commands/options to the UIP-CLI utility:

• task launch - launch a Universal Extension task
• task status - obtain the status of a Universal Extension task
• task output - obtain the output generated by a Universal Extension task

Make all all Task Instance variables set by the Controller for a Universal Extension task available to the Extension.

An extension can access these variables via the self.uip.task_variables dictionary property (e.g., self.uip_task_variables['ops_task_id']).

Add the ability to retrieve values from the Universal Controller File Transfer Task form that support transfers using explicit FTPS (i.e., FTP with SSL). 

To support integration with Universal Monitor tasks, receive information from the Controller that can by used to identify an Extension task launched via a Universal Monitor Trigger. 

Values received from the Controller are saved in the following properties:

• self.uip.trigger_id - the Trigger UUID value set by the Controller that uniquely identifies the trigger instance. This will be undefined if the extension task was not launched by a Universal Monitor Trigger.
• self.uip.instance_id - the EXECID set by the Controller than uniquely identifies the Extension task instance
• self.uip.monitor_id - the Universal Monitor UUID that uniquely identifies the Universal Monitor instance. This will be undefined if the extension task was not launched by a Universal Monitor.

The Universal Extension base class sets the following property when a Trigger ID is received:

• self.uip.is_triggered
  • If the Extension task was executed via a Universal Monitor Trigger, this property will be True. Otherwise, it is False.

Add full support for Universal Monitor tasks, including the ability to reconnect to Universal Extension tasks (executed on behalf of the Monitor task) that continue to run when an Agent is restarted.

Prevent an authentication error for a File Transfer task when the following conditions exist:

• The File Transfer task uses Universal Data Mover (UDM)

• A UDM script is used by the task

• The UDM script issues the exec or execsap command

• The exec or execsap command uses the pwd parameter
• One of the built-in credential variables – $(ops_primary_cred_pwd) or $(ops_secondary_cred_pwd) -- is used for the pwd parameter's value

For example:

open src=local dst=rmthost.ipaddr user=$(ops_secondary_cred_user) pwd=$(ops_secondary_cred_pwd)
exec src cmd="dir" user=$(ops_primary_cred_user) pwd=$(ops_primary_cred_pwd)

Starting with UA 7.0.0.0, this will cause the resolved $(ops_primary_cred_pwd) value in the exec statement to be enclosed in double quotes ("). The double quotes are retained when passed to UCMD Manager (or USAP for an execsap statement). The double quotes will prevent successful password authentication.

UAG Server may crash when a Universal Extension task references a credential token greater than 3000 characters in length.