Interpreting SAS/SHARE Server Log Messages

Reading the Server Log

30Apr2008:07:15:36.690 043131 SAS server SHARE2 started.

A message such as this always appears in the log when the server starts. The message tells the server administrator that the server initialization completed successfully. In this example, server SHARE2 identifies which server was started. After this message is printed, the server waits for clients to connect to it. For information about starting a server, see Starting a Server. For information about server IDs, see Server Log Message Components.

The Connect Message

30Apr2008:07:16:20.048 043021 User john(1) has connected to server SHARE2.

A message such as this appears when a client establishes a communication path with the server. The message contains a user ID, a connection number, and a server ID that tell which user has connected to which server. In this example, user john(1) has connected to server SHARE2 . For more information about user IDs and server IDs, see Server Log Message Components. The Connect message is bracketed in the log by the disconnect message. See The Disconnect Message.

The Create Message

30Apr2008:07:16:20.442 043143 User john(1) has created "Line Mode Process"(1) 
under "Kernel"(0).

A message such as this shows that the user has created a resource environment. During a connection, the user, in this example john(1) , creates mirror resource environments, which are used to maintain (track, scope) the resources that the user consumes in the server's session (or that the server consumes on the user's behalf). The number of each newly created resource environment will appear in later messages about the resources that were consumed.

The quoted string, "Line Mode Process" , is the name of the resource environment that was created. The number in parenthesis is the resource environment number.

The quoted string "Kernel" is the name of another resource environment, and the number in parenthesis is the resource environment number. "Kernel" is the parent resource environment of the created resource environment that this message records. In this example, the "Kernel" resource environment is the parent of the "Line Mode Process" resource environment. It is possible to deduce a resource environment tree that is in effect during a server's session.

The "Kernel" (0) resource environment is automatically created when a user connects to a server. The primary purpose for kernel resource environments is to create child resource environments.

For more information, see Server Log Message Components.

The Create message is bracketed in the log by the Terminate message.

For more information, see The Terminate Message.

The Access Message

30Apr2008:07:16:21.206 043069 Server library TESTDATA 
('/local/u/john/server' V9) accessed as TESTDATA by user john(1).

A message such as this appears when a SAS client executes a LIBNAME statement, or an external client (that is, a client that is not a SAS client) performs an action that associates a libref with a SAS library. This message gives you an association between the libref that you'll see in subsequent messages and the physical name, engine, and server's libref of that library. Under z/OS, accessing a library results in a physical file being opened; in other operating environments, accessing a library is similar to changing directories.

The Access message begins with the libref that the server uses to reference the library. In this example, the libref is TESTDATA . The information in parentheses ('/local/u/john/server' V9) is the physical name of the library (the quoted string), and the name of the engine (V9) that is used in the server's session to access the library.

The end of the message identifies the user who is accessing the library. In this example, the user is john , and the number in parenthesis (1) is the connection number, which is used for tracking a user's activity on the connection.

For more information about librefs, engine names, and user IDs, see Server Log Message Components. For information about accessing a SAS library, see Defining a SAS Library to a Server (All New Users).

The Access message is bracketed in the log by the Release message. See The Release Message.

The Open Message

30Apr2008:07:17:33.537 043100 DEMOTEST.X.DATA(1) opened for input/S via 
engine V9 by "PRINT"(2) of user maria(2).

A message such as this appears when a user opens a SAS data file.

Opening a SAS file allows the user to move around within the file, see which variables are in the file, check the file size and the file formats, and so on.

Opening a SAS data view is more complicated than opening a data file. To open a data view, the server gets help from the engine supervisor to do the following:

load the engine that will interpret the view
open the view file
have the view engine open the underlying files and prepare to interpret the instructions in the view file

The Open message begins with the libref.member-name.member-type. In this example, DEMOTEST.X.DATA shows which file or view is being opened, and the number in parenthesis (1) is the open sequence number. This number is a counter to track how many times a data set is opened within a resource environment.

Input is the type of Open mode, and S is the access pattern for this open.

engine V9 identifies which engine is being used to interpret the view for the member type VIEW.

"PRINT" (2) identifies the resource environment that is being used to open the file or view. Openings are considered resources, so resource environments track them. The same resource environments also track the resources, such as memory, that are consumed when a file or view is opened.

maria is the user ID, which shows who opened the file or view, and (2) is the number of times that the file was opened. For more information about librefs, member names, member types, open modes, access patterns, engine names, resource environments, and user IDs, see Server Log Message Components.

The Open message is bracketed in the log by the Close message. See The Close Message.

The Close Message

30Apr2008:07:17:40.361 043102 DEMOTEST.X.DATA(1) closed by "PRINT"(2) 
of user maria(2).

A message such as this appears when a user closes a file. In this example, user maria has closed the file DEMOTEST.X.DATA under the resource environment "PRINT" . For more information about librefs, member names, member types, resource environments, and user IDs, see Server Log Message Components. See also The Open Message.

The Release Message

30Apr2008:07:19:06.298 04306A Server library TESTDATA (accessed as TESTDATA) 
released by user john(1).

A message such as this appears only if the user explicitly executes a LIBNAME statement that includes the CLEAR option. For example:

libname TESTDATA clear;

In this example, user john has released the library TESTDATA . The Release message is the opposite of the Access message. See The Access Message.

For more information about user IDs and librefs, see Server Log Message Components.

The Terminate Message

30Apr2008:07:19:06.319 043144 User john(1) has terminated "Line Mode 
Process"(1) (under "Kernel"(0)).

A message such as this appears when a user terminates a resource environment which was previously created. See The Create Message. In this example, user john terminated the resource environment "Line Mode Process" (1) , which was a child resource environment of "Kernel" (0) . For more information about resource environments and user IDs, see Server Log Message Components.

The Disconnect Message

30Apr2008:07:19:06.411 043022 User john(1) has disconnected from server SHARE2.

A message such as this appears when a user who was connected to the server has ended that connection. In this example, user john has disconnected from server SHARE2 . For more information about user IDs and server IDs, see Server Log Message Components.

Usually, the Close message appears before the Disconnect message. However, a Disconnect message might appear before a Close message appears if the client's session with the server was ended abnormally (for example, if the line is disconnected or a client's machine crashes).

Accounting Information

30Apr2008:07:19:06.425 043151 Usage statistics for user john(1):
                                  Messages processed:                  14
                                  Bytes transferred:                3,133 
                                  Active time:               0:00:01.8139
                                  Elapsed time:              0:02:46.6840

By default, accounting data is written to the server's log when a user disconnects from the server. (See The Disconnect Message.) This data shows the usage of server resources--that is, the messages processed, bytes transferred, active time, and elapsed time--that resulted from a user's activity while connected to the server. In this example, the data shown is for user john while connected to server SHARE2 .

For explanations of usage statistics for messages processed (MESSAGE), bytes transferred (BYTECOUNT), active time (ACTIVETIME), and elapsed time (ELAPSEDTIME), see The SERVER Procedure. For more information about accounting level, see The SERVER Procedure. For more information about user IDs, see Server Log Message Components.

The Stop Message

The Stop message appears in the log if an administrator uses the STOP command under PROC OPERATE. The server stops all activity and shuts down; all processes end normally. The server log shows that the STOP command was issued, and shows the Close, Release, Terminate, and Disconnect messages that follow as the files, libraries, resource environments, and the connection to the server are shut down. For more information about the server administrator's log and an example of what the STOP command generates in the server administrator's log, see Managing a Server, Its Libraries, and Its Users.

Top of Page