<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">Date:    October 21, 1998

Product: 3.6-SEN-OS2

Component: Distributed Monitoring (DM) OS/2 Gateway

Architecture(s): OS/2

Patch: 3.6-SEN-OS2

Introduction: This product, and the accompanying patch, 3.6-SEN-0009,
              provide a set of functionality for the OS/2 platform that
              allows an OS/2 machine to act as a Distributed
              Monitoring (DM) gateway. This allows TMA Endpoints to
              send DM monitor responses through the gateway to other 
              DM managed nodes or endpoints throughout the managed 
              environment. This Distributed Monitoring 3.6 
              OS/2 Gateway product should only be installed on OS/2 
              managed nodes. It installs a complete set of binaries,
              libraries, database, and message catalog files for this
              product.

Problems Fixed: Provides Endpoint Functionality for OS/2 platform
Pre-installation requirements:

        * Install patch 3.6-TMF-0021
	* DM 3.6 installed on at least one TMR server
	* TME 3.6 installed on each OS/2 machine
  	  to be installed as a DM Gateway

Product Contents:

	* This README file
        * A cdrom image for this product 

Applying the Product:

    1)	From a UNIX system:
	
	Extract the contents into a scratch directory. For the purpose of this 
	release note, assume that the symbol $PRODUCT points to this directory. 

	# cd $PRODUCT
	# tar xvf 3.6-SEN-OS2.tar

	From a Windows NT system:

	Place the product tape in the tape drive and extract the contents into
	a scratch directory. For the purpose of this release note, assume that
	the symbol %PRODUCT% points to this directory.

	&gt; %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
	&gt; X:		  
          ^-- 'X' is drive letter where %PRODUCT% is found
	&gt; cd %PRODUCT%
	&gt; tar xvf 3.6-SEN-OS2.tar

	NOTE:  If you are extracting the tar image on a Windows NT system,
	you will find an executable for tar in the TME installation on
	Windows NT under bin/w32-ix86/tools/tar.exe.

    2)  Use the following steps to install the product using SIS, the
        Tivoli Software Installation Service

        NOTE: SIS can install Tivoli products on any hardware
              platform supported by Tivoli, but there are some
              hardware platforms on which SIS cannot be run. Please
              check your SIS User's Manual for the list of platforms
              on which SIS can be run.

	NOTE: You must have the install_product and super authorization 
              roles to successfully install this product.

        a)  From the Tivoli Desktop, pull down 
            Desktop --&gt; Install --&gt; Software Installation Service.
        b)  SIS will initialize, and bring up the Get Installation
            Password Dialog.  Enter your Installation Password.
        c)  Press the Install Button on the dialog which contains
            the Tivoli image.
        d)  Press the Select Product Button on the Install Spreadsheet
            Dialog.
        e)  Press the Import Product Button on the Select Product
            Dialog.
        f)  Locate the media to 3.6-SEN-OS2 using the file browser, and
            select the CONTENTS.LST file by double-clicking it.
        g)  Select 3.6-SEN-OS2 in the Import Product Dialog, and click
            the Import Button.
        h)  When the import is complete, click the OK Button on the
            Global Progress Dialog.
        i)  Select 3.6-SEN-OS2 in the Select Product Dialog, if it is
            not already selected, and click the OK Button.
        j)  Now click the Select Machine Button on the Install
            Spreadsheet Dialog.
        k)  Select the machine(s) you would like to install 3.6-SEN-OS2
            to, and click the OK Button.
        l)  Click the appropriate cell(s) in the Install Spreadsheet
            Dialog. (NOTE: This should yield an "X" in the cell(s)
            for the machines you want to install 3.6-SEN-OS2 to).
        m)  Press the Install Button.
        n)  Select the install algorithm you want to use on the
            Installation Algorithm Dialog, and click OK.
        o)  SIS will perform the installation(s) you designated
            in the Install Spreadsheet Dialog.
 
        - OR -

    	Use the following steps to install the product using the old
        Tivoli install mechanism.
	NOTE: You must have the install_product and super authorization roles
	to successfully install this product.

        a)  Select the "Install -&gt; Install Product..." option from the
           "Desktop" menu to display the "Install Product" dialog.

        b)  Press the "Select Media..." button to display the "File Browser"
	    dialog.

        c)  Enter the path to the directory containing the product, $PRODUCT, in
	    the "Path Name:" field.

        d)  Press the "Set Media &amp; Close" button to return to the "Install
            Product" dialog.

        e)  The product install list now contains the name of the product.
            Select the product by clicking on it. 

        f)  Select the clients to install this product on. This product changes
            two binaries and needs to be installed on the TME server and 
            on each client.

        g)  Press the "Install" button to install the product.


Using the New Distributed Monitoring OS/2 Gateway:

    Although the DM OS/2 Gateway product has the same functionality
    as the gateways on other managed node machine types
    (Unix, Windows NT, etc), there are a few implementation 
    distinctions.
 
        * As a precursor to future enhancements, there is no Distributed 
          Monitoring engine on the OS/2 Managed Node. Monitoring of the 
          OS/2 Managed Node itself can be accomplished by simply 
          installing a TMA Endpoint on the machine and managing it as 
          if it were any other endpoint.

        * As a corollary to the above, if you attempt to run some
          standard DM command line utilities and select the OS/2 
          Managed Node engine, you will get different output than
          if you selected another manage node type or a TMA 
          Endpoint engine.

          For example, if you run the "wlseng" command like this:

               "wlseng os2_managed_node_machine"

          you will get 

               "No monitoring engine found"

          But if you run

               "wlseng solaris_managed_node_machine"

          or

               "wlseng -z nt_endpoint_machine"

          you will get the normally expected output from those engines.


          These commands are provided on the DM OS/2 Gateway product
          because you can use them for other managed nodes and TMA Endpoints
          in the management environment.

Known problems/issues:

    * There is a slight problem with Netware TMA Endpoints logging remote
      files to a OS/2 Gateway machine. 
 
      If you have a Netware TMA Endpoint logged into any gateway, and
      you set up a monitor that runs a program or logs to a file on
      a host machine, and that host machine is an OS/2 Gateway machine,
      then the file run or the log to file will not work. If you select
      any other type of host for these operations, they will succeed.

      This problem will be addressed by the DM 3.6.1 Maintenance release
      when it becomes available.

</pre></body></html>