Automic Workload Automation

Is there a way to use SET_UC_SETTING with the SET_TRACE keyword to turn on tracing for just one process, or for only one type of AE server process (e.g., only work processes but not communication processes)?

Hi Michael

According to the documentation SET_TRACE will only turn on traces on the WPs - see the example:

The second example retrieves the name of the AE system and then activates the TCP/IP trace for its work processes.

:SET &TRC# = GET_UC_SYSTEM_NAME()
:SET_UC_SETTING SET_TRACE, &TRC#, "1000000000000000"       

It's not possible to activate traces on one WP only. If you change the trace flag of one WP it will affect the other WPs.
On the other hand traces should be activated on one CP at a time - again according to the documentation.

What remains unclear so far is if SET_TRACE can be used for CPs.

Hope this helps.

Best regards,
Antoine

Antoine Sauteron said:

What remains unclear so far is if SET_TRACE can be used for CPs.

Had this issue a year or two ago with V10 - it was NOT possible to set a trace on a CP via script. I did not test it in V11.X so far.

hope this helps.

cheers, Wolfgang

PS: this could be a good idea for the ideas.automic.com trashcan

For future reference: I prefer not to post questions because I do not prefer the format. I deliberately chose to post this as a discussion.

Reading my old script to toggle AE server tracing, I discovered that I knew the answer a couple of years ago, but had forgotten.  :D In short, it is possible to use the scripting command to enable or disable tracing on WPs or CPs. The documentation for SET_UC_SETTING is incomplete and potentially confusing though, so I will clarify how it works here.

First, the documentation does not clearly describe how to specify the Component when enabling or disabling tracing. For WPs, it’s all or nothing, so the component specified must be the system name. For CPs, one can enable/disable tracing only on a per-CP basis, so the component specified must the the CP process name.

• All WPs: SET_UC_SETTING SET_TRACE system_nametrace_flags
Example: SET_UC_SETTING SET_TRACE &$SYSTEM# "2400000000000000"

• One CP: SET_UC_SETTING SET_TRACE CP_nametrace_flags
Example: SET_UC_SETTING SET_TRACE AE_DEV#CP001 "2400000000000000"

Second, several new optional parameters added in a recent release are not well documented. These affect only the form of the command that users the SET_TRACE keyword.

I added the examples above, and a suggestion for how to describe the new SET_TRACE parameters, in [DEAD LINK https://community.automic.com/discussion/comment/32103/#Comment_32103]a comment on the documentation page.