File Transfer (JOBF) from z/OS Agent to Windows Agent stuck in status Connecting
Error Message :
U00011409 FT '': FileTransfer ended abnormally.
A simple File Transfer (JOBF) from a z/OS Agent to Windows Agent gets stuck in a status of Connecting (1546).
Its Report indicates that the transfer has failed as seen in the error message above.
Note:
- A File Transfer in the opposite direction (from Windows to z/OS), with the same Agents, works fine.
- A File Transfer from z/OS Agent to another platform works fine as well.
A Linux Agent as destination is confirmed to work.
Example:
<Please see attached file for image>
Job Report:
Agent Log:
20171121/090548.981 - U02000134 Thread '*FT(4585178)' started.
invalid kennzeichen ' ' at 58
message 121B0F94 107
--------------------------------------------
0000 121B0F94 30303030 30313037 5543343A 676C6F62 .............%?.
0010 121B0FA4 616C3030 314E4154 20202020 20202020 /%...+..........
0020 121B0FB4 20202020 20202020 20202020 20202020 ................
0030 121B0FC4 01085543 46545845 58200308 56574753 ................
0040 121B0FD4 55503132 FE240046 54585245 43565130 .&..............
0050 121B0FE4 310500AA FB1000DA F6450059 00010000 ........6.......
0060 121B0FF4 00000000 00000000 000000 ...........
20171121/091049.000 - The address '' was not found
20171121/091049.002 - U02000135 Thread '*FT(4585178)' ended.
20171121/091050.014 - U02000007 Connection to Agent 'VWGSUP12(4,ID=9)' terminated.
Cause type:
Defect
Root Cause: The file transfer from z/OS to Windows fails. The z/OS agent receives an invalid key in a logical message from the Windows partner during file transfer initiation. The task remains in a connection status.
OS Version: N/A
Update to a fix version listed below or a newer version if available.
The fix allows the z/OS agent to handle/ignore key 0x03, and accept and process the rest of the message as usual so that the file transfer continues.
Fix Status: Released
Fix Version(s):
Component(s): Agent MVS
Automation Engine 12.1.1 - Available
Automation Engine 12.0.4 - Available
Workaround :
N/A