Syntax
attrib logical-name[={dd|dsn|hfs|lib}]
[attribute-name=[attribute_value]]...
Description
The attrib command sets the file system attributes that govern the transfer operations on the host with the specified logical name.
If only a logical name is specified in the attrib command, the current set of attributes for the specified host is displayed. For systems that support multiple file systems, such as z/OS and IBM i, the logical name can be followed by an file system name that indicates the files system to which the attribute applies:
- z/OS: hfs, dsn, dd
- IBM i: hfs, lib
If no file system name is specified, the attributes will be applied for the currently selected file system. If no attributes are specified, the transfer server returns its current set of attributes and their values.
Parameters
Parameter | Description |
logical-name | Logical name of the transfer server for which to set the attributes (or from which to retrieve the attributes). |
dd|dsn|hfs|lib | File system for which the attribute is to be set:
If no file system is specified, the attribute is set for the current file system on the specified server. |
attribute-name | Name of an attribute. |
attribute-value | Value to be set for the attribute. |
Common File System Attributes
The following attributes are common to UDM on most platforms.
Attribute Name | Values | Description |
---|---|---|
asa | yes, no | Note This attribute is used only for UDM for z/OS, when using the dd or dsn file system. |
bom | default, yes, no | Controls byte order mark (BOM) processing for UTF16-encoded output files. |
casesensitive | yes, no | Controls how forfiles wildcard variable expansion is processed. The value should match how the forfiles file list was generated on the target UDM server; in most cases, that will be true. However, Windows has some unique casing scenarios; for example, it is possible for the file system to be mostly case insensitive while one or more specific directories are case sensitive.
|
createop | append, new, or replace | Specification for how the file is to be created: |
defext | Any sequence of characters valid for the destination file system. | Sequence of characters appended to the end of the filename used to write the destination file, if the source filename is being used implicitly as the destination filename. This occurs after the file extension has been truncated (if truncext is set to yes). Note The sequence of characters is appended verbatim. UDM does not add a dot character before the sequence, so if one is desired, it must be specified explicitly. |
eol | Any sequence of valid text data. | End-of-line sequence used in text transfers.
|
linelen | A positive integer | Maximum length of each line of data (record under the z/OS dd and dsn file systems) written. It applies only to the destination side of a transfer and is used in conjunction with the lineop and padline attributes.
|
lineop | none, stream, wrap, or trunc | Line operation for transferred lines (records under the z/OS dd and dsn file systems). Note If an end of line sequence is specified, the length of the sequence is not considered by UDM when determining the length of a line on the destination side. UDM only looks at the raw data that is transferred. |
mode | Set of three numbers (0-7) or nothing. | Note This attribute is used only for UDM for UNIX. |
ostype | AIX, HP, Linux, Solaris, USS, Windows, or z/OS | Type of operating system. This attribute is associated with UDM server. Its default value is set based on the platform that the UDM component was compiled for. |
padline | none, null, or space | Specification for whether or not data is padded. (Used in conjunction with linelen, when linelen is not zero.) |
rdw | yes or no | Specifies how to manage files whose records may start with a 4-byte Record Descriptor Word (RDW). This RDW contains the record length for variable-length record data that originates from z/OS, and is structured as follows: Note The RDW is stored in binary format. To prevent conversion of the record length to a text value, transfer the file as binary using the mode type=binary command. |
regex | yes or no | Allows regular expression pattern matching to select which files are chosen for the copy, delete, dir, and move commands, and the forfiles. Note Regular expression pattern searches are case-insensitive on Windows systems. For Unix and z/OS sessions, they are case-sensitive. |
srccreatetime | yes or no | Note This attribute is used only for UDM for Windows. |
srcmodtime | yes or no | Note This attribute is used only for UDM for UNIX, Windows, and IBM i. |
srcaccesstime | yes or no | Note This attribute is used only for UDM for UNIX, Windows, and IBM i. |
trans | yes or no | Specification for whether or not a transactional file copy is to be performed: Note For z/OS and IBM i, trans is valid only under the hfs file system. |
truncext | yes or no | Specification for whether or not the source filename's extension should be truncated if it is being used as the destination filename (no filename was explicitly specified on the destination side of the transfer operation). Note UDM considers a file extension to be the sequence of characters following the last dot (.) character in the filename. When an extension is truncated, the dot marks the beginning of the extension and is truncated as well. UDM will not consider the a dot character as the first character in a filename as indicating a file extension. |
umask | Three-digit octal value. | File permissions mask used to create the destination file or directory. When the source file comes from an HFS file system and the source UDM component version is 3.2 or greater, the file permission mode is set based upon the source file permission mode. Directory permission modes are always set based on the UMASK attribute or option. Note For UNIX and z/OS (under the hfs file system), umask is valid only on the destination side of the transfer. |
usefqn | yes or no | Specification, when copying a data set under the dsn file system, whether or not the fully qualified data set name is sent over as the source file name to be used by the destination if an explicit destination filename is not given. Note For z/OS, usefqn is valid only on the source side of the transfer. |
Example
To set the line length, line operation, and line padding sequence: