You must create a common MIB environment definition file (pdmibtgt). Specify in this file the HiRDB identifier of the HiRDB to be monitored and the HiRDB directory name. A specification example follows:

 
pdmib -a HiRDB-system-identifier -d HiRDB-directory-name
 

Explanation

• Create the common MIB environment definition file in the HiRDB installation directory: /sample/pdmibtgt.
• In the case of a HiRDB parallel server configuration, create the common MIB environment definition file in the server machine where the system manager is defined.
• To monitor multiple HiRDBs in a multi-HiRDB environment, specify multiple lines. A specification example follows:

 
   pdmib -a HRD1 -d /hirdb_x1
   pdmib -a HRD2 -d /hirdb_x2

You must create an individual MIB environment definition file (pdmibenv). Specify in this file the environment for executing HiRDB commands and utilities. A specification example follows:

 
putenv PDHOST host-name-of-HiRDB-server-to-be-connected
putenv PDDIR HiRDB-directory-name-of-HiRDB-server-to-be-connected
putenv PDNAMEPORT port-number-of-HiRDB-server-to-be-connected
putenv PDUSER authorization-identifier-and-password
putenv LANG character-code-classification
 

Explanation

• The specification of each operand is the same as in the client environment definition. For details about the client environment definition, see the HiRDB Version 9 UAP Development Guide.
• Create the individual MIB environment definition file in $PDDIR/conf/pdmibenv ($PDDIR is the HiRDB directory name specified in (1)).
  

  Note

  If you use the pdchgconf command to modify PDNAMEPORT while HiRDB is running, you must also modify the pdmibenv file.

Register into JP1/ESA the MIB definition file provided by HiRDB. In the case of a HiRDB parallel server configuration, register it in the server machine where the system manager is defined. For details about registering into JP1/ESA, see the manual Job Management Partner 1/Consolidated Management 2/Extensible SNMP Agent.

The path name for the MIB definition file is as follows:

• /opt/HiRDB_S/sample/hirdbMIB (HiRDB single server configuration)
• /opt/HiRDB_P/sample/hirdbMIB (HiRDB parallel server configuration)

Notes about a multi-HiRDB

• Register the MIB definition file of the HiRDB in whose directory the pdmibtgt file was created.
• If the HiRDB whose MIB definition file was registered is uninstalled, you will have to re-register the MIB definition file of a HiRDB that has not been uninstalled.

Because MIB commands are executed with the superuser privilege, a superuser must set up the remote shell execution environment. Settings that permit mutual logon between any server comprising the HiRDB parallel server configuration and the server machine where the system manager is defined must be specified in /etc/hosts.equiv or /.rhosts.

Add the installation directory /lib to the superuser's SHLIB_PATH environment variable. For the Solaris and Linux editions, add the installation directory /lib to the superuser's LD_LIBRARY_PATH environment variable; for the AIX edition, add the installation directory /lib to the superuser's LIBPATH environment variable.

(a) Using JP1/SSO for Database

Use JP1/SSO for Database to select the performance information that you wish to collect. For details about the selection method, see the manual Job Management Partner 1/Performance Management/SNMP System Observer for Extended Resource Management.

Note

Depending on the environment applicable to the history to be monitored and the MIB for which information is to be collected, an SNMP timeout error might occur. In such a case, adjust appropriately the SNMP timeout value for JP1/NNM or JP1/ESA.

(b) Using another company's Management Framework

See the relevant manuals for other company's Management Framework.