Skip to Content

CHECK PLUS data sets

The following table lists the data sets that CHECK PLUS uses. You can override some of the ddnames or ddname prefixes by using CHECK command options. Except where noted, you can allocate the data sets to a tape unit. For more information about these data sets, see CHECK PLUS DD statements.

Related topics

Getting started

How CHECK PLUS works

 

Data set or ddname

Description

Reference

SYSIN

SYSIN is the input data set that contains the CHECK command.

SORTWKnn

SORTWK is the work data set that BMCSORT uses. The data set is used in the CHECK phase. CHECK PLUS can simultaneously invoke BMCSORT one or more times during check processing. Each sort process requires its own set of sort work files. You cannot allocate the sort work files as VIO data sets or tape data sets. You must allocate each individual work file to a single DASD unit.

SYSERR

CHECK PLUS uses the SYSERR data set as follows:

  • Uses SYSERR only with the CHECK DATA command.
  • Uses SYSERR for Db2-defined and user-defined error processing.
  • Writes to this data set during the CHECK phase and reads from it during the FIX RI phase.
  • Uses the error information from this data set during the FIX RI phase to create the discard data set.

SYSDISC

CHECK PLUS uses the SYSDISC data set only with the CHECK DATA command. SYSDISC is the data set that contains the foreign keys in violation of DB2-defined or user-defined RI. The file is written during the FIX RI phase.

SYSPRINT

SYSPRINT is the output data set that contains CHECK PLUS messages.

UTPRINT

UTPRINT is the data set that indicates that sort messages should be reported. The actual messages for each sort process appear in separate SYSnnnnn data sets, where nnnnn is a system-assigned sequential number. This data set is required by any phase that performs a sort.

Error
Warning

JES3 users should be aware of a limitation within JES3 that does not allow concurrent tasks to share SYSOUT data sets.

Db2 data sets

CHECK PLUS dynamically allocates the Db2 data sets (table spaces or index spaces) you are checking. Therefore, you do not need to specify them in your JCL. All Db2 catalog access and access to the CHECK PLUS RI rules tables use SQL.

Not applicable

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

CHECK PLUS for DB2 13.1