Release Notes > Release Notes Version 9.00A > Release Notes Automation Platform

Release Notes Version 9.00A

Highlights


Service Packs 

[Highlights][Service Packs] [Notes for Update Installation] [What's New] [Improvements] [Bug Fixes][Known Issues]

A Service Pack is released within a Automation Engine version and includes modifications and several corrections (critical and non-critical ones). Service Packs are supplied at predetermined dates in intervals of three to six months. 

Note that the Service Packs 1 to 4 include major enhancements and therefore, databaseA database is an organized collection of data including relevant data structures. modifications. Note that the components Automation Engine, Utilities, UserInterface and Initial data of these Service Packs must always be updated together.
You must always copy the complete DB directory before you start to update the database (initial data).
If you use tablespaces that are not AE standard (in Oracle databases), you must also adjust the step_xxx.sql SQL files accordingly. These files are provided in the following DB directory: DB\oracle\9.00A

Note that the agents of the ServicePacks 1 to 4 can only run with an Automation Engine of the same or a later ServicePack level.

Service Pack 1 to 4: For importing XMLfiles and loading Transport Cases, the affected AE system must have the same ServicePack version as the source or a later one. Any attempt to load an XML import file from an SP2 AE system to an SP1 AE system results in an error.

When installing a new Service Pack, make sure that you use the current Online Documentation. If your version is not up to date, an incorrect document may open when you open the help in the UserInterface via the F1 key. This can also happen if you install the Online Documentation with a hotfix but use an older version of the UserInterface.

Hotfixes are released to correct errors for which there is no workaround.

The complete hotfix number provides information about the relevant ServicePack. For more details refer to the document Version Indicator for AE.

Service Pack 12

Service Pack 12 does neither include new features nor modifications.

Service Pack 11

SAP BW: Data for Chain Steps Published as Script Variables

In SAP jobs with BW chains, the agent creates several script variables for each child process. These variables and their values are available automatically in the (child) post process tab, and appear in the Detail Window of the tasks. For the list of variables and their values at the Chain, Step, and Step Job levels, see SAP BW: Data for Chain Steps Published as Script Variables.

The Script function GET_VAR has been restored to its behavior known from versions prior to v9SP4: Static Variable objects will not be resolved recursively anymore. Therefore the key RESOLVE_GET_VAR has been removed from the system variable UC_SYSTEM_SETTINGS.

Service Pack 10

Service Pack 10 does neither include new features nor modifications.

Important: As of version 9.00A, agents handle transfers for FileTransfer objects. The agents write reports with .REP file extensions. The timestamps in the FileTransfer reports represent the time on the agent. In previous releases, FileTransfer reports were written by the Automation Engine with .LOG file extensions and the timestamps in the FileTransfer reports represented the server time.

Service Pack 9

Service Pack 9 does neither include new features nor modifications.

Important: After upgrading to version 9 Service Pack 9 you also have to upgrade all user interfaces to v9SP9. The UserInterface v9SP9 is not compatible to Automation Engine v9SP8.

Service Pack 8

Modifications

The Values of Script Variables That Are Set with :PSET Are Now Only Passed on to the Next Workflows One Level Above

The value of the script variable that is set with :PSET are now only be passed on to the next workflow one level above (parent) but not to the top workflow (such as grandparents or great-grandparents etc.). In previous releases, there was an error where the value of the script variable that was set with :PSET in the lowest script (grandchild) in a workflow that included sub-workflows was passed on to the top workflow (grandparents or great-grandparents etc.).

:PSET No Longer Inherits Values ​​Within Tasks in a Scheduler or Period Container

The value of the script variable that is set with :PSET will never be passed on to a Schedule or Period Container. In previous releases, there was an error where this did occur.

Service Pack 7

New Features

UNIX agent: PAM supported

In addition to Solaris agents, authentication via PAM (Pluggable Authentication Modules) is now also supported in Linux and AIX agents.

Service Pack 6

New Features

RA - Connection objects: Traffic-light symbols signal the connection status

When you open RA Connection objects, the system now verifies whether a corresponding agent is active and that a connection is possible. The new traffic-light symbol now shows the connection status in the specific CONN-object tab.

Selective statistics: New "Remote Context" tab

You can now use the new "Remote Context" tab in order to filter the statistics for RA attributes and certain parameters of the SAP Solution Manager. For more information, see the tab's documentation.

Service Pack 5 

As of version 9 Service Pack 5, the values of object variables that are defined in the Variables&Prompts tab are used without any changes being made to them. This is different to previous versions (v8 and v9 up to SP4) where single inverted commas that were created in this way were automatically removed from the beginning and the end of object variable values. If the value included three or more single inverted commas, they were truncated starting with the second inverted comma.
Special case as of v9SP5: Inverted commas are not removed and therefore, you can no longer use a blank without inverted commas (the value is always: ' '). Automic recommends using the script element :PSET as a workaround in this case.
To ensure a seamless update to version 9.00A, you can use the following SQL statement in order to display a list of all affected objects:
select oh_client, oh_name, OV_VALUE from oh, ov where oh_idnr = ov_oh_idnr and ov_value like '%''%';
Afterwards, you will have to adjust the affected objects manually before you start to update your version.

A change in the Automation Engine has the effect that objects that include prompts can only be processed asynchronously (implements IResponseHandler for asynchronous calls) via the Java Application Interface (uc4.jar) This means that the Automation Engine will only respond to an ExecuteObject request when all prompts have been filled with values. Please refer to the supplied example.zip file for an example code (ExecuteWithPrompt.java).

In the script element GET_LOGIN, AE has implemented a security function that verifies that the login information derives from a backend system. Otherwise, an error will occur. The login information of agents cannot and must not be read using this script element.

New Features

SAP agent: Adjustable encoding for the output files of SAP elements

You can now determine an encoding (such as UTF-8) for the output files of all SAP elements that create an output file (parameter FILE=). You use the new optional parameter ENCODING= for this purpose. When you do not specify this parameter, the system will by default use ISO-8859-1 for the encoding (as in previous versions)

The parameter ENCODING= can also be created in the UserInterface by using the Forms tab. An input assistant is available and lists the supported encodings.

All SAP elements are affected that have the parameter FILE=. These are:

Service Pack 4

Service Pack 4 includes database modifications.

The classes "CallOperator", "ExecutorList" and "ExecutorListItem" have been removed from the AE Java Application Interface. These classes have been flagged as deprecated starting with version 8.00A and a corresponding note that these classes should no longer be used has been added to the javadoc. The classes "Notification", "AgentList" and "AgentListItem" are now available and provide the same functions.

A change has been made to the script function GET_VAR, which is not compatible to version 9SP3 and prior: The called variable will be resolved instead of displaying its name.
To enable the behavior known from previous versions, the new key RESOLVE_GET_VAR has been introduced in the UC_SYSTEM_SETTINGS variable. It provides two values, which allow the switch between the two possibilities, display variable name or resolve it.

Note for using the utilities with Java Version 1.7 which is supported as of Service Pack 4:
To start the graphical interface of the utilities with Java 1.7, you must use the Java call of the new supplied INI files as otherwise, the program will crash. Adjust the existing INI files as shown in the following example for the utility AE DB Load:

Java call for Java 1.6:
cmd="javaw" -Xmx512m -jar -cp .;.\UC4LookAndFeel.jar ucybdbLd.jar

Java call for Java 1.7:
cmd="javaw" -Xmx512m -cp .;.\UC4LookAndFeel.jar -jar ucybdbLd.jar

The behavior of the script function GET_VAR has been changed: Now static as well as dynamic variable values are being resolved recursively, when using GET_VAR. In order to set its behavior so that the value of a static Variable object is read, as it does in previous versions of the Automation Engine, use the new key RESOLVE_GET_VAR in the UC_SYSTEM_SETTINGS variable.

New Features

New script elements

  • :CONST- It creates a script variable as a constant with a specific value.
  • :SWITCH... :CASE... :ENDSWITCH - It checks whether the value of a variable complies with specific values and depending on the result, it processes various statements.
  • GET_LOGIN - Reads information from Login objects.
  • LOAD_PROCESS - It loads a specific data sequence.
  • RERUN_UC_OBJECT- Continues a certain workflow.
  • SAVE_PROCESS- It stores a specific data sequence.

VARA object - New types: SQL SECURE and SQLI SECURE

Basically, the new variable sources SQL SECURE and SQLI SECURE have the same functions as SQL / SQLI with the difference being that you can always use variables (predefined variables or placeholders of VARA objects) within the SQL statements. They are not affected by the setting VAR_SECURITY_LEVEL in the UC_SYSTEM_SETTINGS. There is no security risk for the database that might be caused by an SQL injection.

Note that for using SQL SECURE Variable objects, you need a Database Agent of version v9 SP3 or later.

Overwriting the attributes of RA Jobs during the activation process and on workflow level.

The RA tab of RA jobs now includes the new option "Request task parameters". Activating this option means that a PromptSet dialog will appear when you activate the Job. You use it to set or overrule the specific RA attributes / parameters.

The new Solution tab that is now available in the properties of workflow tasks of RA Jobs is similar to the Job's specific RA tab. You use it to change the RA attributes on workflow level.

The options Task Prompts in the properties of workflow tasks have been moved from the Variable & Prompts tab to the General tab. This has been done because the options do not only affect the PromptSets but also the parameter dialog of RA Jobs.

Extended rollback functions

You can now roll back workflows including their subordinate tasks. In a rollback, the workflow's tasks will be processed from the end to the beginning.

The following new commands are available in the context menu of the workflow monitor:

  • Rollback to this Task: This rolls back the selected task and its successors.
  • Rerun: This can only be used for a complete workflow. It runs all workflow tasks for which the rollback process has been completed or which are waiting for the rollback process.

New states:

  • Waiting for rollback (1655)
  • ENDED_WF_ROLLBACKED (1905)
  • FAULT_ROLLBACK (1830)
  • AgentGroup Rollback (1652)
  • Workflow Rollback (1653)

The new value RERUN is available in the predefined variable &$RUNMODE#.

The fulfillment of external dependencies when removing a blocking condition.

You can now define external workflow dependencies in a way that they are automatically fulfilled when their blocking condition is removed. This is obviously only relevant for external dependencies whose related task is within a workflow or blocks within it.

The properties of external dependencies now provide two new options for the expected status:

  • ANY_OK_OR_UNBLOCKED - The external task ends without an error or it is no longer blocked.
  • ENDED_OK_OR_UNBLOCKED - The external task ends with ENDED_OK (return code 0) or it is no longer blocked.

Extended Login object

Login tab: The column "Platform" has been renamed to "Name" and "Host Type" to "Type"

In the "Name" column, you can now enter and store any value. In the new variable UC_LOGIN_TYPES, you can define types of Login objects that will be listed with the agent platforms in the "Type" column.

The new script element GET_LOGIN has been implemented and the script element MODIFY_OBJECT has been extended.

You can now use these extensions in order to define Login information not only for agents but also for backend systems.

New option for FileTransfers: "Transfer complete folder structure"

So far, empty folders have not been transferred in partially qualified FileTransfers. You can now change this behavior by setting the new option "Transfer complete folder structure" (FileTransfer tab). For compatibility reasons, this setting is not active by default.

You can also use the new attribute FT_TRANSFER_FOLDERS with GET_ATT or PUT_ATT to activate this setting.

PrompSet variables: Using variables in default values

You can now use system properties variables or object properties variables in the format &$VARIABLE# or Variable objects in the format {VARIABLE} or {VARIABLE, key, column} in the default values for PromptSet variables. These variables will be replaced by the corresponding current values when the PromptSet variable is being resolved.

Make sure that you do not use the name of the own variable within the value as this causes an infinite loop that is caught with the following error message:
U1001348 - Possible loop in the variable substitution.

Notification: New template

Automic now supplies a template object for Email--type Notification objects: CALL.MAIL.HTML. It includes a predefined notification text in HTML format and a script. For more information refer to the chapter Creating Notifications.

Utility UC4 DB.Unload - New deletion method

This utility now has a new mode that can be used to delete data during the reorganization process. The new deletion process is faster and consumes less memory.

The following new INI-file parameters are available for the utility UC4.DB Unload:

  • reorg_mode=
    You can select whether the old method (value "0") or the new deletion method ("1") should be used.
  • reorg_chunk_size=
    The size of the transaction blocks for the deletion process.
  • reorg_sleep_time=
    The time in milliseconds that the system should wait between the deletion transactions.

Service Pack 3 

Workflows are referred to as ProcessFlows prior to AE v9 SP 3.

Service Pack 3 includes database modifications.

New Features

New workflow types: IF and FOREACH

Service Pack 3 provides two new workflows types: IF and FOREACH workflows. The default workflow type is "Standard".

You can define the workflow type when you create the object. The Template window now also includes all three workflow types: Standard, IF and ForEach.

To define workflows of type IF and FOREACH, you can use the new Logic tab which replaces the former Workflow tab.

  • IF workflows: These workflows have exactly two serial branches to which you can add tasks. Depending on the user-defined condition(s), either the one or the other branch is processed.
  • ForEach workflows: These workflows represent a loop. For each line of a VARA object or the entry of an array, a task chain is processed once.

The properties of IF and ForEach workflow tasks are the same as the properties of wtandard workflow tasks.

The Preconditions and Postconditions tabs in the properties of workflow tasks now include the PUBLISH VALUE statement. 

The following new predefined variables have been implemented:

  • &$LOOP_COUNT#
  • &$LOOP_INDEX#
  • &$RETURNCODE#
  • &$STATUS#

Rollback

For objects, you can now define backup or rollback actions in the new Rollback tab which is available in all executable objects that can be part of a workflow.

There are two different types of backup/rollback:

  • Custom backup/rollback
    Here you specify an executable object for backup and rollback actions.
  • File backup/rollback
    This action is only available for Unix/Windows Jobs and FileTransfers.
    You must specify a directory or certain files for the backup and rollback action.

To run a file-based rollback / backup under Windows, you must set PowerShell as the agent's interpreter. You can use the parameters ECPEXE= and ECPEXT= in the Windows agent's INI file([GLOBAL] section).

A backup is made when you activate an object, a rollback only when you explicitly make a Rollback. For a more detailed description, see Rollback.

The following new features are available:

  • The new ROLLBACK action in the Postconditions tab (in the properties of workflow tasks). It runs the task in rollback mode.
  • A new agent variable (for Windows and UNIX agents): UC_EX_PATH_BACK
  • Activity Window: The new Rollback button in the toolbar
  • Context menu of the workflow monitor and the Activity Window: New Rollback command

New states: 

  • ENDED_ROLLBACKED (1904)
  • ENDED_ROLLBACK_EMPTY (1913)
  • FAULT_CUSTOM_BACKUP (1825)
  • FAULT_CUSTOM_ROLLBACK (1827)
  • FAULT_FILE_BACKUP (1826)
  • FAULT_FILE_ROLLBACK (1828)
  • FAULT_HOSTGROUP_ROLLBACK (1829)
  • Custom backup (1557)
  • Custom rollback (1650)
  • File backup (1558)
  • File rollback (1651)

New predefined variable:

  • &$RUNMODE#

Deployment

You can run Deployment processes that are defined in the Release Manager (separate product) by using workflows of the Automation Platform. Doing so requires the workflows to be defined in the newDeployment tab.

The General tab which is available in the properties of workflow tasks now includes the new option Run per patch.

You can also define Deployment Workflows using the Enterprise Control Center's new "Process Assembly" perspective.

Note that the Deployment tab and the option "Run per patch" are only displayed if the client's Deployment function is activated in the new setting DEPLOYMENT_CLIENT (UC_CLIENT_SETTINGS).

New script elements

Net areas in AE

The CPs of an AE system can now be located in different net areas. This way, you can manipulate the CP selection of components such as agents.

You can use the new parameter NetArea= ([TCP/IP] section) in the Automation Engine's INI filefor this purpose. TheSystem Overview of the Server processes now includes the new column Net area.

AE.DB Change: Modifying RA attributes

You can now use the utility AE.DB Change in order to change the specific attributes of RA Jobs.

In the script file, you must specify the attribute that should be changed as follows: "CVALUE:attribute name"

SAP Solution Manager Integration

The Solution Manager in SAP can now be used to retrieve information from an AE system and to perform certain actions.

Extended SAP agent functions are now available. In the SAP Connection objects, you can now configure the settings of the SMSE interface.

SAP CallAPI

The SAP Java Connector version 3.0 is now supported.

Note that as of ServicePack 3, the SAP CallAPI does not support any other Java Connector version.

Extended function of the script element GET_UC_SETTING

The script element GET_UC_SETTING can now also retrieve values from Queue objects. To do so, you can use the new parameter Option.

Ring-trace functionality for OS agents

The agent for BS2000, OS/400, UNIX, VMS, Windows and z/OS has the new tracing flag "Memory (INI-file - Section TRACE - Parameter memory=), which activates the so-called Ring Trace.

When the Ring-Trace function is activated (1 - 9), the agent trace is put in memory and written in a file when required. This results in the performance of the agent and the size of the trace file to decrease.

Note that traces are only set in close cooperation with Support.

Service Pack 2 

Workflow - Properties - Pre-/ Postconditions tab: As opposed to Service Pack 1, the action EXECUTE OBJECT always passes the variables of the workflow task on to the started object.

PromptSet objects: The text-field option Show as passwordA secret combination of characters for a Automation Engine user. now actually encrypts the specified value. Passwords that are entered via prompts are no longer shown in clear text in reports, for example.
In former versions, this setting had only a visual effect (only in the PromptSet dialog, the characters were displayed as *). 

Attention: Service Pack 2 also includes database modifications.

The options for a workflow task's prompts (Workflow - Properties - Variables & Prompts tab) are now grayed out if no PromptSet objects are assigned to the object.
In Service-Pack 1, you could activate these two options although doing so had no impact.

The setting SQLVAR_SECURITY_LEVEL in the variable UC_SYSTEM_SETTINGS is now called VAR_SECURITY_LEVEL. For compatibility reasons, the old name is still supported.
Reason: This setting does not only affect Variable objects of type SQL/SQLI but also those of type BACKEND (new as of SP2).

Dynamic PromptSet dialogs
Service Pack 1 required a default value to be defined for PromptSet elements whose value should be inserted in an attribute (such as Host and Login in an SQL variable) of a dynamic PromptSet element's reference variable. This is no longer required in Service Pack 2.

ForSAP agents, the System Overview now displays the SAP Basis version of the SAP system (SW Version column) and a new message that includes the SAP Basis version is written to the agent's log file.

The XML-based reports of SAP jobs are now also available as XML files in the external job Output.

In SAP Connection objects, the default value for the maximum number of simultaneous connectionshas been changed from 10 to an unlimited number. See also SAP note 314530.

New Features

Enterprise Control Center

A new Automic product is now available, the Enterprise Control Center (ECC). The ECC is a web applicationA web application is an application that is accessible over a network (Internet or intranet) and is typically coded in a programming language like Java or JavaScript, combined with a markup language like HTML. Web applications are provided on web servers and web browsers are used as GUI on client computers. that provides an easy and clear access procedure for various applications.

You can use the ECC in order to start particular objects and monitor and influence their execution. The Process Automation and the Process Monitoring perspectives (part of the ECC) are required for this purpose. The installation and configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. documentation is provided in the Administration Guide.

VARA object - New source BACKEND

As of Service Pack 2, the new variable typeBACKEND is available. It can be used to provide the result of an OS command as variable values in the form of user-defined columns.

The new User privilege "Create and modify Backend variables" is now available and can be used to create or edit VARA objects of the source BACKEND.

The variableUC_SYSTEM_SETTINGS now includes the additional setting BACKENDVAR_MAX_ROWS. It can be used to limit the lines that Backend variables return to a particular number. The new settingVAR_TIMEOUT in the variable UC_HOSTCHAR_DEFAULTcan be used to define a maximum time for the execution of commands.

Predefined BACKEND Variable objectsare supplied in client 0 (UC_RB_TEMPLATES folder).

SAP agent

SAP Java Connector version 3.0 is now supported.

As of Service Pack 2 only the version 3.0 of the SAP Java Connector is supported. This version is now required for the SAP agent. 

SAP Process Chains

  • New script element BW_SET_CONSTRAINT.
  • Child processes of process chains can now be restarted.
    They can either be restarted manually by using the Activity Window or automatically. You can define the criteria for an automatic restart by using the new script element BW_SET_CONSTRAINT.
  • The job can now remain active in order to be able to restart a process chain if it has included errors or has been canceled.
    For this purpose, the option SUSPEND has been added to the parameter ERROR= of the script elements BW_ACTIVATE_CHAIN and BW_RESTART_CHAIN.
  • Erroneous or skipped child processes of process chains can be displayed.
    The parameter REPLICATE= of the script elements BW_ACTIVATE_CHAIN and BW_RESTART_CHAIN has been extended for this purpose.
  • You can now decide not to assume the reports of child processes to the job report.
    BW_ACTIVATE_CHAIN / BW_RESTART_CHAIN: new parameter COLLECTLOGS=
  • Spool lists can explicitly be requested.
    The new parameter GET_SPOOL= is now available in the script elements BW_ACTIVATE_CHAIN, BW_RESTART_CHAIN, R3_ACTIVATE_REPORT, R3_ACITVATE_JOBS and R3_ACTIVATE_INTERCEPTED_JOBS.
    The spool list is stored to the directory that can now be defined in the SAP agent's INI file by using the new parameter download_dir= (section [GLOBAL]) as a text file.
  • Spool lists that have been requested using the function R3_GET_JOB_SPOOL or the parameter GET_SPOOL (see script element above) are automatically registered as external job output.
  • Synchronous execution of process chains.
    BW_ACTIVATE_CHAIN: new parameter SYNCHRONOUS=.
  • The exact states of the child processes are now displayed in the Activity Window's Remote status column.
  • The Activity Window combines process chains and their child processes within an SAP job as separate nodes.

The SAP Forms tab has also been extended for these new functions.

Searching for RA Values

The Search can now also consider the specific fields of RA objects (Jobs, Connections).

Service Pack 1

Note that Service Pack 1 includes database modifications.

New Features/Modifications

Prompts - New Features

Text fields with the property "Value required" in the PromptSet input dialog are no longer highlighted in yellow when you have not specified any value.

AE DB Load - Modification

The dialog that displays if an SQL error occurs while the initial data is loaded now includes a new Repeat button.

Calling this button has the effect that the SQL commands are re-executed starting at the position at which the error has occurred. The process continues if the problem does not occur anymore.

Using Prompts and Object Variables in Cockpits

The Variables & Prompts tab is now also available for the object type CPIT.

 


Notes for Update Installation

[Highlights] [Service Packs] [Notes for Update Installation] [What's New] [Improvements] [Bug Fixes][Known Issues

Please verify that your environment complies with the system requirements of the relevant Automation Engine version before you start the installation process. You will find a list of supported platforms and version as PDF in theAE Knowledge Base.

 

Important note for updating to version 9.00A 

The Result tab of workflow tasks has been replaced by thePostconditionstab.

When you update your database or load the Transport Case, the system is automatically converted to the new version. This means that the conditions and actions of the Post Process tab are set in a way that its functionality is similar to the Result tab of version 8.00A or earlier.

Object imports of previous versions (XML) must be converted manually. Do so by starting the utility AE DB Load and select the ConvertResult.txt file which is available in the folder IMAGE:\DB\GENERAL\9.00A.

The action CANCEL PROCESS FLOW (cancels the workflow) differs from the Cancel Workflow option in the Result tab:

Attention: Active workflows are not converted. After updating to version 9.00A, the Postconditions tab of these workflows in the Activity Window is empty and the Result properties of the previous version are no longer available. Automic recommends ending all workflows before starting the update process.

The Result tab no longer exists. This includes that you cannot modify it anymore by using the script element MODIFY_TASK. Adjust your scripts if necessary. Be informed that neither the new Preconditions tab nor the new Postconditions tab can be modified by using the script element MODIFY_TASK.

Script variables and object variables that are named &X and / or &XC must not be used in workflow tasks which include conditions / actions in their properties (Preconditions and Postconditions tab). This rule applies to all workflow tasks of previous Automation Engine versions that include Result properties (Result tab). Automic recommends renaming all existing script and object variables with this name or a runtime error will occur when the workflow starts.

Run the following SQL statements on the AE database in order to list all objects with the specified object variables that are part of a workflow:

select OH_Name as ObjectName, OV_VName as ObjectVariable from OH,OV where OH_Idnr = OV_OH_Idnr and OH_DeleteFlag = 0 and (OV_VName = '&X' or OV_VName = '&XC' or OV_VName = '&XC_' or OV_VName like '%&XC%') and OH_Name in (select JPP_Object from JPP)

The following SQL statement supplies the PSET and :RSET scripting lines of all objects that set the variables &X and &XC (MS SQL Server):

select * from OT where
lower(OT_Content) like ':%rset%&x[ =]%'
or lower(OT_Content) like ':%rset%&x'
or lower(OT_Content) like ':%rset%&xc[ =]%'
or lower(OT_Content) like ':%rset%&xc'
or lower(OT_Content) like ':%rset%&xc+_' escape '+'
or lower(OT_Content) like ':%rset%&xc+_[ =]%' escape '+'
or lower(OT_Content) like ':%pset%&x[ =]%'
or lower(OT_Content) like ':%pset%&x'
or lower(OT_Content) like ':%pset%&xc[ =]%'
or lower(OT_Content) like ':%pset%&xc'
or lower(OT_Content) like ':%pset%&xc+_' escape '+'
or lower(OT_Content) like ':%pset%&xc+_[ =]%' escape '+'

Oracle - databases: The following SQL command lists all affected :PSET and :RSET lines:

set define off
select OH_Client, OH_Name as ObjectName, OV_VName as ObjectVariable from OH,OV where OH_Idnr = OV_OH_Idnr and OH_DeleteFlag = 0 and (OV_VName = '&X' or OV_VName = '&XC' or OV_VName = '&XC_' or OV_VName like '%&XC%') and OH_Name in (select JPP_Object from JPP);
select * from OT where lower(OT_Content) like ':%rset%&x%' or lower(OT_Content) like ':%pset%&x%';

In DB2 - databases use this command:

select OH_Client, OH_Name as ObjectName, OV_VName as ObjectVariable from OH,OV where OH_Idnr = OV_OH_Idnr and OH_DeleteFlag = 0 and (OV_VName = '&X' or OV_VName = '&XC' or OV_VName = '&XC_' or OV_VName like '%&XC%') and OH_Name in (select JPP_Object from JPP);
select * from OT where lower(OT_Content) like ':%rset%&x%' or lower(OT_Content) like ':%pset%&x%';

Agent

The agent for GCOS8 has not been developed further and corresponds to the level of version 8.00A.

The agent for J2EE/JMX (9.00A) only supports the version CE (Composition Edition) 7.1 of the SAP Netweaver Application Server. Refer to the adjusted Installation Guide.

The parameter WorkDirMatch= in the UNIX agent's (9.00A) INI file is no longer considered.

Strongly compressed files can no longer be transferred. In FileTransfer objects, compression can now be activated (normal compression) and deactivated. Therefore, the setting ft_compress_strong= is no longer available in the OS agent configuration files as of version 9.00A.

The agent files for all UNIX platforms are supplied in lowercase letters. Therefore, you must adjust the file name of the job messenger the INI files of older versions:
[VARIABLES] UC_EX_JOB_MD = ucxj???m

As of version 9.00A, agents handle transfers for FileTransfer objects. The agents write reports with .REP file extensions. The timestamps in the FileTransfer reports represent the time on the agent. In previous releases, FileTransfer reports were written by the Automation Engine with .LOG file extensions and the timestamps in the FileTransfer reports represented the server time.

When you use Java agents (SAP, RA, JMX, SQL) of version 8.00A, they must at least be of version 8.00A030-500. Otherwise, the Form tabs will not work.

The Email connection of agents is only available via SMTP. MAPI2 is no longer supported for Windows agents.

The z/OS Event monitor can no longer be started in combination with the z/OS agent. The agent's INI file section CONSOLE has been removed. The Event monitor can only be started as an individual Started Task.

The C-Loader is no longer available for starting the Java agents (SAP, JMX, Rapid Automation and Database) under Windows. Agents under Windows can only be started via the JAR file. Keep this also in mind when using the ServiceManager.

The flow trace of FileTransfers has been changed. More information is now output and the output itself has also been changed. Make sure to adjust all scripts which read data from FileTransfer report (PREP_PROCESS_REPORT).

The report of partially and fully qualified FileTransfers is now structured as follows:

<Timestamp> - U0011124 File search started with filter '*.txt' ...
<Timestamp> - U0011125 'c:\temp\src\a.txt' <Timestamp> - U0011125 'c:\temp\src\b.txt'
<Timestamp> - U0011125 'c:\temp\src\c.txt'
<Timestamp> - U0011126 File search completed, '3' files selected.
<Timestamp> - U0011133 OK '15' Bytes, '0' Records for file 'c:\temp\src\a.txt'->'c:\Temp\dst\a.txt' transferred. Duration '00:00:00'.
<Timestamp> - U0011133 OK '15' Bytes, '0' Records for file 'c:\temp\src\b.txt'->'c:\Temp\dst\b.txt' transferred. Duration '00:00:00'.
<Timestamp> - U0011133 OK '15' Bytes, '0' Records for file 'c:\temp\src\c.txt'->'c:\Temp\dst\c.txt' transferred. Duration '00:00:00'.
<Timestamp> - U0011408 FileTransfer '76836123' completed.

The MBean for VMWare (JMX agent) is no longer available. Use the RA agent for VMWare instead.

As of version 9.00A, the CrystalReports MBean for Business Objects is no longer supplied. Use the RA agent with the solution for Business Objects instead.

The UNIX agent's INI-file parameter FT_Owner= has no effect if the new FileTransfer protocol is used (source and target agent are of version 9 or later). The User who is specified in the Login object is used in this case. 

The UNIX agent automatically sets its real user (UserID) to "root" (0) after it has started. In doing so, the agent can change to another user for FileTransfer actions or when files should be deleted, for example.
To ensure that the ServiceManager can end the UNIX agent, you must start it with root privileges and set the sbit for its owner. For more detailed information refer to the ServiceManager Installation Guide.

OS/400 agent: The default value of the INI-file parameter CheckLogon= has changed from "0" to "1".

In the new FileTransfer protocol, theOS/400 agent uses the OS commands DRTPF and ADDPFM for transferring files. This includes that you can specify CRTPF parameters in the file attributes of FileTransfers. The advantage is that you can draw the conclusion that an unspecified error that occurs during a FileTransfer could be an error that occurs when these commands are being processed. In this case, you will find more information in the related job log.

The file systems IFS (OS/400), OSS (NSK) and USS (z/OS) are now supported for FileTransfers. These file systems support the creation of temporary files. The required behavior can be specified in the agents' INI files using the parameters ft_temp_file_ifs=, ft_temp_file_oss= and ft_temp_file_uss=.

In addition to Windows and UNIX agents, you can now also use Java agents (SAP, RA, JMX, SQL) in order to send mails. Note that you must only configure the AutomationEngine (instead of each agent). The E-mail connection of these agents is always active.

The following diagnostic documentation is now created when a Windows or SNMP agent crashes:
crash_*.log - This file includes a detailed description of the error and the current status of the OS (register, OS version, application version etc.)
crash_*.mdmp - A forced dump that is generated by the OS. It includes the current process memory.

Usually, the Windows agent writes these files in its Temp directory. Under certain circumstances (the INI file is not yet fully initialized) it can happen that these files are stored in the folder in which the agent's program files are stored. The SNMP agent writes these files in the directory %WINDIR%\System32 or in its Temp folder.

Objects

The Group settings "Execution" in the Attributes tab are no longer available due to the functions of the new Queue object.

During the updating process, all Group objects that were used as queues in the previous version are converted to Queue objects of the same name. The queuing functionality remains.

Note that because of this modification, the scripting lines that add objects to a queue do not work anymore (:PUT_ATT START_TYPE = queue).
You can use the following SQL statements to list all scripting lines that assign objects to a Group:

SELECT OH_Client, OH_Idnr, OH_Name, OT_Type, OT_Lnr linenumber, OT_Content line FROM OT,OH WHERE OT_OH_Idnr=OH_Idnr and OT_Content LIKE ':%PUT_ATT% START_TYPE%=%'
UNION
SELECT OH_Client, OH_Idnr, OH_Name, OT_Type, OT_Lnr linenumber, OT_Content line FROM OT,OH WHERE OT_OH_Idnr=OH_Idnr and OT_Content LIKE ':%PUT_ATT% GROUP=%'
UNION
SELECT OH_Client, OH_Idnr, OH_Name, OT_Type, OT_Lnr linenumber, OT_Content line FROM OT,OH WHERE OT_OH_Idnr=OH_Idnr and OT_Content LIKE ':%PUT_ATT% GROUP %=%'
UNION
SELECT OH_Client, OH_Idnr, OH_Name, OT_Type, OT_Lnr linenumber, OT_Content line FROM OT,OH WHERE OT_OH_Idnr=OH_Idnr and OT_Content LIKE ':%PUT_ATT% S=%'
UNION
SELECT OH_Client, OH_Idnr, OH_Name, OT_Type, OT_Lnr linenumber, OT_Content line FROM OT,OH WHERE OT_OH_Idnr=OH_Idnr and OT_Content LIKE ':%PUT_ATT% S %=%'

Queue Groups and all their tasks that are still available in the Activity Window automatically abort during the updating process with the status FAULT_OTHER. Automic recommends ending all queues before starting the update.

The values of object variables in the Variables & Prompts tab are always retrieved from the object definition if a restart is made. Previous Automation Engine versions retrieved the values from the task that had the reference -RunID.

Reports can only be sent using Notifications objects if the user has the relevant authorizations: The "P" authorization for the corresponding object type (such as JOBS) and EXTREP (for external job output files).

An update to version 9.00A automatically sets the Client Queue in all objects in which a Group has been specified as a Queue (setting: Execution - Automatically).

The "start type" field has been changed to "Group". For compatibility reasons, the attribute "START_TYPE" is still available but Automic recommends using the new "GROUP".  

The QueueManager object has been renamed to RemoteTaskManager. The object symbol has also been changed. The new Queue object now shows the former symbol of the RemoteTaskManager.

The "Event History" menu item has been renamed to "ABAP Event History" in the SAP Console Event setting "Data source".  

The Values tab of executable objects has been extended. It is now possible to select PromptSet objects whose input prompt is displayed during the activation process. The corresponding tab has been renamed to Variables & Prompts and displays with a new symbol.

The Checkpoint tab that is available in the properties of workflows has been renamed to General.

Notification object: The "Attach reports from" field in theNotificationtab includes the new option "Source". You can use it in order to determine whether the database's default reports, the output files or both should be sent.

Note that the CLIENT_QUEUE object in <No Folder> is automatically created when a new client is created. It cannot be deleted.

In order to access external job outputs, users require the new EXTREP right. After an update, users of previous Automation Engine versions who have all rights for all objects (table - * in all columns) are also authorized to use the external job output function.

The "validity keyword" column in Variable objects has been renamed to "key".

Regardless of the interface used the message type of Job reports in SAP will now always be shown (example: "S516 Job started").

Script

As of version 9.00A, the :READ script statement does not allow an empty string for the default value. You now must enclose a space character in quotes.

As of version 9.00A, you can no longer use a CallAPI to restart a stopped client (script element: TOGGLE_SYSTEM_STATUS). Explanation: CallAPIs also need an active Queue(new object) in order to start. Because all Queue objects are also stopped if a client is stopped, this procedure is not possible.

The script element :STOP in combination with the stop mode "MSG" can only be used for the error numbers 50-59.If you execute it using a different number, the script aborts and an error message is output that informs about the fact that the error number is not valid.

The script function GET_STATISTIC_DETAILnow returns an empty string ("") if the statistical record could not be found. Previous versions returned a runtime error in such a case. 

Static Variable objects now include 5 value columns. For the script element:PUT_VAR, this means that values that include one or several commas and should be written in one column must always be enclosed in single-quote or double-quote characters. Otherwise, the values are written in several value columns.

In versions 8.00A or earlier, the following scripting line "test1,test2,test3,test4,test5" was written to the value column. As of version 9.00A, this line has the effect that the value "test1" is written to value column 1, and "test2" to column 2, etc. The behavior has also changed.

:PUT_VAR VARA1, "KEY1", test1,test2,test3,test4,test5

If necessary, adjust your scripts. If the value "test1,test2,test3,test4,test5" should be written to the value column 1, use the script element :PUT_VAR as follows:

:PUT_VAR VARA1, "KEY1", "test1,test2,test3,test4,test5"

The script function:SEND_MAILnow only uses the AutomationEngine's Email connection. Ensure that the files that should be sent as attachments are stored at a location the AutomationEngine can access. In jobs, you can also register files as job outputs and send them as email using a Notification object.

Using the script element GET_PROCESS_LINE in order to access the entries of a Variable object (PREP_PROCESS_VAR) without specifying a column number returns the value of all columns (Key / Result column included), separated by §§§ characters. An empty column now includes a blank between the separators. Each value has an actual length as opposed to previous Automation Engine versions, when the validity keyword was always returned with a fixed length of 200 characters and the rest had been filled with blanks.

Please note: As of v9, GET_PROCESS_LINE has to be in a PROCESS loop formed by script statements.

As of version 9, you must use inverted commas in order to specify a value that includes several variables in the script element :PUT_VAR. In older versions, you could use the following line, for example:

:PUT_VAR VARA.TEST, 'Key', &month#_&year#

Now you must enclose the value in single or double quotes or you will not be able to store the script:

:PUT_VAR VARA.TEST, 'Key', '&month#_&year#'

When values are read from a static VARA object by using the script element GET_VAR, the system will now replace the character sequence "&&" by "&". For this reason, you must double the even number of "&" characters that are used in a row in order to ensure that a correct value can be read. Individual "&" characters are not changed.
For example:

Value in the VARA object Wert nach GET_VAR
&TEST# &TEST#
&&TEST&& &TEST&
TEST&&& TEST&&
&&&&TEST&&&& &&TEST&&

The script elements CINT and CSTR are no longer supported for the new data types of script variables. Use the new function CONVERT instead. There is still compatibility with the scripts of previous versions.

For compatibility reasons, the script elements SYS_ACT_JPNAME, SYS_ACT_JPNR, SYS_ACT_JOBNAME and SYS_ACT_JOBNR are still supported. They are no longer listed in the ScriptEditor's auto-completion function and the Automation Engine Documentation because there are other script elements which provide the same functionality.

AE now supports the use of floating-point numbers and negative numbers in scripts. Therefore, scripts that use numbers and arithmetic operations in version 9.00A can supply results that differ from the results of previous versions. Automic recommends adjusting your scripts accordingly. The following table shows several assignments and the results that are output in the activation protocol: 

Value assignment Result version 8.00A or below Result as of version 9.00A
:set &a# = 56 0000000000000056 0000000000000056
:set &a# = -21 -21 -0000000000000021
:set &a# = -25.2 -25 -0000000000000025.2000000000000000
:set &a# = +53 Error 0000000000000053
:set &a# = +49.1 Error +0000000000000049.1000000000000000
:set &a# = "+21.30" +21.30 +21.30
:set &a# = 1,123 0000000000000001 1,123

Note for script variables that should store a negative value: Before assigning a value (:SET), you must create them with a data type that can store negative numbers ("signed" or "float"). You can declare variables to a specific data type by using the script statement:DEFINE.

Note for variables that have been created without a specific data type: A runtime error will occur when you assign a negative value. When you assign a positive floating-point number, this number will be stored without the decimal places.

Version 8 and earlier ones: The script element GET_STATISTIC_DETAIL also retrieves the number of binary file lines (depending on how often CRLF occurred) in combination with the detail RECORDS). New as of version 9: Because this is only useful for text files, the value "0" will always be returned for binary files.

Initial Data

Particular Calendar keywords have been removed from the Holiday Calendars of individual countries because they were not correct. A list of all affected holidays is provided in the section Improvements - General. 

The TimeZone object TZ.MST (Mountain Standard Time) is now supplied by default. Ensure that objects of the same name that already exist in client 0 must be deleted before an update is made. Otherwise, loading the initial data results in an error.

Database

To update a DB2 database to version 9.00A, you required the EXECUTE right for SYSPROC.ADMIN_CMD.

DB2 - Databases on z/OS are no longer supported. 

The Access database UC97.mdb which includes the AE database's structural description is no longer supplied. The structure is still available in HTML format.

Automation Engine

The E-mail connection  must only be configured for the AutomationEngine. The section [MAIL] in the INI files of Windows and UNIX agents has been removed. The mail function of agents is only used if external job output files (attach reports) are sent using Notification objects. Agents of previous versions act as usual and the INI-file section [MAIL] is still available. 

The 16th digit of the setting SERVER_OPTIONS (A = using of the old Server activation) in the variable UC_SYSTEM_SETTINGS is no longer supported. Set it to "N" if necessary.

UserInterface

Important: After upgrading to version 9 Service Pack 9 you also have to upgrade all user interfaces to v9SP9. The UserInterface v9SP8 is not compatible to Automation Engine v9SP9.

The classical workflow view is no longer available. The default view has been improved.

The Mail column in the "Agents" menu item in the System Overview has been replaced by the new "Services" column. It includes either the value MAIL (E-mail connection is active), SQL (Database Agent is used to resolve SQL variables) or no entry at all. Windows, Unix and Java agents (SAP, JMX, RA and SQL) of version 9.00A are always displayed with an active E-mail connection.

The term "JCL variant" has been renamed in the UserInterface. The new term is "platform".

The "Express" command in the Activity Window's context menu has been renamed to "Ignore Agent Resource".

Documentation

The requirements for the Automation Platform are now also available online in the AE Knowledge Base.

Changed Terminology

OS/390 has been renamed to z/OS in the Automation Engine Documentation and the message library because the platform OS/390 is no longer supported. 

The term "UC4 Server" has been replaced by "Automation Engine".

 


What's New

General Information

New object type "Queue" (QUEUE)

Queue objects can be used to combine several executable objects which should be started with a particular priority and a particular maximum number of tasks which can run parallel (max. slots). These settings can also be changed for a particular period of time (exceptions).

All objects start within a Queue. A Queue object can be selected in the Attributes tab of executable objects. The object is automatically executed in the Client Queue if no other Queue object has been selected.

Queue objects take over the main functions of Groups (JOBG). Groups are only used as containers for tasks.

The queue type for group objects from previous releases of AE no longer exist. They have been replaced by Queue objects.
It is possible to assign a title to Folder objects. As in all other objects, this title is displayed in the column "Title" of the UC4 Explorer.

New object type "PRPT" (PromptSet)
PromptSet objects are user-defined prompts which can be used to query values during an object's activation. Variables (similar to object variables) provide the values to the started object and can also be changed. PromptSet objects are assigned via the Variables & Prompts tab which is available in almost all executable objects. The input dialog is defined in theDesigner tab of PromptSet objects: via drag and drop, you can select and arrange the various graphical control elements (e.g., text fields, checkboxes, date and time fields, etc.). Subsequently, you can specify a particular behavior for the control elements (allowed values, default values, etc.) in the properties.

It is possible to override the default values of PromptSet elements for executable objects and Workflow and Schedule object tasks using the Variables & Prompts tab. The Values tab has been extended and the new Variables & Prompts tab is available in the task properties of Workflows and Schedule objects.

Dynamic retrieval of Variable-object values
The Variable object has been extended. It is now possible to retrieve values from a particular data source when the Variable object is directly accessed. The available data sources are an external database, the AE database, other Variable objects or the directory of the agent computer. In this case, the Variable is referred to as a "dynamic variable".

You can still enter values in Variable objects manually or by using script (= static variable). The data source determines whether a Variable is dynamic or static. The source is determined when the Variable object is created and cannot be changed subsequently. TheVariable tabeither includes a value table (static variables) or the settings for the dynamic retrieval of values.

The Attributes tab now includes several settings (output format, min. / max. value, etc.).

During the transports and imports of Variable objects of previous versions (source = static), these are automatically converted to the new data types.

Conditions for workflow tasks
You can now define conditions which will be checked before and/or after the execution of workflow tasks. Use the new Preconditions and Postconditions tabs which are available in the task properties for this purpose. If conditions apply, the corresponding statements are processed (e.g., an object starts if a task ends with a particular status). Else links can also be created and you can even change how often a block is checked ("Once", "Always", "Deactivate").
Using system values and object attributes in scripts and other attributes
Several valuescanbe defined at runtime via pre-defined variablesin attributes and in scripts. These values can depend on the system (e.g., system time, AE system name) or other attributes of the same object (e.g., host). The UserInterface now provides a new dialog in which you can select these values. Call the corresponding windows via the Variables... button which is available in the toolbar of objects.
Usage of Variable objects in object attributes
Variable objects can directly be specified in object attributes using a particular placeholder. This placeholder will be replaced at the object's runtime with the value provided in the Variable's first line and column. For further information refer to the document Using Variable objects.

New data types of Variable objects
The data types "Time" and "Date" are new. All other data types have been renamed:

Old New
Character var. length - AUTOTRIM Text
Number ranging from 0 to 2147483647 Number
Time stamp 16 Byte Timestamp

Starting agents and Server processes via the UserInterface or the script element MODIFY_SYSTEM
You can start agents or server processes via a service in the ServiceManager via the context menu in the System Overview (UserInterface) or with the new script function MODIFY_SYSTEM.

Doing so requires specific settings for the connection to the ServiceManager to be adjusted. This is done either automatically using the command "Refresh ServiceManager Scan" in the System Overview or manually in the Agent or Server object (Attributes tab). An automatic search for suitable ServiceManager services is made when the server processes start for the first time.



Registering Job files
You can now use the newOutput tabor the script element:REGISTER_OUTPUTFILE in order to specify files that can be opened via the UserInterface after they have been processed. These files are external Job-output files that are stored and available on the agent computer. Job files can so be accessed quickly and easily. In addition to the default reports (such as Job report, JCL, and script), these files are also listed in the new Directory tab which is available in the report dialog.

This functionality is supported for Windows, UNIX, SAP,  RA, JMX and Database Jobs.

The Notification object has been extended: A source must be determined in theNotification tab, "Attach report" option. This setting is only relevant if Job reports should be attached and if it must be specified whether the database's or the agent's Job output, or both should be sent.

TheFilter object now includes the new filter category "External Job output". It can be used to search external Job output files also for Job executions (Output Scan tab).

Alias
You can now assign an alias for workflow tasks in the properties ->General tab (in previous Automation Engine versions referred to as Checkpoint tab). This alias is used instead of the object name in the workflow monitor, the Activity Window and the Statistics. The object name is always available in the Detail Window. This function can also be used for external dependencies.

You can also use an alias for tasks that are activated once or recurrently (see:  Execution with Options) or activate it by using the script elementACTIVATE_UC_OBJECT.

UserInterface

General Information

Improved navigation in the UserInterface

  • The "Quick Access" function can be used for a quick object search within a client and direct access to them.
  • Use the Quick Search in windows which list the objects. This function is only available for the following areas: UC4 Explorer, Statistics, Activity Window, Forecast, Auto-Forecast, Search and System Overview.
    It is a text search which displays search results in the form of a list and highlights the matching objects.
  • Fields in the tabs of objects provide a Quick Search function and a Quick Access function via the context menu.
  • Quick Search in workflows. The new function "Connect to" (context menu of the Line Tool) can be used to connect workflow tasks via Quick Search.
New column "Platform"
The Activity Window, the UC4 Explorer and the Statistics include the new column: "Platform" which displays the platform-specific symbols of jobs, RemoteTaskManager, events, agent groups, file transfers and agents.

Automation Engine

General Information

Using floating-point numbers and negative numbers in AE Script

  • Variables can now be created with a specific data type which signalizes that a Variable is a string, a positive or negative integer or a floating-point number. Thus, four different data types are available.
  • The new script statement :DEFINE can be used to declare a variable to a particular data type.
  • The new data types can also be used for arithmetic operations.
  • The script element :SET can be used to solve an arithmetic expression.
  • The new script function CONVERT facilitates the conversion of data types.
Script arrays
Variables can now be created asarrays. In doing so, a Variable can store several different values. Three new script elements serve this purpose ->:FILL, FIND and LENGTH.
Storing and displaying the last Server messages of work processes
The setting MQA_COUNT_BACK in the variable UC_SYSTEM_SETTINGS can be used to determine the number of Server messages of work processes which should be buffered for further analyses. They can then be called via the System Overview (Automation Engine).
A log-file change of work processes automatically changes the log files of all work processes.
New Functionality

:DEFINE - Declares a script variable with a particular data type.
:FILL - Stores several values in a script array.
:PUT_PROMPT_BUFFER -Same function as :PUT_READ_BUFFER
:PUT_VAR_COL - Stores a value to a particular column of a static Variable object.
:REGISTER_OUTPUTFILE- Registers a file as an external Job output.
CONVERT - Converts the data type of a value.
FIND - Searches a script array and returns the corresponding index.
GET_ATT_PLAIN - Supplies the value of a task's attributes during its generation. Variables are not resolved.
LENGTH - Retrieves the size of a script array.
MODIFY_SYSTEM - Executes ServiceManager actions or Queue modifications.
SYS_ACT_RESTART_COUNT- Returns the number of restarted workflows which have been executed using the script statement RESTART TASK (Postconditions). 

Extended Functionality

:PUT_READ_BUFFER- Variables that are located in the ReadBuffer override the PromptSet variables of objects that have been started with ACTIVATE_UC_OBJECT.
:PUT_VAR - Several values can be written to several columns of a static Variable object at once.
ACTIVATE_UC_OBJECT- The task can now be started by using new parameters in a particular Queue object and with an alias.A further parameter determines whether the PromptSet input dialog should be displayed.
CREATE_OBJECT - Creating static variables with the new data types (time and date) is possible. Data types are now specified differently, the former spelling is still supported.
GET_PROCESS_LINE - Access to the extended column number of Variable objects.
GET_STATISTIC_DETAIL - New detail "RUNID". The script no longer aborts if a statistical record cannot be found. The error can be handled using :ON_ERROR.
GET_VAR - Specification of a column number that can be used to access the Variable.
MODIFY_OBJECT- Modification of the data type of static variables, which includes the new data types date and time. Data types are now specified differently, the former spelling is still supported.
MODIFY_TASK - The alias of workflow tasks that have been added using the corresponding script element can be changed.
MODIFY_UC_OBJECT - The attribute "SET_EXPRESS" can also be used for Queue objects.
PREP_PROCESS_VAR - The value filter can now be used for a particular column of the Variable object.
RESTART_UC_OBJECT - Specifying a Queue object for the task to be started is possible with an additional parameter

:RSET statements automatically create object values
When you assign :SET and :RSET statements the same script variable with different values, their values will be set by those :SET and :RSET statements when the job is executed. However, if the job is restarted, the values of both variables will be set by the :SET statement. This is because :RSET statements automatically create object values and :SET statements automatically save the value for a restart. This is a change in behavior from v8, where :RSET statements did not create object values.

Agents

Database

Ingres databases are supported
The agent now also supports Ingres databases.

SAP

Java Schedule Events are supported
Console Events in UC4 can react to Events of the SAP Java Scheduler. The Console-Event object has been extended: The new item "Java Event History" has been added to the menu "Data source". "Event History" has been renamed to "ABAP Event History".
The new Variable object UC_SAP_JXBP_EVENTTYPES which is supplied in client 0 stores the possible Event types of the Java Scheduler. The values of this variable are listed for the Event-type selection in the Console Event.

New JCL parameters
The script elements R3_ACTIVATE_REPORT, R3_ACTIVATE_JOBS and R3_GET_JOB_LOG have been extended for the optional parameters BEG_LOGINES and END_LOGLINES. These parameters can be used to include a particular number of SAP job-log lines in the UC4 Job report.
z/OS

User is checked in jobs that use the setting "Type - JCL incl. z/OS job card"
The parameter userid_type and the section (USERID) in thez/OS agent's INI file are now checked even if the setting "Type" - JCL incl. z/OS job card" has been specified in the Job object (z/OS tab). In other words, even if the Job card and the JCL are retrieved from z/OS, no other OS users are allowed to start the UC4 Job than those that have been specified in the agent's INI file. 

Extended file attributes for FileTransfers
More file attributes are now available for the destination of FileTransfers. These attributes must be specified in a new format(ALLOCATE command). The old format is still supported. As in all platforms, you can also keep the original z/OS attributes (option "Keep original file attributes" in the FileTransfer object). Original attributes cannot be overridden.
USS (Unix System Services) supported
The file system USS is now supported for FileTransfers. Temporary files can be created depending on the setting that has been defined in the's INI-fileparametertemp_file_uss.

Documentation 

General Information

New design for the Automation Engine Documentation
The colors used in titles, table backgrounds and lines and the font for the Automation Engine Documentation have been adjusted to the general UC4 design.


Improvements

General Information

Optimized FileTransfer procedure
UC4 now transfers files in a more efficient and secure manner. The agents now take over tasks, thereby reducing the Automation Engine's workload.

  • Increased speed and transmission security
  • New option for partially qualified FileTransfers: Abort at first error (FileTransfer tab)
  • Sending Agent now solves the complete FileTransfer order.
  • Each FileTransfer has its own connection.
  • File attributes are now supported (NSK, z/OS, OS/400, Windows, BS2000).
  • FileTransfers are handled in threads (OS/400, Unix, Windows, z/OS) or processes (NSK).
  • Original attributes can be passed on to the target file.
  • Extended wildcard usage (several variable placeholders can be used for the destination).
  • Agents create the target directories, if not exists (independent of the option Include sub-directories )
  • Unicode files are supported.
  • The limitation of 31k for the record length has been removed.
  • No file size limit (in early Automation Engine versions: around 2GB per file)
  • File names can be up to 512 bytes long
  • UNIX: FileTransfers run under the user specified in the Login object
  • Synchronous / Asynchronous transmission can be set in the UC_HOSTCHAR_DEFAULT (settings: FT_ASYNC_QUIT*)
  • Nagle algorithm for FileTransfers can be disabled in the Agent's INI file (parameter: tcp_nodelay=)

The old FileTransfer protocol (up to version 8.00A) will be used for compatibility reasons if at least one of the participating agents is of version 8.00A or before.

Selecting an RA Solution in an AgentGroup
In AgentGroups, you can now also specify the Solution name provided that the platform "DIT" (RA) has been selected. In doing so, AgentGroups can only include RA agents of a particular Solution which provides for clear assignments.

Holiday Calendars have been revised
The Calendar objects that are supplied in the system client have been improved. Some Calendar keywords have been corrected and additional ones have been added. Invalid holidays have been removed. The following keywords and Calendar objects are affected:

  • CORPUS_CHRISTI
    UC_HOLIDAYS.F, UC_HOLIDAYS.HK, UC_HOLIDAYS.I, UC_HOLIDAYS.IRE, UC_HOLIDAYS.L, UC_HOLIDAYS.LV, UC_HOLIDAYS.M, UC_HOLIDAYS.MAL, UC_HOLIDAYS.MEX, UC_HOLIDAYS.NL, UC_HOLIDAYS.SGP, UC_HOLIDAYS.SLO, UC_HOLIDAYS.TUR
  • ASCENSION_DAY
    UC_HOLIDAY.HK, UC_HOLIDAYS.I, UC_HOLIDAYS.IRE, UC_HOLIDAYS.LV, UC_HOLIDAYS.M, UC_HOLIDAYS.MAL, UC_HOLIDAYS.MEX, UC_HOLIDAYS.P, UC_HOLIDAYS.PL, UC_HOLIDAYS.SGP, UC_HOLIDAYS.SLO, UC_HOLIDAYS.TUR
  • WHIT_MONDAY
    UC_HOLIDAY.HK, UC_HOLIDAYS.I, UC_HOLIDAYS.IRE, UC_HOLIDAYS.LV, UC_HOLIDAYS.M, UC_HOLIDAYS.MAL, UC_HOLIDAYS.MEX, UC_HOLIDAYS.PL, UC_HOLIDAYS.SGP, UC_HOLIDAYS.SLO, UC_HOLIDAYS.TUR
  • EASTER_SUNDAY, EASTER_MONDAY, EASTER
    UC_HOLIDAYS.MAL, UC_HOLIDAYS.MEX, UC_HOLIDAYS.SGP, UC_HOLIDAYS.TUR
  • GOOD_FRIDAY
    UC_HOLIDAYS.MAL, UC_HOLIDAYS.PL, UC_HOLIDAYS.SLO, UC_HOLIDAYS.TUR
  • LABOR_DAY
    UC_HOLIDAYS.NL
  • CHINESE NEW YEAR (3RD DAY)
    UC_HOLIDAYS.SGP
  • FIRST DAY OF FASTING, CHRISTMAS
    UC_HOLIDAYS.TUR

The following keywords of the Calendar UC_HOLIDAYS.CAN have been renamed:

  • FAMILY DAY - PROVINCIAL ALBERTA to FAMILY_DAY
  • DISCOVERY DAY (YUKON) to DISCOVERY_DAY_YT

UserInterface

General Information
New look and feel
A new interface design (default design) is now also available for the look and feel of Automation Engine version 8.00A (classic design).
New workflow design
A new workflow view is available. The edges of the task boxes are rounded. The connection lines are curved and make it easier to see the tasks that are connected.

Extended Activity Window

  • Host-type selection is possible
  • Usage of negative filters (option "NOT") in the activity selection.

Extended Selective Statistics
Statistical records can be selected according to host types.

Extensions in object naming and storing.

  • The dialog window in which the object name can be entered ("New object", "Rename") now includes the additional text field "Title".
  • Title assignment for folders (object type FOLD). As in all other objects, this title is displayed in the UC4 Explorer's column "Title".
  • Integration of the function "Save as" which can be used to store objects in any folder with a different name (similar to the function "Duplicate"). This function is available through the toolbar of objects.
Several columns in Variable objects
The number of columns in static Variable objects which store values has been changed. Five different values can now be stored per key.
Improved navigation in reports that include several blocks
In the report dialog, you can now directly access the individual pages (blocks) of large reports. Doing so is possible because block numbers are displayed.



Agents

OS/400

Commands
The supplied SAVF file now includes programs and commands that can be used to start or end the Agent in a quick and easy way. The message library can newly be generated by using commands from an IFS path. For further information about the new commands, see KnowledgeBase.

SAP

Improved transfer of spool lists
The following improvements have been made in combination with the XBP interface version 3.0 1.1:

Spool lists are transferred block by block. The block size can be changed in the Connection object (new field "Block size in KB for Spool lists" in the RFC tab - Interfaces - BC-XBP). Doing so increases the performance of the data transfer.

R3_GET_JOB_SPOOL:

  • The parameters FORMAT (not PDF), SPOOLNR and PAGES can now also be used with the standard interface.
  • FORMAT has been extended for the values PDF, BIN and RAW.
  • The spool list can now even be retrieved if the Jobs have already been deleted (setting: "Delete job in CCMS after completion" in the UC4 Job object) and NAME and JOBCOUNT have not been specified.

Documentation

SAP - JCL

Simplified functional differences between UC4 and standard interface
JCL elements including the parameters of the standard interface can also be used with the UC4 Interface. In this context, the table in the Automation Engine Documentation chapter "KnowledgeBase" - UC4 and Target Systems - Automation Engine and SAP - Technical Connection - Functional Differenceshas been simplified. Only script elements are checked whose functions or parameters require the UC4 Interface. The descriptions of the affected R3 script elements (such as R3_ACTIVATE_JOBS) have also been improved.

 


Bug Fixes

 

For detailed and up-to-date information, see the Bug Fixes section in the Automic Download Center.

 


Known Issues

This section contains information about the known issues that have not yet been resolved and, in many cases, also descriptions of workarounds for them.

For detailed and up-to-date information, see the Known Issues & Workarounds section in the Automic Download Center.