Automic Workload Automation

Automation Engine version 11.2.2 is now available for download from downloads.automic.com.

• AE 11.2.2 downloads
• AE 11.2.2 patch descriptions
• AE 11.2.2 documentation
  

Because the release notes lack a complete list of fixes, I have compiled a complete list of fixes in an Excel spreadsheet (as I did with 11.2.1).

For the fixlist my Infra colleagues introduced the Upgrade checker

select component, current version and version upgrading to and it provides a List of Bugfixes and changes:
https://downloads.automic.com/tools/upgrade_checker


https://us.v-cdn.net/5019921/uploads/editor/oj/iio5azt49g29.png" width="1131">

Wolfgang Brueckler said:

For the fixlist my Infra colleagues introduced the Upgrade checker

select component, current version and version upgrading to and it provides a List of Bugfixes and changes:
https://downloads.automic.com/tools/upgrade_checker

I have had mixed results using the upgrade checker.

• If you click the link and are not logged in, the site redirects you to the main log in page. After you have logged in, you are not taken to theupgrade checker, but to the maindownloadspage. You must log in, and then either click the link again or chooseUpgrade Checkerfrom theTools menu. When one visits the downloads site via a link to the upgrade checker, it would obviously be preferable to be taken directly to the desired page automatically after logging in. The fact that the session time-out for the downloads site is less than an hour exacerbates this annoyance.
  
• The upgrade checker lists too many fixes. E.g., I selected:
• Component: Automation Engine
• Sub-Component: (all 59 cub-components)
  
• currently installed version:11.2.1 HF1
• version to upgrade to:11.2.2
With these criteria entered, the upgrade checker lists 622 fixes, including:
• 214 fixes introduced in 11.2.0
• 181 fixes introduced in 11.2.1
• 150 fixes new in 11.2.2
On Saturday, the list of11.2.2 patch descriptionsincluded 158 fixes (See the Excel spreadsheet). This morning the same link lists 152 fixes

Is this(11.2.2) the newest update, or is there another, newer one (11.2.3 as stated at the automic-Homepage https://automic.force.com/support/apex/CommunityNewsDetail?id=a1tb0000000wuOTAAY)?

Nicolai Strelow said:

Is this(11.2.2) the newest update, or is there another, newer one (11.2.3 as stated at the automic-Homepage https://automic.force.com/support/apex/CommunityNewsDetail?id=a1tb0000000wuOTAAY)?

Automation Engine 11.2.2 was released a few days ago, and 11.2.3 will be released in several months.

At first, I assumed that the version number mentioned on the webpage you linked to was a typo.

Upon further consideration however, I fear the confusing numbering might actually be intentional, and that Automic Workload Automation 11.2.3 is the name of the suite of products that includes Automation Engine 11.2.2. This is a manifestation, no doubt, of some technical limitation in the chosen version control & release management system.

NStrelow it is all about 11.2.2.
 The version 11.2.3 mentionned on the webpage is for AWA and AE 11.2.2 is one of its components.

Octavie

is not fixed . We have the same problem with UNIX agents V11.2.2 build 622.

Thomas Berreis wrote:

PRB00113188 is not fixed . We have the same problem with UNIX agents V11.2.2 build 622.

Just out of curiosity, is ANONYMOUS_FT set to Y or N? If it is set to N, you might try again with it set to Y.

The error occurs with both options:

- Agent V11.2.X
- ANONYMOUS_FE and ANONYMOUS_FT set to Y
> Pre-Condition 'CHECK FILE' produces a U02000102: Error by check directory '13(Permission denied)'
'EXIT' in 'XC_INC.CONDITION.CHECK_FILE' , line '00086' ...

- Agent V11.2.X
- ANONYMOUS_FE and ANONYMOUS_FT set to N
> Pre-Condition 'CHECK FILE' produces a U02000102: Error by check directory '13(Permission denied)'
'EXIT' in 'XC_INC.CONDITION.CHECK_FILE' , line '00086' ...

- Agent V10.0.8
- ANONYMOUS_FE and ANONYMOUS_FT set to Y
> Pre-Condition 'CHECK FILE' works properly

- Agent V10.0.8
- ANONYMOUS_FE and ANONYMOUS_FT set to N
> Pre-Condition 'CHECK FILE' works properly

Hello
We have been upgrading our agents from V.9.8.A to 11.2.0 build 2347, and we have experienced a similar error.
During testing, I've noticed that when the filename contains the * wildcard, the condition worked fine, but it fails if I use a fixed filename.

-FIXED FILENAME
2016-07-06 10:48:39 - IF file '/filemanager/prueba.sh1' exists (check via *OWN).
2016-07-06 10:48:40 - U02000102 Error when calling the function 'lstat', error code '2(No such file or directory)'.

-WILDCARD
2016-07-06 12:43:43 - IF file '/filemanager/prueba*.sh1' exists (check via *OWN).
2016-07-06 12:43:44 -    False: Found 0 file(s).
2016-07-06 12:43:44 - FINALLY skip task with message '<TEXT>'

 

... I've noticed that when the filename contains the * wildcard, the condition worked fine, but it fails if I use a fixed filename.

-FIXED FILENAME
2016-07-06 10:48:39 - IF file '/filemanager/prueba.sh1' exists (check via *OWN).
2016-07-06 10:48:40 - U02000102 Error when calling the function 'lstat', error code '2(No such file or directory)'.

I could not reproduce this problem. File checks in preconditions work fine for me.

2016-07-21 12:08:11 - IF file '/tmp/testfile1.txt' exists (check via *OWN).
2016-07-21 12:08:12 -    False: Found 0 file(s).
2016-07-21 12:08:12 - THEN redo evaluation in 1 minutes
2016-07-21 12:09:27 - IF file '/tmp/testfile1.txt' exists (check via *OWN).
2016-07-21 12:09:27 -    True: Found 1 file(s).
2016-07-21 12:09:27 - THEN set object variable FILE_FOUND# to TRUE in scope Workflow
2016-07-21 12:09:27 - FINALLY run task

The agent is 11.2.2+build.622 (x64) on SLES 3.0.101-68-default.

Are you running the agent as the root user?