Search for Usage limitation

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
N/A

Search for usage has a limit of 1000 results, even when the limit is set to 5000.

If the value for SEARCH_SCRIPT_FOR_USAGE is set to "L" you get a maximum of 1000 object.  This is true if GENERIC_SEARCH_LIMIT is set to a default value of 5000 as well. 

This happens if you are searching for objects ans if you use the option Usage of objects / include scripts.

If you change the value for SEARCH_SCRIPT_FOR_USAGE to ‘Y’, no object will be found if  the search option include scripts is activated.
After deactivating this option you need to use wildcards to find objects.

Investigation

1. Create a script object SCRI.ASP.CALL.VARA.EXEC

Content:

<Please see attached file for image>

1. Create the reference object SCRI.ASP.INC00121246
2. Use substring “ASP.INC00121246” for testing purposes

Test Case 1

There are 512 objects where the ‘Teilwort‘ ”ASP.INC00121246” is somewhere in the script:

The parameter SEARCH_SCRIPT_FOR_USAGE in variable UC_CLIENT_SETTINGS is set to ‘L’.

 

<Please see attached file for image>

Results

Actual:  All 512 objects are found.
Expected:  All 512 objects are found.

<Please see attached file for image>

Test Case 2

Duplicate those 512 objects (now there are 1024 objects):

The parameter SEARCH_SCRIPT_FOR_USAGE in variable UC_CLIENT_SETTINGS is set to ‘L’.

<Please see attached file for image>

Results

Actual:  Just 1000 objects are found.
Expected:  There should be 1024 objects found.

Environment

OS Version: N/A

Cause

Cause type:
By design
Root Cause: This behavior is intended. If a search for usage with "Like" in Scripts the search result is limited to 1000 entries due to potentially causing performance issues.

Resolution

This behavior is intended. If a search is performed using Like within Scripts, the search results are limited to 1000 entries to prevent the possibility of causing performance issues due to returning a high number of results that may impact the system.

Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A