This section contains basic information about using MSS with data sets. See Advanced Data Set Information for more information.
All data sets that are referenced in JCL statements or TSO commands must have an entry in the catalog so that MSS can locate the local file that represents the data set. These data sets include:
On the mainframe, data sets can be either cataloged or uncataloged. You can locate cataloged data sets using their catalog entry, and locate uncataloged data sets using their VOLUME number. In the Windows and UNIX environments, you cannot use the VOLUME to map physical locations as you can on the mainframe. Therefore, you should catalog all data sets on Windows and UNIX. The catalog entry for every data set contains a flag that indicates whether a data set is cataloged or uncataloged; however, all data sets, both cataloged and uncataloged, are actually located using the catalog.
When viewing the catalog you can choose to see just the cataloged data sets or to see both the cataloged and uncataloged data sets.
Data sets that are not referenced in JCL statements or TSO commands do not need entries in the catalog. For example, you can write a program that accesses a file that has no entry on the system catalog by specifying its physical filename in the SELECT clause in the Environment division.
There are three methods of including an entry in the catalog:
Click New on the Catalog page in ESMAC. You need to specify both the MVS name and the local physical filename.
When MSS assigns the physical filename, it uses the default data file path set on the Properties > JES page of ES Admin, followed by the mainframe name with the extension .dat, For example, if the default path for data files is c:\catalog\data sets (Windows) /catalog/data sets (UNIX) then a file with an MVS name of MFE2004.S1217.S160553.J01013.D00006.SYSOUT, will be stored locally as C:\CATALOG\data setS\MFE2004.S1217.S160553.J01013.D00006.SYSOUT.DAT (Windows) /CATALOG/data setS/MFE2004.S1217.S160553.J01013.D00006.SYSOUT.DAT (UNIX).