• Remote Copy (IASP Manager)
  IASP Manager-Remote Copy complements PowerHA for IBM i by providing additional functions, customization and simplification of the customer’s run time environment for Metro Mirror and/or Global Mirror environments for Independent Auxiliary Storage Pool (IASP).  IASP Manager-Remote Copy is currently supported for DS8000 external subsystems only.

  Features

  Provides full automation for either a Metro Mirror or Global Mirror environment (or both), including the following:

  •     Check environment for switch readiness
  •     Sends confirmation inquiry during planned (scheduled) switchovers prior to initiating the switch process
  •     Vary off the IASP on production prior to switchover
  •     Automates planned or unplanned switchovers of Metro Mirror or Global Mirror environment
  •     Provides option for automating replication in reverse after switchover
  •     Provides option for "detaching" the target LUNs and bringing a copy of the IASP online to a backup system for data checks or performing backups
  •     Vary on the IASP on "backup" (now, production) after switchover
  •     Facilitates the integration of external storage replication technologies attached to an IBM i through DSCLI and Tivoli Storage Productivity Center ( TPC ) replication interfaces.
  •     Integrates with TPC-R to manage MGM or Metro Mirror functions.

  Benefits

  •     Simplifies switchover (planned switch) or failover (unplanned switch) process AND reversal of replication through single CL command (SWPPRC)
  •     Simplifies "detach" operation through menu option
  •     Extends PowerHA for IBM i capabilities through the use of automated scripts and tools
  •     Facilitates the integration of external storage (DS8000) remote copy technologies
  •     Integrates (as needed) with IBM Copy Services Manager (formerly Tivoli Productivity Center for Replication - TPC-R)
  •     Stores DS data in both the ASP Copy Descriptions in a single interface, making implementation easier.
  •     Stores a second copy of the data in IBM i clustering to capture any changes made to an ASP copy description used in multiple environments (i.e. FlashCopy and Metro or Global Mirror)
    •         This support also prevents a FlashCopy environment change from negatively impacting a remote copy environment, by detecting the copy description in multiple environments and giving precedence to the remote copy environment over the FlashCopy
  •     Additional logging maintained in a centralized location
  •     Provides an interface for managing/fixing replication errors, if required

  Environment required:

  •     V6R1+
  •     IBM DS8000 Storage Units
  •     Copy Services (Metro Mirror or Global Mirror or both)
  •     PowerHA for IBM i Enterprise Edition on all nodes
  •     *SYSBAS volumes (including the Load Source Unit) can be hosted on external storage or IBM i internal disk

• Metro Global Mirror (ICSM & ACS)
  Metro Global Mirror (MGM) combines the synchronous high-availability (HA) solution of Metro Mirror with the asynchronous, longer-distance disaster-recovery (DR) solution of Global Mirror.  Three systems are required:  1)  Metro Mirror "source" (typical production),  2)  Metro Mirror "target" / Global Mirror "source",  and 3)  Global Mirror "target".  This also requires the use of Tivoli Productivity Center for Replication (TPC-R).

  NOTE:  The design of IASP Manager is to support broadcast Multi-Target Copy (MTC) environments for three-site solutions, as opposed to cascading Metro Global Mirror (MGM) -- described on this page.  Current users of Advanced Copy Services (ACS) Toolkit and IASP Copy Services Manager (ICSM) through version 3.1 (predecessors of IASP Manager) with a Metro Global Mirror environment and a valid maintenance contract with IBM Lab Services can still receive support for Metro Global Mirror.

  Features

  Provides full automation for both the Metro Mirror and Global Mirror environments including the following:

  •     Check environment for switch-readiness
  •     Vary off the IASP on production during switch
  •     Automate the planned or unplanned switch of Metro Mirror environment
  •     Automate the switch back to production after a Metro Mirror switch
  •     Automate the initial planned or unplanned switch of Global Mirror environment
  •     Automate the release and reset of the I/O resources during the manual recovery of a Global Mirror switch back process
  •     Vary on the IASP after a switchover to the new node owning the production copy

  Benefits

  •     Provides shorter-distance high-availability (HA) solution to aid in planned maintenance windows and unplanned outages
  •     Provides longer-distance disaster-recovery (DR) solution for unplanned disasters to meet smaller RPO's
  •     Manage the planned or unplanned Metro Mirror switch (reversal of replication direction), while maintaining a Global Mirror replication to the DR site
  •     Manage the initial planned or unplanned Global Mirror switch
  •     Provides CL commands and documented steps to aid in the manual recovery back to normal production after a Global Mirror switch
  •     Extends beyond existing IBM i PowerHA capabilities for more complex environments
  •     Additional logging maintained in a centralized location

  Environment Required

  •     IBM i V6R1+
  •     DS8000 external storage
  •     PowerHA Enterprise Edition
  •     Advanced Copy Services (ACS) Toolkit or IASP Copy Services Manager (ICSM) version 3.1 or earlier
  •     Tivoli Productivity Center for Replication (TPC-R) version 5.1 or higher
    • Use of at least two TPC-R servers is highly recommended for higher availability
    • ACS (or ICSM) requires both servers to have the same user ID and password
  • Three IBM i partitions/systems -- 1) MMIR "source" (H1 node),  2) MMIR "target" / GMIR "source" (H2 node),  3)  GMIR "target" (H3 node)

