Section 2, Task 4: Set Up Your Production Job
Action 1: Create the production job(s)

  1. Copy the batch job that you used with the test PDB.

    Reserve the original in case you want to use the test PDB for other testing.

    Follow these steps below to convert the copy to be your production job(s).

  2. For the JOB statements:

  3. Delete the CLEANUP job step and the ALLOC job step.

  4. Add a BACKUP job step.

    The BACKUP job step in the CMJCLLD member of your CPMISC PDS is an example.

    //BACKUP  EXEC PGM=ADRDSSU                                #1
    //TAPE     DD DSN=your.itsv.pdb,DISP=(OLD,KEEP),          #2
    //            UNIT=cart,RETPD=30
    //SYSIN   DD *
      DUMP DATASET(INCLUDE(your.itsv.pdb.*)) OUTDD(TAPE) -    #3
                 SHARE COMPRESS


    1. This job can also include an optional BACKUP job step to back up your PDB. This example uses the IBM DFDSS program. You may want to replace that step with the backup procedure commonly used at your site.

    2. You may want to change characteristics on the TAPE allocation according to your needs or according to site-specific rules.

    3. You can use the DFDSS DUMP command to back up volumes and datasets, and you can then use the RESTORE command to recover them. You can also make incremental backups of your datasets by doing a dataset DUMP with RESET specified and filtering on the dataset-changed flag. For more information on this facility, refer to the IBM manual Data Facility Data Set Services: Reference V2R5 (SC26-4389-03). You may want to change the DUMP command according to your needs or according to site-specific rules.

  5. In the LOAD job step:

    1. If you have SMF DD statements, modify them to read only the most recent day's data (for instance, if one generation contains only one day's data , change -3 to 0 and delete the next three statements in the SMF DD concatenation).

      On the %CPSTART macro invocation, change the PDB= parameter to specify the production PDB instead of the test PDB.

    2. On the %CMPROCES macro invocation:

      • The first positional parameter is the location of the raw-data file. That information is not needed if it is provided an alternate way, such as the SMF ddname statement in the JCL.

      • The second parameter is the list of tables. The parameter is optional.

        If the parameter is not specified, IT Service Vision processes all tables that are in the PDB and have a Kept status of

        If the parameter is specified, only the tables listed in the parameter are processed by IT Service Vision. Additionally, if a table is listed in this parameter and the table is not currently in the PDB and the table is a supplied table, IT Service Vision automatically adds the table definition to the PDB before processing.

    3. For the report macro invocations.