IBM Support

csv File Format for Copy Set Import

How To


Summary

This document describes how to format a .csv (comma separated values) file for importing copy sets into IBM Copy Services Manager.

Objective

Prepare a .csv file for import into CSM.

Steps

IBM Copy Services Manager provides the ability to populate a session with copy sets by importing a properly formatted .csv file containing the copy set data.
The .csv file is most easily created by using the CSM "Export copy sets" functionality to export the copy sets from an already existing session of the same type (e.g., flash copy, global mirror, etc.) and use that as a template to create your new .csv file. This gives you a file with the correct formatting.
You can also create a file from scratch if you follow the correct format. You can use any editor or spreadsheet software, provided that you save the file in plain text .csv format, taking care to make sure that whatever editor you use does not add special characters (tabs, carriage return / line feeds) or alters the required format in any way.
In general the format is as follows:
1) Commentary header (optional) - each line of the header begins with a pound sign (#) in the first column. The information in the header is not fixed, but generally includes information describing the content of the file. Here is an example:
------- start of example1 ------
#svc
#Global Mirror with Practice
#Aug 9, 2010 3:30:22 PM
#This file was automatically generated by Copy Services Manager
------- end of example1 ------
2) Session definition - this line is required and describes the type of session being defined. Each field represents a site for the copy services operations. Designators specify host source and target volumes (Hn, i.e. H1, H2, etc.), journal volumes (Jn, i.e., J1, J2, etc.), intermediate volumes (In, i.e., I1, I2, etc.) where 'n' (the number) represents the site location for the operation. Here is an example showing the header followed by the session definition:
------- start of example2 ------
#newsession
#Global Mirror w/ Practice (ESS/DS)
#Nov 4
H1,H2,J2,I2
------ end of example2 ------
3) Copy sets - the lines that follow after the session type definition record are the actual copy sets, one line for each copy set. Each line must have the same number of fields as the session type definition, as each field defines the volume at the source or target site to be used in the copy operation. The format of each field varies slightly depending on the type of storage device involved in the session, but generally follows:
DS family devices -
[devicetype]:[model.serial]:VOL:[volid]
SVC family devices -
SVC:VOL:[svcdeviceid]:[volid]
Examples:
------ start of example3 ------
#tinysession1
#metro global mirror
#february 15,2021
H1,H2,H3,J3
DS8000:2107.AA123:VOL:1400,DS8000:2107.AA456:VOL:1400,DS8000:2107.BB456:VOL:1A00,DS8000:2107.BB456:VOL:1E00
------ end of example3 ------
------ start of example4 ------
#tinysession2
#svc global mirror with practice
#february 15,2021
H1,I2,H2
SVC:VOL:1.22.333.444:0:0,SVC:VOL:1.22.333.555:0:151,SVC:VOL:1.22.333.555:0:128
SVC:VOL:1.22.333.444:0:1,SVC:VOL:1.22.333.555:0:91,SVC:VOL:1.22.333.555:0:173
------ end of example4 ------
Once the .csv file is fully populated with all of the copy sets for the session, it is ready to be imported into the corresponding CSM session.
Note: regularly exporting .csv files for each of your CSM sessions and keeping them up to date and stored in a safe location is a best practice for the CSM Administrator. These can be useful to recreate sessions in a recovery scenario, or to help bring up a new CSM server installation.

Additional Information

For information on how to import copysets in IBM Copy Services Manager, or to export .csv files for your existing sessions please refer to the IBM Copy Services Knowledge Center.

Document Location

Worldwide

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSESK4","label":"IBM Copy Services Manager"},"ARM Category":[{"code":"a8m0z0000001iIqAAI","label":"Others"}],"ARM Case Number":"TS005022066","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
15 February 2021

UID

ibm16415665

Page Feedback