The SV (Save) command makes units inaccessible to the system. Saved units can be returned to the system with the RY (Ready) command.

The SV command is not valid for online, mirrored packs. Before the SV can be performed, the pack must be released with the MIRROR RELEASE command.

Syntax

              ┌◄───────────────,─────────────────┐
──┬─SV────┬─┬─┴─<device type>─<unit number list>─┴─┬───────┤
  └─SAVE──┘ ├─CPM─<CPM list>─┬────────┬────────────┤
            │                └─: NOW──┘            │
            └─IOP─<number>─┬────────────┬──────────┘
                           └─: INHIBIT──┘

Explanation

SV <device type> <unit number list>

Makes the devices in the unit number list inaccessible to the system. You can return saved units to the system by using the RY (Ready) command. The device and unit number list can be integers from 1 through 32767. The system does not accept any new requestors of the resource provided by the device, but it does not interrupt current users. If programs are using files on the device, those files continue to be available until the programs close them.

SV CPM <CPM list>

SV CPM <CPM list>:NOW

The system removes the specified CPMs from use and marks them user-saved.

<CPM list> is a range of integers from 0-15. If the NOW modifier is used, the CPM is saved without additional operator input.

SV IOP <number>

The specified IOP is made unavailable for I/O operations unless it serves as the last path to critical units. If the specified IOP serves as the last path to noncritical units, an RSVP is posted to list the devices that will be lost, in which case, the user has the option to abort the request. Once completed, the IOP is marked as SAVED in the PCD. The specified IOP remains SAVED through subsequent halt/loads until the user readies it by means of the RY (Ready) command.

SV IOP <number> : INHIBIT

Same as SV IOP except that the IOP is marked as INHIBITED in the PCD. Use SAVE :INHIBIT if an IOP system is suspected to be bad so that attempts to READY the IOP requires a response to a warning RSVP.

Examples

Example 1

This example saves a tape unit:

SV MT 114

   MT 114 SAVED

Example 2

This example saves a central processing module:

SV CPM 6

   CPM 6 SAVED

Example 3

This example saves a critical pack, which is a pack that has been specified in a DL (Disk Location) command:

SV PK 160

   PK 160 WILL BE SAVED

PER PK

   ----------------------PK STATUS---------------------------
   160*B     [000851] (TO BE SAVED) 

Considerations for Use

Saving a Pack

For pack devices, saving the unit prevents any new areas from being created on that unit, but does not prevent existing areas from being read from and written to. Saving the pack does not prevent the unit from being the object of LB (Relabel Pack), PG (Purge), RC (Reconfigure Disk), or MIRROR CREATE commands. Saving the base pack of a pack family makes the family inaccessible for file open actions and directory inquiries—such as the PD (Print Directory) command. Saving a continuation pack of a pack family does not have this effect. Saving a critical pack causes the pack to be saved after a halt/load.