Running stand-alone services in 370 mode

The following conditions apply to Stand-Alone Services operations in 370 mode:

Tape libraries are not supported by Stand-Alone Services in 370 mode.
The initial program load (IPL) device and the console must be attached to the same processor you IPLed from (when there are two or more processors).
For DASD and tape devices:
- In 370 mode, Stand-Alone Services does not issue Assign or Unassign commands for tape devices, or Device Reserve or Device Release commands for DASD devices.
- The user must ensure that all devices to be used by Stand-Alone Services are not accessed by other systems during IPL and while Stand-Alone Services operations are in process.
Potential interference from other devices can occur as follows:
- When the Stand-Alone Services is IPLed and loaded with the operator console not predefined, a Wait PSW is loaded with the rightmost bytes containing X'FFFFFF'. The Stand-Alone Services program waits for the operator to identify the operator console. The first interrupt presented at this time is expected to be a console and is treated as such.
- When the operator console is predefined and a problem is detected while attempting initial communication with the predefined console, Stand-Alone Services loads a Wait PSW with the rightmost bytes containing X'DDDDDD', giving the operator an opportunity to identify a console (other than the predefined console) to be used as the operator console.
Other devices can generate interrupts that interfere with Stand-Alone Services operations. If this happens, determine which device is causing the interference and follow your installation’s procedures to prevent the device from interrupting until the Stand-Alone Services operation is complete.