            Sample Data Transfer Program Customization Notes

This diskette contains the Sample Data Transfer Programs for use on TSO.
The host TSO system must be using ACF/VTAM Version 1 Release 3 (or
later) or ACF/TCAM Version 2 Release 4 (or later) in order for the File
Transfer Program to be usable.  The Data Transfer Program Upload
procedure is intended to be used by the person responsible for
maintaining the host computer system software. The Sample Data Transfer
Program data sets should be loaded onto the host computer system once
and moved to the appropriate common libraries to make the program
available to all users of the host computer system.


                            TSO Dependencies

The TSO system parameters (member IKJPRMxx of the SYS1.PARMLIB data
set) must have the following characteristics:

   1. The terminal buffers must be at least 80 bytes long. This is
      specified with the TIOC BUFSIZE=nnnn value.

   2. The maximum outbound message size must be at least 2048 bytes.
      This value is calculated from the product of the size of the
      terminal buffers (TIOC BUFSIZE=nnnn) and the maximum number of
      outbound terminal buffers (TIOC OWAITHI=nnnn value). If this
      product is smaller than 2048, increase the OWAITHI value.

   3. The maximum inbound message size must be at least 2048 bytes.
      This value is calculated from the product of the size of the
      terminal buffers (TIOC BUFSIZE=nnnn) and the maximum number of
      inbound terminal buffers (TIOC INLOCKHI=nnnn value). If this
      product is smaller than 2048, increase the INLOCKHI value.


                         ACF/VTAM Dependencies

The UPLOAD procedure uses the 3270 Personal Computer Attachment data
transfer protocols, which requires ACF/VTAM to pass structured fields to
the 3278 terminal. If the 3274 control unit is attached to the host
system via a BSC line, the VTAM System Definition data set
(SYS1.VTAMLST) must specify that BSC transparency is to be used when
sending data to the 3278 terminal. This is done by specifying the
'EDATS' value for the FEATUR2 keyword on the TERMINAL macro describing
the 3278 terminal containing the 3270 Personal Computer Attachment.

For example:
  NK32A311 TERMINAL ADDR=60604040,POLL=40404040,DLOGMOD=T3278M2,       X
       FEATUR2=EDATS

Contact the person responsible for maintaining your ACF/VTAM system data
sets to insure that this keyword is properly specified and that the NCP
is reactivated with the updated System Definition.  Note: The
FEATUR2=EDATS keyword is used only by VTAM, not by the NCP.  Therefore,
changing this keyword in the VTAM System Definition data set does NOT
require rerunning the NCP SYSGEN procedure and does NOT require
reloading the NCP load module.


                         ACF/TCAM Dependencies

The UPLOAD procedure uses the 3270 Personal Computer Attachment data
transfer protocols, which requires ACF/TCAM to pass structured fields to
the 3278 terminal. This support is provided with PTF UZ67877,
which must be installed before attempting to use the UPLOAD procedure.
Also, the Message Control Program must have the following
characteristics:

   1. The buffer size specified for the terminal must be smaller
      than 1536 bytes if the 3274 control unit is attached to the host
      computer using an SDLC communications link or an SNA local channel
      attachment. This is specified by the BUFSIZE keyword on the
      TERMINAL or GROUP macro for the terminal.

   2. The maximum outbound message size must be at least 2048 bytes.
      This value is calculated by multiplying the buffer size (the value
      of the BUFSIZE keyword on the TERMINAL or GROUP macro) by the
      maximum number of outbound message buffers (the value of the
      MAXOUT or MAXBUF keyword on the TERMINAL or GROUP macro). If this
      value is smaller than 2048 bytes, increase the value for the
      MAXOUT or MAXBUF keyword.

   3. The default EBCDIC translation table must be used for the
      terminal. The TRANS keyword on the GROUP or TERMINAL macro must
      either be omitted or must specify TRANS=EBCD. The File Transfer
      program will not work if TRANS=EBCF is specified, since ALL
      inbound data (including structured fields) is folded to upper
      case.


                    3274 Control Unit Dependencies

The UPLOAD procedure uses the 3270 Personal Computer Attachment data
transfer protocols, which require supporting code in the 3274 control
unit. The 3274 control unit must be customized to include the 3270
Personal Computer Attachment code. This should be verified by invoking
the 3270 Personal Computer Attachment Diagnostic Program (3270DIAG)
and specifying the Wrap Test option.  If the Wrap Test does not run
successfully, the UPLOAD procedure cannot be invoked and the 3270
Personal Computer Data Transfer facilities cannot be used.


                      UPLOAD Program Dependencies

The UPLOAD program issues the following TSO commands:

  1. PROF NOCHAR NOLINE NOINTERCOM NOWTPMSG
  2. DELETE (data-set-name) PURGE
  3. EDIT data-set-name NEW NONUM BLKSIZE(3120)

