PREP_PROCESS fails with ANONYMOUS_FT=N
search cancel

PREP_PROCESS fails with ANONYMOUS_FT=N

book

Article ID: 426873

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

PREP_PROCESS fails with ANONYMOUS_FT=N and Login without Password

After upgrading an Agent from 12.3 to 24.4.1HF2, we encountered an issue where the function PREP_PROCESS no longer works under the following conditions:

  • The parameter ANONYMOUS_FT=N is set in UC_HOSTCHAR_DEFAULT.

  • The Login object used contains only a user name, but no password.

With version 12.3 (and earlier) this configuration worked correctly and PREP_PROCESS executed as expected.

The following messages are shown in the Message window (read bottom to top):

12/1/2025 02:56:15 PM        U00010038 Runtime error: Could not create data sequence 'FILETRANSFER'. Status: '0000001820', return code: '0000000000'.
12/1/2025 02:56:15 PM        U00029003 Cannot open file 'EAACFDFU.TXT', error code 'n/a', error description: 'java.io.IOException javax.security.auth.login.LoginException: User or password is invalid.'.
12/1/2025 02:56:15 PM        U00011000 'REPORT' (RunID: '0001004012') could not be started on 'UNIX01'. See next message.
12/1/2025 02:56:15 PM        U00011002 Job 'EVENT.UNIXCMD' (RunID '0001004011') on Host 'UNIX01' ended normally. Remote ID=30380

 Expected behavior: PREP_PROCESS should work in 24.4.1HF2 in the same way as in 12.3, even if the Login object does not contain a password, provided that ANONYMOUS_FT=N is set.

The transfer of the Event report is expected work with ANONYMOUS_JOB=Y . The setting ANONYMOUS_FT=Y should not affect this.

Cause

DE175829

Resolution

Solution:

Update to a fix version listed below or a newer version if available.


Fix version:

Component(s): Automation Engine

Automation.Engine 24.4.3 HF1 - Available

Additional Information

A problem has been fixed where, in case of loading reports resulting from the execution of PREP_PROCESS, the ANONYMOUS_JOB setting was disregarded and a full login check was erroneously required.