• Multi-Target Copy (IASP Manager)
  IASP Manager Multi-Target Copy (MTC) is available in IASP Manager 4.1 to support multi-target solutions using up to three sites.  This includes either two Metro Mirror targets from the same production (source) node -- Metro Mirror - Metro Mirror (MM/MM) -- or one Metro Mirror target and one Global Mirror target from the same production (source) node -- Metro Mirror - Global Mirror (MM/GM).  This support assumes replication of an Independent Auxiliary Storage Pool (IASP) configured on the production (source), using DS8870 external storage.  This also requires IBM Copy Services Manager (CSM) or complete IBM Spectrum Control (Tivoli Storage Productivity Center).

  NOTE:  IASP Manager focuses on Multi-Target Copy (MTC) as its supported multi-site replication strategy.  Support for Metro Global Mirror (MGM) is still available for customers using Advanced Copy Services (ACS) Toolkit or IASP Copy Services Manager (ICSM) through version 3.1 with a valid maintenance contract with Lab Services.

  Features

  Provides full automation for both the Metro Mirror and Global Mirror environments including the following:

  •     Check environment(s) for switch-readiness
  •     Vary off the IASP on production during switch
  •     Automation of the planned or unplanned switch of the Metro Mirror or Global Mirror environment
  •     Additional automation by both CSM and IASP Manager on Global Mirror failover scenarios (degree of automation depends on if the GMIR environment is symmetric or not)
  •     Vary on the IASP after switchover to the new node owning the production copy

  Benefits

  •     Metro Mirror - Metro Mirror (MM/MM) - 2 synchronous pairs of copies of the IASP providing an RPO of zero data loss at two different sites (different from production site)
  •     Metro Mirror - Global Mirror (MM/GM) - 1 synchronous pair of copies of the IASP (RPO=0), and 1 asynchronous pair of copies of the IASP at a remote site with an RPO dependent on bandwidth and writes
  •     Management of planned or unplanned switchovers of both the Metro Mirror environment(s) and Global Mirror environment from a centralized IBM i partition
  •     Provides IBM i CL commands and menu options to manage the entire solution
  •     Extends beyond the capabilities of current IBM i PowerHA capabilities for more complex environments
  •     Additional logging maintained in a centralized location
  •     No restrictions on using incremental FlashCopy at any or all sites in the environment
  •     Full resync's not required after switchover to D/R site
  •     Easier management (less manual intervention required) after failure on H2 node
  •     A switch of one environment is possible, even when the other environment is suspended/failed
  •     Newer GUI in IBM Copy Services Manager (CSM)

  Environment Required

  • IBM i V7R1+
  • (3) DS8870 external storage subsystems, at version 7.4 or higher
  • PowerHA Enterprise Edition
  • IASP Manager version 4.1 or higher
  • IBM Copy Services Manager (CSM) version 6.1 or higher, or complete IBM Spectrum Control (Tivoli Storage Productivity Center) solution
    • CSM can be loaded on any IBM Platform -- IBM i, PPC Linux, AIX, Windows or zOS
    • Use of at least two CSM servers is highly recommended for higher availability
    • IASP Manager requires both servers have the same user ID and password
  • Three IBM i partitions/systems
    • Metro Mirror - Metro Mirror (MM/MM) :  1) [Site 1] MMIR "source" (H1 node),  2) [Site1 or Site 2] MMIR "target" (H2 node),  3) [Site 2 or Site 3] MMIR "target" (H3 node)
    • Metro Mirror - Global Mirror (MM/GM) :  1) [Site 1] MMIR/GMIR "source" (H1 node),  2) [Site 1 or Site 2] MMIR "target" (H2 node),  3) [Site 2 or Site 3] GMIR "target" (H3 node)

