DSNU360I csect-name - IN REORG WITH SHRLEVEL REFERENCE OR CHANGE, DATA SET name EXISTS, 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 performs the following renaming:
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 for Db2-managed data sets.
If a -TERM UTILITY command is issued after any renaming, or a restart of the REORG switch phase occurs after any renaming, the data set names revert back to their original form prior to the renaming:
4
The original data set from the shadow name to the temporary name
5
The shadow data set from the original name to the shadow name
6
The original data set from the temporary name to the original name
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 a temporary name already exists. 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 original name already exists. 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 shadow name already exists. This error condition can arise for a user-managed data set.
4
During switch phase restart or a -TERM UTILITY during the switch phase, on rename 4 (while reverting back to the original name), -TERM UTILITY detected that a data set with a temporary name already exists. This error condition can arise for a Db2-managed or user-managed data set.
5
During switch phase restart or a -TERM UTILITY during the switch phase, on rename 5 (while reverting back to the original name), -TERM UTILITY detected that a data set with a shadow name already exists. This error condition can arise for a Db2-managed or user-managed data set.
6
During switch phase restart or a -TERM UTILITY during the switch phase, on rename 6 (while reverting back to the original name), -TERM UTILITY detected that a data set with a original name already exists. This error condition can arise for a Db2-managed or user-managed data set.
8
During initialization of REORG, REORG detected that a data set with a temporary name already exists. This error condition can arise for a Db2-managed or user-managed data set.

System action

For context code 1, or 2, the utility job step that caused the function to be requested abends with code 00E4031B. The utility job is placed in the stopped state.

For context code 3, the utility job step that caused the function to be requested continues without performing this renaming.

For context code 4, 5, or 6, the object is left in a recovery pending state, -TERM UTILITY continues to undo renaming, and a message is issued. The objects and messages are as follows:
  • 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.

For context code 8, REORG does not execute.

User response

For context code 1 or 2, you can choose between these actions:
  • Delete the data set; then RESTART the utility.
  • TERM the utility. Delete the data set before trying to execute REORG again with SHRLEVEL REFERENCE or CHANGE.

For context code 3, if you want to perform the renaming, delete the data set with the shadow name and then perform the renaming.

For context code 4, 5, or 6, execute the RECOVER or REBUILD INDEX utility; then delete the shadow and temporary data sets (if they still exist).

For context code 8, delete the data set and then execute REORG.

Severity

8 (error)