SAS/ACCESS Interface to SYSTEM 2000 Data Management Software: Reference

Single-User and Multi-User Operation

Single-User Operation

When you invoke the QUEST procedure with single-user access (S2KMODE=S), the SAS System displays the following information:

SYSTEM 2000 initialization parameters
SYSTEM 2000 version number
copyright information.

Issue the USER statement to establish your password and start your SYSTEM 2000 session. For example, the following statements attach the EMPLOYEE database:

   user,demo;    
   data base name is employee;

The SYSTEM 2000 interface to the SAS System accesses the database and displays any output on the output window or in the SAS print file (if you are executing in interactive line mode).

The S2KPARMS File

Since you are running in your own address space when you have single-user access, you can specify a variety of parameters. (Refer to the SYSTEM 2000 Product Support Manual for information about SYSTEM 2000 execution parameters.) To specify execution parameters for the QUEST procedure with single-user access, you must set up a file with a fileref of S2KPARMS. If there is no S2KPARMS fileref, system defaults are used.

For example, the LIST=YES parameter displays the parameter values on the log window when the system is initialized. To suppress this display, edit a file to contain LIST=NO and allocate it with a fileref of S2KPARMS in your SYSTEM 2000 CLIST or EXEC.

Attention Interrupts in TSO

If you press the Attention Interrupt key while processing a where-clause in single-user access, 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 the SAS System, the usual SAS interrupt-handling mechanism is restored.

While it is not recommended, you can prevent single-user access from intercepting the SAS attention-interrupt mechanism by specifying STAX=NO in the S2KPARMS file. Be aware, however, that if you terminate both the QUEST procedure and the SAS System with 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.

Multi-User Operation

When you invoke the QUEST procedure in a Multi-User environment (S2KMODE=M), the SAS System responds with these messages:

QUEST Ready    
S2K3212/00 - SYSTEM 2000 INTERACTIVE INTERFACE READY -

Issue the USER statement to establish your password and start your SYSTEM 2000 session. For example, the following statements attach the EMPLOYEE database:

   user,demo;
   data base name is employee;

The SYSTEM 2000 interface to the SAS System accesses the database and displays any output on the output window or in the SAS print file (if you are executing in interactive line mode).

Temporary Output File

The QUEST procedure uses a disk file to temporarily store output. In CMS, the file is allocated automatically. In TSO, you need to allocate a file with at least ten tracks of 3350 disk space (or the equivalent) with the DDname S2KOUTP. If the file is not allocated, you get a warning message (-895-), and any response from SYSTEM 2000 software that exceeds 4096 bytes will be truncated.

Ten tracks of 3350 disk space is enough for typical use. If some output cannot be stored on S2KOUTP, message -897- appears, and you will lose some output. Reallocate the file with more space later.

Command File

You can save SYSTEM 2000 statements in a file with the SAS Text Editor. You can direct the QUEST procedure to read statements from that file by submitting this statement:

   local command file is fileref;

where fileref is the DDname for the file. However, any SAS macros in the file will not be expanded because the QUEST procedure will submit the statements directly to SYSTEM 2000 software without the SAS System reading them.

The following statement lets you continue to submit statements from the PROGRAM EDITOR window; write it at the end of the Command File:

   LOCAL COMMAND FILE IS INPUT;

If you omit this command, the QUEST procedure automatically returns to the PROGRAM EDITOR window when it finds an end-of-file on the Command File.

Note: SYSTEM 2000 commands in a Command File must be specified in uppercase or a syntax error will occur. [cautionend]

The QUEST procedure allows you to use alternate user files for the Data File, Message File, and Report File also. They can be local files or files allocated in the Multi-User region.

Attention Interrupts in TSO

If you interrupt processing while running the QUEST procedure under TSO, the usual SAS message (asking whether you want to terminate or continue) is not displayed.

Instead, if you interrupt processing while looking at the output screen, the attention interrupt is interpreted to mean that you want to purge any further output. The first line on the next page is displayed, but any further output from your last statement is discarded. If you interrupt processing at any other time, the interrupt is ignored.

To cancel the session, you must first terminate the QUEST procedure.

Chapter Contents
Previous
Next
Top of Page