More about utility devices

Table 1 describes utility support when the UTILITY parameter is specified with either FIX or FLOAT and the XADDPAIR command with a secondary volser is not XRCUTL:
Table 1. Specifying UTILITY(FIX or FLOAT) and the XADDPAIR command with a secondary volser that is not XRCUTL
If . . . Then . . .
The primary volser is not in the session. The primary volser is added to the session.
The primary volser is already in the session and its secondary volser is XRCUTL, but it is not a fixed utility device. The XADDPAIR command processes normal volume initialization.
The primary volser is already in the session, its secondary volser is XRCUTL and it is a fixed utility device. The XADDPAIR command is rejected, with return code 4082.
The primary volser is already in the session and its secondary volser is not XRCUTL. The XADDPAIR command is rejected with either:
  • Return code 490, if the new secondary volser matches an existing secondary volser.
  • Return code 489, if the new secondary volser is different that an already existing secondary volser.
If the following situations occur, a storage control session for a utility volume is converted to an Enhanced Auxiliary session:
If the following situations occur, a storage control session for a utility volume is converted to an Enhanced Primary session:

Storage control sessions suspend whenever all volume pairs in the XRC session are suspended. As a result, utility volumes (XRCUTL) suspend as well. In addition, when the last data volume is suspended in a storage control session, this causes the utilities associated with that storage control session to suspend as well. Further, anytime a data volume is suspended, any storage control session that has no data volumes associated with it will also be suspended.