Object types and migration

Edit online

Understanding what objects IBM® i Migrate While Active will and will not migrate to the copy node is critical. This section examines this topic from the perspective of the type of object on the IBM i. For each class of objects, an explanation of the migration support is given, looking independently at both the system migration stage and the data synchronization stage.

In each section, any exceptions to migration support are listed. Also, additional information explains how a Migrate While Active user could perform a live comparison of the specific object(s) between the source and copy node.

Note: Data within an independent ASP (IASP) can be migrated outside of Migrate While Active using IASP replication technologies found in the IBM PowerHA® SystemMirror® for i (5770-HAS) product. Visit the following web page for additional resources regarding migrating an IASP in conjunction with Migrate While Active: https://www.ibm.com/support/pages/node/7176812.
There are four classes of objects.
  1. Db2® Mirror replication-eligible objects in libraries, where the library resides within SYSBAS.

    The Db2 Mirror environment is used by Migrate While Active to support migration of the object types that are typically updated in user applications.

    Example object types include Db2 for i physical and logical files (*FILE)

  2. Objects in libraries which are not Db2 Mirror replication-eligible, where the library resides within SYSBAS.

    The IBM i operating system has a long list of object types that reside within libraries. This section is focused on the library-based object types that are not eligible for Db2 Mirror replication.

    Example object types include Alert Table and Class (*ALRTBL and *CLS)

  3. Objects within the integrated file system, where the integrated file system path resides within SYSBAS.

    Most objects in the integrated file system are supported by Migrate While Active.

    Example object types include Stream File and Directory (*STMF and *DIR)

  4. Pseudo objects, which have a corresponding value for an object type, but are not found within a library.

    A pseudo object type is a special object type used in the object tracking list to reference an entity that is not a system object. Pseudo object types are defined for system level environment variables (*ENVVAR), security attributes (*SECATR), system values (*SYSVAL), and function usage identifiers (*FCNUSG).