Setting up Rolling Traces
search cancel

Setting up Rolling Traces

book

Article ID: 89541

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

Setting up Rolling Traces

Environment

Release: 12.x 21.x

Product: Automic Workload Automation

Resolution

Detailed Description and Symptoms:

Trace files can become quite large when left on for a long period of time. Setting a Rolling Trace from an Event will make those files more manageable.

Solution: Rolling Traces via Event

These will roll traces over every x minutes. The upper part is for an executor, lower is for WPs and/or CPs.

The following are the instructions to turn on a rolling trace via a time event:

  • In the Time Event tab (called Event tab in some older versions) of the Time Event, be sure that Repeated is set and set your "Check in intervals of" to the correct amount of time.

In the Process tab, put the following; this will turn the trace on when the event is activated:

Agent:

!Set a TCP/IP=9 trace on the Agent - <Agent Name> needs to change to reflect actual executor

!Turn on tracing

:SET_UC_SETTING SET_TRACE, "<Agent Name>", "9000000000000000"

WP/CP:

 

!Set a DB=4 and TCP/IP=2 trace on the WPs

!Get System Name

:SET &TRC# = GET_UC_SYSTEM_NAME()

!Turn on tracing for WPs

:SET_UC_SETTING SET_TRACE, &TRC#, "2400000000000000"

!Turn on tracing for single CP - Before # sign is the System name, after # sign is CPxxx where xxx is the CP number

:SET_UC_SETTING SET_TRACE, "<SYSTEM>#<CPXXX>", "2400000000000000"

In the Process Event tab (called !Process in some older versions), put the following; this will turn the traces repeatedly every x minutes where x is the amount of time you specified in the Event tab:

Agent:

!Turn off tracing

:SET_UC_SETTING SET_TRACE, "<Agent Name>", "0000000000000000"

!Turn on tracing

:SET_UC_SETTING SET_TRACE, "<Agent Name>", "9000000000000000"

WP/CP:

!Get System Name

:SET &TRC# = GET_UC_SYSTEM_NAME()

!Turn off tracing on WPs

:SET_UC_SETTING SET_TRACE, &TRC#, "0000000000000000"

!Turn off tracing on single CP

:SET_UC_SETTING SET_TRACE, "<SYSTEM>#<CPXXX>", "0000000000000000"

!Turn on tracing for WPs

:SET_UC_SETTING SET_TRACE, &TRC#, "2400000000000000"

!Turn on tracing for single CP - Before # sign is the System name, after # sign is CPxxx where xxx is the CP number

:SET_UC_SETTING SET_TRACE, "<SYSTEM>#<CPXXX>", "2400000000000000"

Start your event when necessary and the traces will roll over. This helps maximize the amount of tracing while minimizing the amount of hard drive space necessary.