Control-M/Restart: How to avoid the deletion of a GDG generation by a restart of a job if this GDG is used by multiple jobs?

Version 1
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M/Restart


    COMPONENT:

    Control-M/Restart


    APPLIES TO:

    all versions of Control-M/Restart



    QUESTION:

    How to avoid the deletion of a GDG generation by a restart of a job if this GDG is used by multiple jobs?
     


    ANSWER:

    Set parameters IGNFLUSH and SAMEGDG to YES:

      IGNFLUSH:
      
        
      
      Prevents, during the Restart process, the processing of new GDG data sets from being created by steps flushed during the original run of a job.
    Valid values are:
      
        
      
      - Y – During the Restart process, Control-M/Restart avoids processing of GDG data sets specified with DISP set to NEW if such a GDG data set is specified in a step that did not run (was flushed) during original run of a job. Such processing usually includes scratching and uncataloging corresponding GDG data set created by the original run of a job and correcting the name of the new GDG data set so that it has the same name as during original run. This parameter, together with the SAMEGDG parameter, described below, may be useful when several jobs may create new GDG generations for the same GDG base.
      
        
      
      - N – This feature is not activated and Control-M/Restart processes GDG data sets the same way for all steps. Default.
      
        
      
        
      
      SAMEGDG
      
        
      
      Support of concurrent writing to the same GDG base by different jobs.
    Valid values are:
    -Y – Control-M/Restart supports concurrent writing to the same GDG base by different jobs. This includes additional checking before Control-M/Restart processes any GDG data set (such as scratching, uncataloging, and correcting data set name) that corresponds to a GDG data set (such as scratched, uncataloged, and used data set name) that was really created and/or used by the original run of the same job. This parameter, together with IGNFLUSH (described in this table), may be useful for the cases when several jobs may create new GDG generations for the same GDG base.
    -N – This feature is not activated. Default.
      
      

     


    Article Number:

    000166024


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles