Resolving The Problem

Use the Enhanced 3270UI or the TEP to determine the Sysplex Proxy TEMS:

Start with the HUB that the TEP or Enhanced 3270UI is connected to. For the example steps here the TEMS STC name is M5D0HAHB:

1. Via the Enhanced 3270ui

• log on to the Enhanced 3270ui the connected hub (type '=KOBHUB03' on top/menu line or Tools-->Current Hub Information)

• use the 'NEXT' pushbutton to go to the HOBHUBS, 'All Known Hubs', workspace

• Enter 'T' next on the row with 'Hub Name' that matches the current Hub (highlighted) to navigate to the KOBHBTPO 'Hub Topology' workspace.



• scroll to the list of nodes under 'zos' in the 'Origin Node' column and note all rows with a 'Sysplex' qualifier in the Origin Node name along with their associated 'Managing System'. Now, for these Managing Systems note those with an Origin Node name with the 'MVSSYS' qualifier (in below, Origin Node LPAR400J:MVS:SYSPLEX has Managing System M5510R23:CMS, and for this Managing System, Origin Node LPAR400J:SP23:MVSSYS has the desired 'MVSSYS' qualifier). This Origin Node contains the SMFID for the system with the potential Sysplex Proxy TEMS. Note this SMFID and the Managing System Name (in below, SP23 and M5510R23:CMS).

• Scroll back to the list 'Hub and Remote TEMS' in the 'Origin Node' column. Find the Origin Node that matches the Sysplex node 'Managing System' AND that reports to the current Hub (for our example we found LPAR400J:MVS:SYSPLEX has Managing System M5510R23:CMS and as we see below it reports to the current Hub).

• Use the noted SMFID and continue below at (c) to locate the Sysplex Proxy TEMS.

• go to workspace KOBMSNS ( 'Only Managed Systems' type '=KOBMSNS' on top/menu line to get there)
• scroll on the 'Hub TEMS Name' column until you find the rows containing a qualifier with the connected TEMS stc name (here, the rows with M5D0HAHB:CMS in column Hub TEMS Name)
• find the row that has a node qualifier of 'SYSPLEX' in the Managed System Name

• get the MS ThruNode for this row (M5510R14:CMS)

• match this MS ThruNode to the MS ThruNode for a TEMS with our HUB in the Hub TEMS Name (we can see 1 in the last line of above display)

• the Managed System Name includes the SMFID for the system with the potential Sysplex Proxy TEMS. Note this SMFID.

• Find the correct Sysplex Proxy TEMS on the system with the noted SMFID. There is likely only one. Verify the correct TEMS by searching the RKLVLOG for the HUB name (search for 'nodename'):

2. via the TEP

• log on to the TEP and verify the connected hub via the Enterprise 'Manage Tivoli Enterprise Monitoring Servers' or Self-Monitoring Topology workspace

• select the Enterprise 'Manage System Status' workspace; click on the "Product" column heading to sort all the M5 entries together

• find the 'Name' (and 'Origin node') that matches the Sysplex name on the nav tree branch; note the 'Managing System' for this row (M5510R14:CMS in above)
• find another row with this same 'Managing System' that has a 'Name' (and 'Origin Node') with a 'MVSSYS' qualifier (3 rows above selected row in above)
• The SMFID in the 'Name' (and 'Origin Node') for this row will be for system the Sysplex Proxy TEMS is running on.
• find the correct TEMS as described above in step 'c' for finding the Sysplex Proxy TEMS using the Enhanced 3270ui