UDM - IBM i File Systems

Owned by Stonebranch (Deactivated)
Jul 15, 2024
2 min read

IBM i File Systems

Universal Data Mover (UDM) for IBM i supports two types of file systems:

  • HFS file system supports the root and QOpenSys file systems under IFS.
  • LIB (library) file system supports the original, native database file system.

Although UDM can access other IFS file systems, only root and QOpenSys are certified.

Currently, Stonebranch, Inc.:

  • Does not support other IFS file systems.
  • Recommends that users do not use other IFS file systems.
  • Provides no warranty for use of other IFS file systems.
  • Certifies that users assume all risks in using other IFS file systems.

Risks involved in the use of non-supported IFS files systems include, but are not limited to:

  • Loss of data
  • Corrupted data
  • Non-recoverable exceptions

HFS File System

HFS follows the Common File System (CFS) model.

It supports stream files under the root and QOpenSys IFS file systems. Users using UDM to access file systems under IFS, other than root and QOpenSys, do so at their own risk.

HFS also provides enhanced eol handling and eol attribute values for the mixed ASCII and EBCIDIC environment. See #End of Line Sequence for details.

LIB File System

UDM for IBM i supports three file types of the LIB file system:

  1. Data Physical Files
  2. Source Physical Files
  3. Save Files

The type of file created in a copy command on the destination side is governed by the IBM i-specific FILETYPE attribute (see UDM - IBM i LIB File System Attributes).

The default file type created in a copy command is a data physical file.

CFS Terminology Associated with LIB File Types

The following table associates Common File System (CFS) terminology with these LIB file types.
 

CFS

Physical Files (Source and Data)

Save Files

path

An absolute or relative path.
 
Examples:

  • MYLIB/DATA(NAMES)
  • DATA(NAMES)

An absolute or relative path.
 
Examples:

  • MYLIB/BACKUP
  • BACKUP

absolute path

A fully qualified name containing a library, file, and member.
 
Example:

  • MYLIB/DATA(NAMES)

A fully qualified name containing a library and file.
 
Example:

  • MYLIB/BACKUP

relative path

A name without a library. The name is relative to the current directory (library).
 
Example:

  • DATA(NAMES)

A name without a library. The name is relative to the current directory (library).
 
Example:

  • BACKUP

file

Same a path. It may be relative or absolute.

Same as path. It may be relative or absolute.

directory

n/a

n/a

current directory

Name of the current library in which you are working.
 
Example:

  • MYLIB

Name of the current library in which you are working.
 
Example:

  • MYLIB

Additional Information

The following pages provide additional detailed information for Universal Data Mover Transfer Operations (IBM i-specific):