You can change the deadlock priority value for the following commands:

• pdhold -b (referencing-possible backup hold)
• pdhold -s (synchronization hold)
• pddbchg (replica status switching of a replica RDAREA)
• pdorbegin (database commit after online reorganization)
• pdorend (reflection processing after online reorganization)

The following table shows the deadlock priority values.

Table 9-3 Deadlock priority values

Type and condition				Deadlock priority value
UAP	Value of PDDLKPRIO in client environment definition	96		96
		64		64
		32		32
		Omitted	When X/Open XA interface is used	96
			When X/Open XA interface is not used	64
Utility				64
Command	pdhold -b, pdhold -s, pddbchg, pdorbegin, pdorend			Value of pd_command_deadlock_priority#
	Other commands			64

#: You can specify in this operand a deadlock priority value of 32, 64, 96, or 120. If this operand is omitted, the deadlock priority value is set as follows, according to the type of locked resource:

• Locked resource for which the deadlock priority value is set to 64
  Dictionary table (DICT)
  
• Locked resource for which the deadlock priority value is set to 120
  RDAREA (RDAR)
  RDAREA extension (RDLF)
  RDAREA status (RDAS)
  Backup hold (HOLD)
  Inner replica configuration (INRP)
  Replica group configuration (RPGP)
  

Reference note

• A smaller deadlock priority value indicates a higher processing priority, and a larger deadlock priority value indicates a lower processing priority.
• If two transactions have the same deadlock priority value, the first one that executes is accorded the higher priority.