File Transfer Protocol Scripted Batch Processes using FTP

Introduction

This document describes how to use the File Transfer Protocol (FTP) with a Scripted Batch Process to transfer data files of various formats and content. This includes data files with fixed or varable length records.

We have made a significant effort to ensure the documents and software technologies are correct and accurate. We reserve the right to make changes without notice at any time. The function delivered in this version is based upon the enhancement requests from a specific group of users. The intent is to provide changes as the need arises and in a timeframe that is dependent upon the availability of resources.

Copyright © 1987-2024
SimoTime Technologies and Services
All Rights Reserved

Binary Transfers, FTP for Windows

The default file transfer mode for FTP is ASCII and this works very well in a distributed environment with ASCII/Text Files. When an IBM Mainframe System is involved in the transfer process with a distributed System (Linux, UNIX or Windows) it is the exception when data files contain all text characters. In addition, most Linux, UNIX and Windows systems use ASCII-encoding and an IBM Mainframe System uses EBCDIC-encoding.

Note:  The preceding file structures and field formats are supported on a Linux, UNIX or Windows System using Micro Focus Enterprises Server technologies.

Fixed Record Size, ZOS to Windows

This section will described how to copy and convert a Mainframe, EBCDIC-encoded sequential file with fixed length records to a Micro Focus, ASCII-encoded sequential file with fixed length records. The following shows the content of a control file (ASCII/Text format) that contains a sample FTP script from a client requesting to transfer a file with fixed length records from the Mainframe server to a Windows client. The record structure of the control file is an ASCII/Text format.

userid
Password
CD ..
PWD
BINARY
GET  DATA.SET.NAME  d:\dirname\dirname\filename.ext
QUIT

The 1st parameter of the GET statement is the MVS Data Set Name. The 2nd parameter is the fully-qualified PC File name.

The following is the command line syntax to run the FTP program and use the preceding script file (or control file) to download a file with fixed length records. The file will be downloaded in BINARY mode.

C:\>FTP -v -s:c:\SimoDemo\TestLib1\FTPFIXED.SCR nn.nn.nn.nn

Note: The -v suppresses the display of remote server responses. The -s: is followed by the name of the Control (or script) file. The last parameter is the host identifier (a host name or TCP/IP address).

Variable Record Sizes, ZOS to Windows

This section will described how to copy and convert a Mainframe, EBCDIC-encoded sequential file with variable length records to a Micro Focus, ASCII-encoded sequential file with variable length records. It is important to note that the RDW used on the Mainframe is a different structure than the RDW format used with Micro Focus.

FTP may be used to transfer a file with variable length records. Because the RDW information is stored in a binary format it will be necessary to use BINARY mode with FTP. This is usually not a problem since most mainframe files contained packed or binary information anyway. In order to get the RDW information some additional commands (or statements) will be required in the FTP script or process. The following shows the content of a control file (ASCII/Text format) that contains a sample FTP script from a client requesting to transfer a file with variable length records from the Mainframe server to a Windows client. The record structure of the control file is an ASCII/Text format.

userid
Password
CD ..
PWD
BINARY
LITERAL SITE RDW
GET  SIMOTIME.DATA.ZDDVBE01  C:\MFI01\FTPLIB01\ZDDVBE01.DAT
QUIT

The 1st parameter of the GET statement is the MVS Data Set Name. The 2nd parameter is the fully-qualified PC File name.

The following is the command line syntax to run the FTP program and use the preceding script file (or control file) to download a file with variable length records. The file will be downloaded in BINARY mode.

C:\>FTP -v -s:c:\SimoDemo\TestLib1\FTPVARYS.SCR nn.nn.nn.nn

Note: The -v suppresses the display of remote server responses. The -s: is followed by the name of the Control (or script) file. The last parameter is the host identifier (a host name or TCP/IP address).

Once a variable length file is transferred using the preceding example it will be a mirror image of the file on the mainframe. Therefore, it is not in a Micro Focus File Format and cannot be accessed by a Micro Focus COBOL program using the standard SELECT and FD file definitions. This file must be converted from a mainframe file format to a Micro Focus file format. This is accomplished by using a Byte-Stream I/O program written in Micro Focus COBOL.

Binary Transfer, Mainframe FTP

This section will described how to copy and convert a Mainframe, EBCDIC-encoded sequential file with variable length records to a Micro Focus, ASCII-encoded sequential file with variable length records. It is important to note that the RDW used on the Mainframe is a different structure than the RDW format used with Micro Focus.

