SITE/LOCSITE Commands for MVS FTP
Site/LOCSITE commands to use when FTPing to an MVS/Mainframe system.
Resolving the problem
The IBM FTP products for the eSeries zServer mainframes have an extensive list of SITE subcommands for changing the site defaults on the mainframe. These include setting the defaults for file format and record length.
This page is from the MVS TCP/IP V2.2 User's Guide:
4.10.6 SITE and LOCSITE Parameters
Table 7 lists the parameters of the SITE subcommand and LOCSITE subcommand. A description of each parameter and, where applicable, the possible corresponding values for each parameter are shown.
If multiple parameters are specified on the same LOCSITE or SITE subcommand, they should be separated by a blank space.
Table 7: SITE and LOCSITE Parameters for MVS Hosts
|AUTOMount||Permits automatic mounting of data sets on volumes that are not mounted.|
|AUTORecall||Permits automatic recall of migrated Hierarchical Storage Manager (HSM) data sets.|
|BLocks||Specifies that primary and secondary allocations are in blocks.|
|BLocksize=nnnn||Specifies the block size of a data set.|
|CYlinders||Specifies that primary and secondary allocations are in cylinders.|
|DATASetmode||Specifies that all the data set qualifiers below the current directory are treated as entries in the directory (disables DIRECTORYMODE).|
|DB2=db2_name||Specifies the name of the IBM® DB2® subsystem.|
|DCbdsn||Specifies that the current SITE and LOCSITE parameter values are used for new allocation.|
|DCbdsn=data_set_name||Specifies a data set to be used as a model for a new allocation.|
|DIrectory=nnn||Specifies the number of directory blocks to be allocated for the directory of a PDS.|
|DIrectorymode||Specifies that only the data set qualifier immediately below the current directory is treated as an entry in the directory. In directory mode, this qualifier is the only one used by the MPUT, MGET, LS, and DIR subcommands.|
|FILEtype=value||Specifies the file type of the data set. The description of each file type is:
SEQ: Sequential or partitioned data sets on DASD
PIO: PIO data sets on DASD
SQL: SQL query function
JES: Remote job submission
|LRecl=nnn||Specifies the record size in a data set.|
|MGmtclas=class||Specifies the SMS management class assigned to newly allocated data sets.|
|NCP=nn||Specifies the number of disk I/O buffers to be used during data transfer. Valid values are 2 through 20.|
|NOAUTOMount||Prevents automatic mounting of data sets on volumes that are not mounted.|
|NOAUTORecall||Prevents automatic recall of migrated HSM data sets. A migrated HSM data set may be deleted even though NOAUTORECALL is specified since migrated data sets are not recalled for deletion.|
|NORDW||Specifies that Variable Record Descriptors (RDW) are discarded during ftp transmission of VB or VBS data sets in other than block mode.|
|NOSPread||Specifies that the output is not in spreadsheet format when the file type is SQL.|
|PIOBuf=nnn||Specifies the number of records in a PIOAM buffer. The maximum is 32K.|
|PRImary=nnn||Specifies the amount of primary allocation.|
|Qdisk=volume_serial or Qdisk||Displays statistics about available space on a specific volume. If Qdisk is entered without a specific volume serial, statistics about available space on all storage volumes are displayed.|
|RDW||Specifies that Variable Record Descriptors (RDW) are treated as if they were part of the record and not discarded during ftp transmission of VB or VBS data sets in other than block mode. RDW information is stored in a binary halfword. Transfer files in binary to avoid translation problems that can occur if you transfer this binary field in EBCDIC or ASCII.|
|RECfm=format||Specifies the record format of a data set. Valid record formats are: F, FA, FB, FBA, FBM, FM, U, V, VA, VB, VBA, VBM, and VBS. These record formats have the following meanings:
F Fixed record length
V Variable record length
U Undefined record length
B Blocked records
S Spanned records
A Records contain ISO/ANSI control characters
M Records contain machine code control characters.
|RETPD=nnn||Specifies the number of days that a newly allocated data set should be retained. This value is used to calculate the expiration data associated with the data set. The maximum is 32K.|
|SECondary=nnn||Specifies the number of days that a newly allocated data set should be retained. This value is used to calculate the expiration data associated with the data set. The maximum is 32K.|
|SPread||Specifies that the output is in spreadsheet format when the file type is SQL.|
|SQLCol=type||Specifies the column headings of the output file. The following list describes each type:
Names: Names are the column headings. The labels are ignored. This is the hard-coded default.
Labels: Labels are the column headings. If any of the columns do not have labels, the corresponding column heading in the output file is left blank.
Any: The label is the first choice for column heading, but if there is no label, the name becomes the column heading.
|TRacks||Specifies that primary and secondary allocations are in tracks.|
|Unit=unit_type or Unit||Specifies the unit type (for example, 3380) for allocation of new data sets. If unit_type is not specified, the unit type used for allocation is set back to the system default.|
|Specifies the volume serial number for allocation of new data sets. If volume_serial is not specified, the volume serial number used for allocation is set back to the system default.|
More support for:
Software version: Version Independent
Operating system(s): IBM i
Reference #: N1016959
Modified date: 18 August 2012