Potential Situations and Solutions

Situation

Action

SiteAnalyzer displays a message that the SU job is down.

If the SU job is not down, make sure that the dataset name listed in ddname SMARTSU in the FOCUS startup procedure is the same as the name listed in the SU JCL pointed to by the ddname FOCSU.

Make sure that the communications dataset is allocated to ddname SMARTSU in the FOCUS startup procedure or is listed in the GKSINK ERRORS file.

SiteAnalyzer is not collecting records in the Usage Monitoring Database.

Make sure that the all the SM files are properly allocated to the SU job.

Make sure the SMARTSU ddname is allocated in the FOCUS startup procedure or in the GKSINK ERRORS file.

The SU job may not be down, but SiteAnalyzer is still unable to communicate with it. Enter ? SU SMARTSU from the FOCUS prompt and look for an error message.

The SU job may appear to be executing, but it is waiting for data sets.

SiteAnalyzer displays a message that the SiteAnalyzer library is unavailable.

SiteAnalyzer could not find the GKTABLE file, which it needs to collect data.

For MVS, make sure that the GKTABLE member of SMARTLIB.DATA is available to FOCUS.

For VM, make sure that GKTABLE SMARTLIB is available to FOCUS.

Check to see whether the SMARTLIB dataset has been allocated as OLD by some JOB or user. If it has, change the allocation to SHR.

SiteAnalyzer monitors, but data is garbled and/or unreadable in SMCNTRL.

Make sure that the correct Master File exist on the SU sink machine and that they match those found on the source machine.

For more information on improving SU performance, see the Simultaneous Usage for OS/390 and MVS User's Manual.

Information Builders

Situation	Action
SiteAnalyzer displays a message that the SU job is down.	If the SU job is not down, make sure that the dataset name listed in ddname SMARTSU in the FOCUS startup procedure is the same as the name listed in the SU JCL pointed to by the ddname FOCSU. Make sure that the communications dataset is allocated to ddname SMARTSU in the FOCUS startup procedure or is listed in the GKSINK ERRORS file.
SiteAnalyzer is not collecting records in the Usage Monitoring Database.	Make sure that the all the SM files are properly allocated to the SU job. Make sure the SMARTSU ddname is allocated in the FOCUS startup procedure or in the GKSINK ERRORS file. The SU job may not be down, but SiteAnalyzer is still unable to communicate with it. Enter ? SU SMARTSU from the FOCUS prompt and look for an error message. The SU job may appear to be executing, but it is waiting for data sets.
SiteAnalyzer displays a message that the SiteAnalyzer library is unavailable.	SiteAnalyzer could not find the GKTABLE file, which it needs to collect data. For MVS, make sure that the GKTABLE member of SMARTLIB.DATA is available to FOCUS. For VM, make sure that GKTABLE SMARTLIB is available to FOCUS. Check to see whether the SMARTLIB dataset has been allocated as OLD by some JOB or user. If it has, change the allocation to SHR.
SiteAnalyzer monitors, but data is garbled and/or unreadable in SMCNTRL.	Make sure that the correct Master File exist on the SU sink machine and that they match those found on the source machine.