Replication-eligible objects

The Db2® Mirror environment supports replication of the object types that are typically updated in user applications.

IBM i objects

The following table lists the IBM® i object types that are eligible for replication by Db2 Mirror. More replication details for specific object types are contained in Object replication details.

Table 1. List of Db2 Mirror eligible IBM i object types
Object Type Description
*AUTL2 Authorization list
*DTAARA Data area
*DTAQ6,7 Data queue
*ENVVAR1 Environment variable
*FCNUSG1,2 Functional usage
*FILE3 File
*JOBD Job description
*JOBQ Job queue
*JRN Journal
*LIB Library
*OUTQ4 Output queue
*PGM Program
*SECATR1,2 Security attribute
*SQLPKG5 SQL package
*SQLUDT SQL user-defined type
*SQLXSR SQL XML schema repository
*SRVPGM Service program
*SYSVAL1 System value
Start of change*USRIDX7End of change Start of changeUser indexEnd of change
*USRPRF2 User profile
Start of change*USRSPC7End of change Start of changeUser spaceEnd of change
  1. This is a pseudo object type defined for use by Db2 Mirror. The default inclusion state does not apply to this type.
  2. Objects of this type are always included in replication through Db2 Mirror.
  3. Display files, print files, diskette files, tape files, ICF files, communication files, and save files cannot be replicated.
  4. Spooled files are not specified as replicated objects. An output queue can be specified as a replicated object, which causes all spooled files within that output queue to be replicated.
  5. Extended dynamic packages cannot be replicated.
  6. Distributed data management (*DDM) and display (*DSP) type data queues cannot be replicated.
  7. Replication of data queue entries, user indexes, and user spaces must be enabled using object replication controls.

Definition only

You might need to replicate only the definition of an object and not replicate the content. This option is supported within Db2 Mirror for the object types of *DTAQ, *FILE, and *LIB. A Start of changedata queue orEnd of change file can be replicated either as DEFINITION or all the content can be replicated as well. For a library, you can replicate only the library object, or you can replicate the library and all the replication-eligible objects within the library.

Integrated File System objects

Integrated File System (IFS) objects are made accessible on both Db2 Mirror nodes using a different technology than the replicated IBM i object types. To be accessible, the IFS objects must be contained within an IASP and the IASP must be part of a cluster resource group (CRG). This is described in greater detail in IFS IASPs.