Preparing and sending SQL files

• Define the SQL output data set as VB if the generated SQL statements cannot exceed 27 KB in length. For example:

   SQL MIGRATE
  DATASET MY.MIGRATE.SQL NEW CYLINDERS SPACE(50,20) UNIT(SYSDA) RELEASE RECFM VB

• If minimizing the elapsed time for the file transmission is important, consider not generating and sending a template file. Using the template file increases the SQL file size by 25 percent or more, which affects transmission time and DASD space usage. If High-speed Apply Engine does not use a template file, some SQL will be executed in dynamic mode before binds occur that allow execution in static mode.

• If you are using File Transfer Protocol (FTP), include the following command to ensure that trailing blanks are removed:

  quote site trail

• If you are using FTP to send the SQL file to a Windows server, include the following command to ensure that High-speed Apply Engine recognizes the end-of-line character:

  quote site sbsendeol=lf

• After sending the file, ensure that all characters were translated correctly from EBCDIC to ASCII. You might need to adjust the translate tables used in the data transfer.

• If the SQL output was generated with RECFM set to FB (the default), include the SQL parameter Format with a value of Packed72 in the High-speed Apply Engine configuration file, as shown in the following example:

  [SQL]
    Format=Packed72

For more information about the Format parameter, see Format.

File transfer examples

The following figure shows sample JCL for running FTP in batch mode on the mainframe:

The following figure shows an example FTP session on a Windows or UNIX platform. In the example, bold text indicates user entries.