Transferring Data to Cogito
Posted by Clive Petley on 14/06/17 @ 4:37 PM

Transferring Files/Datasets to Cogito/Syncsort

Cogito/Syncsort provides users access to a high speed FTP server, for transferring diagnostic files/data etc.

The EZ-DB2 suite of products can automatically generate JCL to package and transfer support/debugging data to our FTP server, but you can easily create standard mainframe batch JCL using the FTP server/account details below.

The base FTP details are:


Customers should upload using the following acount:

Userid:      ftpcogito-client
Password:    Coin-Laughter88
Directory:   /Upload

Using this account, you can upload files to us, but you are prevented from being able to see or read any files from the server.

The FTP server supports FTP (port 21) and SFTP (port 22). If you wish to use SFTP to encrypt transfer from the mainframe, you will need to discuss the required mainframe JCL with your security/network teams, as SFTP requires an appropriate SSH layer of mainframe software.

It is often useful to use TRSMAIN to compress the mainframe files(s) first, before transferring them to us - the EZ-DB2 panels that include FTP options, always compress the data first. Note that if you are sending us Variable Blocked data, this MUST always be compressed using TRSMAIN before transferring the file, otherwise it is impossible to reload the data at our end.

Firewalls & Alternative Transfer Options

Depending on your local firewall settings, you may or may not be able to access the above server directly from within you corporate environment.

In many cases, you may be able to access the FTP server directly from your PC/Workstation, but not directly from the mainframe. If the connection/logon to the FTP server times out, then it is almost certainly due to a local firewall.

While it is always preferable to transfer files directly from the mainframe, if that is not possible, then you can often download the mainframe file to your local PC, then transfer it to our server from your PC. When downloading locally, you should always download as binary, to ensure we can successfully reload the data to our mainframe.

Use the above FTP server/logon details to transfer the files from your PC to us, using an appropriate FTP client application. If you do not have a suitable FTP client, or you are blocked from accessing our FTP server from your PC, then you can try to transfer the files via the web interface option – this uses a web connection rather than native FTP and will often be allowed on corporate networks where FTP fails.

To use the web interface, go to and logon using the above client account. 

Note, if you use the web interface, please ensure that any file has a relevant file extension – this is to ensure the file is transferred in the correct format. You can zip the file, so that it has a file extension .zip. Otherwise, for binary files, set the file extension to .bin and for ASCII set the file extension to .txt.

A final mechanism for sending data to us, is to create a ticket on the Cogito support portal ( and attach the PC file to the ticket. You should limit attachments to a maximum size of 6 megabytes.


You should always transfer mainframe files as binary. Please do not zip - always use TRSMAIN on the mainframe to compress the data first. 

For EZ-DB2 customers, option 9.4 will compress an entire Workload for you, Option 9.12 will compress a single dataset, or member of a dataset. When sending job output first print it to a dataset and then use Option 9.12.

The compressed mainframe file should then be transferred to us using the preferred order below:

  1. FTP directly from mainframe to us - use TRSMAIN to compress first if possible.
  2. Download as binary to your local PC then FTP to our server using a PC based FTP client.
  3. Download as binary to your local PC then upload to our server using the Web Interface option - ensure the file has an appropriate file extension (.bin .txt, .zip etc).
  4. Download as binary to your local PC then attach to a support ticket on the portal (max size 6MB) -
  5. Download as binary to your local PC then attach to an email to