IBM Support

Capture/Restore for HFS information.

Question & Answer


Question

Does z/TPF include capture and restore for a hierarchical file system (HFS)? Is there some sort of packing function (for example, zip) we can use to copy the file for backup?

Answer

On z/TPF there are a few more options for ensuring the safety of your HFS data:

  1. The zfile fsck command allows you to diagnose and repair most of the file systems on the z/TPF system to some extent. Also PJ36401 adds support for shadowing collections that are used by the file system (through the zfile attr command) for additional protection of collections that back collection support file system (TFS) files and directories.
  2. Tar, pax and similar utilities allow bundling of files and even entire subtrees so that they can be backed up to other media quickly and easily. You can ftp this tar file to another system (off of TPF) or move it to another file system on TPF (see the next item below). You can also tar directly to tape. Tar support includes APARs PJ31596, PJ31597, PJ31604, and PJ31619.
  3. New file systems added for z/TPF. Of the new file systems (MFS, PFS, FFS, PROCFS, SYSFS), the PFS and FFS provide the ability to store your data in persistent file systems, much like the TFS file system. These new file systems, however, are not backed by Collection Support (TO2) and are, therefore, unaffected should any TO2 (or TFS) corruption occur (and vice versa). This method is useful even if a “zfint on bp” or “zoodb init” is done to initialize the TFS, because the FFS and PFS file systems survive this and can be mounted once the TFS has been successfully recreated.
  4. The mtab file is also not cleared when entering ZOODB INIT command or ZFINT ON BP and the mount entries in mtab are used to remount file systems after the initialization. When using an FFS or PFS the mount point directories will not exist after the initialization so those mounts will fail.

    For this reason unmount any FFS or PFS file systems before entering ZOODB INIT or ZFINT ON BP causing their entries to be removed from mtab and avoiding the mount errors afterwards.
  5. Note that the z/TPF collection support (z/TPFCS) capture/restore is not a file system capture/restore. z/TPFCS capture/restore has the potential to damage the file system on TPF 4.1 and z/TPF if used on file system collections.

[{"Product":{"code":"SSZL53","label":"TPF"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"z\/TPF","Platform":[{"code":"PF036","label":"z\/TPF"}],"Version":"1.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 August 2018

UID

swg21447671