SAM (On Disk) 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.
















The following attributes are always required (i.e., needed for both GET & PUT operations).

1) Real Data Set Name:
                                    to see how to pass the real data set name to the server..

2) TYPE:
    Constant character string DISK

3) DASD Space Manager:
    Tells the server whether the data set resides on a volume controlled by a DASD Manager. 
   
4) RECFM:
    F, FB, V, VB, S, SB or U to indicate
     Fixed, Fixed blocked, Variable,  Variable blocked, Snapnned, Spanned Blocked or
     Undefined, respectively.

5) RECL:
    Logical record length.

6) BLKSZ:
    Block size, if logical records are blocked.

7) CISIZE:
    CI SIZE if the file resides on FBA device,  

8)  Error Option: 
     Tell the server what to do if it experiences soft I/O errors: Quit tells the server to end the FTP.
     Any other value instructs the server to skip the error block and continue processing as normal.

9)  EXP:
      Expiration date YYYY/ddd, where YYYY is 4-digit year and ddd is julian day,  or number of days
      such as 30. Default is 7 days.

10) Location:
      Tell the server, or the DASD Space manager, where the extents are located. Please see how to enter
       EXTENT info down the page.

      Please notice that you can't enter EXTENT info via SITE commands! This means that sequential
      data sets on Unmanaged DASD volumes should be coded in Specific views.


      
Please click here...
Equivalent SITE command:

N/A. See item 1 below. 
SITE TYPE = DISK
SITE FM =   Yes | NO
SITE RECF =  
SITE RECL = 
SITE BLKSIZE =  
SITE CISIZE =              
SITE EOPT =     
SITE EXPIRE =                   
Can't provide via SITE cmd.
Attribute:          

1.  DS_NAME       
2.  TYPE               
3.  DASD Space Manger  
4.  RECFM (rec format)
5.  RECL (rec length)   
6.  Block Size              
7.  CISIZE         
8.  Error Option               
9.  EXPiration              
10. Location (EXTENT
      info)  
View Statement

TGT_FILE      
TGT_TYPE                   
TGT_FM  
TGT_RECFM 
TGT_RECL    
TGT_Block                
TGT_CISIZE         
TGT_EOPT              
TGT_EXPiration            
TGT_BUCKET
Please click here
How To Code EXTENT Info In The TGT_BUCKET Statement:

Please enter EXTENT information as follows:

Volser:ExtentSequence,ExtentSequence;volser:ExtentSequence        
         
     where each  ExtentSequence is two numerical fields in the form of
                        BeginTrackNumber-NumberOfTracks  (for example 3415-300)

Notice that colon (:), Comma (,) semi-colon (;) and Dash (-) are field
delimeters and must be used as follows:


Colon (:) and Comma (,)

   A colon signals the beginning of extent Sequences on the volser that just
   preceeded the colon. Any number of extent sequences can be entered. The
   extent sequences, themselves, are seperated by commas.

The Semi colon (;)

    A semi-colon (;) ends current extent sequences and signals that a new set
    of sequences start on a new pack.

The minus , or dash,  Sign:

   The dash is used in ExtentSequences to separate the BeginTrack field
   from the NumberOfTracks field.



Examples:

    1.  Define a file with two extents on TST000:

          TGT_BUCKET = TST000:ExtentSequence,ExtentSequence

     2. Define a file with one extent on TST000 and two extents on TST001

          TGT_BUCKET = TST000:ExtentSequence;TST001:ExtentSequence,ExtentSequence

    3. Define Track One Data Sets on TST000 (DASD Space Manager locates
        actual extents:
       
         TGT_BUCKET = TST000:1-0


Hosted by www.Geocities.ws

1