DSNU296I csect-name - IN REORG WITH SHRLEVEL REFERENCE OR CHANGE, DATA SET name DOES NOT EXIST, CONTEXT=c

Explanation

For the area (table space or partition) being reorganized, REORG with SHRLEVEL REFERENCE or CHANGE unloads data from the original data sets and reloads data into shadow data sets. REORG then exchanges the names of the original and shadow data sets, using temporary names during the renaming. The original name of a data set is in the form catname.DSNDBx.dbname.psname.I0001.Annn. The shadow name of a data set is in the form catname.DSNDBx.dbname.psname.J0001.Annn. The temporary name of a data set is in the form catname.DSNDBx.dbname.psname.T0001.Annn. REORG uses such data sets for indexes as well as data.

During its initialization, REORG cannot execute if:

  • Data sets with the temporary names already exist
  • Db2-managed data sets with the shadow names already exist
  • User-managed data sets with the shadow names do not already exist

To exchange the names of the original and shadow data sets, REORG renames in the following ways:

1
In the switch phase, it renames the original data set from the original name to the temporary name.
2
In the switch phase, it renames the shadow data set from the shadow name to the original name.
3
In the utilterm phase, it renames the original data set from the temporary name to the shadow name (for user-managed data sets). It deletes the temporary name for Db2-managed data sets.

If either a -TERM UTILITY command is issued, or the REORG switch phase is restarted after REORG has begun renaming data sets, the names revert back to their original form prior to the utilterm phase of REORG:

The context code indicates the specific type of error:

1

During the switch phase of REORG, on rename 1, REORG detected that a data set with an original name does not exist. This error condition can arise for a Db2-managed or user-managed data set.

During the switch phase restart or a -TERM UTILITY during the switch phase, on rename 4, REORG detected that a data set with an original name does not exist. This error condition can arise for a Db2-managed or user-managed data set.

2

During the switch phase of REORG, on rename 2, REORG detected that a data set with a shadow name does not exist. This error condition can arise for a Db2-managed or user-managed data set.

During the switch phase restart or a -TERM UTILITY during the switch phase, on rename 5, REORG detected that a data set with a shadow name does not exist. This error condition can arise for a Db2-managed or user-managed data set.

3
During the utilterm phase of REORG, on rename 3, REORG detected that a data set with a temporary name does not exist. This error condition can arise for a user-managed data set.
7
During initialization of REORG, REORG detected that the shadow data set did not exist. This error can only occur with a table space, index, or partition that is stored in user-managed data sets.

System action

For context codes 1 or 2, utility processing is abended. ABEND reason code 00E4031B is issued. The object is left in a recovery pending state.

For context code 3, the utility job step that caused the function to be requested continues with no renaming. The utility job is placed in the stopped state. The object is left in a recovery pending state, and a message will be issued.

For context code 7, REORG does not execute.

For context codes 1, 2, or 3, the following messages are issued:
  • If the data set is part of a nonpartitioned table space, the object is the table space, and the message is DSNU562I.
  • If the data set is part of a partition of a table space, the object is the partition, and the message is DSNU560I.
  • If the data set is part of a nonpartitioned index, the object is the index, and the message is DSNU557I.
  • If the data set is part of a partition of a partitioned index, the object is the partition of the index, and the message is DSNU559I.

User response

For context codes 1 or 2, execute the RECOVER TABLESPACE or RECOVER or REBUILD utilities.

For context code 3, do nothing.

For context code 7, define all shadow objects prior to running REORG.

Severity

4 (warning) or 8 (error)