BS2000 File Transfer to UNIX Loops and Floods MQWP Table.

Products

• CA Automic Workload Automation - Automation Engine
• Automic SaaS

Issue/Introduction

A File Transfer (JOBF) from a BS2000 Agent to a UNIX Agent hangs in the Transferring state. During this time, the following symptoms occur:

• The Automation Engine's MQWP table fills rapidly with millions of entries (up to 8 million recorded in some cases).
• The Automation Engine system eventually crashes or becomes unresponsive due to database resource exhaustion.
• The WP logs repeatedly show the following message in a loop: U00011019 '[HOSTNAME]' meldet File Transfer-Status 'F'
• The UNIX Agent or TLS Gateway logs may show a WebSocket connection drop with status 1005 (Broken pipe).

Environment

• Automation Engine: 24.4.4
• BS2000 Agent: 21.0.12 or 24.x
• UNIX Agent: 24.4.4 (utilizing TLS Gateway and WebSocket architecture)

Cause

This behavior is caused by a product defect tracked as DE194844.

When the UNIX Agent or TLS Gateway hits a WebSocket defect that drops the connection abruptly (Status 1005), the sending BS2000 Agent does not receive a proper confirmation of the drop. Consequently, the BS2000 Agent enters a blind loop attempting to send the FTXENDQ (File Transfer End) message. The Automation Engine improperly handles these repeated messages, continuously generating entries in the MQWP table until the system crashes.

Resolution

A fix for this defect is scheduled to be included in the following releases:

• Automation Engine 24.4.5 -TBA
• Automation Engine 26.1.0 - TBA

Workaround

1. Manual Cancellation: If a File Transfer is identified as hanging in the 'Transferring' state, manually cancel the JOBF immediately to prevent the MQWP table from flooding.
2. Agent Restart: Restart the BS2000 Agent that is reporting the repeated status messages. This will break the blind loop and stop the message flood to the Automation Engine.
3. Monitor MQWP: Database administrators can monitor the MQWP table size. If the table grows abnormally large, identify the offending JOBF RunID from the WP logs and terminate the process.