Files are left in the run directory when running FILESIZE

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When running FILESIZE on a file that is not owned by the Applications Manager OS user and the file's Group is not the same Group of the OS user, the file is registered, but a copy of the file is copied to the $AW_HOME/run directory.

This file is not managed and is left in the run directory causing a build of leftover files in the directory.

Resolution

FILESIZE does not move a copy of the registered file into the $AW_HOME/run directory. Instead, part of the FILESIZE script runs a cd into the run directory making the present working directory (pwd) the run directory. 

Below is the relevant snippet of code from the FILESIZE script:

    if [ "$SO_GRP" != "$grp_file" ]; then
        echo "file $file_in group of $grp_file"
        cp $file_in $OUTPUT/$file
        cd $SQLOPER_HOME/run
        file=$OUTPUT/$file
        export file
        err=$?

If the custom Job script includes any code that moves the registered file into the present working directory, that present working directory will be the run directory.

Keeping in mind that the shell's current directory is the run directory after the above code, modify the Job script accordingly so files are not mistakenly moved into the incorrect directory.