You can transfer a file or data set from the FTP client to the FTP server by writing to BatchPipes®.

To transfer a file to BatchPipes, perform the following steps:

1. Start the BatchPipes subsystem.
   When you successfully start the BatchPipes subsystem, messages similar to the following ones are displayed on the MVS™ console.

   11.33.43  IEF403I BP01 - STARTED - TIME=11.33.43                               
   11.33.43  ASFP000I BATCHPIPES FOR OS/390 SUBSYSTEM BP01:                       
     PRODID=5655-D45 PRODLVL=HACH301 COMPID=565506500                             
     CONTAINS LICENSED MATERIALS - PROPERTY OF IBM CORP.                          
     CONTAINS RESTRICTED MATERIALS OF IBM CORP.                                   
     5655-D45 (C) COPYRIGHT IBM CORP. 1992, 2000                                  
     ALL RIGHTS RESERVED.                                                         
     U.S. GOVERNMENT USERS RESTRICTED RIGHTS -                                    
     USE, DUPLICATION, OR DISCLOSURE RESTRICTED BY                                
     GSA ADP SCHEDULE CONTRACT WITH IBM CORP.                                     
   11.33.43  ASFP007I BATCHPIPES BP01 COMMAND PREFIX IS BP01                      
   11.33.43  ASFP011I BATCHPIPES BP01 INITIALIZATION COMPLETE.                    
   11.33.43  ASFP017I BATCHPIPES BP01 MODE(LOCAL) PIPEPLEX(**NONE**) 

   ______________________________________________________

2. Start the BatchPipes reader.
   You must start the BatchPipes reader before you can use the FTP server to write to BatchPipes. The following is an example of the Job Control Language (JCL) statements that you can use to start a BatchPipes subsystem reader of data set USER3.SUBSYS.OUTPUT3.

   //USER3@2 JOB MSGCLASS=A,CLASS=A                         
   //STEP1   EXEC PGM=IEBGENER                              
   //SYSIN   DD DUMMY                                       
   //SYSPRINT DD SYSOUT=*                                   
   //SYSUT1   DD DSN=USER3.SUBSYS.OUTPUT2,SUBSYS=BP01,      
   //            DCB=(LRECL=80,RECFM=FB)                    
   //SYSUT2   DD DSN=USER3.SUBSYS.OUTPUT3,                  
   //            DISP=(NEW,CATLG,DELETE),                   
   //            UNIT=SYSDA,                                
   //            SPACE=(TRK,(10,10),RLSE),                  
   //            DCB=(LRECL=80,RECFM=FB)

   When BatchPipes is open for read, messages similar to the following are displayed in the JOBLOG output:

   00  11.35.13  $HASP100 USER3@2  ON INTRDR                    FROM TSU00033 USER2 
     - 11.35.13  ICH70001I USER2   LAST ACCESS AT 11:05:39 ON FRIDAY, MARCH 2, 2007 
     - 11.35.13  $HASP373 USER3@2  STARTED - INIT 1    - CLASS A - SYS 3090          
     - 11.35.13  IEF403I USER3@2 - STARTED - TIME=11.35.13                           
     - 11.35.14  ASFP394I BATCHPIPES READER JOB WAITING FOR OPEN.                    
     -       JOB=USER3@2 STEP=STEP1 DD=SYSUT1 SUBSYS=BP01                            
     -       PIPE=USER3.SUBSYS.OUTPUT2                                               

   ______________________________________________________

3. Start the job that reads from BatchPipes.
   Requirement: The BatchPipes reader must be active for the FTP server to write to BatchPipes.

   ______________________________________________________

4. Configure the FTP server for writing to BatchPipes.
   Use the SITE command to specify the following:

   • The BatchPipes subsystem name. Use the SUBSYS parameter. For example, if your BatchPipes subsystem is named BP01, specify the following:

     SITE SUBSYS=BP01 

   • A record format that is compatible with BatchPipes. Supported record formats are F, FB, V, and VB. Specify the RECFM parameter.
   • A logical record length and block size that are compatible with BatchPipes. Specify the LRECL and BLKSIZE parameters.

   ______________________________________________________

5. Set up the client and server for binary (Type I) file transfer.
   Guideline: With most FTP clients, including the z/OS® FTP client, you can use the Binary subcommand from the client to set up a binary file transfer.
   Restrictions: The following restrictions apply when you specify a SUBSYS value:

   • APPE and REST commands are not supported.
   • Only binary (type I) file transfer is supported.
   • Only FILETYPE SEQ is supported.
   • Checkpointing and file transfer restart are not supported. Checkpointing is described in Restarting a failed data transfer.
   • SMS-managed data sets (data sets with an assigned storage class) cannot be used.
   • Only RECFM values F, FB, V, and VB are supported.

   ______________________________________________________

6. Transfer a file or data set to the FTP server, specifying BatchPipes as the destination. You must put directly to the BatchPipes subsystem rather than appending to BatchPipes, for example:

   put 'user3.source.data' 'user3.subsys.output1'