Usage notes
- If the hierarchical file system element is packaged inline, it must immediately follow the hierarchical file system element MCS and must not contain any records starting with ++. Neither FROMDS, nor RELFILE, nor TXLIB can be specified on the hierarchical file system element MCS.
- To be packaged inline, a hierarchical file system element must contain fixed-block–80 records. If the original format of the element is not fixed-block–80 records, you can use GIMDTS to transform the element into the required format before packaging it. Later, when SMP/E installs the element, it is changed back to its original format. For more information about using GIMDTS, see GIMDTS: Data transformation service routine.
- If the hierarchical file system element is packaged in a TXLIB data set, the ddname specified in the TXLIB operand is required during APPLY and ACCEPT processing.
- For information about elements packaged in RELFILE format, see z/OS Packaging Rules.
- A ++HFS MCS can be used to supply a pre-built program object to be placed into a UNIX file system. A user can do an OGET for an existing program object in the file system to cause the program object to be placed into an MVS™ data set as fixed length records. This data can then be packaged as a ++HFS element with the BINARY operand. The HFS copy utility can then copy the element into the file system as a binary entity, which can then be executed.