Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.

SSH Tectia

Dataset and HFS File System Access

z/OS has both MVS datasets, and Hierarchical File System (HFS) files. As both types must be accessed by the SFTP server, there must be a mechanism for distinguishing between them. Traditionally, MVS datasets in z/OS are accessed using the filename format //'NAME.OF.MVS.DATASET', while HFS files are accessed using the filename format /path/to/hfs/file.

In z/OS, if a dataset name is not enclosed in single quotes, the user prefix is added in front of the dataset name. For example, if user USER1 has a dataset DATASET.NAME1, the user can access it using the dataset name //DATASET.NAME1. It is also possible to use an absolute prefixed name //'USER1.DATASET.NAME1'.

z/OS has also library datasets, whose members are accessed using the dataset name //DATASET.NAME1(MEMBER1).

Migrated Datasets

SSH Tectia Server for IBM z/OS will not mount volumes or consider off-line devices when accessing datasets, instead it will issue an error message if the dataset is in the catalog but the volume is not available.

Case-Sensitivity of HFS and MVS Names

HFS file names are case-sensitive. For example, /tmp/MYFILE and /tmp/myfile result in two different files.

MVS dataset names are case-insensitive. For example //'USER1.DATASET.NAME1' and //'user1.dataset.name1' are handled the same way.

===AUTO_SCHEMA_MARKUP===