Several issues occur when launching a JOBF transfer from a Windows Agent to a MVS Agent 12.3 that fails when trying to connect Windows to MVS as the traffic is not closed.
1. When Reverse File Transfer is performed by the MVS Agent to request the file to the Windows Agent, the JOBF fails with the following kind of error in the Windows Agent Log:
U01002409 Message size is exceeded '131943' > '2473', module 'FTXSEND.FTXSNDRCV.dst_code'.
2. In the JOBF Report there is a reference to a wrong Runid that does not correspond with the current FT.
2020-05-20 16:00:13 - U02000063 Connection to Agent 'REMOTE_AGENT' with connection data 'IP:PORT' not possible. Error code '10061', error description: 'No connection could be made because the target machine actively refused it.'.
2020-05-20 16:00:14 - U00011409 FT '2147479552': File Transfer has ended abnormally.
3. If traces in the Windows Agent are increased to a higher level than ft=2, tcpip=2, the Windows agent crashes.
This is a problem of the MVS Agent.
When performing FTs with reverse connect, the z/OS Agent does not turn the 'FTXRECV.src_code_dist' and 'FTXRECV.src_code_len' integer fields to little endian.
As a result, the Windows Agent receives wrong length and distance numbers in the protocol.
Release : 12.3
Component : AUTOMATION ENGINE
Subcomponent: Agent z/OS
Workaround 1: use an intermediary Windows agent to transfer the files where the traffic is directly opened towards the MVS agent
Workaround 2: downgrade MVS agent to 12.0
Update to a fix version listed below or a newer version if available.
Automation.Engine 12.2.8 - Planned release in February 2021
Automation.Engine 12.3.5 - Planned release in March 2021