Archiving explicitly identified ML2 data sets

You specify the data set selection criteria that the Archive function compares to the MCDS records to evaluate the candidate ML2 data sets. Data sets that meet the criteria are then moved to the archive.

1. Determine what criteria you want to use for classifying ML2 data sets as inactive:
   1. Review the information and examples that are provided in Selection criteria keyword reference for Archive function, and decide which data set selection criteria are best suited for classifying inactive data at your site.
   2. For each of the data set selection criteria keywords that you decide to use, determine what values to use.
      Be aware that some data set selection criteria are applicable only when the inactive data resides on disk (L0).
   3. If you need to exclude some data sets from Archive processing, determine which data set selection criteria are best suited for identifying the exception data sets.
   4. For each of the exclusion criteria keywords that you decide to use, determine which values will successfully identify those data sets that you want excluded from the archive process.
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. Provide the data set selection criteria that will classify candidate data sets as inactive and the criteria that will exclude data sets from Archive processing. Use the information and examples that are provided in Selection criteria keyword reference for Archive function, as a guide for criteria keyword specification.
   • You may code the data set selection criteria in the job itself.
   • You may code the data set selection criteria in member CRITERIA of the product parameter library.
6. Add the ARCHIVE_SOURCE=ML2 data set selection criteria to the rest of your data set selection criteria.
   Do not include any blank spaces in your specification. For example, ARCHIVE_SOURCE=ML2 is valid, but ARCHIVE_SOURCE= ML2 and ARCHIVE_SOURCE = ML2 are not valid specifications.

   Note: Your AXQRCHIV JCL can include multiple ARCHIVE_SOURCE= criteria, but Archive processing honors only the first occurrence. If you omit the ARCHIVE_SOURCE= criteria from the JCL, Archive processing assumes that the candidate data sets are ML2 data sets.
7. Optional: If you want the Archive process to use a flat file that contains the unloaded contents of the HSM MCDS, rather than the MCDS itself, add a //FLATMCDS DD statement to the JCL.
   Here is an example of a //FLATMCDS DD statement:

   //FLATMCDS DD DISP=SHR,DSN=ARCHMGR.MCDSFLAT.OUTPUT

   //FLATMCDS DD DISP=SHR,DSN=dsname

   where dsname is the name of the flat file into which the MCDS contents were copied.

   Note: When the //FLATMCDS DD statement is present in the Archive JCL, Archive processing bypasses the function that determines the catalog status of the candidate data sets and the function that determines the calculated expiration date of the candidate data sets.
8. Optional: If you want to verify before archiving the data that your selection criteria are 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:

      VER 1.1                                   A D V A N C E D  A R C H I V E  FOR  DFSMShsm             AXQRCHIV JOB09763
      DATE: 10/10/2016.284  TIME: 05:11:01   CANDIDATE RECOREDS PASSED TO ARCHIVE TASK FOR PLEXZ0A             PAGE      1
      
       ML/2   BLK/ID   ORIG                 DATA SET NAME                 EXP    SIZE IN KB             RESULTS
      <VSER> <IN HEX> <VSER> <------------------------------------------<-DATE-> <--------> <----------------------------->
      ---------------------------------------------------------------------------------------------------------------------
      START OF GRUP:         GROUP01
      
      VD0892 0000012D R1PD13 APPLTS.AXQ.AXQMAN02.PS.F0098               ********         16 ARCHIVED TO C10439 BID=00000001
      VD0892 0000012E R1PD04 APPLTS.AXQ.AXQMAN02.PS.F0099               ********         16 ARCHIVED TO C10439 BID=00000004
      VD0892 0000012F R1PD10 APPLTS.AXQ.AXQMAN02.PS.F0100               ********         16 ARCHIVED TO CL0439 BID=00000007
      
      SIZE OF PROCESSED GROUP:          0.000GB #DATASETS IN GROUP:                   3
      **********************************************************************************************************************
      
      TOTAL ARCHIVED:                   0.000GB #DATASETS:                            3 #GROUPS PROCESSED:             1

   4. If the simulation results are not as you expected them to be, modify your selection criteria and repeat the simulation until the results are satisfactory.
   5. When the results confirm that your selection criteria are identifying all of the inactive data sets that you want to archive and all of the data sets that you want excluded from the Archive process, remove the SIM value from the EXEC control card then go to step 9.
   Note: Initially, it is likely that a large volume of data will meet the inactivity criteria that you specify. 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.
9. Submit the job for execution.
   Note: Should you need to shut down HSM, you must first stop the Archive job.
10. 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.