• DS8000 Storage Management Toolkit for IBM i
  DS8000 Storage Management Toolkit for IBM i is a collection of utilities that provide for easier implementation and management of IBM i environments integrated with DS8000 storage.

  Features

  Provides additional automation for DS8000-based IBM i environments for the following functions:

  • Create, view, change or delete IBM i host connections to associated storage volumes
  • Save configuration data for future reference
  • Verify PowerHA IASP associations with storage volumes
  • Check IBM i multipath connections
  • Set up SNMP trap support to send DS8000 messages to QSYSOPR by converting the traps to meaningful IBM i messages, along with the full trap in the logs
  • Manage DS8000 users, password files and password expiration

  Benefits

  • Easier management of environment for IBM i integrated with DS8000 storage
  • Centralized IBM i management via menu commands
  • Additional logging to assist with debugging and documentation
  • Conversion of DS8000 errors to IBM i messages, and placement of those errors in QSYSOPR for better debugging

  Environment required:

  • V6R1+
  • IBM DS8000 Storage Units

Additional toolkit information

• ICSM 3.0 Upgrade Instructions

  Pre-req's for ACS 3.0 

  Global Mirror customers.    ICSM 3.0 uses a new method of pausing Global Mirror called pause with consistency.  This new pause method is not available on DS8300 and DS8100 so customers with these models of DS8000 who use Global Mirror should not upgrade to ICSM 3.0

  For DS8700 and DS8800,  the code level requried is 6.3,   but to use this function requires approval via a no charge RPQ.   Customers must request their storage team open a SCORE RPQ  ( new type of RPQ request ),  and reference Global Mirror pause with consistency PCR 1754 

  For DS8870 customers,  code version 7.1 is required to use ICSM 3.0

  FlashCopy customers need to verify that the QLPAR profile is valid for submitting jobs prior to upgrading to ICSM 3.0    Previous versions of ICSM did not submit jobs so many customers have profiles that are disabled or may have missing msgq's etc  that will prevent ICSM 3.0 from running correctly.  To test this,  sign on to the FlashCopy partitions as QLPAR and test submitting a job to ensure it is successful.

  Upgrade process

  Advanced Copy Services for PowerHA on i is delivered as a single library ( QZRDHASM ). For any existing ICSM user, an upgrade library for either a new version or PTF – and should be restored directly over the existing library will MBROPT(*ALL) and ALWOBJDIF(*ALL).  The RUNSETUP command will ensure that any required files are be updated appropriately.   It is normal for 2 objects not restore when upgrading as they are USRSPC's that will not restore one exists.

  ICSM 3.0 uses a new method of storing and distributing CRG data around the cluster. The data is no longer kept in a data CRG; it has been moved into a Device Domain Data space which enables ACS to modify the data from a CRG exit program.
   
  Due to this change, every data CRG used for ACS must be deleted and recreated when upgrading to ICSM 3.0. The steps to do so follow: 

  1. Use DSPCSEDTA to collect the information for each environment
  2. Ensure that all cluster nodes are active.
  3. Use WRKCLU option 9 (Work with cluster resource groups)
  4. Delete the data CRG for each environment
  5. Use CRTCSECRG and CHGCSEDTA to recreate the data CRGs in the new ICSM 3.0 format.

   
  All WRKCSE records must be updated after upgrading to ICSM 3.0. All parameters should be double-checked – especially the new ones for FlashCopy:  Note CSE environments only need to be updated once across the entire cluster,  not on every node.  But don't forget to look at FlahsCopy nodes for environments that do not show up on PPRC nodes.

  • Vary on Source IASP
  • Quiesce Action
  • Connect hosts
  • Wait for completion
  • Completion timeout
  • Exit program and library
  • GMIR CG timeout
  • GMIR CG Failure Action

