Troubleshooting U02000082 - The Agent-Routine 'UCFTXEX' needs xx Seconds for Message FTX
search cancel

Troubleshooting U02000082 - The Agent-Routine 'UCFTXEX' needs xx Seconds for Message FTX

book

Article ID: 263005

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

During some transfers between a Linux and a MVS Agent, we find these kind of messages:

U02000082 Die Agent-Routine 'UCFTXEX' benoetigt '37' Sekunden fuer die Verarbeitung der Meldung 'FTXREPG', RunID 'XXXXXXXXX'.
U02000082 Die Agent-Routine 'UCFTXEX' benoetigt '37' Sekunden fuer die Verarbeitung der Meldung 'FTXDATA', RunID 'XXXXXXXXX'.
U02000082 Die Agent-Routine 'UCFTXEX' benoetigt '57' Sekunden fuer die Verarbeitung der Meldung 'FTXDATA', RunID 'XXXXXXXXX'.
U02000082 Die Agent-Routine 'UCFTXEX' benoetigt '71' Sekunden fuer die Verarbeitung der Meldung 'FTXDATA', RunID 'XXXXXXXXX'.
U02000082 Die Agent-Routine 'UCFTXEX' benoetigt '20' Sekunden fuer die Verarbeitung der Meldung 'FTXQUIT', RunID 'XXXXXXXXX'.
U02000082 Die Agent-Routine 'UCFTXEX' benoetigt '20' Sekunden fuer die Verarbeitung der Meldung 'FTXENDQ', RunID 'XXXXXXXXX'.
U02000082 Die Agent-Routine 'UCFTXEX' benoetigt '20' Sekunden fuer die Verarbeitung der Meldung 'FTXRECVQ', RuD 'XXXXXXXXX'.

We faced the difficulty, that an FTP from Linux Agent (in DMZ) to MVS Agent stalled while other FTPs needed four times longer to finish than usually.

When we cancel stalling FTP in the morning and retry, it works immediately.

So we are wondering if there is any bottleneck or delay, but up to now we did not succeed in finding a reason.

Currently we  assume that Index Maintenance on MSSQL-DB could be the reason.

Can you please tell us, what the exact meaning of U02000082 is?

Is there any configuration that can be adjusted in order to prevent this bottleneck/delay?

Environment

Release : 12.x and 21.x

Component: Automation Engine

Sub-Component: Agents

Resolution

U02000082 is a common message in all Agents. If processing of a specific internal message (in this case FTXDATA, file transfer data package) takes more than 10 seconds, it is going to be written in agent log.

Most typical causes are that the Filesystem was not ready to open a specific file, or Dataset was migrated and Agent has been stopped until it was recovered or this might be caused by the Database Index maintenance.

Additional Information

If more analysis needs to be done, the involved Agents should have its trace level set to:

tcpip=2
ft=2
memory=1

In case of new occurrence, force the dump of the traces with "Reset Trace Flags" as below:

Then open a case with Technical Support with the logs and traces of the two Agents impacted.