DFSMShsm to CA Disk Conversion › Convert DFSMShsm to CA Disk

Convert DFSMShsm to CA Disk

To convert DFSMShsm to CA Disk:

1. Prepare all CA Disk jobs for the daily/weekly/monthly process. (All functions with CA Disk software instead DFSMShsm.)
2. Stop all DFSMShsm-tasks except AUTOMATIC RECALL.
3. Review and submit the CREATEFD member.

   This job creates records from the BCDS and MCDS Control Data Sets and loads them into your CA Disk Files Data Set. The job creates your base Files Data Set used in production. CA Disk can do record maintenance over both DFSMShsm and CA Disk data.

   Command Syntax

   CREATEFD SGIFOFFL=
   

   SGIFOFFL=

   (Optional). When the SMS data set source volume is offline and you cannot determine a Storage Group, use this command to assign a new storage group.

   After CREATEFD has executed, you can submit RPTJCL00, RPTJCL01, RPTJCL02, RPTJCL05, and RPTJCL06 to verify that the data sets are ready for conversion.

4. Update the CA Disk Sysparms member for the DSNDLPEX user exit for a value of ADSHC010. The system issues a DELETE to DFSMShsm when a DFSMShsm pseudo DSNINDEX record is deleted. This exit cleans up and frees the resources that are used in the BCDS/MCDS before being converted.

   Update the CA Disk Sysparms member for the RESCRNEX user exit for a value of ADSHC011. When the system finds a DFSMShsm pseudo DSNINDEX record during restore, this exit issues a RECOVER/RECALL to DFSMShsm to restore the data set.

5. Update the CA Disk Sysparms member for the RESCRNEX user exit for a value of ADSHC011. When a DFSMShsm pseudo DSNINDEX record is found during restore, this exit issues a RECALL to DFSMShsm to restore the data set.
6. Update the CA Disk Sysparms member for the DINXUFEX user exit for a value of ADSHC012. After conversion, this exit issues a delete to DFSMShsm to clean up and free the resources that are used in the BCDS/MCDS.
7. Start the daily work with CA Disk using the Files Data Set created in Step 3.
8. Review the HSMGEN2 member.

   This job sorts the BCDS records created in Step 3 into VOLSER and file sequence number. The job creates the DFSMShsm and CA Disk commands in VOLSER sequence. The commands are bracketed with comments indicating DFSMShsm VOLSER and space to recover the data sets on the volume. The JCL4ML1 DD statement points to the model JCL used for data sets stored on ML1 and the JCL4ML2 to the model for ML2. Update these models to suit the requirements of your installation (members HSMCONB1 and HSMCONB2 of the INSTALL library). A SYSIN command controls the number of DFSMShsm volumes that are selected for processing.

   Command Syntax

   CONVERT	VOLCOUNT=nn,SIM,ML=,NEWHLQ=,STORGRP=,SMSVOL=,
   

   	SMSUNIT=,NSMSVOL=,NSMSUNIT=,BYPERRORS=
   

   VOLCOUNT=nn

   Specify a one- to two-digit number indicating the number of DFSMShsm volumes to be converted. 99 indicates you want to convert all of the volumes.

   SIM

   Specifies a simulation run. In simulate mode, CA Disk produces messages and reports as if processing had taken place in LIVE mode, but no data sets are altered.

   To execute the JCL in LIVE mode after verifying that the results from the SIMULATE run are as expected, remove this parameter.

   ML=

   Specify either 1 or 2 to select either ML1 or ML2 for conversion. Default is 2.

   NEWHLQ=

   A high-level qualifier to be assigned to each data set selected. Default is H2DCON.

   STORGRP=

   Enter the Storage Group name that contains the volumes where the data sets to select reside. If the backup source volume no longer exists, add it to the proper Storage Group definition for this parameter to be applicable. Optionally, you can specify the SGIFOFFL= parameter in the CREATEFD JCL to assign a new Storage Group to the backed-up data set.

   SMSVOL=

   Specify the target VOLSER that the conversion process uses to retry the RECOVER of SMS-managed data sets in case of failure to RECOVER to the original VOLSER.

   SMSVOL= can only be specified together with SMSUNIT=.

   SMSUNIT=

   Enter the unit type to be used with the SMSVOL= parameter. The supported values are 3380, 3390, and 9345.

   NSMSVOL=

   Specify the target VOLSER that the conversion process uses to retry the RECOVER of non-SMS managed data sets in case of failure to RECOVER to the original VOLSER.

   NSMSVOL= can only be specified together with NSMSUNIT=.

   NSMSUNIT=

   Enter the unit type to be used with the NSMSVOL= parameter. The supported values are 3380, 3390, and 9345.

   BYPERRORS=

   Specify one of VSAM, NONVSAM, ALL or NONE to bypass the error and continue processing if errors are found for any of them to stop processing after the first error. This parameter is optional. Default is NONE.

