Setting up an ML3-like policy for your SMS management classes

You assign archive policies and archive groups to your SMS management class definitions and the Archive function automatically builds the data set selection criteria that implement the ML3-like storage tier.

About this task

This section tells you how to use the Archive function to set up an "ML3" storage tier. If you need to archive explicitly identified ML2 data sets or archive L0 disk data sets, your task is documented elsewhere:

To use the Archive function to set up an "ML3" storage tier, you specify the SMS management class name, archive days, and archive group information in the AXQMCPOL member of theAdvanced Archive for DFSMShsm parameter library. The Archive process builds the selection criteria automatically from the information in AXQMCPOL. You can code this information manually, or you can use the SMS Archive Policy Editor to code the information in the AXQMCPOL member of the parameter library.

To illustrate how automatic selection criteria generation works, consider an example in which you have coded the following information in the AXQMCPOL member of the parameter library:
*MGMTCLAS  ARCHIVE  ARCHIVE
*  NAME      DAYS    GROUP 
*--------  -------  --------
STANDARD      720   COSGRP1
ARCHIVE        60     *
The AXQMCPOL member is ignored until you remove the CRITERIA DD from the AXQRCHIV job. When you submit the modified AXQRCHIV job, the Archive process reads the contents of the AXQMCPOL member and generates these selection criteria to compare against the ML2 candidate data sets:
//CRITERIA DD *
GROUP_NAME=COSGRP1
MGMTCLASS=STANDARD
#DAYS_SINCE_LASTUSED=00720-99999
GROUP_NAME=ARCHIVE
MGMTCLAS=ARCHIVE
#DAYS_SINCE_LASTUSED=00060-99999
Note: Users at sites that use DFSMShsm ABARS should be aware that ABARS cannot back up directly from the archive media or restore directly to the archive media the way it does with DFSMShsm-migrated files. When automatic Restore is enabled, Advanced Archive for DFSMShsm becomes aware of the ABARS attempt to access the data set and restore it to DFSMShsm. When automatic Restore is not enabled, ABARS cannot back up the archived files. For these reasons, do not archive files that are likely to be backed up by ABARS.

Procedure

  1. Specify the appropriate policy information in AXQMCPOL:
    1. At the Option prompt on the ISPF menu panel, type TSO AXQISPF and then press Enter to start the Advanced Archive for DFSMShsm ISPF interface.
    2. Type 0 at the Option prompt on the Main Menu and then press Enter to display the Settings menu.
    3. Type 5 at the Option prompt on the Settings menu and then press Enter to display the SMS Archive Policy EditorSMS Archive Policy Editor panel.
      The SMS Archive Policy EditorSMS Policy Editor panel displays one row for every SMS management class.
      • If the management class already has an entry in AXQMCPOL, the corresponding Archive Days column shows a numeric value. Additionally, if an archive group was specified for that management class, the corresponding Archive Group column shows an alphanumeric value.
      • An asterisk (*) in the Archive Group column for a management class indicates that no value has been specified for that entry.
    4. Edit the information to assign archive policies and groups to the appropriate management classes.
      • To add an entry for a management class to the AXQMCPOL member, complete these steps:
        1. In the Archive Days column, type an integer in the range 1 - 99999.
        2. In the Archive Group column, type an alphanumeric value (1 - 8 characters in length) that begins with an alphabetic character.
      • To remove an entry from the AXQMCPOL member, remove the value from the corresponding Archive Days column. There is no need to remove the value from Archive Group column for that management class.
    5. When you have completed your edits to the fields on the SMS Policy EditorSMS Archive Policy Editor panel, take the appropriate action.
      • To save your changes and exit the SMS Archive Policy EditorSMS Archive Policy Editor panel, type SAVE at the Option prompt and then press Enter.
      • To discard your changes and quit the SMS Policy EditorSMS Archive Policy Editor, type CANCEL at the Option prompt and then press Enter.
  2. Open SAXQSAMP library member AXQRCHIV for editing.
  3. Provide appropriate job card information.
  4. Replace all occurrences of @HLQ with your data set prefix.
  5. Remove the CRITERIA DD from the AXQRCHIV job.
  6. Optional: If you want to verify before archiving the data that the Archive process is going to produce the expected result, run the Archive job in simulation mode:
    1. Add PARM=SIM to the EXEC control card in the JCL.
    2. Run the simulation job.
    3. Review the information that was written to the ARCHRPT DD to determine which data sets were selected for processing.
      This is an example of the information written to an ARCHRPT report:
      ********************************* TOP OF DATA ********************************************************************** 
