Example for CTVUPGDB

In this example, reports created by the k06test job, which are not marked "loaded to Global Index" in the Active User file, are processed. All index entries of the index paths defined in these reports that exist in the CTDGDB2 member are unloaded to the CTVP.V900.INDLST01 file. The processed reports are marked "loaded to Global Index".

Figure 113 CTVUPGDB – Example 1

// EXEC CTVUPGDB

//DACTVLST DD DSN=CTVP.V900.INDLST01,...

//SYSIN DD *

LOAD

JOBNAME=K06TEST USER=*

LIST=DB2

In this example, all reports not marked "loaded to Global Index" in the Migrated User file are processed. All index entries of the index paths ACCOUNT/DATE and ACCOUNT/NAME are unloaded to the CTVP.V900.INDLST01 file (if the paths exist in the CTDGDB2 member). The processed reports are marked "loaded to Global Index".

Figure 114 CTVUPGDB – Example 2

//Step01 EXEC CTVUPGDB

//DACTVLST DD DSN=CTVP.V900.INDLST01,...

//SYSIN DD *

LOAD USER=* MIGRATE=ONLY

PATH=ACCOUNT/DATE

PATH=ACCOUNT/NAME

LIST=DB2

/*

All reports in the Active and Migrated User file that belong to the TESTUSER recipient are processed. Al index entries of these reports are unloaded to the file indicated by the DALSTEST DD statement.

Figure 115 CTVUPGDB – Example 3

//STEP01 EXEC CTVUPGDB

//SYSIN DD *

LOAD USER=TESTUSER MIGRATE=YES

LIST=ONLY MODE=TEST FORCE=YES

/*

Parent Topic

CTVUPGDB – Update Global Index Database