Preparing to activate Cloud Data Sets
Select FICON CHPIDs
Select one or more real FICON CHPIDs to associate with the virtual devices.
To define more than 16 devices, you must create control unit (CU) definitions for each range. Each CU must have its own LIBPORT-ID set.
In the Hardware Configuration Definition (HCD), define the CU as NOCHECK:
.----------------------------Add Control Unit------------------------------------.
! !
! !
! Specify or revise the following values. !
! !
! Control unit number . . . . 1100 + !
! Control unit type . . . . . NOCHECK + !
! !Connect the new CU to existing online FICON CHPIDs:
Select Processor / CU Row 1 of 3 More:
Select processors to change CU/processor parameters, then press Enter.
Control unit number . . : 1100 Control unit type . . . : NOCHECK
---------------Channel Path ID . Link Address + ---------------
/ Proc.CSSID 1------ 2------ 3------ 4------ 5------ 6------ 7------ 8------
_ POO5EFF8.0 50 51 52 53 _______ _______ _______ _______Specify an arbitrary free CUADD (for example, 0D—a unit address of 00 and a unit range of 16).
Select Processor / CU Row 1 of 3 More: < >
Command ===> -------------------------------------------------------- Scroll ===> PAGE
Select processors to change CU/processor parameters, then press Enter.
Control unit number . . : 1100 Control unit type . . . : NOCHECK
CU ----------------------Unit Address . Unit Range + ----------------
/ Proc.CSSID Att ADD+ 1----- 2------- 3------ 4------- 5------- 6------ 7------- 8------
_ POO5EFF8.0 Yes 0D 00.016 -------- -------- -------- ------- ------- -------- -------Add the new 3480 devices with matching device numbers and connect them to the newly created CU (for example, 1100).
+-------------------------------- Add Device ---------------------------------+
| |
| |
| Specify or revise the following values. |
| |
| Device number . . . . . . . . 1100 + (0000 - FFFF) |
| Number of devices . . . . . . 16 |
| Device type . . . . . . . . . 3480 + |
| |
| Serial number . . . . . . . . __________ |
| Description . . . . . . . . . |
| |
| Volume serial number . . . . . ______ (for DASD) |
| |
| PPRC usage . . . . . . . . . . _ + (for DASD) |
| |
| Connected to CUs . . 1100 ____ ____ ____ ____ ____ ____ ____ + |Specify a unit address of 00.
+---------------------- Device / Processor Definition -----------------------+
| Row 1 of 1 |
| |
| Select processors to change device/processor definitions, then press |
| Enter. |
| |
| Device number . . : 1100 Number of devices . : 16 |
| Device type . . . : 3480 |
| |
| Preferred Device Candidate List |
| / Proc.CSSID SS+ UA+ Time-Out STADET CHPID + Explicit Null |
| _ POO5EFF8.0 0 00 No Yes __ No ___ |Connect the new devices to the appropriate configuration ID:
+----------- Define Device to Operating System Configuration -----------+
| Row 1 of 1 |
| |
| Select OSs to connect or disconnect devices, then press Enter. |
| |
| Device number . : 1100 Number of devices : 16 |
| Device type . . : 3480 |
| |
| Subchannel Sets used in processor configurations : 0 |
| |
| / Config. ID Type SS Description Defined |
| s MOD9 MVS MOD9 IODF |Configure the following values for the new devices.
+-------------------- Define Device Parameters / Features --------------------+
| Row 1 of 10 |
| |
| Specify or revise the values below. |
| |
| Configuration ID . : MOD9 MOD9 IODF |
| Device number . . : 1100 Number of devices : 16 |
| Device type . . . : 3480 |
| |
| Parameter/ |
| Feature Value + R Description |
| OFFLINE Yes Device considered online or offline at IPL |
| DYNAMIC Yes Device supports dynamic configuration |
| LOCANY Yes UCB can reside in 31 bit storage |
| LIBRARY NO Device supports auto tape library |
| AUTOSWITCH NO Device is automatically switchable |
| LIBRARY-ID 99999___________ 5 digit library serial number |
| LIBPORT-ID 01______________ 2 digit library string ID (port number) |
| MTL Yes Manual Tape Library (NOTE: PORTID LIMIT=32) |
| SHARABLE No Device is Sharable between systems |
| COMPACT No Compaction |- Create and assign the new devices to a new esoteric name (for example, CLOUD). Databases such as Db2 require a valid esoteric to function properly.
- Generate a new production input/output definition file (IODF).
- Activate the new IODF to apply both software and hardware changes.
- Issue the DISPLAY UNITS operator command to verify that the device has been added:
D U,,,1100,1 - Issue the DISPLAY MATRIX for DEVICE operator command to verify the device I/O configuration:
D M=DEV(1100)
Creating Control-M/Tape rules
Create two rules, one to ignore the CDS volumes and another to ignore the CDS VDEVs:
From the IOA primary option menu, select TR (Rule Definition).
Select the rule library and table that are used by your system.
When Control-M/Tape starts, it automatically reads and loads the rule tables in the member referenced in the DD statement DARULLST. The supplied default member RULLIST is in the Control-M/Tape PARM library.----------------- CONTROL-N/Tape RULE DEFINITION ENTRY PANEL ---------------(TR)
COMMAND ===>
SPECIFY LIBRARY, TABLE NAME, RULE NAME
LIBRARY ===> rules LIBRARY
TABLE ===> r table (Blank for table selection list)
RULE ===> (Blank for rule selection list)
AUTOMATIC RULE SORTING ===> Y (Y/N)
SHOW SCHEDULING CRITERIA ===> (Y/N)
SHOW RULE DOCUMENTATION ===> (Y/N)
AUTO-SAVE DOCUMENTATION ===> (Y/N)- Create the UCB rule as follows:
- In ON UCB, specify all the CDS VDEVs and specify A for And.
- In ON DATASET, specify *.
- For both types of requests, select OD DYNVOL and enter I.
Select DO BYPASS = YES
- Create the VOLSER rule:
- Specify the prefix for the BMC AMI Cloud volumes and specify A for And.
- In ON DATASET, specify *.
- For both types of requests, select OD DYNVOL and enter I.
Select DO BYPASS = YES
- Exit the rule definition panels. Make sure that you select SAVE when exiting.
- Activate the new Control-M/Tape rules by issuing S CTTINIT,PARM='RELOAD,TBLT=RULE'. Control-M/Tape now ignores the CDSs.
Configuring DFSMSrmm (RMM)
Choose a two–alphabetic character tape VOLSER name prefix, such as MA, for BMC AMI Cloud to use.
The following FACILITY profiles are needed to allow the M9AGENT to update the library and allow all users to ignore the M9 volumes during RMM processing:
RDEFINE FACILITY STGADMIN.EDG.IGNORE.TAPE.NORMM.MA* UACC(UPDATE)
SETR REFRESH RACLIST(FACILITY)
When changing the default prefix for BMC AMI Cloud volumes from 'MA' to a different value, update the RDEFINE command above to use the correct volume name prefix.
To avoid conflicts with RMM tapes, add the following statements to your EDGRMMxx configuration file:
OPENRULE VOLUME(MA*) TYPE(NORMM) ANYUSE(IGNORE)
PRTITION VOLUME(MA*) TYPE(NORMM) SMT(IGNORE)
On all the relevant systems, refresh the RMM configuration by using the following operator command:
Connecting STCs in RACF
Connect the three CDS STCs to the user and group that BMC AMI Cloud Agent (M9AGENT) is currently in using:
RDEFINE STARTED M9UNICDS.** STDATA(USER(M9USER) GROUP(SYS1))
RDEFINE STARTED M9INSCDS.** STDATA(USER(M9USER) GROUP(SYS1))
SETR REFRESH RACLIST(STARTED)
If you are using the IEC.TAPERING FACILITY profile, enable READ access to allow reading the data from BMC AMI Cloud volumes.
Use the following command to allow access to specific users:
Use the following commands to enable the CDS installer to perform dynamic LPA updates:
PERMIT CSVDYLPA.ADD.IGG019CC CLASS(FACILITY) ID(M9USER) ACC(UPDATE)
PERMIT CSVDYLPA.DELETE.IGG019CW CLASS(FACILITY) ID(M9USER) ACC(UPDATE)
PERMIT CSVDYLPA.DELETE.IGG019CC CLASS(FACILITY) ID(M9USER) ACC(UPDATE)
Setting up the Object Access Method subsystem
To set up a manual tape library, make sure that the Object Access Method (OAM) and STC are active in the system. To start the OAM subsystem and address space, see the IBM documentation.
Configuring DFSMS
Perform the procedures in this section to associate a new SMS manual tape library to DFSMS by using the SMS tape storage group and ACS routines changes.
On the ISMF panels, make sure that you are defined as an administrator in option 0.0. If you had to change your mode to administrator, exit the screens and enter them again to see the new options available for administrators.
To define a new MTL
- On ISMF, select option 10.3 to manage tape libraries.
Select a new library name according to your site standards and select option 3 to define a new one.
TAPE LIBRARY APPLICATION SELECTION
To Perform Library operations, Specify:
CDS Name . . . . . . . 'SYS1.DFSMS.SCDS'
(1 to 44 Character Data Set Name or 'Active')
Library Name . . . . . M9MTL (For Tape Library list, fully or
Partially Specified or * for all)
Select one of the following options :
3 1. List - Generate a list of Libraries
2. Display - Display a Library
3. Define - Define a Library
4. Alter - Alter a LibrarySpecify the same library ID specified on the IODF (99999).
TAPE LIBRARY DEFINE Page 1 of 4
SCDS Name . : SYS1.DFSMS.SCDS
Library Name : M9MTL
To Define Library, Specify:
Description ==>
==>
Library ID . . . . . . . . . . . 99999 (00001 to FFFFF)
Console Name . . . . . . . . . .
Entry Default Data Class . . . .
Entry Default Use Attribute . . P (P=PRIVATE or S=SCRATCH)
Eject Default . . . . . . . . . K (P=PURGE or K=KEEP)- In the Entry default Use Attribute field, specify P (Private).
- In the Eject Default field, specify K (Keep).
Page down and specify YES in the Initial Online Status field for the relevant LPARs.
TAPE LIBRARY DEFINE Page 3 of 4
SCDS Name . : SYS1.DFSMS.SCDS
Library Name : M9MTL
Initial Online Status (Yes, No, or Blank):
M9L1 ===> NO
To define a new storage group
- On ISMF, select option 6 to manage storage groups.
Select a new storage group and give it a name according to your site standards. Use storage group type TAPE and select option 3 to define it to SMS.
STORAGE GROUP APPLICATION SELECTION
To perform Storage Group Operations, Specify:
CDS Name . . . . . . SYS1.DFSMS.SCDS
(1 to 44 character data set name or 'Active' )
Storage Group Name SGM9CDS (For Storage Group List, fully or
partially specified or * for all)
Storage Group Type TAPE (VIO, POOL, DUMMY, COPY POOL BACKUP,
OBJECT, OBJECT BACKUP, or TAPE)
Select one of the following options :
3 1. List - Generate a list of Storage Groups
2. Display - Display a Storage Group (POOL, OBJECT or TAPE only)
3. Define - Define a Storage Group
4. Alter - Alter a Storage Group
5. Volume - Display, Define, Alter or Delete Volume InformationSpecify the same BMC AMI Cloud SMS manual tape library that you have defined in the previous step and select Y to update the storage group status.
TAPE STORAGE GROUP DEFINE
Command ===>
SCDS Name . . . . . : SYS1.DFSMS.SCDS
Storage Group Name : SGM9CDS
To DEFINE Storage Group, Specify:
Description ==> MODEL9 CLOUD DATA SET TAPE STORAGE GROUP
==>
Library Names (1 to 8 characters each):
===> M9MTL ===> ===> ===>
===> ===> ===> ===>
DEFINE SMS Storage Group Status . . Y (Y or N)Make sure to enable the system by using this storage group.
SMS STORAGE GROUP STATUS ALTER Page 1 of 2
Command ===>
SCDS Name . . . . : SYS1.DFSMS.SCDS
Storage Group Name : SGM9CDS
Storage Group Type : TAPE
To ALTER Storage Group System/ ( Possible SMS SG Status
Sys Group Status, Specify: for each:
- Pool SG Type
System/Sys SMS SG System/Sys SMS SG NOTCON, ENABLE, DISALL
Group Name Status Group Name Status DISNEW, QUIALL, QUINEW
---------- ------ ---------- ------ - Tape SG Type
M9L1 ===> ENABLE ===> NOTCON, ENABLE,
===> ===> DISALL, DISNEW
===> ===> - Copy Pool Backup SG Type
===> ===> NOTCON, ENABLE )
===> ===> * SYS GROUP = sysplex
===> ===> minus Systems in the
===> ===> Sysplex explicitly
===> ===> defined in the SCDS
To update the system ACS routines
Update the storage class and storage group ACS routines.
Use the ACS routines’ different variables to redirect the jobs, users, or data sets that you want to use with Cloud Data Sets to the appropriate classes:
- Storage Class—Assign any storage class to indicate that the data sets are SMS managed.
- Storage Group—Assign the storage group that you created in the previous step for Cloud Data Sets.
For example, you can redirect any UNIT=CLOUD to the BMC AMI Cloud Tape storage group.
To activate the SMS changes
- Use ISMF option 7.2 to translate the new storage class and storage group ACS routine changes made in previous steps.
- Use ISMF option 8.5 to activate all changes made from the SCDS to the ACDS.
Defining a z/OS volume catalog
To use Cloud Data Sets (CDSs), you must define a volume catalog (VOLCAT) and dummy tape volumes.
To define the VOLCAT
CDSs require approximately 60,000 tape volsers, so we highly recommend creating a dedicated VOLCAT just for the CDS tapes.
In the following example of defining a VOLCAT for BMC AMI Cloud CDS tape volumes, replace x with the starting character of the volume entries. For example, for volumes starting with MAxxxx, the VOLCAT should be hlq.VOLCAT.VM.
hlq should match the hlq of hlq.VOLCAT.VGENERAL. For more information about VOLCAT naming conventions, see "Defining Names for a Tape Volume Catalog" in the IBM documentation.
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
DEFINE USERCATALOG -
(NAME(hlq.VOLCAT.Vx) -
VOLCATALOG -
VOLUME(volser) -
CYLINDERS(100 20))
/*
To define dummy tape volumes
Use CDSVLENJ to define the volume entries. Supply the volume prefix (PREFIX) and tape library (MTLNAME) defined in the previous steps.
Make sure that the first letter of the prefix matches the last letter of the specific VOLCAT defined in the previous steps.
For example, if you selected MA for volume prefix and M9MTL for the tape library, then use the following script:
// SET MTLNAME=M9MTL
// SET STARTALI=''
// SET STARTVER=''
The script defines volume entries 'MAAA10' up to 'MAZZ99'. The volume names are in the format ppaavv:
- pp—2 alphabetical characters representing the volume prefix
- aa—2 alphabetical characters representing the alias
- vv—2 digits representing the version
Use the following parameters to start the script at a customized point:
- STARTALI (start alias)—Defines the starting alias point for the script. For example, STARTALI='BB' sets the script to define volumes from 'MABB10' to 'MAZZ99'.
- STARTVER (start version)—Defines the starting version point for the script. For example, STARTALI='BB' &amp; STARTVER='77' sets the script to define volumes from 'MABB77' to 'MAZZ99'. Version '77' is used once. After reaching volume 'MABB99', the script defines 'MABC10', that is version '10' (the default starting point).
Where to go from here