A fix is available
APAR status
Closed as program error.
Error description
ENHANCEMENT FOR AGENT'S "COMPLETE THE CONFIGURATION" When customer's agent connects to a non-local z/OS HUB TEMS (Scenario B see below). the customer must install the product also in the CSI or target libraries on the LPAR where the HUB TEMS is running. KCIPRDM1 ---------------- COMPLETE THE CONFIGURATION COMMAND ===> SCROLL ===> CSR The following steps only apply if the Tivoli Enterprise Monitoring Agent (TEMA) is running in its own Agent address space and connects to a non-local z/OS TEMS: Note: A non-local z/OS TEMS pertains to a TEMS defined in another RTE based on the following scenarios: 1. The TEMS (Hub or Remote) is known to this TDOMPT.ITM621.INSTLIB installation library. 2. The TEMS (Hub or Remote) is defined in another INSTLIB (or another CSI) that is not accessible to this TDOMPT.ITM621.INSTLIB installation library. Scenario A: If the Agent's primary TEMS is a non-local z/OS Remote TEMS The Agent must also be installed in the non-local INSTLIB or CSI environment where the z/OS Remote TEMS is installed. In the non-local installation environment where the z/OS Remote TEMS is configured, perform one of two required steps. Step 4a - Copy and refresh the Agent's catalog and attribute files in the non-local z/OS Remote TEMS. Perform one of two steps below: - Execute the RTE Load step in the Remote TEMS RTE ("Load all product libraries after SMP/E" option from the RTE panel) -or- - Execute the "Upgrade attribute and catalog members" option from the RTE Utility menu. Alternative: Applicable if the Agent is not installed in the same CSI as the non-local z/OS Remote TEMS's CSI: You must copy this Agent's catalog and attribute files into the z/OS Remote TEMS' RKANDATV library manually. This Agent's catalog and attribute files are as follows: - CCAPI.SPE.AGTINIRA.RKANDATV(KD5CAT) - CCAPI.SPE.AGTINIRA.RKANDATV(KD5ATR) These members are required in both the Agent's RKANDATV library and in the non-local Remote TEMS' RKANDATV dataset. Refresh these members in the respective RKANDATV libraries when SMP/E maintenance that changes these members is applied. Scenario B: If the Agent's primary TEMS is a non-local z/OS Hub TEMS or if the Agent's primary TEMS is a Remote TEMS and this Remote TEMS is reporting to a non-local z/OS Hub TEMS, then the Agent must also be installed in the non-local INSTLIB or CSI environment where the z/OS Hub TEMS is installed. In the non-local installation environment where the z/OS Hub TEMS is configured, perform the following TEMS registration step. Step 4b - Register the TEMA with the non-local z/OS Hub TEMS. Execute the Register with local TEMS step in the RTE where the non-local z/OS Hub TEMS that this Agent is connected to. Note: The currently selected primary TEMS name is VDCTW. Step 5 - Seed the TEMS using Manage Tivoli Monitoring Services (if applicable). Seed the Hub Tivoli Enterprise Monitoring Server (TEMS) using Manage Tivoli Monitoring Services. This step is only applicable to the Hub TEMS that the Agent reports to. . . UP or DOWN to browse or END to return. Type PRINT to print.
Local fix
When customer's agent connects to a non-local z/OS HUB TEMS (Scenario B see below). the customer must install the product also in the CSI or target libraries on the LPAR where the HUB TEMS is running.
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - ICAT * **************************************************************** * PROBLEM DESCRIPTION: Currently, there is a requirement to * * install the Agent FMIDs in both CSIs if * * the Tivoli Enterprise Monitoring Agent * * is installed and configured in one CSI * * and its z/OS Hub TEMS is installed and * * configured in a separate CSI. This is * * not clearly documented in the Complete * * the configuration text. * * * **************************************************************** * RECOMMENDATION: Apply this PTF * **************************************************************** PROBLEM SUMMARY: The requirement to install the Agent FMIDs in both CSIs if the Tivoli Enterprise Monitoring Agent is installed and configured in one CSI and its z/OS Hub TEMS is installed and configured in a separate CSI is not properly documented in the Complete the configuration text. PROBLEM CONCLUSION: Improve documentation in Complete the configuration.
Problem conclusion
Improve documentation in Complete the configuration. KEYWORDS : REGISTER NON-LOCAL Z/OS TEMS AGENT
Temporary fix
Comments
APAR Information
APAR number
PK83247
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-24
Closed date
2009-04-08
Last modified date
2009-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK45608
Modules/Macros
KD541DFI
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK45608
UP09/04/22 P F904
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 May 2009