CHASE writes a lot of messages in the as_server.$AUTOSERV file

Products

• CA Workload Automation AE

Issue/Introduction

We routinely see 'chase' clogging up a large portion of our as_server logs, and I'm wondering if this is being caused by mutually exclusive instances of the command being issued, or if it's the byproduct of a single command performing its normal work.  For example, here is a tiny segment of an as_server log from yesterday, all lines from the same hour/minute/second:

[03/06/2022 17:13:41.7790] CAUAJM_I_30032 Client [CA WAAE Chase:30697][13][<host>:<port>:<ip>] [0x80ab960][03/06/2022 17:13:41.7747][0:autosys@host123<@host123> 0] API ID [3] execution completed. Total time: 0.002 seconds.
[03/06/2022 17:13:41.7871] CAUAJM_I_30032 Client [CA WAAE Chase:30697][13][<host>:<port>:<ip>] [0x80addd0][03/06/2022 17:13:41.7789][0:autosys@host123<@host123> 0] API ID [87] execution completed. Total time: 0.006 seconds.
[03/06/2022 17:13:41.7911] CAUAJM_I_30032 Client [CA WAAE Chase:30697][13][<host>:<port>:<ip>] [0x80ab960][03/06/2022 17:13:41.7870][0:autosys@host123<@host123> 0] API ID [3] execution completed. Total time: 0.002 seconds.

Does 'chase' write a separate line in as_server for each job in either STARTING or RUNNING state?  Also, what is the difference between API ID [87] and [3]?

Environment

Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)

Resolution

For each job there will be a pair of [3] and [87] completed messages.
Along with a set of additional [37],[39],[69] upfront at the start of chase and then an ending [3],[132] as chase completes.

You will see more rows of logged messages if you have more jobs chase is checking for you.