Inconsistent behavior of PREP_PROCESS_FILE related to the using of Login objects.

Products

• CA Automic One Automation

Issue/Introduction

An inconsistent changes in the behavior of the script function PREP_PROCESS_FILE has been reported in version 21.0.

:set &HOST#=GET_ATT(HOST)
:set &LOGIN#=GET_ATT(LOGIN)
:set &PROC#=PREP_PROCESS_FILE(&HOST#, "<.......>\Agent/Linux/bin/./ucxjlx6.ini", , , , "UC_LOGIN=LOGIN.UNIX")
:process &PROC#
:  set &line#=GET_PROCESS_LINE(&PROC#)
:  print &line#
:endprocess
:CLOSE_PROCESS &PROC#
:p "**************************************************************************************************************"
:set &HOST#=GET_ATT(HOST)
:set &LOGIN#=GET_ATT(LOGIN)
:set &PROC1#=PREP_PROCESS_FILE(&HOST#, "<.......>/Agent/Linux/bin/./ucxjlx6.ini", , , ,)
! ls -lrt /usr/local/uc4_21/Agent/Linux/bin
:process &PROC1#
:  set &line#=GET_PROCESS_LINE(&PROC1#)
! : P Hello
:  print &line#
:endprocess
:CLOSE_PROCESS &PROC1#

 

The jog ends in 21.0.8 successfully with the status ENDED_OK whereas it shout not run and ends with final status FAULT_OTHER and the following message:

 
U00016005 Runtime error in object 'JOBS.UNIX.TESTJOB', line '00018': PREP_PROCESS_FILE without login is not permitted because ANONYMOUS_FT=NO.

Environment

One Automation system 21.0.8 (detected) 

Cause

This is a defect of the Automation Engine 21.0.

Resolution

Resolution Description : A bug was fixed in PREP_PROCESS_FILE where the previously used login was used on calls that didn't specify a LOGIN object.

This bug is fixed in version 21.0.10 (expected around April 2024)

Additional Information

Bug ID : AE-34585
Bug Title : Change in behavior of PREP_PROCESS_FILE blocking the PROD upgrade

 

Please note, that the currently observed behavior was how it worked in version 12.3. In version 21.0 Product Management and Development Team decided to change the way PREP_PROCESS_FILE works. The correction introduced in 21.0.10 reflects what PREP_PROCESS_FILE is expected to do in version 21. This is why the initial case was raised by customer after they updated from 12.3 to 21.0.