If these three commands do not function exactly as specified in the
OS/VS2 TSO Command Language Reference (GC28-0646), the Sample Data
Transfer Program cannot be installed on the TSO system.


                   PCXFBOOT Command List Dependencies

The PCXFBOOT command list issues the following TSO commands procedure
statements:

   1. PROC 0 DEBUG
   2. CONTROL options
   3. IF condition THEN statement
   4. WRITE text
   5. ERROR OFF | statement
   6. DO ... END
   7. SET variable=value
   8. GOTO label
   9. WRITENR text
  10. READ variable
  11. EXIT CODE(value)

If command procedures running on the TSO system cannot execute these
statements exactly as specified in the OS/VS2 TSO Command Language
Reference, the PCXFBOOT command list will not work. If this is the case,
edit the PCXFBOOT.CLIST data set (after PCXFBOOT fails), make the
required syntactical changes, and rerun the PCXFBOOT command list.

The PCXFBOOT command list also issues the following TSO commands:

  1. PROFILE PAUSE
  2. ERROR
  3. DELETE (data-set-name-list) PURGE
  4. ASM data-set-name NOTERMINAL
  5. LINK data-set-name
  6. ATTRIB
  7. ALLOC
  8. CALL
  9. LINK data-set-name LOAD(data-set-name)
 10. FREE ATTR(attribute-list-name) DD(dd-name)
 11. ISPEXEC CONTROL DISPLAY REFRESH

If command procedures running on the TSO system cannot execute these
commands exactly as specified in the OS/VS2 TSO Command Language
Reference, the PCXFBOOT command list will not work. If this is the case,
consult the HELPME.TSO file on this diskette for suggestions on how to
modify the PCXFBOOT.CLIST data set for your system.


                           UPLOAD Procedure

The UPLOAD procedure creates the Sample Data Transfer Program on TSO.
Before starting the UPLOAD procedure, you must do the following:

  1. Switch to Host Computer mode.

  2. LOGON to TSO

  3. Issue the TSO commands required to have the TSO Terminal Monitor
     Program in direct control of the terminal. The UPLOAD program
     will NOT execute successfully if either ISPF or the TSO Session
     Manager program products are in control of the terminal. (For
     example, do not try to execute the UPLOAD procedure while running
     under ISPF option 6.)

  4. You must be able to allocate data sets on a default volume under
     your TSO user ID. If your installation does not allow for this
     function, the UPLOAD procedure will not work.

  5. All data sets created by the UPLOAD procedure will start with your
     defined user prefix. If you want to create the data sets with a
     different starting qualifier, issue the TSO PROFILE command to
     change your user prefix.

To start the UPLOAD procedure, you must do the following:

  1. Switch to Personal Computer mode.

  2. Make sure there is no write protect tab on the Tso Data Transfer
     Diskette.

  3. Insert the TSO Data Transfer Diskette into the default diskette
     drive. (Issue the A: or B: command to make sure this is the
     default diskette drive.)

  4. Issue the following command:

         UPLOAD TSO

  5. Follow the instructions on the display screen. Note that the UPLOAD
     procedure takes about 1 hour and 25 minutes on a lightly loaded TSO
     system, with a 3278 display terminal connected through a 3274
     control unit to a 9600 baud SDLC link. For a heavily loaded TSO
     system, this procedure may take considerably longer to complete.
     The Personal Computer will periodically beep and display a progress
     message while the UPLOAD procedure is executing. If you do not get
     any feedback after about 5 minutes, the UPLOAD procedure probably
     failed. In this case, read the HELPME.TSO file on this diskette for
     assistance.


               Sample File Transfer Program TSO Data Sets