9. Review the HSMGEN1 member.

   This job sorts the MCDS records, created in Step 3, into VOLSER and file sequence number. This job creates the DFSMShsm and CA Disk commands in VOLSER sequence. Messages are printed indicating the DFSMShsm VOLSER and the space to recover the data sets on the volume. The DD statement JCL4ML1 points to the model JCL used for data sets stored on ML1 and JCL4ML2 to the model for ML2. Update these models to suit the requirements of your installation (members HSMCONM1 and HSMCONM2 of the INSTALL library). A SYSIN command controls the number of DFSMShsm volumes that are selected for processing.

   Decrease processing time by splitting the MCDS records into separate data sets and running multiple HSMGEN1 jobs concurrently. Multiple jobs mean more space that is used and more ML1 and ML2 units that are used during processing.

   Two methods exist to run multiple jobs:

   1. Create separate jobs that are based on the full VOLSER list and then cut it into pieces.

      We executed two jobs in parallel. Each job creates a number of records (15000 in the sample) that are treated and submitted with the next job. The samples are named HSMMIGnn. You can find them in our CCUWJCL library.

      Create parallel JCLs which manage the VOLSER one by one. Each new submit removes the first VOLSER on the list. Each JCL submitted once automatically starts the other. Only HSMCOV01 creates the complete VOLSER list. Then a loop starts with HSMCOV02 and HSMCOV03. The loop continues until there are no more tapes to convert.

   Command Syntax

   CONVERT VOLCOUNT=nn,SIM,ML=,STORGRP=,SMSVOL=,
   	     SMSUNIT=,NSMSVOL=,NSMSUNIT=,BYPERRORS=
   

   VOLCOUNT=nn

   Specify a one- to a two-digit number indicating the number of DFSMShsm volumes to be converted. Specifying 99 converts all volumes.

   SIM

   Specifies a simulation run. In simulate mode, CA Disk produces the normal messages and reports as if processing had taken place in LIVE mode. CA Disk does not alter any data sets.

   After verifying that the results from the SIMULATE run are as expected, remove this parameter to execute the JCL in LIVE mode.

   ML=

   Specify either 1 or 2 to select either ML1 or ML2 for conversion. Default is 2.

   STORGRP=

   Enter the Storage Group name that contained the volumes where the data sets to select resided.

   SMSVOL=

   If RECALL to the original VOLSER fails, specify the target VOLSER that the conversion process uses to retry the RECALL of SMS managed data sets.

   SMSVOL= can only be specified together with SMSUNIT=.

   SMSUNIT=

   Enter the unit type to be used with the SMSVOL= parameter. The supported values are 3380, 3390, and 9345.

   NSMSVOL=

   If RECALL to the original VOLSER fails, specify the target VOLSER that the conversion process uses to retry the RECALL of SMS managed data sets.

   NSMSVOL= can only be specified together with NSMSUNIT=.

   NSMSUNIT=

   Enter the unit type to be used with the NSMSVOL= parameter. The supported values are 3380, 3390, and 9345.

   BYPERRORS=

   Specify one of VSAM, NONVSAM, ALL, or NONE to bypass the error and continue processing if errors are found for any of them to stop processing after the first error. This parameter is optional. The default is NONE.

10. Evaluate the results in SIM mode from the HSMGEN1 and HSMGEN2. Using the SIM mode, you can see how much space you require to recover the data sets on the DFSMShsm volumes.
    • The allocated tracks from each data set are added and the total is printed at the end of each processed volume.

      Specify one of VSAM, NONVSAM, ALL or NONE to bypass an error and continue processing if errors are found for any of them to stop processing after the first error. This parameter is optional and NONE is the default. To process the backup versions of a data set, a pseudo HLQ is needed because the data set can exist. Although a new HLQ is used to allocate the data set, all of the information CA Disk requires from the BSDS is maintained in the DSNINDEX record. Only the ARCHVOL data is updated. Since a new HLQ is used, your allocation product can use this HLQ to direct the DFSMShsm recovery to a stand-alone volume group. Doing this relieves any space constraints in the original groups.

    • Submit both jobs in LIVE mode as many times as required to convert the backups and archives from DFSMShsm. Once the commands for a volume have been generated, it is marked as converted so you can rerun the jobs as many times as needed.
11. Verify the conversion by executing RPTJCLA3, RPTJCL03, and RPTJCL04 report jobs. They are based on BCDS reporting compared with Files data set entries.
12. You can shut down HSMGEN1 or HSMGEN2 conversion jobs early and gracefully by using HSMREPLY. A graceful shutdown allows the jobs to complete all current work in progress. The jobs then produce the normal reports of error conditions and the work is successfully completed before early job termination.

    With HSMREPLY active, message “4570 REPLY 'END' TO TERMINATE HSMGEN# PROCESSING” is issued to the operator at the beginning of the job. This message remains on the console until the job finishes. Replying END stops the job early.