Single-User Mode

Using Single-User Mode

When you invoke PROC QUEST in single-user mode (S2KMODE=S), SAS displays the following information:
  • SYSTEM 2000 initialization parameters
  • SYSTEM 2000 version number
  • copyright information
Submit the USER statement to establish your password and start your SYSTEM 2000 session. The following example statements also attach the database Employee to your session:
   user,demo;    
   data base name is employee;
The SYSTEM 2000 interface to SAS accesses the database and displays any output in the Output window or in the procedure output file (if you are executing in interactive line mode).

The S2KPARMS File

Because you are running in your own address space when you are in single-user access mode, you can specify a variety of parameters. (See SYSTEM 2000(R) Software: Product Support Manual, Version 1, First Edition for information about SYSTEM 2000 execution parameters.) To specify execution parameters for the QUEST procedure in single-user mode, you must set up a file with the fileref S2KParms. If there is no fileref named S2KParms, system defaults are used.
For example, the LIST=YES parameter displays the parameter values in the Log window when the system is initialized. To suppress this display, edit the file and specify LIST=NO and allocate it using the fileref of S2KParms in your SYSTEM 2000 CLIST or EXEC.

Attention Interrupts in TSO

If you interrupt where-clause processing under TSO in single-user mode, your request is canceled. A canceled retrieval produces no output, and a canceled update does not alter the database.
If you interrupt processing at any other time, the interrupt is ignored. When you return to SAS, the usual SAS interrupt-handling mechanism is restored.
While it is not recommended, you can prevent single-user mode from intercepting the SAS attention-interrupt mechanism by specifying STAX=NO in the file S2KParms. However, be aware that, if you terminate both the QUEST procedure and SAS by using the SAS Attention exit after having updated the database, you might have unwritten buffers left in memory. As a result, the database could be damaged.