FTP may be used to transfer a file with variable length records. Because the RDW information is stored in a binary format it will be necessary to use BINARY mode with FTP. This is usually not a problem since most mainframe files contained packed or binary information anyway. In order to get the RDW information some additional commands (or statements) will be required in the FTP script or process. The following shows the content of a control file (or FTP script) that that is used at the host to transfer a file with variable length records from the Mainframe server to a Windows client. The record structure of the control file is a sequential file and may be a PDS member.

Once a variable length file is transferred using the preceding example it will be a mirror image of the file on the mainframe. Therefore, it is not in a Micro Focus File Format and cannot be accessed by a Micro Focus COBOL program using the standard SELECT and FD file definitions. This file must be converted from a mainframe file format to a Micro Focus file format. This is accomplished by using a Byte-Stream I/O program written in Micro Focus COBOL.

FTP Script, Variable-Length Records

The following shows the content of a control or parameter file containing an FTP script.

userid
Password
CD ..
PWD
BINARY
LOCSITE RDW
PUT  SIMOTIME.DATA.ZDDVBE01  C:\MFI01\FTPLIB01\ZDDVBE01.DAT
QUIT

The 1st parameter of the PUT statement is the MVS Data Set Name. The 2nd parameter is the fully-qualified PC File name.

JCL Member, a Separate FTP Script

The following (FTPSAMJ1.jcl) is an example of a JCL Member that uses the preceding FTP script.

//FTPSAMJ1 JOB SIMOTIME,ACCOUNT,CLASS=1,MSGCLASS=0,NOTIFY=CSIP1
//* *******************************************************************
//*      This JCL Member is provided by: SimoTime Technologies        *
//*           (C) Copyright 1987-2019 All Rights Reserved             *
//*             Web Site URL:   http://www.simotime.com               *
//*                   e-mail:   helpdesk@simotime.com                 *
//* *******************************************************************
//*//STEPFTP1 EXEC PGM=FTP,REGION=8M,PARM='simotime.com'
//STEPLIB  DD  DSN=As per shop standards and guidelines
//SYSTCPD  DD  DSN=As per shop standards and guidelines
//SYSFTPD  DD  DSN=As per shop standards and guidelines
//SYSPRINT DD  SYSOUT=*
//SYSUDUMP DD  SYSOUT=*
//OUTPUT   DD  SYSOUT=*
//INPUT    DD  DSN=SIMOTIME.PDS.PARMLIB(FTPSAMS1),DISP=SHR
//

JCL Member, an In-Stream FTP Script

The following (FTPSAMJ2.jcl) is an example of a JCL Member that uses in-stream FTP commands.

//FTPSAMJ2 JOB SIMOTIME,ACCOUNT,CLASS=1,MSGCLASS=0,NOTIFY=CSIP1
//* *******************************************************************
//*       This JCL Member is provided by: SimoTime Technologies       *
//*           (C) Copyright 1987-2019 All Rights Reserved             *
//*             Web Site URL:   http://www.simotime.com               *
//*                   e-mail:   helpdesk@simotime.com                 *
//* *******************************************************************
//*//STEPFTP1 EXEC PGM=FTP,REGION=8M,PARM='simotime.com'
//STEPLIB  DD  DSN=As per shop standards and guidelines
//SYSTCPD  DD  DSN=As per shop standards and guidelines
//SYSFTPD  DD  DSN=As per shop standards and guidelines
//SYSPRINT DD  SYSOUT=*
//SYSUDUMP DD  SYSOUT=*
//OUTPUT   DD  SYSOUT=*
//INPUT    DD  *
userid
Password
CD ..
PWD
BINARY
LOCSITE RDW
PUT  SIMOTIME.DATA.ZDDVBE01  C:\MFI01\FTPLIB01\ZDDVBE01.DAT
QUIT

The 1st parameter of the PUT statement is the MVS Data Set Name. The 2nd parameter is the fully-qualified PC File name.

Summary

The purpose of this document is to provide a quick reference for connecting and exchanging information between two systems. This document describes a typical process for an interactive or automated, batch File Transfer Protocol (FTP) session running on a PC with Windows/2000 and connecting to a UNIX system. This process and the FTP syntax may vary slightly depending on the hardware and software configurations of the local and remote systems.

This document may be used to assist as a tutorial for new programmers or as a quick reference for experienced programmers that are interested in transferring files between systems using the File Transfer Protocol (or FTP). Links to additional documents, programming examples and professional services are provided.

In the world of programming there are many ways to solve a problem. This documentation and software were developed and tested on systems that are configured for a SIMOTIME environment based on the hardware, operating systems, user requirements and security requirements. Therefore, adjustments may be needed to execute the jobs and programs when transferred to a system of a different architecture or configuration.

