RE: IBMi communication logs

Prior to your SFTP job,
Start two TRCCNN, one for the local port, one for the remote port.

Cause . . . . . : Command to execute is: TRCCNN SET(*ON) TRCTYPE(*IP) TRCTBL(FTPIN) SIZE(400 *MB) TCPDTA(*TCP (21?) ()).
Cause . . . . . : Command to execute is: TRCCNN SET(*ON) TRCTYPE(*IP) TRCTBL(FTPOUT) SIZE(400 *MB) TCPDTA(*TCP () (21?)).

After the SFTP job ends,

Cause . . . . . : Command to execute is: TRCCNN SET(*OFF) TRCTBL(FTPIN) CCSID(*ASCII).
Cause . . . . . : Command to execute was: TRCCNN SET(*OFF) TRCTBL(FTPOUT) CCSID(*ASCII).

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Doug Englander
Sent: Wednesday, March 20, 2019 9:02 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: IBMi communication logs



We have an SFTP job that connects to another server in a different state and sends a CSV file. Recently, the job has crashed and received 'Broken Pipe' errors. Does anyone know if there is any FTP or communication log on the system that would let me know why or how that message is getting generated? I am looking to identify the cause, and whether the error originates from our server or the remote server.

Any information would be helpful.

Thank you,

Doug