VER 1.1      ***SIMULATE***        A D V A N C E D   A R C H I V E  FOR  DFSMShsm   ***SIMULATE***  AXQRCHIV JOB11405
                                                                                                                                    
DATE: 01/30/2018.030  TIME: 05:22:15      CANDIDATE RECORDS PASSED TO ARCHIVE TASK FOR RSPLEX0D           PAGE      1
                                                                                                                                    
 ML/2   BLK/ID   ORIG                 DATA SET NAME                   EXP    SIZE IN KB             RESULTS                         
<VSER> <IN HEX> <VSER> <----------------------------------------> <-DATE-> <--------> <----------------------------->             
                                                                                                                                  
--------------------------------------------------------------------------------------------------------------------
                                                                                                                                  
START OF GROUP:        COSGRP1                                                                                                    
                                                                                                                                  
VD0900 000004B5 R1PD04 #AXQ.#AXQ001.SMS.PS                        ********         16 SIM: ARCHIVE FUNCTIONS BYPASSED             
VD0900 00000982 R1PD00 @AXQ.@AXQ001.SMS.PS                        ********         16 SIM: ARCHIVE FUNCTIONS BYPASSED             
VD0900 0000169D R1PD06 AAXQ.AAXQ001.SMS.PS                        ********         16 SIM: ARCHIVE FUNCTIONS BYPASSED             
VD0900 00001B9F R1PD08 GAXQ.GAXQ001.SMS.PS                        ********         16 SIM: ARCHIVE FUNCTIONS BYPASSED             
VD0900 0000205F R1PD02 JAXQ.JAXQ001.SMS.PS                        ********         16 SIM: ARCHIVE FUNCTIONS BYPASSED             
VD0900 0000251F R1PD15 PAXQ.PAXQ001.SMS.PS                        ********         16 SIM: ARCHIVE FUNCTIONS BYPASSED             
VD0900 000029DD R1PD00 VAXQ.VAXQ001.SMS.PS                        ********         16 SIM: ARCHIVE FUNCTIONS BYPASSED             
VD0900 00002E9D R1PD01 ZAXQ.ZAXQ001.SMS.PS                        ********         16 SIM: ARCHIVE FUNCTIONS BYPASSED             
                                                                                                                                    
SIZE OF PROCESSED GROUP:          0.000GB #DATASETS IN GROUP:                    8                                                 
                                                                                                                                    
*********************************************************************************************************************
                                                                                                                                    
                                                                                                                                    
TOTAL ARCHIVED:                   0.000GB #DATASETS:                             8 #GROUPS PROCESSED:          1                   
                                                                                                                                    
******************************** BOTTOM OF DATA *********************************************************************
    4. If the simulation results are not as you expected them to be, modify your specifications in AXQMCPOL and repeat the simulation until the results are satisfactory.
    5. When the results confirm that all of the inactive data sets that you want to archive will be archived, remove the SIM value from the EXEC control card then go to step 8.
    Note: Initially, it is likely that a large volume of data will meet the policy information that you specify in AXQMCPOL. It is strongly recommended that you run the initial Archive job in simulation mode so that you can review the data that would be selected for archiving before any of the data is actually archived. Note that you can use the ARCHIVE-SELECTION-MAXIMUM-FILES or ARCHIVE-SELECTION-MAXIMUM-GB (or both) parameters to limit the amount of data that is processed by any one Archive job. See Parameters, for more information.
  7. Submit the job for execution.
    Note: Should you need to shut down HSM, you must first stop the Archive job.
  8. Optional: To monitor or stop the Archive process, use the appropriate console command.
    Console command Description
    STATUS When you issue the STATUS command, the Archive process issues a WTO message that shows the following information:

    • The current number of requests that are queued

    • The number of requests that completed successfully

    • The number of requests that failed to complete

    Syntax: F jobname,STATUS

    where jobname is the job name of the job currently executing.
    HALT When you issue the HALT command, the Archive process terminates after the current group of queued requests has been processed. Any remaining candidate data sets that are not yet queued for processing are ignored without any additional processing or reporting.

    Syntax: F jobname,HALT

    where jobname is the job name of the job currently executing.
    HALT,I When you issue the HALT,I command, the Archive process terminates when the current data set in the group of queued requests has been processed. Any remaining candidate data sets that are not yet queued for processing are ignored without any additional processing or reporting.

    Syntax: F jobname,HALT,I

    where jobname is the job name of the job currently executing.

What to do next

Follow the procedures in Verifying the contents of the archive to confirm that the correct data sets were moved to the archive.

If the Archive function issues error messages or verification reveals that the Archive process did not produce the expected results, go on to Creating a candidate rejection report to create a report that provides information about why candidate data sets were not processed.