The Snapshot Copy function is supported across a sysplex environment.
You must use the IRLMGRP keyword to provide the IRLM group name to the Snapshot Copy function. The Snapshot Copy function passes this name to XBM at Snapshot Copy registration. XBM uses this name to ensure that each active IRLM in a sysplex has an active XBM subsystem. Snapshot Copy registration fails if XBM discovers an active IRLM without a supporting XBM subsystem.
Databases that are registered to DBRC with share level 3 are eligible for sysplex Snapshot Copy processing. Databases that are registered with share level 2 or less are not eligible for sysplex Snapshot Copy processing. Local caching is not allowed for share level 3 data sets.
For XBM to support a sysplex environment, you must set up the Parallel Sysplex Support (PSS) component of XBM. For more information, see SNAPSHOT UPGRADE FEATURE for IMS.
Warning
If you specify the IRLMGRP keyword, the PSS component of XBM must be active.
If you specify the IRLMGRP keyword but the PSS component is not active, XBM might issue return code 12 and reason code 1080 (for OSAM database data sets) during the Image Copy utility’s snapshot task for an IMS database data set. After the first failure of a snapshot task, XBM might issue return code 12 and reason code 1098 during other snapshot tasks for other database data sets. XBM issues the following message (written to the XBM SYSPRINT data set) to explain the failure:
BMC73860E xbmssid Required PSS component support not available for IMS data set dataSetName
If you intended for the snapshot task to run in a data-sharing sysplex environment, determine why the PSS component was stopped and restart the component if appropriate. Otherwise, remove the IRLMGRP keyword from the ICPSYSIN control statement data set.
For more information, see SNAPSHOT UPGRADE FEATURE for IMS, or the Knowledge Base on the Support Central website.