Figure 13-5 shows a typical PTF for TCP/IP (a component of z/OS). You will notice that it contains typical MCS statements such as ++ PTF , ++ VER , and ++ MOD . You will also notice the ++ HFS MCS statement, which directs element EZAFTPSM as a file into the HFS path pointed to by DDDEF SEZAMMSC. In addition, a hard link (alias name) will be created to EZAFTPSM in the directory one higher in the hierarchy (indicated by the '..' in the LINK parameter), called ftpdmsg.cat. In other words, if the path in DDDEF SEZAMMSC points to: /usr/lpp/tcpip/lib/nls/msg/C/IBM Then the element will be written as file: /usr/lpp/tcpip/lib/nls/msg/C/IBM/EZAFTPSM With a hard link defined as: /usr/lpp/tcpip/lib/nls/msg/C/ftpdmsg.cat Note: See how the original file (EZAFTPSM) is written in the /C/IBM subdirectory, while the hard link (ftpdmsg.cat) is created in the /C subdirectory, one directory higher because of the '..' specification in the LINK parameter. This type of packaging allows SMP/E unique element names while also meeting the requirements of UNIX naming conventions. ++ PTF (UQ14899). ++ VER (Z038) FMID (JTCP349) PRE (UQ12633)