• In XA or ESA mode, Stand-Alone Services issues Assign and Unassign commands for tape devices, and Device Reserve and Device Release commands for DASD devices (if the command is supported by the device).
  VM Note: When running Stand-Alone Services under VM, if the Stand-Alone Services program does not run to completion or is unable to free the device, an Assign or Reserve condition may be left outstanding.
• The user must ensure that the devices to be used by Stand-Alone Services are not accessed by other systems while Stand-Alone Services IPL and operations are in progress.

• 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. If the interrupting device is not on the same channel path ID (CHPID) as the devices you are using for Stand-Alone Services processing, configure that CHPID offline, re-IPL the Stand-Alone Services program, and configure the CHPID back online after processing is complete. If the interrupting device is on the same CHPID as the devices you are using for Stand-Alone Services processing, follow your installation’s procedures to prevent the device from interrupting until after the operator console has been identified.