When you are running SiteAnalyzer and collecting usage monitoring data at a site that has multiple partitions, SiteAnalyzer will not pass usage monitoring data across LPARs. Thus for each LPAR, you must have a separate SU sink machine, on which you must place a separate set of Usage Monitoring databases. In addition, each LPAR must have its own copy of the SU communications dataset (SMARTSU.DATA), which must be locally cataloged for that LPAR. SiteAnalyzer uses a member in ERRORS.DATA called GKSINK to point Usage Monitoring to the appropriate SU machine.
The following diagram depicts the architecture of multi-LPAR usage monitoring:
When a user logs on to a particular LPAR and makes a request to a database, SiteAnalyzer checks the first line of the GKSINK member of the ERRORS.DATA dataset (which resides on the shared copy of FOCUS) for the name of that LPAR's locally cataloged SMARTSU.DATA dataset. This ensures that any usage monitoring data associated with that request is directed to the appropriate SU sink machine and Usage Monitoring databases for that LPAR.
A new feature to allow a single GKSINK member to be used by all LPAR configurations was introduced in release 7.08. A variable, &SYSNAME, can be used when defining any record in the GKSINK member. The value of &SYSNAME will be substituted with the SYSID of the LPAR being used by the user or batch. Here is an example of this feature:
prefix.ERRORS.DATA (GKSINK)
SYS1.&SYSNAME.SMARTSU.DATA
SYS1.SMARTLIB.DATA
FOCUS execution results (SYSID is IBI1)
SYS1.IBI1.SMARTLIB.DATA
SYS1.SMARTLIB.DATA
| Information Builders |