• Version & Release History (IASP Manager)

  This includes the version and release history for all previously-branded names and predecessors of IASP Manager.

  Development for this set of tools is under constant development.  The Lab Services team has the ability to quickly respond to customer needs with short turnaround times.  As such, there are more frequent build dates, with few or minor changes with each release.  If your current release is working sufficiently to meet your intended needs, there is no requirement to upgrade with each new build.  Simply review the latest additions and/or fixes to determine if an upgrade would be useful.

  To determine the currently-installed version, ADDLIBLE QZRDHASM, and then DSPDTAARA QZRDHASM/BUILD.

  IASP Manager -- Version 4.1

  This is the first and latest IASP Manager version to include code updates from ACS / ICSM toolkits. It is supported for IBM i O/S 7.1 or higher, and is the recommended toolkit version for all current IASP Manager solutions. This is the first version to support broadcast Multi-Target Copy (MTC) solutions, and requires the use of IBM Copy Services Manager (CSM) or complete IBM Spectrum Control solution. Note:  IBM Copy Services Manager (CSM) is NOT related to the previously-branded name for this toolkit -- IASP Copy Services Manager (ICSM). The confusion of the two partly contributed to the current re-branding.

  June 8, 2016

  • Fixed Opt 10 (Display Replication) on Work with SVC PPRC menu (MCH3601 exception)

  June 7, 2016

  • Fixes for GMIR failover for multi-incremental sessions

  May 20, 2016

  • Enhanced detach operation to wait for GMIR to completely pause with consistency

  May 3, 2016

  • Fixed CSM session number not properly converted to hex

  May 2, 2016

  • Fixed error on command string for target volumes on CHGASPCPYD for MMIR session

  April 28, 2016

  • Added missing space for mkflash_GM_Dcopy script

  April 26, 2016

  • Added additional check code for CHGPPRC command

  April 25, 2016

  • Fixed CPF3CF1 error on procedure getSetHostSessionInit

  IASP Manager -- Version 4.0

  This was the initial version of IASP Manager and was only designed for Full System Replication (FSR) with Storwize (now rebranded as Full System Remote Copy under the Full System Manager tools).

  Customers wishing to upgrade from ACS or ICSM toolkits to IASP Manager need to upgrade to IASP Manager 4.1.

  It is supported for IBM i O/S 7.1 or higher, specifically to manage full system replication (remote copy) between two Storwize (V7000, V5000, V3700, Flash V9000) or SVC-based disk subsystems.

  IASP Copy Services Manager (ICSM) -- Version 3.1

  This is the latest and last version of IASP Copy Services Manager (ICSM), due to the re-branding of the name in February 2016. It is supported for IBM i O/S 7.1 or higher, but the preferred version of the toolkit and this set of tools is IASP Manager 4.1. This is the latest version to support cascaded Metro Global Mirror (MGM), and the last version to support Tivoli Storage Productivity Center for Replication (TPC-R) integration.

  April 1, 2016

  • Send IAS0079 informational message during cold flash, waiting for production operations to complete (including QSYSOPR inquiry message reply)

  February 8, 2016

  • Enhanced verification for FlashCopy target

  January 12, 2016

  • Added *DEBUGCRG option to FLAG parameter in CHGBLDFLG command

  August 4, 2015

  • Enhanced STRFLASH to work at the remote copy (PPRC) target node

  July 13, 2015

  • Enhanced building of pausegmir_PT.script for older D-Copy method

  June 29, 2015

  • Corrected authority issue for ENDFLASH

  May 20, 2015

  • Enhancements to multiple commands using clustering on the same node

  April 7, 2015

  • Minor fixes to device domain data (DDD) locking process

  March 12, 2015

  • Enhanced verifications in FlashCopy prior to FLASH_COMPLETE status

  January 5, 2015

  • Fix for SSL Support

  November 2, 2014

  • Enhanced DMPINF command to convert scripts and results files

  Advanced Copy Services (ACS) Toolkit or IASP Copy Services Manager (ICSM) -- Version 3.0

  This toolkit was re-branded from Advanced Copy Services (ACS) Toolkit to IASP Copy Services Manager (ICSM) in March 2014, but still retained "Version 3.0" across that renaming. The latest "new" development for this version was late 2014, with some of the later fixes being retroactively added to updated code bundles. This is the only supported version of this toolkit for customers at IBM i O/S version 6.1.  Customers must have an extended maintenance support contract for version 6.1 in order to receive support for this toolkit version. Limited support is available via contract with Lab Services for higher versions of O/S, but no fixes will be provided for customers at higher O/S releases.Fix requests for IBM i O/S 7.1 or higher will first require an upgrade to ICSM 3.1 (supported) or IASP Manager 4.1 (preferred).

  February 8, 2016

  • Enhanced verification for FlashCopy target   (retroactive fix from later releases)

  March 12, 2015

  • Enhanced verifications in FlashCopy prior to FLASH_COMPLETE status   (retroactive fix from later releases)

  January 5, 2015

  • Fix for SSL Support   (retroactive fix from later releases)

  December 12, 2014

  • (Fixed) STRFLASH PREFLASHED(*YES) WAITONCOMP(*YES) no longer will return successful prematurely
  • (Fixed) STRFLASH PREFLASHED(*YES) CONNHOSTS(*CURRENT) now performs a RLSASPIO RELEASE(*SOFT)

  October 30, 2014

  • Enhanced capability for GMIR FlashCopy while running in Reversed direction

  October 23, 2014

  • (Fixed) Corrected the showgmir_metrics_PT.script to include the -metrics parameter and showgmir_stats_PT.script to include correct session ID

  October 16, 2014

  • (Fixed) Changed behavior of SWPPRC SWITCH(*COMPLETE) when in Reversed direction to include correct node names in QSYSOPR message

  October 7, 2014

  • Enhanced support for RLSASPIO for greater than 3000 volumes on DS storage

  September 10, 2014

  • (Fixed) Removed error with STRFLASH CONNHOSTS(*NO), when IASP of another copy is currently varied on to the FlashCopy node

  September 4, 2014

  • Changed LONGDRAIN from 600 to 90 seconds

  July 7, 2014

  • Increased logging of QYASCHGDDD calls
  • Enhanced authorization checks for DMPINF log files

  June 25, 2014

  • (Fixed) Resume function restored properly after changes made from 5/30/2014 build

  May 30, 2014

  • Allow for multiple FlashCopies to be submitted simultaneously, using lock-and-wait process, and ensure each FlashCopy status is updated correctly

  April 29, 2014

  • Removed error on source node if location doesn't match

  April 8, 2014

  • Remove FlashCopies without session at 7.1
  • Additional checks for node location

  March 21, 2014   (first build as rebranded IASP Copy Services Manager (ICSM) name)

  • Included multi-incremental D-Copy support

  February 19, 2014   (last build as Advanced Copy Services (ACS) toolkit name)

  • Additional logging of QYASSDMO on RLSASPIO RELEASE(*HARD), using the CHGBLDFLG FLAG(*DEBUGDDD)

  January 23, 2014

  • Allowed for QZRDHASM to be part of system library list (QSYSLIBL)

  October 31, 2013

  • (Fixed) RLSCSELCK *JOB not releasing the lock
  • Added functionality to CHKPPRC to discover deleted host connections for a LUN-Switching environment

  October 10, 2013

  • (Fixed) STRFLASH not switching to QLPAR profile prior to first cluster action

  Advanced Copy Services (ACS) Toolkit -- Versions 2.0.x and 2.1.x   (There are no supported versions)

  The last "new" development for of either of these versions was in August 2013, with a few retroactive fix bundles provided for Version 2.1.x as late as March 2015. Any service for these versions of this toolkit should require an upgrade to ICSM 3.0 (for IBM i O/S 6.1), or ICSM 3.1 or IASP Manager 4.1 (IBM i O/S 7.1 or higher) as a new implementation.

  Advanced Copy Services (ACS) Toolkit -- Versions 1.1.x through 1.3.x   (There are no supported versions)

  The last code update for these versions was in December 2010. Any service for these versions of this toolkit should require an upgrade to ICSM 3.0 (for IBM i O/S 6.1), or ICSM 3.1 or IASP Manager 4.1 (IBM i O/S 7.1 or higher) as a new implementation.

  Copy Services Toolkit (CST) -- Versions 5.x through 7.x   (There are no supported versions)

  This toolkit pre-dates IBM i O/S version 6.1 and pre-dates the Advanced Copy Services (ACS) Toolkit. Any service for this toolkit should require an upgrade to ICSM 3.0 (for IBM i O/S 6.1), or ICSM 3.1 or IASP Manager 4.1 (IBM i O/S 7.1 or higher) as a new implementation.  All old CST libraries and IFS directories should be deleted as part of that implementation process.

