Previous Topic

Next Topic

Book Contents

Book Index

CTVUPGDB Parameters

The CTVUPGDB utility determines which indexes to add to the Global Index database, based on the following user-specified selection parameters. The parameters are specified in DD statement SYSIN.

Table 304 CTVUPGDB Parameters

Parameter

Description

LOAD

Positional parameter. Mandatory.

MODE

Determines whether the utility runs in Production mode or Simulation (Test) mode. Optional. Valid values are:

  • PROD - The utility runs in Production mode. The selected data are written to the file indicated by the DACTVLST DD statement. The selected reports are marked "loaded to Global Index" in the User file. These reports can be selected for loading again only if the FORCE parameter is set. Default.
  • TEST - The utility runs in simulation mode. The selected data are written into the file indicated by the DALSTEST DD statement. The selected reports are not marked "loaded to Global Index" in the User file.

USER

The name of the recipients or mask patterns for which the indexes are added. Mandatory.

Up to 15 users or masks can be specified using the format
USER=(USERA,M*,D??45)

JOBNAME

The job name or mask of the reports for which indexes are added. Optional.

JOBID

The job ID of the report for which indexes are added. Optional.

The format depends on JES definitions; either JOBn..n, where n..n is the job number containing 5 digits or Jn..n, where n..n is the job number containing 7 digits.

REPNAME

The name of the reports or mask patterns for which the indexes are added to the Global Index database. Optional.

If the report name contains embedded spaces, place the report name between apostrophes.

FODATE

The From ODATE of the report. This is the earliest order date from which indexes are selected. Optional.

The date contains slashes, and is in the format dd/mm/yy, mm/dd/yy, or yy/mm/dd, depending on the site standard defined in the IOAPARM member.The parameter can also be specified in the format -N, where N is number of days (0 -99999) preceding to the current date.

TODATE

The To ODATE of the report. This is the latest order date from which indexes are selected. Optional.

The date contains slashes and is in the format dd/mm/yy, mm/dd/yy, or yy/mm/dd, depending on the site standard defined in the IOAPARM member. The parameter can also be specified in the format -N, where N is number of days (0 -99999) preceding to the current date.

FORCE

The action to perform on indexes that have already been added to the Global Index database. Use this parameter for utility runs that were abnormally terminated.

Valid values are:

  • NO – Do not add indexes of reports that have already been added to the Global Index database. Default.
  • YES – Add indexes of reports that have been previously added to the Global Index database.

TRACE

The action to perform on trace messages. Optional.

Valid values are:

  • NO – Do not issue trace messages. Default.
  • YES – Issue trace messages.
  • ALL – Issue trace messages and list all index values added to the Global Index database.

MAXINDX

The maximum number of reports to add to the Global Index database during one run of the utility. Optional. Default: 100.

STORED

The action to perform on reports that are the result of a print mission with the STORE parameter set to YES. Optional.

Valid values are:

  • NO – Do not add reports that are the result of print mission with the STORE parameter set to YES.
  • YES – Add only reports that are the result of a print mission with the STORE parameter set to YES, but do not add the original report.
  • ALL – Add both stored and not stored reports. Default.

MIGRATE

The action to perform on reports from the Migration User file. For Migrated reports, only resident indexes, which are indexes that reside on DASD, are processed.

Valid values are:

  • NO – Do not process reports from the Migration User file, but only from the Active User files. Default.
  • YES – Process reports from the Migration User file, as well as from the Active User files.
  • ONLY – Process reports only from the Migration User only, not from the Active User files.

LIST

Defines the format of the records of the generated flat file. Valid values are:

  • DB2 – Format of the records is described in the INCONTROL for z/OS Administrator Guide. The Path number from the CTDGIDB2 member is included in each record. The DB2 value should be used when the created flat file is used to load the Global Index DB2 tables.
  • ONLY - Record format is the same as DB2 except for the Path number. The CTDGIDB2 member is not scanned when LIST is set to ONLY.

PATH

The index path. Optional.

Locations are separated by a slash, using the following syntax:

main-ixname/sub-index1/sub-index2...

If this parameter is specified, all index paths must be specified.

If this parameter is not specified, add all index paths for all levels (that is, with all their sub-indexes). Default.

SORTNBL

The number of blocks for allocating SORTIN and SORTOUT files. Optional. Default: 3000.

RESTORED

The action to perform on reports restored from the History User file. Optional.

Valid values are:

  • YES – Reload reports restored from the History User file even if they had been loaded to Global Index Database before backup. Default.
  • NO – Do not process reports restored from the History User file if they had been loaded to Global Index Database before backup. This option is ignored if FORCE=YES is specified.

Parent Topic

CTVUPGDB – Update Global Index Database