Customizing the sample JCL for catalog synchronization

Before running catalog synchronization for the first time, you must create the database structures used by the BJTCCATS program. If you are installing for the first time, the SBJTSAMP member BJT@JCDB contains the commands to build the structures. Run BJT@JCBX to perform the BINDs and GRANTs.

About this task

Whether you are installing for the first time or updating from an earlier version, you must also customize the SBJTSAMP member BJTCTSNC, which contains the JCL for running the catalog synchronization utility.

Note: If the SBJTLPA modules are not loaded into the dynamic LPA, it must be link-listed or STEPLIBed until the next IPL.

To customize the JCL in the BJTCTSNC member:

Procedure

  1. Replace the following variables with the values that you set during product customization:
    • ?BJTHLQ? - The high-level qualifier for your Output Manager product libraries
    • ?BJTPLAN?X - The plan name you used in BJT@PRBX for the catalog synchronization plan.
    • ?DB2SSID? - The subsystem ID of the Db2® subsystem that is contains Output Manager database
    • ?SDSNEXIT? The Db2 Exit library for your Db2 subsystem.
    • ?SDSNLOAD?- The fully qualified name of your Db2 load library

    For more information about these variables, see the IBM Tivoli Output Manager for z/OS Installation and Customization Guide.

  2. Ensure that the job card is valid for your site.
  3. In the SYSIN DD statement, specify the appropriate keyword parameters for your site using the syntax
    KEYWORD = VALUE.
    1. (Optional) If you have a Space Management product that moves inactive data sets to another form of storage after being unreferenced after a specified number of days, use the VOLSER keyword to specify the volume serial number that represents a data set has been MIGRATED. If your site uses only MIGRAT(1|2) to represent migrated data sets, this keyword can be omitted. You can specify up to 10 VOLSER values. For example, if your site uses the volsers MIGRAT and ARCIVE to indicate migrated devices, specify the following VOLSER cards: 
      VOLSER = MIGRAT
      VOLSER = ARCIVE
    2. (Required) Use the SSID keyword to specify the subsystem ID of the Db2 subsystem that contains the tables to undergo catalog synchronization processing.
    3. (Optional) If you want the catalog synchronization utility to delete archive table entries that point to data sets that are no longer cataloged, specify both ALLOW_DELETE = YES and ALLOW_UPDATE = YES. If you want the catalog synchronization utility to retain these archive table entries while updating the indication that says whether the dataset is present, specify both ALLOW_DELETE = NO and ALLOW_UPDATE = YES.

      If you are running a test, and you want the catalog synchronization utility to make no database changes at all, specify both ALLOW_DELETE = NO and ALLOW_UPDATE = NO.

    4. (Optional) If you want to print a detailed report of all actions taken during catalog synchronization, specify DETAIL = YES. If you do not want a printed detailed report, specify DETAIL = NO.
    5. (Optional) If you want to display the names of data sets for which the "Migrated" status change, specify SHOW_CHANGED_ARCHIVE_DATASET_NAMES=YES.
    6. (Optional) If you want to specify the number of deletions or updates that the catalog synchronization utility must perform before a Db2 COMMIT is issued, specify the COMMITSIZE keyword with a number from 1 through 1000.

      If you do not specify the COMMITSIZE keyword, the default value of 100 is used.

    7. (Optional) You can set CSI_WORK_AREA_SIZE = 1024000.

      The maximum value that can be specified is 8192000 and if not specified, the value defaults to 102400. A larger value is required if there are GDGs within this HLQ that contain a large number of entries.

    For more information about these keywords, see Catalog synchronization keywords and syntax.

  4. When you are finished customizing the JCL, save the BJTCTSNC member.