Enabling the self-describing agent feature at a monitoring server

By default, the self-describing agent feature is disabled. If you want to use the self-describing agent (SDA) feature, you must enable it at the agent and the remote monitoring server to which the agent reports, and at the hub monitoring server to which the remote reports.

1. If you are configuring a monitoring server as part of this runtime environment and you want to enable SDA support, perform a FIND on KDS_KMS_SDA in the RTE configuration profile.
2. Change the value from N to Y.
   Figure 1 shows an example of this change.

   SP22 				TSTEST.&userid.DEMO.WCONFIG(DEMO)
   Command ===>                                                  Scroll ===> CSR
   000839 ** Enable TEMS Self-Describing Agent (SDA) processing:
   000840 ** This is required if you are enabling the Self-Describing
   000841 ** Agent (SDA) functionality in the z/OS TEMS and Agents:
   000842 ** Note: By default, the TEMS KMS_SDA xKANPARU(KDSENV) parameter is
   000843 **       initially disabled (KMS_SDA=N). Enabling SDA requires USS
   000844 **       system preparation set-up tasks to create the USS file system.
   000845 **       Review other required PARMGEN profile parameters to complete
   000846 **       SDA enablement.
   000847 ** Related PARMGEN CONFIG profile parameters:
   000848 **       - GBL_HFS_JAVA_DIRn (typically in WCONFIG($GBL$USR))
   000849 **       - GBL_DSN_SYS1_SBPXEXEC (typically in WCONFIG($GBL$USR))
   000850 **       - RTE_USS_RTEDIR
   000851 **       - RTE_USS_MKDIR_MODE
   000852 **       - KDS_KMS_SDA_NO_GRANULAR (applicable to ITM6.3.0+ only)
   000853 **       - KDS_TEMA_SDA
   000854 **       - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA)
   000855 ** --------------------------------------------------
          KDS_KMS_SDA                N     * Enablement Parameter *
   

   Ensure that the related parameters are set appropriately. The related GBL_ parameters are found in the WCONFIG($GBL$USR) profile for further customization.