Installation and Configuration Steps

The following section describes how to install and configure SiteAnalyzer. You must complete three steps to install SiteAnalyzer for FOCUS VM:

1. Execute the SMINSTAL FOCEXEC.

2. Create the GKSINK ERRORS file (optional).

3. Modify the FOCPARM ERRORS file.

Procedure: How to Execute the SMINSTAL FOCEXEC

1. Log on to the sink ID and link to and access the FOCUS maintenance disk. See the Simultaneous Usage Reference Manual for CMS for information about using sink machines.

2. Enter FOCUS and execute the SMINSTAL FOCEXEC:

   EX SMINSTAL

This EXEC creates and initializes the SiteAnalyzer databases by default on the sink's A disk.

3. Add SET SMARTMODE=ON to the FOCPARM ERRORS file.

4. Enter the VM user ID that runs the FOCUS Simultaneous Usage Facility.

SMINSTAL displays a message as each file is created to inform you of its progress. For some, file transaction information is also displayed:

NEW FILE SMPRMTRSFOCUS   A1 ON 06/27/2003 AT 12.48.54
>
SMPRMTRSFOCUS   A1 ON 06/27/2003 AT 12.48.57
TRANSACTIONS:      TOTAL =     1  ACCEPTED=     1  REJECTED=     0
SEGMENTS:          INPUT =     1  UPDATED =     0  DELETED =     0
>
NEW FILE SMCNTRL FOCUS   A1 ON 06/27/2003 AT 12.48.59

When SMINSTAL completes, the following messages are displayed:

*******************
* Files created.  *
*******************
 
**************************************************************
* SiteAnalyzer SmartMode installed successfully.             *
**************************************************************

5. When you see the message indicating that initialization is complete, exit FOCUS.

If you used an ID other than the sink ID to initialize SiteAnalyzer, or if you do not want these databases on the sink's A disk, you may move them to any of the sink's other disks. See How to Create the GKSINK ERRORS File to create a file, which directs SiteAnalyzer to the new location of these databases. You must execute this step, however, even if you do want to accept the default location.

6. The default GKTABLE SMARTLIB is created when the SMINSTAL FOCEXEC is executed. It will be on the A disk along with the Master Files and the FOCUS database files. The Master Files can be moved to the FOCUS production disk. This will allow the Sink user ID and the Admin user ID access to them without having to link and access any additional mini-disks.

GKTABLE SMARTLIB should be moved to the user ID and mini-disk specified in the second record of the GKSINK ERRORS file, or placed on the FOCUS production disk if you choose not to add the second record. For more information, see How to Create the GKSINK ERRORS File. If you choose to put the GKTABLE SMARTLIB on the FOCUS production disk, then each time that Usage Monitoring information is changed, the file must be moved to the FOCUS production disk. The user will not see the changes in the file until the production disk is accessed again. If you choose to use the second record in the GKSINK ERRORS file, the updated GKTABLE SMARTLIB must be moved. Each time FOCUS is executed, the user ID and mini-disk are linked and accessed.

Procedure: How to Create the GKSINK ERRORS File

SiteAnalyzer uses the GKSINK ERRORS file to direct FOCUS users' sessions to the appropriate sink machine and to the location of the SiteAnalyzer Usage Monitor Table (GKTABLE SMARTLIB). In order to be monitored by SiteAnalyzer, users must have read access to GKSINK. The GKSINK ERRORS file may have one or two lines. Create it for the users that SiteAnalyzer will monitor, according to the following specifications:

• Line 1 of GKSINK will contain two fields:
• Column 1 must contain the sink ID.
• Column 10 must contain the filemode on the sink ID that contains the SiteAnalyzer database files created in Step 1. Execute the SMINSTAL FOCEXEC.

• Line 2 is optional. If you do not include it, GKTABLE SMARTLIB must be available in the user's search order when FOCUS is involved.

If you do include line 2, it may contain two or three fields:

• Column 1 is required. It must contain the user ID that contains the SiteAnalyzer Usage Monitor Table, GKTABLE SMARTLIB.
• Column 10 is required. It must contain the disk address on the user ID that holds GKTABLE SMARTLIB.
• Column 15 is optional. It may contain the filemode to which SiteAnalyzer will dynamically attach the mini-disk ID. If you do not specify a filemode by leaving column 15 blank, SiteAnalyzer will link the mini disk and access it to the next available filemode.

The following is an example of a GKSINK ERRORS file:

|...+....1....+....2....+....3....+....4....+....5
SASINK   P
SAUMON   192  J

Procedure: How to Modify the FOCPARM ERRORS File

The FOCPARM ERRORS file is located on the FOCUS production mini-disk. To turn on SiteAnalyzer you must add SET SMARTMODE=ON as the last record in the file. This setting will cause FOCUS to read the GKSINK ERRORS file. SiteAnalyzer will not monitor any FOCUS requests if this file is not available to be read.