SIMOTIME Services has experience in moving or sharing data or application processing across a variety of systems. For additional information about SIMOTIME Services or Technologies please contact us using the information in the  Contact or Feedback  section of this document.

Software Agreement and Disclaimer

Permission to use, copy, modify and distribute this software, documentation or training material for any purpose requires a fee to be paid to SimoTime Technologies. Once the fee is received by SimoTime the latest version of the software, documentation or training material will be delivered and a license will be granted for use within an enterprise, provided the SimoTime copyright notice appear on all copies of the software. The SimoTime name or Logo may not be used in any advertising or publicity pertaining to the use of the software without the written permission of SimoTime Technologies.

SimoTime Technologies makes no warranty or representations about the suitability of the software, documentation or learning material for any purpose. It is provided "AS IS" without any expressed or implied warranty, including the implied warranties of merchantability, fitness for a particular purpose and non-infringement. SimoTime Technologies shall not be liable for any direct, indirect, special or consequential damages resulting from the loss of use, data or projects, whether in an action of contract or tort, arising out of or in connection with the use or performance of this software, documentation or training material.

Downloads and Links

This section includes links to documents with additional information that are beyond the scope and purpose of this document. The first group of documents may be available from a local system or via an internet connection, the second group of documents will require an internet connection.

Note: A SimoTime License is required for the items to be made available on a local system or server.

Current Server or Internet Access

The following links may be to the current server or to the Internet.

Note: The latest versions of the SimoTime Documents and Program Suites are available on the Internet and may be accessed using the icon. If a user has a SimoTime Enterprise License the Documents and Program Suites may be available on a local server and accessed using the icon.

    Explore the File Transfer Protocol (FTP) commands using an interactive or scripted batch interface. This document describes a typical process for an interactive and automated, batch FTP session running on a Windows System and connecting to another Windows System, a Linux or UNIX System or an IBM Mainframe System.

    Explore An Enterprise System Model that describes and demonstrates how Applications that were running on a Mainframe System and non-relational data that was located on the Mainframe System were copied and deployed in a Microsoft Windows environment with Micro Focus Enterprise Server.

    Explore the alternatives for transferring data files between systems. This link provides access to a repository of information that includes the transferring and/or sharing of data between Mainframe (ZOS or VSE), Linux, UNIX and Windows Systems.

    Explore the Numbers Connection for additional information about the structure and processing of numeric data items (or numeric fields).

    Explore The ASCII and EBCDIC Translation Tables. These tables are provided for individuals that need to better understand the bit structures and differences of the encoding formats.

    Explore The File Status Return Codes that are used to interpret the results of accessing VSAM data sets and/or QSAM files.

Internet Access Required

The following links will require an internet connection.

A good place to start is The SimoTime Home Page for access to white papers, program examples and product information. This link requires an Internet Connection

Explore The Micro Focus Web Site for more information about products (including Micro Focus COBOL) and services available from Micro Focus. This link requires an Internet Connection.

Explore the GnuCOBOL Technologies available from SourceForge. SourceForge is an Open Source community resource dedicated to helping open source projects be as successful as possible. GnuCOBOL (formerly OpenCOBOL) is a COBOL compiler with run time support. The compiler (cobc) translates COBOL source to executable using intermediate C, designated C compiler and linker. This link will require an Internet Connection.

Glossary of Terms

    Explore the Glossary of Terms for a list of terms and definitions used in this suite of documents and white papers.

Contact or Feedback

This document was created and is maintained by SimoTime Technologies. If you have any questions, suggestions, comments or feedback please use the following contact information.

We appreciate hearing from you.

Company Overview

SimoTime Technologies was founded in 1987 and is a privately owned company. We specialize in the creation and deployment of business applications using new or existing technologies and services. We have a team of individuals that understand the broad range of technologies being used in today's environments. Our customers include small businesses using Internet technologies to corporations using very large mainframe systems.

Quite often, to reach larger markets or provide a higher level of service to existing customers it requires the newer Internet technologies to work in a complementary manner with existing corporate mainframe systems. We specialize in preparing applications and the associated data that are currently residing on a single platform to be distributed across a variety of platforms.

Preparing the application programs will require the transfer of source members that will be compiled and deployed on the target platform. The data will need to be transferred between the systems and may need to be converted and validated at various stages within the process. SimoTime has the technology, services and experience to assist in the application and data management tasks involved with doing business in a multi-system environment.

Whether you want to use the Internet to expand into new market segments or as a delivery vehicle for existing business functions simply give us a call or check the web site at http://www.simotime.com