• ACS and ICSM release versions, features and fixes

  ACS and ICSM release versions, features and fixes

  ICSM 3.0  

  Latest Code bundle   Thursday Oct 31st

  Features added:

  • STRFLASH can be run from any node in the cluster
  • Automatic checking for MMIR in sync when flashing at the MMIR target (DS8K only)
  • Connect and disconnect LUNs from the Flash partition as part of the process

  Fixes

  • 10/31/2013  - RLSCSELCK *JOB not releasing the lock
  • 10/31/2013  - Added functionality to CHKPPRC to discover deleted host connections for a LUN environment
  • 10/10/2013  - STRFLASH not switching to QLPAR profile prior to first cluster action

  ACS 2.1

  Latest code bundle  Thursday Oct 31st

  Fixes

  • 10/31/2013  - RLSCSELCK *JOB not releasing the lock
  • 08/21/2013  - Added functionality to place the cluster node name into the source ASPCPYD to support FlashCopy session with V7R1 TR6
  • 08/08/2013  - Fixed ENDFLASH locking bug where 2 nodes could be locked at the same time but only one was truely locked. This resulted in one node having a status of *FLASHED after the ENDFLASH had completed
  • 07/09/2013  -  added functionality to support TPC-R 5.1.1.1 for MGM customers  ( see install manual for details )
  • 05/21/2013  - fixed mch3601 when reading a large lsfbvol file

  ACS 2.0  ( investigation only  - upgrade to later release for bug support )

  Latest code bndle  02/2013

  ACS 1.1 - ACS13.  

  Upgrade to later release

• Bug Fixes

  IBM i development has fixed a bug in PowerHA with PTF SI48371 (APAR SE47549). After applying this PTF the behavior of STRASPSSN with DS8K is changed.  
  
  Previously we required that neither the Source nor the Target ASPCPYD that we create and manage have a "location" in it  ( i.e., node name ).  With the application of this PTF,  the source ASPCPYD must have a node name. If no location exists, weird cluster name errors will appear.

  To correct the issue, manually enter the name of the source partition node name into the location field of the source ASPCPYD.  

  Note:  Do NOT enter a location into the target ASPCPYD - - otherwise both PowerHA and ACS will try to reject/accept the disk during a flash, and it will fail.