|SAS/SHARE User's Guide|
SLTOOL2 reads the SAS data file produced by SLTOOL1 and creates a group of SAS data sets. Ordinarily, SLTOOL2 is executed during the same SAS session as the SLTOOL1 program.
The libref SLOGDATA is associated with a SAS data library by the LIBNAME statement in SLTOOL0.SAS.
The data sets created by SLTOOL2 are stored in the SAS data library and are associated with the libref SLOGDATA. It is most efficient to run SLTOOL0.SAS one time to create the data files in the library SLOGDATA, and then run any number of analysis programs that access the library SLOGDATA. With large server logs, creating the data sets in the library SLOGDATA can take quite a long time and should be done only once for each server log.
SLTOOL2 creates data sets whose names include either INFO or SUM. INFO files contain observations that record specific SAS/SHARE activities, such as each time a server is started and stopped. SUM files typically present the total number of instances of an activity, such as the total number of connections made to a server.
The following sections describe each data set that is created by SLTOOL2.
SERVINFO records the server name and the times at which it started and stopped. You can use this information to write a descriptive header on a report that relates to that server.
CONNINFO contains connection information, one observation for each time a user connects to the server and one observation for each time a user disconnects from the server.
This data set can be used to obtain a list that shows who connected to a server, how long each user remained connected, or how many times each user connected to the server. This data set can also be used to chart the simultaneous number of connections to a server over a period of time, looking for peaks and valleys in the number of users who access data through a server.
CONNSUM contains only one observation that has one variable, which stores the total number of connections to this server.
TASKINFO contains one observation for each creation of a mirror resource environment and one observation for each termination of a mirror resource environment.
The name of a resource environment in this data set corresponds to the name of a SAS procedure or a window that is used to access data through the server. (SAS procedures and windows that are not used to access data through a server are not recorded in this data set.)
This data set can be used to obtain a list of SAS procedures and windows that were used to access data through the server, and the amount of time each procedure or each window remained active.
LIBINFO contains one observation for each time a user accesses a SAS library and one observation for each time a user releases a SAS library.
This file can be used to determine how many times each library was accessed through the server and the length of time that each library was accessed. You should use the "physical name" variable because each library can be referred to by different librefs at different times.
To obtain a list of the libraries accessed through a server, use the file SLOGDATA.PHYSINFO.
PHYSINFO contains a list of the physical names that correspond to libraries that were accessed through the server.
ENGSUM1 contains a list of the engines that were used to access SAS data libraries through the server.
MEMINFO contains an observation for each time a SAS library member is opened, re-opened, closed, re-named, repaired, or deleted.
This file, which tends to be very large, can be used to derive a list of members for each library that has been accessed through the server; the amount of time each member was accessed; how many times each member was accessed; whether each member was read, updated, or created; and the number of simultaneous users of each member over a period of time.
You should use the "physical name" variable because each library can be referred to by different librefs at different times.
OBJINFO contains an observation for each time a SAS catalog entry is opened, closed, re-named, deleted, aliased, or has its directory information or options changed.
This file is similar to the file SLOGDATA.MEMINFO, but it contains information for catalog entries instead of members of SAS libraries.
IDXINFO creates an observation for each time a user creates or deletes an index through the server.
Because creating an index tends to be expensive, this file is probably most useful as a warning signal. Furthermore, because indexes tend to be very helpful for SAS data sets that are accessed concurrently, having a list of indexes that were deleted during a server's session can also be a warning signal.
DIRINFO contains an observation for each time the directory of a SAS library or the directory of a SAS catalog is opened or closed through the server.
IDXSUM contains only one observation that has two variables. One variable counts how many indexes were created through the server; the other variable counts how many indexes were deleted through the server.
ACCTINFO contains one observation for each accounting message that is written to the server's log when a user disconnects. You must specify the LOG= option in the PROC SERVER statement to collect this data.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.