The UPLOAD procedure creates several data sets on TSO. These data sets
comprise the Sample File Transfer Program. The data sets will probably
have to be merged into other existing data sets in order to use the
Sample File Transfer Program.

   Data Set Name  Contents        Final Destination
   -------------  --------        -----------------
   PCXFER.CLIST   File Transfer   This data set should be copied into
                  command list    member PCXFER of one of the
                                  partitioned data sets which comprise
                                  your TSO command list library (i.e.
                                  one of the data sets which are
                                  allocated to data definition name
                                  SYSPROC). If PCXFER is moved into
                                  a command list library, it can be
                                  invoked as %PCXFER ... Otherwise,
                                  it can be invoked as  follows:
                                     EX PCXFER '...'

   PCXFER.LOAD    File Transfer   The PCXFERP load module can be placed
                  program         in any partitioned data set (or left
                                  in PCXFER.LOAD) that can be used as
                                  a system command library (or, if left
                                  in PCXFER.LOAD, concatenated to the
                                  system command library). See the
                                  OS/VS2 Guide to Writing a Terminal
                                  Monitor Program or a Command Processor
                                  (GC28-0648) for a more detailed
                                  description on adding commands to TSO.
                                  The PCXFERP command is not reentrant
                                  and should not be placed in a library
                                  that is loaded into read-only storage.

   PROFILE.PCXFER File Transfer   This data set contains the default
                  profiles        characteristics for data sets
                                  transferred between the Personal
                                  Computer and TSO. Before executing
                                  the PCXFER command list or the PCXFERP
                                  command, this data set must be
                                  allocated via the ALLOCATE command
                                  with a DDNAME of PCXFPROF.

   PCXFER.PANEL   File Transfer   This data set is only used if you have
                  panels          the Interactive System Productivity
                                  Facility (ISPF) program product
                                  (program number 5668-960) or the
                                  Interactive System Productivity
                                  Facility/Program Development Facility
                                  (ISPF/PDF) program produce (program
                                  number 5665.268) installed on
                                  your TSO system. Members PCXFER,
                                  PCXHLP, PCXFERO, and PCXHLPO
                                  are ISPF panels, and should be
                                  moved into one of the partitioned data
                                  sets which comprise the ISPF panel
                                  library (i.e. a data set which is
                                  allocated to data definition name
                                  ISPPLIB).

   PCXFER.HELP    File Transfer   This data set may be used with the TSO
                  on-line help    HELP command to provide on-line
                                  information about the File Transfer
                                  Program. This data set should be
                                  moved into one of the partitioned data
                                  sets which comprise the on-line help
                                  library (i.e. a data set which is
                                  allocated to data definition name
                                  SYSHELP) as member PCXFER.


                 Using the Sample File Transfer Program

The File Transfer Program may be used to transfer the contents of a
file from a Personal Computer diskette into a TSO data set or to
transfer the contents of a TSO data set to a diskette file on the
Personal Computer or to the Personal Computer printer.

To transfer a file, do the following:

  1. Switch to Personal Computer mode.

  2. Insert a diskette which contains the HOST.EXE file into the
     Personal Computer.  (This file contains the portion of the Sample
     File Transfer application program which runs on the Personal
     Computer.)

  3. Issue the following Personal Computer command:

         HOST

     The HOST command automatically switches to Host Computer mode when
     it is executing.

  4. If you are not already logged onto TSO, issue the LOGON command
     to initiate a TSO session.

  5. If you are using the TSO Session Manager program product, issue
     the appropriate command to terminate the Session Manager.

  6. Invoke the PCXFER command list (see below). You may invoke PCXFER
     directly under the TSO Terminal Monitor Program, or under ISPF
     (from option 6 or from any ISPF menu which has a COMMAND ===>
     input field).

  7. You may transfer one or more data sets by staying in Host Computer
     mode and issuing multiple PCXFER commands.

  8. When you have completed using the File Transfer Program, switch
     back to Personal Computer mode and press the ATTN key. This will
     terminate the Sample File Transfer Program on the Personal
     Computer.


               Invoking the Sample File Transfer Program

Prior to the invocation of the Sample File Transfer Program, the
PROFILE.PCXFER dataset must be allocated via the TSO ALLOCATE command
with a DDNAME of PCXFPROF. This need be done only once, if it is not
FREEd after executing the Sample File Transfer Program.

To invoke the Tso File Transfer Program and be prompted for all required
information from an ISPF panel (if the ISPF Program Product is installed
on your TSO system), issue the following command:

    PCXFER

When using the ISPF panel to specify the file transfer information, you
may request multiple file transfer requests by filling in the panel
each time it is displayed (i.e. after each file has been transferred).
After all data sets have been transferred, you may return to the TSO
Terminal Monitor Program or ISPF by pressing the PF3 key to exit from
the PCXFER panel.

To invoke the TSO File Transfer Program and directly specify all
required information, issue the following command:

    PCXFER  DSNAME(tso-data-set-name)
      or    TO | FROM
    PCXFERP FILESPEC(personal-computer-file-specification)
            < NEW | MOD >
            < EDIT | BAS | VAR | LIST | LIST2 | UNFM >
            < TRAN | TRANS(translate-data-set) | NOTRAN >
            < RECFM(F | FB | V | FB | U | etc.) >
            < VOLUME(tso-volume-identifier) >
            < PASSWORD(tso-data-set-password) >
            < LRECL(nnnnn) >
            < BLKSIZE(nnnnn) >
            < SPACE(nn) >
            < SPACE2(nn) >
            < TRACKS | CYLINDER >
            < DIR(nn) >
            < UNNUM >

The complete syntax for the PCXFER command list and the PCXFERP command
and the explanation of all keywords is documented in the TSO PCXFER.HELP
data set and in your User's Guide.


                   Using the PCXFER Optional Keywords

The PCXFER command list can be invoked using only the required keywords
(DSNAME, FROM or TO, and FILESPEC) most of the time. However, the
optional keywords can be used to tailor the file transfer to fit your
special needs. Please read your User's Guide for more detailed
information on data transfer.
