Use the EATTR statement to specify whether new data sets can have extended attributes and whether the data sets can reside in the EAS of an EAV. You can also use the SIte and LOCSIte subcommands to set this keyword.
- Server
- This setting applies when creating data sets on the server's system.
- Client
- This setting applies when creating data sets on the client's system.
Syntax
.-EATTR SYSTEM------. >>-+-------------------+--------------------------------------->< '-EATTR--+-NO-----+-' +-OPT----+ '-SYSTEM-'
Parameters
- NO
- The new data set cannot reside in the EAS, and its VTOC entry cannot have extended attributes.
- OPT
- The new data set can reside in the EAS, and its VTOC entry can have extended attributes if the volume supports them.
- SYSTEM
- The new data set will use the SMS data class EATTR value. If no SMS data class is defined, or if the data class contains no EATTR specification, the data set will be allocated with the system default. This is the default.
Examples
To allow new data sets to have extended attributes if the volume supports them, and to allow new data sets to reside in the EAS, code the following statement in FTP.DATA:
EATTR OPTRelated
topics:
- See the storage management subsystem (SMS) information in the z/OS Communications Server: IP Configuration Guide for more information about specifying attributes when allocating new data sets.
- BLKSIZE (FTP client and server) statement
- DATACLASS (FTP client and server) statement
- DCBDSN (FTP client and server) statement
- DIRECTORY (FTP client and server) statement
- DSNTYPE (FTP client and server) statement
- LRECL (FTP client and server) statement
- PDSTYPE (FTP client and server) statement
- PRIMARY (FTP client and server) statement
- RECFM (FTP client and server) statement
- RETPD (FTP client and server) statement
- SECONDARY (FTP client and server) statement
- SPACETYPE (FTP client and server) statement
- VOLUME (FTP client and server) statement