Sequential Data set attributes

The server must KNOW the correct values for the following attributes. Please remember that values derived from SITE commands blindly override and replace values dervied from the view.

1) Real Data Set Name:                               to see how to pass the real data set name to the server..
    Tape file names are 17 characters long! .

2) TYPE:
    Constant character string TAPE

3) DISPosition:

    The following discussion outlines how the FTP server uses the specified disposition to manipulate a
    volume (reel or cartridge) to produce various results. It applies only to non-TMS tapes.
    For TMS-controlled tapes, follow the rules of the Tape Management System.

      DISP = NEW:

      This disposition asks the FTP server to create a new tape data set. The server creates a new data set
      as follows:

       1) If you mount an empty tape, or an expired tape & SWITCH_TAPE_OVERWRITE = YES,
           then the server basically creates the file as the first file on the tape (i.e., file sequence 1)
.
       2) If you mount a tape that has not expired yet, or expired but SWITCH_TAPE_OVERWRITE = NO,
           then the server stacks the data set at the end of the tape.

       DISP = MOD:

       This disposition asks the FTP server to APPEND the uploaded data. If the mounted tape is empty,
       then the server acts as if DISP = NEW (i.e., creates a new file). Otherwise, the server
       appends (i.e., enlarges) the last file on the tape.

4) Tape Management System (FM = YES | NO):

         If the data set is to reside on a tape controlled by TMS, then specify YES; Otherwise, specify NO.


5) RECFM: F, FB, V, VB, S, SB or U to indicate
                    Fixed, Fixed blocked, Variable, Variable blocked, Snapnned, Spanned Blocked or Undefined, respectively.

6) RECL:     logical record length.

7) BLKSZ:   block size, if logical records are blocked.

8) Error Option:

     Specify Quit if you want to terminate the FTP in case of soft errors. Any other value instructs the
     Server to skip the error block and continue processing as normal.

9)   ASCII:

       Specify YES if the tape is an ANSII ASCII tape. Otherwise, specify NO (i.e., tape is EBCDIC).

10) VOLSER:

       Whatever you enter here will be echoed in the WTOR (see next item).. However This value is
        not entered into the TLBL.

11) UNIT: (non-TMS files only.....    i.e., TGT_FM = NO is coded):

     The server can ASSIGN, or allocate, tape drives by CUU, MODEL or TYPE as follows:

    CUU Assignment:

           CUU assignment MUST be used if the drive is pre-loaded with the correct tape(s). The application
           does NOT issue a WTOR to the operator. This behavior is intended to aid in transferring tape files
           without operator intervention. Suppose, for example, that you know that a client FTPs tapes at 10:00
           P.M., and you know that no one will be around. What do you do? You pre-load the CUU with the
           correct tape(s) and at 10:00 P.M. the server does its business
.
     MODEL and TYPE Assignments:

            MODEL or TYPE assignment requires operator intervention. The opeator must reply to a WTOR
            as follows:

            The server issues WTOR before it tries to ASSIGN a candidate drive. At this point, the operator
            should:

                   a) ready the drive (i.e., attach it, load the tape, etc, etc) and reply GO, or
                   b) reply with NEXT (the application looks for the next candidate drive, if any), or
                   c) reply with a specific CUU.

             In any case, a new WTOR is issued to get the operator's permission for the tape assignment to
             continue.

            If you have configured a mixed drive configuration (i.e., 3480's and 3490's), then consider
             the following:

             Assignment by MODEL instructs the server to consider only those tape drives whose model
              matches the value coded in the UNIT statement. For example, if you code TGT_UNIT = 3480,
              then only 3480 drives are considered.

             On the other hand, ASSIGNing tape drives by TYPE (i.e., CART) might result in allocating mixed
              type drives, if you group those drives under the same type.

             For more information about How to Configure Tape drives, please see TAPE_DRIVE global
             configuration statement in                               and while at it, you might want to glance at the
             SWITCH_TAPE_OVERWRITE Expired statement as well.

12) EXP:

       Specify Expiration date YYYY/ddd, where ddd is julian day, or number of days. Default is 7 days.

13) LABEL:

      Specify S, U or N for Standard labels, Unlabeled, or Non-standard label, respectively.

14) File Sequence Number:

      specify the file sequence number if applicable.

15) Drive Mode:

      Specify tape drive mode, if applicable.

16) BufferOffset:

      ASCII tapes variable files only. specify BUFOFF, if applicable.