Performing Cloud Data Sets activation

Creating a new PROGxx member

1. Create a new PROGxx member for the CDS activation in the appropriate PARMLIB directory. You can find an example in SAMPLIB PROGM9.
   
   The new member should include the following commands:

   LPA ADD DSN(SYS2.MODEL9.V270.LOADLIB) MOD(ZM9019CW)
   LPA ADD DSN(SYS2.MODEL9.V270.LOADLIB) MOD(ZM9019CC)
   LPA ADD DSN(SYS2.MODEL9.V270.LOADLIB) MOD(ZM9OCEX4)
   EXIT ADD EXITNAME(OCE_FILESTART)    MOD(ZM9OCEX4) ABENDNUM(100,CONSEC)
   EXIT ADD EXITNAME(OCE_FILEEND)      MOD(ZM9OCEX4) ABENDNUM(100,CONSEC)
   EXIT ADD EXITNAME(OCE_FILEVALIDATE) MOD(ZM9OCEX4) ABENDNUM(100,CONSEC)
   EXIT ADD EXITNAME(OCE_LABELANOMALY) MOD(ZM9OCEX4) ABENDNUM(100,CONSEC)
   EXIT ADD EXITNAME(OCE_VOLUMEMOUNT)  MOD(ZM9OCEX4) ABENDNUM(100,CONSEC)

2. Run the following command:

   SET PROG=M9

3. To enable the new member to be loaded after each IPL, add the SET PROG=xx command to the site-standard COMMNDxx member. 

   Error

   Warning

   Do not use the IEASYSxx PROG=M9 statement. Using this statement results in ADD EXIT action failures because the LPA ADD statements take effect only after the IPL ends, not while it proceeds.

Installing CDS started tasks

Specify the tape drives range previously defined in the IODF during Preparing-to-activate-Cloud-Data-Sets for one of the started tasks (STCs) related to the CDS installation.

To avoid manual intervention, add the installation STCs to the IPL procedure.

Task 1: To initialize the CDS STC

1. Customize the M9INSCDS member provided in the BMC AMI Cloud SAMPLIB directory as follows: 

   • BUFSIZE sets the amount of memory to allocate for each virtual device. 

     Warning

     Important

     CDS allocates additional x MB of system memory.

     x = 3 × Number of Devices × BUFSIZE.

     For example, when using default BUFSIZE with 16 tape drives, the formula is as follows: x = 3 × 16 × 5 = 240 MB

   • Set the agent's minimum heap size to 2GB in the model9-stdenv.sh configuration file by using the AGENT_MEMORY setting.

   • For each virtual device, repeat the DEFINE step with the appropriate unit address. For example, to define three devices of range 1100–1102 use:

     //INSTALL  EXEC PGM=ZM9IAMM,PARM='INSTALL,BUFSIZE=0005'    
     //STEPLIB  DD  DISP=SHR,DSN=SYS2.MODEL9.V270.LOADLIB       
     //*                                                        
     //D1100  EXEC PGM=ZM9IAMM,PARM='DEFINE=1100,XCF=M9ARCH'
     //STEPLIB  DD  DISP=SHR,DSN=SYS2.MODEL9.V270.LOADLIB        
     //D1101  EXEC PGM=ZM9IAMM,PARM='DEFINE=1101,XCF=M9ARCH'
     //STEPLIB  DD  DISP=SHR,DSN=SYS2.MODEL9.V270.LOADLIB        
     //D1102  EXEC PGM=ZM9IAMM,PARM='DEFINE=1102,XCF=M9ARCH'
     //STEPLIB  DD  DISP=SHR,DSN=SYS2.MODEL9.V270.LOADLIB 

2. When the member is ready, copy it to your site PROCLIB and start the STC by using the START operator command:

   S M9INSCDS
3. Verify that the STC ended on return code zero.

Task 2: To copy the STC uninstaller

Copy the M9UNICDS member to your site PROCLIB. You can use this STC to uninstall Cloud Data Set from the current environment.

Task 3: To customize the Virtual Devices Hook Installer STC

1. Customize the M9VDEV member provided in the BMC AMI Cloud SAMPLIB directory as follows:
   • Update the device range to be controlled by the Cloud Data Set feature.
   • Update the VOLSER prefix according to the defined tapes in To define dummy tape volumes.
   • Update the Storage Group Name selected for Cloud processing.

   • Add the TIME=1440 parameter to the M9VDEV EXEC statement. 

     Warning

     Important

     While the SMS storage group can be of any length, the value of the JCL SG variable must be exactly 8 characters. If needed, pad it with trailing underscores. For example, SG='M9CDS___'. 

     Error

     Warning

     Do not change the CHPID and SCHNO parameters without technical advice from BMC.

2. When the member is ready, copy it to your site PROCLIB and start the STC using the START operator command:

   S M9VDEV

   The STC is expected to remain running. You can expect the following output:

   ZM9017I MODEL9 VTAPE STARTING...     
   ZM9004I PST =0x810DD0F0              
   ZM9003I HOOK(ZM9SIOTP),DEV(0570-057F)
   ZM9002I COMM=0x1D050000              
   ZM9004I SSCQ=0x81281100              
   ZM9016I MODEL9 VTAPE STARTED       

Task 4: To vary the tape library online

Issue the following command to vary online the manual tape library:

You should see the following message in the syslog and OAM address space: 

Task 5: To vary BMC AMI Cloud tape drives online

When M9VDEV is up and M9INSCDS successfully installed, you can vary the BMC AMI Cloud tape drives online:

Task 6: To display the MTL Status

To display the status of the MTL issue the following command:

You should see an output similar to this:

ONL DRV and AVL DRV should contain the number of devices that you varied online.

Making changes after activating CDS