Data that should not be replicated - assure_mimix - 10.0

There are some considerations to keep in mind when defining data for replication. Not only do you need to determine what is critical to replicate, but you also need to consider data that should not be replicated.

As you identify your critical data, consider the following:

• Do not place user created objects or programs in the LAKEVIEW, MIMIXQGPL, or VSI001LIB libraries or in the IFS location /visionsolutions/http/vsisvr. Any user created objects or programs in these locations will be deleted during the installation process. Move any such objects or programs to a different location before installing software. The one exception is that job descriptions, such as the MIMIX Port job, can continue to be placed into the MIMIXQGPL library.

• Only user created objects or programs that are related to a product installation should be placed within the product’s installation library or a data library. Examples of related objects for MIMIX products include user created step programs, user exit programs, and programs created as part of a MIMIX Model Switch Framework implementation. 

• Certain types of information must not be replicated. Also, some temporary data associated with applications may not need to be replicated. Table 3 identifies what data to exclude from replication.

  Table 1. Data to exclude from replication

  Data Category	Type	Do Not Replicate
  Application Environment	Temporary objects or files	You may not need to replicate temporary files, work files, and temporary objects, including DLOs and stream files. Evaluate how your applications use such files to determine if they need to be replicated.
  System Environment	Libraries	IBM-supplied libraries, files, and other objects for System i, which typically begin with the prefix Q.
  	User profiles	System user profiles, such as QSYSOPR and QSECOFR
  MIMIX Environment	Libraries (and contents)	LAKEVIEW MIMIXQGPL MIMIX product installation libraries MIMIX data libraries - for example, mimix_0 and mimix_1. MXIWIZ* VSI001LIB #MXJRN* (MIMIX journal libraries) Note: MIMIX is the default name for the MIMIX installation library -- the library in which Assure MIMIX is installed. MIMIX data libraries are associated with a MIMIX installation library and have names in the format installation-library-name_x, where x is a letter or number.
  	IFS directories (and contents)	/LakeviewTech /VISIONSOLUTIONS /VisionISOImages
  	User profiles and corresponding message queues	LAKEVIEW MIMIXOWN MIMIXCLU
  iOptimize Environment	If iOptimize is installed on the same system or in the same partition as MIMIX, do not replicate the following:
  	Libraries (and contents)	IOPT IOPT71 IOPTSPLARC IOPTOBJARC Note: IOPT is the default name for the iOptimize installation library -- the library in which iOptimize is installed. iOptimize data libraries are associated with an iOptimize installation library and begin with the default name.
  	Authorization lists	IOAUTLST71
  	User profiles  and corresponding message queues	IOPTOWNER ITIDGUI VSI001LIB
  	Device description	VSINSVRT
  	IFS directories (and contents)	VISIONSOLUTIONS /VisionISOImages
  MIMIX Director™ Environment	For MIMIX Director, 8n is the release level. For example, n=1 in release 8.1. If MIMIX Director is installed on the same system or in the same partition as MIMIX, do not replicate the following:
  	Libraries (and contents)	ITID8n  IDSPLARC8n IDOBJARC8n
  	Authorization lists	IDAUTLST8n
  	User profiles and  corresponding message queues	ITIDOWNER ITIDGUI VSI001LIB
  	Device description	VSINSVRT
  	IFS directories (and contents)	VISIONSOLUTIONS /VisionISOImages