Interpreting SAS/SHARE Server Log Messages

Server Log Message Components

Server log messages consist of the following components, which are repeated throughout the log:

engine-name

is the name of the engine that will process the SAS library in the server's SAS execution.

libref

is the name temporarily associated with a SAS library. You assign a libref by using a LIBNAME statement or operating system control language.

libref.member-name.member-type (open sequence number)

libref is the first part of a multi-level SAS filename that is temporarily associated with the SAS library in which the file is stored.

member name is the filename in a SAS library that references an access descriptor, or a stored program.

member type is the name assigned by SAS that identifies the type of information that is stored in a SAS file (for example ACCESS, DATA, CATALOG, PROGRAM, or VIEW).

The open sequence number, in parentheses, is a counter that is used for tracking.

open mode / access pattern

The following table shows the types of open mode and their functions.

Open Modes
Open Mode		Function
Input		Opens files to read.
Output		Creates or replaces files. (Do not use a slash when specifying the Output mode.)
Update		Modifies existing observations or adds new observations, or both.
Utility		Modifies the header data (for example, assigning a new label or format to a variable).

The following table shows the types of access pattern and their functions.

Access Patterns
Access Pattern		Function
Random (R)		Processes observations according to the value of an indicator variable without processing preceding observations.
Sequential (S)		Processes observations one after the other, starting at the beginning of the file and continuing to the end of the file.
Two-pass (2)		Enables a SAS procedure to pass through the data more than one time.
BY-group rewind (B)		Enables a SAS procedure to pass through the data more than one time.
Contents type (C)		Reads header data, such as names of variables, but does not read observation data, such as data that PROC PRINT reads.

The two-pass and BY-group rewind access patterns both enable SAS procedures to pass through the data more than one time. For example, during the initial pass a sum or count is computed; during the second pass, the values of the variables in each observation are compared to, added to, or subtracted from the value that was computed in the first pass. The distinction between these two access patterns is subtle.

When a SAS data set contains only one BY group, there is no difference. When a SAS data set contains multiple BY groups, rewinding a BY group after the first BY group is processed requires the ability to position to a random location in the file, which is not complicated when using disk devices but is almost impossible when using tape devices. (The I/O supervisor is able to remember the starting position of the current BY group.)

Only the two-pass access patterns require the ability to rewind the entire SAS data set.

resource environment (resource environment number)

is a structure that is used within SAS to scope and manage the usage of system resources. Examples of resource environments include SAS procedures, SAS windows, DATA steps, or other internal SAS activity.

The resource environment number, in parentheses, is a counter that starts at 1 for each connection. To precisely identify a resource environment in a server's log, you need the connection number and the resource environment number.

serverid

specifies a name for the server. The server name must meet the criteria for a valid SAS name, which can include the following special characters: dollar sign ($), at sign (@), and pound sign (#). For more information, see the rules for naming SAS variables in SAS Language Reference: Concepts.

Naming a server must also include criteria that are imposed by the operating environment and the access method that you specify for communication between a server and a client session. For example, if you are using the TCP/IP communications access method, the serverid that is specified must be a valid TCP/IP service as defined in the TCP/IP SERVICES file.

For information about naming servers by operating environment, see Communications Access Methods for SAS/CONNECT and SAS/SHARE.

userid(connection number)

specifies a valid user ID for the accessing client on the server. The operating environment on which the client runs can affect user naming conventions. For details about specifying valid user IDs, see User ID and Password Naming Conventions.

The connection number is shown in parentheses after the user ID. This number begins at 1 and increases by 1 each time a user connects to the server. The server maintains this counter. The connection number is shown in most of the messages that are recording activity for each connection. If the same user ID is connected to a server more than one time, it is possible to track the activity of each connection separately.

Top of Page