I notice that within the ..CA\DSM\SD\asm\library\output folder there is an extremely large number of sub-folders and files. What are they and can they be removed?
search cancel

I notice that within the ..CA\DSM\SD\asm\library\output folder there is an extremely large number of sub-folders and files. What are they and can they be removed?

book

Article ID: 26503

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Software Delivery

Issue/Introduction

I notice that within the ..CA\DSM\SD\asm\library\output folder there is an extremely large number of sub-folders and files.

What are they and can they be removed?

Environment

CA Client Automation - All Versions

Resolution

The files and sub-folders in the ..CA\DSM\SD\asm\library\output folder represent Software Delivery (USD) 'Job output', which can be viewed via Job Target Properties.

The sub-folders and files can be removed but it should be noted that associated Job output will also be lost.

We suggest to use the configuration policies mentioned below to let the Manager to clean the directory.

Removing the sub-folders and files will improve GUI performance as the API instance will not have to cache so many files.

The Job Output files are kept for the time the jobs are kept on the Jobs folder for each Agent and this is controlled by the configuration parameters under the configuration policy folder DSM > Software Delivery > Manager:

 

Maintenance: Job history cleanup time

Identifies the number of hours a job that has executed will be displayed in the Computer - Jobs folder.

The default is 4320 hours (180 days). Note: After the time expires, neither installation jobs, if they refer to software that is still installed, nor delivery jobs, that refer to software still present in a Scalability Server library, are deleted.

 

Maintenance: Job history output file cleanup time

This is the number of days that a job output file is maintained. Default is zero which means it will be maintained until the actual job is removed or in the case of an install or delivery record never removed. Note that the file will not be considered for removal until the actual job is about to be considered for clean up (see Maintenance: Job history cleanup time)

 

Maintenance: Job history output file remove limit

This limits the number of output files removed during one clean up. Default is zero which means no limit.